Guides / Where to start
If you run a small shop on QuickBooks and spreadsheets, you've probably been told you need an ERP. Maybe you do. But for a lot of shops your size, an ERP is the wrong first move — too big, too disruptive, too expensive for what it fixes. Here's the honest read on whether you need one, and what's worth automating first.
A shop running on QuickBooks plus a folder full of spreadsheets is not a shop doing it wrong. It's the system most small manufacturers actually run on. The question isn't whether that setup is embarrassing. It's whether the duct tape is costing you more than fixing it would.
I ran a machine shop for about a decade before I started building software. For a long stretch the books lived in QuickBooks and everything else — quoting, the job log, who-owes-what, the running list of open POs — lived in Excel. It worked until it didn't, and the place it stopped working was never where the salesperson selling me an ERP said it would.
So before you sign up for a six-month implementation and a per-seat license, it's worth being clear-eyed about what an ERP actually buys you, and whether the thing that's hurting today is even an ERP-sized problem.
An ERP earns its keep when the work itself has outgrown what one person can hold in their head and a spreadsheet can track. The honest signals that you've crossed that line:
If several of those are true, an ERP is a real conversation, and I'll tell you so plainly. (If JobBOSS, E2, or Global Shop is already on the table, I've written separately about getting straight reporting out of each.)
But here's the part the ERP vendors don't lead with: if your process is fairly stable, your BOMs don't change much, your accountant is happy, and the pain is really just a few specific spreadsheets and handoffs — you probably don't need to rip everything out. An ERP is a big, disruptive spend, and the wrong-sized one means you're rebuilding again in two or three years. Picking it because you're tired of one bad spreadsheet is using a building permit to fix a leaky faucet.
Most of what makes a QuickBooks-and-spreadsheets shop feel chaotic isn't the absence of an ERP. It's a handful of specific gaps — the spots where work falls between two systems and a person has to babysit the handoff. Those are cheap to fix and you feel the relief immediately. The honest first move is to find the one or two that cost the most and close just those.
Here are the ones that fit a shop on QuickBooks and spreadsheets. These are real builds, deployed and running at a mid-size machine shop, not a feature list:
A small automation built right inside the shop's own Microsoft 365 watches the inbox for incoming RFQs, creates the folder, and files the request, the drawings, and the quote you sent back — automatically. A couple of minutes per quote, which is nothing on one job and real over a year. Nothing ends up buried in someone's inbox, and when the customer calls back in six months, the whole thread is where it should be. No new system to log into; it runs on the Microsoft 365 you already pay for.
A QuickBooks Online connector so the rest of your tools can read from and write to the books without anyone re-keying numbers between QuickBooks and a spreadsheet. On its own it's quiet plumbing. It's also the foundation the next two pieces stand on.
A morning email — cash position, backlog, sales month-to-date — pulled straight from the books and sent before you've had coffee. No logging in, no stitching three reports together, no waiting until after month-end to find out where you stand. For an owner who's used to "I'll know when the books close," this is the single change people notice most.
A quiet watcher that matches each vendor's order acknowledgment back to your PO line by line — price, quantity, due date, part number — and stays silent unless something doesn't match. You get one daily digest of only the exceptions. On the shop where this runs, it flagged a missed order in the first week and cut buyer time per vendor PO by roughly 45%. There's a fuller write-up in vendor PO acknowledgment tracking.
None of these is an ERP. None requires you to change how the shop runs. Each one takes a specific piece of manual babysitting off a person's plate and leaves the rest of your setup alone.
The RFQ filing, the QuickBooks connector, the owner's daily briefing, and the vendor PO watcher are all in daily production at a mid-size machine shop. The systems, and the numbers, are real — we just keep clients anonymous. The full set, with results from the actual deployments, is on the work page.
See selected work →I don't quote any of this off a price sheet, because the honest answer depends on what's actually breaking. The way it works:
Compared to an ERP — a five- or six-figure rollout, months of implementation, and retraining the whole shop — closing one or two real gaps is a smaller, faster, lower-risk thing. That's the whole point of starting there.
I'm not against ERPs. When a shop has genuinely outgrown spreadsheets — real inventory complexity, scheduling across a lot of work centers, traceability you're legally on the hook for — an ERP is the right tool and the gap-fixing approach won't carry you. If that's where you are, I'll say so, and I'll help you think about getting clean reporting and connectors out of it once it's in.
But most shops asking "do I need an ERP?" are really asking "how do I make this stop hurting?" Those are different questions. The faucet might just need a washer.
Yes — that's most of what I do. The automations above run alongside QuickBooks and your existing spreadsheets and leave the rest of your setup in place.
No. The build is fixed-price, it deploys in your own Microsoft 365 or Google tenant, and you own it. There's a twelve-month care plan, but no per-seat license and no platform you're stuck renting.
That's exactly what the paid Diagnostic is for. We measure what the gap costs first. If the math doesn't support building, I'll tell you, and you'll have a clearer picture of your operation either way.
It depends on the gap, which is why we measure first. For CNC and machine shops specifically, a lot of the groundwork already exists, so delivery is lighter and smaller jobs make sense. The first call is free, so it costs you nothing to find out.
That's a good first call. It's free, runs about 30 minutes, and it's mostly questions about how your shop actually runs. If the honest answer is "leave it alone for now," you'll hear that too. I'm an hour up the road in Sheridan, Michigan, and I ran a shop for a decade before I built software for them.