BUSINESS AUTOMATION / CUSTOMER ONBOARDING

New customer setup

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.

WORKING DEMOSample data only

Try the workflow.

Change the input. Run the example. See what happens.

01 / YOUR SAMPLE INPUT

Run the example twice to test duplicate handling, or choose another status to see when it stops.

Your result appears here when you run the example.

This demo runs locally in your browser. Nothing is sent or saved to a business account. A commissioned workflow connects your agreed applications after testing and approval.

CDM SETUP FEE

Setup: individually quoted

Configuration, agreed testing, instructions and handover. You approve the scope and fee before work starts.

YOUR CHOICE

Support: optional, quoted separately

Choose an agreed maintenance allowance or manage the workflow using your handover notes.

PAID TO YOUR SUPPLIERS

Software and usage: separate

Subscriptions and usage charges belong to your own accounts. These are not CDM’s setup or support fee.

See the running-cost allowance ↓
THE WORKFLOW, STEP BY STEP

Turn an accepted job into an organised start.

Acceptance and your agreed checks come first. An enquiry or draft quote cannot start this process.

Follow the steps, at your pace.
Illustrations explain the process. They are not a live activity feed.
  1. Human decision

    Confirm the job is ready.

    An authorised person or agreed system records explicit acceptance. Required agreement and payment conditions are checked before setup begins.

    An approved starting point
  2. Prepare the workspace.

    Create the agreed folder and checklist from your templates. A repeated acceptance reuses the original workspace.

    A consistent place for the work
  3. Human decision

    Welcome the customer.

    Send the approved welcome message and information request. Your project owner reviews the returned information before work begins.

    Clear next steps for the customer and owner

Where you stay in control

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.

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

Trigger and actions — the detailed workflow

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

  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.
What you provide and which applications can connect
  • 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

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

Connections depend on subscription, permission and compatibility checks. Use named access in your own accounts; do not send passwords in an enquiry.

Setup deliverables, testing and handover
  • 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

Extra sources, additional connections, historical data cleanup and later changes may need a separate quote. Your proposal confirms the included scope before work starts.

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.

Explore the other workflows.

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