The Offer Has Three Parts: Problem, Promise and Delivery
Clarify your offer by naming the customer’s problem, the change you promise and how you deliver it, so buyers can understand what they are considering.
The common mistake with an offer is to lead with the service rather than the problem it addresses. A list of tasks may sound competent, but a prospective customer still has to work out why those tasks matter, what should change and what they must do next. A clearer offer connects three parts: problem, promise and delivery.
Keep those parts distinct while making them fit together. The problem gives the offer a reason to exist; the promise describes the intended change; delivery explains what the customer actually receives and how the work proceeds. When one part is vague, sales conversations tend to fill with clarification, mismatched expectations or requests for work that was never included.
Name the customer’s problem
Start with a situation the customer can recognise, not an abstract category such as “business growth” or “better marketing”. Look for the specific difficulty behind the request: enquiries arrive but are not followed up, new staff cannot find the current procedures, or a shop’s product descriptions leave shoppers unsure which option suits them.
That wording is not a diagnosis of the customer. It is a useful description of the friction they want addressed. Ask what is happening, where it becomes inconvenient and what the person is trying to do when they encounter it. You can use what customers already tell you in ordinary conversations, support messages or enquiries; this is not the same as claiming to know every customer’s motives.
Be careful not to mistake the requested solution for the underlying problem. Someone might ask for a new website when the immediate issue is that customers cannot find opening hours or understand how to book. The website may be appropriate, but naming the obstacle first gives both sides room to consider a smaller or better-fitting response.
Choose a problem narrow enough to guide a decision. “The booking page does not explain what information to prepare” is more actionable than “the customer journey needs work”. The narrower statement helps you decide which work belongs in the offer and which would be a separate project.
Make the promise observable
The promise is the change the offer is designed to support. It should be meaningful to the customer and clear enough to discuss, without presenting an uncertain outcome as certain. A promise can describe a deliverable or a change in usability: for example, a set of product descriptions that makes the differences between options easier to compare.
Prefer language the customer could recognise in the finished work. “A clearer route from enquiry to booking” gives you something to discuss and review. “Transform your business” does not say what will be different, and “increase sales” may depend on factors outside the work you control.
Separate the intended change from the conditions around it. A consultant can prepare a plain-language booking page, but customer response may also depend on availability, pricing, traffic and the way the page is used. State what the work is meant to improve, then be candid about what remains outside the offer.
Say you run a small design studio and a local caterer says customers keep asking what each menu package includes. You might define the problem as unclear differences between packages, promise a set of descriptions that makes those differences easier to compare, and deliver revised copy with a review round. The useful result to look for is whether the descriptions answer the questions they were written to address, not a claim about how many orders they will produce.
Explain the delivery
Delivery turns the promise into a concrete arrangement. Describe the main work, the customer’s role and what they receive. Depending on the offer, that might mean a workshop and written recommendations, a monthly bookkeeping service, a set of edited pages or a scheduled maintenance visit.
Be specific about the boundaries that shape the experience. If the customer must supply product details, identify that input. If the work includes a draft and one review round, say so plainly. If the offer does not include implementation, ongoing support or additional pages, name the limit rather than letting the customer infer it.
Do not confuse delivery detail with a long inventory of minor tasks. A customer usually needs to understand the sequence and the hand-offs, not every internal action. “You send the current menu; I prepare revised descriptions; you review them before the final copy is supplied” is easier to discuss than a dense list of editing operations.
Choose a delivery format that suits the nature of the work. A short written plan may be useful when the customer needs to share decisions with colleagues. A live session may suit work that depends on discussion. A physical service may need a clear appointment window and an agreed way to confirm completion. Keep the format proportionate to the customer’s problem.
Where do the three parts meet?
What should an offer sentence include?
Name the customer’s situation, the intended change and the delivery in everyday words. A sentence is a starting point, not a substitute for explaining scope, timing or customer responsibilities.
How can you tell if the problem is too broad?
If the problem could describe nearly any business, it will not guide a useful offer. Add the place where the difficulty occurs or the task the customer is trying to complete.
Should the promise describe an outcome or a deliverable?
Use the change the customer cares about, then connect it to work you can actually provide. If the wider outcome depends on factors you do not control, avoid presenting it as a certain result.
What if delivery varies by customer?
Set out the common parts and explain which details are agreed for each engagement. That gives the customer a stable understanding without pretending every project follows an identical script.
Check the fit before quoting
Before presenting an offer, read the three parts together and ask whether they describe the same piece of work. A problem about unclear booking information, a promise about better staff morale and delivery consisting of a redesigned booking page do not quite align. One part may be missing, or the offer may be trying to solve several problems at once.
- Problem: Can the customer recognise the situation in this wording?
- Promise: Is the intended change visible in the work or its use?
- Delivery: Does the customer know what they receive and what they need to provide?
- Boundary: Are exclusions and additional work easy to identify?
- Fit: Does each delivery item contribute to the stated promise?
If an item does not support the promise, decide whether it belongs in a separate option or should be removed. If the promise cannot be expressed without relying on a result outside your control, rewrite it around the part you can deliver and explain the wider uncertainty in conversation.
It is not worth polishing a slogan before the underlying offer makes sense. Clever wording cannot compensate for an unclear customer problem or an undefined hand-off. A direct sentence that exposes a mismatch is more useful than a polished line that conceals one.
Use the offer in conversation
Present the problem first and let the customer correct your wording. They may describe a different obstacle, or reveal that the issue occurs only in a particular situation. Treat that clarification as a reason to adjust the scope, not as an invitation to promise every possible improvement.
Then explain the intended change and delivery in terms the customer can question. Ask which part matters most, what they would need to provide and whether any boundary is unclear. These questions help uncover a mismatch before it becomes a dispute about what was included.
Use the same three-part description in a proposal, a service page and a spoken conversation, but adapt the detail to the setting. A short introduction can name the problem and promise; the proposal can spell out responsibilities and limits. Consistency matters more than repeating identical wording.
A useful offer makes the decision easier to discuss, not automatic. Keep the problem specific, make the promise observable and spell out delivery in plain terms. When those three parts agree, both you and the customer can see what is being considered—and where a different offer may be needed.
