| Course | BUS 799 Graduate Capstone |
|---|---|
| Module | Module 1 |
| Paper type | Capstone proposal |
| Length | About 1,114 words, 7 pages |
| Format | APA 7 student paper |
| School | Aspen University |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for BUS 799 Module 1
Seventy-One Days to Get Paid: A Capstone Proposal to Shorten Collections at a Commercial Electrical Contractor
Student Name
Master of Business Administration Program, Aspen University
BUS 799: Graduate Capstone
Instructor Name
Month Day, Year
Seventy-One Days to Get Paid: A Capstone Proposal to Shorten Collections at a Commercial Electrical Contractor
A graduate capstone should solve a real problem that matters to the organization and can be completed within the course. This proposal describes such a project at Keystone Electric, a composite commercial electrical contractor where the author works as a project controls analyst. Keystone collects its receivables too slowly, and the delay forces it to borrow against its credit line to meet payroll. The proposal defines the problem, explains its significance, sets objectives and scope, describes the method, and lists the deliverables and timeline.
The Organization
Keystone Electric installs electrical systems in commercial buildings, schools, and health care facilities in a three-state region. It has 210 employees and annual revenue of about $38.0 million. Most work is performed as a subcontractor to general contractors, and the company bills monthly through progress payment applications, which the general contractor and project owner must approve before paying. Contracts typically allow the general contractor to hold back 10 percent of each payment as retainage until the project is complete.
The Problem
Keystone's days sales outstanding, accounts receivable divided by average daily revenue, averaged 71 days over the last four quarters. At $38.0 million in revenue, each day of receivables represents about $104,100, so Keystone carries roughly $7.39 million in receivables. The company's owners have set a target of 50 days. Reaching it would free about $2.19 million in cash. Because Keystone draws on a credit line at about 8 percent interest to cover payroll while it waits to be paid, the lower balance would save about $175,000 a year in interest and reduce the risk of a cash shortage during a slow month. Keystone is profitable on paper and short of cash in practice, and the gap between the two is 21 days.
Significance
The link between collection speed and business performance is well documented. In a study of 1,009 large Belgian firms, Deloof (2003) found that managers could increase profitability by reducing the number of days of accounts receivable and inventories, and a study of 8,872 small and medium-sized Spanish firms reached a similar conclusion, that shortening the days accounts are outstanding and the cash conversion cycle improved profitability (García-Teruel & Martínez-Solano, 2007). In construction specifically, a survey of New Zealand practitioners found that payment problems cluster around contractual issues, the financial strength of other parties, disputes, shortcomings in payment processes, and knock-on effects along the payment chain (Ramachandra & Rotimi, 2015). Some of these causes lie outside a subcontractor's control, but process shortcomings and disputes can be addressed from within.
Objectives and Scope
The project has three objectives: to measure how each stage of Keystone's billing and collection process contributes to its 71 days; to identify the causes of delay that Keystone can control; and to design, cost, and plan the implementation of changes expected to bring days sales outstanding to 50 within 12 months. The scope includes progress billing, change order documentation, retainage release, and collections. It excludes renegotiating contract terms with general contractors, changing the company's credit line, and pursuing legal claims on disputed accounts, which are decisions for the owners. The capstone will deliver a plan and a pilot on two projects; full implementation will follow after the course.
Research Questions
Three questions will guide the analysis. First, how many of Keystone's 71 days are attributable to each stage: the time from the end of a billing period to submission, the general contractor's and owner's review, payment after approval, rejected applications, unapproved change orders, and retainage? Second, which of those stages are within Keystone's control, and what specific practices cause delay in each? Third, what combination of changes would plausibly remove 21 days, at what cost, and in what order should they be introduced? The first two questions are descriptive and diagnostic; the third is prescriptive and will be answered with a costed plan.
Method
The project will follow the DMAIC structure used in Six Sigma process improvement: define, measure, analyze, improve, and control. Linderman et al. (2003) argued that Six Sigma's effectiveness comes partly from setting specific, challenging goals and pursuing them through a structured method, which fits a project with a clear numerical target. Data will come from the accounting system's receivables aging and 24 months of payment applications, a sample of late invoices coded by cause, and interviews with project managers, the controller, and two general contractors' accounts payable staff.
Confidentiality and Ethics
The project uses Keystone's financial records and the payment histories of its customers, which are confidential. The owners have approved the project in writing on three conditions: customer names will be replaced with codes in all course documents, no contract terms will be quoted, and interview participants will be told that their comments are for internal improvement and will not be attributed to them by name. Because the author is an employee, there is a risk of bias toward conclusions that favor the project controls department. To reduce it, the controller will review the cause coding of late invoices, and the analysis will report findings that reflect poorly on any department, including the author's own.
Assumptions and Project Risks
The proposal assumes that 24 months of payment application data are complete in the accounting system, that project managers will be available for interviews during the busy summer season, and that two general contractors will agree to share how they review subcontractor applications. If the data prove incomplete, the analysis will rely on a larger sample of invoices traced by hand. If general contractors decline to participate, their review process will be inferred from rejection notices and email records. The largest risk is that the pilot projects end or change phase during the course, which would be managed by selecting pilots with at least six months of billing remaining.
Deliverables and Timeline
The capstone will produce a literature review, a data collection plan, a current-state analysis with causes ranked by their contribution to days outstanding, a stakeholder and change plan, recommendations with an implementation schedule, a financial justification, and a final report and presentation to Keystone's owners. The work will follow the eight modules of the course, with the current-state analysis complete by the fourth module and the pilot running during the sixth and seventh.
Conclusion
Keystone Electric waits 71 days to collect what it bills, which ties up about $2.19 million beyond its target and costs about $175,000 a year in interest. This capstone will measure where those days come from, focus on the causes the company controls, and deliver a costed plan to reach 50 days, benefiting the organization and developing the author's skills in process improvement and financial analysis.
References
Deloof, M. (2003). Does working capital management affect profitability of Belgian firms? Journal of Business Finance & Accounting, 30(3-4), 573-588. https://doi.org/10.1111/1468-5957.00008
García-Teruel, P. J., & Martínez-Solano, P. (2007). Effects of working capital management on SME profitability. International Journal of Managerial Finance, 3(2), 164-177. https://doi.org/10.1108/17439130710738718
Linderman, K., Schroeder, R. G., Zaheer, S., & Choo, A. S. (2003). Six Sigma: A goal-theoretic perspective. Journal of Operations Management, 21(2), 193-203. https://doi.org/10.1016/S0272-6963(02)00087-6
Ramachandra, T., & Rotimi, J. O. B. (2015). Causes of payment problems in the New Zealand construction industry. Construction Economics and Building, 15(1), 43-55. https://doi.org/10.5130/ajceb.v15i1.4214
BUS 799 Module 1 instructions, in plain terms
The first BUS 799 module at Aspen generally wants a proposal for a project you will carry out where you work. Introduce the company in a paragraph. Put a number on the problem, then convert that number into money. Show why it matters, with evidence from research. Set a few objectives and define the scope, including what is out of scope. Write research questions the project will answer. Choose a method and justify it. Explain how you will protect confidential data and what the organization has approved. List assumptions and risks. Give deliverables and a timeline. Keep the organization composite in course documents, and pick a problem small enough to finish but large enough to matter to the owners.
Inside the BUS 799 Module 1 example
The introduction states that a capstone should solve a real problem the organization cares about. The organization section describes Keystone's work as a subcontractor in three states. The problem section defines days sales outstanding and translates 71 days into about $7.39 million in receivables. The significance section reports Deloof's finding and the cost of borrowing to cover the gap. The objectives section sets three aims: measure each stage, find controllable causes and design changes. The research questions section asks how many days each stage contributes, what causes late invoices and what would recover them. The method section explains define, measure, analyze, improve and control. The ethics section lists the owners' conditions. Assumptions, deliverables and a timeline close the proposal.
Where the marks sit in the BUS 799 Module 1 rubric
Capstone proposals in BUS 799 earn credit for a clearly defined problem with financial stakes, evidence of significance, focused objectives, answerable research questions, a suitable method and attention to ethics. This example earns marks by translating days into dollars, which tells graders the student understands why the owners care. Deloof's 2003 article in the Journal of Business Finance and Accounting supports the link between receivables and profitability. Linderman and colleagues' 2003 article in the Journal of Operations Management supports the DMAIC method. The confidentiality section, with written approval and coded customer names, shows professional conduct. Listing risks such as interview availability in a busy season shows realistic planning.
Common BUS 799 Module 1 mistakes, and how to avoid them
Capstone proposals often describe a problem without numbers. Quantify it and convert it to dollars. Another common gap is a scope too broad to finish; set objectives the course can accommodate. Students also skip ethics when using company data. Get written approval and code names. Write research questions that data can answer. Justify the method. List risks and assumptions. Give a timeline that fits the course. Keep the organization composite. Avoid promising results before measuring. Finally, confirm that the data you need exist and that you can reach them, since a proposal that depends on records nobody keeps will stall at the measurement stage.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
More BUS 799 and MBA sample papers
- BUS 799 Module 2: Capstone Literature Review
- BUS 799 Module 3: Capstone Methodology
- BUS 799 Module 4: Capstone Findings
- BUS 799 Module 5: Capstone Stakeholder Discussion
- BUS 799 Module 6: Capstone Recommendations
- BUS 799 Module 7: Capstone Financial Justification
- BUS 799 Module 8: Final Capstone Presentation
- BUS 510 Module 1: The Language of Business
- BUS 551 Module 8: International Corporate Finance
- BUS 560 Module 8: Ethical Leadership
- BUS 530 Module 5: Product and Brand Strategy
BUS 799 Module 1 questions, answered
What does BUS 799 Module 1 usually ask for?
The opening work in a graduate business capstone typically asks for a project proposal: the organization, the problem, its significance, objectives, scope, method and timeline. Aspen does not publish module deliverables, so your classroom's instructions govern.
How do I choose a capstone project at work?
Pick a problem that matters financially or operationally, that you can measure with data you can access, and that can be analyzed and planned within the course, with implementation continuing afterward if needed.
What is days sales outstanding?
Accounts receivable divided by average daily revenue, which shows how many days of sales are waiting to be collected.
Where can I find a free BUS 799 Module 1 sample paper?
The full BUS 799 Module 1 paper is above, an MBA capstone proposal to cut a contractor's 71 days of receivables toward a 50-day target.
What if company data prove incomplete in BUS 799 Module 1?
The proposal plans for it: a larger sample of invoices would be traced by hand, and a general contractor's review process would be inferred from rejection notices and emails if it declines to take part.