Service 03 / 10AI ideas, agents and rules
AI strategy and AI agents that do everyday tasks for you.
We find where AI helps you most, then build AI agents that draft quotes and chase invoices. We test each agent on your own examples. A named person approves every risky step.
An illustrative AI task board for “Your company”. Six tasks sit in four columns: queued, agent working, needs approval and done. Each card shows the agent and the person who owns the work. It also shows the level, spend against a budget and progress through the steps. A billing dispute waits for the Service lead to approve a $240 credit before the agent adds it.
What each agent may do alone
- L1Suggestsuggests only
- L2Drafta person sends it
- L3Act with approvala person approves
- L4Act within limitselse asks a person
01Why now
Why AI trials stall, and what we agree before we build.
AI trials rarely fail because of the AI. They stall for the 4 reasons below. Screens marked Illustrative are examples, not client results.
What happens to 100 AI ideas
Illustrative- Ideas raisedEvery team has a list 100
- 01 Stalls on: No owner, no measure −58
- Demos builtTried on sample data 42
- 02 Stalls on: Data not ready −24
- Trials with usersLive data, a few people 18
- 03 Stalls on: Risk unclear −10
- Approved for wider useOwner, risk and cost agreed 8
- 04 Stalls on: Cost unknown −3
- In daily useMeasured every week 5

Agreed before we build
- A named owner for the work
- A starting number and a target
- How ready your data is
- A risk level and AI limits
- A cost limit per task
-
01
No owner, no measure
Nobody owns the work the demo changes, or the number it should move.
How we fix itEach idea gets a named owner, a starting number and a target first.
Ranked AI ideas -
02
Data not ready
The demo used a clean sample. Live data is scattered, out of date or hard to reach.
How we fix itWe score the data for each idea, and every gap goes on the plan with an owner.
The workshop -
03
Risk unclear
Nobody can say what the agent may touch or who approves it, so legal says no.
How we fix itEach agent gets a risk level, limits, named approvers and a log of every action.
Safe AI rules -
04
Cost unknown
Nobody knows what each task costs at full volume compared with doing it by hand.
How we fix itFrom day 10, we compare the cost per task with doing it by hand.
How we test
02Ranked AI ideas
Your AI ideas ranked, with the top 3 costed.
We score each idea on value, ease, risk and time. You get a plan by quarter and business cases for the top 3.

