We implemented Business Central for Gear for the Game in two weeks—February 17th to March 2nd, working about 20 hours total. Here's what actually happened and what made it possible.
Week One: Financial Foundation
Chart of accounts replacement. Their system came with the generic IFRS structure. We replaced it with a GAAP-compliant chart of accounts that matched their actual business and reporting needs.
Posting groups configuration. Set up customer, vendor, and inventory posting groups to automate transaction flows. This is unglamorous work, but it's what makes the system actually function without constant manual intervention.
Tax setup. Configured sales tax handling for their business requirements and locations.
The financial structure had to be right first because everything else depends on it—customer invoices, vendor bills, inventory movements, all of it posts to the general ledger.
Week Two: Operations and Data
Customer and vendor setup. Configured posting groups, payment terms, and document layouts. Created separate document layouts for their multiple DBAs—they operate under different business names and needed that reflected in customer-facing documents.
Inventory configuration. Sports equipment has specific requirements. We set up item coding, units of measure, and costing methods for accurate inventory valuation.
Data migration. Imported current customers, vendors, inventory balances, and open transactions. We didn't migrate years of history—just what they needed to operate immediately.
Multi-entity tracking. Used dimension tracking to segregate transactions by business entity. This gave them operational separation while keeping everything in one system.
What Made Speed Possible
Client responsiveness matters. They made decisions quickly, provided immediate feedback, and showed up for testing sessions. When clients take two weeks to review a recommendation, projects take months.
Focused scope. We concentrated on what they needed to run their business immediately. Nice-to-have features can come later. This isn't about cutting corners—it's about sequencing work intelligently.
Training throughout, not at the end. We involved their team in configuration decisions and explained our recommendations as we went. By go-live, they understood their system, not just how to click buttons.
What Got Delivered
By March 2nd, Gear for the Game had a working system. They could:
- Process customer orders
- Manage inventory
- Handle vendor transactions
- Generate financial reports
- Operate their business without workarounds
Their team knew how to use it. That's the actual test of an implementation.
The Practical Takeaway
You don't need a six-month project to get Business Central running. You need:
- Clear priorities on what's essential
- Quick decision-making
- Someone who's configured these systems before and knows where the problems are
- Willingness to go live and iterate rather than trying to configure everything perfectly upfront
Traditional ERP implementation approaches exist for a reason—some businesses need extensive discovery and elaborate change management. But many growing businesses just need a working system quickly. The methodology you choose should match your actual situation, not some textbook project plan.
