Company playbook / 02 / Finding buyers
Rippling
Create distribution before hiring for scale
Rippling is not a developer tool. It is here because its sales leader has explained how the company went from direct, testable outbound to a much larger revenue organization.
01 / What they actually did
Programmatic outreach before a large SDR team
Matt Plank describes testing programmatic outbound and account databases before the company grew a larger, human-led outbound operation. The important practice is measuring cohorts, not copying its current headcount. [R1]
Partners already trusted by buyers
Rippling developed broker and accountant relationships, and its partner program still makes those routes visible. Those partners had their own client relationships and a reason to introduce Rippling. [R1] [R2]
Different products can need different sales motions
Plank describes asking three questions before building a specialist sales team: is the buyer different, are the economics good enough, and can the product stand alone? [R1]
02 / What you can learn
Lesson to keep: Pick a very specific audience, reach it directly, and learn which message gets a real conversation. Add people and volume only after you understand conversion.
Don’t over-copy: Rippling operates in a much larger horizontal market. Its outbound conversion rates or sales structure are not generic DevTools benchmarks.
03 / How to do something similar
- 01Create three small account lists defined by a real trigger, not just industry or job title.
- 02For each list, write one painful problem, one believable proof point and one ask.
- 03Separate warm introductions from cold outbound so you can compare them fairly.
- 04Review positive replies, qualified meetings, pipeline and deal progression every week.
- 05Test one complementary partner by creating a useful joint offer—not a ceremonial partnership announcement.
Examples you could publish or run
What to measure
Qualified opportunities and pipeline per 100 well-matched accounts.
04 / Copy the framework
Inspired by Rippling
Account cohort + outreach
Test a narrow audience before trying to send thousands of messages.
COHORT: [100 accounts sharing a genuine trigger] BUYER: [role with this problem] TRIGGER: [why the problem matters this quarter] CURRENT ALTERNATIVE: [what they use instead] EVIDENCE: [one specific, provable result] ASK: [technical conversation, assessment, useful resource] EMAIL 1 Subject: [specific problem at company] Hi [first name] — noticed [real signal]. Teams dealing with [problem] often run into [consequence]. We put together [proof / short resource]. Worth comparing notes on how you're handling [specific job]? FOLLOW-UP: Share one useful technical fact, not “bumping this.” TRACK BY COHORT: delivered → replies → qualified meetings → opportunities → ARR, with warm and cold separated.
05 / Original sources