Video summary
One Offer, One Year, $1M
Main summary
Key takeaways
Core business problem: “Custom work” vs scalable offers
If you try to be “everything to everyone,” you become “nothing for no one,” and you end up building whatever each customer asks.
In software/services, this creates the pattern of becoming a cheap labor/dev shop:
- Each new customer requests new features → you keep adding
- You spend big time for low recurring revenue
- Example: 15 hours built to support a $50/month subscription
Solution: Find the “meaty middle”
Find the meaty middle—an offer specific enough to solve real problems, but substantial enough to fund growth.
Build a scalable offer that stands on its own, rather than a stream of custom requests.
The “One Offer, One Year, $1M” strategy (execution playbook)
Positioning + offer design
Create an offer that:
- Sounds like you understand the customer’s specific problem
- Is a full-feature solution (missing features will show up as objections)
- Targets the meaty middle customer segment
- Not entry-level and not enterprise (those buyers differ)
Pricing framework
Price it as if you had to pay someone else to do the work.
- Rule: determine what you’d charge the customer if you were outsourcing the delivery.
- This prevents underpricing that traps you in “build labor for cheap.”
Sales feedback loop
Treat objections as structured product requirements:
- “No” often means: “I’m not hearing what I need to say yes.”
- Reverse-engineer the offer after a few sales calls:
- Identify recurring objections
- Add features that would convert “no” into “yes”
Goal outcome: after iteration, you have one coherent offer that converts.
Marketing + sales simplification for scaling
Once the offer is set, run for 1 year with:
- One marketing channel
- One message
- One sales tool
- One sales process
- One product/offer
Avoid expanding into multiple offers too early:
- Selling three things increases complexity roughly as “cubed”
- Not 3x harder—rather, it disrupts marketing/sales/case studies/pitch fit
Implied KPI/target
Consistent execution of the above for 12 months → ~$1M business (stated outcome/goal).
Actionable recommendation: Assessment-based sales (and when to use it)
A strategy discussed by the other presenter:
- Run an audit/assessment first
- Then quote after the sales call
Guidance given:
- Works best when price point is ~$10k+
- Reason: it’s a slower, two-step close:
- assessment call
- close call presenting the solution
- For lower prices, the faster “direct conversation → purchase” approach is often better.
Price threshold example:
- Assessment approach was discussed around $2,500–$5,000
- But the advice was that assessment-based sales typically performs best at higher (~10k+) levels.
Concrete “next steps” checklist (from the talk)
- Pick the meaty middle segment (one primary buyer profile).
- Build one full-feature offer (not a bundle of custom deliverables).
- Set pricing:
- Outsourcing-equivalent pricing (what you’d pay someone else to do it).
- Run sales calls, log objections, and iterate the offer until objections are resolved via added features.
- Commit for 1 year to:
- one channel + one message + one sales process + one offer.
Sources / presenters
- David (mentioned during the offer/marketing question: “Does that make sense, David?”)
- Main speaker (not named in the subtitles; also author of the Scale Workbook mentioned at the end)