What happens today

Every start is reinvented, and something gets forgotten.

The work is done with care. It's the list of what needs doing that only exists in someone's head.

01

No checklist, or one nobody follows

Contract, access, billing details, first meeting: the order changes from one customer to the next, and a step ends up skipped.

02

A document is missing, but which one?

The file sits waiting. You ask again for a document already received, and forget the one that's actually missing.

03

Who takes over?

The information is shared verbally. The next person doesn't know what's been done or what they should do.

How it works

One journey per customer type, one document checklist, one owner at every step.

The workflow compares what's been received with what's expected, updates the status and prepares the requests. Decisions stay with the team.

Step 01

The journey starts on its own

As soon as a quote is signed or a form is filled in, the customer gets their journey: steps, expected documents, an owner and due dates. A welcome message explains what will happen.

Step 02

Documents are detected and filed

A document received by email or dropped in a shared folder is recognised, matched to the right customer and ticked. A request for what's missing is prepared, to review before sending.

Step 03

Each step hands over

When a step is complete, the next one opens and the person concerned is notified with the context. The customer sees where they stand.

What changes

Before and after: what actually changes.

The care given to each customer doesn't change. Its consistency does.

SituationTodayWith the workflow
Starting a new customerFrom memory, differently every timeOne journey per customer type, the same for all
Documents to gatherRequested as you go, sometimes twiceList known from the start, gaps spotted as each one arrives
The customer knows where they standIf they callMessage at every completed step
Handing overVerbally, or not at allNotification to the right person, with context
OverviewNoneEvery customer being onboarded, their step, their gaps
You stay in control

What stays in your hands.

The start of a relationship is your responsibility. The workflow organises the information, it doesn't decide on substance.

You define the journeys

Each customer type has its steps and its document list. They can be changed without technical help.

Requests are reviewed

A document request is prepared, never sent without approval. You can automate simple cases later.

Documents stay with you

Documents are filed in your own storage, not copied elsewhere. The workflow reads and sorts, it keeps nothing.

Exceptions are flagged

Unreadable document, duplicate, customer outside the standard journey: the situation is flagged to a person, never handled silently.

Tools involved

Your current tools, connected together.

The workflow plugs into the tools you already use. Compatibility is checked for your case, never assumed.

n8nn8n· orchestration AirtableAirtable· shared database Your mailbox· intake and detection Your storage· Drive, OneDrive, Dropbox BrevoBrevo· message sending E-signature· possible trigger
“A well-welcomed customer asks fewer questions, sends their documents faster and stays longer.”Design principle
Illustrative scenario

An accounting firm, a new client.

A fictional example to show the sequence. The timings and rules are the ones you would choose.

Monday

Engagement letter signed

The e-signature triggers the “new self-employed client” journey: 6 steps, 9 expected documents, owner Sophie. A welcome message goes out with the list.

Tuesday

Four documents received

The client emails four documents. They're recognised, filed and ticked. Five are missing, the list is current.

Thursday

Request prepared

An email listing the five missing documents is prepared. Sophie removes one not needed in this case, sends.

Following Monday

File complete, hand-off

The last document arrives. The “documents” step closes, the “setup” step opens. Marc is notified with the file link and summary.

Week 3

First meeting

The client receives the booking link for their first review. The sheet shows where every client being onboarded stands.

Illustrative scenario: the timings, messages and rules are examples. They are defined with you, from your tools and the way you work. An illustration is not a promise of results.

Frequently asked

Before you ask.

Where do we start if all our customers are different?

With the most frequent customer type. We list its steps and documents, and connect the document intake. Other journeys come later, if relevant.

Does the workflow read the content of documents?

It recognises the document type to file and tick it. It makes no decision on its content. A doubtful document is flagged to a person.

What about sensitive data?

Documents stay in your own storage. We define together what may transit, and we ask you never to share confidential documents during the test phase.

Does the customer see their progress?

If you wish: a message at every completed step, or a simple tracking page. You decide the level of detail.

Going further

The other workflows we look at with you, and Kayo's creative arm.

Next step

Which task would you like to stop redoing the same way?

Describe what repeats, the tools involved and what you would like to improve. No need to have chosen a solution yet.