What is "The Sales Acceleration Formula" by Mark Roberge about?
Mark Roberge wrote "The Sales Acceleration Formula" in 2015 from his tenure as Chief Revenue Officer at HubSpot, where the sales function scaled from zero to over 100 million in revenue in a few years. The book proposed that the sales operating model should be a system of four interdependent sub-formulas: the Sales Hiring Formula (data-driven hiring against predictive rep traits like coachability, curiosity, prior success, intelligence, and work ethic), the Sales Training Formula (standardised ramp curriculum against defined competencies with certification events), the Sales Management Formula (metrics-driven coaching against activity and attainment thresholds), and the Demand Generation Formula (inbound lead generation tied to a defined score and a lifecycle hand-off). The thesis is that scalable sales is a system of recalibrating formulas rather than a culture of top performers.
Why is the Sales Acceleration Formula hard to actually run?
The four sub-formulas have specific data requirements: hiring needs a durable record of predictive-trait scores plus the attainment outcome in the same system, training needs a competency model plus a certification system plus the attainment outcome in the same system, management needs activity data plus attainment data on one record, and demand generation needs a lead score plus a lifecycle plus a hand-off trigger on one data model. The platforms available in 2015 did not let the four formulas run on one data model, so teams ran them across five to seven tools (CRM, MAP, sequencer, LMS, forecast tool, hiring ATS). The quarterly recalibration that is the point of the formula rarely happens because the data lives in five systems. Strkr ships the primitives for all four sub-formulas on one data model so the recalibration actually ships.
How does Strkr support the Hiring Formula?
Strkr supports custom fields on the user record for predictive-trait scores. The sales leader defines the trait set (the Roberge default is coachability, curiosity, prior success, intelligence, and work ethic, but the business can define its own) and logs the scores at hire. The attainment outcome accrues on the same user record over the first 6, 12, and 24 months. The correlation between trait scores and attainment renders in-tool via the formula engine, so the Hiring Formula owner runs the correlation report at quarter-end, sees which traits are actually predictive for this specific business, and updates the hiring rubric for the next quarter. The predictive signal strengthens over time because the feedback loop is on-platform.
How does Strkr support the Training Formula?
Strkr supports a competency model on the user record with certification events as timestamps. The Enablement operator defines the ramp curriculum (product, sales process, buyer, tools, competitive) and the certification events that mark completion. The ramp curve against plan renders as a native saved view, which shows each new hire's attainment week by week against the defined ramp. Reps who are off the curve surface in week three or four, not month four, so the Enablement operator runs targeted coaching while it still matters. The ramp model recalibrates on evidence every cohort because the competency-to-attainment correlation ties ramp evidence to the actual outcome.
How does Strkr support the Management Formula?
Activity (calls, emails, meetings, sequence steps) and attainment (quota, closed, commit, best-case) both live on the user and opportunity records in Strkr. The front-line manager opens one view for the weekly 1:1 with the activity curve for the last 60 days, the attainment curve for the quarter, and the deals behind both. The Management Formula coaches on evidence instead of memory. The three-dashboard stitch job that most teams run on the sequencer-plus-CRM-plus-BI stack stops because the data is on one record. The activity thresholds that drive top-decile outcomes recalibrate quarterly from the attainment distribution, so the coaching conversation runs on the metrics that currently matter for this motion.
How does Strkr support the Demand Generation Formula?
Strkr ships lead scoring in the formula engine on behavior, firmographic, or custom criteria. The lifecycle stage field is first-class on contact and account. The MQL to SQL promotion fires on a flow when the score crosses the threshold. The hand-off between Marketing and Sales becomes a stage move instead of a field-mapping document between the MAP and the CRM. The lead-score-to-closed-revenue correlation renders in-tool at quarter-end, so the MQL threshold recalibrates on evidence. The MAP-plus-CRM reconciliation stops because the score and the outcome live on the same record. The Demand Generation Formula owner optimises against the actual leakage stage in the funnel instead of guessing.
Does Strkr require Mark Roberge's specific framework to work?
No. The Sales Acceleration Formula is one example of a disciplined operating model, and the Strkr primitives support it well because the thesis of the book (one data model, recalibration loops, metrics-driven coaching) matches the thesis of the platform (one data model across Sales, Marketing, and CS, with the admin surface designed for a RevOps generalist). Teams that run other frameworks (Winning by Design, Topo, Jacco van der Kooij, Daniel Pink) see similar leverage because the underlying primitives are the same: durable records, cross-object formulas, lifecycle stages, native reports, and a quarterly recalibration ritual. The Strkr thesis is that the platform should support any disciplined operating model, which the Sales Acceleration Formula happens to be a well-known example of.
