ERP implementation, de-risked · for distributors and manufacturers, 20 to 100 employees
+1 (514) 701-6084
ERP implementation, de-risked · for distributors and manufacturers, 20 to 100 employees
+1 (514) 701-6084
We implement Odoo and Acumatica, real ERP for growing manufacturers and distributors.
(We know the duct-tape stage, and we build past it. Read this before you sit through a single vendor demo.)
Built on your real data and proven working before you sign anything.
The whole argument is below. Five minutes to read. ↓
Re: What the ERP horror stories have in common, and how to keep yours from getting written.
Montreal, July 2026
Dear owner (or the controller reading this for one),
You know the routine by heart. Nothing in your stack actually talks to the rest of it. The warehouse count lives in a spreadsheet that's right most of the time. A quote goes out built on a BOM cost that's already a little stale. Receipts get emailed to your admin and keyed in by hand, again, somewhere else. Month-end starts as a close and turns into archaeology, three weeks of it, and the number that finally comes out the other end is one nobody in the room fully trusts.
Sit in the distributor and manufacturer forums for an afternoon and it is the same story on repeat. A distributor running 6,000 SKUs across two warehouses, reconciled in a spreadsheet, stocking out on the best-sellers while dead stock piles up in the back. One machine shop, 14 people, where allocating material to a job means somebody also goes and updates a second Excel file, every single time. A factory manager whose team still counts inventory by hand, daily. A manufacturer whose real BOM costs live in one person's head, so every quote drifts a little further from what the materials actually cost.
Sound like your Tuesday?
Here's the part nobody explains to you up front: buying the ERP software and getting it implemented correctly are two different purchases. Everybody shops hard for the first one, compares per-seat pricing, sits through demos, negotiates the license. Almost nobody vets the second one the same way, and the second one is where the six-figure risk actually lives.
Then two things are true, and the first one is this: the mess is proof you grew. Nobody builds a $10M company inside one tidy system. You bolted on whatever kept orders moving at the time, it worked, and somewhere along the way you personally became the bridge between five systems that have never spoken to each other.
The second thing: the duct tape is now on payroll. Quotes drift. Margin reports land three weeks late. Bids get built from numbers you only mostly trust. Doing nothing is a decision too, and it keeps billing you in hours and blown jobs instead of invoices.
And if you run QuickBooks Desktop, Intuit already made part of this decision for you. The last non-Enterprise version stops receiving payroll tax tables, bank feeds, and security patches on September 30, 2027, a deadline Intuit picked without asking you. Enterprise buys you a reprieve, but it is its own treadmill of climbing per-seat fees, not a place to settle.
So why do smart operators sit in the mess for years?
Because you've read the same stories we have. The manufacturer who thought the switch would take 6 months and watched it take 16. The small manufacturer who was $170,000 in before a single unit was produced. The company in year 3 of a nightmare implementation, six figures deep in unbillable work. Panorama Consulting's research has put more than half of ERP projects short of their objectives, year after year.
One buyer on a manufacturing forum said it plainly: "This is our first time implementing an ERP, and the more I read, the scarier it sounds."
The fear makes sense. We'd just aim it at the right target, because most buyers are watching the software when they should be watching something else.
Read the horror stories again. Something jumps out
Almost none of them are software failures. The exact system that buried one company runs beautifully at the shop across town. Same code, same modules, opposite outcomes. What failed was the discovery nobody did, the scope that never got written down, a data migration with no clear owner, and in more cases than you'd think, a partner who quoted the job before he ever saw the floor.
Acumatica's own user community reached the same verdict about implementation partners: a good one makes all the difference. The badge on the website doesn't tell you which kind you're talking to. There are over a hundred certified partners selling the same software with the same logos.
The partner is the decision. The software is just the tool the partner installs.
Here's the uncomfortable part: that finding should make you more suspicious of people like us, not less. We're a partner. We have the badge too. So instead of asking for trust, we'd rather show you the control system we work under, in writing.
Two more structural things, because they decide budgets.
Licensing, briefly, because it is the part any partner controls least. We lead with Acumatica, where we hold Gold certification, partly because it is priced by what you actually use rather than charging a toll on every person you hire, and when the cheaper path genuinely fits we implement Odoo instead and say so. Past that, we do not spend your call litigating seat prices we cannot change. The money that decides your project is the implementation, and that is the conversation worth having.
Adoption. Half the fear we hear isn't about software at all. It's "my people aren't tech savvy, they'll revolt, and it'll be my fault." Our line on this: if your least technical person can't run their part of the day in the new system, it isn't implemented. It's installed. Training sits inside the scope document like everything else.
And sometimes the right read is you don't need an ERP yet. A tight four-person shop on QuickBooks with real discipline should probably stay put for now, and we'll tell you exactly which conditions would flip that answer. It costs us a sale here and there. We'll take that trade.
Talk soon,
Anthony Boulos
Kerningcode, Montreal
Answer these honestly with your leadership team first. If you can answer all six, you walk into every demo in control of the conversation. And if a vendor can't engage seriously with them, that tells you something too.
1. What is the chaos costing us today? Hours, errors, delays, key-person risk. Put a rough number on it. That's your baseline business case.
2. Which processes must the system fit, exactly? Your non-negotiables: how you quote, build, ship, invoice. Generic software bends your business. Good implementation fits it.
3. What does success look like in 12 months? Three to five measurable outcomes. Live inventory accuracy, days-to-close, quote turnaround. No targets, no accountability.
4. Who owns this internally? Every rollout that works has an internal champion with real authority. Not just IT. Someone who owns the outcome.
5. What's the total cost, and is it capped? Licenses, implementation, training, support. The real question underneath: is the implementation price fixed, or an open-ended estimate?
6. What happens if it doesn't work? What do you pay for unfinished work? Who supports you after go-live, and for how long? The answers reveal who is actually carrying the risk.
We work through all six with you on the call, on your numbers.
Whatever logo is on the box, NetSuite, Dynamics, Acumatica, Odoo, the implementation runs one to two times the first-year license, sometimes more. The sticker price you spend weeks comparing is the smallest number in the project.
Which is the whole reason this page is about the partner and not the software. We do not control what a vendor charges for a seat, and neither do you. What decides whether your project lands on budget is who does the work and how honestly they scope it, and that we control completely. Your real number comes from that scope, which is exactly what the working session pins down.
You'll get one clear read on whether an ERP is even warranted for your company, real cost ranges for your size and shape stated out loud, and the reasoning behind all six vendor questions. "Not yet" is a live answer, and you'll hear it if it's true.
There's no demo and no deck, and nobody chases you afterward.
The first ten minutes or so are your shape. Entities, jobs or SKUs, how many QuickBooks files, what gets typed twice, where month-end dies. You don't need anything prepared. You already know these answers cold.
Most of the rest is the math and the traps. What companies your size actually end up spending, license versus implementation, where the quotes you'll receive will try to hide the ball, and which of the six questions matter most for your situation.
The last few minutes are the read: ERP now, or not yet, and what would change the answer. If it's "now" and we look like a fit, we'll describe what a written-scope discovery looks like. Then you go think about it. We don't do follow-up sequences.
It's for manufacturers and distributors across North America, owners, controllers, and ops leads at companies of roughly 20 to 100 people, running on QuickBooks plus spreadsheets plus point apps where the SKUs, BOMs, lots, and warehouses have multiplied past what the duct tape can carry. If your day runs on landed costs, BOM accuracy, lot or serial tracking, and inventory spread across more than one location, whether or not job costing is also part of the mix, this was built for your business, not a generic mid-market.
It probably isn't for you if you're under twenty people with tight discipline and one clean QuickBooks file (keep it), or if the decision is already made and you're shopping for someone to bless it. And if what you want is the cheapest possible Odoo subscription with no implementation help, Odoo sells direct. That might genuinely be your answer.
Everything above is the argument. This is the structure we actually work under, and you should hold any partner you talk to, including us, to the same standard. The center of it is simple: you see it work on your own numbers before you sign anything. Discovery, the price, the payment schedule, all of it exists to get you safely to that moment.
It also means one name is on the hook for the whole thing. If something goes wrong, you are not stuck refereeing a fight between the software vendor and whoever installed it. That's this team, start to finish, discovery through go-live and the months after. One accountable partner, not two companies pointing at each other.
Notice what that structure does: at every step, we carry the risk of our own promises. If the proof of concept doesn't convince you, you've lost a few weeks. Not your budget, and not your confidence. That isn't generosity. It's confidence. A partner who controls their delivery can afford to guarantee it. A partner who bills by the hour cannot, because the longer your project runs, the more they earn.
The session is free and costs you thirty minutes. Worst case, you leave armed for every sales conversation that follows.
Thirty minutes and real numbers, with a real person from our Montreal office, serving manufacturers and distributors across North America.
Trouble seeing the calendar? Open it in a new view here. Or just call: +1 (514) 701-6084.
Scope decides it, so we give real ranges on the call instead of a sticker here. The shape of it: the per-seat price you see advertised is the smallest number in the project, and implementation typically runs one to two times the first-year license. We'd rather you hear that from us than get anchored on an $80-a-user headline that has almost nothing to do with what your project actually costs.
That skepticism is earned. The change-order-every-day shop is real, and we've cleaned up after a few. What's different is the sequence: discovery happens before the contract, the scope document names what's in and what's out, new requests get priced in writing before work starts, and after discovery the document is yours even if you walk. Ask any partner to put that sequence in writing and watch what happens.
Maybe. Ask them how many chart-of-accounts conversions they've done. ERP projects fail on process design, data migration, and change management far more often than on anything infrastructure-shaped, and those are different trades.
Possibly not, and that answer is free. One accountant on Reddit put it well: Acumatica targets the "not quite big enough for NetSuite" companies, and its consumption licensing sizes to what you use. On the call you'll get the crossing conditions, meaning the SKU counts, entity counts, and process signals that say it's time (or that it isn't).
So have we. The 16-month stories tend to share a history: discovery was thin and the scope kept moving. With both pinned down in writing, a typical mid-size implementation lands in the 4-to-6-month range, phased so the business keeps running while it happens, and you'll see the phasing before you commit to anything.
Thirty minutes with someone from our Montreal office, serving manufacturers and distributors across North America. Real numbers, the six questions, and a clear read on whether you even need this yet.
Book Your Working SessionP.S. Remember the pattern: it was almost never the software. It was discovery that got skipped and scope that never made it into writing. Both are checkable before you sign anything, and checking them is what the free session is for. Pick a time here.
P.P.S. Prefer to do homework first? The free guide covers when you need one (and when you don't), the real cost math, and all six vendor questions. Grab it here, then book whenever you're ready.