Agree the work.
Test the next step.
A proposed framework for an engagement. Timing, deliverables, fees and support depend on the workflow and belong in a separate agreement.
- 01
Audit
Is this the right task?
Map the existing workflow, the people involved and what a useful change would mean.
- Proposed output
- A proposed scope, constraints and acceptance questions.
- Your input
- A description of the task and access to the people who understand it.
DecisionAgree whether a small pilot is worth designing.
- 02
Design
What needs to be agreed?
Describe the sources, integrations, human decisions and behavior when something goes wrong.
- Proposed output
- A workflow design, data-handling requirements and a test plan.
- Your input
- Representative, appropriate sample material and a named decision maker.
DecisionApprove the scope and safeguards before implementation.
- 03
Pilot
Does it work in context?
Evaluate a contained implementation against the agreed cases, including errors and human handoffs.
- Proposed output
- Test findings, limitations and a recommendation for the next step.
- Your input
- Time for testing, review and a decision about any proposed release.
DecisionContinue, change the design or stop. A pilot is not automatic release approval.
- 04
Operate
Who owns it day to day?
Set the responsibilities for review, support, costs, changes and eventual handover.
- Proposed output
- An agreed operating plan with owners and review arrangements.
- Your input
- A business owner for the workflow and an agreed support scope.
DecisionConfirm operating arrangements separately before ongoing service begins.
Before an engagement.
How are fees and usage costs agreed?
Audit scope, implementation fees, provider usage and ongoing support belong in a proposal. This website does not publish a fixed package, retainer or consumption guarantee.
How long does a pilot take?
Timing depends on the workflow, integrations, data readiness and review process. Agree a bounded scope and acceptance criteria before setting a delivery date.
Where would our data go?
Provider access, region, retention, model-training terms and permissions must be confirmed for the engagement before data is shared. Do not include confidential customer or patient data in an initial enquiry.
Can the existing tools stay?
Start with the systems you use. Their interfaces, permissions and constraints need to be checked before an integration can be proposed.
Who needs to be involved?
A business-side owner should be able to explain the task and make scope decisions. The project may also need input from people responsible for data, security, operations or the systems involved.
What happens at handover or exit?
Ownership, documentation, access, data export and transition support should be specified in the agreement. Make these part of the initial scope rather than an assumption.
Bring one task.
Start a conversation.
Describe the work, the tools and the point where your team needs help. Scope and arrangements can be discussed from there.