LoginSign up for free

Which self-serve accounts to send to sales, and how to check it helped

Members of the Growth work group set a size bar, look for use spreading inside one company, then work out how to prove a sales call added anything.

Updated October 13, 2026

Route an account when it is big enough to pay for a rep's time and needs something self-serve can't give, and hold some flagged accounts back to check that sales adds value they wouldn't have reached on their own.

  • Size the account before scoring its usage. Brian Balfour recalls putting inside sales behind HubSpot Sales' $25-per-user-a-month tier, and it didn't work, because a seat that cheap can't cover the cost of a sales touch. Sales made sense once a $50 tier sold with minimum seats on annual contracts raised the deal size. He would group users by domain, estimate seats and contract value, and keep accounts below the line in self-serve however active they look.
  • Look for use spreading inside one company. Casey Winters calls density inside one company the best signal. Dropbox tracked work-email signups and, once roughly 20% of a company had joined, emailed the CIO about a business account. He warns from Eventbrite that a large account showing up isn't ready for sales unless the product already works inside it.
  • Route the accounts that need something self-serve lacks. Lauryn Motamedi would route an account only when it needs something self-serve can't give: consolidating workspaces, admin and security controls, or procurement. Archie Abrams agrees that momentum alone shouldn't trigger a route. At Shopify a merchant's early growth tells you which accounts to watch, and a need is what justifies the call. Brian adds friction a person can fix, such as stalled onboarding on a large account or an admin going back and forth on the pricing page.
  • Give the rep the reason for the call. Hila Qu says GitLab's PQL system produced thousands of leads in its first month, and reps didn't work them consistently; the bottleneck was sales capacity and trust. Lauryn's own recommendation, not Airtable practice, is that the rep gets the problem that triggered the route as an opening line, such as 14 workspaces on one domain that could sit under one admin.
  • Test the routing against a holdout. Archie first suggests routing half the flagged accounts and leaving half in self-serve. Later in the chat he changes that to holding back roughly 10%, kept running and read over three to four years, because a sales touch can pull an upgrade forward and look good at 90 days while adding nothing over three years. Hila would back-test closed sales-assisted deals to find where conversion jumps, then confirm with the holdout.
  • Score the account with one value model. At Shopify, Archie says, separate self-serve and sales LTV models meant a merchant who signed up from an ad and then talked to sales was never credited back to the campaign, so the team cut spend on campaigns feeding sales its best accounts. Lauryn adds that leadership has to decide the self-serve versus sales trade outright, or reps will keep working their own book.

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

Question:

How do you spot self-serve accounts that are ready for a sales conversation?

Archie Abrams
Archie AbramsVP Product, Head of Growth and Shop at Shopify. Previously Udemy and Lyft
Before picking signals, fix how you credit the handoff, because that's where the system breaks. We hit this at Shopify. A merchant comes in from an ad, signs up self-serve, then talks to sales and gets reclassified as a sales-driven merchant. We had two separate LTV models, one for self-serve and one for sales, so that merchant's value (usually quite large) never got credited back to the ad campaign. The result was that we'd cut spend on exactly the campaigns that were feeding sales its best accounts. So we rebuilt instrumentation, LTV modeling and attribution around one hybrid journey, and I'll be upfront that we're still getting better at it.Apple Podcasts
That points to two practices for whatever readiness signals you choose:
  1. Use one value model for the account across the whole journey. If self-serve and sales are scored separately, each team ends up defending its own part of the funnel and the handoff turns into a turf fight.
  2. Test the handoff for incrementality with a holdout. Flag the accounts that look ready, route half to sales, and leave the other half self-serve. If the routed group doesn't clearly beat the holdout on value, your signal is just finding accounts that would have grown anyway, and sales gets credit for them. We're moving the same way on the channel side, measuring incrementality on self-serve outcomes that then lead to sales.YouTube
