Software for construction and engineering firms
Contractors do not lose money on the build. They lose it in the gap between the site and the office — the day-old photo, the variation nobody priced, the plant sitting idle on a finished job. We close that gap with software your teams will actually use on site.
- Site + office
- iOS · Android · web
- Odoo & accounting integrations
- 8–16 weeks to first release
The short answer
We build custom software for contractors, engineering consultancies and developers: mobile site apps that work offline, snagging and QA workflows, plant and materials tracking, procurement and cost control on Odoo, and dashboards that give the office a same-day view of every project. One team covers design, mobile, web, backend and the ERP integration, delivered in fixed-price phases — and you own the code.
What actually costs you money
Five patterns show up on nearly every project we are asked to fix. None of them are engineering problems; all of them are information problems.
Site reports that arrive too late
Progress is written on paper, photographed, and sent that evening — or Monday. By the time the office sees a problem, a day of labour has been spent on it.
Photos scattered across chat
Thousands of site photos live in group chats with no project, no location, and no date that survives an export. When a dispute starts, nobody can find the one image that settles it.
Variations priced from memory
Extra work gets done first and priced later, from a foreman's recollection. Anything not captured on the day is a straight write-off against the margin.
Plant nobody can locate
Equipment stays on a finished site because no one flagged it. You pay hire or idle depreciation on machines a live job is waiting for.
Handover packs assembled by hand
At completion, someone spends two weeks rebuilding the QA record from files, chats and inspection sheets that were never one dataset.
What we build
Each of these can ship on its own and connect to what you already run. Most clients start with one and add the next when it pays for itself.
Site diary & daily progress app
Offline-first iOS and Android app for foremen: labour and plant on site, weather, progress against the programme, geotagged photos, and instructions signed on the phone. It syncs when signal returns — not when someone gets back to the office.
Mobile app developmentSnagging, QA & inspections
Defects raised against a drawing or a location, assigned to a subcontractor with a due date, closed with photo evidence, and exported as a handover pack the client can sign.
Mobile app developmentPlant, materials & deliveries
One register of what you own and hire, where it is, who has it, and what it is costing per day — with delivery notes captured on site instead of pinned to a cabin wall.
Web platform developmentProcurement & cost control on Odoo
Purchase orders, subcontractor valuations, retention and variations in one ERP, with cost-to-complete per project rather than per company. We implement, customise and integrate Odoo rather than bending your process to fit it.
Odoo ERP implementationClient & consultant portals
A read-only view of programme, progress photos, RFIs and approvals for the client, the consultant or the funder — so the weekly report writes itself.
Web platform developmentDashboards and reporting
Programme, cost, headcount and safety on one screen, fed by the systems above instead of a Monday-morning spreadsheet merge.
Analytics & dashboards
Together they replace the evening WhatsApp round-up with a record the office can act on the same day — and the client can be shown without a week of assembly.
What it connects to
Construction software fails when it becomes a second place to type things. It has to write into the systems you already keep.
How a construction build runs
Phased, fixed-price, and shaped so the first release lands on one live site before it goes company-wide.
Phase 01
Discovery on site
1–2 weeks
We spend time on a live project with the people who will use the app, map the current paper trail, and fix the scope and the price of phase one.
Phase 02
Design & prototype
2–3 weeks
Screens designed for gloves, glare and one hand, tested with a foreman before a line of production code is written.
Phase 03
Build
6–10 weeks
One Flutter codebase for iOS and Android, the web back office, and the integrations — demoed every two weeks.
Phase 04
Pilot on one project
2–4 weeks
A single site runs it end to end while we fix what reality exposes. Adoption is decided here, not at launch.
Phase 05
Rollout & support
Ongoing
Company-wide rollout, training for site teams, and a support plan with a named engineer.
At a glance
Frequently asked questions
How much does construction software cost to build?
A first phase — one mobile app, the back office behind it and one integration — typically runs $25,000–60,000. A full suite across site reporting, snagging, plant and Odoo procurement lands between $80,000 and $200,000, delivered in phases so each one is in use before the next begins.
Why not just use Procore or Autodesk Build?
If an off-the-shelf platform fits your process, use it — it is cheaper. Custom pays off when your process is the differentiator, when per-user licensing across hundreds of site staff and subcontractors becomes the largest line in the budget, or when you need it to work the way your ERP and your contracts already do. We will tell you honestly which case you are in.
Will it work with no signal on site?
Yes. Site apps are offline-first: everything is written to the device and synced when a connection returns, with conflict handling so two people editing the same record does not lose data. This is a requirement, not an extra.
Do you integrate with Odoo?
Yes — Odoo is our main ERP practice. We implement projects, purchase, inventory and accounting for contractors, build custom modules for valuations, retention and variations, and connect the site apps to them through a documented API.
Will site teams actually use it?
Only if it is faster than what they do now. That is why we design for gloves and glare, test with a foreman before production code, and pilot on one project first. If the pilot does not stick, we change the product — not the training.
Who owns the software?
You do. Code, repositories, infrastructure accounts and documentation are yours from day one, and there is no licence you have to keep paying us for to keep it running.
Start a project
Tell us what you're building. We reply within 24 hours, scope it on a 30-minute call, and send a fixed quote — usually within two business days.
- 01Reply within 24 hours
- 0230-minute scoping call
- 03Fixed quote in ~2 business days