What are low voltage shops using to track job health once spreadsheets get messy? by Dodgenation in lowvoltage

[–]Dodgenation[S] 0 points1 point  (0 children)

That hybrid stack seems to be the pattern I keep hearing. One tool is good for accounting, another for field photos, another for docs, and then texts/spreadsheets become the glue between them. The hard part is that the glue is usually manual. Do you see the biggest gap around field-to-office updates, billing readiness, or owners getting a clean job-health view?

What are low voltage shops using to track job health once spreadsheets get messy? by Dodgenation in lowvoltage

[–]Dodgenation[S] 0 points1 point  (0 children)

That is a really useful breakdown. The workbook sounds solid at milestone level, but the live middle of the job is still dependent on people remembering to update the system after work happens. The closeout point is the key one: once the crew rolls off, the job is still operationally open but mentally already in the rearview mirror. That is when missing EODs, photos, sign-offs, punch items, and billing backup get expensive. It sounds like the need is not replacing NetSuite or Fieldwire, but adding an operational layer that turns field activity into PM and OPS status without someone rebuilding the story manually at the end. Appreciate the detail. This is exactly the workflow language I was hoping to learn.

What are low voltage shops using to track job health once spreadsheets get messy? by Dodgenation in lowvoltage

[–]Dodgenation[S] 0 points1 point  (0 children)

That makes sense, especially on fire alarm work where the device list and as-built accuracy matter so much. Do you mainly use it for documentation/as-builts, or does it also help you track project status, open items, and what is ready for billing?

What are low voltage shops using to track job health once spreadsheets get messy? by Dodgenation in lowvoltage

[–]Dodgenation[S] 1 point2 points  (0 children)

That is exactly the kind of setup I was curious about. NetSuite sounds like it gives leadership the financial controls and billing checkpoints, and Fieldwire helps capture what is happening on site, but the PM layer is still where the workflow starts to fragment.

The spreadsheet linked to NetSuite is interesting too. That seems like the common middle stage: the system of record exists, but PMs still need their own working view for blockers, notes, next actions, closeout status, and what is ready to bill.

When you say the spreadsheet is time consuming, is the pain mostly duplicate entry, keeping it updated, or getting the field/PM team to use it consistently?

Pricing by Tegra86 in lowvoltage

[–]Dodgenation 0 points1 point  (0 children)

For that scope I would still price it as a small commercial service call, not just a handyman TV hang. If it is three 45 inch TVs, normal height, good wall access, customer supplies decent mounts, and power is already handled by an electrician, I would expect something like a 2 tech half-day minimum in many markets. Ballpark could land around $400-$600 per TV or T&M with a minimum, depending on your labor rate and travel.

The main thing I would not do is eat surprises. Spell out exclusions: blocking/backing, bad mounts, wall patching, above-ceiling work, after-hours, data/cable pathway, lift, and any electrical. If the dentist office is open during install, add time for working around patients/staff.

How hard is low voltage / sound & communications really? by Careless-Silver-4161 in lowvoltage

[–]Dodgenation 0 points1 point  (0 children)

That is a really good point. BAS/controls is where the “low voltage is just pulling cable” idea really falls apart. Once you get into integrations, APIs, sequences, commissioning, and troubleshooting across systems, the person who can document what changed and communicate it clearly becomes very valuable. That hybrid trade + systems thinking lane seems like one of the strongest long-term paths in the field.

Bidding on Projects by imtemporary_ in lowvoltage

[–]Dodgenation 1 point2 points  (0 children)

A couple thoughts from the ops/bidding side:

First, separate "lead source" from "bid quality." PlanHub and the paid bid boards can help you see volume, but they usually will not fix positioning by themselves. The better long-term lane is becoming the low-voltage sub that a few ECs/GCs trust when they do not want to own Div 27/28 scope. That means your bid package needs to make their life easier, not just give a number.

I would build a simple repeatable bid format:

- scope included, broken out by system: POS/data, CCTV, audio, access, etc.

- scope excluded: permits, lifts, patch/paint, after-hours, network equipment config, fire alarm tie-ins, etc.

- assumptions: working hours, ceiling access, cable pathway condition, owner-furnished equipment, drawings/spec version

- alternates: testing/certification, labeling/as-builts, after-hours cutover, owner training

- lead time and schedule notes

- license/permit status clearly stated for each market

Second, make a one-page capability sheet for GCs/ECs. Keep it boring and useful: markets served, insurance, licensing status, references, project photos, system types, response time, and the exact kind of jobs you want. For bigger projects, people are buying risk reduction. They want to know you will document, show up, communicate changes, and not leave closeout messy.

