Sometimes you show up to solve one problem and discover something completely different needs fixing. That's what happened with Gear for the Game.
The Original Ask
Gear for the Game reached out for Business Central training. They'd already purchased licenses and figured they just needed someone to show their team how to use it. Seemed straightforward enough.
But when we started looking at their system during the first discovery session, we hit a problem: there was nothing to train on. Their Business Central was basically a blank template filled with generic sample data that had zero connection to their actual business.
You can't train people on a system that doesn't reflect reality. It would be like teaching someone to drive using a cardboard cutout of a car.
What They Actually Needed
The real issue wasn't knowledge—it was that their system wasn't set up to do anything useful. They'd invested in the software but were stuck with an empty shell.
We proposed switching from training to our BC Rapid implementation. They already had the licenses. They were committed to using Business Central. What they needed was a system that actually worked.
Building From the Ground Up
Over four weeks, we configured their Business Central environment to match their actual business operations:
Financial setup: Implemented a GAAP-compliant chart of accounts, configured posting groups for automated transaction flows, set up proper sales tax handling, and established accounting periods.
Customer and vendor management: Created posting groups, templates, and payment terms that matched how they actually do business—including handling foreign vendors.
Inventory and products: Built out item coding, units of measure for sports equipment variations, FIFO costing, and basic warehouse management.
This foundation matters because every transaction in Business Central flows through these configurations. Get them wrong and you're fighting your system every single day.
The Unexpected Complexity
During implementation, we discovered Gear for the Game operates under two separate DBA entities. This wasn't something that would've come up in a training scenario, but it was critical for system design.
We implemented dimension tracking and created separate document layouts for each entity so their Business Central could properly segregate activities and reporting for both businesses.
From Expensive License to Working System
Before we started, Gear for the Game had software they couldn't use. After four weeks, they had a functioning business management system handling their complete order-to-cash process, managing inventory across product lines, tracking financial performance for both entities, and providing useful reporting.
More importantly, their team was trained and confident using it—because now there was actually something worth using.
Built for What's Next
The system is now configured to handle growth: new product lines, additional sales channels, increased volume. They won't need to reconfigure as they scale.
That's the difference between implementing a system right versus just going through the motions. One gives you a foundation for growth. The other gives you an expensive problem.
