Software for teams that build, fix, dig, and deliver.
Replace spreadsheet workflows, re-keyed field sheets and email approvals with software built around how your team works. Built by an engineer who knows mining and site work. You own the code.
Systems in use across the BMS Mining & Civil Group
Most industrial businesses aren't short on data. They're short on usable systems.
Spreadsheets holding things together
One overwritten cell and a safety or engineering number is wrong. Nobody notices until someone checks.
Slow reporting
Someone spends a day each month copying numbers into a report the board reads in ten minutes.
The same data typed twice
Field sheets get re-typed in the office. Each re-type costs time and adds a chance of error.
Know-how in people's heads
When an engineer leaves, their folders and their methods leave too.
One engineer, from first call to rollout.
Work directly with me, no handoffs or account managers.
I'm Joe, mechanical engineer turned software engineer. Ten years working in engineering and manufacturing, then ten years building digital products primarily for mining, civil, and manufacturing teams. I also co-founded and built geomechanics.io, calculation tools for geotechnical engineers.
I work with a small number of clients at a time, and I stay with each one until the new tool is part of the daily routine.
Systems for teams that build, fix, dig, and deliver.
I specialise in mining, engineering, civil, and manufacturing. The tools work with gloves on, offline, and are simple enough to use mid-shift. I set them up and show your team how to use them.
Dashboards & reporting
Live views across sites, shifts, and KPIs: operations, ESG, quality, and safety, fed from the systems you already use.
Board packs and site reports in minutes, not days.
AI systems
Search over your documents, or assistants and agents that do work in the background, grounded in your data with sources you can check.
Find the right clause or diagram without opening twenty folders.
Client portals
Branded spaces for clients and partners: reports, approvals, document packs, and status, with a clear audit trail.
Fewer email threads and version mix-ups.
Field data capture
Inspections, photos, signatures, and structured logs on phones and tablets. Offline on site, sync when coverage returns.
Office gets clean data without re-keying.
Data visualisation
Maps, sections, timelines, and charts for geotech, production, and asset data, built to handle large, messy datasets.
Spot trends across thousands of records without exporting to Excel.
Lightweight internal tools
Quoting, scheduling, asset registers, and QA checklists, replacing spreadsheet workflows tied to how your team works.
Quotes and sign-offs same day instead of chasing cells.
AI where it saves time.
AI is one tool I use when it fits the problem. You don't need an AI strategy. Usually it means search over your own reports with a source for every answer, or an assistant that drafts a report from your data. I set it up, then stay while your team learns it.
- 1
Pick one job worth doing
One clear job, such as answering questions from your files, drafting a report or flagging an exception.
- 2
Connect the data and systems
Files, databases, and tools wired up so the model can read what it needs. I do the setup.
- 3
Ship a small pilot
A working tool in weeks, with a handful of people trying it on real work.
- 4
Train, then widen
Walkthrough for the first users, fix what trips them up, then open it up or add the next use.
Start with one problem. Agree the first 30 days before you pay.
Tell me which workflow costs your team the most time. We agree a first milestone before you pay. Continue when the next piece is worth building.
You work with me directly. Pause or cancel anytime.
Discuss a workflowPause or cancel anytime. No minimum term.
75% refund in your first week if it's not a fit.
Frequently asked
- What happens if I cancel?
- Your app keeps running, and the code stays in your repos. Bug fixes and patches stop until you resubscribe.
- What if you're ill or on holiday?
- Your cycle pauses, so you don't pay for days I don't work. Every project ships with a handover document, so another developer can take over.
- Who owns the code?
- You own the code I write for you. I keep my existing tools and reusable parts, and you get a permanent licence to use them.
Ready for software that fits how you work?
If your team is ready for practical, well-built software without months of planning overhead, tell me about your project.
Pause anytime · You own your code · 75% back if week one isn't right