A customer who once needed one phone call now needs three. The company has added people, systems, and management layers, but getting an answer takes longer. Internally, the business looks more organized. To the customer, it has become harder to work with.
For owners and leadership teams, that friction is a competitive threat. Growth can erode the responsiveness, familiarity, and reliability that helped the company win work in the first place.
Larger competitors may have more capacity, broader coverage, and deeper financial resources. Regional and mid-sized companies can still offer something customers value: less effort and uncertainty in getting work done. Protecting that advantage requires measuring growth by what customers experience, not only by how the organization looks from inside.
Customer familiarity has practical value
Consider an illustrative commercial roofing contractor serving a property management company. Over several years, its team learns which buildings have recurring drainage issues, which tenants need advance notice, and which access points affect equipment placement. That knowledge makes estimating, scheduling, and completing repairs more straightforward.
The customer spends less time restating requirements, checking arrangements, and correcting preventable mistakes. The contractor adds value by reducing the time and effort the customer spends coordinating the work.
A competitor may offer a lower price or a larger crew. Switching still requires the customer to rebuild that working knowledge and test whether the new supplier can deliver reliably. Familiarity strengthens a competitive position only when it produces dependable results; longevity alone is not an advantage.
The same principle applies to a manufacturer that understands a customer’s inspection requirements or a marine services business that schedules repairs around vessel availability. The advantage is not a general promise of better service. It is specific knowledge applied consistently.
Growth can push work back onto the customer
As volume increases, companies need clearer responsibilities, shared information, and consistent processes. Those changes should make service easier. Trouble begins when internal arrangements require customers to coordinate the company for themselves.
A customer may repeat a problem to dispatch, explain it again to a technician, and then contact an account manager for approval. Each department completes its step, but no one owns the issue through resolution. The organization gains specialization; the customer inherits the handoffs.
Examine the cost of the handoff
Consider a regional HVAC company that introduces a ticketing system as it expands. Previously, a service manager who knew the customer’s sites coordinated the response directly. Now calls enter a central queue, scheduling sits elsewhere, and exceptions require another manager’s approval.
To protect this advantage, the system needs to carry relevant history forward, identify who can decide, and keep ownership visible. If it merely routes requests between departments, customers become the link between them, chasing updates, repeating instructions, and reconciling conflicting answers.
Internal reports can miss that burden. A call is answered quickly, a ticket is assigned on time, and each department closes its task, yet the customer’s problem remains unresolved. Efficient steps do not add up to an effective experience when the handoffs fail.
In The Effortless Experience, Matthew Dixon, Nick Toman, and Rick DeLisi argue that reducing customer effort is central to loyalty in service interactions. For a growing business, the operational question is simple: how much work must customers do to receive what the company has already committed to deliver?
Preserve the advantage through better operating practices
Customer familiarity is fragile when it lives only in the memory of a founder, account manager, or experienced technician. Absence, turnover, and expansion expose that weakness. The goal is not to preserve informal habits; it is to convert useful knowledge into an organizational capability and asset.
Capture the details that materially affect delivery: site access, agreed service windows, recurring problems, approval contacts, and customer commitments. Put them where teams plan and perform the work, and assign responsibility for keeping them current. Information protects the relationship only when people can find, trust, and use it.
Pair shared knowledge with clear authority. Teams should know which routine adjustments they can make and which exceptions require approval. Customers should also have a point of contact who remains accountable across internal handoffs, even when several departments contribute.
Richard Rumelt’s Good Strategy Bad Strategy offers a complementary principle: understand the source of an advantage and coordinate action around it. When a customer values a company’s responsiveness and understanding of their business, new systems and processes should help its team deliver those advantages consistently.
Owners and leadership teams can apply that test to every new approval layer, central service function, or software platform. Name the customer outcome the change should improve, define how it will reduce effort or uncertainty, and then verify that the result matches the intention.
Review customer requests from start to finish
Choose five recent requests from established customers, including at least one problem or change. Reconstruct each request from first contact to final resolution with the people who handled it. Where possible, ask the customer where the process demanded more effort than expected.
Use four questions to expose where growth may be weakening the experience:
Repeat. What information did the customer have to provide more than once, and why was it unavailable to the next person?
Chase. Where did the customer have to follow up for an answer, update, or decision that the company should have supplied?
Coordinate. Where did the customer have to connect departments, reconcile instructions, or explain an internal handoff?
Recover. When something went wrong, was someone clearly responsible for resolving the whole issue?
Select one recurring source of effort that creates meaningful delay, uncertainty, or disruption. Trace it to a specific cause before choosing a fix. Missing site details may call for a better service record; recurring approval delays may require clearer authority. Another form, meeting, or checkpoint may simply relocate the burden.
Assign responsibility for the change, test it on comparable requests for one month, and track the measure closest to the problem, such as repeated explanations, customer follow-ups, or time to full resolution. Monitor accuracy, delivery cost, and work quality alongside it so a faster response does not conceal a poorer result.
Ask the people doing the work whether the change is usable, and ask affected customers whether the process became easier. A closed ticket or completed internal step counts as progress only when it moves the customer’s issue toward resolution.
Growth should make a business more dependable by giving its people better information, support, and capacity. The competitive risk is allowing those additions to obscure accountability or force customers to manage the company’s complexity.
The advantage worth protecting is the customer’s confidence that the company understands the work and will see it through. The best operating changes preserve that confidence as the business grows.
As your company grows, identify where customers are having to coordinate between your teams, then agree on what you will change first.