We've shipped 300+ products in 21 countries. Here's what happens when you refuse to bill hourly.

The moment we decided to stop billing hours

Back in 2023, we were running a pretty standard agency model. Time-and-materials contracts, monthly retainers, scopes that drifted. We were good at delivery, but the commercial structure kept creating the wrong dynamics.

Clients watched burn rate instead of progress. We made more money when projects took longer. And when we started integrating AI tooling into our workflows, Copilot, then more sophisticated agentic stacks, the dishonesty of the model became impossible to ignore.

AI was shaving 40–50% off implementation time on certain modules. We were either going to quietly pocket that as margin while billing historical rates, or we were going to restructure the whole thing.

We restructured.

What we built instead

The model we landed on: fixed-price, outcome-defined delivery sprints. No hourly fallback. No "flexibility" clause that quietly converts to T&M when the scope gets fuzzy.

Every engagement starts with a scope governance phase, a written, line-item scope agreement before a single line of code is written. What's in, what's out, what triggers a formal change order. That document is the contract's backbone. It's not glamorous work, but it's what makes the fixed price defensible.

Then delivery happens in a governed 38-day sprint, with AI tooling embedded across the stack, code generation, documentation, QA scaffolding, under human review gates at each milestone.

The result: 38-day median delivery on what traditional teams were completing in 90–120 days.

What nearly broke it

Honest answer: clients.

Not because they were difficult, but because they were reasonably skeptical. "Fixed-price" has a history of meaning "we'll deliver something adjacent to what you wanted and call it done." We heard that objection constantly in the first six months.

What changed it was case studies. Documented outcomes, not testimonials. Specific scope, specific timeline, specific result. Once we had six of those, the skepticism shifted from "can you actually do this?" to "walk me through your scope process."

The other near-breaking point was internal. The pressure to add hourly "flexibility" for edge-case clients is real. Every sales conversation where a client pushes back on a fixed price feels like a closed door. We lost deals to hourly competitors who promised "transparency." Some of those deals came back to us six months later, over budget and under-delivered. That pattern is what made the model durable. We saw what the alternative actually looked like.

Why 2026 is the inflection point

GitHub's data now shows 46% of code in production repositories is AI-assisted or AI-generated. McKinsey puts AI tooling to reduce code generation time by 35–45%. Gartner projects 80% of large engineering orgs will operate as smaller, AI-augmented teams by 2030.

The orgs already operating this way are shipping 3–5× faster at comparable cost.

Against that backdrop, billing by the hour is not just inefficient, it's structurally dishonest. A vendor running AI tools and billing hourly is either hiding efficiency gains in their margin or billing the client for work that took a fraction of historical time. Neither is a partnership.

The market is figuring this out. We built ahead of it, and the discipline required — upstream scope governance, change-order systems, fixed-price financial modeling that accounts for AI leverage — is now a genuine competitive moat.

What 300+ products across 21 countries taught us

The bottleneck is no longer code. It's decision-making. With AI handling implementation velocity, the constraint moves upstream, to scope clarity, stakeholder alignment, and what you're actually building. Teams that haven't adapted their process to this new bottleneck are shipping faster in the wrong direction.

Governance is the differentiator, not tooling. Everyone has access to the same AI models. The teams winning are the ones with disciplined workflows around them, prompt governance, human-in-the-loop review, and QA that's designed for AI-generated defect patterns. Ungoverned agentic development produces technical debt at scale.

Clients don't want hours. They want outcomes. This sounds obvious until you're in the room and a procurement team asks for a "transparent hourly breakdown." What they actually want is budget certainty and delivery confidence. Fixed-price, well-scoped, with a documented change-order process, gives them both better than any timesheet ever did.

The next 12 months

There will be a significant shakeout in development agency pricing models. Vendors still selling hours while running AI tools won't survive the transparency. Clients are getting smarter about asking: "If AI cuts your build time by 40%, why is your quote the same as 2023?"

The honest answer to that question is a fixed-price model with visible scope governance. Everything else is accounting fiction.

If you're building a product and evaluating development partners right now, the pricing conversation is the right place to start. Ask any agency: "What happens to your margin if the project takes twice as long?" If the answer is "nothing," you're on the wrong model.

We're at ailoitte.com/ai-velocity-pods if you want to see how the model actually works. And happy to answer questions in the comments, especially from anyone who's tried to make fixed-price work and hit the scope governance wall. That's the real conversation.

#buildinpublic #pricing #AI #productdevelopment #agencygrowth