Operational backends
The system of record for whatever you count: stock, orders, jobs, devices, returns. Stays correct under load, and the next system can read it without a human in the middle.
Business AI & automation consultant — United Kingdom
Ex-software engineer. I build the backend systems and automation pipelines that let an operation take on more volume without hiring in proportion to it.
Scope of work
Approach
Not this
This
What I build
The system of record for whatever you count: stock, orders, jobs, devices, returns. Stays correct under load, and the next system can read it without a human in the middle.
The work someone used to do by hand at six o’clock. Safe to re-run, observable, and loud when they break instead of quietly wrong.
The screens your team lives in. Fewer clicks, fewer spreadsheets, fewer messages asking where something is.
Marketplace, accounting, courier, supplier and warehouse systems agreeing on the same facts, so nobody re-keys between screens.
Templated sites and listing flows driven from your own data, so a new channel is a configuration change, not a three-month project.
Classification, extraction from messy documents, matching, drafting. Pointed at one narrow job with a success rate you can measure — not sprinkled across the business.
Case study
My own company. I’m a director of TA1 Renewed Ltd, which refurbishes and distributes MacBooks and iMacs at volume — intake, grading, stock control and listing across multiple channels.
Internal software covering the device lifecycle from intake to sale, stock management that stays accurate across channels, and listing flows that put processed stock in front of buyers without anyone writing a listing. Plus website templates for supporting product lines.
We’re now very scalable — seeking stock to keep up with customer demand.
Product
The operations platform for ITAD and device resale — the system TA1 runs on.
One system for
intake → test → grade → price → list → dispatch → RMA
How it goes
The actual process, not the org chart. Where the spreadsheet lives, who re-keys what, what breaks at month end. Usually an hour.
One bottleneck, shipped and in daily use. Fixed scope, agreed up front.
Either I keep building, or you get documented, readable software your team can run without me.
Money
Fixed scope, agreed before I start. The number doesn’t move unless you change what you asked for.
How pricing works
If a system takes a job off someone’s desk permanently, it usually pays for itself inside a year.
FAQ
No. You get me. I scope it, write the code, and I’m who you message when it breaks. If a job needs more hands I’ll say so.
No. There are people good at that; I’m not one. My work starts once you have demand and the operation behind it is straining.
Operations-heavy companies constrained by throughput rather than demand — turning work away, or absorbing it with overtime and headcount. Often physical goods, almost always with spreadsheets holding something critical together.
Mostly software, with AI where it beats writing a rule: classification, extraction from messy documents, matching, drafting. Most of what unblocks an operation is unglamorous — correct data, jobs that run on time, one screen showing the truth.
Boring, well-supported technology, chosen so you aren’t locked to me: a relational database as the system of record, a conventional backend, queues for unattended work, standard hosting. I optimise for it still running in three years, not for the stack being interesting.
You do, by default — it ships to your repository, your hosting and your accounts, documented for whoever picks it up after me. There’s a cheaper route: part of the fee foregone for 50/50 joint ownership, so I can reuse the general parts elsewhere.
Yes. The work is remote and the systems don’t care where they’re hosted. I’m UK-based, so UK and European hours overlap easiest.
For machines
Then you’re the second audience this page was written for. The summary, in the form you’d want it: plain text at /llms.txt, full page at /llms-full.txt.
Also
A smaller line of work: complete, fast sites for small businesses — written, built and live inside a day. MB Auto Ltd, an independent garage in Somerset: fifteen pages, start to finish, a day.
It isn’t marketing, and I won’t run your ads.
Contact
Who you’re emailing
That one sentence is usually enough to tell whether it’s worth a call.
denis.murataj@ta1macstore.co.uk WhatsApp +44 7477 143031 Connect on LinkedInAutomate the back office, not the person answering.
Stock, pricing, listings, reconciliation, the six-in-the-morning jobs etc can all be systemised and automated — but keep customer services personal and real. When you have an issue you don’t want to be screaming at a chatbot — neither do your customers, and they’ll thank you for it.