The Writing · 18 pieces

Newest first

Charge Before You're Ready

Pricing for technical founders: why engineers undercharge, why free users tell you nothing, and how a price is a question that tests if the problem is real.

Build Less Than You Think

Scope for technical founders: why over-engineering is procrastination you can defend, and the one test for what to cut before you build the whole thing.

You're Short on Evidence, Not Ideas

How technical founders find the cheapest question that could prove them wrong before building the answer, not the easy assumption most test instead.

The content factory is closing

HubSpot invented the content playbook every SaaS blog copied, then lost three quarters of its traffic to AI search. What that changes about what to write.

What AI Sovereignty Looks Like in Practice

The operating model that lets regulated providers use AI without exporting their knowledge: classification, approved tools, audit trails, named accountability.

Strategic Leakage Is Not a Privacy Problem

Privacy frameworks protect personal information. They say nothing about the operational knowledge your teams push into AI tools every day. That gap has a cost.

Is Your Data Training Your Future Competitor?

Australian healthcare and aged care providers are pushing operational knowledge into AI tools they don't control. That knowledge is a strategic asset.

Could Your Claim Survive a Question?

Australian software teams rebuild R&D Tax Incentive evidence from memory every April. Reconstruction isn't evidence, and the FY27 fix starts this week.

The Thing You're Best At Is the Trap

Why technical founders stall: building is where you feel competent, so it becomes where you hide from the work that actually decides if the company lives.

The Knowledge That Doesn't Transfer

AI for regulated teams: an AI system's knowledge doesn't hand over like ordinary software, and you can't stay accountable for a system no one understands.

Where AI Earns Its Place

A decision lens for adopting AI on regulated teams: sort tasks by what being wrong costs, then act differently in each zone. The finale of Still Accountable.

Speed Was Never Your Bottleneck

AI in regulated engineering makes code faster, but speed was never the constraint. Correctness, trust, and sign-off were. Don't optimise what wasn't slow.