DEEPGRAIN · AN OPERATING CONSULTANCY BUILT FOR THE AI ERA.
Find your builder. Move your middle layer.
Agents take the repeatable work. People learn to design, run and extend them. When we leave, the capability stays in the team, not in a vendor.
- 37
- Champions trained
- 11
- Functions reshaped
- 0
- Vendor lock-in
Where the value is
Find your builder. Move your middle layer.
One person. Three workflows shipped. The whole function shifts.
In every function there is one person who is already doing this. Find them, name them, give them air cover and a fifth of the week. The upside is asymmetric.
- ↗Already wires their own tools together on the quiet.
- ↗Talks about the work in workflows, not headcount.
- ↗Has a backlog of friction they'd fix if anyone asked.
Where the value leaks. Three postures, all real.
The middle layer decides whether the practice spreads or stalls. They are not the enemy. They are watching to see whether you mean it.
- Leaning in
Curious, asking how to use the new tools well. Multiply these people first.
- Freezing
Quiet, watching. Will move once the first builder ships something visible.
- Resisting
Active brake. Often the most experienced. Needs honest air cover, not training.
The matrix
Not every role automates. Most have a piece that should.
Cross the role type with the automation potential of the clicks inside it. Six honest answers, no slogans.
Builders. Automate the routine off their desk so they do more of what only they can do.
Senior judgement, founder relationships. Leave alone. The leverage is human.
Coordination, scheduling, follow-up. Agents do this well. Redesign the role around what is left.
Trusted-advisor work. Slow change. Keep the human, surface better information underneath.
Compliance checks, policy queries, control evidence. High ROI, requires governance.
Investigations, judgement calls, escalations. Agents brief. People decide and own.
People upskilled
What the metric means.
When we report “people upskilled” at the end of an engagement, we mean three things. Not certificates. Not seat licences. A change in what the team can do without us in the room.
Everyone in the function can brief an agent and judge its output. The work stops feeling foreign.
Three or four champions design and ship workflows themselves. They are your internal builders.
The capability stays after we leave. New joiners pick it up from colleagues, not from a deck.
The champion model
You need three or four champions, not engineers.
A champion is someone already inside the team. A senior coordinator, a People Partner, an Ops lead. Someone with deep tacit knowledge of how the work flows, and curiosity about wiring things together. People you already pay, given a different mandate.
This works because of grain. Champions know where the friction is, because they live in it. They know which approvals are theatre and which handoffs drop information. An engineer would have to discover all of that. The champion starts with it.
Three or four champions, spread across the function, give you something a single builder cannot. Review. Shared patterns. Cover when one is buried. The nucleus of a real practice.
- Air cover
A named exec sponsor, and a protected fifth of the week that does not get pulled into the next crisis.
- Tools and budget
One workflow tool, an LLM provider on the right terms, a small monthly budget with no procurement friction.
- A small starting brief
One bounded, painful workflow owned by a willing colleague. Not a programme. A first build.
The coaching curriculum
Six modules, run alongside the build.
The curriculum runs in parallel with shipping real workflows. No classroom phase. People learn the craft on their own systems, with their own data, on problems they already wanted to solve.
Where agents fit, and where human judgment has to stay.
Prompts as specifications. Writing for a system that has to act.
Tools, triggers, and handoffs. The plumbing that makes an agent useful in a real working day.
What stays human, what gets reviewed, what gets logged.
Hours saved, judgment freed, capability gained. A real story about what changed.
Running the champion circle after we leave. Reviewing each other's work. Training the next one.
What you walk away with
A practice the team holds.
- Three or four trained champions inside the function.
- Eight to twelve production workflows, owned by the teams that use them.
- A governance pattern your team understands and can defend.
- Capability that keeps growing into corners we never touched.
Six months on, the champions are still building. They have extended the work into places nobody asked them to touch, and they are training the next champion. That is what capability looks like.
Onboarding & after
What working with us actually looks like.
- How does onboarding work in the first two weeks?
- We name an exec sponsor, identify three or four champions inside the function, and pick one bounded, painful workflow to build first. No procurement marathon, no tooling debate — we use what you already have where we can, and stand up the missing pieces (an LLM provider, one workflow tool) on the right terms in week one.
- Who from our team needs to be involved, and how much of their time?
- An exec sponsor for air cover (a few hours a month), and three or four champions giving roughly a fifth of their week. Champions are existing senior coordinators, People Partners, or Ops leads — people you already pay, given a different mandate. We do not need engineers.
- What does the coaching curriculum actually cover?
- Six modules run alongside live builds: reading the grain, briefing agents, wiring workflows, governance and trust, measuring value, and sustaining the practice. There is no classroom phase — champions learn the craft on their own systems, with their own data, on problems they already wanted to solve.
- What happens after the engagement ends?
- Champions keep building. They extend the practice into corners we never touched, and train the next champion. We stay reachable for occasional questions, but the capability is genuinely held by the team — not parked with a vendor on a retainer.
- How do you measure that the capability has actually transferred?
- Three signals. Champions ship a workflow we did not scope, end-to-end, without us. A new joiner is brought up to speed by a colleague rather than a deck. And six months on, the workflow count has grown — not flatlined. If those are not true, the engagement did not land, regardless of hours saved.
The first move
Map one workflow with me.
Thirty minutes. Twenty mapping, ten agreeing the first move.