Case Study

Case Study: Coaching Practice Client Journey Automation

We built a connected client journey for a small executive and career coaching practice: a CRM pipeline with consented nurture, qualified discovery call booking, proposal-to-onboarding sequencing, AI-drafted session notes the coach approves and payment plans with kind reminders. The coach now spends less time on admin between sessions, and every coaching, pricing and fit decision is still theirs.

Practice type
Executive and career coaching, one-to-one packages and retainers
Team involved
Founding coach, an associate coach and a part-time assistant
Systems connected
CRM, scheduling, video, e-signature, Stripe, email platform, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Leads came from talks, podcasts, a guide and referrals, and most sat in a newsletter list with no follow-up.

An open booking link filled the calendar with poor-fit calls, and no-shows were common across time zones.

Proposals went quiet, and onboarding steps were sent separately and out of order.

Session notes were written late at night, and payment plan chasing was handled personally and reluctantly.

Goals

What the project had to change

  • Every lead is tagged by source and gets a consented next step.
  • Discovery calls are booked by good-fit prospects who turn up.
  • Onboarding runs in the right order and clients arrive prepared.
  • Recaps go out the same day with the coach's approval.
  • Payments are chased kindly without the coach doing it personally.

What we built

What we built, as one connected system.

01

CRM and nurture

We connected the guide, webinar sign-ups, contact form and referrals to one CRM pipeline with source tags, a short consented nurture sequence and warm-lead nudges.

Service details
02

Discovery calls

A discovery page with four qualifying questions, routing to the calendar or a free resource, a pre-call brief and reminders in each prospect's time zone.

Service details
03

Proposals and onboarding

Polite proposal follow-ups, then contract, first payment, intake questionnaire and welcome pack released in order, plus a proper offboarding with feedback and honest testimonial requests.

Service details
04

Session notes

With recorded consent, Zoom transcripts become draft notes and action items in the coach's template, approved before the recap is sent, and raw transcripts are deleted on schedule.

Service details
05

Payments and renewals

Payment plans and retainers on Stripe Billing with kind reminders, failed-payment follow-up and renewal prompts before a package ends.

Service details

Architecture

How the practice's workflows connect

Forms and pages Leads, bookings Zoom sessions Transcripts Stripe Payment events n8n Five workflows AI drafting Briefs, notes CRM Pipeline, clients Client messages Email, reminders Coaches Approve, decide Assistant Admin follow-up Monthly summary Leads and money
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Forms, Zoom transcripts and Stripe events feed one n8n instance.
  2. 2 Five workflows update the CRM, send client messages and use an AI step for call briefs and note drafts.
  3. 3 Coaches approve notes and make every coaching and pricing decision; the assistant handles admin follow-up.
  4. 4 A monthly summary shows leads, calls, clients and payments.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What clients see

  • A useful guide and a few helpful emails after signing up
  • A short form, then a discovery call in their own time zone
  • Onboarding in a clear order
  • Same-day recaps after sessions
  • Kind payment reminders

What the coaches see

  • One pipeline with sources
  • A brief before each discovery call
  • Draft recaps to approve
  • Alerts only when a person is needed

What the automation does

  • Captures, books, reminds and chases on schedule
  • Checks consent before any recording is used
  • Never coaches, sets prices or publishes a testimonial without permission

Edge cases and fallbacks

A client declines recording
Nothing is recorded; the coach writes that client's recaps.
A prospect is borderline on routing
Booked with a flag for the coach to judge on the call.
A payment fails twice
The coach is alerted to talk to the client personally.
Unhappy feedback at offboarding
No testimonial request is sent.
A tool or n8n outage
Events are queued and replayed, and the assistant is alerted.

Integrations

What we connected

All integrations

Calendly

Scheduling

Discovery calls and sessions, reschedules and cancellations written to the CRM.

Calendly API and webhook subscriptions.

HubSpot

CRM

Contacts, deals, pipeline stages and tasks.

HubSpot's CRM REST API.

Stripe

Payments

Payment plans, retainers, invoices and failed payment follow-up.

Stripe Billing API and webhooks.

Zoom

Video sessions

Session links and, with consent, cloud recording transcripts for note drafts.

Zoom Meetings API cloud recording endpoints.

Kit

Email marketing

Lead magnet delivery and consented nurture sequences.

Kit public API.

DocuSign

E-signature

Coaching agreements and consulting contracts.

