Monday Morning, Two Ways: Running a Fleet

Tyreese: Look. Forget features for a minute. Forget pricing pages. I want to show you a Monday morning, because Monday morning is where your software stack either works for you or you work for it. And I am going to show it to you twice.

First, the stitched stack. It is six forty-five in the morning and the owner is on his second coffee, and he has a question that should be simple. What is happening today, and what needs me?

He opens Jobber first, because that is where the jobs live. Three techs, a full day, looks fine. But Jobber knows nothing about last week. It does not know the big plumbing fleet across town finally answered an email. It does not know two prospects went quiet. Jobber knows jobs. That is all it has ever known.

So he opens Monday, because that is where the pipeline lives. The board says follow up on three fleets. Okay. Follow up how? The last email to one of them lives in Brevo. The call notes from another one live in the sales rep's phone, in a text thread, under a photo of a carburetor. The third one, the owner swears somebody sent them a postcard in the spring, but mailing meant exporting a list and emailing artwork to a mail house, and nobody can find the thread, so maybe it went out and maybe it did not. Nobody knows. The board says follow up. The board cannot say with what, or what already happened, or what anybody said back.

And the rep? The rep is good. The rep is also working from memory and a spreadsheet tab named final version two. He makes the calls he remembers. He does not make the calls the system forgot, because the system is three systems, and each one of them is telling him a third of the truth. By nine o'clock the day is running fine on the surface. The trucks roll, the jobs get done. But the growth work, the follow-up, the touches that turn into fleet accounts, that work leaks out of the cracks between the logins. Not because anybody is lazy. Because nobody can see the whole board.

Now run the same Monday on one system. Six forty-five, same coffee, same question. What is happening today, and what needs me?

The owner opens his command view. Today's stops, all of them, grouped by location. Money outstanding, who owes what and how late it is. And the approvals waiting on him, because in this business the owner is the approver, and one of them is a postcard a rep queued on Friday afternoon. One look, one click, approved, and it mails against the mail credit the shop already bought. No export, no mail house, no artwork thread. Approved before the coffee cools.

The dispatcher opens the board. Three techs, stops grouped by location, assignments across the whole day. When a customer calls to move a stop, she moves it once, in the same record the tech is looking at, and nobody re-types anything into a second system.

The rep opens his day, and his day is already built. It is called Sales Today, and it is exactly what it sounds like. The calls that are due, with a brief written for each one, who they are, what their fleet looks like, what the last touch was. The email drafts the agent wrote over the weekend, sitting in a review queue, because nothing goes out under his name that he has not read. The mail approvals for his accounts. The sales kits to print for the drop-ins he is doing this afternoon. His meetings, in the same screen. He does not go hunting for his job in three applications. His job is laid out in lanes, in the order a human would do it.

And the tech opens the field app and sees his stops, and at every stop he sees the vehicles, and on every vehicle he sees its work order and its inspection, the same record the office sees, updated the moment he closes a job out. The invoice that generates off that work order is right because the work order is right, because it was never re-typed by anybody.

Then lunch happens. The rep is fueling up across from a competitor's yard and he photographs one of their vans, the way you do. By dinner, that photograph is a researched prospect sitting on the pipeline. Company, address, phone, what their fleet looks like, and the first touch already staged on the ladder, email if there is an email, the website form if there is not, the postcard after that, and the call last, when it is warm. Nobody researched it at midnight. Nobody typed it in twice.

That is the whole episode, right there. Same people, same trucks, same Monday. In one version the software is three partial truths and a rep with a good memory. In the other it is one record that every role reads from. Your takeaway is small and you can do it today. The next time you catch yourself copying information from one system into another, stop and say it out loud: I am the integration. Count how many times it happens this week. That count is the real price of your stack, and no vendor is ever going to put it on an invoice for you.

That's the show. Go run your numbers. See you at the next one.