Outcome-Based Everything: Why We Tie Our Success to Yours_

Outcome-Based Everything: Why We Tie Our Success to Yours

I'll start with a confession. For the first year of Moonxi's consulting practice, we billed by the hour. Time and materials. The industry standard. The safe default.

And I hated every invoice we sent.

Not because the work wasn't good — it was. Not because the rates were wrong — they were market. I hated it because hourly billing creates a structural misalignment between what the client wants and what the consultancy is incentivized to do. The client wants the project finished. The consultancy benefits when it takes longer. Nobody says this out loud. Everyone knows it's true.

So we changed. Not incrementally — a small discount here, a blended rate there — but fundamentally. We moved to outcome-based pricing across everything AI Gens does. Consulting. Investment. Incubation. Every engagement structured so that our success is mathematically tied to yours.

It nearly killed the business. It was the best decision we ever made.

The Misalignment Nobody Talks About

Here's the dirty secret of professional services: the hourly billing model was designed for law firms in the 1950s. It made sense when the work was advisory — you're paying for expertise applied per unit of time. But software engineering isn't advisory work. It's building. And when you're building, what matters isn't how many hours you spent. It's what you shipped.

The T&M (time and materials) model creates three specific pathologies:

Scope creep is profitable. Under hourly billing, every requirement change, every "small addition," every "while you're in there, could you also..." is revenue. The incentive to push back on scope creep is zero. The incentive to encourage it is significant.

Speed is penalized. If your senior engineer solves a problem in two hours that a junior would take twenty, hourly billing says the senior's contribution is worth less. The client pays for ten percent of the effort. The consultancy earns ten percent of the revenue. Everyone loses except the mediocre engineer who takes the long way around.

Outcomes are invisible. When the invoice says "324 hours of engineering services," nobody asks whether those hours produced anything worth having. The metric is effort, not result. You could bill 324 hours of beautifully crafted code that never ships, and the invoice looks identical to 324 hours that transformed the business.

EPAM, one of the largest IT services companies in the world, has been publicly shifting from T&M to outcome-based models. They've seen what everyone in the industry sees: clients are tired of paying for activity when they want to pay for results. The old model is dying. The question is what replaces it.

What Outcome-Based Looks Like at AI Gens

Across our three pillars — consulting, investment, and incubation — outcome-based alignment takes different shapes. But the principle is the same: we eat what we kill.

Consulting: Tied to Delivery Metrics

For Moonxi's consulting engagements, we define success metrics before the first line of code is written. Not vague aspirations. Measurable outcomes.

Deployment frequency. Time to production. System reliability. Cost per transaction. Developer productivity. Margin improvement. These are the numbers that matter to the client's business, and these are the numbers our fees are tied to.

The structure varies by engagement, but the pattern is consistent: a base fee that covers our costs, plus a performance component tied to hitting — and exceeding — specific targets. If we improve deployment frequency from weekly to daily, we earn more. If we reduce infrastructure costs by 30%, we share in the savings. If we don't move the needle, we absorb the loss.

This changes everything about how we work. We don't staff projects to maximize billable hours. We staff them to maximize impact per hour. We don't extend timelines to extend revenue. We compress timelines because faster delivery means faster results means we get paid sooner.

Investment: Equity Alignment

For our venture investments, outcome alignment is structural. We take equity. We don't charge management fees on our direct ventures. Our returns come from the same place our founders' returns come from: the long-term value of the company.

This means our investment team isn't incentivized to deploy capital quickly (to start earning fees) or to push for premature exits (to generate carry). We're incentivized to build real value over time. If the company compounds at 30% annually for a decade, everyone wins. If it flames out in year two, everyone loses.

The alignment is simple. The patience it requires is not.

Incubation: Shared Risk, Shared Upside

For ventures we incubate internally — Apollo, HOST360, Mustard — the outcome alignment is the most direct. We invest our own capital, our own team, our own time. There's no client writing checks. If the product works, we own the upside. If it doesn't, we eat the loss.

This is the purest form of outcome-based building. Nobody's billing hours to an incubated venture. The venture either creates value or it doesn't. The team either ships something users want or they don't. There's no invoice to hide behind.

The Hard Truth About Defining Outcomes

Here's where I have to be honest about something most advocates of outcome-based pricing gloss over: defining outcomes is genuinely, brutally difficult.

McKinsey published research showing that when clients were given the choice between activity-based and outcome-based pricing, 90% chose activity-based. Not because they philosophically preferred paying for hours. Because defining success metrics — the specific, measurable outcomes that both parties agree on before work begins — requires a level of clarity that most organizations don't have when they start an engagement.

Think about it. To do outcome-based pricing, you need to:

1. Know what success looks like. This sounds obvious. It's not. Most companies know they need "better software" or "faster delivery" or "AI capabilities." Translating that into measurable metrics — specific numbers, specific timelines, specific baselines — requires deep understanding of the current state.
2. Agree on attribution. If deployment frequency improves from weekly to daily, was that because of the consultancy's work? Or because the internal team finally fixed their CI pipeline? Or because a new engineering manager instituted better practices? Attribution in complex systems is genuinely hard.
3. Accept the measurement overhead. You can't manage what you don't measure. Outcome-based pricing requires instrumentation, baselines, tracking, and reporting. That's real work. Some clients look at the measurement infrastructure and decide hourly billing is simpler.
4. Navigate the asymmetry. The consultancy has more information about what's achievable than the client. This creates an adverse selection risk: consultancies might cherry-pick engagements where they know outcomes are easy to hit, and avoid the hard problems where outcome-based pricing would actually be most valuable.

