Do we need to know what agent we want?

No. The Agent Opportunity Audit identifies which workflows are worth turning into agents first.

Yes — and we recommend it. Most engagements start with one Quick-Win Agent Build.

How long does implementation take?

Timelines depend on scope and complexity. Most businesses should start with a focused workflow rather than a full transformation programme.

Complexity of the workflow, integrations required, data quality, risk surface, and the level of ongoing management.

Yes. We prefer existing tools before introducing new platforms unnecessarily.

We monitor, improve, expand, and keep humans in control under a Managed Agent Support engagement.

engagements

Projects are scoped after the audit. You receive a fixed-scope proposal before implementation begins — no open-ended retainers, no surprise invoices.

band_01

start_here

A focused diagnostic that identifies the highest-value agent opportunities in your business before any build commitment.

Best for: SMEs unsure where to start, or weighing multiple competing automation ideas.
What's included: Diagnostic working session, workflow review, scoring rubric, ranked opportunity list, build roadmap.
Typical output: Audit document, bottleneck map, scored opportunity shortlist, recommended first build.
How scope is handled: Fixed-scope engagement. Outcomes and deliverables agreed before kickoff.
Why it reduces risk: No build commitment. You leave with a roadmap you can use with us or independently.
Typical duration: Typically 1–2 weeks from kickoff to delivered roadmap.

band_02

first_agent

One contained agent workflow, built end-to-end inside your existing tools, with clear scope, testing, and human approval boundaries.

Best for: Teams that have identified a clear repetitive workflow and want a single working agent in production.
What's included: Workflow design, integration build, approval boundaries, testing in a controlled environment, deployment, handover documentation.
Typical output: One production-ready managed agent with monitoring and approval points.
How scope is handled: Fixed-scope proposal issued after the audit. Change requests handled transparently.
Why it reduces risk: Single workflow. Reversible. Human approval points designed in from day one.
Typical duration: Typically 3–6 weeks depending on workflow complexity and integrations.

band_03

scale_up

A connected set of agents across one function — sales, finance, support, or operations — sharing context and approval rules.

Best for: Teams that have proven value from a first agent and are ready to layer more across one department.
What's included: Multi-agent design, shared context layer, coordinated approval rules, integration build across the function's stack, staged rollout.
Typical output: A working operations layer for one department, with clear ownership and run-book documentation.
How scope is handled: Phased fixed-scope proposal. Each phase is independently usable and reviewable.
Why it reduces risk: Phased deployment. Each agent proves itself before the next is connected.
Typical duration: Typically 2–4 months depending on department breadth.

band_04

ongoing

Ongoing monitoring, optimisation, and expansion of agents already in production. Agents are not a one-shot project.

Best for: Businesses running deployed agents that need a reliable owner for tuning, exception handling, and safe expansion.
What's included: Monitoring of agent runs, exception triage, prompt and rule tuning, integration updates, quarterly review and expansion planning.
Typical output: Healthy, improving agents with measurable performance — and a clear backlog of next opportunities.
How scope is handled: Monthly engagement, scoped to current agent surface. Expansion handled as separate build proposals.
Why it reduces risk: Continuous oversight. Issues are caught and corrected before they compound.
Typical duration: Rolling monthly engagement. Cancellable with notice.

pricing_faq

No. The Agent Opportunity Audit identifies which workflows are worth turning into agents first.