Take the agreed reporting period.
At the scheduled time, read the approved records for a defined week or month.
Your regular report starts with copying and pasting.
Calculate agreed figures from structured records and send a scheduled summary with a link back to its source.
Change the input. Run the example. See what happens.
Try a zero count, then leave a day blank. Zero and missing data are handled differently.
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 ↓Agreed calculations and source references help you understand the report. Missing data stays visible.
At the scheduled time, read the approved records for a defined week or month.
Validate required fields and use fixed calculation rules. Flag missing or inconsistent records instead of inventing a result.
The report goes to approved recipients with source references. The owner reviews exceptions and decides what action to take.
You agree definitions, cut-off dates and recipients, keep source records accurate and review exceptions. Business decisions remain yours. Changes to a calculation need review and testing.
Stop rules: Invalid or incomplete inputs produce a visible exception. A report period has one delivery reference to prevent duplicate sends. Totals use deterministic calculations, not AI estimates.
The agreed weekly or monthly reporting time arrives.
Excel tables or Google Sheets, Microsoft Lists or a compatible CRM, with Outlook or Gmail. Sources must offer suitable structured access.
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.
Paid data/API access or larger usage allowances may be required. Reporting from invoices or accounting platforms needs separate assessment.
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.