Confirm the job is ready.
An authorised person or agreed system records explicit acceptance. Required agreement and payment conditions are checked before setup begins.
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.
Change the input. Run the example. See what happens.
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.
Configuration, agreed testing, instructions and handover. You approve the scope and fee before work starts.
Choose an agreed maintenance allowance or manage the workflow using your handover notes.
Subscriptions and usage charges belong to your own accounts. These are not CDM’s setup or support fee.
See the running-cost allowance ↓Acceptance and your agreed checks come first. An enquiry or draft quote cannot start this process.
An authorised person or agreed system records explicit acceptance. Required agreement and payment conditions are checked before setup begins.
Create the agreed folder and checklist from your templates. A repeated acceptance reuses the original workspace.
Send the approved welcome message and information request. Your project owner reviews the returned information before work begins.
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.
An authorised person marks a job accepted, or an agreed system records the customer's explicit acceptance.
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.
Extra sources, additional connections, historical data cleanup and later changes may need a separate quote. Your proposal confirms the included scope before work starts.
Start with the applications you already use. Review the setup cost, running costs and handover together before you decide to go ahead.
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.
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.
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.
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.
Your website, forms and internal workflow need to work together.