The Music Man of Construction

The Traveling Salesman’s Oldest Trick

There is an old musical about a traveling con man who rolls into a small town and convinces the locals that a new pool table in the billiard hall is about to corrupt every kid in town. Once the town is sufficiently worried, he offers the fix: buy uniforms and instruments, form a boys’ band, and the problem disappears. He never intended to stick around and actually deliver on any of it.

The trick is simple and old as sales itself: undisturbed people rarely buy anything, so if you want to sell something, first you manufacture the disturbance. That exact playbook shows up constantly in construction technology today, and it is worth learning to recognize it before it costs real money.

The Real Pain: Being Sold a Solution to a Problem You Don’t Actually Have

The real pain shows up in a familiar pitch. A software company opens not with a question about what is actually broken on your project, but with a declaration: stop using spreadsheets, get rid of the sticky notes on the wall, ditch the old way of doing things.

Notice what is missing from that pitch. Nobody asked what your actual production problem is. Nobody diagnosed anything specific to your team, your schedule, or your project. The problem was simply announced, the same way a pool table got announced as a moral crisis, and the fix just happens to be whatever that company is selling.

The Failure Pattern: The Manufactured Problem

The failure pattern is easy to spot once you know the shape of it. A pitch that starts by attacking a tool you already use effectively, rather than starting with a genuine question about what is actually costing you time or money, is a straw man dressed up as a diagnosis.

If a vendor cannot tell you specifically what real problem you have, only that your current tool is somehow the problem, that is worth treating as a warning sign rather than a selling point. A real solution starts with a real, specific problem, not an invented one.

A few signs tend to show up when a pitch is built around a manufactured problem rather than a genuine one, and they are worth checking honestly:

• The pitch opens by telling you to abandon a tool you already use effectively, before ever asking what is actually going wrong on your project.
• The proposed fix locks your team into one narrow, proprietary system instead of adding real, specific capability you were missing.
• Nobody involved in the sales conversation can name a concrete, specific problem your team currently has, only a vague sense that your current approach is outdated.

This Isn’t About Being Anti-Technology, It’s About Being Anti-Con

None of this is an argument against technology. Every superintendent and project manager genuinely needs to be comfortable with computers, scheduling software, and the full range of digital tools available today. Refusing to learn technology is its own kind of career-limiting mistake.

The issue is specifically with vendors who manufacture a problem instead of diagnosing a real one. That is a different thing entirely from a legitimate tool that genuinely solves something your team is actually struggling with.

Why Excel Earned Its Place in the Toolkit

Here is a direct, honest opinion worth stating plainly: Excel may be the single most versatile piece of software ever built for construction. It handles charts, graphs, trend lines, logistics maps, Takt zone maps, schedules, org charts, and even coordinate geometry calculations, all inside one flexible, endlessly adaptable tool.

That said, honesty cuts both ways. Excel is not flawless. A single bad formula or a mistyped number in an estimate once contributed to a seven hundred thousand dollar loss on a real project. The lesson from that mistake was not to abandon spreadsheets entirely, it was to recognize the one place a more specialized tool genuinely earns its keep: estimating, where built-in checks, automatic unit rate transfers, and a connected database meaningfully reduce the risk of a costly manual error. That is a real, specific problem with a real, specific solution, which is exactly the standard every other pitch should be held to.

Why It Matters: Real Problems Deserve Real Solutions

This matters because falling for a manufactured problem costs more than just a subscription fee. It often means locking a team into an expensive, narrow platform that cannot flex the way a general tool can, sometimes for tens of thousands of dollars a year, without ever actually solving anything specific.

It also has a quieter cost. Superintendents and project managers who are told their foundational tools are obsolete may never fully develop real fluency with something as broadly useful as Excel, and that is a genuine loss of builder experience that follows them for the rest of their careers.

Teach the Framework: Ask What Problem This Actually Solves

The test for any new tool or pitch is straightforward. Does this genuinely solve a specific, real problem my team already has, or does the pitch start by telling me my current tool is the problem before ever asking what I actually struggle with? A legitimate solution can always name the exact issue it fixes. A manufactured one can only ever gesture vaguely at being “the old way.”

It is also worth asking whether a proposed tool adds real capability or simply repackages something a flexible, general tool like Excel already does perfectly well. Estimating passed that test because of a specific, nameable risk, formula errors and manual data entry mistakes that a connected database genuinely reduces. Most scheduling and project management pitches never clear that same bar.

A few practical questions help separate a real solution from a manufactured one before signing anything:

• What specific problem does this solve that my current tool genuinely cannot handle?
• Can this vendor name the exact issue my team has, or are they only describing my current tool as generically outdated?
• Am I being asked to give up flexibility and lock into one narrow system, without gaining any real new capability in return?

Turning This into Daily Practice

None of this requires becoming suspicious of every new tool that comes along. It just means holding every pitch to the same simple standard: a real problem, clearly named, with a real solution that actually addresses it.

Keep building genuine fluency in flexible tools like Excel across the team, since that skill pays off regardless of whatever software trend comes and goes next. When a new tool does solve something specific and real, like the case for estimating software, adopt it deliberately and for that clear reason, not because a pitch successfully manufactured a sense of urgency.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to ask sharper questions before adopting a new system, and without teams that keep developing real foundational skills instead of assuming the next platform will replace the need for them.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, using tools chosen because they solve a real problem, not because a pitch invented one.

The Challenge

So here is the challenge worth carrying into your next software pitch: before adopting anything new, ask what specific, real problem it solves, and be honest about whether the answer is actually clear. As Jason put it plainly, “If somebody’s selling you a straw man or a pool table problem, that means they don’t actually know what your real problem is.” On we go.

FAQ

Why does Jason consider Excel one of the best tools available for construction?

Because of how genuinely flexible it is, capable of building schedules, zone maps, logistics plans, org charts, trend charts, and even coordinate geometry calculations, all inside one adaptable tool. Its versatility across so many construction tasks is difficult for any single specialized platform to match.

Is there any situation where Jason recommends moving away from Excel?

Yes, specifically for estimating. A connected database with built-in checks and automatic unit rate transfers reduces the risk of costly manual errors, which is a real, specific problem worth solving with specialized software.

How can you tell if a software pitch is built around a manufactured problem?

Watch for pitches that open by telling you to abandon a tool you already use effectively, without ever asking what your team is actually struggling with. A legitimate solution can always name a specific, real problem it solves, rather than just describing your current approach as generically outdated.

Does being skeptical of manufactured problems mean avoiding new technology altogether?

No. Every superintendent and project manager genuinely needs strong technology skills to do the job well. The caution is specifically about vendors who invent a problem to sell a fix, not about avoiding legitimate tools that solve real, specific issues.

What is the real cost of falling for a manufactured problem in software sales?

Beyond the direct cost of an expensive, narrow platform that may not solve anything real, it can also mean team members never develop genuine fluency with flexible foundational tools like Excel. That loss of real builder experience often outlasts whatever software trend prompted it.