Value
Hours saved or sales affected, using your own volumes.
Ease
How easy it is to build: where the data lives and how clean it is.
Risk
EU AI Act risk level, personal data and the harm if the agent is wrong.
Time to results
Weeks to a measured trial, data work included. Each week takes 0.05 off the score.
A chart of twelve AI ideas by value and ease to build. Three in the high-value, easy-to-build corner are marked to build first. They are reconcile vendor invoices, triage inbound RFPs and draft renewal quotes. The ranked list that follows holds the same information.
Minimal Limited · transparency duties High risk · Annex III
Bubble size = hours of work a month · axes 3–10Illustrative portfolio
score = 0.45·value + 0.35·ease + risk − 0.05·weeksrisk: +1 minimal · +0.4 limited · −1 high
What you take away
- Ranked planAll 12 ideas, in order, by quarter
- Business case × 3Today’s numbers, target, costs and payback
- Owners and measuresOne owner and one number to move per idea
Selected · rank 01 · score 7.5
Reconcile vendor invoices
Finance · owner Finance lead · 4–6 wks to a measured trial
- Value
- 360 hours a month matching about 2,900 invoices to orders and receipts.
- Ease to build
- Invoices and orders already sit in the accounts system. About 18% arrive as PDFs to be read first.
- Risk Minimal risk
- Minimal tier. Supplier data only, and payment release stays with a person.
DecisionBuild first
Trial starts atL2 · Draft
Top level allowedL4 · only after 90 days at L3
03Agent demo · Illustrative
How much an agent does alone is up to you.
Pick a task, set the level and limits, and run it. The level only changes the last step. If the agent hits a limit, it passes the task to a person.
Interactive agent run: choose a task, an autonomy level and limits, then press Run. The trace lists each step; the run ends in a suggestion, a draft, an approval request, an action within limits, an escalation or a halt, and adds an audit row. Outcomes are pre-written; no live model is called.
run_7f3a21 · renewals-agent · prompt renewals v14.1
Renew a customer contract
- Latency
- 3.9 s
- Tokens
- 4.6k → 800
- Records
- 3
- Spend
- $0.020
Run complete · approved by Sales ops lead · quote sent · audit entry written
-
Plan
plannerrouter-smallinGoal: renew account 20-418 before 14 Oct
out4 sub-tasks · tools kb, crm, calc
640 ms1.2k → 180$0.0003
-
Retrieve policy
kb.searchreadembedin“renewal discount policy”
outPricing policy v4 §3.2 · discounts up to the approval limit
410 ms40 → 0<$0.0001
-
Read system
crm.get_accountreadinaccount_id = 20-418
outARR $48,000 · 3 seats added · usage +18%
280 ms——
-
Calculate
calc.renewalinARR, seats, 24-month term
outPrice $51,840 · discount 8%
35 ms——
-
Draft
llm.draftreasoner-largeinQuote and cover email in the account’s tone
outQuote Q-7731 · email of 146 words
2100 ms3.4k → 620$0.020
-
Policy check
policy.checkindiscount, records, spend vs limits
outDiscount 8% ≤ 10% · records 2+1 ≤ 25 · spend $0.020 ≤ $0.25 · cites §3.2
90 ms——
-
Write action
crm.update_quotewriteinQ-7731 → status “sent”
outApproved by Sales ops lead · Q-7731 sent
320 ms——
Ready
Press Run agent to start. Change a limit first to see a guard step in.
Suggestion · L1 changes nothing
Renew account 20-418 for 24 months at $51,840 with an 8% discount. Sources: pricing policy v4 §3.2 and CRM usage.
Sent to Sales ops lead. A person does the work.
Draft saved · crm.save_draft
Editable. Nothing leaves until Sales ops lead sends it.
Approval needed · Sales ops lead
Send quote Q-7731 to the customer?
Evidence: pricing policy v4 §3.2 · CRM usage +18% · 3 records affected
Executed after approval
Quote Q-7731 sent. Approved by Sales ops lead.
- Write
- crm.update_quote · Q-7731 → status “sent”
- Approver
- Sales ops lead
- Waited for a person
- 14 s
- Audit row
- run_7f3a21 · append-only
Run stopped by a guard
The run passed its limit and stopped before acting.
Handed to Sales ops lead with the trace so far.
- Stopped at
- —
- Written
- Nothing
- Spend so far
- —
- Audit row
- —
Audit log · append-only · newest first
-
10:42:07run_7f3a21L3Renew a customer contractExecuted after approval
- Approver
- Sales ops lead
- Models
- router-small · embed · reasoner-large
- Prompt
- renewals v14.1
- Tools
- kb.search:r · crm.get_account:r · crm.update_quote:w
- Records
- 3
- Spend
- $0.020
Approved tools only
Only the tools each level allows.
Limited access
It can read a lot but change little.
Spend and record limits
Checked before each step and each change.
Policy checks
Each change checked against your written rules.
A person approves
Risky steps wait for a named person.
Full action log
Model, prompt, tools, cost and approver.
LLM06 · Excessive Agency. OWASP’s list of AI security risks warns against giving AI too much power. We give few tools, ask approval for risky steps and check outside the model.
04How it works
What a live AI agent is made of.
A demo needs a model and an instruction. A live agent needs 8 parts, each tested, watched and easy to swap. We pick the tools for each part with you.
-
Models
planA small, fast model for easy steps and a bigger one for hard ones. From a provider, or open models in your region.
- Anthropic
- Google Gemini
- Meta Llama
- Mistral AI
- OpenAI
- vLLM
- Hugging Face
-
Task steps
planEach task saves progress, retries and picks up after a failure.
- LangGraph
- LangChain
- Temporal
- Python
-
Memory & knowledge
planShort-term memory in Redis. Your documents indexed, with a link to each source.
- PostgreSQL
- pgvector
- Qdrant
- Redis
- LlamaIndex
-
Logins & access
actEach agent has its own login, with only the access it needs, for a short time.
- Okta
- Auth0
- Vault
- OpenID
A diagram of an agent loop: plan, act, observe, repeated until the task is done. Eight parts sit around it. On one side: models, task steps, memory and knowledge, and logins and access. On the other: your systems, automatic checks, testing and monitoring. Each part lists the technologies used for it.
-
Your systems
actMCP, a standard AI link, connects your systems once for all agents, within limits.
- Model Context Protocol
- FastAPI
- OpenAPI Initiative
- HubSpot
- Salesforce
-
Automatic checks
actYour rules checked on every action, personal data hidden, inputs and outputs checked outside the model.
- Open Policy Agent
- Microsoft Presidio
- NeMo Guardrails
- Llama Guard
-
Testing
observeEvery change runs on your own examples before release. An AI scores each case, checked against your team.
- promptfoo
- Ragas
- MLflow
- GitHub Actions
-
Monitoring
observeEvery step recorded with its speed, cost and inputs, in the tools your engineers already use.
- OpenTelemetry
- Langfuse
- Grafana
- Datadog
Models you can swap
Changing a model is one setting, and all the tests run again before release.
Your data stays yours
Paid business terms, or models on your own servers. Nothing trains on your data.
Your region if needed
Models and data stay in the region your policy or GDPR (Europe’s data law) requires.
05How we test
Every change is tested on your own examples.
Each agent has a test set made from your own cases. A change goes live only if it passes. A person still signs off each release.
An illustrative test dashboard for one agent. It shows five pass marks and success per scenario against its mark. It compares three models. It shows the cost and energy saved by using a small or a large model per step. A test history follows. An instruction change lets the agent act before its rules check, and the test check blocks the release. The rule moves into code and the re-run passes.
-
Task success
94.2%
pass ≥ 92%
-
Correct tool use
98.1%
pass ≥ 97%
-
Policy violations
0
must be 0
-
Cost per task
$0.021
manual $4.80
-
95% of tasks done in
6.8 s
pass ≤ 10 s
Success by scenarioIllustrative
- Standard renewal64 cases 98%pass ≥ 95%
- Seats changed mid-term38 cases 96%pass ≥ 92%
- Discount over the limitmust hand off25 cases 100%pass = 100%
- Usage data missing25 cases 88%pass ≥ 85%
- Hidden instructions in account notesmust refuse · LLM0130 cases 100%pass = 100%
- Ambiguous contract termmust ask36 cases 84%pass ≥ 80%
- Scorer agreement
- κ 0.84 vs human labels
- Marked by 2 people
- 40 of 218 cases
- Last calibrated
- release 0418
Model comparison · every step on one modelSame 218 cases
| Metric | router-smallhosted · fast | reasoner-largehosted · strongest | open-weight 70Bself-hosted · in-region |
|---|---|---|---|
| Task success | 86.1% | 94.6% | 91.7% |
| Correct tool use | 97.4% | 98.3% | 97.9% |
| Cost per task | $0.006 | $0.058 | $0.031 |
| 95% of tasks done in | 3.9 s | 7.4 s | 8.1 s |
| Policy violations | 0 | 0 | 0 |
| Used for | Routes, classifies, extracts | Drafts and reasons | Fallback where data must stay in-region |
Right-sized · cost and carbon per taskSCI · ISO/IEC 21031:2024 — Software Carbon Intensity
- Every step on reasoner-large $0.0582.4 Wh est. · 94.6% success
- Right model per step · inputs reused $0.0210.9 Wh est. · 94.2% success
SCI = ((E × I) + M) per R, a carbon score, with R = one completed task. The manual process is the limit: about 4.8 Wh a task (4.8 minutes at a workstation). An agent that does not beat it on cost and carbon does not go live.
Test history · last 4 runs · step-order checks on
- run 0412 renewals v13 214 / 214 checks passed · every run used tools in the allowed order release allowed
-
run 0418
renewals v14
Step-order check failed in 6 of 25 “discount over the limit” cases. The quote was changed before the rules check, so the agent acted instead of asking
release blocked
expected…
draft→policy.check→crm.update_quotegot…draft→crm.update_quote→policy.check - fix renewals v14.1 Changes now wait for the rules check to pass. Code enforces this, so the AI cannot skip it · 4 step-order cases added (218) awaiting re-run
- run 0419 renewals v14.1 218 / 218 checks passed · 0 tools out of order · released after the Sales ops lead signed off release allowed
Test cases from your experts
Your own tickets, labelled by the people who do the work. Tricky new cases from live use join every week or two.
AI scorer, checked
An AI scores every case. Each release, we check it agrees with your team (Cohen’s κ 0.8 or more).
Attack tests
Hidden instructions, over-limit actions and missing data. Each must be refused or passed to a person.
Tests before release
Every change to instructions, tools or models runs all the tests. One failure stops the release.
06Safe AI rules
Clear AI rules that let legal say yes.
Before any agent goes live, we write down what it may do, who approves and which laws apply. It all maps to the standards your auditors use.

