The Button Presser Is Gone. Who's Still Pressing Yours?
- Sahand H
- Mar 27
- 3 min read

For most of the early 20th century, elevators required a dedicated operator. They stood inside the lift, controlled the speed, aligned the floor, opened the doors, and announced each level. It was a real job. A necessary job. Buildings employed dozens of them.
Then the automatic elevator was invented.
Not because operators were bad at their jobs. Not because building owners were cruel. But because once the system was designed properly — with the right sensors, controls, and logic built in — a human standing there pressing buttons was no longer adding value. The machine could do it more consistently, more reliably, and without a wage.
The elevator operator didn't lose their job to a smarter person. They lost it to a smarter system.
That transition is coming to construction. And the businesses that design their systems now will be the ones still standing when it does.
Most Construction Businesses Are Still Running Manual Elevators
Think about how much of your current operation relies on someone standing in the lift, pressing the buttons.
Chasing subcontractors for compliance documents. Manually consolidating project costs into a weekly report. Updating a spreadsheet so leadership can see where the business stands. Following up outstanding invoices. Reminding a project manager that a budget needs reviewing. Recompiling tender data that already existed somewhere else in the business.
These aren't skilled functions. They're coordination functions. They exist not because they require human judgment — but because no one has built a system that handles them automatically.
The result is that your best people — your project managers, your estimators, your commercial leads — are spending meaningful hours every week doing the equivalent of pressing floor buttons. Hours that should be spent on decisions, relationships, and delivery.
That's where your margin is going.
The Framework: Standardize → Automate → Eliminate
The automatic elevator wasn't invented overnight. Before automation was possible, engineers had to first understand exactly how the system worked — every variable, every condition, every input and output. They had to standardise the mechanism before they could automate it.
The same logic applies to your construction business.
Standardize means designing your operational workflows so information moves consistently through the business — from estimating, through project delivery, to financial reporting and leadership oversight. One source of truth. Clear ownership. No ambiguity about where data lives or how it flows.
Automate means using that consistent structure to replace manual coordination with triggered, rule-based action. When your system is standardised, automation becomes genuinely powerful. Alerts fire when subcontractor insurance expires. Dashboards update in real time without anyone compiling a report. The system follows up. The system reminds. The system flags. Without anyone pressing buttons.
Eliminate is where the margin moves. Once the coordination is automated, you can see clearly which manual effort, duplication, and low-value activity was consuming time across the business — and you can start removing it from your cost structure permanently.
That's not cutting people. That's redesigning which work people do.
AI Is Only as Good as the System Behind It
Here's the part of the AI conversation that nobody selling you software will explain clearly.
AI tools — which we embed directly into the operational systems we build — are extraordinary. They can analyse data, identify patterns, answer complex questions, and surface insight in seconds. But they are completely dependent on the quality and structure of the information they're working from.
An elevator operator can't automate away if the elevator has no sensors, no consistent logic, and no reliable mechanism underneath. You can't replace the human until the system is designed properly.
The same is true of AI in construction. Feed it fragmented spreadsheets, disconnected emails, and inconsistent data — and it fails. Not because the technology isn't capable. Because there's nothing structured for it to read.
Businesses that first build a properly integrated operational environment — and then layer AI on top of it — gain the ability to ask:
Which projects are currently tracking outside budget based on cost and progress?
Which tenders in the pipeline represent the highest expected revenue over the next 90 days?
Are there any overdue subcontractor invoices across the portfolio?
Are there unusual productivity patterns on any active sites?
And get accurate, instant answers.
That is what AI looks like when the system underneath it has been properly designed. The AI isn't the product. The structured operational environment is the product. The AI is what it unlocks.



Comments