← All notesSTRATEGY·05 Oct 2024·5 min

Technical decisions clients actually care about

Clients don’t care about your architecture. They care about outcomes. How to stop explaining JOINs and start building trust.

I've spent years explaining technical decisions to clients. Most of those explanations failed — not because clients couldn't understand, but because I was answering questions they hadn't asked. I'd reach for the architecture diagram when they wanted a date, a number, and a reason to relax.

The four things

Every technical decision ultimately affects four things clients care about. Lead with these, always. If your recommendation doesn't connect to at least one of them, you're having the wrong conversation — and they can feel it, even if they can't name it.

01

Time

When will it be done? Not the optimistic version — the one you'd bet on.

02

Money

What will it cost to build, and what will it cost to keep?

03

Risk

What could go wrong, and how badly, and what are we doing about it?

04

Flexibility

Can we change course later, or are we pouring concrete?

Translate, don't simplify

There's a difference between dumbing something down and translating it. Dumbing down is condescending and usually wrong. Translation keeps the truth intact and changes the units — from JOINs and indexes into ‘pages load in under a second even on the busiest day’. The fact survives; only the language changes. Clients can tell the difference instantly, and they trust the translator far more than the lecturer.

  • Instead of ‘we'll refactor the data layer’ → ‘we'll make changes safer and faster, so future work costs less’.
  • Instead of ‘it's not indexed’ → ‘some pages get slow as data grows; here's the fix and what it buys you’.
  • Instead of ‘that's technically possible’ → ‘we can do that; here's the time and trade-off it adds’.

Trust is built in the unknowns

The moment that actually earns a client's confidence isn't when you have a slick answer — it's when you don't, and you say so cleanly. ‘I don't know yet’ followed by ‘here's how I'll find out, and when’ tells them you'd rather be right than impressive. That's the person they want holding the budget.

Clients don't hire certainty. They hire someone who tells them the truth at a pace they can act on.

‘I don't know, but I'll find out by Thursday’ builds more trust than a confident guess. The confident guessing is just gambling with someone else's money.

Still with me?

Weighing a rebuild, a rescue, or a roadmap?