How to Set Up CRM and Automation for a Small Manufacturing Business (From Scratch)

Starting With Nothing

You've taken over a small manufacturing business. Or started one. Either way, there's no CRM, no automation, probably a mix of spreadsheets, a few email chains, and one person who keeps everything in their head. That person is either you or someone who could leave.

This post is about how to fix that. Not the theoretical version. The actual decisions you need to make and the specific tools worth using.

I'll cover the CRM choice, the automations to build first, how to connect everything without a developer, and what a basic order tracking integration looks like in practice.

The CRM Decision

Two tools worth considering for a small manufacturer. You don't need a long list.

Pipedrive if your main need is sales pipeline management. You're tracking quotes, following up on proposals, moving deals through stages. Pipedrive is designed for that. It's simple, the UI makes sense within a few days, and it doesn't require a consultant to set up. Plan starts around $15 per user per month. Reporting is basic but enough.

HubSpot if you also need marketing integration. If you send newsletters, want to track which contacts opened what, or plan to do any kind of automated nurture to existing customers, HubSpot's free tier covers a lot. The tradeoff is it's more complex. More menus, more features you won't use, a steeper learning curve for anyone who needs to log in and do something quickly.

The practical answer for most small manufacturers in the first year is Pipedrive. Clean pipeline, clear next actions, low administrative overhead. You can move to HubSpot later if you grow into needing it.

One thing that matters more than the tool: define your pipeline stages before you set anything up. A manufacturing sales pipeline typically looks something like this: Inquiry Received, Qualification Call Done, Quote Sent, Quote Followed Up, Negotiation, Order Confirmed, Delivered, Invoice Sent. Agree on what those stages mean before you create them in the CRM. "Quote Sent" should mean the same thing to everyone logging deals.

The Automations Worth Building First

You don't need 40 workflows. You need 5 or 6 that run reliably and save real hours.

Quote follow-up

Someone receives a quote from you. You hope they read it. You intend to follow up. But there's production to manage and two other things happening, so it slips.

A quote follow-up automation fixes this. When a deal in Pipedrive moves to "Quote Sent" stage, trigger a sequence: follow-up email at day 3, another at day 7, optionally a WhatsApp message on day 5 for high-value quotes. All personalised with the client's name and quote details. The rep gets notified if a reply comes in.

This is a half-day build in Make. Once it runs, quotes don't get forgotten.

Order status updates to clients

Once an order is confirmed, clients want to know where it is. They'll email asking. Your team answers. This repeats 40 times a week.

Instead: when an order status changes in your tracking sheet (more on that below), a Make automation sends the client a short email or WhatsApp with the update. "Your order [reference number] is now in production. Expected dispatch: [date]. We'll message you again when it ships."

That's it. No human touch unless something changes.

Supplier reminder triggers

If you place purchase orders with suppliers, tracking those is often messier than tracking client orders. A reminder automation triggered from a Google Sheet: when a supplier PO is logged with an expected delivery date, the system sends a reminder to your ops inbox 3 days before, and a follow-up if no confirmation has been received. Simple conditional logic in n8n or Make, built in an afternoon.

Invoice follow-up

A manufacturing business sending 30 to 60 invoices a month cannot chase payment manually on all of them. An automation that checks invoice status weekly and sends a follow-up to anything past 30 days saves hours and money. Most accounting tools (Xero, QuickBooks) have API connections in Make. Map the overdue invoice data, build the follow-up email, done.

New client onboarding message

When a deal moves to "Order Confirmed" in your CRM, send a short welcome message to the client covering what happens next: timelines, contact details for updates, what to do if something changes. Takes 20 minutes to set up. Reduces inbound questions by a lot.

Connecting the CRM to a Basic Order Tracking Sheet

Most small manufacturers aren't going to implement a full ERP in year one. What they usually have is a Google Sheet that tracks active orders with columns like: order reference, client name, product, quantity, production start date, expected dispatch date, dispatch status, invoice status.

The integration between this sheet and your CRM is actually useful and not complicated.