18 documents across the 4 parts of NIST AI RMF 1.0 · frameworks we build to, with no certificate claimed
01GOVERN
Govern
Policies, roles and accountability, so every decision about AI has an owner.
-
AI use policy and principles
-
Roles, approval rights, who does what
-
List of AI tools used
-
Training record for owners and approvers
No document in this part for this framework.
02MAP
Map
Each AI idea in context: who it affects, what could go wrong, which rules apply.
-
Context sheet and EU AI Act risk tier
-
Risk assessment with treatment plan
-
Impact assessment where high-risk
-
Data map and lawful basis
-
Threat model for the agent
No document in this part for this framework.
03MEASURE
Measure
Evidence, not opinion: every risk has a test, a number and a trend.
-
Tests, test sets and attack-test results
-
Model cards per model and version
-
Bias and fairness tests where people are affected
-
Monitoring: success, cost, hand-offs, quality
No document in this part for this framework.
04MANAGE
Manage
Controls in place, kept working after launch, and a plan for when they fail.
-
How people stay in charge: the four levels
-
Safety check and approval rules
-
Labelling: people are told they are talking to AI
-
Audit log and retention rules
-
Changes, undo and incident response
No document in this part for this framework.
Frameworks we build to
- NIST AI RMF 1.0AI Risk Management Framework
- ISO/IEC 42001:2023Artificial intelligence management systems
- ISO/IEC 23894:2023AI risk management guidance
- EU AI ActArtificial Intelligence Act (EU) 2024/1689
- OWASP Top 10 for LLM ApplicationsSecurity risks in generative AI applications
- DPDP Act 2023Digital Personal Data Protection Act, 2023
- GDPRGeneral Data Protection Regulation (EU) 2016/679
EU AI Act · when duties start
- 2 Feb 2025 in forceBanned AI uses and AI skills for staffArt. 4 · Art. 5
- 2 Aug 2025 in forceRules for general-purpose AI modelsChapter V
- 2 Aug 2026 in forceAI disclosure duties and most other rulesArt. 50
- 2 Dec 2026 aheadMarking AI content from systems already on sale, and a new banned useArt. 50(2) · Art. 5
- 2 Dec 2027 aheadHigh-risk uses in Annex III, moved later by the 2026 changeArt. 6(2) · Annex III
- 2 Aug 2028 aheadHigh-risk AI inside regulated productsArt. 6(1) · Annex I
Regulation (EU) 2024/1689, as changed by Regulation (EU) 2026/1744 (the Digital Omnibus on AI), in force since 27 July 2026. High-risk dates moved later. From 2 December 2026, systems already on sale must mark AI content, and a new banned use starts. We follow the text in force.
What this covers
These documents are the proof an auditor or regulator asks for. Seeking a certificate is your choice. GDPR and India’s DPDP Act 2023 sit in the same map, so one list covers privacy and AI risk.
Cybersecurity & AI Trust07How long it takes
From idea to a working agent in weeks.
Test results decide each step. Your team’s speed at checking cases and approving steps sets the pace. Times shown are typical, agreed in the workshop.
A stopwatch drawn to scale over 8 weeks, with 5 milestones. Week 1: two-day workshop. Week 2: test version on your data. Week 3: first tests and check G1. Week 5: trial with 10 users. Week 8: live use at L3 after check G2. The milestone buttons that follow describe each one.
What exists on week 1
- The long list scored and the first three chosen, each with a named owner
- Today’s numbers for doing it by hand
- Test space: safe copies of your data
workshop · 12 scored · 3 chosen · now 4.8 min per task · test space ready
Who decidesOwner and sponsor agree the measure
What exists on week 2
- One system linked through MCP, read-only access
- 40 test cases taken from real tickets
- First runs at L1 Suggest, every step logged
test version · 1 tool · 40 cases · L1 Suggest
Who decidesThe team who does the work reviews the first outputs
What exists on week 3
- 120 cases marked by your experts; AI scorer checked (κ 0.82)
- Cost and time per task measured against doing it by hand
- Gate G1, go to prove: decided on the numbers
tests · 120 cases · κ 0.82 · $0.03 per task · 95% in 8.6 s · G1 passed
Who decidesSponsor, owner and legal sign G1 on evidence, not on the demo
What exists on week 5
- Practice run first, then L2 Draft for 10 named users
- Safety checks, spend limits and approvals switched on
- Weekly review of hand-offs adds to the test set (214 cases by week 7)
trial · 10 users · L2 Draft · 214 cases · 0 rule breaks
Who decidesLegal and security sign the safety rules
What exists on week 8
- Act with approval for the whole team, after check G2
- Action log, monitoring and guides handed over
- Decision note: the tests for moving to L4 later
live · L3 · G2 passed · action log · guides · review in 90 days
Who decidesSponsor signs the release; the owner runs it
Model swap · testing
reasoner-large v2 on the same link
- 1New model on the same linkNo code change: the link points at the new model in the test space.0 h
- 2Tests re-run: 218 casesTwo new failures on “ambiguous contract term”, fixed with one instruction line and re-run.day 1
- 3Live at L3, with sign-offThe action log records the model version; the old model stays ready to switch back.day 2
Model swap · now live
Re-tested and live in 2 days
- Cases re-run
- 218 / 218
- New failures
- 2 found · 2 fixed
- Policy violations
- 0
- Cost per task
- $0.021 → $0.017
Model version recorded in the action log · old model kept ready to switch back
Test space on day 1
Copies of your data with private details hidden, kept apart, so nothing waits on live access.
A standard set-up
Tool links, tests, safety checks and action logs, ready to fit your systems.
Test results decide
Each stage check is a test score, so go or stop is a quick review with the owner.
08The workshop
AI strategy with the people who run the work.
Two days in week 1 with operations, legal, security, finance and the team that does the work. Together we score your AI ideas and agree a one-page plan.

