What Venture Building Looks Like From the Inside

Our ventures did not start as ventures. Each one began as a problem we kept meeting in client work, solved badly with spreadsheets for a while, and eventually built properly because the workaround became embarrassing.

That origin matters. The hardest part of building a product is finding a real problem with real urgency, and consulting work hands you those every week.

The process we use

**Notice the repetition.** If three unrelated clients describe the same pain in the same quarter, that is signal. One client's pain is a project. Three is a market.

**Build the smallest honest version.** Not a mockup and not a platform — something that does one job end to end for one real user. Ship it internally first.

**Charge early.** The gap between "this is interesting" and "here is my card" is the only reliable measure of demand. Free pilots teach you very little.

**Give it a real owner.** A venture without one accountable person will lose every scheduling conflict with client work, forever.

**Decide in advance what stopping looks like.** Write down the number that means stop, then honour it.

Where internal ventures die

**The second month.** The novelty has worn off, the first users have found the rough edges, and paying work is louder. Most products die here, unfinished, and nobody notices.

**The first real customer.** Support, onboarding and invoicing turn a side project into an operation. Teams that have not planned for this quietly stop selling.

**The first plateau.** Growth flattens and the temptation is to add features. Usually the answer is distribution, not scope.

What we bring to it

The same things we bring to client engagements: engineering, cloud infrastructure, search visibility and the commercial experience to price something properly. Being an ICANN accredited registrar and an AWS partner means the unglamorous foundations — domains, hosting, deliverability, security — are handled in-house rather than outsourced and hoped for.

Why we keep doing it

Running our own products keeps our advice grounded. When we tell a client that a decision will be painful later, it is usually because it was painful for us. That is worth more to the people we advise than any framework we could draw on a whiteboard.