Every service business is about to face the same question: if your client can get a 70% version of what you sell from AI in an afternoon, what exactly are they paying you for?
The businesses that will thrive all answer it the same way: with a service powered by software they built themselves. I call it Service With Software.
Service With Software is a service powered by software in the backend. Not a SaaS company you licence from someone else. Software you built yourself, that your team is trained on, built on your data, your core competencies and your way of working, tailor-made to how you deliver outcomes.
The service is what the client buys. The software is why it’s better. And the software is never for sale, because it only makes sense inside the service it powers.
That’s the whole model in three sentences. The rest of this page is the detail: what qualifies, what it looks like in practice, the maths, and who should be building one.
Two things, at the same time.
First, AI made 7 out of 10 the new average. Any service, your client can now get a competent version from AI in an afternoon. The market for average work is gone, and the value has moved to the last stretch, from 7 to 10. I’ve written about this in full here: The 7 Out of 10 Principle.
Second, building software stopped being expensive. The entire SaaS industry existed because software cost hundreds of thousands to build, so you rented someone else’s and bent your business around it. My team now ships internal tools in days. When both of those things are true, the logical move for a service business changes: stop renting generic tools, start building your own.
Code can be copied. Data has to be accumulated. People have to be built and kept. That order is the strategy, and it’s why the model defends itself: a competitor can clone your features in a week, but they can’t clone your years.
Let me be clear about the boundary, because every agency on earth is about to claim they have proprietary AI.
A workflow in ChatGPT is not software. A white-labelled dashboard is not your software. A prompt library is not an operating system.
The bar: your team built an actual application, on your own data, with your own workflows, that your business runs on. Slack is the famous example of the shape. A games studio built an internal communication tool because they had a communication problem, and the tool turned out to be a whole piece of software in its own right. That’s the bar. Something real enough that it could stand alone, even though (and this is the difference in this model) you never let it.
So the minimum is all three: owned software, proprietary data feeding it, custom workflows around it. Two out of three is a head start, not a moat.
At StudioHawk we’re building HawkOS, the operating system that powers how we deliver SEO. I won’t go deep on internals, but here’s the shape of it.
Before, our client knowledge lived everywhere: the CRM, the project management tool, call recordings, onboarding docs, briefs, keyword data across half a dozen sources. Workflows were segregated and knowledge sat in silos. HawkOS centralises all of it into one source of truth per client, so everything we do pulls from the same database and stays consistent.
Then the compounding starts. Take information architecture, one of the most valuable things we build for clients. It used to take dozens of hours of senior time. It now takes a couple of hours, because the system holds all the client’s data, knows how we structure an IA, and has learned from every IA we’ve ever built. Each one makes the next one better. That’s the data lake working: not storage, compounding.
| Pure service | Service With Software | Pure SaaS | |
|---|---|---|---|
| Gross margin | 30-50% | 50-70% | 80%+ |
| Scales with | Headcount | Data | Servers |
Better margins than a pure service, because software carries more of the delivery. Not SaaS margins, because people still make the calls AI can’t. Full breakdown with benchmark data here: Service Business Margins.
I think this is the future of most service businesses. If you’re five people or more, you should be working on some kind of software layer under your service, and the build cost has fallen far enough that you have no excuse not to start with one tool.
Below that it gets harder. I think this genuinely disrupts freelancers: not because they lack skill, but because they don’t have the time or the accumulated data to build a moat like this. A solo operator using AI well is exactly the “new 7 out of 10” the market now gets for cheap.
Where’s it going next? Anywhere a service runs on repeatable judgement over accumulated data. SEO and marketing are early because the data is digital and abundant. Accounting, legal, recruitment and consulting are the same shape.
Isn’t this just tech-enabled services? It’s the evolution of it. Tech-enabled meant using tools. This means owning them. Full comparison here.
Isn’t this Service-as-Software, the VC thing? No, and the difference matters: they say replace your people with agents, I say arm them. Full comparison here.
Why not sell the software? Because it’s worth more inside the service than out of it. Sold, it’s a product competing with every other product. Inside, it’s the reason the service can’t be copied.
Couldn’t a client just build their own? Honestly, yeah, and the honest version of that answer is a page of its own: How Service Businesses Build a Data Moat.