Services-as-software

We don't sell seats. We seat a bench.

There are two familiar ways to buy help, and they share a ceiling. You can license a tool and hope the people you already have find the time to learn it well enough to change how they work. Or you can retain a firm and pay by the hour for exactly as long as you keep paying. In both cases the value arrives while the invoice is open and leaves when it closes, and nothing you bought last quarter makes this quarter any better.

We built a third shape. We take the standing workforce that runs our own work — master practitioners, each held to the standard the best human in that discipline would hold themselves to — and we seat a bench of them inside your organization, on the functions where you are thin. They do the work rather than helping somebody else do it. They coordinate across your desks the way a real firm's departments coordinate. And because the bench is standing rather than assembled for a job, the practitioners who learn your buy-box, your lenders, your counterparties and your house style this month are the same ones working for you next month, sharper for having done it.

What services-as-software means when it is real

Start with why the two familiar shapes both stall. A licensed tool asks your people to change how they work before it pays anything back, so its value is gated behind an adoption step that most organizations never fully complete. An hourly firm has no adoption problem at all, but it has a worse one: the arrangement is designed so that nothing accumulates. Every engagement starts near zero, re-learns your context, bills for the re-learning, and hands back a deliverable that carries none of that context forward. Neither shape is dishonest. Both are simply capped by their own structure.

The third shape removes the adoption step and keeps the accumulation. We seat practitioners rather than software or hours, and what they hand over is finished work to a professional standard, not a capability you still have to wield yourself. The leverage is software-shaped — always on, scales without a hiring cycle, marginal cost that bends the right way — and the delivery is service-shaped. The client buys an outcome. The outcome improves on its own, because the bench that produced it is still seated when the next one comes around.

That last clause is the whole thesis, so it is worth being precise about it. A bolt-on lane lands inside a customer's operation and compounds there. In the first month the bench is learning the shape of your work: which counterparties are careful and which are not, which lender wants the file assembled which way, which exception you will always take and which you never will. By the third month that knowledge is not written in a handbook somewhere, it is in how the work comes back. None of that transfers to a competitor and none of it evaporates when a person leaves, which is a different durability from either a subscription or a retainer.

It is also why a lane does not churn the way a seat churns. A seat churns because nobody adopted it, and the renewal conversation is a referendum on a behaviour change that never happened. A lane has no adoption step to fail — the work is being done either way — so the renewal conversation is about output that is already visible. And a lane expands the way a good team expands: you seat one, it earns the next, and the second is easier to justify than the first was, because the first is in front of you every morning. That is the difference between a tool business and a workforce business, and it is where we point our sharpest energy.

We run the other half too. We build and ship software, and what we have already put in market is catalogued on the products page rather than described again here. The two halves feed each other — a product is a practitioner discipline crystallised into something other people's work can run through, and a bolt-on lane is those same disciplines meeting an operation that is not ours. But if the question is which half carries the enterprise value, the honest answer is this one, and we would rather say it plainly than have you work it out from the org chart.

One thing does not change when a bench seats, and it is the thing worth asking about first rather than last. A human principal still owns every outcome, and where a discipline is licensed — law, appraisal, title, accounting — a licensed human of record still signs. The accountability model is set out on the roster page and seating a bench does not move it by an inch. What moves is the volume of work that no longer has to pass through the one person who was becoming the constraint.

Configure the bench

Pick the shape of your organization and the function you would bolt onto, and see exactly which practitioners seat, what they own, what you keep, and what the first thirty days actually looks like.

1 — Your organization

2 — The function you'd bolt onto

The bench that seats

  • Robertdrafts and reviews every agreement before it reaches a signature, and stands up the entities underneath them
  • Emilyholds the front door so a legal request never arrives, waits, and quietly ages out of relevance

They own

  • The drafting and the second read of every routine agreement the business generates
  • Entity formation, plus the operating agreement that should have arrived with it
  • One current record of what was agreed, with whom, and on which version
  • The chase on outstanding signatures, so following up stops being a thing somebody has to remember

You own

  • Counsel of record, and every term you are unwilling to accept
  • Which matters escalate to your attorney and which stay routine
  • The final decision on every signature, without exception

First 30 days

  • The first week is a read: the bench works through the agreements already in force and names the templates you are actually using, including the ones nobody knew were still in circulation
  • From there it runs live on new work with a human reviewing every draft before it leaves the building
  • By the end of thirty days you have a standing contract set, a written escalation rule, and a signature queue that is visibly current rather than assumed to be

Deliberately not shown: hours saved, return on investment, headcount replaced. We hold no audited figure for any of them, and a made-up one would be worth less than nothing. Talk to a human about numbers.

Why a lane compounds and a seat does not

The mechanic is specificity, and specificity is the thing that never survives an hourly engagement. In the first weeks a bench is learning the shape of your operation: which counterparty is careful and which is not, which lender wants the file assembled which way, which exception you will always take and which you will never take, whose sign-off is real and whose is ceremonial. None of that is written in anybody's handbook. In an hourly arrangement it is re-learned and re-billed each time, and it walks out of the door with whoever happened to hold it. In a seated lane it stops being knowledge anyone has to hold and starts being visible in how the work comes back.

The second-order effect is the one that matters commercially. Once a lane holds that context, the next lane inherits it. A diligence bench that already knows your counterparties makes an underwriting bench cheaper to seat, not because anything was discounted but because the learning was already paid for once. That is how a lane expands the way a good team expands — one earning the next — rather than the way a subscription expands, which is by being sold again to somebody who has not adopted the first one.

You will notice this page states no return figure, no hours-saved figure and no headcount comparison, and we would rather explain that than have you assume it is an oversight. We hold no verified outcome metrics, and an invented number on the page an investor reads is worse than no number at all — it is the one thing that, once caught, makes everything true on the page unreadable. So we sell the shape. If you want to see the coordination rather than read about it, the boardroom page runs it live; if you want to talk about a specific lane in your own operation, the partner door is the honest next step.

How this looks in the wild

Capital Consortium is the standing example: the whole autonomous workforce bolted onto a real operation, doing real deal work end to end rather than a pilot running beside the real thing. We name it because a thesis with no live lane behind it is a slide, and because the shape of that lane is what actually transfers to somebody else's organization.

We are deliberately not attaching a metric to it. We hold no verified outcome figures, and we would rather point at something real without a number than attach a number we cannot source to something real. What we will do instead is walk you through the lane itself — which practitioners seat, what each of them owns, where the handoffs happen, what the humans still decide, and what went wrong early enough to be worth telling you about. That conversation is more useful than a statistic would be, and it is the one worth an hour of your time.

If you are sizing the category rather than buying a lane, there is an honest investor read behind this page — ranges and confidence, never a number picked first and justified afterwards. Here's the investor read

Talk to us.

Four doors, one next step behind each. A human reads every one.