I build practical AI systems, train the people who use them, and stay responsible for them once they land. Built, taught and kept running by the one person who made it. Adelaide based, working with businesses across Australia.
Built. Taught. Kept running. For operators, finance teams and business owners who need the thing to work on a Tuesday.
Plenty of people can stand up an AI tool. The hard part starts the day it lands on someone's desk. The dashboard nobody opens. The automation everyone quietly works around. The chatbot that gets asked three questions and then forgotten.
That is not a technology problem. It is a handover problem. The system was built for the brief instead of for the person, and nobody was ever shown what it changes about their day.
I treat the handover as the product, and the software as the part that gets you there.
Start with the problem in front of you, whether it needs a hard look, something built, your people trained, or someone to keep the whole thing running afterwards.
Best for deciding what is worth doing
A short, sharp piece of work that finds where AI genuinely pays and where it is a distraction. You get a plain ranked list, not a strategy document.
Best for repeatable work
The working thing, wired into what you already run. Your ERP, your CRM, your spreadsheets, your email. Built to be handed over, documented, and owned by you.
Best for confident adoption
A half-day workshop, a tailored program built from a discovery session, or a session every month as confidence grows. Always on your own systems and your own work, never a generic slide deck. Yours whether I built the system or not.
Best for life after handover
I look after the systems I built for you. Every build ends with a month of support included, so the switch actually happens, and after that you pick the level that matches how much you lean on it.
Training
Training built from your own systems and your own work, never a generic slide deck. You do not need to have bought anything from me first, and you keep the written guide afterwards.
Book trainingHands-on with your real documents and real tasks, sized for a whole team in one sitting. You leave with a written guide built from what we actually worked through.
I sit with your people first and find out which systems they really use and what they are really trying to do. The sessions get built around that, not around a template.
Ongoing training as confidence grows and the tools keep changing. It works on its own or folded into a support plan for a system I built you.
What AI gets wrong, what must never be pasted into it, when to stop and check, and how to tell a confident answer from a correct one.
Every build ends with a month of support included, so the switch from the old way of working actually happens rather than quietly stalling. After that you pick the level that matches how much you lean on it, or you pick nothing at all.
Anything broken gets fixed, anyone in your team can ask me anything, and small tweaks are free. New features are quoted like any other work. It is part of the handover rather than a separate invoice, because the first month is when a new system either takes hold or gets worked around.
It stays running. I fix anything that breaks, keep an eye on the health of the system, and send you a short note once a month on what it has actually been doing.
The small changes and adjustments that come up as the work shifts, so the system keeps matching the business instead of slowly drifting away from it.
Includes everything in EssentialA standing block of time each month for new work and ongoing training, for the businesses where this has become part of how the place runs.
Includes everything in ActiveThe home page stays focused on services. The separate portfolio contains seven detailed systems, each with the problem, build, outcome and four expandable screens.
Explore AI operations, business intelligence, automation, internal software, KirCob and Reflect without losing your place in the Bots & Pieces site.
Leadership had a business intelligence tool that nobody opened, because a single dashboard took most of a minute to load. Teams had gone back to exporting spreadsheets by hand and arguing about whose numbers were right.
I rebuilt the platform from the ground up, indexed the underlying data properly, and precomputed the heavy figures overnight instead of on every click.
Sales, finance and operations each pulled their own extracts from the ERP, the CRM and a pile of spreadsheets. Every meeting started by reconciling numbers that should have matched.
I built a central data warehouse that pulls live from every source on a schedule, plus monitoring that flags a stale or broken feed before anyone reports it as a data problem.
Setting up a new employee crossed half a dozen systems and took most of a day, and the steps were held in one person's head rather than written down anywhere. Undoing it when somebody left was worse, because access quietly stayed switched on.
I automated the whole chain from a single trigger: the account, the licence, the group access, the mailbox, the phone and the device, with a written record of every step as it happened.
The recurring work that keeps a business honest, the data checks, the digests, the chasing, the reporting, was all manual, and so it was the first thing dropped in a busy week.
I built an operations control centre that runs those jobs unattended on a schedule, shows the health of every one in a single view, and switches to a backup path automatically if a service is unavailable.
Staff were moving between separate tools for CRM, EOS, spreadsheet-style work, IT help, receivables and account applications. That meant repeated sign-ins, disconnected records and no single place to see what needed attention.
I built an Operations Hub: one authenticated, mobile-ready internal platform that brings those workflows together while leaving the ERP as the financial system of record.
A private shared household app for projects, repeating tasks, shopping, meal planning, photos, notifications and two-way Google Calendar sync.
A mobile-first reflection and mental-health journal with long-term memory, guided check-ins, pattern review, offline support and strict owner-only privacy.
Four stages. You can stop after any one of them, and you keep everything produced up to that point.
Half an hour on what is actually slow, expensive or annoying. If AI is not the answer, I say so on that call and there is no invoice. That happens more often than you would expect.
You leave with: a clear yes, no, or better next step.
Time watching how the work really gets done. For a build, that becomes a ranked list of opportunities with an honest estimate of cost, effort and what each one saves. For training, it is what the guide gets built from, so the material covers your systems and your use cases rather than generic examples. Fixed price, and yours to keep whatever you decide next.
You leave with: a ranked opportunity brief with cost, effort and expected value.
I build the narrowest version that solves a real problem end to end, and get it in front of the people who will use it early. No six-month project that reveals its flaws on delivery day.
You leave with: a working pilot tested by the people who use it.
Training on your own work, written guides, and the accounts and the code in your name. Then a full month of support included, so the switch actually happens, and a plan afterwards only if you want one.
You leave with: the code, the accounts, the guides and a month of support built in.
No account manager and no mystery delivery team. You work directly with the person responsible for the result.
The person behind the systems
AI systems, training and ongoing support, Adelaide
Bots & Pieces is run by Jacob Roberts. You work directly with the person who maps the problem, builds the automation, trains the team, keeps it running afterwards and stays accountable for whether it works in the real world.
That comes from more than eight years in technology and from running the whole systems function inside a multi-entity operating environment: Microsoft 365, ERP, reporting, integrations, automations and the staff who rely on all of it. Knowing how a business actually runs is why the systems land.
Usually not. Smaller businesses often get more out of it, because one person is doing four jobs and the repetitive parts of those jobs are exactly what this removes. The first call is free and will tell you honestly either way.
No. Every system described on this page took work off people rather than taking people off the payroll, and the ones that stuck were the ones the team wanted to keep. If your goal is headcount reduction, I am probably not the right fit.
It is a real question and it gets answered before anything is built. Depending on how sensitive the work is, that can mean keeping the data inside your own tenancy, stripping identifying details before anything is sent, or running the whole thing on your own infrastructure. You will know exactly what leaves your business and where it goes.
The first month after handover is included in the build, so anything broken gets fixed and anyone can ask me anything while the system beds in. After that there are three levels of monthly support to choose from, or you can take none. You own the code and the accounts from day one either way.
No. Everything is documented in plain language specifically so somebody else can pick it up, and the code and accounts are in your name. The plan exists because most people would rather I kept looking after it than because you would be stuck without it.
Not as a service any more. I do not take on helpdesk work, devices, printers or general Microsoft 365 administration. What I do keep doing is looking after the AI systems I have built for you, which is a different job, and the years of IT behind me are why those systems fit how a business actually runs.
Discovery is a fixed price agreed upfront. Builds are quoted per project once you and I both know what is being built, never open-ended hourly. Training is priced per session or per group, and support plans are a fixed monthly amount set once I know what I am looking after. You will never get an invoice for something that was not agreed first.
Half an hour on what is slow, expensive or annoying in your business. No slides, no obligation, and a straight answer on whether this is worth doing at all.
Online booking is not switched on yet, so this emails me to arrange a time. You can also just call.
Or reach me directly.
Pick the work, then fill in four boxes. I reply within a working day.