A CRM is a promise to reply: how we wire follow up so nobody is forgotten

A lead came through a landscaper's website on a Saturday morning. By the time anyone looked at the inbox on Monday, the homeowner had hired someone else. That is not a sales problem. It is a follow up problem, and it is fixable with software.

What a CRM is actually for

People think of a CRM as a place to store contacts. That is the least useful thing about it. The useful thing is that it makes a promise on the company's behalf: every person who reaches out will hear back, and nobody will fall through a crack. The software exists to keep that promise while the owner is on a roof, in a meeting, or asleep.

We build the CRM for each client instead of buying one, because the promise is specific to how that business sells. A painter follows up differently than a retirement advisor. The wiring has to match the business.

The four pieces of follow up

An instant acknowledgment that reads like a person. The moment a form is submitted, the prospect gets a reply. Not "Thank you for your submission, a ticket has been created." A short note in the owner's voice: thanks for reaching out about the backyard, we will take a look and get back to you by tomorrow, here is a number if it cannot wait. It is written once, with the owner, in their words, and it goes out within seconds. The prospect now knows they were heard, which is most of what they wanted in that moment.

A task with a deadline. At the same moment, a task appears for whoever handles new leads: reply to this person, due by a specific time. It sits at the top of their list until it is done. If the deadline passes, it changes color and shows up in the owner's view. A lead cannot sit quietly in an inbox because it is no longer in an inbox. It is a task with a clock on it.

A nudge when the prospect goes quiet. Most leads do not close on the first reply. The prospect asks a question, gets an answer, and then life happens. The CRM watches for that. When a lead has had no activity for a set number of days, it creates a follow up task and drafts the message: just checking in, still glad to come by and take a look. The owner reviews and sends it, or the system sends it after a delay if that is how they want it set. Either way, silence does not turn into forgetting.

Email threads on the timeline. The company's real email account is connected, so every message to or from the prospect appears on the lead's page, in order, alongside the form, the notes and the calls. Anyone on the team can open the lead and see the whole conversation without digging through three inboxes. When the owner asks "where are we with the house on Ocean Avenue," the answer is one click away.

Why built and not bought

• Off the shelf CRMs assume a sales team with a pipeline and quotas. A four person trade business has an owner with a phone.
• The acknowledgment, the deadlines and the nudge timing are the whole product. In a bought tool they are buried in settings and automation builders nobody on the crew will open.
• Lead intake is wired directly to the website, the website assistant and the email account, so nothing has to be copied between tools.
• The client owns it. The data is theirs, the code is theirs, and the ongoing cost is hosting, not a per seat subscription that grows every time they hire.

We built the first of these for a custom home builder, then cloned it for a landscaper and a painting company, changing the fields and the follow up timing for each. The bones are the same because the promise is the same.

What it looks like on a Saturday

A form comes in at nine in the morning. The homeowner gets a warm reply in the owner's words within seconds. A task appears with a Monday morning deadline. If the owner happens to check the app from the truck, they can reply right there and the task closes. If they do not, Monday morning opens with that lead at the top of the list, in color, and the reply goes out before the first coffee is finished. If the homeowner goes quiet after that, the system drafts the check in a few days later. Nobody had to remember anything.

What changes for the owner

The owner stops being the only person who knows what is going on. The crew lead can answer a lead. The office can see what the owner promised on the phone. Weekend leads get a human sounding reply on Saturday and a real one on Monday, in that order, every time. And the owner stops lying awake trying to remember whether they ever called that one person back, because the system remembers for them.

A CRM that keeps the promise to reply is the first thing we wire into every lead system we build, whether the client is a landscaper in West Palm Beach or a software company selling to universities.

Questions people ask