← The Automation Files
AI & MCP 7 min read · July 2026

The voice layer only works if the foundation underneath it is clean.

How we added MCP to Church Outlet’s Zoho pipeline, what it looks like in practice, and why the order of operations matters more than most people realize.

Church Outlet sells baptistries and church furniture. Before we started working together, everything ran on pen, paper, and a system of email threads and file folders that worked because the right people knew where everything was. A few years ago we helped them move the whole operation into Zoho, and spent a long time building it around the workflow they already had rather than the other way around.

Six stages, fully automated. Web form to filed documents. A prospect submits an inquiry, and it moves through CRM, quoting, vendor freight coordination, estimate, signature, purchase orders, bill of lading, and WorkDrive filing without anyone manually carrying it from one step to the next. The owner has six touch points in the whole pipeline. Everything else runs itself.

Once that was solid and had been running cleanly for a while, we added something new. We connected MCP.

What MCP is in one sentence

MCP stands for Model Context Protocol. It’s a standard that lets an AI model communicate directly with your live business tools, not just answer questions about them. We’ve written a plain-English explainer if you want the full technical picture. The short version: before MCP, AI was a very good advisor that couldn’t touch anything. After MCP, it’s a participant that can look up live data, trigger actions, and move work through your system while you talk.

What it actually looks like at Church Outlet

The owner is standing in a church parking lot after walking a site with a client. On the way back to his car, he pulls up Claude on his phone, hits the microphone, and speaks the context of the meeting. What the client needs. What product they’re looking at. A few specifics about the order.

The CRM record gets created. The quote starts building. The follow-up task is logged. By the time he’s back in the car, the pipeline has already moved.

No laptop. No login sequence. No navigating to the right screen and filling in the right fields. He described what happened. The system handled the rest.

What he can say: Create a quote for a new client. Check the status of a deal. See which freight quotes are still outstanding. Pull up what’s been sent to a particular vendor. Trigger the next step in a workflow. All in plain English, from anywhere, without opening a browser.

Why the order matters

Here is the thing people miss when they get excited about AI and voice control: a voice layer on top of a broken system is just a faster way to create chaos.

If the data in your CRM is inconsistent, MCP will surface that inconsistency faster. If your workflow has manual gaps and redundant steps, AI will try to navigate those gaps and either get confused or create duplicate work. If nobody really understands where a deal is supposed to be at any given stage, asking an AI to check the status of that deal will produce a confident answer that reflects the mess underneath.

The reason MCP works so well at Church Outlet is specifically because we spent the time before it building a pipeline that is clean, consistent, and automated. Every record follows the same structure. Every stage has a clear trigger. Every document goes to the right folder with the right name. The AI has reliable data to read and reliable processes to move.

That is not accidental. That is the prerequisite.

The honest sequence for any business thinking about AI

Most of the excitement around AI for small business is focused on the layer we added last. The voice interface. The natural language commands. The feeling that the computer finally understands you.

That part is real and it is genuinely useful. But it’s the third step, not the first. The sequence that actually produces results looks like this:

First, map the actual workflow. Not the one you think you have, the one your team actually uses. Where does information enter the business, who touches it, where does it live, and what happens when someone is out sick or forgets a step.

Second, automate the steps that can run without a human decision. The record creation, the document generation, the file routing, the status updates. Get those running reliably before you put AI on top of them.

Third, and only after the first two are solid, add the AI layer. Now you have something worth connecting. Now the AI has structured, reliable data to work with. Now the voice commands produce consistent, trustworthy results because the system underneath them is trustworthy.

Church Outlet is at step three. Most businesses we talk to are still at step one, and they want to start at step three. That’s why a lot of AI pilots fail in small businesses. Not because the technology doesn’t work. Because the foundation wasn’t ready for it.

If you’re wondering where your business is in that sequence, that’s exactly what an automation audit is for. We map what you have, identify where the gaps are, and tell you what needs to happen before the AI layer makes sense. See how the audit works →
← MCP in plain English The Church Outlet CRM build →

More plain-English business tech

No jargon. No sales pitch. Just the stuff you actually need to know.

See all posts →

Related reading