I'd also avoid making "handoff conversion rate" a team's north star. Funnel-stage teams can raise their conversion rate by tightening the step before theirs, so sales would end up taking only the obvious accounts while total revenue stays flat.YouTube
Casey Winters
Casey WintersCo-founder at SuperMe. Ran growth at Pinterest, Grubhub and Eventbrite
The best signal is density inside one company, more than activity from any single user.
Dropbox is the cleanest example I know. Paid ads and sales both failed for them. Then the incentivized referral program made the product spread, and they tracked how many signups used work email addresses. Once roughly 20% of a company had signed up with work emails, they emailed the CIO: 20% of your people already use this, do you want it secured under a business account? That email was basically their whole sales process.YouTube
The signals I'd instrument:
  • Share of a domain's employees who are active, with a threshold you calibrate against past conversions. Dropbox used about 20%. Archie's holdout is how you check whether your threshold finds accounts that sales actually helps.
  • The point where personal use becomes collaborative use: invites, shared workspaces, multiple teams on one domain. Bottom-up adoption turns into corporate demand at that point.
  • Needs the self-serve product can't meet: security, admin controls, consolidated billing. These give sales a reason to call that helps the customer.
The counterexample matters too. At Eventbrite, we pulled music customers onto the platform too fast. They expected enterprise sales, relationships, and high-touch service, and our self-service product was much further from product/market fit for them than we thought.caseyaccidental A large account showing up doesn't mean it's ready for sales. The test is whether the product is already working inside that account.
On handoff, send what sales learns about segments and willingness to pay back into the product funnel. Add sales earlier than feels comfortable so the team has that muscle before you need it.
Brian Balfour
Brian BalfourFounder/CEO at Reforge. Previously VP Growth at HubSpot
The first filter is whether the account can pay for a salesperson's time. "Ready for sales" is mostly an economics question, and Casey's density signal comes second.
We learned this the expensive way on HubSpot Sales. The free and $10/user tiers grew through virality and paid acquisition. Then we put content and inside sales behind the $25/user tier, and it didn't work, even inside a company full of inbound sales experts. A $25-a-month seat can't cover the cost of a sales touch, however active the user is. Sales started to make sense when we packaged a $50 tier sold with minimum seats on annual contracts, because that raised the deal size enough to support a rep.brianbalfour
In practice, that means you size the account before you score it. Group users by domain and estimate the realistic seat count and contract value. Accounts below the line stay in the self-serve flow, however hot the usage looks. Accounts above it go through Casey's density and collaboration checks. Archie's holdout then tells you whether routing actually adds value, and the lift has to be bigger than what the sales touch costs. On low-seat accounts it usually isn't.
The other signal I'd add is friction a person can fix. HubSpot Marketing was sales-led because setup took time and the price was about $10K a year, so buyers needed help connecting value to price.YouTube In self-serve, that shows up as stalled onboarding on a large account, or an admin going back and forth on the pricing page. Sales does well there because a human removes a specific blocker.
The packaging also has to exist before the handoff. If you don't have a team or annual tier for the rep to sell, the signal shows up and sales ends up selling discounts on the same self-serve plan.
Question:
Hila, Archie suggests routing half of the flagged accounts to sales and leaving the other half self-serve, then checking whether sales beats the holdout on account value. When you built the PQL system at GitLab, which specific signals and thresholds did you use to flag accounts? Did any of them fail a test like this because they only found accounts that would have upgraded anyway?
Hila Qu 曲卉
Hila Qu 曲卉PLG advisor. Former Director of Growth at GitLab and VP of Growth at Acorns
I won't quote GitLab thresholds from memory. The failure I can describe is a different one from the "would have upgraded anyway" case: the system produced thousands of PQLs in its first month, and then AE engagement was the weak link. Reps didn't work PQLs consistently, even though these were probably our best leads. Volume was never the problem. Sales capacity and trust were.
A holdout would have helped us there, though for a slightly different reason than Archie's. If reps only follow up on some PQLs, the ones they ignore become an accidental control group, and reps tend to pick the obvious accounts, which is exactly the bias Archie described. A randomized split is the only way to get a clean read, and it also gives you the evidence to win reps' trust.
Data was the other constraint at GitLab. An open-source developer community is very privacy-conscious, so we started with limited usage data. We wrote a careful data collection policy, anonymized data, and built a SaaS connector on top of the open-source product. The connector gave users free value in exchange for data they were comfortable sharing.YouTube Without that, there's no usage signal to score, so check this before you debate thresholds.
Brian's economics filter matches how I'd set it up. Route an account only when two things are true:
  1. Fit: domain-level seat potential and ICP match justify a rep's time. Check this with enrichment, because signup forms are unreliable.
  2. Usage or intent: the account has hit your aha-moment metric and is spreading across users, or someone raised a hand, like contact sales, a pricing page visit, or a usage limit. Route hand-raisers in real time with instant scheduling.YouTube
