How founders win their first ten B2B customers
Members of the Growth work group trace first customers to the founder's network and one narrow buyer, then debate free pilots, launches and what proves the product works without the founder.
Updated
Most first B2B customers come from founders selling by hand to one narrow buyer, starting with warm intros and asking for payment early. The first ten deals then show who actually buys, at what price, and which channel can reach the next ones.
- Check whether one user gets value alone. Lauryn Motamedi, citing a post she reshared, says self-serve only really works when one or two people get a lot of value alone, and otherwise sales is usually the better bet. She finds most B2B founders reach for a self-serve funnel too early. A startup's first 5 to 10 customers look more like an enterprise evaluation, with a founder on calls setting the product up and learning the workflow, so warm intros and the founder's network come first.
- Pick one buyer you can turn into a list. Hila Qu would start with 1 to 3 segment hypotheses, compare early wins with losses on velocity, close rate, ACV and retention, and turn the shared traits into lists in Clay, Apollo or LinkedIn. If the list can't be sourced, the ICP isn't actionable yet. Brian Balfour suggests looking at the adjacent buyer. HubSpot Sales' early adopters were existing HubSpot marketing customers whose marketing leader influenced the sales team.
- Ask for payment from the first customer. Gustaf Alströmer was the first paying customer of one founder's first product, at $20, and would have founders ask their network, batchmates and former colleagues to pay instead of offering a free pilot. A free offer can work when it is a scoped diagnostic, as in a YC launch post that offered about 100 test calls. Hila adds that AI products often run 20 to 60% gross margins, so an open-ended free pilot costs real inference money.
- Sell where the founders know the pain. Gustaf points to Coperniq, which makes software for solar installers and had several leading installers as customers while still in the batch. In concentrated industries he would push founders to land one recognized operator early, even at a discount. For hardware, he says a first customer ordering a second unit is the clearest proof the product works after the founder steps back.
- Treat a stalled self-serve account as a paywall bug. From Dropbox trial conversion, Lauryn would have the founder find out what blocked a stalled account, such as a missing payment method, a buyer who isn't the user, or a plan that doesn't fit how a team trials the product. In team products, she says, an account with five active teammates and no card is often a better lead than one solo user with a card. Hila would pair interviews with usage data, as GitLab did, to see which behavior comes before payment.
- Write down who paid and what they paid. Brian says HubSpot Sales found paying segments it never targeted, such as small business owners, recruiters and marketers, and its $25-per-user tier was too low to pay for content and inside sales. He would record who the first 10 customers are and what they paid before scaling. Casey Winters would pull the founder off a few accounts to see whether usage and renewals hold, and Lauryn would track accounts still paying 60 to 90 days later.
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.
When can a marketplace copy its first city?
When service holds after subsidies come down, a new manager can run the launch playbook without the founders, and the team knows whether the channel behind market one's demand starts warm or cold in the next market.
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.
