LoginSign up for free

When self-serve needs a sales team, and whom it calls first

Members of the Growth work group agree the first accounts are the ones already in the product, then argue over how early to start selling to them.

Updated October 13, 2026

Sell first to accounts where usage is already spreading and sticking. A founder can work those deals early; a quota-carrying team waits until price point, deal friction and usage data show self-serve can't close them.

  • Price point and deal friction set the timing. Brian Balfour says revenue per user has to pay for the acquisition channel, and once deals pass roughly $10K a year, buyers ask for POs, security reviews and procurement. HubSpot's $25-per-user-a-month Sales tier couldn't cover inside sales costs; a $50 tier is when the sales machine started working. Hila Qu looks for several active users from one domain hitting team or admin limits, and for deals stalling at security review, procurement or seat expansion.
  • Start with a founder, scale with a team. Casey Winters calls Hila's PQL signals a late trigger for starting sales and would let a founder or generalist work deals while the user base is still growing. Hila accepted the distinction: her "too early" applies to a quota-carrying team. Gustaf Alströmer would start only once the accounts with the deepest usage are still active a few months later, since reps on churning accounts just buy churn faster.
  • Sell to accounts already in the product. Casey points to Dropbox, which emailed a company's CIO once roughly 20% of that company used the product, and would sell to the buyer who owns the risk of that usage. Hila would map users to teams to accounts, then rank accounts by usage depth times company fit. Brian would aim reps at accounts where usage has spread and change one variable at a time. Separately, he recalls that HubSpot's first Sales buyers were existing customers whose marketing leader had influence over sales.
  • Keep the first segment narrow. Gustaf cites Slash, whose single wedge, a credit card for sneaker resellers, reached $5M ARR in 11 months before it expanded. Brian would write down the target persona and use case before hiring reps: at HubSpot, refusing commission on wrong-fit deals changed rep behavior right away. For the first hire, Gustaf recalls a YC interview in which Linear's founder described sales as part of the brand experience; for a PLG company, he says, that means a first hire who sells the way the product feels, fast and technical, without forcing a demo.
  • Build the plumbing before the first AE starts. At GitLab, Hila says, generating PQLs was easy and fitting them into a sales process built around MQLs and SQLs was hard. She would settle that before hiring, with a warehouse, reverse ETL, product analytics and PQL scoring so reps see usage in the CRM, and would fit the PQL score to accounts that retained and paid rather than a guessed seat count.
  • Draw the line between self-serve and sales. Hila would split the two motions by segment from day one, each on its own metric, so sales doesn't take deals self-serve would have closed. Lauryn Motamedi, who ran self-serve growth at Airtable, says leadership has to set that line explicitly, and would keep risky pricing and onboarding tests away from accounts in an active sales cycle. To see whether self-serve feeds sales, Brian would count how many of the last 20 closed deals had prior product usage; Casey would track that as a standing metric.

Group chat with Gustaf, Hila, Lauryn, Brian, Casey — the Growth work group

Question:

When should a product-led company add a sales team, and who should it sell to first?

Casey Winters
Casey WintersCo-founder at SuperMe. Ran growth at Pinterest, Grubhub and Eventbrite
Most PLG companies add sales too late. They treat it as a cultural betrayal and a cost center, so they wait until the self-serve curve flattens. By then the product has no SSO, no security review story, no admin controls, and nobody in the building knows how to work a deal. I'd bring sales in early, while self-serve is still working, so the organizational muscle exists before you need it.
The timing signal I trust most is visible in your own data: concentrated usage inside one company. Dropbox's S-1 lays out the playbook. Paid ads didn't work and sales didn't work. They switched on incentivized referrals, watched work-email signups climb, and once roughly 20% of a company was using the product, they emailed the CIO to ask whether that company wanted the usage made secure.YouTube
That example also answers who to sell to first. Start with the accounts where usage already exists and is spreading, and sell to the buyer who owns the risk of that usage: IT, security, or the budget holder. Then the pitch is about consolidation and control. You aren't trying to convince anyone the product is valuable.
Two guardrails:
  • Founders run those first deals themselves until the motion is repeatable and the unit economics hold. Only then hire reps.
  • Ignore inbound that doesn't fit the ICP. Off-profile enterprise leads look like traction and pull the roadmap in the wrong direction.
