TMT Internal Case Study
When "We Need AI" Isn't Actually the Problem
A contractor asks for AI. The real constraint turns out to be something else entirely. Here's the system TMT built to make sure the request never becomes the diagnosis.
Richard Fritzke — Founder, The Modern Trades Mentor. Trades and operations leader with more than 26 years of HVAC, facilities, and mechanical-systems experience.
Published August 16, 2026
A business owner calls and says, "I need AI." It's tempting to take that at face value — quote an AI project, build it, move on. That's also how a consultant ends up selling the wrong thing to a business that never had an AI problem in the first place.
What someone asks for is not necessarily what the business actually needs. TMT's own intake system is built to keep those two things separate on purpose, so the original request never quietly disappears — and the eventual recommendation never gets shaped by what the customer said, instead of by what discovery actually found.
System: Service Interest vs. Qualified Commercial Path
Status: Active internal implementation
Outcome data: Not yet measured
Purpose: Keep customer intent recorded separately from business diagnosis
What this does not prove: this is a system-design case study, not measured client ROI. No result is claimed until one has actually been measured.
Inside the system
Every inbound request gets recorded as a Service Interest — what the person actually said they wanted, in their own words. A contractor who says "I need AI" gets that recorded exactly as said. Nothing is reinterpreted yet.
Discovery then determines the real constraint — missed follow-up, a broken handoff, a CRM gap, pricing, capacity. That becomes a separate field: the Qualified Commercial Path — the engagement that actually fits what was found, which is not always the one originally requested. The original Service Interest is never overwritten by the diagnosis; both stay on the record.
What goes wrong without this
Skip this separation and a business ends up selling whatever the customer named first. A contractor who says "I need AI" gets an AI project — even if the real problem was that estimates sit unanswered for three weeks, which no AI feature fixes on its own. The fastest way to lose a client's trust is to build the thing they asked for and watch the business problem stay exactly where it was.
The business lesson
The customer's request is input. It is not the diagnosis. A customer who says "I need AI" may actually need consistent estimate follow-up, a CRM that catches missed calls, or clearer scheduling — none of which require AI to fix first. Letting the request dictate the solution skips the diagnosis that makes the recommendation correct. Business first. Tools second.
What this means for your business
Before you buy the tool someone recommended, or the one a competitor mentioned, ask what you'd actually be fixing:
- What does the customer say they want, in their own words?
- What did discovery actually find underneath that request?
- Is the real constraint follow-up, CRM, dispatch, pricing, or something else?
- Does the request map to an existing qualified path, or a new one?
- What happens to the original request if the diagnosis changes it?
If you're not sure whether the tool you're considering solves the actual constraint in your business, that's exactly what a Strategy Call is for.
More from Inside the System
See the other real TMT systems and the business lessons behind them.