For Australian mining and construction
Internal apps that keep the job moving.
Most of the value is not in a chatbot. It is in the ordinary systems that track progress, close out defects and chase the follow-ups, so work stops stalling between steps.
Custom built for how your site already runs, then developed further as the work changes.
Calls booked to suit Australian hours.
If you got here from the Handy video: yes, we build assistants like Handy too, ones that answer off your own run sheets and manuals. They work best on top of the kind of systems below.
Everyone is selling you an assistant
It is the easiest thing to demo. You ask it a question, it gives you an answer, and the room nods. We build them too, and a good one is genuinely useful.
It is rarely the thing that changes your Monday. What changes your Monday is duller: knowing which jobs are stuck, who is holding them and what happens next, without a supervisor spending half a shift ringing around to find out.
That is the work we specialise in. Internal apps built around one operation, kept running and extended over time.
The unglamorous list
None of this is exciting to look at. It is what takes the admin load off a site.
Progress tracking that matches the real job
One place that shows what is done, what is open and what is waiting on someone else. Built around your stages and your language, not a template you have to bend to fit.
Defects, NCRs and close-out
Raised on a phone in the field, moved through the trades automatically, closed out with the evidence attached. The audit trail builds itself as the work happens.
Follow-ups that happen without chasing
The system contacts the next person when it is their turn. Your supervisors stop spending their afternoon ringing around to find out where something got to.
Reporting that writes itself
Daily and weekly reporting generated from what was already captured, so nobody rebuilds it from scratch in a spreadsheet on Sunday night.
Handovers and approvals
Packs assembled from the record rather than compiled by hand, and approvals that move without sitting in somebody's inbox.
Assistants, where they earn their place
An assistant trained on your gear, procedures and history is genuinely useful for answering questions on site. It works best sitting on top of systems that already hold good data.
A worked example
A defects tracker, built for one operation
Defects do not cost money because they are hard to fix. They cost money because they stall between steps. Responsibility goes unclear, a contractor gets called to site before the work is ready for them, an inspection slips, and the status only becomes obvious once the time is already lost.
So the app does one job. It moves a defect from the moment somebody spots it to final sign off, and it makes stalling impossible to ignore.
Only the essential fields
Raised in seconds with a photo, on a phone, with gloves on. Nothing is asked for that somebody else could fill in later.
It moves itself
The system contacts the next person when it is their turn. Your site staff are not the ones doing the chasing.
Nothing hides
Every defect is visibly moving or visibly stuck. If one is not moving, it is immediately obvious why.
What it is, and what it is not
What it is
- A custom tool specific to one operation
- A movement and accountability layer
- Something a chaotic site gets calmer with
What it is not
- Document control
- Finance or claims
- Another enterprise platform to administer
- A generic one size fits all
Why it gets used
Software usually fails on site because it asks for too much. Adoption happens because the thing makes someone's day easier, not because it was mandated in a meeting they were not in.
Fast enough to use standing up
Gloves on, one hand, in the weather. If it takes longer than the old way, it will not get used and no policy will fix that.
Photo first
Capture the evidence, type as little as possible. A photo says more than a paragraph and takes a fraction of the time.
No training day required
It behaves like the apps people already use on their own phones, so the rollout is not a project in itself.
Plain language
Fixes, not tickets or issues. The words on screen should be the words used on site.
The build is where it starts
A one off delivery gets handed over and slowly stops matching the job. These systems are meant to be lived in, so they are built in stages and kept developing after they land.
Pilot
One site, one problem
- A single site and selected trades
- One workflow, scoped tight
- Rapid iteration while people use it
Review
Adjusted to what actually happened
- Changed against real field feedback
- Workflows refined, thresholds set
- Widened once it is earning its keep
Ongoing
It keeps developing
- Rolled out across projects
- Repeat patterns surfaced from the data
- New capability added as the work changes
As AI advances, so will you.
The AI underneath these systems gets better every few months. Because I build on it every day, the systems keep improving, and so does what your team can do with them. You are not buying a snapshot, you are buying a direction.
You deal with me, not an agency
I'm Pete Harris. Australian, now based in Ireland, and I still do most of my work with Australian operations. No account managers, no offshore team, no layers between you and the person building it.
I've spent 20+ years around mining and construction, from on the tools to training package production and now building the software, on sites where the paperwork was the bottleneck. That is why this work is worth having from me: I can read an operation, not just write code for one.
I also build and run my own software company, AutoListing.io, a full production platform with customers, billing and uptime to keep. So the systems I'd build for you are the same kind I build and run for myself.
Working with Australian operations
The work is done remotely, which is already how most Australian sites run their support functions. Calls get booked to land inside your business hours rather than mine.
- Perth
- Pilbara
- Karratha
- Port Hedland
- Kalgoorlie
- Darwin
- Brisbane
- Mackay
- Bowen Basin
- Gladstone
- Hunter Valley
- Newcastle
FIFO rosters, multiple sites and head office all pulling on the same information is the normal starting point, not a complication.
Your data stays yours
Modern, enterprise-grade security practices: secure authentication, encrypted data storage, and strict access controls.
Your systems run in isolated environments, your IP remains yours, and AI components do not train on or share your data.
Tell me where the job keeps stalling
One workflow or the whole operation, fifteen minutes on the phone will tell us both whether it's worth doing. If it isn't, I'll say so.
Or email peter@streamlinedai.tech