- How long
- 2-4 weeks
- How it is billed
- Fixed fee, one agreement
- What happens at the end
- It ends. There is a deliverable and a decision, and no rolling commitment.
One agreement, agreed before we start. The number comes up on the call, because it moves with the scope and a figure on a page that does not know your scope is a figure you would have to correct anyway.
Development Process
- 011 week
Planning & Design
We finalize requirements, design the solution architecture, define success metrics, and create a detailed project plan with clear milestones.
- 021-2 weeks
Iterative Development
Build the AI solution in 2-day sprints with regular demos. This includes model development, integration with your systems, and user interface creation.
- 031 week
Testing & Refinement
Testing with real users, performance tuning, and improvements on each round of feedback. At the end we confirm the agreed requirements, one by one.
- 041 week
Deployment & Handover
Installed in production or staging, with written documentation, training sessions, and the handover to your team.
Everything it produces presses on one decision.
The failure cases are written together before anyone trusts it, so the pilot ends with an answer rather than an opinion. The answer can be no.
- A working agent on your data
- Real users trying it
- The cases it still gets wrong
Everything below is in the agreement.
Each line is written into the scope before we start.
- A working system, built and installed
- 2-4 weeks of dedicated development
- Integration with existing systems
- Technical and user documentation
- Team training and knowledge transfer
- 1 month of post-launch support
What you'll receive
A complete, production-ready AI solution
- 01
A working system on your data
It runs in your environment, on your data, with the people who do the job using it.
- 02
Technical Documentation
Complete documentation covering architecture, deployment, and maintenance procedures.
- 03
Training and knowledge transfer
Hands-on training for your team to operate, maintain, and improve the AI solution.
- 04
Scale-Up Recommendations
Strategic guidance on how to scale the pilot to full production and expand to additional use cases.
We need three things from you before we start.
Every ask on this list is something only you can bring. The boxes are drawn empty on purpose: ticking them is your call.
A slice of real data
Anonymised if it must be, but real. A proof on synthetic data proves nothing.
An owner on your side
One person who can answer a question the same day and say what good looks like.
The failure cases, agreed first
What the agent must never do, and what happens when it cannot do its job. We write them together before anyone trusts it.
Work that began with this package.
Every one of them is on this site with what it does, what it is built with, and who stays in the loop.
Frequently Asked Questions
While it's highly recommended, it's not required. If you already have a clear AI use case identified and defined requirements, we can start directly with AI Pilot. However, AI Discovery significantly increases the success rate by ensuring we build the right solution.
We select the best technologies for your specific use case. Common choices include OpenAI GPT models, Anthropic Claude, open-source LLMs (LLaMA, Mistral), LangChain, vector databases (Pinecone, Weaviate), and cloud platforms (AWS, Azure, GCP). We prioritize solutions that are maintainable and scalable.
Yes, absolutely. You receive full ownership of all custom code, models, and intellectual property developed during the engagement. We provide complete source code, model weights (where applicable), and documentation to ensure you have full control of the solution.
The package includes 1 month of post-launch support covering bug fixes, minor adjustments, and questions about operation. For ongoing support, maintenance, or new work, we offer separate support contracts or can help you build internal capabilities.
Three steps, and the first one is thirty minutes.
No form to fill in, no scoping document to write before we speak. The call is where we find out whether there is a project here at all, and we will say so if there is not.
- 0130 minutes
A call
Thirty minutes. You describe the job that is slow. We ask what the exceptions are, because that is usually where the work is.
- 022 working days
A written scope
What we would do, what it costs, and what you get at the end. One page, sent within two working days.
- 03The week after
We start
One agreement, signed once. The first round begins the week after.
One path, four stages, and training alongside it.
- 01 / 04
AI Discovery
- Two weeks
- fixed fee
The problem in one sentence, your data seen, one prioritised backlog and a go or no-go.
Learn more - 02 / 04
AI Pilot
- Weeks
- fixed scope
A working agent or skin on your data, with the failure cases written before anyone trusts it.
You are here - 03 / 04
AI Rollout
- Staged
- one agreement
Production on your systems, under your permissions, with our team after.
Learn more - 04 / 04
AI Operations
- Monthly
- rolling
We keep the system running once it is live: monitoring, the fixes, an agreed scope of change each month, and a one-page report.
Learn more
Bring us the problem nobody has cracked yet.
We are a small team of senior specialists. We pick the right model and the right layer, and we build the least machinery that does the job. You get a call with an engineer, not a sales deck.