Why We Don't Bill by the Hour

Traditional consulting has a dirty secret: billing by the hour incentivises the wrong things. The longer a project takes, the more money the consultancy makes. Efficiency is literally punished.

This was always a bad model. AI makes it absurd.

The Hourly Billing Problem

When an AI-augmented engineer can ship in two weeks what a traditional team takes three months to build, billing hourly creates a perverse situation. Either you inflate hours to justify the cost — which is dishonest — or you bill accurately and the client wonders why they're paying consultancy rates for "only" two weeks of work.

Both outcomes are bad. The first erodes trust. The second undervalues the result.

The client doesn't care how many hours something took. They care that it works, that it shipped on time, and that it solves their problem. Hours are a proxy metric for effort, and effort is a proxy metric for value. Why not just measure value directly?

How Outcome-Based Pricing Works

Our model is straightforward: fixed scope, fixed price, aligned incentives.

At the start of every engagement, we define the deliverable in concrete terms. Not "build an AI system" but "deploy a document processing pipeline that handles 500 documents per day with 95% extraction accuracy, integrated with your existing data warehouse."

We agree on a price for that outcome. If we deliver it in two weeks, great — we've earned our fee efficiently. If it takes longer, that's our problem, not yours. The price doesn't change.

This only works because we scope aggressively. We'd rather deliver a focused, excellent system than a sprawling mediocre one. Clear boundaries protect both sides.

Working Software Every Two Weeks

We don't disappear for months and emerge with a big reveal. Every two weeks, we deliver working software that the client can see, touch, and test. This serves two purposes.

It builds trust. You can see progress in real time, not in status reports. If something isn't right, we catch it in week two, not month three.

It reduces risk. If the engagement needs to change direction — and they sometimes do — we haven't burned months heading the wrong way. The working increments are yours to keep regardless.

"What If It Takes Longer?"

This is the most common question we get. The answer is simple: that's our risk.

We've been doing this long enough to know what's achievable in a given timeframe. Our scoping process is thorough precisely because our margin depends on getting it right. If we underestimate, we absorb the cost. The client's price is the client's price.

This model self-selects for competence. You can only offer fixed-price outcomes if you're genuinely good at estimating and executing. Consultancies that pad timelines or under-deliver can't sustain it.

You Own the Code

Everything we build belongs to the client from day one. Full source code, documentation, deployment configurations, architecture decision records. No lock-in. No proprietary frameworks that only we can maintain.

When we leave, your team should be able to maintain, extend, and modify everything we've built. If they can't, we haven't done our job.

Why Clients Prefer This

The feedback we hear most often is that outcome-based pricing removes the anxiety of watching a meter run. Clients ask questions freely without worrying about billable hours. They request changes without mental arithmetic. The relationship becomes collaborative rather than transactional.

We like it too. It means we're rewarded for being efficient, creative, and effective — not for being slow.

The Simple Principle

Charge for what you deliver, not for how long it takes. When your tools make you faster, your clients should benefit from that speed. And so should you.