Why one person should own product, brand and growth, and what it costs when three people do

Here is a meeting I've sat in more times than I can count. A founder, a developer, a designer and a marketer. The marketer wants a landing page that promises a feature. The developer says the feature is three weeks away. The designer has mocked a version of the feature that the developer says isn't what was specced. The founder, who has been paying all three for two months, asks when it ships. Nobody in the room can answer, because the answer lives in the gaps between them.

The gaps are the problem. Not the people. Every handoff between product, brand and growth loses information, adds a meeting, and creates a place where nobody is accountable. The fix I've arrived at, after years on both sides of that table, is simple to state and hard to do: one person owns the whole outcome.

The argument

Product, brand and growth are not three disciplines. They are three views of one question: what is this thing, who is it for, and why would they choose it? A product decision (what does the free tier include) is a brand decision (what does generosity say about us) and a growth decision (what converts) at the same time. Splitting them across three people doesn't make the question easier. It makes it unanswerable, because each person is optimising a third of it.

When one person holds all three, the store page and the onboarding and the pricing and the ad all come from the same understanding of the customer. There's no translation, because there's no one to translate to. Decisions take minutes instead of meetings. And when something is wrong, there's one name to ask.

Product, brand and growth are one question asked three ways: what is this, who is it for, why would they choose it.

The evidence, from my own ledger

I didn't arrive at this as a theory. I arrived at it by building my own things and noticing what worked. ShotPop was designed, built, store-paged and launched by one person this week. Celeste was built, listed and marketed by one person, and has thousands of installs. The Prints Plus was rebuilt, fed and advertised by one person, and orders come from cities the family has never visited. In each case the thing that made it work was that the person writing the ad had also written the onboarding, and knew exactly which promise the product could keep.

Then I did it for other people. Fanture, a footwear brand: store, checkout, campaigns, one pair of hands. Zentika Pharma: a manufacturer's site in four languages built to win enquiries, and it does. In every case the founder got one name to call and one person who could answer 'when' and 'why'.

What it costs when three people do it

• Time. Every handoff is a meeting, a document and a wait. Three disciplines means at least three handoffs per feature.
• Fidelity. The designer's intent survives the developer's implementation about seventy percent of the time. The developer's constraints survive the marketer's copy less often than that.
• Accountability. When it's late or wrong, three people each own a third, which is the same as nobody owning it.
• Money, in the least visible way: not the salaries, but the features built and never launched, and the campaigns run for products that weren't ready.

How I actually run it

Define: scope, positioning, and what winning means

Before anything is built we agree on three things in writing: what we're building, who it's for and what 'done' means in numbers. Then a fixed price. Founders are surprised by the fixed price. I insist on it because it forces the scoping conversation that most projects skip and then pay for later.

Build: design and ship by the same hands, visibly

Design and code happen together, by me, and the founder sees a working build every week, not a deck. A build is honest in a way a deck can't be. If something is hard, the build shows it. If something is delightful, the build shows that too, and it changes what we do next.

Grow: the part builders usually hand off

Store page, launch, feeds, ads, the first iterations after real users arrive. This is where most projects are handed to someone new, who has to learn the product from a document. Here it's the same person, who has been thinking about the ad since the first scoping call.

What a week looks like, concretely

Founders ask this, so here it is. Monday is the build call: twenty minutes, the working version on screen, what shipped, what's next, what I need from them. Tuesday to Thursday I build, in blocks, with the store page or the landing page open in a second window because the copy and the interface are written together. Friday morning is numbers, whatever numbers exist yet: conversion on the page, drop-off in onboarding, the cost of the first ads. Friday afternoon is the written update, one page, no slides. The founder never has to ask 'where are we', because the answer arrived before the question.

There is no project manager, because there is nothing to manage between. There is no design review, because the design was reviewed by the person who then built it. There is no marketing brief, because the person writing the ad wrote the onboarding. What there is, every week, is a working thing and a page of honest words.

Why the price is fixed, and why founders end up liking it

A fixed price puts the risk of scope on me, which is exactly where it should be, because I'm the one who can see the scope. It forces the definition conversation up front, which is the conversation most projects avoid and then pay for in month three. And it aligns the incentive with shipping: I'm paid for the outcome, not the hours, so I have every reason to make the outcome arrive.

The founders who start out wary of it are usually the ones who've been billed hourly for a thing that never launched. By the second week, when the build is on screen and the price hasn't moved, the wariness goes away. Nobody has ever asked to switch back.

What I say no to

• Anything where the founder wants a team managed rather than a product built. That's a different job and I'm not the right person for it.
• Products whose growth plan is 'go viral'. Growth is a system, and if we can't describe it in a sentence at the scoping call, we can't build it.
• Rebuilds of things that work. If it works, the money is better spent on the next thing.
• More than a few founders a year. The model only works if every founder gets the whole person.

The limits, honestly

One person doesn't scale past a certain size, and shouldn't pretend to. When a product needs a team, the job of the one person is to have built the thing clearly enough that a team can take it without a translation layer. Every product I've built is documented for the person who comes after me. The point isn't that one person should do it forever. The point is that the first version, the one that decides whether there's a company, should come from one understanding.

If that sounds like the way you'd want your thing built, the brief form on the front page is the start. Two founder slots per quarter. Reply within a working day.

Written by

Jay Butani

Product builder from Surat. Ships his own apps, runs live broadcasts, and takes on a few founders a year for product, brand and growth. hey@jaybutani.com