Low-voltage estimating is the practice of pricing the labor and materials for a low-voltage system install — structured cabling, access control, intrusion, fire alarm, audio/visual, surveillance, paging, and the network backbone they all ride on. It is the bid step in the work of a low-voltage integrator: turning a set of drawings, a scope of work, or a walked building into a number the contractor can stand behind for the length of the project.
What separates it from general construction estimating is the unit of measure. A low-voltage estimate is not built on square footage or cubic yards. It is built on counts — cable drops, terminations, devices, head-end equipment, racks, and the labor hours each one carries. A 40,000-square-foot tenant fit-out and a 4,000-square-foot one can carry nearly the same cable count if the device density is the same, and a small space packed with card readers, cameras, and access points can out-cost a large open warehouse. The estimator's job is to get the counts right, attach the right labor and material to each one, and not lose money on the parts of the system that don't show up on a floor plan.
What goes into a low-voltage estimate
A complete low-voltage estimate carries several layers, and the ones that get missed are usually the ones that aren't visible in the device count. The first layer is the cable and pathway: the count of drops, the cable type per drop (Cat6, Cat6A, fiber, shielded, plenum vs. riser-rated), the run length per drop, and the pathway — conduit, cable tray, J-hooks, or open air — that the cable lives in. Run length matters because labor scales with it and because exceeding the 100-meter channel limit on copper forces a design change the estimator has to catch at bid time, not at trim-out.
The second layer is termination and device labor. Every drop gets terminated on both ends, every device gets mounted and connected, and every termination carries a labor figure that varies by device type — a keystone jack is not a fire-alarm pull station, and a dome camera on a 12-foot ceiling is not the same labor as one on a 30-foot warehouse ceiling that needs a lift. The third layer is the head-end: the racks, switches, controllers, NVRs, access-control panels, fire-alarm control units, and power supplies that the field devices report back to. The fourth is the work that has no device — programming, commissioning, as-built documentation, AHJ inspection coordination, testing and certification, and the project management hours that the bid has to carry or eat.
The estimate also has to account for the things that turn a clean bid into a loss: waste factor on cable, slack loops, firestopping at every rated penetration, the labor premium for occupied or after-hours work, and the coordination overhead of working behind or alongside the electrical, mechanical, and ceiling trades. An estimate that prices the devices and forgets the firestopping and the after-hours premium is an estimate that wins the job and loses the margin.
Why low-voltage estimating is harder than it looks
The difficulty is structural, and it comes from the fact that a low-voltage estimate is a count problem layered on top of a labor-rate problem layered on top of a documentation problem. Get the count right and price the labor wrong, and the bid is off. Price both right and miss that the job is prevailing-wage, and the bid is off in the other direction. The estimator is reconciling a takeoff, a labor library, a material catalog, and a compliance regime at the same time, and most of the tooling for those four things lives in four different places.
The takeoff itself is the first failure point. Counting drops and devices off a PDF set by hand is slow and error-prone, and the drawings the integrator bids from are frequently incomplete — a riser diagram with no device locations, or a device plan with no pathway. The estimator fills the gap with experience and assumptions, and the assumptions are where the money leaks. The second failure point is the labor library. A device count is only as good as the hours attached to each line, and stale or generic labor figures — the same minutes for a jack termination whether the run is 20 feet or 280 feet — produce bids that are right on average and wrong on every individual job.
The third is the seam between estimating and everything downstream. The bid wins, and now the device counts have to become a bill of materials for procurement, a schedule for dispatch, a submittal package for the engineer of record, and a labor budget for job costing. When estimating lives in a spreadsheet, every one of those handoffs is a re-type, and every re-type is a chance to drop a device, fat-finger a count, or order the wrong cable. The estimate that was accurate at bid time decays a little at each seam until the job that priced at a healthy margin closes at a thin one and nobody can point to where it went.
Low-voltage estimating and prevailing wage
A large share of commercial low-voltage work lands on schools, hospitals, courthouses, transit, military installations, and public housing — which means a large share of low-voltage estimating has to carry a prevailing-wage assumption from the first line. On a Davis-Bacon or state public-works job, the technician's labor isn't billed at the shop rate; it's billed at the prevailing wage for the work classification, plus fringe, and certified to the contracting agency every week the work is in progress.
This changes the estimate at the root. The labor hours are the same, but the labor cost per hour is set by the wage determination, not the integrator's payroll, and the estimator who prices a prevailing-wage job at shop rates either loses the bid by padding it blind or loses the margin by under-pricing the compliance labor. The estimate has to know, per classification, what the prevailing rate is — and the bid that ignores this is the bid that turns into a bookkeeper's three-day weekend filing WH-347 forms for a job that was never priced to carry them. Low-voltage and security/fire integrators carry some of the heaviest prevailing-wage exposure of any commercial trade, which is why estimating and payroll on these jobs can't honestly live in separate tools.
Where the standard tools are the right call
Honest first: there are real reasons an integrator runs the estimating tool they run, and a glossary entry that pretends otherwise isn't worth reading. If a shop has spent years building a labor library and a product catalog inside an estimating package and the whole team knows it cold, that institutional knowledge is worth real money — switching costs are not a marketing footnote, they're real, and a mid-bid changeover slows the whole team down before it speeds anything up. A purpose-built takeoff tool with deep symbol libraries and assembly-based counting genuinely speeds the count, and a shop whose entire process is built around one of those tools should think hard before moving.
D-Tools, in particular, is a long-standing standard for AV and low-voltage estimating and proposal generation, and it is a capable product with a deep catalog and a large installed base. For an integrator whose workflow is settled on it, who has the catalogs maintained and the proposals tuned, D-Tools is doing its job. The case for changing isn't that the estimating tool is bad. The case is narrower and more specific: it's about what happens at the seams after the estimate is done, on the jobs where estimating, payroll, documents, and the field can't afford to live in separate systems.
How Forge approaches low-voltage estimating
Forge is one platform for commercial installation contractors — estimating, scheduling and dispatch, CRM, documents, payroll, communication, and field ops in one chest, where the modules share an architecture rather than an integration. The bet is that the value isn't in any single drawer being marginally better at its job; it's in the device count from the estimate carrying through to procurement, job costing, the submittal package in Plate, and the dispatch schedule without being re-typed at every seam. Federation, not integrations: because the estimate and the payroll drawer are built on shared architecture rather than bolted together, the intent is that a prevailing-wage job priced at the wage determination at bid time certifies from the same data at trim-out.
Where estimating meets the field, Forge runs Hyperion — the iPad and iPhone LiDAR scanning system that captures a space's geometry as ground-truth instead of inferring it from a drawing set or an aerial image. Forge publishes a measurement methodology of plus-or-minus 0.8% on commercial flat and low-slope geometry and plus-or-minus 2% on complex geometry; that figure is currently published as a methodology and sample plan on the proof page and graduates to an independently verified benchmark only after third-party verification, not before. The point for the low-voltage estimator is that the count and the dimensions come from the building as it stands, not the building as it was drawn.
Low-voltage is an active Forge vertical — AV and low-voltage ship today alongside security and fire, roofing, solar, HVAC, and electrical. Treasury, the payroll drawer, carries certified payroll, Davis-Bacon and prevailing-wage calculation, and WH-347 generation natively, which is the half of low-voltage estimating that the estimating tools were never built to close. The estimate is where the margin is set; the seams after the estimate are where it's kept or lost, and the design intent of the chest is to stop the margin leaking at the seams.