Account executives, Founders, Sales reps, Sales managers, Consultants
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales pricing strategist. Your task is to create a clear pricing justification that helps a buyer understand why the proposed investment is reasonable based on their situation, expected value, alternatives, and cost of inaction.
### Required Input
- Offer: [What you sell, e.g. onboarding automation software for customer success teams]
- Pricing Structure: [How pricing works, e.g. monthly subscription, implementation fee, usage-based, fixed project fee]
- Buyer Role: [Who needs the explanation, e.g. CFO, Operations Director, Founder, Procurement Manager]
- Buyer Situation: [Relevant context, e.g. growing team, manual process, missed deadlines, cost pressure]
- Confirmed Pain Points: [Problems the offer addresses, e.g. rework, delays, errors, low visibility]
- Expected Outcomes: [What the buyer wants to improve, e.g. reduce manual admin, improve reporting accuracy]
- Alternatives Being Considered: [Status quo, internal build, competitor, manual workaround, unknown]
- Buyer Pricing Concern: [Exact concern if known, e.g. too expensive, not budgeted, cheaper competitor]
- Available Metrics: [Costs, time, volumes, error rates, revenue impact, or state unknown]
- Tone: [Executive, consultative, direct, plainspoken, finance-friendly]
### Input Validation
Review all inputs before creating the explanation. If pricing structure, buyer situation, confirmed pain points, expected outcomes, or buyer pricing concern are missing or vague, ask specific clarification questions. Pause and wait for clarification before generating the final output.
### Instructions
Explain pricing through business logic, not defensiveness. The explanation should help the buyer see what the investment is tied to and why the price is not just a number, but a trade-off against current costs, risks, and missed outcomes.
Map the price to value drivers such as time saved, workload reduced, cost avoided, revenue protected, faster decisions, lower risk, better visibility, improved consistency, or improved customer experience. Do not claim exact savings unless the input provides enough data.
Compare the offer against realistic alternatives. Include the status quo as an option and explain what the buyer continues to absorb if they do nothing. If a cheaper competitor or internal approach is mentioned, compare based on trade-offs rather than attacking the alternative.
If metrics are available, create a conservative value calculation. If metrics are missing, provide a calculation framework and list the exact data needed to complete the business case.
Avoid discounting language unless the input specifically asks for it. Do not apologise for the price. Keep the explanation confident, practical, and buyer-centred.
### Output
Provide the pricing justification in this format:
1. Pricing Logic Summary
2. Buyer Value Drivers
3. Price-to-Outcome Mapping
4. Cost of Inaction Explanation
5. Alternative Comparison
6. Conservative Value or ROI Calculation Framework
7. Buyer-Facing Pricing Explanation
8. Response to the Specific Pricing Concern
9. Data Needed to Strengthen the Case
10. Follow-Up Question to Advance the Conversation
Rewrite the explanation for a CFO audience using conservative assumptions and payback logic.
Required inputs used:
Offer: Onboarding automation software for customer success teams
Pricing Structure: $2,400/month subscription plus $9,500 one-time implementation fee
Buyer Role: CFO
Buyer Situation: A 90-person B2B SaaS company is adding 35 to 45 new customers per month, but customer onboarding still relies on spreadsheets, manual reminders, and customer success manager follow-up.
Confirmed Pain Points: Rework, delayed onboarding tasks, inconsistent customer experience, poor visibility into onboarding status, preventable escalations, and customer success managers spending too much time on administration.
Expected Outcomes: Reduce manual onboarding administration, improve reporting accuracy, shorten time to first value, increase onboarding consistency, and protect retention.
Alternatives Being Considered: Status quo, internal build by operations team, and a cheaper competitor with lighter automation.
Buyer Pricing Concern: The CFO believes the price is high compared with the cheaper competitor and wants to know why the investment is justified.
Available Metrics: 40 new customers onboarded per month, average 6 manual admin hours per customer, customer success loaded labor cost of $65/hour, estimated 20% to 35% reduction in admin time is realistic, average annual customer value is $18,000.
Tone: Finance-friendly and consultative
The pricing is reasonable because it is connected to a measurable operating problem: the company is growing customer volume faster than its onboarding process can scale. The investment is not simply for software access. It is for replacing repeated manual work, improving visibility, reducing preventable delays, and creating a more consistent onboarding experience without immediately adding more headcount.
The one-time implementation fee funds the work required to configure workflows, connect key systems, migrate onboarding templates, define reporting views, and train users. The monthly subscription reflects the ongoing value of automated task routing, status visibility, customer onboarding tracking, reporting, and scalable process control.
For a CFO, the strongest pricing logic is that the current process already has a cost. The proposed investment should be evaluated against manual labor, rework, delay, customer risk, and management visibility gaps rather than against software price alone.
Implementation fee: The $9,500 implementation fee is tied to setup work that the buyer would otherwise need to complete internally. This includes workflow design, system configuration, onboarding template buildout, reporting setup, stakeholder training, and launch support. The outcome is faster deployment with less internal trial and error.
Monthly subscription: The $2,400/month subscription is tied to ongoing use of automation, task management, reporting, visibility, and process consistency. The outcome is a repeatable onboarding engine that can support increased customer volume without a matching increase in manual effort.
Manual workload reduction: The price supports the goal of reducing customer success manager administration. If the team currently spends 240 manual admin hours per month on onboarding, even a conservative reduction creates meaningful capacity.
Reporting accuracy: The price supports more reliable onboarding data. This reduces the time managers spend chasing updates and improves confidence in operational decisions.
Retention protection: The price supports a better early customer experience. Even if the solution prevents only a small number of onboarding-related churn risks, the value can be significant because the annual customer value is high.
Doing nothing is not cost-free. The current process already consumes customer success capacity, creates avoidable management follow-up, and increases the chance that customers experience delays during a critical stage of the relationship.
If onboarding volume continues at 40 customers per month and each customer requires 6 manual admin hours, the company is spending approximately 240 admin hours per month on onboarding coordination. At a loaded labor cost of $65/hour, that equals $15,600 per month in manual onboarding administration exposure.
The status quo also creates less visible costs. These include slower time to first value, inconsistent handoffs, higher customer frustration, delayed escalation visibility, and leadership time spent asking for updates. As the company grows, those issues usually become more expensive because the process depends on people remembering tasks instead of the system managing them.
Status quo:
The status quo has no new vendor cost, but it continues the existing labor burden, reporting gaps, and inconsistency. It may appear financially safer in the short term, but it keeps the company dependent on manual coordination as volume increases.
Internal build:
An internal build may offer more control, but it requires operations, customer success, and technical resources to design, build, test, maintain, and improve the system. It may also take longer to deploy and can distract internal teams from core priorities. The true cost should include internal labor, opportunity cost, maintenance, and delayed impact.
Cheaper competitor:
A cheaper competitor may be appropriate if the buyer only needs basic task tracking. However, if the buyer needs deeper workflow automation, reporting, implementation support, and scale readiness, the lower price may come with trade-offs in adoption, process fit, and long-term usefulness.
Proposed offer:
The proposed offer is strongest if the buyer values implementation support, automation depth, operational visibility, and a faster path to consistent onboarding. It is not the cheapest option, but it is designed to reduce operating drag and create a more scalable process.
Current monthly manual onboarding administration:
40 customers per month × 6 admin hours per customer = 240 admin hours per month
Current monthly labor exposure:
240 hours × $65/hour = $15,600 per month
Conservative 20% admin reduction:
240 hours × 20% = 48 hours saved per month
48 hours × $65/hour = $3,120 labor capacity recovered per month
Moderate 35% admin reduction:
240 hours × 35% = 84 hours saved per month
84 hours × $65/hour = $5,460 labor capacity recovered per month
Monthly subscription comparison:
At $2,400/month, the subscription is below the conservative estimated labor capacity recovered of $3,120/month.
Implementation fee payback framework:
$9,500 implementation fee ÷ $3,120 conservative monthly labor capacity recovered = approximately 3.0 months to offset implementation through labor capacity alone.
Additional value not included in the conservative calculation:
The reason we price the solution this way is that the investment is tied to both implementation effort and ongoing operational value. The implementation fee covers the work required to build the onboarding workflows properly, connect the right systems, set up reporting, and prepare the team to use the process consistently. That reduces the risk of buying software that does not get adopted.
The monthly subscription is connected to the ongoing value of reducing manual administration, improving onboarding visibility, and helping the customer success team support higher customer volume without adding the same level of operational cost.
Based on the current volume of 40 customers per month and 6 manual admin hours per onboarding, the team has roughly 240 hours of manual onboarding coordination each month. Even a conservative 20% reduction would recover about 48 hours per month, or roughly $3,120 in labor capacity at the current loaded cost. That means the subscription can be justified through recovered capacity alone, before accounting for retention protection, reduced escalations, or faster customer activation.
I understand the concern that the competitor is less expensive. The key question is whether the comparison is based on license cost or on the total cost of solving the onboarding problem.
If the goal is basic task tracking, the lower-cost competitor may be enough. If the goal is to reduce manual administration, improve visibility, standardise onboarding, and avoid adding headcount as volume grows, then the comparison should include implementation quality, automation depth, reporting, adoption support, and the cost of continued manual work.
The proposed solution costs more because it is designed to solve a broader operational issue, not just provide another place to track tasks. The right decision is not simply the lowest price. It is the option that gives the company the best trade-off between cost, speed, adoption, and measurable operating improvement.
Would it be useful to compare the three options side by side using total cost, implementation effort, expected time savings, and risk to customer onboarding outcomes so finance can evaluate this as a business case rather than a software price comparison?
Get access to all workflows, across every sector, with structured systems built for better results.