The PLG Segment That Outgrew Self-Serve
Brightlane is a product-led SaaS company with 14,000 self-serve accounts and $6M ARR. Eight percent of accounts generate 70% of revenue; these are accounts above $10k annual spend. Inbound enterprise interest is about 30 accounts per month. Two sales-assist reps cover all inbound, from $2k self-serve upgrades to $150k enterprise evaluations. Self-serve conversion is 2.1%; sales-assist close rate is 28%; enterprise cycles run 120 days and implementation averages 45 days. The CEO wants to hire six enterprise AEs next quarter to 'go upmarket.' The CFO asks for a coverage model before approving headcount. Current CRM has one pipeline stage model for all deal sizes, and marketing routes every demo request to the same queue. The VP Sales says enterprise deals stall after technical validation because no one owns implementation readiness.
1. What segmentation and coverage decisions should precede the six AE hires?
Read the worked answer
Segment by revenue potential and buying behavior, not by inbound queue. The data already shows a natural break: 8% of accounts produce 70% of revenue, and these are above $10k. Create three motions: self-serve for low-spend accounts, sales-assist for the $10k-$50k upgrade band, and enterprise for complex, multi-stakeholder deals above roughly $50k.
Before six AEs, validate pipeline coverage: 30 inbound enterprise accounts per month may not support six AEs at a $1.5M-$2M quota each. Also fix implementation readiness; 45-day implementation will throttle enterprise bookings. Hire two or three enterprise AEs plus a sales engineer or implementation lead first, and build outbound and marketing pipeline rather than assuming inbound scales. Coverage decisions should follow account potential and sales-cycle complexity, not a title.
2. How would you allocate the next quarter's go-to-market capacity across self-serve, sales-assist, and enterprise, and what would you measure?
Read the worked answer
Allocate capacity by expected return and binding constraint. Keep two sales-assist reps focused on the upgrade band and give them a quota and playbook; route enterprise to dedicated AEs with a sales engineer. Do not spread the two reps across both motions. For next quarter, add two enterprise AEs and one implementation or solutions role, not six AEs.
Measure stage conversion by segment, enterprise cycle time, time-to-implementation, sales-assist upgrade rate, self-serve conversion, and CAC by motion. If enterprise pipeline coverage is below 3x, adding AEs will create empty desks. The judgment is to relieve the binding constraint-implementation and qualified pipeline-before adding quota capacity. Otherwise six AEs increase cost without increasing revenue.
3. What revenue architecture risk does the single pipeline stage model create?
Read the worked answer
A single pipeline stage model hides where enterprise deals stall. Self-serve and enterprise do not share the same validation, security, procurement, or implementation stages. If enterprise deals stall after technical validation, a generic 'Proposal' stage will show them as progressing while no one owns implementation readiness.
Build stage definitions by motion, with exit criteria: technical validation, security review, business case, implementation scoping, and procurement. This improves forecasting and makes handoffs explicit. Revenue architecture is not just org design; it is the data model and stage definitions that let the company see the bowtie. Without them, the company cannot tell whether the problem is demand, conversion, or delivery.