A client-owned app studio earns commissioned development fees, not the app’s future store sales. Those fees must pay for requirements, implementation, testing, review and release work within the retained studio calendar. This fictional four-specialist team has a paid nonbillable owner and still reports an operating deficit at its full-ramp service mix.
Quote a bounded accepted deliverable and reserve the real skills and review time it needs. A client’s hoped-for app revenue or an assumed maintenance renewal cannot fund the studio’s current payroll.
What revenue belongs to a bespoke app studio?
The case is a boutique studio in a moderate-cost US hybrid workspace, serving national business clients from January 2027 through December 2029. Native iOS, Android, cross-platform, product design and maintenance work divide one sold-hour pool. It excludes a speculative consumer-app catalogue, platform sales, recurring SaaS revenue and guaranteed store approval.
Four paid specialists provide 640 available hours per month. At 65% sold utilization the full-ramp mix sells 416 hours, leaving 224 delivery hours outside sold work. The compensated owner principal manages scope, contracts and cash without adding another developer. Quarter-time operations coverage is a prorated support budget.
How does the project mix use the paid team?
The table allocates the same 416 sold hours across platform development, design and maintenance. These are delivery-hour fee equivalents, not counts of apps shipped. Maintenance uses part of that pool; it does not create a second automatic subscription on top of the modeled work.
Actual skills still constrain the schedule. Spare design hours do not establish capacity for an Android release, and a review bottleneck can delay acceptance while other hours remain unused. Define supported devices/interfaces, test responsibilities, client approvals, handover and ownership in the scope before promising a fee and deadline.
| Delivery allocation | Sold hours | Fee/hour | Earned fees |
|---|---|---|---|
| iOS apps | 104 | $165.00 | $17,160.00 |
| Android apps | 104 | $160.00 | $16,640.00 |
| Cross-platform | 104 | $155.00 | $16,120.00 |
| Design | 41.6 | $145.00 | $6,032.00 |
| Maintenance | 62.4 | $135.00 | $8,424.00 |
Who pays for testing, revisions and release work?
External specialists and project cloud/device testing are direct purchases. Recurring business software, security, premises and the retained team sit in operating expenses. Client production hosting and platform/store responsibilities require an actual agreement and are not extra receipts in this scenario.
Write acceptance tests and a dated review/release plan alongside requirements. Record which revisions are included and how changed requirements affect price and delivery. A client delay or an unpriced release task can occupy the paid calendar without creating more earned fees. Do not assume the owner will absorb that delivery work outside the compensated management role.
Does the selected mix support the paid studio?
March earns $64,376.00. Direct costs of $3,862.56 and operating expenses of $61,827.11 produce EBITDA of -$1,313.67. The deficit occurs before depreciation, interest and income tax, with owner remuneration retained. First-year net income is -$84,300.39 and the later years are also negative.
The scenario assumes 30 collection days, no supplier delay and no inventory. Proposed uncommitted equity of $285,947.46 funds startup uses of $44,500.00 and liquidity; no debt is modeled. Minimum forecast cash is $43,963.35. That conditional cash reserve does not prove the delivery mix generates enough contribution.
What should the next client milestone prove?
Take a paid milestone through requirements, build, testing, sponsor review, release/handover and cash receipt. Record every specialist’s sold and unsold effort, the paid owner’s coordination and project purchases. Separate newly authorized maintenance from warranty or finishing work already owed under the original scope.
Use the actual collected contribution to revise the fee, scope, mix or retained-cost plan. If acceptance depends on unresolved client interfaces, data or platform responsibilities, resolve those dependencies before expanding the studio. Do not count client app sales, speculative SaaS income or a renewed support contract that has not been agreed.
Make the next decision with your own evidence
Reconcile a collected client milestone to all requirements, testing, review, release and purchased effort, then revise the fee or retained-cost plan before accepting a larger studio commitment.
Explore published business plan examples ↗PocketHarbor Studio is a fictional prelaunch scenario prepared with AI assistance. Inputs are illustrative; forecast results come from the matching saved financial model. Funding is proposed. The diagrams explain the case and do not depict actual premises, established demand or promised earnings. Replace the assumptions with evidence before committing.
Read our methodology