All posts
Consulting

How I Price Consulting Work

By Beatriz6 min read

Consulting pricing and proposal notes

People ask for "pricing" as if consulting work is one product.

It is not.

A focused positioning sprint, an ongoing fractional PMM engagement, and a one-off workshop create different kinds of value and carry different delivery risk. Pricing them the same would be lazy and usually wrong.

What am I actually pricing?

I price for the shape of the problem and the commitment required to solve it.

Usually the work fits one of these buckets:

  • -->a defined strategy sprint
  • -->a workshop or advisory block
  • -->a launch or messaging project
  • -->ongoing fractional PMM support

The clearer the scope and output, the easier it is to use a fixed fee. The more ambiguity, cross-functional coordination, or shifting priorities involved, the more likely I am to use a retainer.

When do I prefer fixed-fee pricing?

Fixed-fee works best when:

  • -->the problem is narrow
  • -->the deliverable is clear
  • -->the timeline is contained
  • -->dependencies are relatively stable

Examples:

  • -->positioning sprint
  • -->messaging workshop plus narrative doc
  • -->launch planning package
  • -->sales deck or enablement rewrite tied to a known scope

Clients usually like fixed-fee because it feels clean. I like it when the conditions above are true because it rewards focus.

When does a retainer make more sense?

Retainers make sense when the work is not just production. It includes ongoing judgment, sequencing, and adaptation.

That usually means:

  • -->weekly decision support
  • -->shifting priorities across product, sales, and marketing
  • -->multiple launches or narrative changes
  • -->ongoing review of assets and motion

Fractional PMM is usually not one project. It is an operating role. Pricing it like a single deliverable usually creates stress for both sides.

What makes pricing go wrong?

Under-scoped expectations.

The common failure mode is a client saying they need one thing, while the real job requires three upstream decisions and two downstream reviews. That is how a "quick messaging project" turns into positioning, website, launch planning, and sales enablement.

So before I price, I clarify:

  • -->what the client thinks the problem is
  • -->what I think the problem actually is
  • -->which outputs are included
  • -->what feedback loops are required
  • -->what is explicitly out of scope

If that part is vague, the proposal will be wrong no matter how good the number sounds.

How do I think about value without becoming abstract?

I do not price on "hours times rate" alone, but I also do not pretend value pricing is magic.

I use a simple blend:

  • -->complexity of the problem
  • -->scope of the work
  • -->speed and access required
  • -->commercial importance of the outcome

Example: helping a team prepare messaging for a major launch that influences pipeline this quarter has different value and urgency than a slower brand-thinking project. That does not mean infinite pricing. It means the commercial context matters.

What protects the working relationship?

Boundaries.

A strong pricing model needs:

  • -->clear scope
  • -->clear timeline
  • -->clear decision owners
  • -->clear revision limits or cadence

This is not about being rigid. It is about making the work sustainable enough to do well.

That is also why I prefer straightforward language in proposals. Clients should know what they are buying, how the work unfolds, and what success looks like.

How do I handle clients who want "a little bit of everything"?

I split the work into phases.

Instead of pretending one price will cover an undefined bundle, I say:

  1. -->here is the strategy phase
  2. -->here is the implementation phase if needed
  3. -->here is the ongoing support option if the team wants operating help

This protects scope and improves decision-making. It also helps clients buy the right amount of support for their stage.

What pricing principle matters most to me?

Price should make the work better, not more resentful.

If the structure encourages vague asks, constant overflow, or hidden expectations, it is a bad price even if the number looks attractive.

The right pricing model gives the client confidence and gives me enough room to do sharp work without burning the engagement down.