Start with one workflow
Useful starting points include proposal drafts, quote preparation, follow-up drafts and recurring internal research. We assess the actual workflow before promising an integration. A task that relies on incomplete records or constant judgement may need a process change before automation.
The goal is a measurable reduction in manual work. We agree what to measure and what still needs your team before implementation begins.
How the engagement works
We map the current task, define the inputs and approval points, then agree a scope. A working version is tested against representative examples before wider use. Handover and support responsibilities belong in the agreed scope.
- Discovery: document the current process, volume and pain points.
- Scope: agree deliverables, integrations, acceptance criteria and exclusions.
- Build and test: compare output against real examples with your team.
- Handover: document operation, ownership, access and maintenance responsibilities.
What will it cost?
There is no single price for every business. Cost depends on the workflow, data readiness, connected systems, exception handling and support. We quote after reviewing the brief. The R990 workshop price is a training offer, not the price of a custom automation project.
Ask for setup costs, recurring service costs and third-party subscriptions separately. Agree how changes will be handled so a small first project does not grow without a decision.
Your systems and your information
Tell us which tools you already use. Compatibility depends on their APIs, account permissions and the workflow you need; a mention of a tool is not a promise of an existing connector.
Keep confidential customer data out of an initial enquiry. During scoping, agree appropriate data access, retention, human review and who can approve external actions. We do not claim that installing an AI tool alone makes a workflow compliant with any law.
Training or implementation?
Choose the workshop if you want to build and understand your own starting workflow. Discuss implementation if the workflow spans systems, needs testing and maintenance, or your team needs delivery support. Either way, begin with a concrete task rather than a promise to automate the entire business.