The week before · a short pre-readAI agents sum up your process documents, sample tickets and systems list. Every line links to its source, so the workshop is spent deciding.

-
Day 1 · Morning
How the work runs today
Your staff walk us through 3 to 5 tasks, start to finish.
Task maps with today’s times
-
Day 1 · Afternoon
The long list, scored
Every idea on the wall, scored on value, ease, risk and time.
A scored long list, usually a dozen

-
Day 2 · Morning
Risk and data, idea by idea
Legal sets the risk, security the access, system owners the data.
Risk level, AI limits, data gaps
-
Day 2 · Afternoon
Pick the first 3
The first 3, each with an owner, a starting number and a target.
The one-page plan, signed
AI strategy · one page · Your company · v1Illustrative
What leaves the room
-
1Ambition and measures
Return about 700 hours a month to sales ops and finance by the end of Q2; cost per task under a quarter of manual.
-
2AI ideas · build first
Reconcile vendor invoices · Draft renewal quotes · Triage inbound RFPs. Nine more planned by quarter.
-
3AI team roles
Embedded: agents owned by the teams that run the process, with a small central platform and review group.
-
4Data readiness gaps
Billing history split across two systems · 18% of invoices arrive as PDFs · customer company details incomplete.
-
5Budget and measures
Build, run and review budget per AI idea; one owner and one measure each; reviewed each quarter.
-
6Risk level and AI rules
Two limited-risk AI ideas must tell people they use AI; two high-risk ideas wait for a legal plan.
Agreed in the room
- COO
- CFO
- CISO
- Head of sales ops
09Project stages
Assess, prove and scale, with a check after each stage.
We move on only when the numbers hit targets set in week 1 and the named people sign.
-
013 weeks
Assess
Interviews and the 2-day workshop in week 1. Then a test version on your data, with first test scores for the top idea.
You get
- Ranked list of AI ideas
- One-page AI strategy and plan
- Business cases for the first 3
- Test version and first scores
AI level reachedL1 · SuggestTest version only suggests, on safe data copies
G1 Go to prove Passed
- A named owner, today’s numbers and first test scores for the top idea
- Read-only data access agreed, test space ready
- Risk level set, and the AI’s limits written down
- Budget approved, with a cost limit per task
Signed bySponsor · owner · legal
-
025 weeks
Prove
One agent, tested on your experts’ cases. From week 5, 10 users try it at L2. In week 8 it goes live at L3, with approval on every change.
You get
- Working agent and its tool links
- Tests, test cases and attack-test results
- Safety and approval rules
AI level reachedL3 · Act with approvalActs on your systems once a named person approves
G2 Go live Passed
- All tests passed, attack tests included
- No rule broken in any run
- Cost per task under the limit, 19 in 20 tasks on time
- Safety rules signed by legal and security
- Guides and on-call handed over
Signed bySponsor signs · owner runs
-
03Ongoing
Scale
The next agents from the ranked list, with risks tracked. A task gets more freedom only when results allow.
You get
- Next agents from the plan
- List of AI tools and risks, kept up to date
- Quarterly review against the measures
AI level reachedL4 · Act within limitsFor named tasks, inside limits, after G3
G3 Give more freedom Every 90 days
- 90 days at L3 with approvers changing under 2% of actions
- Hand-offs to people answered on time
- No incident traced to the agent
- One task moves up one level, with new limits
Signed byOwner · risk · security
10What you get
Plan, agent, rules and guides, all in your accounts.
What we make for you is yours once it is paid for. Tools we already had stay ours, and you get a free, permanent licence to use them.
Tab 1 of 4Your company · AI project · handover
Strategy
Where AI fits, what comes first and what each idea is worth.
-
ai-strategy-one-page.pdfOne-page AI strategy Document -
use-case-portfolio.xlsxMap of AI ideas, ranked BoardSheet -
roadmap-business-cases.pptxAI plan with business cases DeckSheet -
operating-model.pdfHow your team works, and who approves what Document
Handover checklist
- Signed by the sponsor and the 3 owners
- Source files kept in your own storage
- Scores you can edit, formula included
Tab 2 of 4Your company · AI project · handover
Agent
The agent, in your own code store and cloud account, with its tests.
-
agents/renewals-agent/Live AI agent or AI helper Sourceyour cloud -
mcp-servers/Tool links for sales, billing and documents Source -
evals/Tests, test cases and attack-test results Testsreport -
infra/Set-up scripts for your cloud account Terraform
Handover checklist
- Code moved to your company’s account
- Release tools, keys and cloud in your name
- AI instructions saved with each version
Tab 3 of 4Your company · AI project · handover
AI rules
The written answers legal, security and auditors ask for, in one place.
-
guardrails/policy.yamlSafety and approval rules Policyconfig -
ai-governance-framework.pdfSafe AI rules Document -
ai-inventory-risk-register.xlsxList of AI tools and risks Register -
model-cards/A fact sheet for each model Document
Handover checklist
- List owner named, review dates booked
- Legal and security sign-off recorded
- Every row linked to its evidence
Tab 4 of 4Your company · AI project · handover
Running it
Everything your team needs to run, review and change the agent without us in the room.
-
dashboards/agent-actionsLog of every agent action Dashboard -
runbooks/Guides: hand-offs, undo, model change Document -
training/Training for owners, approvers and reviewers Sessionsrecordings -
reviews/q-review-template.pdfQuarterly review pack Report
Handover checklist
- Support rota and contacts agreed
- Approvers trained and named in the policy
- First quarterly review in the calendar
Each tab shows a mock of the first file in that part of the handover. For strategy, an AI plan by quarter. For the agent, the code layout. For AI rules, the AI list and risk register. For running it, a hand-off guide.
1190-day review
6 measures decide whether an agent stays.
We review every agent on 6 measures. Each has a pass mark and a hold mark. An agent that misses its hold mark moves back a level. The marks shown are targets.
Hours returned per week
Time saved per task × volume, against today’s numbers taken before the build
74 h
Pass
Task success in tests
The test set, re-run on every change and at each review
94.2%
Pass
Cost per task vs manual
Models, tools, hosting and review time per completed task, as a share of manual cost
13% · $0.62 vs $4.80
Pass
Hand-off rate
Share of runs handed to a person, by reason
6.8%
Pass
Policy violations
Changes outside the rules, from the action log and attack tests
0
Pass
Carbon per task vs manual
Carbon estimate per completed task, as a share of the manual process on the same power grid
19% · 0.9 vs 4.8 Wh est.
Pass
Decision
Stays at L3L3 · Act with approval
Review in 90 days whether quotes with discounts of 5% or less can move to L4, inside limits.
Signed · ownerReviewed · risk and securityLogged · audit trail
Illustrative reviewWe agree the marks for each agent before we build. Cost includes the time people spend checking.
Offers & plans
Find where AI pays off, then build agents to do the work.
We rank your AI ideas, build the agents and AI helpers, and set the rules to run them.
- Categories
- 04
- Offers
- 15
- Plans
- 04
How to buy
- 01Pick offers. Ask about one, or add several to one enquiry.
- 02Choose a plan. A small job, a fixed project or ongoing help.
- 03Send your enquiry. We reply within one working day.
How we work with you
Ways to start, from a question to a quote.
Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.
Or book a 30-minute call-
01
For a first chat, a press request or anything not ready to plan yet.
You get A reply from a named lead
-
02Recommended
Goals, who it is for, budget and timing, so our first reply can outline the work.
You get Options and prices after one call
-
03
Your documents, deadlines and the purchasing and security rules to meet.
You get Confirmation and a named lead
How it is priced
Each plan shows how it is priced. Work starts once we agree a written scope and price.
Opens the project form with this plan chosen.
-
In your enquiry
- Typical length
- 1–3 weeks
- Pricing
- Fixed fee
-
In your enquiry
- Typical length
- 4–12 weeks
- Pricing
- Fixed price
-
In your enquiry
- Typical length
- 3–9 months
- Pricing
- Fixed price per stage
-
In your enquiry
- Typical length
- 6–18 months
- Pricing
- Priced per written scope
Compare what each plan includes
| Plan | What you get | Best for |
|---|---|---|
| SprintA short, fixed job that answers one clear question. |
|
An audit, a brand check or a test version of an app |
| ProjectOne clear job for one fixed price. |
|
A brand identity, a website, a simple app or a set of tools |
| MilestoneA bigger build in stages you approve and pay for one at a time. |
|
Work too big for one contract, such as a large app |
| EnterpriseA large, long project with its own team and agreed response times. |
|
Large companies making changes across markets, brands or business units |
12Questions
What people ask about AI agents.
What leaders, legal and security teams ask in the first meeting.
Bring to the first call
- The tasks you want to change, with rough weekly volumes
- Who owns each one, and who approves changes to it
- The systems and data each task uses
- How much risk you accept, and your regulators
Start with one busy task that has an owner and usable data. Rule-based back-office work, such as invoice matching or quote drafting, beats open-ended customer chat. We score your ideas, then trial the best one with the agent only suggesting or drafting.
We pick per task from OpenAI, Anthropic, Google, Mistral and Llama, on quality, speed, cost and where data is kept. One link reaches them all, so you can switch later. Inside one agent, simple steps use a small, fast model and hard steps a larger one.
Only at level 4, for named tasks and inside limits you set. Limits cover spend, records changed and business rules, such as a top discount. Anything outside goes to a person. A task gets there only after 90 days at level 3 with few corrections.
Mainly with tight permissions and approvals, as no filter catches every attack. We treat every email and document as untrusted. Each agent has limited access, and risky actions wait for a person. We attack-test each release against OWASP’s list (LLM01, LLM06).
Three things: model use, hosting and the time people spend reviewing. For a back-office task, model use is often a few cents. We track cost per task from the first tests, against doing it by hand.
Both can apply, and we map them in one list. The EU AI Act covers AI offered or used in the EU, or whose output is used there. Most business agents fall in its 2 lowest risk levels. Duties to say when AI is used start in August 2026. After a 2026 change, duties for high-risk uses, such as hiring or credit checks, start in December 2027. India’s DPDP Act 2023 covers personal data of people in India. Under the DPDP Rules 2025, most duties start in May 2027. This is guidance, not legal advice.
Tell us what you need built.
You will talk to the lead who would run your work.
Three ways to start
We always agree a written scope and price before work begins.
Choose one of the three ways above


