AI agents · first step
Your AI pilot works in a demo. We get it into production
Most AI pilots stall on the same questions: what the agent may see and do on its own, how you know it is right often enough, and what it will cost at full volume. We review your pilot against those questions and give you a priced plan to ship it. If you build with us, the fee is credited in full.
What we check
What the audit covers
- Data: what the agent can see, how fresh, who is allowedWe trace each source the agent reads, check how current it is, and test that it can't show a user records that user isn't allowed to see.
- Permissions and approval: what it may do on its ownWe list every action the agent can take against what its role should allow, and mark which ones need a person to approve before they happen.
- Evaluation: how you know it is right, before and after launchWe look for a test set built from real cases and a pass mark the business agreed. If there isn't one, we draft it from your past cases and run the pilot against it.
- Running cost per task, and the plan to ship with its priceWe measure what each task uses on real examples, project the monthly cost at your volume, and price every piece of work between today and launch.
What you get
A plan you can act on, with or without us
- One-page verdictShip as it is, ship with fixes, or rethink, and the three things that decide it.
- Findings by areaData, permissions and approval, evaluation, logging and cost, each with the evidence we found.
- Every fix pricedEffort in days and cost in euros, in the order that unblocks production first.
- Running cost at your volumeCost per task and per month, and where a cheaper model would do the same job.
- Walk-through callWith your team, and anyone who has to approve the launch.
- Yours to keepWritten so your own team or another supplier can act on it without us.
Timeline
From access to plan
- Day 0
Kick-off
NDA signed, read-only access to the code, prompts, logs and any test results, and a call with whoever built the pilot.
- Days 1–3
Review
Data access, permissions, approval points, evaluation, logging and cost, tested against real examples from your business.
- Days 4–5
Plan and price
Every finding turned into a fix with days and a price, ordered by what blocks launch first.
- Day 5
Walk-through
The verdict, the plan and your questions, on a call with your team.
What we need from you
A few hours of your time
- Read-only accessThe repository, prompts and configuration, and logs of the pilot's runs. We never need production write access.
- A 60-minute kick-offWith whoever built the pilot and whoever owns the process it is meant to run.
- Real examplesA sample of past cases the agent should handle, and any notes on where the demo went wrong.
What it is not
Clear about the edges
- Not a buildWe don't change your system during the review. Fixes come after, with you or with anyone else.
- Not a penetration testWe tell you if you need one and work alongside the tester.
- Not legal adviceWhere the EU AI Act or GDPR may apply, we say so. Your lawyer confirms.
Questions
Before you book
We built the pilot with another vendor. Can you still help?
Yes. We need read-only access to what they built and an hour with someone who knows it; the vendor doesn't have to take part. The report is about the pilot, not about who built it, and is written so any team can act on it.
Do you only work with Claude?
No. Claude is our default for our own tools, but the review works with whatever your pilot runs on, whether that is OpenAI, Google or an open model in your own cloud. Sometimes the fix is a different or smaller model; sometimes it is no model at all for part of the task.
Is the review fee credited?
Yes. If you build or fix with us, the review fee is credited in full against the build. If you don't, the report is still yours to use.
Who owns the code and the IP?
You do, from the first commit. We work in your repository and your accounts, and the contract assigns the IP to you in the present tense, not at some later date.
Who will actually work on our project?
The engineers named in the proposal, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.
How do time zones work for a UK or US team?
We work on Lisbon time, which is the same clock as London: Mon–Fri, 08:00–18:00 UK time. That leaves about four working hours a day in common with the US East Coast. You get a demo of working software every week and a short written update every working day.
What contracts do you sign?
A master services agreement with a statement of work for each project, or your own paper if you prefer. A mutual NDA before we see anything, and a GDPR data processing agreement. US clients get a W-8BEN-E from us. Which law governs the contract is answered on Contracts & security.
How do we pay?
The fixed-price first step is paid upfront. Builds are billed by milestone, after you have seen the work running. Monthly care, if you want it, is billed at the start of each month. We invoice in euros, pounds or dollars.
Free 30-minute call
Tell us what has to work, and by when
You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.