Define the outcome, scope, and boundaries of your consulting offer

1. Describe the outcome in the buyer’s terms

Begin with the change a client wants to make, not the tasks you know how to perform. “Run stakeholder interviews and review the pipeline” describes activity. An outcome statement names the intended destination, such as “give the leadership team a prioritized view of where qualified opportunities stall.” Treat that as a clear aim, not a guarantee of business results.

Use this sentence frame: “I help [specific buyer] move from [current situation] to [defined deliverable or decision] by [time or process, if you can responsibly commit to it].” Keep only the parts you can explain and control. If the client’s decisions, data, or implementation affect the result, say so rather than promising an outcome you cannot ensure.

• Buyer: Who has the problem and can agree to the work?
• Starting point: What must be true before the engagement begins?
• Finish line: What will the client receive, decide, or be ready to do?
• Evidence: What observable artifact or decision shows the work is complete?

2. Translate the promise into scope

Scope is the working agreement behind your outcome. List the deliverables, activities, timing, and client inputs that make the work possible. Deliverables should be tangible enough to review: a diagnostic, a prioritized recommendation, a workshop, or a written implementation sequence. Specify the format and limit of any ongoing support.

A compact scope can fit in five lines: what is included; how many sessions or review rounds; when delivery is expected; what the client must supply; and what marks completion. Use ranges only when uncertainty is real, and explain what changes the timeline.

3. Make boundaries explicit

State what is excluded, what depends on the client, and how you will handle work that changes after kickoff. For example, implementation may be separate from recommendations, or additional stakeholder interviews may require a revised scope. Use terms that match how you work.

Write a short “not included” section in plain language. A buyer should be able to tell before agreeing whether the offer includes execution, ongoing access, extra revisions, or work outside the named problem. Where a boundary depends on context, explain the trigger and how you will agree on the next step.

• Included: the specific deliverables and agreed touchpoints.
• Client responsibilities: access, information, decisions, or approvals needed.
• Not included: adjacent tasks outside this engagement.
• Change rule: pause and agree on revised scope, price, or timing before adding work.

4. Let scope inform the price

Price the defined engagement, not an unlimited version of your expertise. Consider delivery effort, complexity, risk, and the value of the decision or progress the client is buying. Be able to explain what the fee covers. If important parts of the scope are unknown, narrow the offer or make the first phase a paid diagnostic with a clear output.

Read the scope and price together. Can a buyer see why the work costs what it does? Can you deliver it without quietly adding unpriced work? If either answer is no, adjust the deliverables, boundaries, or price before writing promotional copy.

5. Turn the offer into buyer-facing words

Write a short explanation using the same outcome and boundaries: who it is for, what they get, what their part is, and what happens next. Keep the promise consistent across your page, email, and conversation.

6. Prepare a first-buyer launch plan

A launch plan should turn the offer into specific actions, not imply that buyers will appear on a schedule. Choose a small set of people or channels that plausibly reach the intended buyer. Prepare an offer explanation, a relevant invitation to talk, and a way to record questions or objections. Use responses to improve clarity; silence alone does not show whether the offer has value.

1. Day 1: finalize the offer statement and check that the promise matches the scope.
2. Day 2: prepare a page or document with deliverables, boundaries, and the next step.
3. Day 3: draft a personal message for a relevant contact or referral source.
4. Day 4: send tailored invitations and track them.
5. Day 5: review replies or questions and note unclear language.
6. Day 6: revise the offer explanation where feedback points to confusion.
7. Day 7: decide what to test next: buyer, problem framing, scope, or channel.

A final scope check

Before you share the offer, ask a prospective buyer to explain what they think they receive, what they need to contribute, and what happens if the request grows. If their understanding differs from yours, improve the wording before accepting the work. The goal is an offer that is understandable to buy and bounded enough to deliver.