Should you stop serving neighborhoods that don’t produce route density?
I had to make this decision in my own business. Early on, I said yes to customers 35–45 minutes outside our core area because I wanted the revenue, reviews, and growth. Over time, those accounts became expensive in ways that didn’t show up on the invoice. More windshield time, more miles, fewer stops per hour, and harder routes for the team. We eventually started looking at which cities were producing our best customers and tightened our advertising around those areas. I also had to let go of an original client who had been with us for more than 4 years because she was simply too far outside where the business had grown. That wasn’t an easy conversation. But a $100 monthly customer can look very different financially when they require a 30-minute detour every visit. Revenue alone doesn’t tell you whether an area is worth serving. At what point do you stop advertising to an area or let existing outlier customers go?How Do You Roll Back a Major Change?
Have you guys ever made a major organizational change then needed to go back? This last year I tried to help buy back some of my time and created a Project/ Operations manager position so I could focus on sales and marketing. It's been a bumpy road to say the least. I first tried to hire two guys from outside the organization, I really thought I did my due diligence but it didn't work out with either of those guys. One guy I learned after a week (lol) the other took me a month and a half. On our third guy, I promoted from within and it seemed like it was working but here we are almost two full quarters in and we have less capacity because I haven't been successful in finding a replacement for him in the field, and we are making less money on jobs because ... well it's a combination of things but he might not be a fit for the position. I'm thinking I need a more decentralized approach since essentially we are at the same revenue number as last year when we didn't have his big overhead position. So the question is - how do you roll that back? Is it possible to make a change like that without alienating the person I'm demoting? Would it be easier to demote if I'm citing financial and structural changes for the company? What's ya'll take on that.
Fix the Plumbing Before Adding AI
Greetings Community 👋🏿 A concept I’ve thought about a lot: automating a broken workflow doesn’t save time, it just makes the mess move faster. A lot of teams jump straight to automation and the newest AI tools while the systems underneath are already disconnected: scattered user records, inconsistent permissions, duplicate data, and no clear source of truth. Identity is one of the best places to start. A well-managed IdP gives you a central place to manage users, access, and the SaaS applications your business depends on. It makes implementing SSO, provisioning, and deprovisioning across applications cleaner while establishing clear ownership of identity and access. Now you have a cleaner foundation to connect systems and build automations that actually make sense. Otherwise, you’re just automating the mess.Should owners still work in the field once they have employees?
I think there’s a balance. An owner who never touches the field can lose sight of what the team is actually dealing with. Long drive times. Bad notes. Locked gates. Difficult yards. Awkward customer requests. Routes that look fine on the calendar but feel rough in real life. Getting back in the field occasionally keeps you connected to the work and helps you spot problems you won’t see from behind a screen. But there’s a danger too. If the business only survives because the owner jumps in every time there’s a gap, the owner may still be the safety net holding everything together. I’ve had seasons where covering routes was necessary. Employees were out, someone was leaving, or the schedule had to get done. That’s part of ownership. But if it becomes the normal plan, burnout creeps in fast. The field can teach you what needs to be fixed. It shouldn’t become the place you hide from fixing it. Do you still work in the field, or have you fully removed yourself from production?First timer here!
Greetings community👋🏿 . I work professionally in IT infrastructure and engineering, mostly around identity and access management, endpoint, automation, and improving how different enterprise systems work together. In my free time im usually building or researching something. I’m interested in Saas tools, ai automation, open data, business ops, and finding better ways for systems to talk. I like taking real-world problems, digging into how the existing workflows actually work, and experimenting with ideas or small projects to see if there’s a better approach. I here in the Jobber Community because I’m interested in learning how real people use Jobber and other field services tooling.. what works well, where workflows bottleneck, and new builds/integrations. Looking forward to learning from you all and contributing where I can!!Strategies for Explaining Your Contract to Your Client
Contracts are a tough subject. First of all, that word in of itself elicits a negative chemical reaction in the brain so don't call it the contract to your customers. It's called an agreement. But just because you have something in the agreement, doesn't mean that you are completely off the hook and they customer reads and understands it. The reason I'm even writing this is every once in a while, a customer approves a time and materials job then our technician shows up and the conditions the customer presented make it impossible to perform the service. In our agreement, we have a "failed job" clause where they get charged $150. Our technician planned their day around the job, we did our best to assess it ahead of time but sometimes the customer doesn't know or hides details. This is clearly stated in our contract. I've tried to "enforce" this a few times but it always leaves a negative taste in their mouth. This also applies to leaving pets out while we are working, change orders and all sorts of things we have written out in a policies and procedures contract. I don't think it's enough to just put it in the contract. Try these things: If the job is big enough, go over all the most important items with them in person. Have a landing page telling them what happens next and who to contact Make a fun video going over some of the items Check This Out Main thing is don't assume they read it because they probably didn't. If you do it in person, use a Plaud unit and send them a summary of the convo after. Don't be that person that tries to just say "well it was in the contract". What is everyone's experience with describing contracts to customers?How early is too early to start servicing a customer?
This came up for me because summer routes can get brutal. When temperatures are pushing 95 to 100 degrees, I don’t want my team out in the hottest part of the day if it can be avoided. In our line of work, the job is outside. It’s physical. There’s no shade in a lot of backyards. The heat wears people down fast. So my general opinion is this: If the sun is up, visibility is good, and the technician can clearly see the yard, then it’s reasonable to start service. For pet waste removal, that means we can see the ground, see the waste, safely walk the property, check gates, read yard conditions, and do the job to our standard. I don’t think the clock alone should decide whether it’s “too early.” The bigger question is whether the customer has been properly prepared for how your service operates. If a customer thinks you’re coming between 10 AM and noon, and you show up at 6:30 AM, that’s going to feel wrong to them. If your onboarding explains that service may begin early during summer months, especially to protect technicians from extreme heat, then the expectation is different. Communication is what makes the difference. For us, this is why customer expectations matter so much. You can’t surprise people with an early arrival and then act like they should have known. They need to know upfront: what your service window is whether you give exact arrival times how much notice they get before arrival what happens if dogs are outside what happens if gates are locked why summer routes may start earlier how you handle extreme heat days I’m a big believer in the on-the-way message. If the customer gets a reasonable heads-up before arrival, they can bring dogs inside, unlock the gate, or prepare for the visit. That message matters even more when service starts early. The goal is not to sneak onto a property before people are awake. It is to run the route safely, protect the team, and still give customers enough communication to feel respected. There’s also a real operations side to this. If you wait until late morning to start every summer route, the team may end up doing the hardest part of the day in the worst heat. That can affect: speed morale safety quality callbacks employee retention A customer may prefer a later visit. But the business also has to protect the people doing the work. If we can safely complete a yard at 7 AM instead of 2 PM on a 100-degree day, that’s usually better for the technician and the route. The key is making sure your policy is clear before it becomes a problem. For example: “During summer months, our team may begin routes earlier in the day to avoid extreme heat. You’ll still receive an on-the-way message before arrival so dogs can be secured and gates can be accessible.” That one line can prevent a lot of confusion. This is another example of something that feels small until the business grows. When you’re solo, you can adjust everything manually. Once you have a team, policies matter more. You need a standard that protects the customer, the technician, and the route. How early is too early for your team to start work? And do your customers know your summer service window before the appointment happens?
Multiple jobs approved and scheduled at the same time, crew, and address
We sometimes have clients who ask for items to be quoted out separately instead of as an optional line on one quote. Then they are approving them all and I am putting all of them on the same dates since all the work for them is being completed at the same time. Is there any way or maybe it can be added in the future for combining them together into one calendar item? Kind of like when you have multiple things to invoice for a client it lets you select and invoice them together. I feel like it will help my calendar look a little cleaner and might be a bit easier on the crew if they can see everything at once instead of looking into 2 or 3 job scopes of work.
