Services

Pricing built around real outcomes.

Three tiers, transparently priced. Setup gets you live; agentic stack scales the system; retainer keeps it useful.

01 · Setup

OpenClaw Setup

£3,500

one-off · 2–3 weeks

A properly structured OpenClaw deployment your team can actually operate. Workspace, memory, core skills, channels, docs, and training in one focused setup project.

Best for getting from zero to a safe, working agent.

✓Workspace + role architecture
✓Memory + knowledge structure
✓5 custom starter skills
✓Tool + channel integrations
✓Operating runbook
✓Team training session

Start setup →

Most chosen

02 · Build

Agentic Stack

£6,500

project · 4–6 weeks

Move from one assistant to a coordinated agent team. Orchestration, security boundaries, model routing, evals, and production operating rules.

Best for teams moving from one assistant to coordinated workflows.

✓Multi-agent workflow design
✓Model + cost routing
✓Sandbox + approval boundaries
✓Eval pipeline + monitoring
✓Production operating rules
✓Handover to retainer

Scope a build →

03 · Operate

Retainer

£950 / mo

rolling · 3-mo minimum

The setup is the start. Retainer covers eval reviews, prompt updates, skill changes, model migrations, troubleshooting, and continued capability development.

Best for keeping live agents useful, safe and improving month by month.

✓Monthly evals + audit
✓Prompt + skill updates
✓Model migration support
✓New skills (2 / month)
✓Priority response
✓Quarterly review

Add retainer →

Free OpenClaw resource

Safe setup checklist and permission matrix.

Use this before giving an agent access to files, inboxes, CRMs, production systems, or client data. It turns vague AI risk into a plain set of permissions, approvals and evidence.

Open the checklist Ask for a setup review

✓Map the workflow before choosing tools

✓Decide read, draft, approve and execute permissions

✓Set approval gates for external messages and risky changes

✓Log agent actions, sources, owner decisions and rollback steps

How the work runs

A narrow first deployment beats a broad transformation plan.

The first engagement should prove a real workflow, make ownership visible, and leave the team with a system they can explain. Scope expands when the operating evidence supports it.

Step 1

Assess the workflow

Step 2

Design the controls

Step 3

Build the smallest useful version

Step 4

Train, review, and improve

Start here

Need the right starting point?

Tell us what workflow is slow, messy, or too manual today. We will tell you whether the next move is setup, rollout support, custom development, or something simpler.