Protect Consulting Margin Before the Proposal

Margin usually gets damaged before the proposal is written.

The risk starts when you accept vague urgency, unclear decision authority, or a result that depends on work the client has not committed to doing. By the time the proposal goes out, those gaps feel like assumptions instead of risks.

Run the margin check first

Before you price the work, write down:

• the business result the client wants
• the visible deliverables you will own
• the decisions the client must make on time
• the work that is explicitly outside scope

If any line is missing, the margin risk is not pricing. It is clarity.

Name the pressure points

Most consulting margin leaks come from predictable pressure:

1. More stakeholders enter after kickoff

2. The client delays decisions but expects the same timeline

3. A deliverable becomes a standing support channel

4. Success criteria move after the work is underway

Put those pressure points in the proposal as operating rules. That keeps the conversation practical instead of defensive.

Price the delivery model, not just the output

A simple deliverable can still require a complex delivery model. Weekly executive reviews, async stakeholder feedback, and fast-turn revisions all cost time.

If the operating model is heavy, the price should reflect that. If the client cannot support the model, reduce the scope before you reduce the fee.

Protecting margin is not about charging more by default. It is about making sure the promise, process, and price describe the same engagement.

[Build cleaner consulting engagements](https://getconsultkit.com)