One specialist.
Built on three sides of the same job.

Background — 12+ years, three continents, three sides of the table

Shoaib's career started in Pakistan as a site engineer — building infrastructure on the ground. From there to Saudi Arabia, also as a site engineer, working on civil and infrastructure projects in Gulf-region conditions. Back to Pakistan as a client-side project engineer on a complete land development project — government-funded affordable housing for state employees, where the brief was a full subdivision from greenfield to handover. Water mains, sewer reticulation, telecom and gas utilities, roads, the whole scope. Years of seeing every discipline come together on the same project, from the client’s side of the table.

Then migration to Australia, and a deliberate move into estimating:

• Plumbing estimator — multi-million-dollar projects across high-rise residential, complex commercial, and high-end luxury apartments. Large-scale plumbing where the technical complexity matched the budget
• Contractor-side civil estimator for a Sydney water infrastructure firm — subdivisions, complex water mains, projects for major regional water authorities
• Rail and civil infrastructure estimator for a Sydney specialist contractor — high-stakes infrastructure under tender pressure, dense drawings, tight deadlines
• Founder and lead estimator at WSE Sydney

Each role taught a different way of seeing the same job. It's why our estimates think about how the work actually plays on site, not just what the drawings say.

Why WSE Sydney exists

Two reasons, to be honest.

I’d always wanted to build something of my own. After 12+ years inside other companies, the timing felt right.

But the real reason was technical. I’d come to genuinely enjoy water and sewer infrastructure work — especially the complex jobs. Solving a complicated estimating puzzle, and producing something I deeply understood, made the work satisfying in a way most jobs aren’t. This is genuinely tough work. Site conditions stack. Authority specifications differ region to region. The fittings list alone is enough to derail a junior estimator. But that’s exactly what drew me in. I wanted to take on that challenge and build something around it.

What makes our work different

The honest answer is: I don't estimate jobs from behind a screen.

Most estimators read drawings, apply rates, produce a number. That works for simple jobs. It fails on complex ones — and water and sewer infrastructure is rarely simple.

When I price a job, I want to be able to stand on the site as the supervisor and watch the work being done exactly the way I estimated it. That mental discipline forces you to think about how things actually happen — not how the drawings imply they should happen. It's why I make a point of doing site visits where the project allows. Standing on the ground, looking at the actual road, the actual existing services, the actual ground conditions, gives you a depth of understanding that no PDF can replicate.

That's the edge: estimating jobs the way the supervisor will execute them, not the way the drawings flatten them.

The kind of work that makes this interesting

Most estimators avoid the hard jobs. I'm drawn to them.

What makes a project interesting isn't a single challenge — it's the way challenges stack on top of each other. Let me walk you through what I mean.

Imagine a job where the pipe has to go in deep — say six metres. That's already a serious cost driver: trench stability, shoring or benching decisions, plant selection, productivity rates all change at depth. Now add existing services to the picture. The Dial Before You Dig drawings show telecom, gas, electricity, water, sewer, stormwater all converging along the alignment. Most of those — telecom, gas, electricity, water — sit within the top metre, so services search has to be done carefully through the shallow zone before any machine digs. Below that, sewer and stormwater are the live concerns. Suddenly the job isn't just deep — it's deep and slow, because every metre of excavation has to work around what's been mapped above it.

Take another scenario. We're working in brownfield — already a constraint compared to greenfield. But on top of that, the trench has to go deep. And not just deep — there's an existing structure metres from the trench wall. Now we're managing risk to a third party while we excavate. The job that was awkward is now awkward and high-stakes.

Or take a live road. Working along live traffic is already complex — you've got traffic control, restricted hours, water-filled barriers, productivity drops significantly. Now add overhead wires above the trench. Machinery selection narrows. Working under the wires changes safe work methods. Now add a private fence on the other side — working width is constrained. Now the trench has to cross five different existing services on its way through.

Any one of these factors is manageable on its own. Stack three or four together and the cost profile changes completely. Stack all of them and it's a different job from the one the drawings flatten it into.

Then there are the technical wrinkles inside the codes themselves. Take slope, for example. If the trench slope is more than 5%, the WSA Code kicks in. Between 5% and 14% slope, we have to provide trench stops at specified intervals. Between 15% and 29%, those become concrete bulkheads — reinforced retaining walls cast into the trench. Above that, the rules change again. Get the slope band wrong by a few percent and the cost line is wrong, the construction method is wrong, the programme is wrong. The estimate is no longer defensible. That's one example among many. We work with this kind of code-level detail every day. That’s the work.

Professional philosophy

The goal: when a client opens our estimate, they should be able to say "this is the best estimate I've ever seen. Nothing comes close to it."

That's the standard I work toward. You can never claim you've achieved 100% efficiency — there's always something to refine, something to improve, something a previous estimate missed that the next one shouldn't. Every estimate is a chance to do better than the last one. That's the standard, and the work.

The thinking behind this is simple: an estimate isn't a deliverable, it's a decision-making document. The contractor uses it to bid. The client uses it to set budget. The site team uses it to understand what they've committed to. If the estimate is rough, every downstream decision is rough. If the estimate is genuinely thought through — line by line, site condition by site condition, fitting by fitting — every downstream decision is grounded in something real.

How we work with clients

Two questions come up most often before clients engage us. Confidentiality and capacity.

On confidentiality: every client receives an estimate built specifically for them — their supplier rates, their plant rates, their preferred markups. Even if we happen to price similar scope for two firms, the estimates come out genuinely different because the underlying inputs are different. We never reveal who else is quoting. We never share intelligence between clients. We never publish project details. Discretion is the foundation of the relationship.

On capacity: we ask for the deadline upfront. If we can meet it with the quality of work the project deserves, we say yes. If not, we say so honestly and as early as possible. We don't take on work we can't deliver. The reputation of the next ten estimates depends on the integrity of this one.

The setup

WSE Sydney operates from a head office in Bankstown, Sydney. Our work covers New South Wales, Victoria, Queensland, and increasingly other Australian states as opportunities come — Sydney Water, Hunter Water, Coliban Water, GWM Water, and regional Queensland councils. Drawings arrive electronically. Site context comes via geotech reports, video walk-throughs, photos, and authority correspondence. Distance hasn't been a constraint on quality.

ABN: 40 646 914 141.