No slideware, no jargon. Working tools your team actually uses, and the training to make them stick.
A short, fixed-scope look at your workflows, with honest “don’t bother here” guidance.
A custom assistant or pipeline for one real workflow. Smallest useful thing first.
Plain-English training in your own workflows, then support while it beds in.
A survey-equipment manufacturer selling into 60+ countries had deep product knowledge spread across long-serving staff and thousands of documents. Answers existed; finding them took time.
I ran discovery with their sales and support teams, onboarded them onto modern AI tooling, and built bespoke assistants around the two workflows that mattered most.
Non-technical teams, curious about AI, no clear starting point.
A support assistant grounded in their own documentation, and a sales assistant for spec and quoting questions.
Routine questions answered in seconds by the team themselves, and a staff who now reach for the tools without being asked.
Most people in this space can only talk about AI. Most engineers can’t explain it to a team. The useful work happens in between.
I build the working tool and then sit with the people who use it until it’s part of how they work. That second half is where most projects quietly fail, so it’s the half I take seriously.
Build the smallest useful thing, prove it works, then expand. Plain language over jargon. If your team can’t explain it, it won’t stick.
Usually in the repetitive middle of a workflow: the answering, drafting, looking-up and summarising that sits between the work your people are actually good at. The first job is finding those spots honestly, including the ones where the answer is “leave this alone”.
It’s the normal case, and it’s the part I’m built for. Training happens in your real workflows with your real documents, in plain English. The measure of success is that people keep using the tool a month after I leave.
A short, fixed-scope engagement: a few conversations with your team, a look at how the work really flows, and a concrete plan you own whether or not we keep working together.
We decide up front what the tools can see and where it lives. I’ll tell you plainly what each option means in practice, without the compliance theatre.
Tell me what your team spends its week on. If there’s something worth building, I’ll say so, and if there isn’t, I’ll say that too.
Book a short call →