How to Create a Sales Process for More Predictable RevenuePredictable Revenue and reposted with permission. The concept is not new. In order to consistently hit quota, sales development reps must strike a balance between volume and personalization. If you’re emailing at too low a clip, you risk being put out of commission by a few bounces and an out-of-office. If you toss hundreds of emails over the fence each day, you’re putting your success and the company’s reputation at risk. This post isn’t about restating a well-known fact using different language. It’s about creating a simple process that helps strike the right balance. It’s about taking what’s worked and what hasn’t. It’s about formulating a cold email methodology that makes your team’s semi-personalized emails stand out from the heavily-automated content, and even the highly-personalized one-offs. But before we dive into that, check out our epic Predictable Revenue Infographic to refresh on the core principles of Predictable Revenue and SDR’s.
Emotions book demos; logic wins dealsSDRs understand that their job is to book qualified demos. For most orgs, that looks something like a 30-minute meeting with a decision-maker who has the budget and need for your product. Here’s the disconnect: too many SDRs are trying to win the deal before winning the meeting. In most cases, winning the deal is nearly impossible — it involves numerous touchpoints, multiple stakeholders and a dizzying web of budget and legal approvals. Winning the meeting involves one guy, in one department, with one agenda and 30 minutes to kill next Thursday. To convince this guy, you don’t need a clear-cut business case with hard ROI stats, you just need a story.
Telling stories starts with your customersSo how can you take what you’ve currently got and turn it into a story? The first step is to look at the stories your customers have already given you. If you have a kickass product and the marketing team is pulling their weight, you should have a nice catalog of case studies to pull from. A typical case study format goes something like this, and provides a starting point for your pitch. The Before:
- What was the customer doing before they chose you? What were their pain points and how were they being addressed?
- How has your product improved things for the customer? What previous solutions and process did it replace and how has that impacted the business?
- What kind of results came after adopting your product? How do these results measure up to previous performance?