Book an intro call

INSIGHTS

Notes from delivery.

Practical notes on building, rescuing and running commercial software, written from inside the projects.

Rescue or rewrite: how we decide what a stalled codebase deserves

The instinct after inheriting a mess is to burn it down. Sometimes that's right. Here's how we decide.

Read the article

What a paid discovery actually buys you

Requirements, architecture, risks and an estimate you can hold someone to, before the big check.

A software requirements document template you can copy

The structure we use in discovery, section by section, with a short example for each. Copy the headings and fill them with what you know about your business.

Is your Lovable app ready for paying users?

Lovable gets a product in front of people fast. Before you charge them, check the database rules, the keys, the server-side logic and your way out of the platform.

A security checklist for vibe-coded apps

Apps built with AI tools can look finished long before they are safe. Eight checks to run before real users, real data and real payments arrive.

The checklist we run before anything goes live

What separates software that demos well from software a business can charge money for.

My developer disappeared mid-project: what to do this week

Secure your access first, then find out what actually exists, then decide what happens next. A practical order of work for the first week.

Taking over a codebase nobody documented

Recovering requirements from old emails, observed behavior and the product itself.

What client ownership means in practice

Accounts, code, infrastructure and data, set up so you can walk away from your vendor whenever you choose.

Writing requirements an engineer can actually build from

Turning what you know about your business into specs an engineer can build from.