Client onboarding workflow automation: how it works and what it costs

What does client onboarding workflow automation actually automate?

Onboarding is usually where the handover breaks. Sales knows the deal is closed, delivery finds out two days later, and someone emails the client three times for the same file. Automation here is not about removing people. It is about removing the chasing and the re-typing.

The parts that are worth automating in most businesses:

• Trigger on signature or payment. A signed agreement or a paid deposit starts the workflow rather than a person remembering to start it.
• Intake in one place. One form or one portal login instead of a PDF, a shared drive link and three emails.
• Document collection with reminders. The system knows what is outstanding and chases on a schedule, so your account manager does not.
• Internal task creation. The delivery board, owner and due dates are generated from the deal record, not copied by hand.
• Scheduling. Kick-off call booking linked to the right person's calendar and the right meeting type.
• Status visibility. The client can see where they are without emailing to ask, and you can see every account stuck at the same step.

Our own Agentryx platform does a version of this: branded client onboarding from a single link, delivery boards shared between the agency and each client, and AI that turns a call summary into tasks and a draft follow-up email for a person to check. That last point matters. The AI drafts, a human sends.

Our advice, learned the expensive way: start with the one journey that causes the most chasing. Connect only what that journey needs. Add the rest once the first part is genuinely in use.

How much does client onboarding workflow automation cost?

There is no flagship package. Every build is scoped around what the business needs and already has. These are our standard commercial terms.

Engagement	UK price	US price	What you get
Paid audit	£3,000 + VAT	$5,000	Written report within 10 working days, mapping how the business runs, the tools it uses and where work gets stuck. Credited against the build if the build deposit is paid within 14 days of the report.
Scoped build	£5,000 to £20,000	$10,000 to $30,000	The automation itself, built in your accounts. Timeline agreed per scope.
Run & Improve (Care)	£1,000/month	$2,000/month	Optional ongoing support and improvements.
Run & Improve (Improve)	£2,000/month	$3,500/month	Optional ongoing support and improvements.
Run & Improve (Scale)	£4,000/month	$6,000/month	Optional ongoing support and improvements.

Retainers have a three-month minimum, then run monthly with 30 days notice. Payment on projects defaults to 50% upfront and 50% on launch, the audit is paid in full, and retainers are monthly in advance. The signed scope controls in every case. Scope, tax treatment, currency and service allowances are confirmed in writing before anything starts.

If onboarding needs a client portal

Many onboarding workflows end up as a portal, because the client needs a login to upload documents and track progress. Those are priced in bands:

Band	Price	Scope
Single client type	£4,500 to £10,000	Login, onboarding, files, messages, progress
Multiple roles	£10,000 to £20,000	Several roles, approvals, payments or integrations
Platform	£20,000 to £30,000+	Multi-role or white-label, complex workflows, AI, data migration

Portals take three weeks to three months from a signed scope. Larger custom projects are priced separately. Full detail is on our client portal pricing page.

Running costs sit outside this. Hosting, software, phone minutes and AI usage are paid directly to the providers from your own accounts, so you see the real bill and can switch provider without asking us.

What drives the price up?

• Number of roles. One client type is simple. Admins, coaches, sales, assistants and external partners each needing a different view is a platform.
• Approvals and payments. Anything that collects money or needs a sign-off before the next step adds states, permissions and failure paths.
• Integrations. Each system you connect is another authentication, another rate limit and another thing that can change under you.
• Data migration. Moving existing clients into a new onboarding system is often more work than the onboarding flow itself. See CRM migration pricing.
• Regulated steps. If a step involves financial promotions, legal commitments or regulated advice, it needs human approval designed in, not bolted on.

What pulls the price down: keeping what already works. If your CRM is fine, we build around it rather than replacing it.

When client onboarding workflow automation is not the right choice

We turn work down for these reasons regularly.

