App Development Pricing Models: Six Structures and What Each Costs You

Software pricing is usually discussed as a binary between fixed price and hourly billing, and there are six structures in common use. Each one allocates risk differently, and the allocation is what you are actually choosing. The rate is a consequence of it.

Knowing all six matters because the right structure frequently differs by phase. The model that suits a first build is rarely the model that suits the year afterwards.

1. Fixed scope, fixed price

How it works: a defined deliverable at an agreed price. Changes are priced events.

Who carries risk: the agency carries estimation risk on the agreed scope. You carry the risk of having specified the wrong thing.

Rate effect: 10 to 25 percent above the equivalent hourly total, which is the price of transferring uncertainty.

Suits: first versions, rebuilds, migrations, and defined integrations. Also anyone who needs a number they can commit to a board, an investor, or a launch date.

Requires: real specification work up front, which is why firms offering this well tend to sell discovery separately. Bolder Apps prices project work fixed-scope rather than hourly with projects starting around $30,000 and sells paid discovery as a standalone engagement, and the two go together: a fixed price is only safe for either side once the scope has genuinely been analysed.

Watch for: a proposal with no exclusions section. Under this model exclusions are where change-order revenue lives, and their absence means the scope is not actually fixed.

2. Time and materials, uncapped

How it works: hourly or daily billing against actual work.

Who carries risk: you, entirely.

Rate effect: lowest headline rate, no risk premium.

Suits: genuine research and development where the shape of the work cannot be known, post-launch iteration where priorities legitimately shift weekly, and integration with an undocumented legacy system where any fixed price would be padded or renegotiated.

Requires: technical leadership on your side who can assess velocity and challenge decisions. Without it, you are paying for hours you cannot evaluate, which is the structural reason non-technical founders often fare badly under this model despite the lower rate.

3. Capped time and materials

How it works: hourly billing with a not-to-exceed ceiling and a mandatory written review before the ceiling is reached.

Who carries risk: shared. You pay for actual hours and cannot be surprised beyond the cap without a conversation.

Rate effect: close to uncapped, sometimes a small premium.

Suits: the very common middle case where the work is mostly definable but contains one genuinely uncertain area. It is the most underused structure in this list and frequently the most sensible.

Watch for: a cap with no review trigger, which is a cap that gets breached and then explained. The review before the ceiling is the mechanism, not the number.

4. Milestone-based fixed price

How it works: the project is divided into phases, each priced and each with acceptance criteria. Later phases are priced when the earlier ones complete.

Who carries risk: shared and sequenced. Each phase is a fixed price, and the plan can change between phases.

Suits: larger projects, anything where the second half genuinely depends on what the first half reveals, and clients who want the option to stop.

Why it is good for the client: payment stays coupled to verifiable progress, so a stalled project stops consuming money. It also preserves the option to change partners between phases, which is real leverage.

Requires: written acceptance criteria per milestone. Without them, milestone completion is a negotiation.

5. Dedicated team or retainer

How it works: a monthly fee for a defined team allocation, typically with a minimum commitment of three to six months.

Who carries risk: you carry outcome risk; the agency carries staffing risk.

Rate effect: usually a modest discount against hourly, in exchange for the commitment.

Suits: ongoing development after launch, staff augmentation where you have technical leadership, and long-running products where continuity of the same people matters more than a defined deliverable.

Watch for: allocation percentage. A dedicated team that is 50 percent allocated across three clients is not dedicated, and the term is used loosely. Ask for the percentage in writing.

6. Deferred fee, equity, or revenue share

How it works: some or all of the fee is deferred, exchanged for equity, or paid from revenue.

Who carries risk: shared, and priced accordingly. Expect the total cost to be substantially higher than a cash engagement, because the agency is absorbing your commercial risk.

Suits: a narrow set of cases, and it is worth being clear-eyed. Agencies that do this at all do it selectively, for products where they have conviction, and the equity or revenue percentage reflects real risk rather than goodwill.

