The Fractional Playbook + How to Get Steady Monthly Clients

How to Get Steady Monthly Clients

One of the biggest fears when moving from hourly pricing to monthly retainers is scope.

How to Get Steady Monthly Clients

Monthly retainers don’t need vague scope.
They need a simple rule: talk outcomes early, lock scope once there’s a yes, and use addendums when the work changes.


Key takeaways

  • Don’t lead with legal language. Lead with outcomes.

  • Scope becomes real in the SOW, not the first call.

  • Addendums prevent awkward “free extras” without killing momentum.

  • When clients push back, you return to the original scope and offer options.

  • You can price add ons without going back to hourly.


I hear this a lot:

“I’m worried I’ll say yes to too much. How do I know what’s in scope and what’s an add on?”

Fair concern.

When you stop selling hours and start selling a monthly engagement, you need boundaries that don’t feel like a 12 page contract on day one.

Here’s the pattern that works in real life.


Step 1: the meeting (talk like a human)

This isn’t the moment for lawyer speak.

It’s the moment for clarity.

You’re showing them you have a plan, not selling time.

Example:

“Month 1 we’ll figure out what’s broken. Month 2 we’ll run a few tests and get signal. Month 3 we’ll make it repeatable so you’re not reliant on me.”

No hours.
No list of deliverables.
Just what gets better over time.


Step 2: the follow up (make it feel official)

After the call, you send the same plan as bullets.

This is the “structured, not rigid” layer.

Example:

90 day outcomes

  • Month 1: audit + interviews → clear gaps and priorities

  • Month 2: testing cadence + 2 to 3 studies → steady flow of insights

  • Month 3: insights system + team training → work that sticks

This gives confidence without forcing the entire contract conversation yet.


Step 3: the yes (this is where scope lives)

When they agree, now you formalize it.

Scope belongs in Schedule A of the contract.

Same bullets, just more specific.

Example:

Schedule A: scope of work

  • Month 1: research audit + 4 to 6 stakeholder interviews. Short report on gaps and priorities.

  • Month 2: establish testing cadence + run 2 to 3 usability studies. Findings and recommendations.

  • Month 3: build an insights repository + train the team. 90 day plan for continuing without me.

  • Add one simple guardrail

    This is the line that prevents most problems:

    Anything outside Schedule A becomes a separate addendum.

    That’s it.


    Step 4: the curveball (handle scope creep cleanly)

    A few weeks in, they ask:

    “Can you also run a workshop for our new product line?”

    This is where people either:

    • say yes and resent it later, or

    • say no in a way that feels rigid

    Better move:

    “Happy to do that. It’s not in our current scope, so let’s add it as an addendum.”

    Then you send a mini scope. Same format. Clean and consistent.


    The pushback you’ll get (and what to say)

    “I was hoping this would be included.”

    Response:

    “I get that. The reason we wrote Schedule A is so we both know what ‘included’ means. We can absolutely do this, but it’s additional work. Two options: we swap it with something already in scope, or we add an addendum.”

    That keeps it calm. No debate. No guilt.


    How to price addendums without going back to hourly

    Keep it tied to the original rate so it feels fair.

    Three simple options:

    1. Trade
      Swap one item out, bring the new item in. Same fee.

    2. Extend
      “This adds about two weeks of work, so we extend the engagement by two weeks at the same monthly rate.”

    3. Add a project fee
      “This is a discrete push. We’ll scope it and price it as a one off add on.”

    You’re not charging for minutes.

    You’re charging for more surface area.


    The point

    This is the natural sequence:

    • Meeting: outcomes, plain language

    • Follow up: outcomes as bullets

    • SOW: bullets with dates and guardrails

    • Addendum: bolt on when work changes

    Conversational when you’re building trust.
    Structured when you need clarity.
    Contractual only when you need protection.

    Thanks for reading,
    Gev