Business automation / Customer Onboarding
CUSTOMER ONBOARDING

Every new customer means the same admin.

Turn an explicitly accepted job into a project folder, a checklist, an information request and approved welcome messages.

Illustrative workflow · example steps
  1. 01Job accepted
  2. 02Human check
  3. 03Project & checklist
  4. 04Welcome & request

Agreed rules. Visible exceptions. A person in control.

ILLUSTRATIVE EXAMPLE · FICTIONAL DATA

An accountant welcomes an accepted client

Acceptance creates a client folder and checklist, then prepares an approved information request. Staff check access and missing documents.

Client
Example Trading Ltd
Acceptance
Recorded by account owner
Workspace
Folder and checklist created
Next action
Review information request
HOW IT WORKS

A clear start. An agreed next step.

The trigger

An authorised person marks a job accepted, or an agreed system records the customer's explicit acceptance.

The actions

  1. Create the agreed project folder or client workspace once.
  2. Copy the approved checklist and prepare the information request.
  3. Send the approved welcome message and notify the project owner.

Where people stay involved

You confirm acceptance and any required agreement or payment checks before the workflow starts. You approve the checklist and messages. Staff decide whether the returned information is sufficient to begin work.

When it stops

An enquiry or draft quote cannot start onboarding. Closed jobs stop pending actions. A repeated acceptance reuses the original workspace rather than creating another.

YOUR PART & THE SETUP

Built around the way you work.

What I need from you

  • Accepted job reference, customer contact details and project owner
  • Folder location, naming rules, checklist and approved welcome wording
  • Access to storage, task system and business email; agreed agreement/payment gates

Use named, permissioned access rather than sending passwords in an enquiry.

Example applications

SharePoint or Google Drive for folders; Microsoft Planner, Trello or an existing client portal for tasks; Outlook or Gmail for messages.

Examples are subject to compatibility, subscription and access checks. A connection is confirmed during scoping.

Included in the agreed setup

  • Define the acceptance gate and project naming rules
  • Build one folder/checklist template and information request
  • Test repeat acceptance, missing information and interrupted setup
  • Document failure handling, controlled retries and a manual fallback
  • Provide the workflow map, configuration notes and a handover walkthrough
SETUP, RUNNING COSTS & OWNERSHIP

Know the cost. Keep control.

Start with the applications you already use. Review the setup cost, running costs and handover together before you decide to go ahead.

A quote built around your working day

Show me the task you want to improve. I’ll map the steps and quote for connecting your applications, checking the workflow and showing you how to use it. You can review the cost before committing.

Storage, task-management seats, electronic signatures or additional mailboxes may add charges when included in the agreed process.

Ownership and handover

Your written quote confirms what is included, responsibilities, exclusions and any applicable VAT. Your accounts belong to you, with subscriptions normally paid directly to suppliers.

You receive a workflow map, configuration notes, template copies and a walkthrough. Access is granted through your accounts, with the permissions needed for the job. We agree how CDM access is removed or retained at handover.

Running costs are separate

  • Automation platform subscription and usage allowance
  • Additional email accounts or software upgrades
  • Paid CRM/API access, forms, electronic signatures, SMS, storage or document processing where required
  • Optional CDM maintenance with agreed limits and response arrangements
  • Future changes, extra workflows or increased usage

For planning, allow approximately £10–£30/month for a small Make-based workflow, excluding existing application subscriptions and CDM maintenance. This is an indicative allowance, not a supplier quote or a guaranteed ceiling. Check current Make plans, usage, currency, billing term and taxes before purchase.

Care after handover

Your team owns day-to-day status updates and reviews failed runs. Optional maintenance can cover agreed monitoring, connection checks and small changes; scope and limits are written into the proposal. Without maintenance, the handover explains how to pause, retry and recover manually. These five starting workflows do not require runtime AI. Any later AI processing needs a separate explanation of purpose, review and charges.

A useful website. A connected process.

Your website, forms and internal workflow need to work together.

START WITH ONE REPEATED TASK

Show me where it gets stuck.

Tell Adam what happens today, which applications you use and who needs to approve the next step.

Discuss your workflow