• An existing tool already fits without workarounds. If an off-the-shelf product does 90% of your onboarding and you are not fighting it, buy it. Paying £5,000+ to rebuild what a subscription already does is poor maths. Our view on that trade-off is set out in custom software vs SaaS.
• The process is still changing week to week. Automating a process you are still inventing means paying to rebuild it. Run it manually until it stabilises, then automate the version that survived.
• You need it next week. We do not promise a delivery time before a scope is signed. If the deadline is immovable and close, a shared checklist and a calendar reminder will serve you better.
• Volume is genuinely low. If you onboard two clients a quarter, the chasing is annoying but it is not a £5,000 problem.

The cheaper alternative

For many businesses, a no-code tool is the honest first step. Worth knowing how it is billed: in Zapier, each successful action step counts as a task, while triggers, filters and paths do not, and at your plan limit new runs are held unless you pay for extra tasks. That is fine at low volume and gets uncomfortable as onboarding volume grows and each client triggers dozens of actions. We compare the two routes in Zapier vs custom automation and no-code vs custom build.

How we build it: six stages

1. Audit. We map how the business runs, the tools it uses and where work gets stuck. Paid, £3,000 plus VAT, written report within 10 working days.
2. Design. A written scope covering systems, integrations, permissions and success measures. Nothing gets built from a conversation.
3. Build. Inside your own accounts, keeping what already works.
4. Test. Real cases, edge cases and failure paths, before anything touches a customer. What happens when a document upload fails or a payment bounces is part of the build, not an afterthought.
5. Launch. In stages, with the team trained and documentation handed over.
6. Improve. Review the numbers, agree the next changes. Optional, as a monthly retainer.

More detail on each stage is on our approach page, and the full service list is on solutions.

What this has looked like in practice

TMMB Academy, a TikTok Shop academy, came to us with a fragmented funnel, fragmented operating processes, rising software subscriptions and no single system. We built one portal with role-specific workspaces for admins, coaches, creators, sales, assistants and brands, covering onboarding, creator performance, subscriptions and payments, course modules, calls, messages, community resources, brand deals, deliverables and operational alerts. The implementation ran for more than 60 days. TMMB was able to take on greater capacity and improve scalability and retention, and reports generating six figures within roughly two to three months. That last figure is client-reported and shared with permission.

MRM Group, a UK property development and investment company, had a public funnel connected to GoHighLevel and needed an authenticated internal command centre for clients, deals and tasks. We built client and deal workspaces with agreement-before-payment flows, document handling, task workflows, reminders and audit history, plus operational reporting with human approval at sensitive financial-promotion and AI decision points.

Two Trustpilot reviews, verbatim: "When it comes to building systems to acquire clients, Quam is your guy." (Denzil Jones). "Quam introduced me to the idea of having a solid infrastructure and helped me build it." (Stefano Ezeokaka).

Where automation should stop and a person should start

Keep a human on decisions about money, legal commitments, complaints, and any message sent in your name. This is not caution for its own sake. In Moffatt v Air Canada (2024), a British Columbia tribunal held the airline liable for incorrect fare information its website chatbot gave a customer, and rejected the argument that the chatbot was responsible for its own actions. What your system says, you said.

The same applies to outbound contact. Under UK PECR, as the ICO explains, automated marketing calls need the person's specific prior consent, and general marketing consent is not enough. If your onboarding flow dials people, that needs designing properly.

Our principles on every build: it lives in your accounts, permissions are explicit, human review sits on anything sensitive, and handover is supported. Any AI in the system is limited to approved information, says when it does not know, hands over to a person, and tells people it is automated.

On speed, there is a reason the front of the journey matters. Harvard Business Review's "The Short Life of Online Sales Leads" (2011) found firms that tried to contact a web lead within an hour were nearly seven times as likely to qualify it as those that waited even an hour longer, and more than 60 times as likely as those waiting 24 hours or more. Of 2,241 US companies audited, 37% responded within an hour and 23% never responded. US data from 2011, but the logic carries into onboarding: the gap between a client saying yes and your system responding is where the doubt creeps in. See lead follow-up automation for the front half of that journey.