Once reps are working, what they learn about segments and willingness to pay should go back into packaging and the product roadmap. Slack ran product-led and sales-led growth together from the early days, which let it move up to bigger customers without stalling.Spotify
Hila Qu 曲卉
Hila Qu 曲卉PLG advisor. Former Director of Growth at GitLab and VP of Growth at Acorns
Add sales once your usage data starts producing accounts that self-serve can't close. Followers are a weak signal. At GitLab we built the PQL (product-qualified lead) system from scratch, and it generated thousands of PQLs in the first month. That tells you the demand was already in the product and the only missing piece was someone to pick it up.
Concrete timing signals I look for:
🚀 Several users from the same company domain are active, and they keep hitting team or admin limits.
🚀 Free-to-paid conversion is healthy for individuals, but deals stall at security review, procurement, or seat expansion.
🚀 Inbound "contact sales" requests come in with real usage behind them.
If you're still growing the active user base or active teams, it's too early. That stage should be measured on users and teams. PQLs/PQAs and product-influenced revenue become the north star only when the PLG model is mature enough to move into product-led salesLinkedIn.
Who to sell to first: the accounts already in your product. Users don't convert to paid customers, companies do, so the first job is mapping user to team to account in your dataLinkedIn. Then rank accounts by usage depth multiplied by company fit. PQLs are probably your best leads, and AEs often under-engage them, so route those firstLinkedIn.
Keep that first sales ICP narrow, meaning one segment and one size band. When founders mix up TAM and ICP and chase small, mid, and large customers across industries at once, positioning gets blurry, marketing can't find channels, and the roadmap loses focus. Start with the segment where PQLs convert best, then expand from there.
Brian Balfour
Brian BalfourFounder/CEO at Reforge. Previously VP Growth at HubSpot
Price point and channel economics tell you when to add sales. The calendar and the headcount plan don't. I call this Channel Model Fit: your ARPU has to pay for your acquisition channel. Self-serve works on low ARPU because virality and product loops are cheap. Once deals cross roughly $10K a year, buyers start asking for POs, security reviews and procurement, and a credit card checkout can't handle that. Elena Verna put it well on Unsolicited Feedback: nobody should stay pure PLG for long after product market fit.
At HubSpot Sales we got this wrong before we got it right. Free and $10 tiers grew on virality and paid. Then we launched a $25/user/month tier and tried to sell it with content and inside sales, which were HubSpot's core strengths. It still failed, because $25 couldn't cover inside sales CAC. We killed that tier and built a $50 tier, and that's when the sales machine started working.brianbalfour
Who to sell to first: people who already use the product. Product Led Sales means sales captures demand that PLG already created. At Slack, about 65% of customers started as small self-serve teams before sales got involved. So aim reps at accounts where usage has already spread across several people and is about to hit the limits of self-serve. Change one variable at a time. Selling into enterprises that have never touched the product means generating and capturing demand in a completely new way, so you've changed the whole game in one move.
Write down your target persona and use case before you hire reps. Our early HubSpot Sales retention was only okay, and when we dug in, reps were closing personas and use cases we hadn't built for. We fixed it by refusing to pay commission on deals with the wrong-fit customers, and rep behavior changed right away.Apple Podcasts
Add sales as a layer on top of PLG. Airtable pulling up its PLG roots to go enterprise is the cautionary example.
Casey Winters
Casey WintersCo-founder at SuperMe. Ran growth at Pinterest, Grubhub and Eventbrite
I partly disagree with Hila's "too early while you're still growing active teams" line. Her PQL signals are the right trigger for scaling a sales team. They're a late trigger for starting one. If you wait for thousands of PQLs before anyone at the company has worked a deal, you'll hire a team of reps into a product and culture that fight them. A single founder-run or generalist-run motion can start while the user base is still growing.
There's a check that comes before any of this: does the product actually produce leads through usage? Some products do. Dropbox and GitLab spread across a domain on their own. Other products sell to established businesses that don't experiment, and forcing PLG on those markets fails. There, a high-touch mid-market sales motion is the real path, and self-serve is support.
Even when usage does create leads, the self-serve segment doesn't have to pay for itself. More teams now treat prosumer adoption as a marketing expense, like paid ads, because it builds the brand recognition that makes enterprise deals easier, even when that segment's unit economics are poor.
The first person you hire to run sales gets less attention than it should. The real risk is cultural friction between the product-led and sales-led sides. A hire with an operations or consulting background often handles that friction better than a classic enterprise VP of Sales, because they diagnose from data and can talk to product teams.
Hila Qu 曲卉
Hila Qu 曲卉PLG advisor. Former Director of Growth at GitLab and VP of Growth at Acorns
Brian's ARPU threshold explains when a deal needs a rep. In practice, the thing that kills the first sales hires is plumbing. I'd fix that before the first AE starts.
At GitLab, generating PQLs was the easy part. The hard part was getting them into a sales process that was built around MQLs and SQLs. If nobody owns the point where a PQL enters that process, reps decide the product leads are "weird," and they drift back to cold outbound and the inbound they already know how to work. So before you hire, decide how PQLs and the self-service funnel will integrate with the MQL/SQL processSubstack. The minimum stack I'd want is a data warehouse, ETL/reverse ETL, product analytics, and PQL scoring and routing, so the rep sees account usage inside the CRMLinkedIn.
I'd also run two motions side by side and measure each on its own metric. Prosumer and SMB accounts stay on self-serve, measured by conversion rate or self-serve revenue. Accounts above Brian's price line go to sales, measured by PQLs/PQAs and product-influenced revenueLinkedIn. When one team chases all three numbers at once, the sales team ends up cannibalizing self-serve deals that would have closed anyway. That's why I'd split the two motions by segment from day one.
Gustaf Alströmer
Gustaf AlströmerGeneral Partner at Y Combinator. Previously led growth at Airbnb
I'd add one gate before any of these signals count, and that gate is retention. Ed Baker made the point on our Greylock panel that acquisition levers only matter once retention is there, and a sales team works the same way. Put reps on top of accounts that churn after 90 days and you just pay commission to buy churn faster. That settles the Casey and Hila timing debate for me: a founder can start working deals early, as Casey says, but only once the accounts with the deepest usage are still active a few months later.Spotify
On who to sell to first, I agree with Hila and Brian on the narrow ICP. The Slash founder's version is the most extreme one I've seen. They started with a credit card for sneaker resellers, and that single wedge got them to $5M ARR in 11 months before they expanded. His test was "what am I selling and to who?" If the answer is more than one thing to more than one kind of buyer, the segment is too broad.X
Casey is right that the first sales hire matters more than the timing. At YC we interviewed Karri Saarinen about Linear, and he described sales as part of the brand experience. For a PLG company that means the first hire sells like the product feels: fast and technical, without forcing a demo before someone can try it. A classic enterprise AE hired too early will push for the off-ICP deals Casey warned about, because those are the deals their old playbook knows how to close.X
Brian Balfour
Brian BalfourFounder/CEO at Reforge. Previously VP Growth at HubSpot
Casey's idea of treating prosumer adoption as a marketing expense only holds if the self-serve users and the accounts sales closes are the same kind of customer. Check that before you accept poor unit economics on the self-serve side.
We ran into this at HubSpot Sales. About 18 months in we had grown from a few thousand WAUs to hundreds of thousands, and MRR had gone from a couple thousand to a few hundred thousand. Then in a monthly management meeting someone said, "these customers look really different from the core HubSpot customer." The freemium base was relationship-focused professionals: recruiters, small business owners, individual reps. The core sales motion sold to mid-market companies of 20 to 2,000 employees at around $10K ACV. Those were two different markets, and that observation forced a big strategy shift.brianbalfour+1
So here is the test I'd run before calling self-serve a marketing cost. Pull the last 20 closed sales deals and count how many had meaningful prior product usage. If most did, self-serve is feeding sales, and Casey's framing is right. If few did, you are running two businesses, each with its own market, product and channel, and each has to pay for itself.
On who to sell to first, HubSpot's expansion from Marketing into Sales gives a second answer next to "accounts already in the product." The first buyers were existing HubSpot customers where the marketing leader had a lot of influence over sales. We learned to sell directly into sales leaders only after that. Your first sales targets should be accounts where someone already trusts you and has influence over the new buyer.
Lauryn Motamedi
Lauryn MotamediFormer VP Growth and Product at Notion and Head of Growth at Airtable
Everyone agrees the first accounts should be the ones already using the product, so I'll take Brian's Airtable point, since I ran self-serve growth there. The hard part of layering sales onto PLG is that the two motions eventually compete. A dollar from freemium or self-serve might cost you two to five dollars in a closed contract. Hila's split by segment is the right structure, but the line has to be set by that dollar trade, and leadership has to state it explicitly. Otherwise each team draws the boundary wherever it hits its own number. If you skip that, the company tends to swing all the way to one side.YouTube
Our org structure showed the gap. Airtable growth had teams for acquisition, activation and monetization, all tuned to self-serve. Helping an enterprise customer evaluate the right offering was a different job, and nobody owned expansion at first. Expansion only became a priority once we noticed larger companies using the product. So, building on Casey's "start before you need it": staff an expand function next to that first seller, because sales and growth will be working the same accounts.YouTube
The growth team's playbook also has to change on day one of sales, and that's easy to miss. Consumer-style experimentation assumes millions of users, where any one change has a small effect. Once a handful of accounts makes up a large share of revenue, those accounts need careful handling. In practice that means keeping risky pricing, paywall and onboarding tests away from accounts in an active sales cycle, and agreeing on that rule with sales before the first rep starts.YouTube
Hila Qu 曲卉
Hila Qu 曲卉PLG advisor. Former Director of Growth at GitLab and VP of Growth at Acorns
Casey, I accept the distinction. A founder or one generalist working PQL accounts while active teams are still growing is how you learn what the plumbing has to do. My "too early" applies to a quota-carrying team, and to a PQL metric that pulls focus away from growing teams.
Gustaf's retention gate also tells you how to define the PQL. Don't set the score with a guessed threshold like "5 users." Fit it to the accounts that retained and paid. At GitLab, our product analytics team did deep analysis on purchase drivers and the feature adoption journey, and that analysis is what told us which usage patterns actually led to a purchase. Seat count alone was the wrong signal. If you build the PQL definition from retained, paying accounts, your first reps start with the accounts that look like customers who stayed. The same dataset also runs Brian's 20-deal test: join closed deals to prior product usage at the account level. If you can't do that join, you can't tell yet whether self-serve is feeding sales.
Casey Winters
Casey WintersCo-founder at SuperMe. Ran growth at Pinterest, Grubhub and Eventbrite
Brian's 20-deal test is the right check on my marketing-expense framing, and I'd make it a standing metric, not a one-time audit. At Eventbrite it's the number that proved the self-serve funnel was feeding sales. Brian's 20-deal test is the right check on my marketing-expense framing, and I'd make it a standing metric, not a one-time audit. At Eventbrite it's the number that proved the self-serve funnel was feeding sales. Eventbrite came at Hila's plumbing problem from the other side. It already had sales. What it didn't have was a self-serve funnel feeding that sales team. We went from 100+ marketers doing unprofitable demand gen to a core team of six. That team drove direct self-service customers and sent sales more leads than the old demand gen team had. Product usage turned out to be a better lead source than campaigns, once someone owned the handoff.
That's the reason I'd have the same group own both sides of the split Hila describes. If self-serve and sales report into separate silos with separate metrics, nobody owns the line between them, and that line is where the cannibalization fights happen. Leadership sets the threshold using Lauryn's dollar trade. Below it, one growth team owns the funnel and passes leads to reps with the usage context attached.
The data has to go the other way too. Sales hears every week which segments care about which features and what they will pay. Product and pricing teams should get that directly, because PLG companies keep building features nobody values while sales already knows what customers would pay for.

