Fixed quote after a free call

Client onboarding for coaches and consultants, in the right order every time

We build one flow from "send me something" to the first session and from the last session to the testimonial: polite proposal follow-ups, then contract, invoice or payment plan, intake questionnaire, welcome pack and first-session booking released in the right order, with reminders for anything not done. At the end it sends a summary, a feedback form and, for happy clients, an honest testimonial request. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why proposals go quiet and onboarding feels messy

A prospect says "send me something", the proposal goes out and then nothing. Many coaches feel awkward chasing, so warm opportunities cool off for want of one well-timed message.

When someone does say yes, onboarding is stitched together by hand: a contract from one tool, an invoice from another, an intake form sent late and a welcome email forgotten. Clients arrive at session one without the prep, and the last session ends without a proper close, a feedback form or a referral ask.

What we build

What our coaching client onboarding automation includes

Proposal follow-ups

Two or three well-spaced, genuinely helpful follow-ups after a proposal, stopping the moment they reply or sign.

Onboarding in order

Contract, then invoice or payment plan, then intake questionnaire and welcome pack, then first-session booking.

Gentle reminders

Nudges for unsigned contracts, unpaid first invoices and unfinished questionnaires.

Intake summary

A short summary of the questionnaire for you to read before session one.

Offboarding

A wrap-up summary, a feedback form and resources at the end of the engagement.

Honest testimonial requests

Requests only to clients who said they were happy, in their own words, with permission before publishing.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Proposal sent

    Sending a proposal starts a short, polite follow-up sequence.

  2. 02 Automated

    Signed and paid

    Contract signature and first payment release the intake and welcome pack.

  3. 03 Automated

    Prep chased

    Unfinished steps get reminders, and you get an intake summary.

  4. 04 Coach reviews

    Coach reviews

    You read the intake and approve offboarding and testimonial messages.

  5. 05 Coach or consultant decides

    Scope and terms

    Pricing, scope, refunds and what is published are decided by you.

How it behaves

How proposals and onboarding behave

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

What the client sees

  • A few helpful follow-ups after a proposal
  • Contract, payment and intake in a clear order
  • A proper close and a feedback form at the end

What the coach sees

  • Signed, paid and prepped status at a glance
  • An intake summary before session one
  • Offboarding and testimonial messages to approve

What the automation does

  • Releases each step only when the last is done
  • Sends reminders with stop rules
  • Never publishes a testimonial without permission

Edge cases and fallbacks

Client signs but payment fails
Intake waits; a payment reminder and a note to you go out.
Client wants a custom package
You adjust the proposal manually; the sequence restarts from signature.
Unhappy feedback at offboarding
No testimonial request; the feedback comes straight to you.
Contract or payment tool outage
Steps are queued and retried, and you get an alert.

Architecture

Proposal to onboarding to offboarding at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Proposal sent CRM or portal n8n workflow Order and timing Contract and pay E-sign, Stripe Intake and pack Questionnaire Intake summary For the coach Coach Reviews, decides
  • Input
  • Logic and services
  • Output
  • AI step
  • People

How it flows

  1. 1 Sending a proposal starts a short follow-up sequence that stops on reply or signature.
  2. 2 Signature and first payment release the next steps in order.
  3. 3 The intake questionnaire and welcome pack go out, with reminders for anything unfinished.
  4. 4 You read a short intake summary before session one, and approve the offboarding messages at the end.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Proposals, client onboarding & offboarding project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Offers, current proposal and onboarding steps, tools for contracts, payments and forms.

  2. 02

    Design

    2 to 3 days

    Step order, follow-up timing, reminder wording, offboarding and testimonial flow.

  3. 03

    Build

    1 to 2 weeks

    Follow-ups, onboarding sequence, reminders, summary and offboarding.

  4. 04

    Shadow run

    About 1 week

    A test client runs end to end, then a real one with you watching.

  5. 05

    Launch

    1 to 2 days

    Switch on for new clients.

  6. 06

    Support

    Ongoing

    New offers, contract changes and wording edits.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Dubsado or HoneyBook via Zapier, or HubSpot DocuSign or your portal's contracts Stripe Payment Links or Billing Your form tool for intake Claude or OpenAI for intake summaries

Cost estimate

What it costs, line by line.

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

    Step order, timing and wording.

    $200 – $400

  • Build

    Follow-ups, onboarding sequence, reminders and offboarding.

    $500 – $1,300

  • Integrations

    Portal or CRM, e-signature, payments and forms.

    $150 – $400

  • Testing and shadow run

    End-to-end test client and a watched live run.

    $100 – $250

  • Launch and training

    Switch-on and walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. E-signature, payment, form and n8n plans are billed to you directly. If you already use Dubsado or HoneyBook workflows, we extend them rather than replace them.

Monthly running costs you pay directly

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

  • Client portal or CRM: Your Dubsado, HoneyBook, Paperbell or HubSpot plan.
  • Payments: Stripe's standard processing fees on your account.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

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

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: honest testimonials

The FTC rule bans fake or false testimonials, including AI-generated ones, and buying reviews that express a set sentiment, so requests ask for the client's own words.

Source: www.ftc.gov

Confidentiality of client records

The ICF Code of Ethics asks coaches to keep records, including electronic files, in a way that protects confidentiality, security and privacy.

Source: coachingfederation.org

EU and UK: sensitive information

Intake answers can include health information, a special category under Article 9 GDPR, so questionnaires ask only what you need and stay in tools under contract.

Source: gdpr-info.eu

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.

FAQ

Proposals, client onboarding & offboarding questions, answered.

Two or three short, helpful messages spaced a few days apart, each adding something useful, and stopping the moment they reply. The workflow sends them so you never have to remember.

Contract first, then payment, then intake and welcome materials, then the first session booked, with reminders for anything outstanding. Clients arrive prepared and you start strong.

Yes. Both have built-in workflows; we extend them through their Zapier triggers and actions to reach tools they do not cover, such as your CRM, Slack or a custom intake summary.

Only to write you a short summary. You read the original where it matters, and nothing in it is acted on automatically.

Only clients who told you they had a good experience are asked, in their own words, with permission before publishing and any incentive disclosed. No gating, no invented quotes.

Proposal-to-client rate, days from yes to first session, share of clients who complete intake before session one and testimonials received.

Free 20-minute call

Want this 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