Plenty of firms know they want to do something with AI, and have no idea where to start. So before anything gets built, we help you work out which of your processes an agent would genuinely help with.
It's the thinking that happens before a build: working out whether an AI agent is the right answer for you, and if it is, what it should do.
There are no workshops to buy here, and no slide deck at the end of it. The advice is either the start of building something useful, or the honest reason not to.
When a firm comes to us unsure, the work is practical. We look at how a process actually runs. We'll investigate if it's a good fit for an agent, and if not, we're up-front about it.
Every firm starts from a different place. A scoping conversation usually covers these four things.
Not the ideal version from the manual; the real one. The steps people actually take, and the exceptions they work around. Where the time goes, and where the process tends to break down.
You can't automate a process well until you genuinely understand it.
An honest AI readiness assessment. We'll check if there's enough volume to be worth it. Are the rules clear enough to hand to an agent? Are your data and systems in the right state to support one?
Readiness is about your processes and your systems, not how much AI you've read about.
For the processes that fit, we sketch out what an agent would actually do. Where it picks the work up, and what it works through. What it puts back (and where it puts it). Concrete enough that you can picture it, before any building starts.
See how it'll work before it gets built.
Some processes aren't ready for an agent because something else has to come first. It could be a rule that's interpreted differently by different people. Or data that isn't where it needs to be. We point them out, so you know what you'd be solving before any agent gets near it.
Sometimes the right first move is fixing the process, not automating it.
AI consulting isn't a product we sell on its own. It's the doorway into how we actually work: design, build and run. If a scoping conversation shows an agent is worth building, that's the natural next step, and the same team carries it through.
Nothing about a scoping conversation commits you to anything. If it turns out an agent isn't the right answer, you'll hear that plainly, and you can walk away knowing it. Knowing where AI does and doesn't fit your firm is worth something on its own, whether or not we end up building a thing for you.
The first conversation is free. Thirty minutes, no obligation, and no expectation that you take it any further.
We don't bill for advice by the day or by the workshop. If a piece of scoping work ever sits between conversation and build, we'll be clear about exactly what it involves before you agree to anything.
That's when the commercial model starts: a refundable commitment per agent, then per-output billing once the agent is live.
There's nothing to pay.
Here's an example. A firm comes in wanting to use AI across their back office, with three processes in mind.
A team checks incoming form submissions against a defined set of rules. A few hundred come in each week. The rules are settled and most cases are routine. The bit that takes time is the volume, not the difficulty. Verdict: build an agent.
A weekly report has been frustrating the team for months. Three people compile it three different ways, and the format shifts depending on who's asked for it. There's nothing for an agent to standardise on yet, because the process itself isn't standardised. Verdict: fix the process first.
A piece of work comes up twice a month. One person handles it in an afternoon and nothing about it is broken. Building an agent for it would cost more time than it would ever save. Verdict: leave it alone.
One agent worth building, one thing to fix and one thing to leave well alone. That's a good outcome, even though only one of the three became a build.
This is an illustrative example. What a scoping conversation turns up depends entirely on your firm and your processes.
No. That's exactly who a scoping conversation is for. Plenty of firms arrive knowing only that AI should probably be useful to them somehow. Working out the what, and the whether, is the job, and you don't need to have done any of it first.
No. It's a real working conversation about your processes, and sometimes it ends with us saying an agent isn't worth it for you. We'd rather tell you that than sell you something that won't earn its place.
Not much. A rough idea of the processes that frustrate you, and ideally someone in the room who knows how those processes actually run day to day. We'll take it from there.
Then we'll tell you, and explain why. You'll have spent half an hour and learned something useful: that your money is better spent elsewhere for now. That's a genuine result, not a wasted call.
We build and run them. The advice comes from the people who would have to make the agent work, which is why it tends to be practical rather than theoretical. We're not a day-rate consultancy that hands over a strategy and leaves.
If an agent is worth building, you move into a build, designed, built and run by the same team. If it isn't, nothing happens, and you're under no obligation. Either way, you leave with a clearer picture than you came in with.
We design it. We build it. We run it.
You only pay when it delivers.