The $1.2 Million Problem Hiding in Plain Sight

customer cards and gears to show system connections

David closed another deal. A big one: $240K.

He walked back to his desk, updated the spreadsheet, and moved on to the next lead. No celebration. No team acknowledgment. Just another day in the sales department.

On the surface, everything looked fine. David was one of the top salespeople at the precast concrete company. He had four active projects totaling $962K in the pipeline. Deals were closing. Revenue was coming in.

But underneath? The system was quietly hemorrhaging money and opportunity.

Customers were getting a grab-bag experience, roll the dice, and you might get the VIP treatment or a chaotic circus act. The team was guesstimating labor costs like they were fortune-tellers reading tea leaves, bleeding profits without realizing it. Prices had been so sky-high they scared off customers faster than a surprise credit-card charge. And David, their rock-star salesperson who actually got how things worked, was stuck on repeat, selling the same old way instead of unleashing his full potential to transform the whole operation.

Nobody realized how much these “little issues” were costing until we sat down for a Systems Jam Session and actually mapped out the current state of their sales process.

What we discovered saved them $1.2 million over the next 12 months.

Here’s what’s crucial: these problems didn’t appear overnight. They accumulated slowly, like dust on a shelf. Each small inefficiency seemed manageable on its own, so nobody addressed them systematically.

That’s why the most successful businesses I work with don’t wait for crisis. They schedule Systems Jam Sessions twice a year, treating their operational systems like a car that needs regular maintenance before it breaks down on the highway.

Why Systems Drift (And Why It’s Costing You More Than You Think)

Let me share something most business leaders don’t realize: your systems are deteriorating right now, even if they’re working.

Here’s how it happens:

Your team has turned workarounds into an art form, duct-taping broken systems like it’s an Olympic sport. New hires show up, learn the old hacks, and proudly invent fresh ones of their own. Meanwhile, technology keeps evolving like a caffeinated teenager, but your processes are still rocking a flip phone. When seasoned team members leave, they take half the playbook and the secret sauce recipe with them. And while the market’s shifting like sand under your feet, your pricing is standing still, stubborn as a statue in a windstorm.

Six months later, you’re running a completely different operation than you think you are.

David’s sales team was a perfect example. They’d been using the same onboarding process for three years. It had worked well initially. But gradual drift had introduced inconsistencies:

  • Different salespeople were promising different timelines
  • Customer handoffs from sales to operations were happening differently each time
  • Pricing calculations were based on outdated cost estimates
  • Nobody was tracking actual labor hours against estimates, so profitability was a guess

Each issue alone? Annoying but survivable.

All of them together? $1.2 million in lost efficiency, missed opportunities, and customer churn.

The brutal truth: if you’re not reviewing your systems at least twice a year, you’re operating on outdated information and wondering why results feel harder to achieve.

The Six-Month Sweet Spot: Why Timing Matters

I’ve experimented with different review cycles with clients over the past five years. Here’s what I’ve learned:

Annual reviews are too infrequent. By the time you identify problems, they’ve been costing you money for months. Plus, you’re trying to remember what happened in February when you’re reviewing in December. Details get fuzzy.

Monthly reviews are too frequent for strategic systems work. You don’t have enough data to measure meaningful change. Teams need time to implement improvements and see results.

Quarterly can work, but it’s rushed. Just as you’re settling into new systems, you’re reviewing them again. Implementation fatigue sets in.

Six-month cycles hit the sweet spot. Here’s why:

  1. Enough time to implement and measure results. You can test a hypothesis, gather data, and see if it actually works.
  2. Short enough to catch drift before it’s expensive. Problems are still manageable and haven’t compounded.
  3. Aligned with natural business rhythms. Most businesses have natural half-year cycles (busy/slow seasons, fiscal halves, planning periods).
  4. Keeps teams engaged without overwhelming them. People can focus on execution between reviews rather than constantly changing direction.
  5. Often fits in around slower periods. Many businesses come in cycles. A good time to review systems is in mid June and mid December due to seasonal slow downs.

For David’s team, we scheduled Systems Jam Sessions in January and July. This timing allowed us to review performance after their busy fall season and mid-year during their planning phase.

What Actually Happens in a Systems Jam Session

Let me walk you through the exact process we used with David’s sales team. You can replicate this with any department or system in your business.

Phase 1: Document Current State (The Reality Check)

We didn’t start by brainstorming solutions. We started by documenting what was actually happening, not what the process manual said should happen.

I shadowed David through three complete sales cycles. I interviewed the other salespeople. I talked to customers about their experience. I reviewed the handoff to the operations team.

What we discovered:

  • The sales process David followed was completely different from what new salespeople were taught
  • Customer satisfaction scores varied by 40% depending on which salesperson they worked with
  • There was no system for celebrating wins, leading to a “just get to the next deal” culture
  • Labor hour tracking was based on estimates from 2019, making profitability calculations nearly meaningless
  • Pricing strategy had shifted, but wasn’t consistently applied across the team

