okhp3-outcome-modeling-sales

Topics in the source

• okhp3-outcome-modeling-sales
• Scope
• Reframe the sales outcome
• Computational payload
• Workflow
• Validation gates
• Output contract
• References

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Apply outcome modeling to sales and business decisions where raw wins can hide discounting, easy-opportunity selection, churn, service cost, or money left on the table. The primary object is economically efficient contribution, not a flattering headline metric such as close rate. -- | In scope | Out of scope | |----------|-------------| | Pipeline and revenue forecasts | Fabricated CRM or customer information | | Margin, retention, expansion, and capacity-aware decisions | Personnel decisions based on a single metric | | Rep, account, territory, and opportunity comparisons | Unauthorized outreach or CRM writes | -- Do not treat a 100% close rate as proof of superior performance. First examine opportunity assignment, customer fit, deal size, competition, discounts, cycle time, retention, expansion, service burden, and capacity consumed. Use an economic objective such as: The exact objective must be agreed before ranking salespeople or allocating resources. Read references/computational-model.md for expected contribution, incremental lift, and constrained allocation formulas. Read references/glossary.md before using sales abbrevi

This is an excerpt. Refer to the complete source and its current requirements.