What customer expectation caused you the most problems?
One expectation I wish I had defined earlier was arrival times. When I first started, it was easy to tell a customer: “I’ll be there around 10.” Or: “We should be there between 12 and 1.” At the beginning, that felt like good customer service. The schedule was smaller. The routes were lighter. I had more control over the day. As the business grew, specific arrival times became harder to keep. All it took was: one chatty customer talking for 10 minutes a locked gate a dog outside extra waste in a yard traffic road construction an accident a customer note that needed attention Suddenly the whole route was pushed back. And once you miss the arrival time you gave the customer, even if the work itself is done well, you’ve created frustration because the expectation was set wrong from the beginning. That forced us to change how we communicate scheduling. Now we set the expectation that we scoop from sunrise to sunset. Customers know their service will happen on their scheduled day, and they’ll receive an “on the way” message 30–60 minutes before arrival. That one change reduced a lot of unnecessary pressure. It also made the route easier to manage because we weren’t trying to force the day into exact arrival windows that didn’t hold up once real life happened. I think a lot of service businesses run into this. You create an expectation early because it feels manageable, then growth exposes how hard it is to keep that promise consistently. For us, the lesson was pretty simple: If the business cannot deliver it consistently at scale, be careful promising it casually in the beginning. What expectation did you set early on that later became hard to manage as the business grew?
