Every AV and security integration company eventually buys some type of software, from estimating platforms to project management tools to service ticketing systems. The market is full of them, and most owners have written the check for at least one.
The harder problem that determines whether that purchase pays for itself or becomes shelfware is adoption. It means getting salespeople, designers, project managers and technicians to actually run their day inside the software instead of defaulting back to email threads, side-conversations and spreadsheets the moment things get busy.
This is not primarily a software problem… it's a management problem. Integration firms that solve it treat software adoption as a leadership discipline — a set of habits, incentives, and expectations set from the top and reinforced at every level — rather than a one-time training event. This article looks at why that discipline matters more than most owners realize, what it costs when it's missing, and what a top-to-bottom adoption philosophy actually looks like in practice.
The Real Cost of ‘We'll Just Handle It by Email’
Every integration business has a version of this story: a proposal goes out with the wrong labor rate. A change order gets agreed to verbally in the field and never makes it onto an invoice. A project manager who's been carrying the details of three jobs in his head leaves for a competitor, and nobody can reconstruct what he knew. None of these are software failures. They're the predictable result of critical business information living in someone's inbox, someone's head, or a spreadsheet tab instead of in a shared system of record.
Miscommunication and disconnected workflows cost businesses an average of $12,506 in lost revenue per employee per year.
The data on what this actually costs is more precise than most owners assume. Grammarly Business's 2023 State of Business Communication Report found that miscommunication and disconnected workflows cost businesses an average of $12,506 in lost revenue per employee, per year. For a 10-person integration firm, that's $125,060 walking out the door annually not from a single catastrophic error, but from the accumulated friction of information that doesn't move cleanly between people and systems.
That number lines up with what's specific to this industry. The 2024 CE Pro/Commercial Integrator software deep dive research on integration businesses found that companies not using an end-to-end business management platform lose an average of $10,399 in gross profit per employee per year, compared to those running on a unified system.
That same study also found:
- 47% of integrators use four to five different, disconnected software solutions to run their business.
- 67% of integrators report little to no integration between those tools.
- Nearly 9 in 10 integrators (89%) have abandoned a piece of software at some point in their business, which is usually a sign that the tool, or the rollout of the tool, never earned the trust of the people using it.
Put simply: the fragmentation of using multiple spreadsheets and different software solutions is real, measurable and larger than most owners have on a line item anywhere in their P&L.
The $100,000 Spreadsheet Error That Changes Minds
Abstract statistics rarely change behavior on their own. What usually does is a single, expensive, entirely preventable mistake — the kind every integrator has a war story about.
Red Thread Spaces, a Boston-based Steelcase dealer with a large AV integration division, has one of the better-documented examples. Fifteen years ago, the company misbid an AV project by $100,000 because of a formula error in the spreadsheet it used to build proposals.
"When we first built the business, which was largely from the ground up, we were using spreadsheets to manage our product catalogues and put together our proposals for our customers. Obviously, using spreadsheets is wrought with calculation errors," said Brian Baril, Director of AV Business Operations at Red Thread Spaces, recounting the incident.
That error was the catalyst for an exhaustive software evaluation that ultimately moved the company onto an end-to-end business management platform (D-Tools) for its product catalog, proposals, and project operations — including change order tracking, which Baril says has since performed "flawlessly" even through complex construction projects with heavy change-order volume.
The lesson isn't that spreadsheets are inherently dangerous… they're not, for the right job. It's that spreadsheets and email have no guardrails. A single dropped decimal, an outdated labor rate copied into the wrong cell, or a verbal agreement that never gets logged doesn't trigger a warning; it just ships. A shared system built for the business can catch that error before it reaches a customer. A spreadsheet can't.
The Gap Between Adopters and Holdouts Is Widening
The businesses that have made the leap to a unified platform aren't just avoiding errors, they're pulling ahead financially. D-Tools' 2025 research on integrator performance found a striking split: one in five integrators saw a sales decline of 21% or more, typically firms still relying on disconnected tools, manual processes, siloed teams, and no real-time visibility into the business. One in three integrators, by contrast, grew sales by 51% or more, and their common traits were a unified platform, automated workflows, connected teams, and real-time data.
In 2025, one in five integrators saw a sales decline of 21% or more. By contrast, one in three integrators grew sales by 51% or more.
The profitability data tells a similar story. The same 2024 CE Pro/Commercial Integrator research found that integrators using an end-to-end software solution report an average profit increase of 13%, and that one in 10 integrators who fully adopt an end-to-end platform see a profit boost of 30% or more. One platform, in other words, is increasingly replacing the four or five disconnected tools most integration businesses have historically stitched together.
This is happening inside an industry that is, by most measures, growing fast: AVIXA projects the global Pro AV market to reach $402 billion by 2029, with 14% annual revenue growth expected for pro AV and integration businesses over the next five years, and the electronic security integration market is estimated at $182 billion globally with 7.8% annual growth. Growth alone won't decide which firms capture that opportunity. Operational discipline will.
It's Not Just a Balance-Sheet Problem — It's a People Problem
The financial case for adoption is strong enough on its own, but it's not the whole case. The status quo of fragmented tools and manual workarounds also has a direct, measurable cost on the people running the business and the teams beneath them.
Industry research from Emerald Research finds that 84% of integrators report chronic stress on the job, 52% have no exit strategy for their business, and 46% doubt they will ever be able to retire from it. Those numbers track closely with what happens inside a business built on tribal knowledge and manual handoffs: when critical information lives in one person's head instead of a shared system, that person can never fully step back, and the business can never be sold, handed off, or scaled without them.
84% of integrators report chronic stress on the job, 52% have no exit strategy for their business, and 46% doubt they will ever be able to retire.
This is where the adoption conversation connects directly to culture and retention. A team working from one shared playbook — common data, common process, common visibility into what's happening on every job — creates a fundamentally different day-to-day experience than a team where every handoff between sales, design, project management, and billing requires someone to manually chase down information.
The former reduces the friction, rework, and finger-pointing that drive good employees to quit. The latter is a slow-motion retention problem, because the employees most likely to leave are the ones your business depends on most — the estimator with the pricing knowledge, the project manager who knows which vendors are reliable, the salesperson who remembers every customer's history. Every one of those departures is more costly, and more disruptive, in a fragmented-tools environment than in a connected one.
Consistent software adoption isn't just an efficiency play, in other words. It's a hedge against turnover and a foundation for a business that can eventually run — and be sold — without depending on any single irreplaceable person.
Why Adoption Efforts Usually Fail
Most integration companies don't fail to adopt software because they picked the wrong platform. They fail because they treated the rollout as an IT project instead of a management commitment. A few patterns show up again and again:
-
Leadership doesn't use it themselves. If the owner or GM still asks for a status update by phone instead of pulling it from the system, everyone else gets the message that the system is optional.
-
The software is layered on top of existing habits instead of replacing them. Teams are told to "also" log things in the new platform, which just adds a second job on top of the spreadsheet they were already keeping.
-
Adoption is treated as a training problem. A single onboarding session doesn't change behavior that took years to form. Habits change through repetition, accountability, and visible consequences — not a one-time webinar.
-
There's no consequence for reverting to the old way. If a salesperson can still win deals and get paid while working out of a personal spreadsheet, there is no real pressure to change.
-
The system is harder to use than the workaround. If logging information into the platform takes longer than firing off an email, people will choose the email every time, regardless of the long-term cost.
Recognizing these failure modes is the easy part. Building a management philosophy that avoids them is the harder, more durable work — and it's where the real advantage lives.
Building an Adoption Philosophy from the Top Down
Getting an entire team — sales, design, project management, field technicians, and back office — to work inside one system consistently requires treating adoption as a leadership discipline, not a rollout event. In practice, that means:
- Make leadership the first and most visible user. Owners and managers should pull every status update, forecast, and report directly from the platform — and be seen doing it — rather than asking for a verbal recap. Behavior modeled at the top sets the real expectation for everyone below it.
- Retire the workaround, don't just discourage it. If a spreadsheet template or shared email inbox is still doing the job the software is meant to replace, shut it down. Parallel systems guarantee people default to whichever one is more familiar.
- Tie using the system to the money. Commissions, project profitability reports, and performance reviews should be calculated from data in the platform. When pay and performance visibility run through the system, using it stops being optional.
- Reduce the platform to its lowest point of friction. Audit the workflow from the perspective of the newest hire, not the power user. If entering a proposal or logging a service call takes more clicks than sending an email, fix the workflow before blaming the team.
- Assign clear ownership for data hygiene. Someone — not "everyone" — should be accountable for catalog accuracy, labor rate updates, and clean customer records. Shared responsibility without a named owner tends to mean no one's responsibility.
- Build in a "single source of truth" rule. Establish, in writing, what information must live in the system before it's considered official — a signed proposal, an approved change order, a scheduled service call — and hold every department to it, no exceptions for tenure or seniority.
- Treat every abandoned software attempt as diagnostic, not just a bad purchase. With 89% of integrators reporting they've walked away from a platform at some point, most failures trace back to rollout and reinforcement, not the tool itself. Before switching again, examine whether the failure was the software or the management commitment behind it.
- Revisit and reinforce quarterly. Adoption erodes quietly under deadline pressure. Build a recurring review — quarterly is reasonable — where leadership checks utilization, not just outcomes, and re-anchors the team to the standard.
The Bottom Line
The businesses pulling ahead in AV and security integration aren't necessarily using better software than everyone else — plenty of firms in the "falling behind" category own the same tools as firms in the "pulling ahead" category. What separates them is whether the organization actually runs on that system, top to bottom, every day, without exception. That's a management philosophy, not a purchase order. The firms that build it get measurably better financial outcomes, fewer catastrophic $100,000 errors, and — just as important — a team that isn't quietly burning out under the weight of information that only lives in their heads.
