Insights

Useful thinking,
made practical.

Field notes on building clearer brands, better digital products, and the systems that help them grow.

A curve descending steeply and then settling into a long flat plateau, captioned “Narrow before you add”

After the MVP: turning first users into product-market fit

The MVP was the question. The months after launch are the answer, and most teams misread it by adding features when the correct move is to narrow the audience.

One smooth form passing through a narrow gap between two slabs while others wait behind, captioned “Ready is not a feeling”

Web strategy9 min read

How to know when your MVP is ready to launch

Launch readiness is not about feeling ready, which never happens. It is about whether the launch can produce evidence you would be willing to act on.

A balance beam where many small blocks outweigh one large block, captioned “What actually moves the number”

Studio notes9 min read

What an MVP actually costs, and what drives the number

Published ranges span twenty-fold and tell you almost nothing. The useful question is which decisions move your number, and which costs never appear on the quote.

Two towers of equal height, one built from modular cubes and one carved from solid stone, captioned “Build the hard part properly”

Web strategy9 min read

No-code, low-code or custom: choosing your MVP stack

The question is not which approach is better. It is whether the part of your product that has to be special is something the platform will let you make special.

One continuous rail running diagonally while broken alternative routes fall away beneath it, captioned “Decide earlier, build less”

Product10 min read

The fastest honest way to build an MVP

Speed in an MVP does not come from working faster. It comes from deciding earlier, building less, and refusing to rebuild things that already exist.

A fixed tray packed full of blocks with larger blocks left outside it, captioned “Fixed time, variable scope”

Product9 min read

How to scope an MVP when the deadline is fixed

Estimates expand to fill the runway available. An appetite does the opposite: it states what the answer is worth, and forces the scope to fit inside it.

A lone illuminated doorway in empty space with measuring lines across the floor, captioned “Measure demand before you build”

Web strategy9 min read

The landing page test that comes before the MVP

A page describing a product that does not exist yet is the cheapest demand instrument available. It is also the easiest one to run badly and misread completely.

A cloud of weightless translucent shapes above one small dense sphere, captioned “Evidence, not encouragement”

Product9 min read

How to validate a startup idea before you build anything

Most validation produces encouragement rather than evidence. The difference is whether the person on the other side of the table gave up anything to say yes.

Three abstract objects at increasing stages of completion in a row, captioned “Three questions, three tools”

Product9 min read

MVP, prototype, or proof of concept: which one you need

Three words used interchangeably in most kick-off meetings, answering three different questions. Picking the wrong one is how teams spend a quarter proving something nobody doubted.

Scattered abstract fragments resolving into a single upright measuring instrument, captioned “Maximum learning, least effort”

Product8 min read

What an MVP actually is, and four things it is not

A minimum viable product is not a cheap first version of the real thing. It is the smallest instrument that answers the question most likely to kill your business.