DocuSign eSignature REST API and Connect webhooks.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We walked through one client journey end to end, mapped tools and data, and agreed consent wording, retention rules and what stays with the coaches.

  2. 02

    Design and access

    Week 2

    Pipeline stages, routing rules, message wording in the coaches' voice, note template and access to each tool.

  3. 03

    Sprint 1: CRM

    Week 3

    Built lead capture, source tags and the nurture sequence; checked with live sign-ups.

  4. 04

    Sprint 2: discovery calls

    Week 4

    The CRM went live. Built the discovery page, routing, brief and reminders.

  5. 05

    Sprint 3: onboarding

    Week 5

    Discovery booking went live. Built proposal follow-ups, onboarding order and offboarding.

  6. 06

    Sprint 4: session notes

    Week 6

    Onboarding went live for new clients. Built consent capture, transcript drafting and approval for consenting clients.

  7. 07

    Sprint 5: payments

    Week 7

    Session notes went live. Built Stripe plans, reminders, failed-payment follow-up and renewal prompts.

  8. 08

    UAT and handover

    Week 8

    The coaches and assistant ran user acceptance testing on every workflow, then we switched everything on, handed over the run book and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures and tags leads and sends consented nurture emails
  • Routes discovery applications and sends reminders
  • Releases onboarding steps in order and chases gaps
  • Drafts session notes from consented transcripts
  • Sends payment reminders and failed-payment links
  • Prompts renewal conversations before packages end

The team does

  • Follows up warm leads and admin questions
  • Checks onboarding status and helps clients with forms
  • Marks offline payments and keeps records tidy
  • Reviews the monthly summary with the coaches

Coach or consultant decides

  • Decides fit and what to offer each client
  • Approves every session recap before it is sent
  • Sets prices, terms, refunds and pauses
  • Decides when to refer a client to another professional

Compliance handled

Privacy, consent and safety, built in.

Recording consent

Consent is captured at onboarding and confirmed each session; California requires all-party consent to record a confidential conversation.

Source: california.public.law

Coaching ethics and AI

The ICF Code of Ethics extends confidentiality to any technology used, including AI, so drafts stay private and are approved by the coach.

Source: coachingfederation.org

Email marketing rules

Nurture emails carry a physical address and an opt-out honoured within 10 business days under CAN-SPAM.

Source: www.ftc.gov

Honest testimonials

Testimonials are requested only from happy clients, in their own words, with permission, in line with the FTC rule on fake reviews and testimonials.

Source: www.ftc.gov

Sensitive information

Intake and session data can include health details, special category data under Article 9 GDPR, so collection is minimal and transcripts are deleted on schedule.

Source: gdpr-info.eu

Outcomes

What changed for the practice

  • Every lead is tagged by source and gets a consented next step.
  • Discovery calls now come with a brief, and fewer poor-fit calls reach the calendar.
  • Clients move from yes to first session in a clear order, usually with their intake done.
  • Session recaps go out the same day, approved by the coach.
  • Payment reminders run on their own, and the coaches step in only when it matters.

What we track

The measures the practice watches.

Lead to discovery call

Share of leads by source who book a discovery call.

Show rate

Discovery calls attended versus booked.

Proposal to client

Proposals signed and days from yes to first session.

Recap timeliness

Share of sessions with an approved recap sent the same day.

Payments

Overdue amounts and failed payments recovered each month.

Renewals

Renewal conversations held before packages ended and renewals agreed.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Journey mapping, data flows, wording and the backlog for all five workflows.

    $1,000 – $2,000

  • CRM and nurture module

    Lead capture, tags, nurture and nudges.

    $700 – $1,700

  • Discovery call module

    Booking page, routing, brief and reminders.

    $800 – $2,000

  • Onboarding module

    Proposal follow-ups, onboarding order and offboarding.

    $800 – $2,000

  • Payments module

    Stripe plans, reminders and renewal prompts.

    $500 – $1,300

  • Session notes module

    Consent capture, drafting, approval and retention.

    $700 – $1,600

  • Integrations

    CRM, scheduling, Zoom, Stripe and email platform.

    $200 – $400

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $300 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every practice gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM, scheduling and email: The vendors' own plans.
  • Stripe: Stripe's standard processing fees on the practice's account.
  • n8n: Self-hosted Community edition on the practice's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • AI usage: Pay-per-use AI model fees, usually small at practice volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your coaches & consultant?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call