client onboarding automation

Onboarding that chases documents so your team doesn't

Intake, document collection, reminders and status tracking, automated from signature to kickoff. 5x ROI in 30 days. Or we work for free.

Teams we build for

  • Hoyes Michalos
  • Nurse Next Door
  • Fedi
  • UBC Sauder
  • Merchant House Capital
  • Picton Investments
  • Campbell Froh May & Rice LLP
  • Barnakl
  • Hungerford
  • Breez

The problems this solves

01

The gap between signed and started eats goodwill.

The client said yes weeks ago. They are still waiting for a kickoff because three documents are missing.

02

Document chasing is a full-time job nobody was hired for.

Polite reminder number four, written by hand, by your most expensive admin.

03

Nobody knows where any file stands.

Status lives in someone's inbox. When they are away, onboarding stops.

04

Intake data gets typed twice.

Once into the form, once into the system. Errors ride along both times.

05

Compliance checklists are remembered, not enforced.

ID checks and engagement letters happen when someone recalls them. That is not a process, that is luck.

What we build

01 · Intake

Structured intake that captures everything once and writes it everywhere it needs to go.

02 · Document requests

The system knows what each engagement needs and asks for exactly that, automatically.

03 · Reminders

Escalating sequences that pursue missing items politely and relentlessly until every document is in.

04 · Verification and filing

Incoming documents checked for completeness and filed in your storage, in your structure.

05 · Status dashboard

One view of every onboarding in flight, so nobody asks an inbox where things stand.

06 · Handoff

When the file is complete, the kickoff triggers itself and the delivery team gets everything in one package.

What's included

  • Intake forms, request logic and reminder sequences built for your engagement types
  • E-signature flow wired in
  • Status dashboard in your stack, not another login
  • Team training plus monitoring and iteration after launch. Cancel anytime

Weeks, not quarters.

How the full engagement works

01 Discovery

WEEK 0

02 Prototype

WEEKS 1-3

03 Deploy & train

WEEKS 4-8

04 Run & improve

WEEK 9+

How we build it

Step 01

Define done before automating the chase.

Most onboarding delay is nobody agreeing what a complete file is. We write that down first, which is usually the highest-value hour of the engagement.

Step 02

Automate the chase, measure the gap.

Reminders and document extraction run on a schedule. Time-to-complete is measured against the baseline recorded in step one.

Step 03

Assemble the pack last.

Engagement letters and document packs generate from verified parameters. A person releases every one.

What we will not automate

Signing, filing, or accepting an incomplete file as complete. The system tells you what is missing, it does not decide the risk is acceptable.

How it is built

See the full stack

Retrieval

Your engagement letters, intake requirements and prior client files are indexed, so the system knows what a complete file looks like for this kind of client instead of asking for a generic checklist.

  • pgvector
  • Full-text BM25
  • Document layout extraction

Agents and orchestration

Intake chase, document extraction and pack assembly run on a schedule. The agent knows what is missing and who owes it, and escalates to a person when the gap stops moving.

  • agent-worker
  • Scheduled runs
  • Escalation handoff

Evaluation

Extraction is graded field by field against files your team has already onboarded, so nobody has to trust that it reads a statement or an ID correctly.

  • Eval graders
  • Field-level accuracy
  • quality-worker

Models

Document models for intake forms, statements and identification. Frontier models for drafting engagement letters from parameters. Rules for the completeness check, because that should be deterministic.

  • Document layout extraction
  • Frontier models, one gateway, routed per task
  • Deterministic rules

Data boundary

Client data is scoped per engagement at the database layer from the first upload, before anyone has decided whether the client is onboarding at all.

  • Supabase row-level security
  • Per-engagement scoping
  • No-training API terms

Named tools in this build: Claude · Supabase · PandaDoc · Slack · Integration catalog

FIG. 01
Client onboarding: how the system fits togetherIntake forms, Client documents, Your CRM feed a hybrid index. The agent runtime works from that index, and every consequential action passes a human approval before it reaches Workflow builder, Task board, Approval queue.Intake formsClientdocumentsYour CRMHybridindexAgentruntimeYourapprovalWorkflowbuilderTask boardApproval queueYour systemsWhere your team works
Client onboarding: how the system fits together.REV 2026.08

What that means in practice

Vision, documents and speech

AI for eyes and ears: reading documents, watching camera feeds, transcribing calls.

Where we stop. Bespoke computer vision is justified by volume and latency, not by novelty. Below that bar, a vision-language model on demand is cheaper to run and easier to maintain, and we will tell you which side of the bar you are on before anything is built.

How we use it

Agents and orchestration

AI that does the work instead of just answering: looks things up, calls your systems, completes multi-step tasks, and knows when to hand off to a human.

Where we stop. Multi-agent swarms are oversold; most jobs need one well-guarded loop. If a cron job and a script solve it, that is what we build, because 90 percent per-step accuracy compounds to 59 percent over five chained steps and no framework changes that arithmetic.

How we use it

Security, privacy and governance

Keeping your data yours, and your AI safe to put in front of customers.

Where we stop. We do not claim certifications we do not hold, and we will not ship a customer-facing agent without a human gate and an eval suite. If a vendor cannot offer no-training terms, it does not get into the stack.

How we use it

Questions? Straight answers.

Three ways in. No long discovery.

Free · 3-5 days · No obligation

AI Opportunity Audit

We map your operations, find the highest-ROI automations, and hand you a ranked plan with payback math. Yours to keep, whoever builds it.

No obligation. No follow-up sequence.

Paid · Fixed scope

First Build

One high-ROI system, built on your real data and deployed in your stack, with your team trained to run it. Fixed scope. Quoted after the audit. Covered by the 5x ROI guarantee.

Scope my first build

Paid up front. Cancel anytime after.

Free · 15 min

Intro Call

Fifteen minutes with James, not a sales rep. Bring your worst bottleneck, leave with a straight answer.

Book 15 minutes

No pitch deck.

Every first build is covered: 5x ROI in 30 days. Or we work for free. Read the full terms

Start free. Know your number in five days.

A 3 to 5 day audit of your operations, ending in a plan with the ROI math attached. No obligation.

5x ROI in 30 days. Or we work for free.