Soil logs and site records
Capture borehole or test-pit observations, sample references and photos from a phone. Generate the agreed PDF format from the same record, with checks before issue.
ADELAIDE · CIVIL & CONSTRUCTION
Custom apps for the worksite and the office.
A spreadsheet can contain a useful method and still be awkward to use in the field. We help Adelaide contractors and engineers turn that method into a phone-friendly platform, with clear inputs, review steps and records the office can use.
Built around the way your team works.
Ben has used AI and custom development to turn spreadsheets into usable platforms in his own business. The starting point is the process you need to preserve: its formulas, observations, approvals and outputs. The app should make that process easier to run and maintain.
Inspections and field forms
Build forms around inspections, pre-starts, defects or daily records. Use required fields, consistent choices and job references to reduce missing information and later re-entry.
Engineering calculation interfaces
Put a checked design spreadsheet behind a clearer interface for your team. Preserve units, assumptions, limits and calculation versions, then compare results against agreed test cases.
Connections to the office
Link approved records to email, web systems or a CRM where supported. Agree which system owns each record, how duplicates are prevented and what happens when a connection fails.
ILLUSTRATIVE WORKFLOW
Example: site observations to a reviewed PDF log.
- 01
Select the job and record observations, sample IDs and photos on the phone.
- 02
Validate required fields and send the record through the agreed review step.
- 03
Generate the approved PDF layout and file it against the correct project.
Check whether it makes a difference.
Compare time spent recording, transcribing and preparing the final log. Also check missing fields, corrections and whether the field team can use it comfortably on its actual devices.
Agree the checks before the build.
Offline operation, synchronisation and native phone features are separate design decisions. Test them on the intended devices. Engineering calculations and interpretations still require review by the responsible engineer; an app does not validate the underlying method by itself.
The proposal sets out deliverables, account access, testing, handover and support. Read the security and privacy safeguards and service terms.
Practical questions.
Will it work without mobile reception?
Offline use is possible for suitable designs, but it must be included in the scope. Local storage, synchronisation, conflicting edits and device security need to be designed and tested.
Can we maintain the app ourselves?
That is part of the aim. The proposal sets out account ownership, source or configuration access, documentation, training and any ongoing support. The handover should match your team's skills.
Is a complete platform included in the starting build price?
No. Implementation starts from A$5,500 including GST for a defined first scope. A connected platform with migration, multiple roles or offline use needs its own quote and may be delivered in stages.