Output-based vs Time & Material: why we (still) mostly sell time.

TL;DR — On LinkedIn, fixed-price has become a moral stance and Time & Material a sin. The reality on the ground is simpler: most of our revenue is in Time & Material, and that's a deliberate choice. The contract model says nothing about how honest an engagement is. A T&M engagement can be perfectly aligned; a fixed-price one perfectly cynical. What matters is seniority, transparency and delivery culture. Here's how we run T&M without the pathology it's accused of, and when we switch to fixed-price.

Fixed-price has become a moral stance

Open LinkedIn on a Tuesday morning. A consultant explains that he has “stopped selling time,” that T&M “rewards slowness,” that billing by the day is a dishonest relic of the 90s. Fixed-price, by contrast, is commitment, courage, alignment.

It's a nice speech. It has one flaw: it confuses the billing model with the provider's ethics.

We mostly sell time. Time & Material. And after ten years running engineering teams for banks, scale-ups and industrial groups, we think it's often the right model, not an admission of weakness.

What T&M actually is

Time & Material bills a daily rate per engineer, multiplied by the days worked. Simple, legible, contractually light. It has been the standard for IT services firms for thirty years for a reason: it fits the reality of a living product.

A product in production changes its mind. The PM reorders the backlog on Monday, a major client forces a feature on Wednesday, a production incident blows up the sprint on Friday. In that world, freezing a scope over six weeks to bill it at a fixed price is billing a fiction. T&M follows the movement without renegotiating an amendment at every turn.

Most of our engagements live there: integrated teams, over time, inside product organizations where the scope shifts constantly. T&M isn't the “default for lack of better.” It's the model suited to that context.

The false promise of “we killed T&M”

The headline argument against T&M is the incentive: a firm paid by the day supposedly earns more by dragging things out. That's true in the abstract. It's equally true that fixed-price creates the exact opposite incentive, and no one mentions it.

On a fixed price, your margin grows if you deliver the bare minimum on the signed scope. The reflex becomes: under-staff the team, refuse anything not written in black and white, turn every request into a change request, ship a product that ticks the boxes without going a euro over. We've seen “outcome-aligned” fixed-price deals produce mediocre products, because the contractual outcome wasn't the right product, just the cheapest scope to reach.

Fixed-price isn't more honest than T&M. It simply moves the risk of cheating from one side of the table to the other.

The real problem is never the contract. It's alignment.

An engagement is honest when the provider's interests and the client's point in the same direction. That isn't decided by the type of contract, it's built in the way you work.

You can be fully aligned on T&M: a senior team that finishes early, says so, releases the unused days and offers the client to reinvest that budget elsewhere. You can be fully misaligned on fixed-price: a team protecting its margin by delivering on the cheap. The paper decides nothing. The culture does.

How we keep T&M honest at Abbeal

T&M has no built-in guardrails, that's true. So we put them in ourselves. That's the real work.

Seniority

All our engineers have real experience on their stack. A senior finishes fast and has no need to pad. The padding pathology mostly comes from junior teams that don't know any other way.

Transparency on the day you bill

The client sees what's done. Not cosmetic activity reporting, the real thing: what moved forward, what got stuck, what served no purpose. We'd rather say “this task isn't worth the cost” than bill it silently.

The reflex to release days

When the current scope is delivered, we don't stretch. We give the days back or reinvest them with the client's agreement. It's counter-intuitive for a firm billed by time. It's exactly what makes a client keep a team for three years rather than six months.

Saying stop

Anti-padding discipline is cultural. Over-engineering, unrequested refactoring, over-documentation: these are polite ways to inflate the invoice. We treat them as defects, not as “premium code.”

When we switch to fixed-price

Fixed-price isn't the enemy. It's a tool, and we use it when it's the right one.

It works when the scope is genuinely definable: an isolated, well-specified feature, a migration with clear edges, a deliverable you know from the start what it looks like. There, committing to a price and a date makes sense, and the client buys predictability.

It doesn't work when the scope is moving, when the client discovers the need while building, when the team is small and the risk poorly pooled. Forcing a fixed price on a fuzzy scope means either blowing up economically or delivering on the cheap. When in doubt, we stay on T&M and run it well.

That's why our portfolio leans toward T&M: most of our engagements are living products, not frozen deliverables.

The honest test

Next time someone explains that T&M is dishonest, ask one question: honest for whom, and measured how?

A good T&M provider saves you time and tells you when you're wasting it. A bad fixed-price provider hands you a shell that's contract-compliant. The billing model has never protected anyone. Seniority, transparency and the refusal to pad have.

We sell time. We own it. And we commit to the only thing that really matters: never billing you a day that doesn't serve you.

Do you run an IT services firm or a consultancy, or are you on the client side wondering which model for your next engagement? Let's talk for 30 minutes, no strings attached: https://calendly.com/d/csr7-3vm-vhw/meeting-abbeal