For coaches, consultants, and fractional operators

Turn your recommendations into changes that stick.

Your client knows something needs to change. I help trace the problem, improve the workflow, and put the procedures, guidance, or tools into practice.

You keep the advisory relationship and wider strategy. I bring more than two decades in customer experience and operations to the follow-through.

Bring me a client workflow See the three ways to work together

Nothing is quoted, scoped, or promised to your client until I have reviewed the actual workflow.

One person
reviews the workflow and leads the agreed work
Written
scope and responsibilities agreed before anything is sold
Yours
your advisory relationship stays yours throughout

The gap

The recommendation is clear. The work stays the same.

You have probably already told a client some version of the list below. Knowing it should happen is rarely the hard part, and hearing it again next quarter is not what changes anything.

  • Give every inquiry an owner and a next step
  • Write down the process that lives in one person’s head
  • Stop retyping the same details into three different tools
  • Say the same thing to every customer, not whichever version somebody remembers
  • Prepare the team before a new service goes live
  • Find why customers keep asking the same question

The hard part is turning the recommendation into clear ownership, usable procedures, and tools people can work with. That is the follow-through I help deliver.

Ways to work together

Three ways to work together.

Which one fits depends on how involved you want to be, and how much of the client relationship you want to keep carrying yourself. You can use different ones for different clients.

  • Way 01

    Refer

    You make the introduction. I review the workflow and agree the scope directly with the client. You stay informed at the level agreed together.

    • Best when you have spotted a recurring problem and want someone to lead the follow-through.
  • Way 02

    Collaborate

    We agree who handles discovery, process design, tools, and adoption. I take the workflow work your engagement needs, with responsibilities written down before we start.

    • Best when a workflow improvement supports a larger advisory engagement you are already running.
  • Way 03

    Embed

    Implementation delivered inside your own client offer. Branding, client communication, pricing, and who answers the phone are all settled in writing before anything is sold.

    • Offered once we have delivered a client engagement together and each of us knows how the other works.
Bring me a client workflow

How you are paid is agreed in writing before anything is sold, and it depends on which of the three you pick. Ask on the first call and you will get a straight number.

Who handles what

The line is drawn on purpose.

Before work starts, we agree who owns discovery, decisions, delivery, and adoption. The split below is a starting point, shaped to each engagement.

What I handle

Workflow diagnosis and the agreed implementation.

  • Customer journey and workflow mapping
  • Root-cause review, ownership, and handoff design
  • Procedures, customer communication, and scoped tools
  • Testing changes and setting approval boundaries
  • Documentation the client keeps and controls
  • Training the people who will use it
  • Measures to check whether the change is helping
  • Automation where it fits the problem and scope
  • Follow-up support where it is included in the scope

What you handle

The client relationship and wider business context.

  • Spotting the business problem worth solving
  • The strategic context behind it
  • Helping the client make business decisions
  • Aligning sponsors and the wider engagement
  • Reinforcing the changes we agree together
  • The wider coaching or consulting relationship

You do not need to arrive with a tool specification. I review the customer experience and the work behind it, then bring the findings back to you before we recommend a scope.

How your reputation is protected

Built to protect the relationship you earned.

Your name is attached to everyone you introduce. So every partner engagement runs on the same written rules, and they do not bend for a deadline or a deal.

Principles are easy to write down. If you are about to put your name next to mine, go and look at the running systems instead:

see what I currently operate

Partner engagement standard

Form PS-01 · Applies to every introduction

  1. The workflow is reviewed before a scope is promised.

    No quote, no scope, no commitment until I have looked at the real workflow, the people involved, and the tools they use. We agree what can reasonably change.

  2. The scope goes in writing.

    The outcome, deliverables, boundaries, price, and responsibilities. Any tools, running costs, and ongoing support are spelled out before work starts.

  3. The client always knows who supports what.

    No wondering whether a question goes to you or to me. Your client gets one clear answer about who to call, and it is written down before launch.

  4. Sensitive actions sit behind an approval.

    Where tools handle customer-facing or high-impact actions, we agree approval rules, limits, and a human owner for exceptions before they go live. The controls form part of the scope and testing.

  5. Changes are checked and documented before handoff.

    Your client gets documentation they own and training on the revised workflow, so the team knows what changed and how to use it.

  6. Problems get surfaced, not hidden.

    When the agreed work reveals a dependency, limitation, or new problem, I raise it with you. After handoff, monitoring and support follow the arrangement the client has chosen.

  7. Access stays inside the project.

    Client data and system access cover what the agreed work actually needs, and the connection ends cleanly whenever the client says so.

The client needs a better way of working, with clear responsibilities and people prepared to use it. That is what the engagement should deliver.

Qualifying an opportunity

What kind of client problem fits.

Look for recurring customer confusion, missed handoffs, inconsistent procedures, or teams unprepared for a new service. The problem is specific enough to investigate and important enough for someone inside the business to own the change.

  • Fit 01

    Inquiries and follow-up

    An owner, a response procedure, and a clear next step so inquiries do not depend on memory.

  • Fit 02

    Repeat customer questions

    Trace recurring confusion to the messages, procedures, or handoffs creating it.

  • Fit 03

    Procedures people can use

    Turn knowledge in one person’s head into clear steps, decision guidance, and escalation paths.

  • Fit 04

    Readiness for a new service

    Check the customer journey, team guidance, ownership, and support paths before launch.

  • Fit 05

    Adoption and measurement

    Help the team use the revised workflow and agree how to tell whether the change is helping.

  • Fit 06

    Tools that support the workflow

    Use existing tools, scoped automation, or a small build where they address the cause of the problem.

A clearer procedure or a named owner may be the right first fix. When automation fits, the recommendation also covers what should stay human and who handles exceptions.

How an opportunity moves

From your conversation to a working change.

Five steps, and you can stop after any of them. Nothing reaches your client until you have seen it first.

  1. You bring the problem

    What the client is trying to improve, what happens today, and where it breaks down. A paragraph is enough to start. You do not need to know what the solution looks like.

  2. I review the workflow

    What customers experience, where the work breaks down, and what needs a closer look. The initial call checks fit; a detailed diagnosis belongs in an agreed paid engagement, with findings reviewed together.

  3. We pick the delivery model

    Refer, collaborate, or embed, based on how involved you want to be and what the client actually needs. Compensation is settled here, in writing, not after the fact.

  4. The client gets a written scope

    The outcome, deliverables, responsibilities, price, any tool costs, and the support arrangement. They sign knowing exactly what they are getting and who to call.

  5. I lead the agreed work through handoff

    I handle the agreed process changes, tools, testing, and team guidance. After handoff, my responsibility follows the support arrangement the client chooses. We check the change against the measures agreed in the scope.

Start here

Bring me one client workflow.

One real client, one recurring problem. Tell me what customers or staff keep running into, and what the business has already tried.

I will tell you whether it fits my experience and what an appropriate next step could be.

Partner enquiry

Form PE-01 · Read by Bryan Piard

You will talk directly with me about the workflow and the work it needs. What you send is stored so I can reply, plus your IP address to prevent abuse. See the privacy policy.

Or write to me directly: bryan@perseidechocreations.com · or call 425-243-3473