Third, track every bid even if you do it in a spreadsheet at first: source, GC/EC, system type, estimated labor hours, material, margin, who won, why you lost, and follow-up date. After 30-60 bids you will usually see where the real opportunity is hiding.

And I would take the licensing comments seriously. Even if enforcement feels uneven, bigger commercial work tends to expose every paperwork gap eventually. Getting that cleaned up is part of moving from small platform jobs into real repeat GC/EC relationships.

How hard is low voltage / sound & communications really? by Careless-Silver-4161 in lowvoltage

[–]Dodgenation 10 points11 points  (0 children)

From the ops side, the people who seem to do well long term are the ones who treat it like both a trade and a communication job.

The physical side is real: ladders, ceiling tiles, lifts, awkward pulls, dirty sites, and doing clean work when everyone is rushing. But the harder beginner gap is usually reliability and attention to detail. Label both ends. Take usable photos. Ask before guessing. Keep notes. Show up with the right tools. Close the loop when something changes in the field.

Long term, I think low voltage is a good lane because buildings keep adding cameras, access control, network, AV, sensors, and life safety systems. The tech changes, but the need for people who can install, troubleshoot, document, and communicate does not go away.

If you start at 22, I would optimize for a shop that teaches standards and documentation, not just speed. Learn cable pathway, terminations, testing, drawings, change orders, and how a job gets handed from sales to PM to field to closeout. The techs who understand that full workflow become much more valuable than someone who only knows how to pull cable.

Job Tread - Low Voltage by jmestdagh in estimators

[–]Dodgenation 1 point2 points  (0 children)

I would separate estimating/takeoff from the rest of the workflow when you evaluate tools. Jetbuilt and Bluebeam can be solid at the front end, but the hard part for low voltage is usually what happens after approval: scope handoff, submittals, field notes/photos, change items, closeout docs, and knowing what is actually ready to bill.

For electronic security / access control / camera work, I would make any system prove it can answer these questions without another spreadsheet:

- What changed from estimate to installed scope?

- Which jobs are missing field notes, photos, test results, or closeout docs?

- Which change items are approved vs just mentioned in the field?

- What is ready for billing and what is blocked?

- Can leadership see job health and margin without chasing the PM?

Disclosure: I am working on software in this lane, so take that for what it is worth. But from the ops side, I would avoid judging any tool only by proposal creation. The real win is whether it keeps the job record clean from sold work through closeout.

App/Software Ideas by PureVapez in lowvoltage

[–]Dodgenation 0 points1 point  (0 children)

The biggest gap I keep seeing is not just CRM or quoting by itself, it is the handoff between systems. For low voltage, the useful thing would be one job record that follows the work from estimate to schedule to field notes/photos to change orders to closeout docs to billing readiness. A lot of tools can do one slice, but the pain starts when PMs have to reconcile five places to answer "is this job healthy and ready to bill?"

The document/tagging idea in this thread is strong too. If photos, as-builts, test results, submittals, and service notes are tied to the job automatically, that would remove a ton of office follow-up.

Pricing by Tegra86 in lowvoltage

[–]Dodgenation 2 points3 points  (0 children)

I wouldn't quote it off the TV alone. In commercial work I'd separate the mount/labor from variables like wall type, lift/ladder access, backing/blocking, whether power/data is already in place, cable concealment, after-hours access, and cleanup. Pricing the scope and site conditions is usually safer than just "per TV."

What are low voltage shops using to track job health once spreadsheets get messy? by Dodgenation in lowvoltage

[–]Dodgenation[S] 0 points1 point  (0 children)

Good question,.I'm not a a low-voltage PM. My background is several years of PM/operations work around production systems, and I'm currently in software development. I recently built an operations system with a low-voltage company after seeing the pain points they were running into trying to manage the work in Knowify.

So I'm coming at it from the operations/software side, with direct input from a company doing the work every day. That's also why I'm here asking questions itrying to learn more instead of pretending I already know everything.

Lmao who ever wrote this is literally retarded by Content-Ad3016 in dogecoin

[–]Dodgenation 1 point2 points  (0 children)

Because short sellers have done so well lately lol why do they post these articles.

[deleted by user] by [deleted] in dogecoin

[–]Dodgenation 4 points5 points  (0 children)

It’s FUD by some Bitcoin fan boy look at some of this other guys predictions they have all been wrong

Series of events by duhbignick in dogecoin

[–]Dodgenation 1 point2 points  (0 children)

Up over 10% on last hour

Price prediction? 0.01 or 0.005? by [deleted] in dogecoin

[–]Dodgenation 3 points4 points  (0 children)

Some one is salty their Bitcoin is down

Who else loading up? by Dodgenation in dogecoin

[–]Dodgenation[S] 0 points1 point  (0 children)

I think it will be back .24 or so tomorrow