How 24,000 calls helped create $4.7M in pipeline and a better outbound playbook at Rippling
From Shawn Fletcher’s time at Rippling, this field report shows how better funnel visibility, discovery, talk tracks, and qualification helped turn outbound activity into stronger pipeline.
Rippling sells several products across HR, IT, and Finance. That creates more opportunity, but it also creates more ways for outbound to miss.
generated
new clients
and tracked
call-to-demo rate
The right message for a CFO may not work with a Head of HR. A meeting can look good on the calendar but never become a real sales opportunity. A rep can make hundreds of calls without learning what needs to change.
The work was not only creating more activity.
It was building a better way to see what was happening, learn from every conversation, and turn that information into stronger targeting, messaging, discovery, and follow-up.
More activity did not always mean more qualified pipeline
Rippling's outbound team worked across different products, buyers, company sizes, and reasons to buy. One prospect may care about payroll. Another may be trying to control company spend. Another may be dealing with onboarding, compliance, or hiring across several states. That meant the team could not rely on one message or one basic script.
It also meant the normal top-of-funnel numbers did not tell the full story. A meeting could be booked with the wrong buyer. A prospect could agree to a demo without a strong reason to change. One segment could create many conversations but very little pipeline. Another could produce fewer meetings but much larger opportunities.
Make the full funnel visible
The first step was understanding where the outbound motion was breaking. That meant looking beyond total calls and meetings booked. The team needed to see how many calls became connections, how many connections became pitches, how many pitches became conversations, how many conversations became meetings, how many meetings became qualified opportunities, and which buyers, messages, and segments created real pipeline.
Dashboards helped make those gaps easier to see.
Instead of telling reps to simply make more calls, the team could see whether the issue was the data, the opener, the discovery process, the offer, or the quality of the meeting.
This made it possible to change the part of the system that was actually holding results back.
Use calls to improve discovery
The calls were not only a way to book meetings. They were also the fastest way to understand what buyers cared about. Discovery training was built around helping reps collect better information and avoid stopping at the first surface-level problem. That included:
This helped increase the call-to-demo rate by 26%. The improvement did not come from finding one magic opening line. It came from helping reps hold better conversations once someone answered.
Build new talk tracks around new products
As Rippling expanded its outbound motion, the team also needed new ways to explain products that buyers did not always connect with Rippling. One example was standalone Spend. The talk track had to help a rep move from a cold opening into a useful conversation about how the company managed cards, expenses, approvals, and financial control. The talk track was reworked, tested, and then shared with more than 200 SDRs.
This was not only a new script. It was a way to help a large team understand a new buying problem and speak about it in a consistent way.
Remove work that kept reps from selling
Call logging was creating unnecessary manual work. An initiative with Nooks helped remove that step, allowing call activity and results to be captured without making reps stop and enter everything themselves. That change helped improve SDR metrics by 30%.
It was a simple lesson. Sometimes the best way to increase activity is not to ask people to work harder. It is to remove the work that should not have been there in the first place.
Change the plan when the market changed
Summer created a different problem. Prospects were traveling, spending less time at their desks, and pushing decisions into the fall. The answer could not only be to keep using the same cadence and hope people responded. A new summer outbound plan was built around:
The plan also separated real objections from brush-offs and gave reps better questions to keep conversations open.
Outbound became easier to measure, teach, and improve
The work contributed to:
Better visibility into the difference between activity, meetings, qualified pipeline, and revenue. Once we could see it, we could aim for the top-right, not just the top of the funnel.
A clearer way to run outbound
The larger result was not one script or one dashboard. It was a clearer way to run outbound.
A loop, not a line
Calls created information. That information improved discovery and messaging. The improved motion created stronger meetings. The meetings could then be followed through pipeline and closed revenue.
Outbound needs to learn from what happens after the activity
A lot of outbound teams stop the analysis at replies and meetings. But a meeting is not the final result. You also need to know:
We do not only make calls and send emails. We track what the market tells us, what becomes pipeline, which companies become valuable clients, and what needs to change in the next round.
That thinking became part of how Velosite works today.
Book a call