Sales-assisted
saylz uh-SIS-ted
A buying model where customers start self-serve but get human help for larger deals. The middle ground between PLG and traditional sales.
Sales-assisted is the hybrid model. Users discover and try the product on their own (self-serve), but a salesperson helps close the deal when it gets big enough. The rep does not cold-call. They reach out to accounts already using the product.
This is the dominant model for developer tools that sell to enterprises. The developer signs up, builds something, and gets value. When the team grows or the company needs enterprise features, sales steps in. The sales rep already knows the account is active, what features they use, and what limits they are hitting.
The trigger for sales involvement varies. Some companies use a revenue threshold ($500/month in self-serve spend). Others use a usage threshold (50+ seats). Others use a feature trigger (someone requests SSO or a custom contract). The best triggers are signals that the customer is ready for a conversation, not that the company wants to force one.
Examples
A PQL triggers a sales conversation.
A company has 30 developers on Vercel's Pro plan, spending $600/month. The account activates preview deployments for 15 repos. Vercel's system flags this as a product-qualified lead (PQL). An AE reaches out: "I see your team is scaling. Want to discuss Enterprise features like SSO and priority support?"
Sales assists without blocking.
A startup using Stripe processes $50,000/month in payments. Stripe's growth team notices and offers a call to discuss volume pricing, custom reporting, and Stripe Atlas for incorporation. The call is optional. If the startup ignores it, nothing changes. They keep using Stripe.
Sales-assisted conversion at Datadog.
Datadog lets developers monitor 5 hosts for free. When a company's self-serve bill hits $2,000/month, an SDR reaches out to discuss annual contracts (with a discount). The conversation is easy because the customer already uses and trusts the product. Close rates for these deals exceed 40%.
In practice
Read more on the blog
Frequently asked questions
When should sales step in?
When the customer signals they are ready: they hit usage limits, request enterprise features, or their self-serve spend crosses a threshold (typically $500-2,000/month). Never have sales reach out before the customer has experienced value. The worst thing you can do is put a demo gate in front of a developer who wants to try the product.
How do you staff a sales-assisted motion?
Start with one AE who handles inbound PQLs. Do not hire outbound SDRs first. Your product generates the leads. The AE converts them. Add SDRs only when you have more PQLs than one AE can handle. Typical ratio: one SDR per 50-100 PQLs per month, one AE per 20-30 qualified opportunities.
Related terms
A buying experience where customers sign up, configure, and pay without talking to a salesperson. Credit card in, product out.
A go-to-market strategy where the product itself drives acquisition, conversion, and expansion through self-serve usage.
A sales approach where product usage data identifies and qualifies sales opportunities from self-serve users.
Custom pricing for large organizations, typically requiring a sales conversation. The "Contact us" plan on your pricing page.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.