Implementation Roadmap
Starting from Ground Zero
Starting from scratch actually puts Nobilia North America in a strong position: you can design solid, future-ready processes before bad habits hard-wire themselves into the new system. This implementation roadmap combines process design with ERP selection/implementation so you don't automate chaos.
Assemble a "Seed" Team
Executive Sponsor
Clears roadblocks, signs checks, maintains strategic alignment.
ERP Champion / PM
Owns scope, timeline, vendor wrangling, day-to-day project management.
Sales Lead
Defines quote-to-cash process, CRM requirements, sales reporting needs.
Operations / Install Lead
Maps warehouse → job-site flow, inventory requirements, Procore integration needs.
Finance Lead
Defines GL structure, reporting needs, multi-currency requirements.
Optional: IT Admin or Fractional ERP Partner
Installs sandboxes, handles pilots, provides technical expertise.
Tip: Keep the seed team small—big committees stall momentum.
18-Month Implementation Timeline
Blueprint High-Level Processes
- Document current-state processes (even if informal)
- Design future-state "minimum viable process"
- Remove obvious waste (manual duplicate entry, email approvals)
- Keep only the checkpoints that protect cash and schedule
Draft Requirements & Rank Them
Split into three buckets:
- Must-Have: Multi-company, EUR↔USD GL, Procore connector, etc.
- Should-Have: Automated landed-cost, integrated CRM, etc.
- Nice-to-Have: Fancy CPQ, AI dashboards, etc.
Force-rank each list 1…N to prevent scope creep.
RFP Lite & Vendor "Shoot-Out"
- Build a 5-use-case script for vendors to demonstrate
- Invite Acumatica and NetSuite (and a wild-card if desired)
- Give each 2-hour slots; record sessions
- Grade on fit to must-have list, implementation effort, 5-year TCO
Parallel Tracks: Process & ERP Pilot
Track A: Process Hardening
- Write draft SOPs (one pager each)
- Decide data owners (who creates customers, SKUs, projects)
- Create first-pass chart of accounts & cost codes
Track B: ERP Pilot
- Stand up sandbox of front-runner ERP
- Run the 5 use-cases with real data on one live job
- Iterate weekly; log show-stoppers immediately
Phase 0: Foundation
- Core finance, chart of accounts, multi-currency setup
- User roles and permissions
- Basic system configuration
Phase 1: Quote-to-Cash + CRM
- Lead → Sales Order flow
- Integrated CRM setup
- Simple dashboards and reports
Phase 2: Procure / Inter-company / Landed Cost
- Inter-company PO flow to Germany
- Container receipts and tracking
- Landed-cost voucher implementation
Phase 3: Inventory & Warehouse
- Bin locations and warehouse setup
- Barcode scanning implementation
- Cycle count procedures
Phase 4: Procore Integration + Projects
- Connector configuration and testing
- Budget, change orders, vendor bills syncing
- Project templates and workflows
Phase 5: Install & Field Service
- Task templates for installations
- Mobile time capture for field teams
- Punch-list and close-out procedures
Phase 6: Reporting & Optimization
- Margin-per-job reporting
- Cash-flow forecasting
- Continuous improvement processes
Change Management Essentials
Successful ERP implementation requires more than just technical setup—it requires effective change management:
- Weekly 30-min "Show & Tell": Keeps non-project staff in the loop, prevents sabotage-by-surprise.
- 90-day "blackout window": No major policy changes during go-live to isolate ERP issues.
- Train the trainer: Seed-team users become in-house experts; lowers reliance on consultants.
- Data-cleanup sprints: Perfect data beats perfect features—schedule recurring scrub sessions.
Budget Guard-Rails
When planning your ERP implementation budget, consider these rule-of-thumb allocations:
Quick sanity check: First-year ERP cost ≈ 0.75-1.25% of annual revenue is typical for mid-market roll-outs.
Success Metrics
To measure the success of your ERP implementation, track these key metrics:
System Adoption
Transactions posted in ERP by Month 4 after go-live
Quote-to-Order Cycle Time
Time from quote creation to confirmed order
Inventory Variance Resolution
Time to resolve inventory discrepancies
Procore-ERP Budget Variance
Difference between Procore and ERP budget figures
Financial Close Time
Time to produce P&L after month-end (was 20 days)
Track these metrics publicly and celebrate quick wins to maintain momentum and demonstrate ROI.