Phase 2: Identify What’s Working (The Hidden Diamonds)

This is the step most business owners skip, and it’s a massive mistake.

David had developed an incredibly effective relationship-building approach that resulted in deals closing within six months, fast for their industry. But this approach lived entirely in his head. Nobody else on the team knew how he did it.

We documented his process in detail:

  • How he structured first conversations
  • His follow-up cadence
  • How he handled objections about price
  • His method for building trust before talking numbers

Phase 3: Map Improvement Opportunities (The Priority Matrix)

Now we had a clear picture: what’s working, what isn’t, and what’s costing the most.

We created a simple priority matrix based on two factors:

  1. Impact: How much time/money will this save or generate?
  2. Effort: How difficult is this to implement?

High-impact, low-effort improvements went first. For David’s team:

Quick Win #1: Document David’s sales process

  • Impact: High (could be replicated across the team)
  • Effort: Low (just needed structured documentation)
  • Timeline: 2 weeks

Quick Win #2: Implement deal celebration system

  • Impact: Medium (improved morale and team culture)
  • Effort: Low (simple recognition at team meetings)
  • Timeline: 1 week

Strategic Project #1: Improve cost tracking

  • Impact: Very High (directly affects profitability insights)
  • Effort: Medium (requires tool implementation and training)
  • Timeline: 8 weeks

Strategic Project #2: Develop David into hybrid PM role

  • Impact: High (better utilizes his operational knowledge)
  • Effort: Medium (gradual responsibility transition)
  • Timeline: 6 months

Phase 4: Create 90-Day Implementation Roadmap (The Action Plan)

We didn’t try to fix everything at once. We built a systematic 90-day roadmap focused on the highest-priority improvements.

Month 1:

  • Document David’s sales process (weeks 1-2)
  • Implement deal celebration system (week 1)
  • Research time-tracking tools (weeks 3-4)

Month 2:

  • Train sales team on documented process (weeks 1-2)
  • Select and purchase time-tracking tool (week 1)
  • Begin tracking actual labor hours vs estimates (week 3)

Month 3:

  • David begins attending weekly project management meetings (observer role)
  • Analyze first month of real labor data
  • Adjust pricing models based on actual cost insights

Month 4-6:

  • Repeat system 1-3.

Phase 5: Measure & Iterate (The Scientist Mindset)

This is where most improvement efforts fail. Companies implement changes but never measure if they actually worked.

We established clear metrics before implementing anything:

  • Customer satisfaction scores (measured quarterly)
  • Customer retention rates
  • Time from first conversation to closed deal
  • Profitability margins by project type
  • Sales team morale (simple quarterly survey)

Six months later, we reconvened for the next Systems Jam Session to review results:

  • Customer satisfaction increased by 35% after standardizing the sales process
  • Customer retention improved by 18% due to consistent experience
  • Profitability insights improved dramatically with real labor tracking
  • Team morale climbed with the celebration culture

Most importantly, we identified new friction points that had emerged and started the cycle again.

The Compound Effect of Bi-Annual Systems Reviews

Here’s what happens when you commit to Systems Jam Sessions twice a year:

Year 1: You catch obvious inefficiencies and fix them. You save time and money.

Year 2: Your team starts suggesting improvements between sessions because they understand the process. Systems thinking becomes part of your culture.

Year 3: New problems get caught and fixed faster because everyone’s trained to spot friction. Your business becomes increasingly efficient while competitors slowly decay.

Year 5: You’ve built a learning organization that continuously improves. Your systems are documented, your team is empowered, and you’re not just running your business, you’re systematically optimizing it.

David’s sales team is now 18 months into this rhythm. The transformation isn’t just in the numbers, it’s in how they approach problems. Instead of accepting friction as “just how things are,” they proactively identify and fix issues.

The Bottom Line

David’s team didn’t save $1.2 million through one brilliant insight. They saved it by systematically reviewing their sales system, identifying accumulated inefficiencies, and implementing prioritized improvements.

Your business is crawling with hidden opportunities tucked inside dusty systems that haven’t seen the light of day since the last password reset. The question isn’t if friction exists; it’s how much it’s already costing you while you sip your coffee thinking everything’s fine. Every week you wait is another slow leak draining six months of productivity and profit right under your nose.

The most expensive system in your business is the one you haven’t reviewed in six months.

Ready to uncover what’s creating unnecessary friction in your business which is costing you time and money? Take my 5-minute Customer Experience Quiz to identify friction points in your most critical systems. Then let’s schedule a Systems Jam Session to document your current state, map improvements, and create a 90-day roadmap that turns hidden problems into measurable results.

Your systematic transformation doesn’t require perfection. It requires rhythm. Let’s build yours together.

Scroll to Top