Skip to content

Diagnostics — A Fast, Honest Read on Where You Stand

These are the quick diagnostics I’ve put online — the same questions I ask in the first hour of an engagement, turned into something you can run yourself in a few minutes. Each one gives you an honest read on a specific decision: is your architecture going to hold, what is your tech debt actually costing you, should you build or buy, is your project quietly heading for trouble, and whether a day rate you’ve been quoted is fair. None of them sells you anything. They tell you where you stand and what I’d do about it.

A tool is not advice tailored to your exact situation — that’s what a conversation is for. But a good diagnostic does the most valuable thing a consultant does early: it points you at the real question. Most expensive mistakes I get called in on weren’t caused by a hard problem. They were caused by nobody asking the right question soon enough. These are designed to ask it for you.

Why these exist, and what they’re not

I’m wary of online calculators, because most of them are lead-bait dressed as insight — they ask three questions, return a scary number, and funnel you toward a quote. These aren’t that. The logic underneath each one is the way I actually think, which means it carries a point of view, not a sales funnel.

That point of view is consistent across all of them. I’d rather you owned the thing your business runs on than rented it. I’d rather you built the lean version fast and banked the money than commissioned the cathedral. I’d rather you solved the real problem than the impressive-looking one. So a build-vs-buy calculator here doesn’t quietly nudge you toward a subscription — it surfaces the cases where owning a small system beats renting a big one. A tech-debt calculator doesn’t just frighten you with a number — it points back at the systems you don’t fully own as the place the cost compounds. The diagnostic and the worldview are the same thing.

The honest limit: a tool reads a situation from a handful of inputs. It can’t see the context that changes the answer — your team, your runway, the politics, the thing you didn’t think to mention. So treat every result as a sharp prompt, not a verdict. Where the read surprises you, that’s the signal to dig in, not to act blindly.

How to use them

Run the one that matches the decision in front of you. Read the result, then read my interpretation of it on the page — the number or the band only means something once you know what’s usually behind it. Then take the next step the page points you to: a Playbook when you want the full reasoning, a Service when you want it fixed, or a conversation when the result didn’t sit right.

If you don’t know which one you need, that’s a useful signal in itself. It usually means the question isn’t “which tool” — it’s “what’s actually wrong here,” and that’s worth a direct conversation rather than a calculator.

What’s in here

  • Architecture risk assessment — a fast read on whether the way your system is built will hold as you grow, or whether it’s storing up an expensive rebuild. For founders and CTOs who suspect the foundations are shakier than the demo suggests.
  • Tech debt calculator — what your accumulated shortcuts are actually costing you in slowed delivery, not an abstract score. For teams that feel every change taking longer than it should.
  • Build vs buy calculator — the honest math on whether to build a lean system or rent a SaaS one, over a real timeframe rather than this month’s invoice. For anyone about to sign a subscription they’ll be paying for years.
  • Is your project at risk? — a check on whether a build in flight is heading for the rocks, before it’s obvious to everyone. For founders watching a project that’s started to feel wrong.
  • Developer day-rate benchmark — a directional read on whether a rate you’ve been quoted is fair for what you’re getting. For non-technical owners trying to tell a fair price from a bad one.

Where this goes next

A diagnostic gives you the read; the rest of the site gives you the depth and the fix. The playbooks are the full reasoning behind these tools — the build-vs-buy calculator is the short version of a much longer argument. The services are what you hire me for when the read says something needs doing. Tools sit at the front of that journey on purpose: they’re the cheapest way to find out whether you have a problem worth my time.

If a result surprised you, or you ran one and still aren’t sure what it means for you, tell me about it — twenty minutes usually makes the next move obvious. And if what a tool surfaces is a full build with a team behind it, that’s what my agency, Digital Royalty, is for. (Back to the homepage.)