Stage 5: When does bringing in a specialist justify its cost?

The privacy review should happen early: ICO guidance specifically recommends involving information-governance professionals from the earliest stages of AI projects. (ico.org.uk)

For integration work, distinguish technical access from contractual permission. Joblogic’s current terms, for example, impose approval and scope conditions on AI integrations and automated changes. A working API demonstration is not the entire approval process. (joblogic.com)

How do you decide whether the assessment itself is worth buying?

Ask the specialist to identify:

1. The decision their work will enable.
2. The implementation or recurring expenditure that could be avoided.
3. The internal hours required with and without their involvement.
4. The evidence and reusable documents you will receive.
5. The fixed fee, exclusions and stopping point.

If nobody can name the decision or the deliverable, defer the engagement. Do not assign a speculative monetary value to avoiding a safety incident merely to justify a consulting fee.

What should credible agency evidence look like?

Request two comparable references where possible, and ask to speak with the person who manages exceptions—not only the owner quoted in the case study.

• [ ] What software, services and call volumes were involved?
• [ ] What was the baseline and comparison method?
• [ ] Were reported results enquiries, bookings, completed jobs or contribution?
• [ ] How much human supervision remained?
• [ ] What failed, and what changed after launch?
• [ ] Who currently maintains the system?
• [ ] What were the full first-year costs and renewal terms?

A useful caution comes from a published UK plumbing-and-heating case study: the supplier reports 226 handled calls in 11 weeks, but the reviewed page does not establish incremental completed-job contribution. Treat it as supplier-reported call-handling evidence, not verified ROI. (locateai.co.uk)

What belongs in the agency contract checklist?

These are recommended commercial requirements; negotiate them explicitly rather than assuming they follow from purchasing the service.

• [ ] A precise scope: channels, branches, services, permissions and exclusions.
• [ ] Acceptance criteria tied to your test cases and agreed outcome measures.
• [ ] Milestone payments linked to accepted deliverables.
• [ ] Client control of business numbers and critical accounts, or a documented transfer arrangement.
• [ ] Rights to use and export configurations, workflows and relevant documentation.
• [ ] A permitted data-export route, format, timetable and price.
• [ ] Support hours, escalation contacts, incident responsibilities and restoration expectations.
• [ ] Written change-control, maintenance charges and model/configuration change notification.
• [ ] Cancellation, renewal, minimum term and exit-assistance terms.
• [ ] A processor agreement and authorised subprocessor arrangements where applicable.

Data-protection return/deletion obligations are important, but do not assume they also grant ownership of software or workflow intellectual property. ICO processor-contract guidance addresses personal-data obligations; negotiate the commercial assets separately. (ico.org.uk)

Stage output: comparable proposals and a signed pilot agreement—not a broad transformation retainer.