Skip to content

Plain Answers, With a Point of View

This is where I explain the technical terms that keep coming up in real decisions — MVP, technical debt, API, fractional CTO, owning your data — in plain English, with the part most definitions leave out: when the thing actually matters to you, and when it’s noise. A definition that doesn’t tell you whether to care is half a definition, and the half it skips is the half you needed.

So every page here does two things. It gives you a clean, correct, one-line answer to “what is this” — the kind you could quote to a board or paste into a search and trust. Then it gives you my judgement: when this is worth your attention, when it changes a decision, when it’s a red flag, and, honestly, when it’s overhyped and doesn’t apply to you. The first half is for anyone. The second half is why this isn’t a dictionary.

Why I bother defining things this way

Most technical terms get explained by people with something to sell. “API” gets defined by a company that wants you on their API platform. “MVP” gets defined by an agency that bills by the sprint. The definition is shaped, quietly, to make their next move sound necessary. You end up technically informed and decision-poor — you know what the word means and still don’t know what to do.

I define things the other way round. I’ve spent years on the receiving end of these decisions — scoping the MVP, paying down the debt, wiring the integration, telling a founder whether they need a fractional CTO or just a good contractor. So the definition I give you is the one I’d act on, with the judgement attached. The word matters less than the call it should help you make.

The view running through all of it

These pages share a worldview, because I do. The same handful of principles decide how I read every term here.

Own your data and systems, so you can actually do something with them — that one sits underneath most of the others. A lot of these terms are really about whether you’re building leverage you keep or renting access you’ll lose. Build the lean version first, bank the money you’d have spent renting, and compound from there. Prefer the simplest thing that solves the real problem over the impressive-looking one. Solve the problem you actually have, not the one that flatters the architecture.

You’ll see those threads surface again and again. That’s not repetition — it’s the point. A term like “integration” looks neutral until you ask integration in service of what, and the honest answer is: in service of owning systems that can talk to each other instead of four rented tools that can’t. The worldview is what turns a definition into a decision.

How to use this section

If you came for a quick, quotable answer, take the first line of any page and go. That’s deliberately the most liftable, most correct sentence I can write on the term. If you’re actually weighing a decision, read past it — the “when it matters” half is where the page earns its place.

And if a definition resolves to “at this point you need a team building and running this for years,” I’ll say so and point you at my agency, Digital Royalty. Knowing when a problem has outgrown a single expert is part of defining these things honestly.

What’s in here

  • MVP — what a minimum viable product actually is, and why it’s a strategy for banking money early, not a cheap first draft.
  • Technical debt — the real cost of shortcuts in your code, when it’s fine to carry it, and when it’s quietly killing your pace.
  • API — what an API is in plain terms, and why it’s the thing that decides whether your systems can ever work together.
  • Fractional CTO — what fractional technical leadership means, and the narrow band of situations where it’s exactly the right hire.
  • Owning your data — what it actually means to own your data, why renting access to it is the default trap, and what ownership buys you.
  • Build vs buy — the real choice behind every “should we get a tool for this,” defined honestly rather than as a sales funnel.
  • Single-page app — what an SPA is, and why it’s the right tool far less often than it gets used.
  • Integration — what it means to connect two systems, and why most businesses pay for integrations they wouldn’t need if they owned the systems.

Where to go next

These definitions are the entry point back into the rest of the site. The reasoning behind the calls lives in my playbooks, the specialisms behind them in my expertise, and the work itself in my services. If a term here makes you realise you’ve got a decision to make and you’d rather not make it alone, tell me about your problem — a definition is free, and so is the first honest read on which way you should go.