Question 1: What are the first signs that a growing company has outgrown its sales process and needs outside help?
Erin Balzer, founder and principal consultant at BalzESystems, has seen the pattern play out many times. The first warning sign is when success depends on specific people rather than a repeatable process. "If your CRM requires tribal knowledge, you've already outgrown your process," she explains. When she hears phrases like "Ask Jessica" or "Only Jessica knows how to do that," she knows the system isn't supporting the business—the people are.
Another tell is when leadership spends more time asking for updates than making decisions. "Sales meetings become status meetings because nobody trusts the data," Balzer notes. She emphasizes that growth doesn't create inefficiency; it exposes it. What worked with five employees usually starts showing cracks at twenty. That's when companies realize they don't have a sales problem—they have an operational one.
Is Your Sales Process Built to Scale?
Our resident expert, BalzESystems, will help you identify friction points in your sales operations. Complete this short questionnaire to receive a personalized assessment of your scaling readiness.
Question 2: When implementing a new CRM, what mistakes do you see companies make most often?
The biggest mistake, according to Balzer, is treating the CRM as the strategy instead of the tool. "Buying a Ferrari doesn't make someone a race car driver, and buying Salesforce, HubSpot, or Dynamics doesn't magically create an efficient sales organization," she says. Companies get excited about automation, dashboards, and integrations before they've answered basic questions: How do we actually sell? Who owns each step? What does 'qualified' even mean?
Then they spend months—and sometimes millions—building technology around a broken process. Balzer's philosophy is simple: "Garbage in, garbage out. If you automate a broken process, all you get is broken results, just faster. Don't automate confusion. Fix it first."
Question 3: How do you measure whether a sales operations improvement is actually working?
The obvious answer is metrics—shorter sales cycles, cleaner forecasts, higher CRM adoption, and better conversion rates. But Balzer points to a less obvious indicator: silence. "The frantic 911 messages stop. The 'Can someone help me find...' emails disappear," she says. Sales reps spend less time fighting the system and more time selling. "Good sales operations should feel almost invisible because the process simply works."
When leadership trusts the numbers, onboarding becomes easier, and people stop creating spreadsheets to compensate for the CRM—that's when you know you've made a real impact.
Question 4: What's the relationship between sales process design and the technology stack—which should come first?
Balzer is unequivocal: "Always process. Every. Single. Time." Technology should support the business, not force the business to support the technology. She has watched organizations spend six or seven figures implementing CRMs only to discover halfway through the project that no one agreed on how opportunities should move through the pipeline. "The software wasn't broken. The business process was."
As she puts it, technology amplifies whatever already exists. If your process is great, technology scales it. If your process is inconsistent, technology just helps you make mistakes faster. This principle is a cornerstone of effective sales process design.
Question 5: For a company with a limited budget, what's the one thing they should fix before anything else?
"Document your process," Balzer advises. Not because documentation is exciting—it isn't—but because every business has a 'Jessica': the person who knows everything, the person everyone depends on, the person who eventually takes a vacation, retires, or leaves. "When knowledge only exists in people's heads, your business isn't scalable; it's vulnerable."
The best investment isn't always another piece of software. It's creating a process that's understandable, repeatable, and doesn't depend on institutional memory to keep the lights on. That's how organizations stop surviving and start scaling.