Questions, answered plainly.

No. Many builds start from paper forms, a whiteboard, or just a job someone’s sick of chasing. If there is a spreadsheet, we’ll bring its history across. See custom apps.

Maintenance and asset tracking is where most shops start, but pre-start checks, shift handovers, tooling life, spares, quality logs, job cards, dashboards and training records are all common. If your team does it every day, it can probably be an app. See three examples in the industry previews.

No. Send them exactly as they are. Inconsistent dates, blank cells and duplicate entries are part of the job, and anything we can’t resolve is flagged for you to confirm rather than guessed.

A spreadsheet conversion is typically three to six weeks, depending on how many assets and modules are involved. From-scratch apps vary more with size. Either way, you’ll get a firm timeline in your proposal before anything starts.

Whatever you use now — spreadsheets, forms, or just an explanation — plus a 45-minute to one-hour call on Zoom or Teams, and someone who can answer questions while we build.

No. The call and the quote are free, with no obligation either way.

Client systems run on Supabase, a secure cloud database platform, in its Sydney data centre — so your data stays in Australia unless your proposal says otherwise.

Each client’s data sits in its own separate project, never shared with anyone else’s.

Your team, and us while we’re building or supporting the system. We don’t share it, sell it, or use it for anything else. The details are in our privacy policy.

We raise it in the first conversation, not after delivery. Most networks only need a single domain allowed, and your IT team gets exactly what they need to approve it.

Yes. Everything is built to work on a phone or tablet beside the machine.

Because most shops this size don’t want to rent software forever. You pay for the build once and own the result. Ongoing support is there if you want it, not a condition of keeping the system.

Your data is always yours. Once the project is paid in full, you own the system built for you. Any general tools we reuse across projects come with a permanent licence for your business to keep using them. The detail is in our terms of engagement.

No — it’s quoted the same way, on scope, before any work starts.

Each change is quoted before any work starts, based on its size. No hourly meter running in the background.

Any time. You keep the system either way.

If we built it wrong, fixing it is on us. New features or changes to how it works are quoted before any work starts.

Yes. New apps, modules, reports, sites or asset types can be added later, and new apps can share data with the ones you already have. Each addition is quoted before work starts.

You keep the system and your data. We hand over everything we’ve built, give you an export of your data in a common format like CSV at no cost if you ask within 60 days, and help move any hosting accounts across to you.