Playbooks — How I Make the Technical Calls
These are the decisions people actually bring me, written down with the reasoning attached. Not tutorials, not lists of tips — the call I’d make on your behalf, and enough of the working that you can make it yourself.
A playbook is one of my judgement calls generalised. When a founder asks “should we build or buy this?” or “is the quote we got reasonable?” or “do we even need a fractional CTO yet?”, they don’t want a neutral overview of the options. They want someone who has made the call enough times to tell them which way it usually goes, where the exception lives, and how to spot which side of the line they’re on. That’s what these are.
What a playbook is, and why I write them this way
Most advice on these questions is either a sales pitch dressed as guidance or a hedge dressed as balance. The sales pitch tells you to buy the thing the author sells. The hedge tells you “it depends” and lists ten factors without ever weighting them, which is useless — of course it depends; your job was to tell me on what, and which way it leans.
I do neither. Every playbook here leads with the call I’d actually make, then shows the reasoning, and then — this is the part that matters — names the exact line where the opposite call becomes correct. If a playbook of mine is dogmatic, if it never tells you when I’d do the other thing, distrust it. Certainty with no concession is the tell of someone who hasn’t done the work enough times to have been wrong. I have been wrong enough times to know where the edges are, and the edges are where the value is.
The reason these are useful is that the hard part of a technical decision is almost never the technical part. It’s knowing which question you’re actually answering. People ask “which CRM should we buy” when the real question is “should this be a thing we rent at all.” They ask “why is this build taking so long” when the real question is “was this ever scoped to ship.” They ask “should I hire a full-time engineering lead” when what they need is six hours a month from someone senior. The playbook’s job is to back you up one step, to the decision underneath the decision, and answer that one straight.
The worldview these calls run through
I don’t make these calls neutrally, and I won’t pretend to. There’s a point of view underneath all of them, and it’s consistent enough that you’ll see it surface on every page.
Own your data and the systems that run your business, so you can actually do something with them. Build the lean version of the thing that’s genuinely yours rather than renting a fix you’ll pay for forever. Ship the smallest thing that solves the real problem, bank the money you’d have spent renting, and compound from there. Reach for the simplest approach that works, not the most impressive-looking one. And solve the problem in front of you, not the one that would make a better slide.
That worldview is not decoration on top of the advice — it is the advice. When I tell you to build a lean internal tool instead of buying a subscription, it’s because owning the data behind it is leverage you’ll use for years. When I tell you to scope an MVP ruthlessly, it’s because the fastest route to owning a working system is to stop trying to own all of it at once. The calls and the worldview are the same thing.
Where these calls have a limit
A playbook hands you my judgement. It does not hand you a team, and that’s the honest boundary. These pages will tell you which way to decide and why. They’ll tell you what good looks like and how to spot the failure modes. What they can’t do is execute a multi-month build with people on it, owning the delivery and the risk. When the honest next step is “this needs a team and a process behind it, run for a year,” that’s not advisory work any more — that’s my agency, Digital Royalty, and I’ll say so on the page where it applies rather than pretend one person solves everything.
What’s in here
Build or buy? — the one most people get backwards. When to build a lean version of the software that runs your business, when to just buy the commodity, and the MVP-first math that makes year two pay for itself. Start here if you’re staring at a SaaS comparison table.
When you actually need a fractional CTO — the honest trigger conditions for bringing in part-time senior technical leadership, and the just-as-honest signs you don’t need one yet and would be buying reassurance instead of capability.
How to evaluate a software quote — how to read a build quote when you’re not technical: what the number is actually telling you, the questions that separate a real estimate from a guess, and why the cheapest and most expensive quotes are usually the two to walk away from.
How to rescue a stalled build — what to do when a project has gone quiet, slipped twice, and you can’t tell whether it’s nearly there or nowhere. How I diagnose where it actually is before anyone writes another line of code.
How to scope an MVP — how to cut a big idea down to the smallest thing that solves the real problem and can ship, without gutting the point of it. The single question I use to decide what stays and what waits.
Modernise or rebuild? — when an ageing system is worth fixing in place and when it’s genuinely time to start again. The call most people get wrong in the expensive direction, and how to tell which one you’re facing.
Owning your data when you leave a SaaS — the practical playbook for getting your data out of a tool you’ve outgrown and into something you own, without losing your history or breaking your operation mid-move.
How to brief a developer — how to describe what you want so you get what you meant. Briefing well is the cheapest way to make a build go right, and most failed projects failed at the brief, not the code.
Where to go from here
If a playbook lands and you want to see what the engagement looks like when I make the call alongside you rather than at a distance, the services pages cover the productised advisory work directly. And the comparisons section handles the head-to-head “X vs Y” decisions — consultant vs agency, fractional vs full-time — where a playbook only touches them in passing.
If you want me to make one of these calls for your actual situation rather than the general case, tell me about your problem. Most of these are a short conversation that saves a long, expensive detour. (Back to the homepage.)