01 · Define
Scope the work
Agree the workflow, available data, owner, expected output and acceptance checks. Identify the dependencies before committing to a build.
Discuss your scope02 · Deliver
Build the pilot
A written proposal sets out the deliverables, responsibilities, review points and fee. Changes to that scope are discussed before extra work begins.
Request a pilot quote03 · Operate
Support & extend
Agree maintenance, monitoring and future changes separately. Review the evidence from the first workflow before extending it to more work.
Discuss ongoing supportWhat affects the quote
- Data readiness
- The quality, access and preparation needed for the input records.
- Workflow complexity
- The number of steps, systems and exceptions the workflow must handle.
- Review requirements
- The acceptance checks, approval points and testing needed before use.
- Running volume
- How often the workflow runs and the model, hosting or vendor usage it requires.
Included in the agreement
- The deliverables and what is outside the scope.
- Responsibilities for data access, review and operating the result.
- The fee, payment schedule and any separately billed vendor costs.
- Acceptance criteria, review dates and how changes are handled.
There is no self-service subscription or checkout on this site. Bring your current workflow and a sample output to a scoping conversation; we can then prepare a proposal for the work that makes sense.