Hourly billing pays the builder more when the work takes longer — which means the client funds every inefficiency, meeting and false start. Fixed price flips it: the studio profits by being fast and scoping honestly, and the client knows the number and the date before a line of code exists. It only works with tight scoping and the discipline to eat your own misjudgments. We do both, on purpose.
Follow the incentives
Every pricing model pays for something. Ask what, and most of the software industry's dysfunction explains itself.
Hourly pays for time spent. Not outcomes — time. Under hourly, a slow week bills the same as a brilliant one. The nine-person status meeting is revenue. Rework is revenue. The vague spec that guarantees rework? Also revenue. Nobody at an hourly shop wakes up scheming to be slow — they don't have to. The model quietly stops rewarding speed, and organizations drift toward whatever their model rewards.
Fixed price pays for the outcome. The number is agreed, so every hour saved belongs to the builder and every hour wasted comes out of the builder's margin. Suddenly efficiency is not a virtue, it's the business model. That's the entire trick — and it's why our AI-accelerated stack and fixed pricing belong together: we invested in being fast because we keep the difference, and you get the date.
"But hourly is fairer" — is it?
The argument for hourly is that you only pay for what you get. In practice, you pay for what happened — including everything that shouldn't have. An estimate isn't a price; it's an opening bid with no penalty for being wrong. The risk of every unknown lands on you, and the party controlling how long things take is the one paid by the hour. Calling that "fair" requires not thinking about it too hard.
Fixed price moves the estimation risk to the people best placed to price it: the ones who've built the thing before. If we misjudge a build, we eat it — that's not a bug in the model, it's the feature that keeps our scoping honest. A shop that won't carry that risk is telling you something about their confidence in their own estimates.
How we make fixed price actually work
Fixed price has a bad reputation from shops that do it lazily — quote low, win the deal, then nickel-and-dime through change orders. The model needs discipline in four places:
- Productized scopes. Our packages exist because we've built these systems repeatedly — store, internal tool, ops system. Known shapes price honestly. Novel shapes get a discovery conversation, or a $3,500 sprint that turns unknown into known.
- Scope in writing, exclusions included. The one-pager says what's in and what's out. Most fixed-price disasters trace back to a scope that listed features and stayed silent on boundaries.
- 50% to start, balance at ship. Skin in the game on both sides, and our incentive stays pinned to "shipped", not "in progress".
- Honest change orders. New ideas mid-build are welcome — as new scope with a new number, decided by you. Small nudges get absorbed; real additions get priced in daylight. What never happens: silent hours appearing on an invoice.
What it feels like on your side
- You know the total cost before you commit — budgeting is arithmetic, not faith
- You know the ship date, and the studio is financially motivated to hit it
- Adding scope is a decision you make with a price attached, not a surprise you discover on an invoice
- Speed stops being suspicious. Under hourly, fast work reads as corner-cutting. Under fixed price, it's just what the incentives produce
Where hourly is honestly the right model
Fairness cuts both ways, so: hourly (or retainer) is legitimately better for open-ended R&D where nobody can define "done", for embedded staff-augmentation inside your team, and for ongoing maintenance with an unpredictable stream of small asks. The dividing line is definability. If "done" can be written down, it can be priced. Our builds can be written down — so they're priced.
The one-question test
Whoever you're evaluating, ask: "What happens to your profit if this takes twice as long as you think?" If the answer is "we bill more", the risk is yours. If the answer is "we lose money", the incentives are pointed at your outcome. There are only two answers, and every quote you'll ever receive contains one of them — usually hidden in the fine print.