AI agents · workshops · advisory
You do not get a slide deck explaining how and why you could use AI agents. You get one or more productive Agent Crew AI colleagues that your people understand, can steer, and can keep developing themselves.
Typical reply within one working day · The first conversation is free and no-obligation
Services
Most people start with a workshop, because it is the cheapest way to find out whether there is a business case at all. Then we build.
A day where your people build their first agent themselves. Not a presentation about AI — hands on the keyboard, on your own tasks, with your own data. We find the three to five processes where agents actually make sense, and you leave with something that runs.
The format fits 6–14 people from operations, finance, sales or IT. No prerequisites beyond knowing your own work.
From idea to something running in production, integrated with what you already use — CRM, ERP, Microsoft 365, your own systems. We design the agent team, build it, and hand it over with documentation so you are not dependent on us afterwards.
A typical engagement is 4–8 weeks. You own the code, the configuration and the model choices — there is no platform you get locked into.
For those already underway who need someone who has seen it go wrong before. Architecture, model choice and what it costs, governance and EU requirements, and an honest answer about what is not worth building yet.
Can be a fixed day a month, sparring during an internal project, or a second opinion on a decision that is expensive to reverse.
Cases
Insight Estates
An agent team that develops software: a PM/PO who breaks work down and prioritises, an architect and lead engineer who make the technical calls, and a developer who builds. A human reviews and approves — the agents deliver the draft.
Software development · agent team with four roles
Yoga Auckland
A customer-service agent drafts replies, categorises incoming requests and handles refunds automatically within pre-set limits. Anything outside those limits is escalated to a human rather than guessed at.
Customer service · draft replies, categorisation and refunds
Independent management consultant
A finance agent keeps the books, and a sales agent researches relevant work and prepares outreach. What used to wait until the weekend now gets done as it comes in.
Finance and sales · two agents, one person
The tool behind the work
The tool we ourselves use in the first days of an engagement. Describe the goal, upload a few documents, and get three concrete proposals for an agent team — with roles, model choices and an estimate of monthly cost. Free to try.
About us
We are two: one who builds it, and one who knows when it is worth building. We rarely take more than two engagements at a time, because that is the only way we can promise it is us doing the work.
What you get is someone who says no when a task should not be solved with an agent. That happens more often than the industry sales material suggests.
We work from three principles: build the smallest thing that can go into production before you build more. Design the escalation to a human from the start, not at the end. And hand over something someone other than us can read and keep running.
FOUNDER · TECHNICAL LEAD
Has built software for fifteen years and worked with agentic systems since they became useful rather than impressive. Responsible for architecture, model choice and the implementation itself.
LinkedIn
COMMERCIAL LEAD
Many years of experience with business processes in mid-size and large companies. Responsible for finding out where agents actually move the needle — and where they do not.
LinkedInWhat you are probably thinking
Often yes. We can run on EU-hosted models or locally, depending on the task. It is one of the first things we clarify — not something discovered at the end.
It depends entirely on how many systems need integrating, and how much already exists. We give a fixed estimate with a ceiling after the first conversation — and if the task is too small or too early to be worth the money, we say so instead.
Then it is a bad idea to build. That is why the workshop is usually the right first step: it shows whether you have the people, and if you do, it enables them.
A workshop leaves you with something running the same day. An implementation typically has something in production after three to four weeks.
No. You own what is built, including configuration and model choices. Handover includes documentation written to be read by someone other than us.
Contact
We will come back with whether it is something we can help with — and what it would take.