Watch for: misaligned incentives on scope. An agency with equity has a reason to want the product to succeed and also a reason to keep cash costs low, which can mean a thinner build than you need. Also consider what a future investor will make of a development agency on your cap table.

The comparison that resolves most decisions: convert every bid to an expected total before comparing. An hourly bid's expected total is its working estimate plus a realistic overrun allowance of 20 to 40 percent plus the value of your own management time. Against that, a fixed price is usually much closer than the headline numbers suggest.

The clauses that matter more than the model

Whichever structure you choose, six terms determine whether it protects you, and they are worth more attention than the rate.

An exclusions list. Specific, written, and present. Under a fixed price it defines the boundary. Under hourly billing it tells you what will surface as additional work.

Acceptance criteria per deliverable. What finished means, written before the work rather than negotiated after it. Without these, a final holdback is unenforceable and milestone completion is an argument.

A change-request process with pricing. Documented rather than informal. Informal understandings become invoices.

IP assignment on payment, covering code, design assets, and documentation, plus repository and infrastructure under your own accounts from day one rather than delivered at the end.

Time reporting granularity, under any hourly or retainer model. By person and by task, detailed enough to audit. A monthly total with no breakdown is not reporting.

A defined exit. Notice period, handover contents, and what happens to work in progress. This is the clause nobody reads and the one that decides how expensive a bad relationship becomes.

What is negotiable and what is not

Useful to know before you spend goodwill in the wrong place.

Generally negotiable: payment schedule and deposit size, the size of a final holdback, the number of revision rounds included, notice periods, and whether a small paid engagement can precede the main one. Also frequently negotiable: whether the firm will quote the same scope under two different models so you can see both numbers.

Generally not negotiable, and pushing hard tends to backfire: rate, since a firm that discounts steeply usually reallocates its stronger people elsewhere. Scope at the same price, which produces a thinner build rather than better value. And quality assurance as a percentage, which is the one place a discount is genuinely dangerous because the cost transfers to your users rather than disappearing.

The most productive thing to negotiate is not price at all. It is sequencing: a small paid discovery or audit before the main commitment. Bolder Apps sells discovery and code audits as standalone engagements alongside fixed-scope project work, and asking any firm for a small paid first step gives you a real read on how they think for a few thousand dollars rather than on the strength of a proposal.

The sequence most experienced buyers use

Rather than choosing one model for everything, match the model to the phase.

Discovery: small fixed price. A bounded engagement producing a specification, architecture plan, and estimate you own. Also a cheap test of how the firm thinks.

Build: fixed scope or milestone fixed price, using the specification discovery produced. The estimate is now grounded in analysis rather than a sales conversation, which is what makes a fixed price safe for both sides.

Post-launch: time and materials or a retainer. Fixing scope during iteration is actively counterproductive, because the entire point of the phase is responding to what you learn.

Forcing a fixed price onto genuinely unknowable work does not remove the risk. It converts it into a padded estimate, a defensive scope, or a change-order dispute.

Payment structure, which matters as much as the model

Two engagements at the same total can distribute risk very differently depending on when money moves.

Milestone payments tied to verifiable deliverables are the structure to prefer, because progress and payment stay coupled. Time-based payments release money monthly regardless of progress, which is simpler to administer and weaker for you.

A deposit of 20 to 30 percent at kickoff is normal. Above roughly 30 percent, you are funding the agency's working capital before any deliverable exists, and 50 percent upfront on a six-figure engagement warrants a direct question about why.

A final holdback of 10 to 20 percent against written acceptance criteria is the single most useful clause available to a client, and it only functions if the criteria exist. Define what finished means in the contract rather than in the final week.

Sources

• US General Services Administration definitions of contract types, gsa.gov
• Federal Acquisition Regulation Part 16, contract types, acquisition.gov
• Project Management Institute, PMBOK Guide, on procurement and change control
• World Intellectual Property Organization guidance on software IP assignment, wipo.int