The two-day process audit
Two days on site watching how the work actually gets done, then a written report costing every system and subscription and ranking what to automate by what it saves. Most engagements start here.
AI consultancy · Solihull
The National Motorcycle Museum at Bickenhill runs its admissions, e-commerce, events and conference systems on software we built. We start every new engagement the same way: two days working out what your business actually costs to run.
The Solihull market
Solihull's business base looks different from the rest of the region. Alongside the Jaguar Land Rover plant at Lode Lane and the suppliers around it, the borough holds a dense professional and corporate layer — Blythe Valley Park, Birmingham Business Park, and a town centre with a concentration of solicitors, accountants, wealth managers and consultancies serving an affluent catchment across Knowle, Dorridge and Balsall Common.
Then there is the events economy. The NEC, Birmingham Airport, Resorts World and the surrounding hotels all sit inside the borough, and they support a long tail of smaller businesses whose entire year is shaped by somebody else's calendar — caterers, AV and staging firms, transport operators, exhibition contractors, hospitality suppliers. Their problem is rarely steady-state efficiency. It is that demand arrives in spikes, and the systems that cope fine in a normal week fall over in a show week.
That seasonality changes what is worth automating. In a business with an even workload, you automate the thing that happens most often. In an event-driven business, you automate the thing that breaks when volume triples — usually the handoff between taking a booking and telling the people who have to deliver it. The audit is built to tell those two cases apart, because getting it wrong means spending money on the wrong month.
The other Solihull-specific factor is proximity without belonging. The borough is West Midlands rather than Warwickshire, sits on the edge of Birmingham, and many businesses here sell into the city while operating from somewhere quieter. That tends to mean more systems, not fewer — a Birmingham-facing sales process bolted onto a locally-run back office.
Four service lines, in an order we do not skip.
Two days on site watching how the work actually gets done, then a written report costing every system and subscription and ranking what to automate by what it saves. Most engagements start here.
For event-driven businesses, the useful question is not what happens on a normal Tuesday but what breaks during a show. We look for the handoffs that fail under volume, because those are what cost you money and reputation at once.
We built and maintain the admissions, e-commerce, conference and events systems for a major visitor attraction in the borough. It is the kind of software that cannot go down on a Saturday, and that constraint shapes how we build.
For professional practices: client details entered once, routine documents generated from that record, and an audit trail nobody has to maintain by hand.
Built around your process rather than the other way round, with no per-seat licence waiting at the end of it and no vendor able to reprice you at renewal.
Fast, findable, and built to take real transaction volume rather than to look good in a pitch.
What this looks like in practice
Patterns common in Solihull businesses. Illustrative rather than client case studies — the audit establishes which are actually yours.
A job is confirmed by email or phone, then somebody retypes it into the operational system, the rota and the calendar. In a quiet week that is an irritation. In show week it is how something gets missed entirely.
One booking, everyone told automatically
The tool that runs the business perfectly well at forty jobs a month is the same tool being asked to handle two hundred in the week of an event.
Systems sized for the peak, not the average
Selling into larger organisations means their purchase orders, their portals, their supplier questionnaires and their invoice formats. Each one is a small manual job that recurs forever.
Their format, produced from your record
The booking system, accounts package, mailing list and website each hold part of the picture and none holds all of it.
One customer record everything reads from
Four stages. You can stop after any of them.
On site, watching the real work — and in an event business, ideally during a busy period rather than a quiet one.
Every system, subscription and licence, what it does, what overlaps, and where the same data is held twice.
What to automate first, what to leave alone, and the saving attached to each. Yours to keep and yours to take elsewhere.
With the audit fee credited in full against the build if you book within ninety days.
Local proof
Over a thousand exhibits, a conference and events business, admissions, e-commerce and a forty-year operating history — running on systems we designed, built and still maintain. It is ten minutes from Solihull town centre, next to the NEC, and it is the kind of operation where the website going down on a bank holiday weekend is not a technical problem but a commercial one. We are happy to talk about how that was built, and what we would do differently now.
We are based in Kenilworth, roughly twenty minutes from Solihull town centre and fifteen from Bickenhill. On-site work carries no travel charge across this area.
Yes. The National Motorcycle Museum at Bickenhill runs its admissions, e-commerce, conference and events systems on software we built and continue to maintain. We are happy to discuss it in detail.
Not practically — Kenilworth is about twenty minutes from Solihull town centre and we work across the borough regularly. We would rather be clear about where we are than claim a local address we do not hold, which is more than can be said for several sites ranking for this search.
It is the interesting case. Even workloads and spiky ones need different things automated, and the common mistake is optimising the average week when the money is lost in the peak. We look specifically for what breaks under volume.
Most of our work is closer to yours than to a museum. The pattern is the same everywhere: client details entered repeatedly, routine documents assembled by hand, and reporting rebuilt every month from systems that already hold the answer.
Then that is the finding, and you keep the written picture of what you spend. If it does not pay for itself, you do not pay for it.
No. The people who did the audit do the build and look after it afterwards. That limits how much work we can take, which is the trade-off we have chosen.
Connecting the systems you already pay for, then automating the parts of a process that waste your people's time.
Read moreSoftware built around how you actually work, owned by you, with no per-seat licence waiting at the end.
Read moreSites that load fast, read well and are found by the people looking for what you sell.
Read moreIf the audit doesn't pay for itself, you don't pay for it. Twenty minutes from Solihull, and we come to you.