For teams moving data manually or losing track of ownership and next actions.
A quote request goes from the website form into a spreadsheet. Each enquiry has an owner and a next action.
Before, after and when something fails
Illustrative workflows. One pilot does not include every operation below; time and errors are measured in your own process.
A person copies a form enquiry
- After implementation
- The workflow creates a record with an ID, owner and next action.
- Exception and human action
- CRM unavailable: the owner sees the error; an agreed retry or manual recovery checks for duplicates.
The team copies order details into a document
- After implementation
- The document is assembled from agreed fields and a template.
- Exception and human action
- Required data is missing: the document is not sent; a person completes the record and restarts the check.
A report is assembled from several files
- After implementation
- The workflow prepares a report for a defined period from agreed sources.
- Exception and human action
- A source is out of date: the report is marked incomplete; a person checks the source before using it.
How this stage is accepted
- The trigger, destination record, owner and next action are verified.
- Agreed tests cover duplicates, missing data and service outages.
- Recovery instructions are handed over; a method for comparing manual actions, time and errors before and after is agreed.
Choose a process with a clear result
We map the trigger, data, responsible person and expected output. We record the starting point: handling time, manual actions, missed tasks or duplicate records.
Examples include a form feeding a CRM, documents prepared from order data and scheduled reports. Each integration has its own dependencies and scope.
Decide whether AI is needed
Moving data and updating statuses often needs a standard integration. AI can help classify enquiries, draft replies or find information in documents.
For an assistant we agree knowledge sources, permitted actions and handover to a person. Model costs and data requirements are assessed separately.
Check failures as well as successful runs
We review API access, permissions, duplicate handling and third-party outages. Acceptance checks cover the saved result and a practical recovery route.
Handover includes access, process documentation and usage instructions. Support and additional functions are agreed separately.
A focused enquiry-tracking pilot
One existing website form → one Google Sheet → an owner and a next action.
The diagnostic is separate: D1 $190 + P1 $990 = $1180 in total. Pilot payment: $693 (70%) upfront and $297 (30%) after acceptance. 7–10 business days after access is ready. 30 agreed acceptance checks; 14 days of fixes for defects within the agreed scope after acceptance.
Changing a system that already works
We assess your current website, campaigns or CRM first. A replacement or migration is a separate decision with an explanation of the scope and cost.
Record the starting point
Identify the pages, data, access and workflows involved. Agree what must be preserved and who approves changes.
Propose a bounded scope
Compare improvements to the existing system with alternatives. Agree the stage, owner, dependencies and a way to restore the previous state where possible.
Verify before handover
For website or CRM changes, agree backups and a test environment where needed. Check the agreed workflows after release and hand over the change log and instructions.
Advice, implementation or ongoing work
Choose the format that fits the task. A paid audit is not a mandatory entry point for every project.
Advice / assessment
Discuss a specific question and receive recommendations or a plan. Your team can handle implementation.
Implementation
We make the agreed changes, show progress and verify the acceptance criteria.
Support / development
Agree the period, work items, reporting and responsible person separately. New tasks are estimated before work starts.
Work example
From the owner’s experience: preparing enquiries with an AI agent
An example from the project owner’s experience. These figures describe a specific implementation, not a forecast for your project.
Before we start
Must we replace our CRM?
We first assess the capabilities of your current tools. Replacement and data migration are separate projects where needed.
Can we start without AI?
Yes. A standard integration is enough for many repeatable tasks.
How do we accept the result?
We agree scenarios before development, verify records in the destination system and test errors and recovery.