Every Implementation We've Ever Done Was 90% Complete. Here's Why That's the Point.

I've been building ERP systems for gun stores for four years. In that time, I've broken more things than most consultants will admit exist.

I've miscounted inventory. I've watched accounting reconciliations collapse at month-end because of a field I forgot to map. I've sat on calls at 11pm fixing a compliance workflow that should have been caught in testing. I've deployed code to production on a Friday — more than once — because a store owner needed to open Saturday morning and the old system was already dead.

Every single Odoo instance I've launched for a gun store has gone live at about 90% complete. Every one.

Not because we didn't care. Not because we cut corners. Because the last 10% doesn't exist until the store actually uses it.

---

Nobody Had Done This Before

When we started building an ERP for firearms retail, there was no playbook. There was no GitHub repo. There was no "Odoo for Gun Stores" template sitting on a shelf.

There were gun stores running 15-year-old point of sale systems duct-taped to QuickBooks, syncing inventory through prayer and spreadsheets, and entering every serialized firearm into three different systems by hand.

And there were ERP platforms that had never heard of a 4473, didn't know what a bound book was, and couldn't spell "FFL" if you spotted them the first two letters.

So we built it. From scratch. One module at a time. One client at a time. One mistake at a time.

FastBound integration for ATF compliance. Direct API connections to RSR, Lipsey's, Sports South, Davidson's. Automated drop-ship fulfillment with FFL verification. POS that talks to accounting that talks to inventory that talks to compliance — in real time, in one system, without a human copying numbers between tabs.

Related: Four Things Killing Gun Store Efficiency

None of that existed four years ago. All of it exists now.

---

The Accounting Problem Almost Killed Us

I'll say the quiet part out loud: we got accounting wrong. Not once. Several times.

Early implementations had a problem with how product data got into the system. When inventory was imported or received, the accounting entries behind the scenes didn't always land where they were supposed to. The numbers looked right on the surface, but the books underneath told a different story. The kinds of problems that make a bookkeeper's eye twitch and a store owner question every decision they've made.

We fixed it. Every time. Sometimes at 2am, sometimes with SQL queries that would make a DBA cry, sometimes by rewriting entire modules. We built reconciliation tools. We rewrote journal entry logic. We created audit trails where none existed.

But I'm not going to pretend those problems didn't happen. They did. And every one of them taught us something that the next client never had to experience.

The system we deploy today is not the system we deployed two years ago. It's not even close.

---

The 90% Problem

Here's the thing about that last 10%.

You can build the most complete, most tested, most thoughtful ERP implementation in the world. But until a real person behind a real counter sells a real gun to a real customer on a real Saturday morning — you don't know what you don't know.

Maybe the store runs layaway differently than every other store. Maybe their receiving workflow has a step that exists because of something that happened in 2019 that nobody wrote down. Maybe their bookkeeper has a month-end process that contradicts their accountant's process, and both of them think the other one is wrong.

That last 10% is the store's DNA. You can't build it in a vacuum. You can only discover it in production, together, with the people who live inside the business every day.

And that requires something harder than writing code.

---

Change Management Is the Real Project

I can deploy a perfectly configured Odoo instance in a matter of weeks. I cannot make a staff of eight people change how they've done their jobs for the last decade in a matter of weeks.

Adoption is the hardest part of every implementation. Harder than the accounting. Harder than the compliance integrations. Harder than syncing four distributor APIs into a single product catalog.

People don't resist change because they're stubborn. They resist it because the old way — broken as it is — is predictable. They know where the pain is. They've built workarounds for the workarounds. A new system means new pain in new places, and nobody signed up for that.

The stores that succeed with our platform are the ones where ownership stays engaged. Where the GM actually uses the dashboards. Where the staff gets real training — not a PDF and a prayer — and has someone to call when the screen doesn't look like they expected.

We've learned to meet people where they are. Not where the implementation timeline says they should be.

---

What Four Years of Mistakes Built

Today, we have gun stores running their entire operation on a single platform. Point of sale, e-commerce, accounting, inventory, compliance, distributor ordering, drop-ship fulfillment, serialized tracking — all of it, in one system, talking to itself.

We have stores that went from 20 hours a week on distributor ordering to 2. Stores where month-end close went from a week-long nightmare to an afternoon. Stores where every serialized firearm is tracked from the moment it enters a purchase order to the moment it leaves the building — automatically, accurately, in compliance.

We built a product intelligence platform that gives independent gun stores access to the same kind of data that big-box retailers have had for years. Real-time pricing. Stock levels across distributors. Market trends. The ability to search a UPC and know — in seconds — who has it, what it costs, and whether you can drop-ship it.

None of this came easy. All of it came from doing the work, getting it wrong, fixing it, and doing it again.

---

The Point

I'm not writing this to sell you something. If you've read this far, you already know whether your current system is costing you money and sanity.

I'm writing this because the firearms industry deserves honesty about what ERP implementation actually looks like. It's not a flip-the-switch moment. It's a process. It's messy. It takes longer than anyone wants. And the vendor who tells you otherwise is either lying or has never done it in this industry.

We've done it. Imperfectly, stubbornly, and repeatedly. And the system that exists today — the one our clients actually run their businesses on — was built by every mistake we made along the way.

If that sounds like a company you'd trust with your operation, we should talk.