Practical AI systems built the way you work.
I build systems that take repetitive work off your team, fit the way they already work, and keep running afterwards. Based in Adelaide, working Australia-wide.
- AdelaideAustralia-wide
- 10+ yearsTechnology
- Your dataYou decide where it goes
- You own itCode and accounts
- NV1 clearedAustralian Government security clearance
- 1Capture the detailsOne record. No retyping.
- 2Draft the next stepAI prepares. Your team decides.
- 3Keep the follow-up movingA clear owner and next action.
What do you need help with?
Choose the work you need. Expand a service for details, or browse ready-to-brand systems in the Systems Studio.
Best for repeatable work Build the system Quoted against what it saves you, never open-ended hourly
The working thing, wired into what you already run. Your ERP, your CRM, your spreadsheets, your email. Built to be handed over and documented.
- Connects to your live systems, not a demo copy
- Anything touching money or customers gets a human check
- The code, the data and the accounts go into your name
- If any part has to run on my infrastructure, I tell you upfront and price the alternative
The quote is set against what the current way of doing it actually costs you: the hourly rate of whoever does it, multiplied by how long it takes, multiplied by how often it happens in a year. I compare the build and ongoing costs with an estimated saving, allowing for adoption and the time your team still needs to spend. We review those assumptions together before agreeing to the work; the estimate is not a guarantee. If the saving does not clearly justify the cost, I tell you plainly rather than build it anyway. Smaller, ongoing improvements are bundled into one set price rather than sold piecemeal as separate projects.
Ask about a build See related dashboard workPractical AI systems support after launch Keep it running Confirmed once I know the system
Optional care for systems I built. The first month of your chosen plan is included in the build. No lock-in; cancel at the end of any month. Prices are confirmed once I know the system.
If the system is down, or nobody can do the work it supports, you hear from me the same business day.
-
EssentialLevel oneConfirmed once I know the systemBest for a system that just has to stay up
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. Includes one hour of fault work a month.
Ask about Essential -
Most chosenActiveLevel twoConfirmed once I know the systemBest for work that keeps changing shape
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 two hours of changes a month.
Includes everything in Essential Ask about Active -
EmbeddedLevel threeConfirmed once I know the systemBest for when the system runs the place
A standing block of time each month for new work and for showing your team whatever has changed, for the businesses where this has become part of how the place runs. Includes four hours a month.
Includes everything in Active Ask about Embedded
First-month cover and response targets
In month one, faults are fixed, your team can ask questions, and small tweaks are included. New features are quoted separately.
How quickly you hear back
| If this happens | You hear from me |
|---|---|
| The system is down, or nobody can do the work it supports | Same business day |
| A material function is wrong, but there is a way around it | Within two business days |
| A question, a small fault, or a change request | Within five business days |
Business hours, Adelaide time. These are first response targets rather than resolution times, and they are the same ones written into the support agreement you sign. Faults are answered by message during the day, and a call is arranged when one is needed.
How an engagement runs
Four stages. You can stop after any one of them, and you keep everything produced up to that point. From the first conversation to handover usually takes four to eight weeks.
- Conversation30 minutesFree
- DiscoveryAbout a weekStop point
- Build and test2 to 6 weeksStop point
- HandoverAbout a weekStop point
Who you are actually hiring
No account manager and no mystery delivery team. You work directly with the person responsible for the result.
Jacob Roberts
AI systems, built and kept running, Adelaide
More than ten years ago I started running the technology side of an Australian business: ERP, reporting, integrations, automation, whatever needed a system to actually work. That's still the job, just under my own name now instead of someone else's.
Explore systems I have built and operated across reporting, business workflows and automation in the project portfolio. Each case study explains its context, what it delivers and the limits that matter.
- 10+ years in technology
- AI and automation
- System integration
- ERP and reporting
- NV1 security clearance
- Adelaide based
Fair questions
Cost
It always starts with a free half-hour conversation, no obligation, before you spend a cent. If that points to something worth a proper look, I first work out what the current way of doing it actually costs you: who does it, how long it takes, and how often it happens in a year. That gives a real number to quote against, so the price is set to land comfortably under what you stand to save, not against a fixed list.
If the saving does not justify the cost, I tell you plainly and you owe nothing further. Smaller, ongoing improvements are bundled into one set price rather than sold as separate projects. Support is only ever for a system I built or configured for you, whether that's a custom build or one from the Systems Studio catalogue. It's optional, has three levels depending on how much ongoing change the system needs, and is confirmed once I know what I would be looking after. You will never get an invoice for something that was not agreed first.
Your data
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.
Your information is not put into any AI service that has not been agreed for your engagement, and it is never handed over for training a provider's general model unless you approve that in writing. The default is that it is not. This is written down rather than promised on a call.
I also hold an NV1 security clearance from the Australian Government. That is a check on my own background and trustworthiness, not a certificate for your data. What keeps your data safe is the setup above, and you get it in writing.
Is this the right fit
This works at any size. In a small business, one person is often doing four jobs, and the repetitive parts of those jobs are exactly what this removes. In a larger one, a single process change can ripple across several roles at once, so the same fix returns a bigger number. The first call is free and will tell you honestly which applies to you.
No. None of the systems in the portfolio cost anyone their job. They took work off people instead, 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.
Support after handover
If you take a support plan, its first month comes with the build, so anything broken gets fixed and anyone can ask me anything while the system beds in. There are three levels to choose from, priced to fit the plan, or you can take none at all. The accounts stay in your name, and the code is yours once the build is paid for, 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 so you have the option of me keeping an eye on it, not because you would be stuck without it.
How Jacob works
Not yet. Bots & Pieces is new. A small number of projects are taken on at a time, and anything that cannot be done properly gets a no. Everything in the portfolio is real work I built, five of them in a technology role and two for myself, just never for a paying client.
A clearer next step in half an hour.
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.
Tell me the problem first and I will come back with times that suit, Adelaide time. You can also just call.
What you leave with
A clearer problem definition, suitable options and an honest assessment of whether a build makes sense. Bring one example of work that is slow or repetitive; no presentation needed.
After you enquire
- I read your enquiry and reply with any questions and suitable times.
- We talk through the work, the constraints and what a useful result looks like.
- If there is a fit, I explain the next step and how scope and price will be agreed.
Or reach me directly.
Tell me what is slow
Pick the work, then fill in four boxes.