Most businesses that reach a certain size don't have a lead problem. They have a workflow problem. And when the workflow breaks down, no amount of new business fixes it.
This is a story about a firm that had both figured out, except for one thing.
Their operations were running on a permit system that technically worked. Approvals were going through. Compliance boxes were getting ticked. But the people using it every day were frustrated, mistakes were slipping through, and nobody had the visibility they needed to manage it properly.
One permit, submission to approval, was taking close to 30 minutes. Across dozens of permits a day, across multiple active sites, that adds up fast.
We came in to fix it. Here's what that looked like.
The Firm
A Singapore civil engineering company. Earthworks, cable and pipe laying, over 2,000 workers across multiple active project sites.
They already had an electronic Permit to Work (ePTW) system in place. The problem wasn't that they didn't have a system, it was that the system wasn't built around how their people actually worked.
What Was Going Wrong
Permits were being raised. Approvals were going through. But nothing was smooth.
Fields that could have been auto-filled weren't. Notifications weren't reaching the right people at the right time. Project managers had no clear view of what subcontractors were doing on site. Admins had no proper dashboard to manage users and projects across the portfolio.
And then there were the mistakes, location conflicts that should have been caught before approval, slipping through because the manual checks weren't consistent.
On a construction site, small problems compound. A 30-minute permit process that should take 3 minutes isn't just a time issue. It's a safety issue, a coordination issue, and an operational drag that hits every project.
How We Came In
The first few weeks were conversations, not code.
We sat down with the people who actually used the system, site operators, project managers, management, admins. Not to write a spec sheet. To understand what the work actually required versus what had just been done a certain way because nobody had stopped to question it.
That takes time. But it saves significantly more time later.
What came out of those sessions became the foundation for everything that followed.
What We Built
The rebuilt app covers the full ePTW process from creation through to approval. A few things worth calling out:
Role-based access that reflects how the site actually works. Every level has a distinct view, applicant, supervisor, trade supervisor, subcontractor safety, project manager. Each person sees what's relevant to them and can only action what's within their role. No confusion over approvals. No accidental sign-offs. And when the business grows or site requirements change, new configurations go in with minimal setup and no downtime.
Automated fields and notifications. The information that can be pre-filled, is. The right person gets notified at the right step, not after someone chases them.
Location conflict detection. The system flags when permits overlap on site in ways that could cause problems. This used to rely on someone catching it manually. Now it's automatic.
Admin dashboard with full portfolio visibility. The people running the operation can see what's happening across users, projects, and subcontractors, in one place, in real time.
Scalable project onboarding. The firm is currently running five projects on the system. When a new site starts, they're onboarded immediately. Pay-as-you-go infrastructure. No large setup fees, no overcommitting to capacity they don't need yet.
Six Months Later
Permit process: down from around 30 minutes to 3.
The supervisors on the ground are using it without complaint. If you've worked with site-level teams before, you know they'll tell you straight if something isn't right. The absence of pushback means something.
We launched soft on one site, gathered feedback fast, and pushed updates from there. Features came from what the team asked for. Minor improvements go out regularly. No extra charge for reasonable requests.
The firm is now expanding the system to cover more of their operations. That work is ongoing.
What This Was Really About
Getting the result required listening properly before touching anything.
A lot of vendors come in, scope the job, build what was asked, and move on. That works fine for simple projects. But when the software is running your safety workflows, site access, and permit approvals, you need someone who understands the business, not just the brief.
The permit process was a symptom. The underlying issue was a system that had been built around assumptions rather than reality. Fixing it meant going back to the source.
That's how we work. And that's why the relationship is still going.
Got a process that's slower or messier than it should be? We're happy to take a look. No pitch, just an honest conversation about what's there and what's possible.
