Team First, Customer Second, Product Third
A fixed priority order for founders: build the team before the product, because magical teams are what produce magical products.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 90%
Paul English wrote this priority order into Kayak's culture plan on day one in 2004 and has repeated it across all six companies he sold. The claim is causal, not sentimental: if you become a phenomenal recruiter, assemble an amazing team, and then lead that team so there is no stress in the office, the team produces a magical product, and a profitable business is usually findable inside a magical product. He is explicit that people should work hard and have fun and crank things out without stressing each other out. He credits the strength of Kayak's tech leadership bench for letting him leave after ten years without hurting the company, because he had people who could do UI, product, and architecture without him. The inversion he warns against is the founder who leads with the product and treats the team as a means to it.
Origin
English put it in the Kayak culture plan on day one in 2004 and has restated it as the operating order for every company he has started since.
Core principles
- 01Team quality is upstream of product quality, not downstream of it
- 02Become a student of recruiting the way you would study any craft
- 03A hard-working team should not be a stressed team
- 04Magical teams create magical products
- 05A magical product almost always has a profitable business hiding in it
How to run it
- 1
Write the order down as a culture plan on day one
Before the first line of product code, commit the priority order to a written culture plan the whole company can read. English did this at Kayak's founding so the order was a stated rule rather than a retrospective story.
Pro tip State it as an order of operations, not a values poster, so it can actually settle arguments about where time goes.
- 2
Become a genuine student of recruiting
Treat recruiting as a skill to be studied, not a chore to be delegated. Read the books, listen to the podcasts, and learn from people who are further along. English says he is still trying to get a little bit better with each company.
Watch out Delegating recruiting to a recruiter before you are good at it means you never learn the judgment that makes the first five hires right.
- 3
Recruit the amazing team before scaling the product
Spend the founder hours on assembling people rather than on the feature list. The bet is that a strong enough team will find the product, whereas a strong product with a weak team will decay.
- 4
Lead so the office has no stress in it
Once the team exists, the job flips to leadership: keep people working hard and shipping while removing the interpersonal stress people put on each other. English names low-stress high-output as the specific condition that makes a team magical.
- 5
Let the magical team produce the product, then find the business
Only at this point does product take the wheel. English's claim is that a magical product is nearly always monetizable, so the business model question is the last one to solve, not the first.
- 6
Test the team by whether you could leave
Use founder-replaceability as the scoreboard. English left Kayak after ten years because his tech leadership could cover UI, product, and architecture, which he treated as proof the team was actually strong.
Pro tip If the answer is no, that is a recruiting gap, not a loyalty win.
In the wild
English and co-founder Steve Hafner put the team-customer-product order into Kayak's culture plan when the company was founded. Over ten years he built a tech leadership bench deep enough to own UI, product, and architecture independently of him.
→ Kayak went public in 2012 and was sold to Priceline for roughly two billion dollars, and English was able to leave shortly after without damaging the company because the team could run it.
English applied the same order at Boston Light, Intermute, GetHuman, Kayak, Moonbeam, and Lola, saying he stated it for each company and tried to get a little better at the recruiting half each time.
→ Six companies sold in a row, with English now running Boston Venture Studio and nine apps under development on the same operating order.
Common mistakes
Putting product first and calling the team a resource
Founders who lead with the product treat hiring as staffing rather than as the actual work. English argues the order runs the other way: the team is what generates the product, so inverting the order caps how good the product can get.
Confusing a hard-working team with a stressed team
English specifically calls for people cranking stuff out without stressing each other out. Teams that mistake internal friction for intensity burn the exact people the framework depends on retaining.
Never testing whether the company survives your absence
A founder who remains structurally necessary has not built the bench the framework calls for. Without that test, the priority order stays a slogan and the team weakness only surfaces at the worst moment.
Is it for you?
Best for
Founders and CTOs starting a new company who are deciding where to spend their own hours in year one
Not ideal for
Solo indie builders shipping a one-person tool, or anyone in a pure execution role with no hiring authority
From the transcript
“I always said for each of my companies, it's team first, customer second, product third. I said it for Kayak on day one when we…”
“I always say magical teams create magical products. And then usually if you can create a magical product, you can find a profitable business there.”
“If you focus on becoming a phenomenal recruiter and really becoming a student of recruiting, like read all the books, listen to the podcasts, learn…”
From the episode
Paul English: How He Built And Sold 6 Companies And Why He Believes Irritation Becomes Inspiration
Paul English