.svg){kind=icon}
Your offer started with one good idea.
Then somebody asked if there'd be private support, so you added a call. You worried the call wouldn't be enough, so you added voice notes. The program felt a little light next to somebody else's twelve-module course, so in went the resource library, the guest session, the bonus, and lifetime access to the portal nobody's opened since week two.
Nothing in there is ridiculous. That's what makes it hard to see. Every addition is defensible. Every addition might even be useful.
But put together, the offer's become a record of every moment you worried the work wasn't enough.
And I want to name that first, because "just remove some bonuses" is an insultingly shallow answer to what's actually happening. If you've always proven your value through how much you notice, how much you give, how available you are — of course a simpler offer feels like a lesser one.
It's not a generosity problem. It's a legibility problem. You're trying to make the value visible through the volume of your labour, when the real value is your judgment, your method, and the change the work is built to create.
More stuff doesn't automatically mean more value
A buyer might appreciate the long list. She's not really buying the list, though. She's trying to answer a much smaller set of questions:
- Is this for the problem I have right now?
- Do I understand what's going to happen?
- Do I trust this process, and this person?
- Can I see how the support actually helps me move?
- Does this feel worth the money, energy, and time it asks for?
A crowded offer makes those questions harder to answer. She sees a long list and assumes the value's in there somewhere — she still has to go find it.
Same crowding creates a capacity problem for you. Every extra touchpoint has to be prepared, delivered, tracked, remembered, held. A bonus can look free on a sales page and quietly cost you hours every single time the offer runs.
Run this on your own offer
List every call, review, resource, message channel, bonus, and customization inside the offer. Then run each one through these four questions.
1. Does this change the result?
Keep the parts that help the client understand, practise, apply, or finish the work.
Feedback on a first attempt can meaningfully change the result. A second workbook that repeats the same lesson in a different format probably doesn't.
Why it works: it ties the offer's shape to the transformation, not to how much material you can produce.
2. Does this reduce a real point of uncertainty?
Some support belongs because it helps the client know what to do when the work gets hard.
That might be one scheduled check-in after implementation, a clear FAQ, an example, a defined way to ask for help. It doesn't have to mean open access to you all the time.
Why it works: predictable support builds more trust than vague abundance. She knows exactly where the help is and what it's for.
3. Does this belong in this offer, or somewhere else?
A useful resource can still be in the wrong container. A foundational workshop might actually be a prerequisite, a low-cost entry offer, or a bonus for a totally different buying moment.
Why it works: every offer gets one clear job. Nobody's asked to buy your entire body of knowledge in a single transaction.
4. Did I add this because I was worried the core work didn't look like enough?
The uncomfortable one.
If your real value is your ability to diagnose the pattern, pick the right intervention, and guide someone through it — twelve unrelated assets can make that judgment less visible, not more.
Why it works: it separates client support from your own reassurance. Both needs are real. Only one belongs in the offer.
A before-and-after
Before: Twelve weekly calls, unlimited messaging, a thirty-video portal, five guest workshops, custom practices, weekly written reviews, lifetime access.
After: A twelve-week three-stage method, one weekly group call, two private application reviews, one defined question channel, and a focused library with only the practices used in the method.
"But what if somebody needs more?" I can hear it already.
Then we decide what "more" is, what problem it solves, and where it goes. We don't pre-install unlimited access for every hypothetical struggle before a real client's even in the room.
The second offer isn't less caring. It makes the care deliberate. Easier to understand, easier to use, and a lot more sustainable for you to actually deliver.
Your assignment
Build a table with four columns:
- Offer component
- Job it does
- What happens if it disappears
- Keep, move, combine, or cut
Don't ask if each thing is nice to have. Ask if it changes the result, reduces real uncertainty, or protects the quality of the work.
If you can't say its job in one sentence, it doesn't stay by default.
