Solutions
Estimating, BOQ and job tracking software for construction and trade services
For quantity surveyors, cost consultancies, PMOs, MEP suppliers and specialist contractors whose estimating, permit tracking and subcontractor follow-up still live in Excel and email. We build the one system that replaces the spreadsheet, scoped as a fixed pilot, live in weeks.
Active users on Crangle, the lift-planning platform we built for construction teams
Fixed pilot: one process, end to end, before anything else is committed
Products and platforms shipped across 12+ industries
The processes we are asked to fix in construction and trade services
Estimating and BOQs
Bills of quantities built in Excel, re-keyed from drawings and reused by copy-paste. We turn the estimator's method into a quoting system with rate libraries, versioned quotes and a client-ready output, without changing how they price.
Permit, spec and compliance tracking
Permits, specifications, EPDs and certifications tracked across email threads and folders. A single register with owners, expiry dates and reminders, visible to the people who get asked for them.
Subcontractor and progress tracking
Who is on which job, what has been invoiced against what was done, and what is late. A job board that subcontractors update from a phone and the office reads at a glance.
Client and PMO reporting
The weekly report that someone rebuilds every Friday from four systems. Dashboards that pull from the tools you already run and send themselves.
Construction software we have shipped
Systems for people who plan lifts, price jobs and chase subcontractors, built around how the work is actually done on site and in the office.
Crangle
A specialised lift-planning and crane-configuration platform used by construction teams to plan lifts safely and quickly. Cross-platform web, iOS and Android, with 100,000+ active Android users and 50,000+ downloads.
100K+ active users, 50K+ downloads
Web, iOS and Android from one codebase
Built for site conditions: fast, offline-tolerant, simple
Configuration logic that matches how riggers plan
Which part of the job is still in a spreadsheet?
What a build like this looks like in practice
Process per pilot
estimating, tracking or reporting, scoped and quoted after a two-hour audit
Weeks to live
running on real jobs before a second phase is discussed
New habits required
the update has to be faster than the spreadsheet or it will not stick
Construction and trade services: common questions
We already use an estimating or project tool. Why would we build anything?
Usually because the tool covers the standard part of the process and the firm's edge lives outside it: a pricing method in Excel, a compliance register in email, a subcontractor list on WhatsApp. We do not replace the tool. We build the piece around it that the firm actually runs on, and connect the two.
How do you scope a build for a QS firm or specialist contractor?
A Process Audit: a two-hour working session with the estimator, the office manager and whoever chases subcontractors, walking through the process as it happens today. We write up the current flow, where the time goes, what we would build first, and a fixed quote. The audit is a fixed fee, credited against the build.
Can the people on site use it?
That is the test every build has to pass. If updating the system takes longer than a phone call or a whiteboard, the site will go back to the phone call. We design the field side as a single action on a phone: scan, tap, photo, done. Crangle runs for 100,000+ users on exactly that principle.
How long does a build take?
A fixed pilot covering one process ships in two to four weeks. A multi-role platform with a client portal and mobile takes several months, and we only propose that once the pilot is running on real jobs.
We are in the UAE / UK / New Zealand. How does working with a Lahore team go?
Most of our operator clients are in the UAE, UK, NZ, Australia and the US. Calls are in your working hours, the first call is a working session rather than a pitch, and every engagement starts with a fixed, written scope so there is nothing to interpret across time zones.
What does it cost?
Every build is quoted as a fixed price after the audit, so you see the number before you commit. The price moves on how many systems the build touches, whether people need to act from it or only read it, and how clean the underlying data is.
Which process goes first?
Tell us which process is still manual. The first call is a working session, not a pitch.
