Insights

Short takes. Strong opinions.
Held loosely.

Different from the blog. The blog is tutorials. Insights are arguments — on AI, automation, pricing, tooling, and the practice of building software on your own. Direct. British. Sometimes wrong, never neutral.

PracticeMay 20266 min read

Why I only take one client at a time.

Splitting attention across projects is a hidden tax that everyone pays except the consultant. Here is the case for going deep with one client.

Read the full take
ToolingMay 20267 min read

The stack I actually use, and why.

Next.js, Supabase, Vercel, Resend, Claude. The list is short and stays short. Here is how I picked it and why I have not budged.

Read the full take
PricingMay 20268 min read

Why fixed-price beats hourly, for both of us.

Hourly billing aligns the wrong incentives and turns every conversation into a clock-watch. Fixed-price moves the risk to where it belongs — me.

Read the full take
AIMay 20267 min read

When to choose AI over a rules engine.

Most of the time, an LLM is the wrong answer. Here is the heuristic I use to decide whether a problem actually needs a model or just a switch statement.

Read the full take
CostMay 20266 min read

The real cost of stitching SaaS tools together.

Eight tools at £8 a seat sounds reasonable until you do the maths. The hidden costs are integration debt, lock-in, and the tax of nobody owning the workflow.

Read the full take
ToolingMay 20267 min read

Why I prefer Supabase to almost everything.

It is not the marketing. It is that Postgres + RLS + realtime + auth + storage in one project removes more accidental complexity than any other choice I make.

Read the full take
AutomationMay 20266 min read

Automation that actually pays off.

Most automation projects die in production because they automate the wrong thing. Here is the test I use to decide whether something is worth automating at all.

Read the full take
EngineeringMay 20267 min read

The myth of best practices.

Most “best practices” are decisions someone else made about a context that is not yours. Here is when to follow them, and when to ignore them with confidence.

Read the full take

Let's build something good.

You've got a problem. I solve problems with software for a living.The fastest way to find out if we can work together is to talk.

Get in touchTell me about your project

Stack I build with

Next.jsTypeScriptPythonSupabaseAWSVerceln8nClaudeOpenAIPostgreSQL