Consulting Engagement Setup

Consulting Engagement Setup: Scoping, Pricing, and Protecting the Work

This skill sets up an independent consulting engagement correctly from the start. Most first-time consultants either underprice the work, underscope the deliverables, or both. The result is an engagement that expands without additional compensation, produces resentment, and ends the client relationship faster than the work would have ended it naturally.

The goal of this skill is not to protect the consultant from the client. It is to create a clear shared understanding of what is being purchased so that both sides can evaluate whether the work was done correctly. Ambiguity in scope is not a negotiating advantage. It is a liability that collects interest until it is paid with a damaged relationship.

---

HOW TO SET UP THIS SKILL

Provide:

• What the client has asked for, in their words if possible
• How the conversation started (referral, inbound, prior relationship)
• Whether a rate has been discussed or if that conversation is

still ahead

• Your current read on what the client actually needs versus what

they asked for

• Any constraints: timeline, budget signals, internal politics

at the client

• Whether this is your first consulting engagement or you have

done this before

---

The Conversation Before the Proposal

The most important conversation in a consulting engagement happens before any proposal is written. Most first-time consultants skip it because they are eager to win the work. Skipping it is the reason most engagements go wrong.

The pre-proposal conversation has one goal: understand the problem the client is actually trying to solve, not the solution they have already decided they want.

A client who says "we need someone to clean up our HubSpot" may actually need attribution rebuilt because the CEO is asking why marketing cannot show pipeline contribution. Cleaning up HubSpot is one step in that solution, not the solution itself. A consultant who scopes to the stated request will finish the cleanup and leave the client unsatisfied because the underlying problem is unchanged.

Questions to ask in the pre-proposal conversation:

"What will be different about how you operate when this engagement is complete? How will you know it worked?"

"Who else has a stake in this outcome? Who will evaluate whether it was successful?"

"Has this been attempted before? What happened?"

"What is the cost of not fixing this? Is there a deadline or an event that is driving the timing?"

"What does success look like in 90 days? In six months?"

These questions accomplish two things. They reveal the real problem. And they demonstrate practitioner judgment before the engagement starts, which is the fastest way to establish rate credibility.

---

Scoping the Work

A scope has three components: what is included, what is excluded, and what success looks like. Most consulting proposals include the first component and omit the other two. That is where engagements go wrong.

---

What is included

Be specific about deliverables, not activities. "HubSpot audit and remediation plan" is a deliverable. "Review HubSpot workflows and provide recommendations" is an activity. Deliverables are evaluable. Activities are not.

For each deliverable, name:

• What you will produce
• What format it will be in
• Who will receive it
• When it will be complete

If a deliverable requires client input or access to proceed, note that explicitly. "HubSpot audit, delivered as a written report within two weeks of receiving admin access to the instance" is a scoped deliverable. The client knows what they will get, when, and what they need to provide to make it happen.

---

What is excluded

This is the section most consultants skip and the one that causes the most problems. Explicitly name the things the client might reasonably expect to be included but are not.

Common exclusions for a HubSpot or RevOps engagement:

Implementation of recommendations is not included unless specified. An audit produces a remediation plan. Executing the plan is a separate engagement.

Training or ongoing support is not included unless specified. If you produce a new workflow architecture, teaching the team how to use it is separate work.

Content creation is not included. If the engagement involves improving email programs, writing the email copy is not part of an operations engagement.

Integrations with third-party tools are not included unless specifically scoped. Connecting HubSpot to a new tool the client decides to buy mid-engagement is out of scope.

Name these explicitly in the proposal. It is not adversarial to say what is not included. It is professional. Clients who have worked with good consultants before expect it.

---

What success looks like

Define the success criteria in measurable terms before the engagement starts. Not aspirational terms. Specific metrics or observable outcomes that both sides can evaluate.

For a HubSpot audit and remediation: a prioritized list of identified issues with severity ratings, and a written remediation plan with estimated effort for each item.

For an attribution rebuild: a functional pipeline attribution report that shows marketing-sourced pipeline as a percentage of total pipeline, with a documented methodology.

For a training engagement: all named team members have completed the defined workflows without errors, verified by a defined test.

If success cannot be defined in measurable terms before the engagement starts, the scope is not clear enough to price accurately.

---

Pricing the Engagement

Pricing is where most first-time consultants make the mistake that is hardest to recover from. They price based on what they think the client will accept rather than what the work is worth. The result is an engagement that is resented from the inside.

---

Hourly versus project versus retainer

Hourly works when the scope is genuinely uncertain, the work is exploratory, or the client needs occasional input rather than a defined output. The risk is that hourly billing creates a ceiling on value: you are paid for time, not for outcome.

Project pricing works when the deliverable is well-defined and the effort is estimable. You quote a fixed price for a specific output. The risk is underestimating effort. The mitigation is building scope constraints and exclusions into the proposal. If the scope changes, the price changes. State this explicitly.

Retainer works when the client needs recurring access to your judgment rather than a one-time deliverable. A monthly retainer for a defined number of hours is appropriate for ongoing advisory, not for a project with a defined endpoint.

