Resources

How to prove a product before you build the team.

This is where our thinking lives: how founders and companies can validate an idea with a real, working product first, so the team and the budget follow evidence instead of a pitch. Below is how we approach it, and the articles that go deeper.

Our approach

Build the proof, then decide.

Most advice about new products stops at the strategy. We think the fastest way to an answer is to build the smallest real version that carries it, put it in front of users, and read what actually happens.

Scope to exactly what proves it. A first MVP, a single critical feature, or a phased build. The discipline is deciding what to build for real and what to fake for now, so you spend the least to learn the most.

Name the hard parts out loud. Architecture, reliability, evaluation, and the calls about what is worth building. AI gives the speed. Judgment is what makes the result hold up, and it is the part worth writing about.

Let evidence, not opinion, make the call. A working product changes every conversation, with users, with customers, and with investors. Decide on something you can click, not a deck and a hope.

Elsewhere

More of Imran's writing lives on imranbaig.io, and shorter updates are on LinkedIn.

Have an idea worth proving

Skip the reading and just talk it through.

Send a note. We will tell you the fastest way to prove your idea, even if the honest answer is not yet.

Let's talk