Make AI earn its place in your business.

We work out where AI is genuinely worth using, then build the system and stay until your team runs it without us.

A quick, honest check of how your business would handle the changes AI brings. Two minutes, no sign-up.

Where would AI earn its keep in your business?

Paste your website. We'll read it and tell you where, in a business like yours, the hours quietly go and whether AI would help. Before anyone books a call.

https://

No website, or it doesn't say much? Tell us in a sentence instead.

Prefer a quick self-check? Take the two-minute adaptability test.

Sound familiar?

It's almost never the technology that's stopping people. It's not knowing where to begin.

Five things people say to us on almost every first call. Here's what we know about each.

01

We don't have the expertise in-house — and hiring it is brutal.

The most common reason businesses hold back, and the obvious fix is the slow one. A “Head of AI” search runs for months, the title means something different at every company, and the few people who've genuinely run AI inside a business are gone before most ads close.

02

We wouldn't know where to start.

In one survey of 1,000 UK small-business leaders, 41% said they want to adopt AI but don’t know where to start. Not “AI is useless”, just no obvious, sensible first step.

03

We tried a pilot and it went nowhere.

Most pilots never reach production. The widely-cited studies put failure rates for AI projects above 80%, roughly double the rate for ordinary IT projects. A failed attempt can cost an SME £20,000–£80,000 in direct spend alone, before the internal time.

04

Our people are worried it's here to replace them.

Adoption usually stalls on fear. When researchers go back and ask why AI projects failed, it's almost never the technology. It's that the business wasn't ready and the people weren't brought along. The less prepared the company, the worse it goes.

05

We can't tell the real thing from the hype.

Every product now claims AI. Without someone independent in the room, it's hard to know which claims survive contact with your business.

Sources: Indeed survey of 1,000 UK small-business leaders (41% want to adopt AI but don't know where to start); BT Business, The AI Opportunity for Small Business (60% cite lack of understanding); RAND, The Root Causes of Failure for Artificial Intelligence Projects (RR-A2680-1, 2024); Melbourne Business School Centre for Business Analytics, Why do analytics and AI projects fail? (2024). Implementation cost ranges are typical UK SME figures from 2026 industry reporting.

Listening in a working session, notes being taken.
How a Blueprint works

Two weeks. One workflow. A plan you could hand to anyone.

Fourteen days, day by day. Here's exactly what happens in each.

  1. Day 1
  2. Days 2–4
  3. Days 5–7
  4. Days 8–10
  5. Days 11–13
  6. Day 14
Day 1

We sit with the people who do the work.

Not the org chart — the person who chases the invoices, re-keys the order, builds the forecast in a spreadsheet at 7am. Half a day, no slides.

What we're listening for
"I do that every Monday. It takes the morning."
The sentence that usually starts a Blueprint
Days 2–4

Every workflow gets a number.

Hours a month, error rate, what a late decision costs. Most businesses have three or four candidates, and one is usually obvious once it's on paper.

A real one
  • Payment chasing — best part of a week a month
  • Quote turnaround — two days, often lost to a rival
  • Month-end reporting — three people, four days
Collections client, before the Blueprint
Days 5–7

We design what happens when it's wrong.

We pick one workflow off that list and draw it end to end: what the AI does, what a person still signs off, where it stops and asks. This is where we decide the controls, rather than adding them after something goes wrong.

The rule we don't break

Anything that touches money or a customer gets a human approval step. Always.

Days 8–10

If it's going to fail, it fails now.

A working slice, run on your real invoices, orders and forecast history. Better to find that out for the price of a Blueprint than halfway through a Build.

What you see
  • Your last month, run start to finish
  • Every decision it made, and why
  • The ones it got wrong, flagged
Warts and all
Days 11–13

Costs, dates and an owner against every line.

Who owns what, what it costs, and what "working" means in numbers. Written so your finance director can read it and your ops lead can run from it on Monday.

Plain English, deliberately

If the plan needs us in the room to make sense, we've written it badly.

Day 14

You decide. With us, or without us.

The plan is yours: some clients build it themselves, some bring their own developers, most ask us. We'd obviously rather it was us, but you'll have a plan that works either way.

Then, if you want it
  • Build — six weeks to a working system
  • Embed — the part where it sticks
How we help

Get the workflow right, then build something your team will actually use.

The Woodlark Academy

Learning that survives the training day.

Practical sessions for teams who want to know what AI is good for, where it bites, and what to do about it. Not a certificate.

Book a conversation ↗
  • Get your bearingsPlain-language guidance on where AI can add value — and where it cannot.
  • Pick a first projectPractical ways to choose useful use cases before buying or building anything.
  • Make it routineSimple governance and team habits that turn experimentation into confident use.
The proof

We don't advise on this from a distance. We build with it every day.

The numbers below aren't projections. The first two are a client's, from their own management accounts; the rest are counted from the systems we built and run inside our own business.

6.5%
net-margin improvement across operations
six months against the previous six
13
working days to build the system
and hand it over
30+
AI agent roles running a real company
around the clock
~£400
a month runs the whole fleet
every agent, every day
~3
months to build it
part-time, alongside the day job

Client figures: a leading UK logistics business, from its own management accounts, comparing six months of trading with the previous six. Approved for publication; the company is not named. The remaining figures are our own, counted from systems we run.

The control problem

Autonomy is earned, one approval at a time.

How do you hand real work to AI without losing control? In our own company, every agent has to earn it: three tiers of autonomy, against three levels of stakes. Clean approvals move it up. One bad call moves it straight back down.

Each tier, at low, medium and high stakes.

Autonomy, earned approval by approval
Low stakes Medium High stakes
Do Earned at ~30 approvals
Does the work. You read the audit trail.
Does the work — inside hard spend caps.
Does the work — with tripwires that escalate to a human.
Suggest Earned at ~20 approvals
Drafts the action. One tap to approve.
Drafts the action. You approve or edit before it moves.
Drafts the action. A named approver signs it off.
Report Earned at ~10 approvals
Watches, logs, and tells you what it sees.· every agent starts here
Watches, and flags what looks off.
Watches only. High-stakes work always starts here.
Low Stakes — the cost of getting it wrong High
  • Approve — the right call. One approval closer to the next tier.
  • Edit — close, not quite. Your correction is fed back into the agent; its tier holds.
  • Reject — you say why, in a line. The agent takes the lesson and drops straight back to the bottom tier.

Ours have earned the top row: last night, while we slept, they answered support in 13 languages, reconciled the day's numbers and drafted this morning's content. Every move on the board is reversible. When you correct a draft, that correction is written into the rules the agent works to next time, so the same mistake gets caught once rather than every week.

Book a conversation.

Thirty minutes with a founder. We'll tell you where AI is worth using in your business, and where it isn't. Plain answers, no pitch.

Book thirty minutes ↗