Comparison
Product Studio vs Dev Agency: Fixed Scope vs Billable Hours
Both build software. Only one structurally prevents overruns. The pricing model is the difference.
The pricing model is the difference
Hourly billing rewards time spent. Fixed price rewards efficient execution. These are not equivalent incentive structures, and they produce different outputs.
An agency on hourly is rational to extend the engagement. A studio on fixed price is rational to ship. The same engineers under different contracts behave differently because the contract structure tells them what to optimize for.
The cost of a wrong build decision is significant. A Clarity Sprint prevents that cost. Hourly billing makes prevention nobody's job; fixed-price makes it everyone's.
Side by side
Criterion
Pricing
Dev Agency
Hourly, time-and-materials, or per-sprint
Product Studio
Fixed price tied to locked scope
Criterion
Scope handling
Dev Agency
Change orders adjust price and timeline
Product Studio
Scope changes require a separate scope exercise
Criterion
Decision-making
Dev Agency
Executes against your direction
Product Studio
Surfaces and locks decisions in a Clarity Sprint
Criterion
Team continuity
Dev Agency
Resourced from a pool; team may rotate
Product Studio
Same team start to finish across stages
Criterion
IP ownership
Dev Agency
Negotiated per contract
Product Studio
You own everything from day one
Criterion
Project management overhead
Dev Agency
PM layer typically billed
Product Studio
No PM tax; senior team manages directly
Criterion
Velocity
Dev Agency
Predictable hours, variable output
Product Studio
Predictable output, fixed timeline
Criterion
What is on the SOW
Dev Agency
Hours, rate cards, time-bounded phases
Product Studio
Locked scope, deliverables, fixed price
What scope creep looks like in each model
Agency model
Scope creep becomes invoice creep.
Founder requests an addition mid-build. Agency issues a change order. Timeline shifts, price climbs. Three change orders later, the engagement is 40 percent over budget. Nobody intervened to question whether the additions should have happened, because nobody was incentivised to.
Studio model
Scope creep stops at the door.
Founder requests an addition mid-build. Studio responds: that is a scope change. We do a one-week scope exercise to decide whether to include it, defer it, or reject it. If included, we re-quote. If deferred, we document. The conversation forces the decision instead of absorbing it.
A dev agency makes sense if
- You have a multi-year roadmap with stable scope
- Your procurement requires hourly contracts and time-and-materials
- You have an internal product team and need pure execution capacity
A product studio makes sense if
- You want a fixed-scope outcome with predictable spend
- You want decisions made with you, not executed around you
- Your budget is allergic to overruns and surprise invoices
If you are choosing between a studio and an agency
The Clarity Sprint is a fixed-price engagement that locks scope before any build. If a studio is not the right fit, you walk away with a decision document you can hand to an agency. Either way, you are no longer paying for scope drift.