Copy, paste, copy, paste
An order lands in the inbox. Someone keys it into Sage, then keys the same numbers again into a spreadsheet only one person is allowed to touch.
Eleven Twelve / 11/FLOW Workflows & automation
Stop typing the same order twice.
Orders in, invoices out, chasing, reporting. We take the jobs your team does by hand every day and make them run on their own, with a person signing off anything that could cost you money.
01 The problem
The jobs that eat your week
Chasing is somebody's whole job
Half of Tuesday goes on invoices that are a fortnight late and quotes sat in someone's sent items since March. It's the first thing to slip when the trade counter gets busy.
Nobody spots it till Monday
Thursday's job didn't run. You found out on Monday when a customer rang about an order nobody had picked, then spent an hour working out how far back it went.
02 What you get
What you end up with
Order in, invoice out
We map one full sequence the way it goes on a bad day, exceptions and all, then build it so it runs without anyone babysitting it. Order lands, gets checked, gets into the system, invoice goes out.
A needs-a-human tray
Anything that doesn't match cleanly stops and sits in one tray with a note saying why. Somebody clicks yes or fixes the line. Nothing gets guessed at and posted to your accounts at 2am.
AI does the messy middle
Reading a purchase order that arrived as a photo of a fax, and working out that a supplier's"12 ea" is your"12". That's where AI earns its keep. Approving stays with your people.
Chasing without anyone chasing
Follow-up goes on day three, the polite nudge on day fourteen. You write the wording so it sounds like you, we set the timing, and each morning you get a short list of who's still ignoring you.
An alarm when it stops
Every run writes down what it did. If Thursday's job doesn't finish, you hear about it on Thursday, and the log tells you which order it stopped on.
03 Why it won't fall over
Why it won't fall over
The systems we sell are already running someone's business.
We built the operations system Embello's team runs on, 50,000 products and 100,000 customers with next day turnaround out of Tamworth, and we've stood in that building watching orders go out while the automation did its bit. That's a different test to a demo. We built the Lordwell website too, 56,000 product lines with live UK stock and next working day delivery, so we know what a Tuesday looks like when a supplier's CSV turns up with two columns swapped.
Maxwell Reeley · Eleven Twelve, Tamworth
04 How it happens
How the build goes
Stage 01
We watch the job
Half a day stood next to whoever does the work now, at the time of day they do it. We want to see the Friday order rush and the bit where they sigh and open the spreadsheet.
Stage 02
One run first
We pick the sequence costing you the most hours and build that one. It'll take weeks, not months.
Stage 03
Run both for a bit
For a couple of weeks the automation runs alongside the manual job and we compare the two. If it gets something wrong, we find out while the old way is still there to catch it.
Stage 04
Hand it over
You get the thing running, the logs, and one page telling your team what to do when it falls over. If you'd rather we kept an eye on it, that's a retainer. If not, it's yours and we'll clear off.
05 Questions
The stuff you're too polite to ask.
Why not just use Zapier for thirty quid a month?
Often you should. If your run is five steps and every one of them is tidy, buy Zapier or Make and keep your money. We're worth paying when the middle is messy: PDFs, part numbers that don't match, an order emailed as a photo of a fax. If a £40 a month product does what you need, we'll tell you on the call and we can both get on with our day.
What happens when the AI gets something wrong?
It will, now and then. That's why nothing goes to a customer or into your accounts without a person saying yes on the bits that matter, and why the needs-a-human tray exists. Worst case you've got a job sat waiting for someone to look at, which is where it was before we turned up. What we won't build is an automation that invents a number on the quiet and posts it.
What if the people who built it disappear?
More than one person here knows your system, so nobody is the only way in. We build on things you can hire for, plain code and standard hosting, no private black box, and every account is in your name. The code and the documentation live in your accounts, so another developer can pick it up and carry on. We take a handful of builds at a time so you get people who know your business, which also means we'll say straight out if we haven't got room for yours.
06 Start
Come and get a free walk-round.
Tell us the one job that eats the most hours and we'll tell you whether it's worth automating or whether you should leave it alone.