Forrester has projected that consultancies will increasingly put fees at risk — tying revenue to results rather than activity. But they've also noted that the transition is slow precisely because of these measurement challenges. The model everyone wants is the model nobody knows how to implement cleanly.

How AI Gens Navigates the Tension

So if defining outcomes is so hard, how do we actually do it?

The answer is unglamorous: we spend more time on engagement design than most consultancies spend on proposals. Before we write a single line of code — before we even agree on a statement of work — we invest in understanding the client's current state deeply enough to define meaningful outcomes.

This means:

Discovery before commitment. We run a paid discovery phase — typically two to four weeks — where we instrument, measure, and establish baselines. This isn't a sales exercise. It's engineering. We deploy monitoring. We measure deployment frequency, lead time, error rates, infrastructure costs. We establish the numbers as they exist today, so we have a foundation for defining what "better" means.

Outcomes, not outputs. We explicitly avoid output-based metrics. "Deliver 50 microservices" is an output. "Reduce time-to-market from 12 weeks to 3 weeks" is an outcome. Outputs can be gamed. Outcomes require actual value creation.

Shared dashboards. Every engagement has a live dashboard that both sides can see. No quarterly reports. No "trust us, the numbers look good." Real-time visibility into the metrics that determine our compensation. If the numbers are trending down, we know it before the client tells us. If they're trending up, the client sees it before we invoice.

Graduated risk. We don't go full outcome-based on day one of a new client relationship. We start with a blended model — a larger base fee and a smaller performance component — and shift the ratio as trust builds and measurement matures. By month six, the majority of our revenue should be tied to outcomes. If it's not, either the engagement isn't working or we defined the wrong outcomes.

Outcome Pricing as Trust Signal

Here's something I didn't fully appreciate until we'd been doing this for two years: outcome-based pricing isn't just a business model. It's a trust signal.

When a consultancy tells you, "We'll tie our fees to your results," they're making a statement about confidence. They're saying: we believe we can actually move these numbers. We believe our work creates measurable value. We believe it enough to put our revenue at risk.

The inverse is also true. A consultancy that insists on hourly billing is saying, implicitly: we're not confident enough in our impact to let you measure it. We want to be paid for showing up, not for what we produce.

I'm not suggesting that every hourly-billing consultancy is incompetent. Many are excellent. But the pricing model communicates something about self-belief that no pitch deck can replicate. When we walk into a room and say, "We'll put 40% of our fees at risk tied to these specific metrics," clients hear something beyond the commercial terms. They hear conviction.

And conviction is rare enough in professional services that it creates its own competitive advantage.

The EPAM Precedent

It's worth noting that we're not alone in this shift. EPAM Systems — a $6 billion IT services company — has been publicly transitioning from T&M to outcome-based pricing. Their reasoning mirrors ours: in a world where AI is automating significant portions of software delivery, billing by the hour becomes nonsensical. Why would a client pay for 1,000 hours of engineering when an AI-augmented team can deliver the same outcome in 200?

EPAM's approach has been to create "outcome-based pods" — teams configured around specific business results rather than staffed to fill a timesheet. The pod's composition (humans, AI agents, automation tools) is fluid. What's fixed is the outcome the pod is responsible for delivering.

This is exactly the model Moonxi has adopted, though at a smaller scale. Our delivery teams are organized around outcomes, not headcount. If an AI agent can handle 60% of the deployment automation, we don't replace the agent with a human to keep billing hours. We let the agent work and tie our fees to the deployment metrics that improve as a result.

The Future: Agents Make Outcome-Based Natural

Here's where this gets genuinely exciting. The rise of AI agents doesn't just enable outcome-based pricing — it makes it the only rational model.

Consider: an AI agent completes a task. You can measure exactly what it did. How many code changes it made. How many tests it wrote. How much infrastructure cost it reduced. How many minutes of human time it saved. The output is quantified by definition.

Now try billing hourly for an agent. What's the "hour"? The 47 seconds it took to process the request? The three minutes it took to execute the workflow? The concept of time-based billing doesn't even apply to non-human workers. You can't bill for an agent's "time." You can only bill for its results.

This is why I believe outcome-based pricing will become the default for technology services within five years. Not because consultancies will choose it for philosophical reasons. Because the technology will make activity-based pricing impossible to justify.

When your client can see that an AI agent resolved 200 production incidents in a month — with timestamps, root cause analyses, and resolution verification — billing them for "engineering hours" looks absurd. You bill for the outcome: 99.9% uptime. 73% reduction in mean time to resolution. Zero data loss incidents.

The agent doesn't have hours. It has results. And results are outcomes.

The Uncomfortable Conclusion

Outcome-based pricing forces an uncomfortable question that most service businesses would rather not answer: do you actually create value?

If the answer is yes, outcome-based pricing should be welcome. It's a chance to capture more revenue than hourly billing would generate, because the value you create exceeds the cost of the hours you spend. If you can reduce a client's infrastructure costs by $2 million per year and you're billing $500,000 in fees, outcome-based pricing lets you capture a percentage of that $2 million — potentially more than you'd earn billing hours.

If the answer is no — if the value you create is ambiguous, unmeasurable, or indistinguishable from what the client could achieve without you — then outcome-based pricing is terrifying. Because it exposes the gap between what you charge and what you deliver.

At AI Gens, we've made our choice. Every pillar of our business is structured so that our success is a function of your success. We consult to outcomes, invest for compounding, and incubate with shared risk.

It's harder than billing hours. It requires more upfront work, more measurement infrastructure, more honest conversations about what success looks like. Some months, it pays less than T&M would have.

But it aligns our incentives with reality. And in a world where AI is making the cost of activity approach zero, the only sustainable business model is one that charges for what matters.

Results. Outcomes. Value created.

Everything else is just time passing.