How I Help Professional Services Firms Own the Workflows They Rent Per Seat
Professional services firms — law, accountancy, consultancy, surveying, recruitment — quietly pay per-seat, forever, for the workflows that are their business, when many of those workflows are things they should own outright. The practice-management tool, the document-assembly system, the client-intake and matter-tracking software: priced per professional, per month, in perpetuity, scaling up every time you hire. For a people-heavy firm that’s a cost that compounds against you precisely as you grow. I help these firms see which of their rented workflows is a lean owned system away from being a one-time build that pays for itself — and which genuinely isn’t worth touching.
The mistake: renting your core workflow per head, forever
The recurring professional-services error is accepting per-seat SaaS as simply how things are done, even for the workflows that define the firm. A fifty-person firm paying per-user, per-month for the system its fee-earners live in is paying a tax that grows with headcount and never ends — and often for a tool that does ninety percent of what they need and fights them on the ten percent that’s specific to how they work. The per-seat model is brilliant for the vendor and quietly punishing for a firm whose entire growth model is adding more billable people.
This is build-don’t-rent in its most overlooked setting, because professional-services firms rarely think of themselves as software businesses and so never question the rent. But the maths is stark in a people-heavy firm: a workflow that costs a meaningful sum per seat per month, across dozens of seats, for years, is often more expensive in total than building a lean owned version that does exactly what the firm needs — and the owned version doesn’t get more expensive every time you hire. The firms that see this turn a forever-cost into a one-time investment and an owned asset. The ones that don’t keep paying the headcount tax indefinitely.
The professional-services-specific reality that sharpens it: your workflows are usually unglamorous and well-understood — intake, document generation, time and matter tracking, reporting. That’s exactly the kind of thing that’s cheap to build lean and own, because it’s not novel and it’s not complex; it’s standard process that off-the-shelf tools charge a premium for precisely because every firm needs it. The very ordinariness that makes you assume you must rent it is what makes it a good candidate to own.
What actually moves the needle: owning the workflows that scale with headcount
What matters is identifying the one or two workflows where you’re paying per-seat for something the firm could own — usually the ones most specific to how your firm actually works, where the rented tool is a poor fit anyway — and building the lean owned version. That’s not “rip out everything and build bespoke”; that’s the over-building trap, and for genuinely commodity tools renting is correct. It’s surgical: find the workflow where per-seat rent against headcount has quietly become a serious cost and the fit is poor, and own that.
These systems are almost always dashboards and automations at heart — a clean internal system that tracks the work, assembles the documents, and automates the repetitive process your fee-earners currently do by hand or pay a per-seat tool to do. Built lean with judgement, the owned version is cheaper over any reasonable horizon and fits your firm exactly, because it was built for your process rather than the average of ten thousand firms. The own-your-data angle is real here too: your client and matter data is one of your most valuable assets, and per-seat tools keep it in their silo on their terms.
I’m useful here because I’ll do the honest maths with you — which rented workflow has crossed the line into worth-owning, and which is fine left rented because owning it would cost more than it saves. A technical advisory engagement is usually the right shape: a clear-eyed read on your stack and a direction you can act on, without bringing anyone in-house.
How I work with professional services firms
Usually it’s advisory and one-off to start: a review of what you’re renting against headcount, the honest maths on what’s worth owning, and a plan for the one workflow where ownership clearly pays. Some firms then want a light standing relationship while they build and adopt the owned system. The shape is deliberately small, because the value is the decision and the direction, not a big project — and often the right answer is to own one thing well rather than everything badly.
Who this isn’t for
If you’re a small firm where the per-seat rent is genuinely modest and the tools fit fine, owning your own systems isn’t worth it — keep renting, and I’ll tell you so. The build-lean case only holds once the headcount tax and the poor fit are real costs. And if owning the workflow turns out to need a substantial, maintained build, that’s Digital Royalty territory, where the team and process come in rather than one advisor.
Tell me what you’re renting per head
If you’re paying per-seat for the workflow your firm runs on and you’ve never questioned whether you should own it, that’s the conversation worth having. Tell me what’s in your stack and I’ll do the honest maths on what’s worth owning and what isn’t. If your firm is more of a software product than a practice, the SaaS read fits, and if you run an agency specifically, the agency page covers owning what you rent from a related angle. The other sectors I work in are there if your firm sits elsewhere.