When your service menu makes the buyer design the offer

A consultant’s service page might list research, strategy, workshops, coaching and implementation. Each item can be a useful piece of work. Together, they can leave a prospective customer with another assignment: work out which pieces belong together and in what order.

For an established service business, that is a practical offer problem. Your team knows the dependencies between its services. The buyer may know only that something in the business needs attention. A service menu should help those two kinds of knowledge meet.

Choose what your business wants to be responsible for

A small firm can be tempted to add every service it now has the tools to produce. AI may make another deliverable easier to offer, while the work of understanding the customer, reviewing quality and carrying the promise remains.

Before expanding the menu, ask whether the new service belongs to the problem you have chosen to solve. Could you explain its value to the same buyer? Do you have the judgment to assess it? Can your team deliver it alongside the commitments it already makes?

A narrow offer can leave you more room to adjust execution, test an extension and learn from the customer. A long menu can commit you to several kinds of work before you know whether you want the business they create. Keep the starting point clear and expand when you have a reason you can defend.

Give each service a reason to be considered

Start with a situation in which the service makes sense. A workshop could help a leadership team agree on a decision it has already researched. It could also expose disagreement that needs investigation before anyone writes a plan. Those are different assignments, even if both involve people in a room.

The GOV.UK Service Manual’s guidance on learning user needs recommends understanding what people are trying to accomplish and validating needs through research. Its setting is government services. For a commercial offer, a useful adaptation is to describe the customer’s situation before naming your preferred intervention. That description still needs evidence from your buyers.

For every service on your page, write down the condition that makes it worth discussing, the decision or task it helps with and any prerequisite. If two services have the same answers, their distinction may belong inside the delivery process rather than in the buyer’s first choice.

Show the order when the order matters

Consider an illustrative operations consultancy with three services: a workflow review, a handover plan and manager coaching. The offers and situations in this example are hypothetical.

A buyer whose team repeatedly loses track of work could start with the workflow review. A buyer who has already agreed on responsibilities might need the handover plan. Coaching could become useful once a manager owns a defined set of responsibilities and has begun carrying them out.

The website can make those conditions visible:

Service	Fits when	Decision	Needs
Workflow review	Cause of delays is unclear	Which handoffs need work	One team and workflow in scope
Handover plan	Roles are agreed	How to transfer each role	A named owner for each role
Manager coaching	A manager owns the work	How to handle real issues	A clear remit

This is a proposed way to explain those offers. It does not establish that the consultancy’s buyers use these categories or that the sequence improves sales. A real business would check both the wording and the delivery dependencies.

Some customers will still need help selecting a starting point. Say what an introductory conversation can resolve, such as whether the problem is sufficiently defined to scope a review. Avoid asking them to purchase discovery merely because your page leaves the choices unexplained.

Let buyers compare without remembering every page

Nielsen Norman Group explains the recognition rather than recall principle: visible information can reduce the burden of retrieving details from memory. Applied to a service menu, that suggests showing the same useful comparison fields beside each option.

Use consistent fields for purpose, scope, client participation and prerequisites. If one page describes outcomes, another describes hours and a third lists deliverables, the visitor has to reconstruct the comparison. A shared structure lets the differences become visible.

There is no universal correct number of offers. A specialist buyer may benefit from a detailed catalog. Someone facing an unfamiliar problem may need a small set of starting situations. Decide what your reader needs to distinguish, then choose the structure that supports that decision.

Check where a buyer’s interpretation diverges

Ask a recent buyer to look at the menu with a specific situation in mind. Ask where they would start, what they expect that service to resolve and what they think they would need to supply. Let them answer before explaining the intended choice.

Their answer can reveal a different issue from the one you expected. The service name might be unfamiliar. The scope might sound broader than it is. A prerequisite may be obvious to your team and invisible to the buyer. Fix the particular discrepancy, then check the revised explanation.

Use the offer worksheet to describe one starting point in full. Connect it to the decision customers are paying to make, and make sure the price has an intelligible scope. A useful menu gives a capable buyer enough context to discuss the next step with you.