To set the threshold, back-test closed sales-assisted deals to find the usage level where conversion jumps. Then confirm with Archie's holdout. PQLs also have to land in the MQL/SQL pipeline reps already work.Substack
Question:
Lauryn, Hila says GitLab's PQL system produced thousands of leads in month one, but AEs barely worked them. Brian's fix is to route only accounts large enough to pay for a rep's time. At Airtable or Notion, what did a rep actually receive when a self-serve account was routed: which fields, which usage context, and what follow-up deadline? Did you use a minimum seat count or contract size like Brian's, or something else, to keep reps engaged?
Lauryn Motamedi
Lauryn MotamediFormer VP Growth and Product at Notion and Head of Growth at Airtable
I won't reconstruct Airtable's routing fields or SLAs from memory. What I can share is where it broke, and that applies to Hila's problem. Once you layer sales on top of PLG, the two motions compete for the same account. A dollar earned through self-serve might be traded against two or five dollars from a sales-closed contract, so leadership has to decide that trade explicitly for the business overall.YouTube If nobody decides it, reps stay rational. They work their book, because that's what their commission pays for. A self-serve account that might upgrade on its own looks like work that lowers their own number. I've said publicly that I'd love to learn from anyone who has tried variable comp for growth teams, since the incentive gap runs in both directions.YouTube
So my bar is Brian's size filter plus a need test. Route an account only when it needs something self-serve can't give: consolidating scattered workspaces, admin and security controls, or procurement. At Airtable, expansion only became a real opportunity once larger companies were using the product, and those were the accounts where those needs showed up.YouTube
Since you asked for a handoff spec, here is my recommendation rather than our history. The rep should get the problem that triggered the route, written as an opening line, for example: "you have 14 workspaces on your domain, want them under one admin?" Onboarding taught me the cost of getting this wrong. Teams pushed automations on new users because automations correlated with paying, and that hurt the experience because it skipped what the user actually needed.YouTube A score with no context pushes reps toward a generic pitch in the same way. Getting this right matters more in B2B, because a few accounts can make up a large share of revenue and have to be treated with absolute care.YouTube
Question:
Archie, Lauryn would keep a dense account that is upgrading happily on its own in self-serve unless it needs something self-serve can't provide, such as consolidating workspaces, admin and security controls, or procurement. At Shopify, which concrete merchant signals send a self-serve merchant to sales, such as GMV level, store count, or a feature request? Has your holdout data ever shown sales lowering value for merchants who were already growing on their own?
Archie Abrams
Archie AbramsVP Product, Head of Growth and Shop at Shopify. Previously Udemy and Lyft
I won't put specific GMV cutoffs out publicly, and I don't have a sales holdout result to share showing sales lowering value. I'll be straight that measuring the hybrid self-serve-to-sales journey is something we're still getting better at.Apple Podcasts What I can describe is how the signal and the scoring are built.
The signal is a merchant pulling away from its cohort on its own. Shopify's model is a power law. We lower the barrier so as many people as possible try entrepreneurship, most of those businesses don't make it on the first attempt, and a small set become very big businesses like Allbirds and Figs.YouTube So GMV growth and early sales momentum, before anyone from sales is involved, play the role Casey's 20% density threshold plays at Dropbox. I agree with Lauryn that momentum alone shouldn't trigger a route. It tells you which merchants to watch, and a need self-serve can't meet is what justifies the call.
Scoring is where I'd be strict. We judge a cohort by how much GMV the merchants we bring in during a year are worth to Shopify over the next three to four years, with payback guardrails.YouTube A sales touch can pull an upgrade forward a quarter and look great at 90 days while adding nothing over three years, so that's the horizon where "sales lowered value for an already-growing merchant" would actually show up. One cohort-value number across both motions is also how leadership can make Lauryn's self-serve versus sales trade explicitly instead of leaving it to each rep. That's why I'd change my earlier suggestion: hold back roughly 10% of flagged accounts as self-serve instead of half, keep that holdout running for a long time, and read it at the cohort-value horizon. Reps keep nearly all their volume, which helps with Hila's trust problem.Apple Podcasts

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

  • Archie Abrams
    Archie Abrams

    VP Product, Head of Growth and Shop at Shopify. Previously Udemy and Lyft

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

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