For a first engagement with a new client, project pricing is usually cleanest. It forces scope clarity on both sides and avoids the awkwardness of tracking hours.

---

How to arrive at a rate

The rate should reflect three things: the market rate for your expertise, the value of the outcome to the client, and the minimum you will accept to do the work well.

For a B2B SaaS RevOps or HubSpot consulting engagement at Director level:

Search for current market rates before quoting. Rates vary by market, specialty, and whether you are competing with agencies or independent consultants. Use this skill's web search capability to verify current benchmarks before the client conversation.

The value framing matters as much as the number. A rate of $150 per hour presented as "eight hours to complete a HubSpot workflow audit" sounds like $1,200. The same work presented as "a remediation plan that will reduce your sales cycle by identifying the workflow gaps that are costing you deals" sounds like a different investment. Both descriptions are accurate. The second one frames the value correctly.

Do not quote a range. A range signals that you are uncertain about the value of your work. Quote a number. If the client pushes back, understand their constraint before adjusting the price. Sometimes the right response to budget pressure is a narrower scope, not a lower rate.

---

The rate anchor conversation

If the client has not mentioned budget and you have not named a rate, someone needs to go first. Go first.

"For an engagement like this — a full HubSpot instance audit with a prioritized remediation plan — I typically work on a project basis. Based on what you have described, this would likely fall in the range of $X to $Y. Does that align with what you had in mind?"

Naming the range first establishes the anchor. If the client comes back lower, you are negotiating down from your number, not up from theirs. If the client says yes immediately, the rate may have been too low.

---

What to Put in Writing Before Starting

A written agreement does not require a lawyer. It requires clarity. At minimum, confirm in writing before any work begins:

The deliverables: Exactly what you will produce, in what format, by when.

The exclusions: What is not included.

The rate and payment terms: Total project price or hourly rate, payment schedule, and what happens if the scope changes.

Access requirements: What systems, data, or people you need access to, and who is responsible for providing it.

Intellectual property: Who owns the work product. For most consulting engagements, the client owns the deliverables. If you have proprietary frameworks or templates you are bringing to the engagement, note that you retain ownership of those.

Termination: How either side can end the engagement and what happens to payment if it ends early.

A short email that confirms these six items is sufficient for a first engagement. A formal statement of work is better for larger engagements or clients with procurement processes.

---

Handling Scope Creep

Scope creep is not the client being difficult. It is ambiguous scope producing predictable misalignment. The client asks for something they believe is included. The consultant believes it is not included. Neither side is wrong given the ambiguity.

The way to handle scope creep is not to say no. It is to make the trade-off visible.

"That is not part of the current scope, but I can include it. It would add approximately X hours to the engagement, which would adjust the project cost by $Y. Would you like to add it or keep the current scope and address it separately?"

This approach does three things: it confirms that you are tracking scope precisely, it gives the client a real choice rather than a refusal, and it establishes that scope changes have cost implications.

Do not absorb scope creep and resent it later. Name it in the moment and give the client the choice.

---

Deliver the Engagement Setup Plan

Output in this format:

CONSULTING ENGAGEMENT SETUP
Client: [company name or anonymous if not provided]
Engagement type: [audit, project, retainer, advisory]
Built: [today's date]

PRE-PROPOSAL CONVERSATION GAPS
[What the user still needs to learn from the client before scoping
accurately. Specific questions, not generic advice.]

RECOMMENDED SCOPE

Deliverables:
1. [Deliverable with format, recipient, and deadline]
2. [Continue as needed]

Explicit exclusions:
- [Item the client might expect that is not included]
- [Continue as needed]

Success criteria:
[Measurable outcome that defines completion]

PRICING RECOMMENDATION
Structure: [hourly / project / retainer and why]
Rate: [recommendation with reasoning, plus instruction to search
for current market benchmarks before the client conversation]
How to open the rate conversation: [specific language]

WHAT TO PUT IN WRITING BEFORE STARTING
[Short email or agreement structure confirming the six required
elements]

SCOPE CREEP RISK
[The one or two areas where the scope is most likely to expand
based on what the client has asked for, and the language to use
when it happens]

RED FLAGS IN THIS ENGAGEMENT
[Anything from what the user described that suggests the client
has unclear expectations, a misaligned understanding of the work,
or is likely to be difficult to satisfy. Named directly, not
diplomatically softened.]

---

Output Rules

• Always recommend searching for current market rates before the

engagement conversation. Rates change and stale information creates risk.

• If the user has not done the pre-proposal conversation, do not

produce a full scope. Produce the questions they need to ask first. A scope built on insufficient information creates problems that cannot be fixed after the proposal is accepted.

• Be direct about red flags. A client who cannot define success,

who has tried this before and failed, or who is using price as the primary selection criterion are real risks. Name them.

• Never recommend absorbing scope creep silently. Name the trade-off

every time.

• No em dashes. Use commas or periods.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: matellez
• Source: matellez/claude-skills
• License: MIT
• Homepage: https://linkedin.com/in/manuelvallestellez

Install and usage instructions live in the source repository linked above.