The tests to run before a marketplace opens its next city or category
Members of the Growth work group test whether market one holds up without subsidies or founders, then argue over how to rank the next city and when a new category is a new company.
Updated
Expand when the home market keeps its service quality after incentives come down, a new manager can run the launch playbook without the founders, and the team knows whether the channel that built demand starts warm or cold in the next market. Then run market two as an experiment with its bars and its team written down first.
- Pull the subsidies and see what holds. Adriel Frederick's main test from Lyft is whether pickup times, reliability and prices hold once driver incentives and rider discounts come down. He would look at the tail, meaning bad hours, neighborhoods and weather, and wants utilization inside a band, with drivers busy enough to keep logging on and enough slack that a rider in a quiet area still gets a car at a normal price. He would also want positive contribution per transaction at normal pricing before expanding.
- Expand only once the launch is written down. Casey Winters says Grubhub ran only in Lincoln Park in Chicago for a while, and its launches followed a written playbook: two salespeople with a contract quota, then live listings, online ordering, AdWords and SEO pages. If a team can't write down which actions unlock liquidity and who owns each one, he would launch one market at a time. His checklist ends with the second market reaching liquidity on the playbook without founders running it.
- Rank cities by demand that shows up unprompted. Gustaf Alströmer would track one metric that needs both sides, such as trips or nights booked, and check whether it keeps growing with the ads off. He would rank targets by searches, signups and waitlist entries from outside the core market. Later he adds the cost side, including the regulatory fight Adriel raises and local product changes such as payments or ID checks, and puts each candidate city on one sheet.
- Check whether the channel and its pages carry over. Luc Levesque would name the one channel that made market one work and check whether it starts warm or cold in the next market. Domain authority travels, he says, but page content doesn't, and a city page with no reviews ranks badly and converts worse. Casey's answer is that Thumbtack and early Grubhub filled pages before supply signed up, with lead forms routed by hand and menus collected from every restaurant they could find.
- Treat a new category as a possible new company. Brian Balfour is more cautious about categories than cities. Two orders a day per restaurant says nothing about whether florists or caterers will stick, so before launching he would check that the core use case and supply behavior stay the same and that market one's channel works for the new category. If the supply behaves differently, Gustaf would score that category as a new company.
- Write down market two's bars and staffing before launch. Adriel would run market two as an experiment, with its criteria and the response to a miss decided in advance, after a Lyft pricing system his team held onto too long. Brian adds the opposite failure, killing market two after under-resourcing it, for example by sharing a team with market one. He would name a dedicated team and budget next to the bars, and add resources quickly once the early bars are hit.
Ask a follow-up
Growth
Frequently Asked Questions
How do you choose a startup's first growth channel?
Pick a channel the product can feed, test it with one narrow segment on a set budget and date, and judge it by how many users reach value and come back.
What should a founder check first when growth stalls?
That the data is right, then cohort retention split by segment and channel. If curves trend toward zero in every slice, fix the product before spending more on acquisition.
How do you tell a growth problem from a product problem?
Bring in a small batch of users from one clean channel and read their cohorts. If they activate and return but there aren't many, it's distribution. If they leave within the first week, product owns the fix.
What moves activation in a new user's first few days?
Find where users drop, then match the lever: pre-answer setup for users who stall, make the first action an earned win for users who feel nothing, and bring back users who got value.
Who should own acquisition and retention, growth or marketing?
Most members would split near signup, with marketing on channels and the promise and growth on the path to first value. The line still has to follow the growth model, and both teams judge channels by the cohorts that stay.
Should a growth team report to product or marketing?
Wherever the biggest lever is. For most product-led companies that is product, next to core rather than inside it, and once paid spend matters too, one growth leader owns acquisition and activation.
Which lifecycle emails should a team build first?
The ones aimed at the steepest drop on the retention curve, usually the activation email. Depth and renewal emails come next, and win-back to fully churned users comes last.
How do you bring back signups who went quiet?
Watch a few try the next step and fix where they stall, then test the message with and without the fix against a holdout, and count retained use rather than opens.
When should a product-led company add sales?
A founder can start working accounts where usage is spreading and retaining. A sales team follows once deals need security reviews and procurement that self-serve can't handle.
Which self-serve accounts should a sales rep call?
Ones big enough to pay for a rep's time, with use spreading inside the company and a need self-serve can't meet. Hold some flagged accounts back to check that sales added value.
Which early action should count as activation?
Use two measures: an early action onboarding can move as the team's operating metric, and a later repeat action to check that those users came back. Randomize the onboarding change so motivated users don't skew the read.
What makes a good north star metric for an early product?
A retention measure built from how often the problem occurs, the action that solves it and the user it describes, with activation as an input. Drop it if the team can raise it without users getting more value.
Should a new marketplace build supply or demand first?
Whichever side gets a buyer to a completed transaction while giving the supplier a reason to stay. Start in one narrow market and track matches, supplier earnings and repeat buyers.
How should you test a landing page?
Show visitors what they searched for before the ask, start with the page's first clear funnel drop, and count activated users per visitor alongside signups.
Should a startup with a few dozen users stop acquisition?
Stop broad acquisition but keep a small hand-picked flow from one segment, onboard those users live, and count only return visits nobody prompted.
How does a B2B startup find its first paying customers?
Have founders sell by hand to one narrow buyer, starting with warm intros and asking for payment early. Then check who actually paid, and at what price, before choosing a channel to scale.


