The Sectors I Work In — and How I Read Each One
I don’t sell “industries we serve.” I sell knowing where your specific kind of business predictably gets the technical decisions wrong. A fintech founder, an agency owner, and an ecommerce operator each waste money in different places — and the value of bringing me in is that I’ve already seen your sector’s particular mistake before you make it. This section is how I read each one.
The reason a sector lens matters at all is that the worst technical decisions aren’t generic. They’re shaped by the pressures of the business. A scaleup over-engineers because it’s terrified of the traffic it doesn’t have yet. An agency rents a stack it could build and resell because nobody framed the tools as a product. A professional-services firm pays per seat, forever, for a workflow it should own outright. The mistake is industry-specific, so the read has to be too.
The same worldview, pointed at each sector’s weak spot
Everything I do points back to one idea: own your data and your systems, build the lean version first, and don’t rent at scale what you could own. That doesn’t change by sector. What changes is how each sector tempts you to break it.
Ecommerce gets seduced into renting every piece of its operation — catalogue, orders, customer data — through a dozen SaaS subscriptions, until the business doesn’t actually own the thing it runs on. Startups get seduced into building for a million users before they’ve banked a pound. SaaS founders get seduced into bolting on features instead of owning a clean core. Fintech and healthtech get seduced into treating compliance as a reason to over-build everything, when the real move is to own a small, well-governed core and be ruthless about the rest. The worldview is constant; each page below names the specific trap that sector falls into and the cheaper way out.
That’s the spine of every page here, and it’s why these aren’t market reports. I’m not telling you your sector is “growing fast and needs good software.” Everyone knows that, and it’s useless. I’m telling you where the technical money gets wasted in your world and what I’d do instead.
Where the sector ends and the problem begins
There’s a limit to how far the sector label takes you, and I want to be honest about it. Two ecommerce businesses can have nothing in common technically; a fintech and a SaaS company can have nearly identical real problems. The sector is a starting read, not a diagnosis. When you bring me in, the first thing I do is find the actual problem under the sector framing — because “we’re a healthtech company, we need X” is usually wrong in the specifics, and the specifics are where the money is.
So treat these pages as the fastest way to see whether I understand your world, not as a promise that your business fits a template. If the read on your sector lands — if you read it and think yes, that’s exactly the mistake I nearly made — that’s the signal it’s worth a conversation.
The sectors
- Startups — for founders who need a revenue-banking MVP, not a platform built for scale they don’t have yet. Where to spend and where to stop.
- Scaleups — for the company past product-market fit whose early build is now the thing holding growth back. What to fix, what to leave, what to rebuild.
- Agencies — for agency owners renting tools they could build lean, own, and resell as their own margin instead of paying someone else’s.
- Ecommerce — for operators whose business runs on a dozen rented systems and doesn’t actually own its own catalogue, orders, or customer data.
- Fintech — for founders where the real problem is owning a clean, well-governed data core, not bolting on more compliance theatre.
- Healthtech — for teams where data sensitivity is real but is being used as an excuse to over-build everything instead of owning a small, careful core.
- SaaS — for founders whose product is drowning in features bolted onto a core nobody owns cleanly, when the leverage is in the core.
- Professional services — for firms paying per-seat forever for workflows they should own, when a lean owned system would pay for itself.
- Property — for property businesses stitching together portals and spreadsheets when the data that matters should live in one system they control.
Where a sector needs a team, not an advisor
These pages are about the advisory work — the judgement, the hard calls, the fractional seat, the audit, the rescue. Some sectors, at some stages, honestly need a standing team to build and run software for years, not one senior person to advise. When that’s the truth for your business, I’ll say so, and that’s what my agency Digital Royalty exists to do — same standards, with the team and process behind it. Knowing which side of that line you’re on is itself one of the calls I’m useful for.
Find your sector
Read the page for your world and see if the read lands. If it does, the next question is usually which engagement fits — the services section lays those out, and the expertise pages show the kinds of problems I actually solve. Or just tell me about your problem and I’ll tell you straight whether I’m the right person for it. (Back to the homepage.)