Outbound Wiki

Economic value propositions

Showing the financial value of an offer through savings, revenue gains, productivity or payback.

An economic value proposition puts an offer into monetary terms and shows its contribution to the customer's profitability.1 Build it from the current process, put a dollar value on the impact, and use the buyer's own success measure to shape the case. A preliminary business case is a few quantifiable benefits discovered with your champion, such as savings, productivity gains, or revenue increases.2 That gives you a working version to test in conversation.

Find the economic change

Start by naming the business change the offer should create. Keep asking until you can express that change financially.

Look for monetary value in revenue gains, improved productivity, service enhancement, or speed.3 A simple test is whether the opportunity saves money or makes money; if it does neither, it may be too weak to justify a purchase.4

Ask:

  • What does this process cost today?
  • Where does it hold back revenue or productivity?
  • What happens if the problem stays in place?

Include foregone opportunity in the conversation. Knowing an initiative's dollar cost or foregone opportunity cost lets you compare choices and use financial measures when deciding whether to proceed.5 Move on when the buyer can state the affected measure, the current consequence, and the change the offer should create.

Quantify the impact

Start with the buyer's baseline and show each assumption. The buyer should be able to trace the estimate from current conditions to the expected financial effect.

Quantify cost savings from process scale-up.6 If revenue is the mechanism, quantify what the problem could be worth as revenue potential.7 Use a bounded estimate of potential ROI and time to value.8

Ask which measure will show the impact, what its current value is, and what change would count as meaningful. Ask who owns the measure and which assumptions need confirmation.

Cost gives the action economic context and leaves the decision open.9 The buyer can inspect the tradeoff without treating the estimate as an automatic approval or rejection.

Build the business case with the buyer

Once the impact has a working estimate, turn it into a case the account can carry internally. Give the buyer something useful in exchange for the details needed to tighten the estimate.

After identifying the problem's impact, start crafting a business case, and when the prospect provides information about the current process, provide a business case in return.1011

Build the case around benefits the buyer recognizes. Ask which benefit would get attention in an internal review, which assumption someone would challenge, and what would make the case easy to repeat to another approver.

Make expected ROI easy for the customer to communicate, because that helps the customer defend the numbers.12 Add the buyer's human reason for acting to the quantitative case. A business case combines emotional drivers with logical quantitative drivers.13

Test the economics

Treat the case as a hypothesis until the account's own success measure and approval path have tested it. The next conversation should find the measure the buyer already trusts.

Ask, "How are you measuring the success of your sponsorship engagements?".14 Let the answer determine which measures appear in the case. When ROI comes up, ask the customer how to quantify it and build the business case together.15

Partner with your champion while assessing potential economic benefits.16 Confirm those benefits with the economic buyer.17 Move on when the people involved can repeat the same financial case and explain how the measure will be checked.

Turn the math into a decision

Give the buyer a measure that fits the way the spend gets approved. Use ROI or payback when the buyer needs to compare the investment with the return.

Corporate financial analysts use the payback period to value investments or operational projects and determine which to undertake.18 The ROI calculation subtracts total project cost from total annual retrofit savings to obtain net savings, then divides net savings by total project cost.19 Use the same discipline with the measure the buyer has accepted for the offer.

Connect pricing to the prospect's problems, pains, or impacts.20 Tie the solution and its deployment to the organization's bottom line, revenue, and customer support model.21 Buyers purchase based on how a solution drives the economics of their business.22

What not to do

Use this check before presenting the case. It keeps the estimate tied to a decision the buyer can explain.

  • Enterprise buyers purchase proof or math, so leave abstract future promises out of the enterprise case.23
  • A promise that buying the product will make the customer 1.2 percent better does not constitute a business case.24
  • The customer business case needs more than an ROI calculator.25

Sources

  1. 1
    “Our definition of a value proposition is “the translation of the supplier’s offers into monetary terms that demonstrate their contribution to the customer’s profitability.””
  2. 2
    “While this might sound sophisticated, it is nothing more than a few quantifiable benefits you have discovered together with your Champion such as savings, productivity gains, revenue increase, etc. that your solution will bring.”
  3. 3
    “Adding value (e.g. revenue gains, improved productivity, service enhancement, speed, etc.)”
  4. 4
    “to find out the why, and if it's not saving money or making money, it's probably not valuable”
  5. 5
    “Knowing how much it will cost to undertake an initiative, either in dollars or in foregone opportunity, makes it possible to ascertain the supply cost of any initiative, compare choices, and use traditional financial metrics in making a go/no-go decision.”
  6. 6
    “ Quantify cost savings from process scale-up”
  7. 7
    “And ideally starting to quantify like what that would be worth in terms of revenue potential.”
  8. 8
    “The third input is a bounded estimate of potential ROI and time to value.”
  9. 9
    “Knowing what something costs provides critical knowledge for understanding the economic implications of a given action; it does not preempt or prohibit the action.”
  10. 10
    “because where I would go from then is starting to craft a business case.”
  11. 11
    “If we're getting information on the current process, absolutely I will give them a business case.”
  12. 12
    “So if you can make it easy for them to say, hey, we're going to get this ROI, then obviously”
  13. 13
    “combination of emotional drivers and logical quantitative drivers.”
    I Ran a Sales Call For A Product I Never Sold

    30 Minutes to President's ClubBack to the text

  14. 14
    “The wrong way is to pull up 12 different ROI case studies and go through every single line item of our customer QBRs. The right way is to say, well, look, every customer tracks us a little bit differently. Some people look at direct source pipeline. Others look at influenced pipeline. I've got some case studies I could take you through. I guess I'm curious, how are you measuring the success of your sponsorship engagements?”
  15. 15
    “put it on the customer, ask them how you're going to quantify it and build the business case”
  16. 16
    “You must partner with your champion”
  17. 17
    “And then you must confirm with the economic buyer,”
  18. 18
    “Corporate financial analysts do this with the payback period.”
  19. 19
    “Total annual retrofit savings – Total project cost = Net savings ÷ Total project cost = Return on investment (ROI)”
  20. 20
    “When you're doing pricing, connect the dots back.”
  21. 21
    “to your organization's bottom line and your revenue and your customer support model.”
  22. 22
    “They buy on how your solution is going to drive the economics of their business.”
  23. 23
    “But your buyer doesn’t purchase the future; they purchase either proof or math.”
  24. 24
    “Not if you buy my stuff, you'll be 1.2% better”
  25. 25
    “It's not just based on a ROI calculator.”