Years of “you should really get a CRM.”

I’d been telling this client for years that he needed a CRM. Years. Every time we touched base about the website, I’d work it into the conversation. He was running a full distribution operation — church supply: chairs, pews, baptistries, flooring, the whole thing — on pen, paper, and memory. He knew his customers. He just had no visibility into his business.

I’d ask him: how many jobs are waiting on a quote right now? He’d shrug. Which ones have paid and are ready to ship? Another shrug. If a customer went quiet, what happened to that job? Usually nothing good. It just sat somewhere, waiting for someone to remember it existed.

He’d nod when I brought it up. Say it made sense. And then go back to the way he’d always done it, because it worked well enough and change is genuinely hard when you’re also running a business every day.

Then his son came on. And things got better — and more complicated.

His son joined the business and built out a set of Excel templates. Good ones, actually — organized, consistent, better than the paper. It was a real step forward.

The problem was that now instead of information in no one place, the information was in many places — a folder full of individual spreadsheets, one per job, saved with dates and customer names, with no way to see across them. You could find any single job if you knew what you were looking for. But you couldn’t answer the questions that actually run a business. How many open? How many waiting on approval? How many billed but not paid? Those answers required someone to physically open files until they found the answer.

He still didn’t know his numbers. He just didn’t know them in a more organized way.

Eventually he said yes.

I don’t know exactly what tipped it. Maybe the questions I kept asking finally accumulated. Maybe the business grew to a point where the manual approach became genuinely painful. Maybe he just got tired of not being able to answer simple questions about his own operation. Whatever it was, one day he said: okay. Let’s try the CRM.

We set up Zoho. Built a contact form that fed directly into Leads in the CRM. Got the basics running. He started using it.

Then he asked: how do I create a quote in here?

So we built that.

Then he mentioned he was spending too much time entering data that already existed somewhere else. Why did he have to type the same information again?

So we built the automation that moved it for him.

A few months later.

We mapped every place a human was touching data and asked: does this actually need to be a human? Some things did. Most didn’t.

The result, built piece by piece over several months, was a complete six-stage digital operation:

• Stage 1 — New Inquiry: Customer fills out a web form or staff enters a call-in. Either way, a Lead is auto-created in Zoho CRM with all the relevant information.
• Stage 2 — Qualify Lead: One status change converts the lead. Contact record, Church record, and Open Sale all created automatically. WorkDrive folder created for the client.
• Stage 3 — Build Quote: CPQ quote builder with a full product catalog. Products, pricing, quantities — all organized. Quote generated from existing data, not re-entered.
• Stage 4 — Send Estimate: Estimate sent to the client. Books Estimate created simultaneously. Every approval timestamped.
• Stage 5 — Estimate Accepted: Two flows fire at the same moment. Invoice generated. Purchase orders auto-created and grouped by vendor. Bills of lading generated. All of it from the data that already exists.
• Stage 6 — Sign & Complete: Documents sent via Zoho Sign. Signed copies auto-filed to the correct WorkDrive folder. Done.

The questions I used to ask — how many are waiting on a quote, which ones have paid, where does this job stand — now take about three clicks to answer. The information is there. It’s current. It’s organized. And almost none of it required a human to put it there.

We’re already in Phase 2.

The thing about building a real system is that once it’s running, you start to see what else is possible. What else you could add on top of a foundation that already works. What reporting you could build, what additional automation, what visibility you now have access to that you didn’t before.

That’s where we are. Phase 2. And the only reason Phase 2 exists is because someone finally said yes to the CRM.

If I’d walked in with a six-stage pipeline diagram on day one, he would have said no. Politely, but no. It would have been too much, too fast, too abstract to see the value in. The right move was exactly what happened: start where he was, build what he needed next, and let the momentum do the rest.

That’s not a strategy. That’s just how people actually change.