Here's the basic setup:

When a deal in Pipedrive moves to "Order Confirmed," Make reads the deal data (client name, product, quantity, agreed date) and creates a new row in the order tracking Google Sheet automatically. No manual entry. The order reference is auto-generated (we use a formula: =TEXT(TODAY(),"YYMMDD")&"-"&ROW() to produce something like 260707-14).

From there, any update to the "dispatch status" column in the sheet can trigger an outbound message. You change a cell from "In Production" to "Dispatched," and within a few minutes the client gets a message saying the order has shipped.

This is not a custom integration. It's a Make scenario with maybe 8 nodes. Pipedrive trigger, data formatter, Google Sheets append, done. The reverse direction (sheet update to CRM) requires a bit more: a scheduled Make scenario that checks the sheet every hour and updates the corresponding deal stage if certain columns have changed.

Neither requires a developer. Both require someone willing to spend a Saturday afternoon setting it up.

What to Actually Use for Integration

Make is the right tool for most of this. It has native connectors for Pipedrive, HubSpot, Google Sheets, Gmail, WhatsApp Business (via official API), Twilio for SMS, Xero, and QuickBooks. The visual interface makes it possible to understand what a scenario is doing just by looking at it.

n8n is worth knowing about. It's open source, which means you can run it on your own server for free and have full control over your data. For a manufacturing business handling any client data that's sensitive, that matters. The learning curve is a bit steeper than Make but not dramatically so. If you're comfortable enough to set up a web server (or have someone who is), n8n is worth it.

Zapier works too, but it's more expensive per task and the free tier is very limited. If you're already paying for Zapier from a previous tool, use it. If you're starting fresh, Make is better value.

What to Skip in Year One

There's a version of this stack that costs $50,000 and takes 6 months to implement. It involves an ERP, custom APIs, production scheduling software, and a consultant. You don't need that.

Skip the ERP until your manual process is clearly broken. An ERP is complex to set up, complex to maintain, and overkill for a business doing under 500 orders a month. A Google Sheet with some automations connecting to a CRM will handle a lot more than people expect.

Skip the custom chatbot for client inquiries. A shared inbox with clear routing rules and auto-responders handles this fine at the volume most small manufacturers are dealing with.

Skip the "all-in-one" platforms promising to manage production, CRM, invoicing, inventory, and HR in one tool. They compromise on everything. Your orders are not the same as a retail business's orders. Use purpose-built tools connected together.

A Realistic Setup Timeline

Week 1: Choose your CRM (30 minutes of genuine decision-making, not 3 weeks of demos). Set it up. Import your contacts from wherever they currently are. Define your pipeline stages. Add your active deals manually. This is not automatable yet and shouldn't be.

Week 2: Set up the Google Sheet order tracker if you don't have one. Keep it simple. Eight columns max to start. Make sure at least one other person is using it by end of week.

Week 3: Build the quote follow-up automation. One scenario, one week of testing. Confirm it works.

Week 4: Build the order status update automation. Test it on one real order before turning it on for everything.

Month 2: Add invoice follow-up. Add supplier reminders. Connect the sheet to the CRM for auto-row creation.

After that, you have the core stack. Everything else is an enhancement.

The One Thing Most Small Manufacturers Miss

The reason most manufacturing businesses don't have good systems isn't budget. It's that the person who knows the most about the business is also the person who doesn't have time to set anything up.

At some point someone has to sit down and define the process before building the automation. What does a quote follow-up actually say? What's the right timing? What happens if a client replies asking to negotiate? What does "order confirmed" actually mean in terms of the production timeline?

These decisions take a few hours. They're uncomfortable because you have to commit to an answer even when you know exceptions will exist. But they're what separates a system that runs the business from a collection of tools that create more overhead.

If you do this at all, do it in order: process definition first, manual version second, automation third.

Order status updates and CRM syncing like the ones above are exactly what our call summaries and CRM updates service automates end to end.

If you want us to build this for you, book a free workflow audit at airtective.com