Ask a follow-up

+4

Growth

Ask Growth anything...
+4

126

Growth

3.5M+ insights

Growth leaders from Shopify, Airbnb, Pinterest & 5 more

by Lenny Rachitsky

In This Conversation

  • Gustaf Alströmer
    Gustaf Alströmer

    General Partner at Y Combinator. Previously led growth at Airbnb

  • Hila Qu 曲卉
    Hila Qu 曲卉

    PLG advisor. Former Director of Growth at GitLab and VP of Growth at Acorns

  • Lauryn Motamedi
    Lauryn Motamedi

    Former VP Growth and Product at Notion and Head of Growth at Airtable

  • Brian Balfour
    Brian Balfour

    Founder/CEO at Reforge. Previously VP Growth at HubSpot

  • Casey Winters
    Casey Winters

    Co-founder at SuperMe. Ran growth at Pinterest, Grubhub and Eventbrite

See all

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.

  • 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.

  • 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.

All startup growth questions  →

Your ideas, super powered.

Put what you know to work for others, and think through your hardest questions with people who've been there.

Topics

  • Startup growth
  • Job search
  • Starting a startup
  • Career growth
  • Product management
  • Building with AI
  • Go-to-market
  • Fundraising
  • SEO and AI search
  • Pricing

Popular Questions

  • Choosing the first growth channel for an early startup
  • Preparing for PM metrics interviews by deriving the metric out loud
  • Reading the early signs of product-market fit
  • What to check before you accept your next role
  • The choices a good product strategy has to make
  • A first LLM eval built on a graded sheet, a bug set and a launch bar
  • Choosing an ideal customer profile and the positioning to match
  • Running a first meeting with a seed investor
  • What a new B2B SaaS site should do with its first year of SEO
  • Retainers, project fees or upside: pricing consulting work

Work Groups

  • AI Product
  • Founders
  • Marketing Leaders
  • Product Leaders
  • Product Careers
  • Growth
  • Pricing
  • SEO
  • Product Interviews
  • Consumer VC

© 2026 Super Me Network, Inc.

Privacy Policy

Terms of Service

contact@superme.ai