Why We Start From the Need, Not the Point Count

A point count is a guess wearing a number

The fastest way to win a job is to quote a low price against a long list of points: sockets, light fixtures, detectors, cameras, data drops. It looks precise. It rarely is.

A point count answers the wrong question. It tells you how many things will be installed. It does not tell you whether the building will actually work when those things are switched on together.

We start somewhere else. We start with the need.

What the project has to do

Before we price anything, we want to understand the operating reality. What runs in this space, and when? What are the loads, and how do they behave through the day? Where does heat build up, where do people move, what has to keep running when something else fails?

A coffee roastery is not an office floor. A workshop with three-phase machines is not a retail unit. The same point count means completely different things in each, and pricing them the same is how problems get installed into the walls.

So we ask first, then we count.

Scope before price

When the scope is clear, the price means something. You are paying for a system that was sized for your actual demand, routed so it can be maintained, and built so the next phase does not require tearing open the first one.

When the scope is vague, the price is just a number that will grow. Variation orders, rework, "that wasn't included" conversations. Everyone has lived through that project. The cheap quote became the expensive job.

Defining scope properly is not bureaucracy. It is the part of the work that protects the budget.

The project is one operating system

We do not see electrical, fire alarm, low-current, and control as separate trades that happen to share a building. We see one system: power that carries the load, safety that protects it, low-current that connects it, control that runs it, and maintenance that keeps it alive.

When you design from the need, these layers line up. The panel has room for the safety circuit. The cable routes leave space for the data runs. The smart control talks to the equipment instead of fighting it.

When you design from a point list, they collide. Everything fits on paper and nothing fits in the ceiling.

Build to stay maintainable

A system that works on handover day is the minimum, not the achievement. The real test is the building two years later, when someone has to find a fault, add a circuit, or swap a failed component.

That future is decided now, in how the panels are labeled, how the routes are planned, how much headroom the design leaves. We size for it on purpose, because we expect to still be answering the phone after handover.

Honest about the trade-off

Starting from the need takes longer up front. The first meeting is more questions than answers, and the proposal arrives after we understand the site, not before.

That is the trade. Slower at the start, steadier for years. We would rather lose a fast quote than win a job we will be apologizing for later.

Define the need. Size the system. Then talk about price. In that order, the number actually holds.