ARC Gaming & Technologies unified CRM, asset management, accounting, expense, and payroll on Weaver. In the first month after rollout across two regulated divisions, ARC logged 10,000+ interactions across 246+ venues.
Where the data flows
A deal closing in CRM books revenue in the GL automatically. A new machine procured into the asset register flows into the books on the same write. No Reverse-ETL, no nightly sync jobs, no integration tax between divisions.
Apps in use
Three Weaver-native capabilities, all deployed in production at ARC, all writing to the same data layer.
Field-route CRM for managing 246+ venues across two regulated markets, with native VoIP, route planning, and pipeline.
A fleet of 2,000+ depreciating, geographically distributed gaming machines tracked end-to-end alongside the books.
The architectural layer that makes "deal closes in CRM → invoice writes itself in the GL" literal, not aspirational.
How the migration ran
Each workstream replaces one or more legacy vendors. Together they tell the story of one customer running multiple Weaver apps on the same data layer.
ARC was running two Salesforce Enterprise instances — one per regulated market — at a combined ~$250K/year. Workflow changes required certified consultants, and field teams had no real route-planning surface. The migration consolidated both divisions onto one Weaver deployment with two isolated workspaces.
Week 1
Mapped existing pipelines, custom fields, and workflows. Imported customer records into two isolated workspaces. Configured an 8-stage pipeline (Prospect → Customer) per division and set up regional account ownership.
Week 2
Configured custom fields and data-completeness scoring. Stood up the click-to-call dialer (Twilio-backed) for both instances. Enabled Sales Gravity for field teams with route planning. Built workflow automations: compliance triggers, check-in reminders, status escalations.
Week 3
Hands-on pipeline training for both division sales teams. Mobile rollout with bottom-nav-optimized interface. Daily activity report generation enabled for managers.
Week 4
Both instances fully operational. Salesforce decommissioned. Weighted-pipeline forecasting (Revenue Insights) active. Surpassed 10,000 recorded interactions across calls, emails, meetings, and venue check-ins.
A route operator at ARC's scale has an asset-tracking problem most ERPs do not solve elegantly: thousands of regulated machines across hundreds of venues, each with its own location, maintenance history, depreciation schedule, and compliance status. Weaver shipped asset lifecycle, full accounting, expense management, and payroll on one platform — instead of an ERP plus a separate asset tool plus a separate expense tool plus a separate payroll vendor.
Roll-in
Imported the existing machine fleet via spreadsheet UI with column mapping and validation. Tagged each asset with location, division ownership, and depreciation method.
Capture
Field technicians use camera + barcode scanning to update assets in place. AI suggests the right asset record; ARC's technician confirms and saves. Every change is logged with who made it and when.
Procure
16-step PR → PO → GRN → Invoice → Capitalization flow connects new-machine procurement to the GL automatically. 3-Way Match (PR ↔ PO ↔ Invoice) reconciles before posting.
Close
Automated monthly depreciation runs across the fleet with category, life-based, and status rollups. CPA-standard reports out of the same workspace, no spreadsheet round-trip.
CRM, accounting, asset management, expense, and payroll all run on Weaver's Single Data Backbone — the same layer that handles fleet telemetry and BI for ARC's 2,000-machine, 246-venue operation. No Reverse-ETL between operational systems and analytics, no nightly sync jobs between divisions, no warehouse round-trip to ask a question of live data.
Operational systems
CRM, accounting, asset management, expense, and payroll write to the same Weaver data layer. Every cross-app outcome on this page — deal closes in CRM, invoice writes itself in the GL; new machine procured, GL entry posted automatically — is a direct consequence of the shared backbone.
Analytics & telemetry
Per-machine and per-venue activity, fleet utilization, and BI dashboards run on the same backbone. ARC asks live operational questions of real data, not a copy that landed in the warehouse last night.
Outcomes
Numbers from the ARC migration. Where context matters (denominators, time windows), it is included.
| Outcome | Context | Workstream |
|---|---|---|
| 2 isolated workspaces, one platform | The two regulated divisions run as fully independent CRMs without paying for separate orgs. | Sales Operations |
| ~30 days, kickoff to production | Both CRM instances live and Salesforce decommissioned within the first month. | Sales Operations |
| 10,000+ interactions in month one | Calls, emails, meetings, and venue check-ins logged across ~246 venues — roughly 40 interactions per venue, per month. | Sales Operations |
| $250K/year Salesforce contract eliminated | Two SF Enterprise instances at ~120 seats consolidated onto a single Weaver deployment. | Sales Operations |
| 2,000+ machines under one asset lifecycle | Every regulated machine tracked end-to-end (active → maintenance → retired) on the same data layer as the books. | Financial Ops |
| One platform, four vendor categories collapsed | ERP + asset tracking + expense + payroll consolidated where most operators run four separate tools. | Financial Ops |
Why this works (under the hood)
Most ops stacks fragment data across a CRM, an ERP, an asset tool, an expense tool, and a payroll vendor — then bolt them together with integrations and nightly sync jobs. Weaver puts every app on the Single Data Backbone so a write in one app is immediately visible to every other app, with no glue code in between. The full bibliography behind this design — including the lakehouse-architecture and data-integration literature — sits at the bottom of this page and at /research.
About this case study
ARC consolidated CRM, asset lifecycle, accounting, expense, and payroll onto Weaver across two regulated divisions. If your operation is fragmented across vendors, we should talk.
Weaver's unified-platform design is anchored to the lakehouse-architecture and data-integration literature, with ERP-failure and CRM-as-process research as supporting context.
Armbrust, M., Ghodsi, A., Xin, R., & Zaharia, M. (2021). Lakehouse: A new generation of open platforms that unify data warehousing and advanced analytics. In Proceedings of the 11th Conference on Innovative Data Systems Research (CIDR '21).
The Databricks "lakehouse" paper — the architectural argument for unifying warehouse and lake into one platform that supports both analytics and applications.
Read sourceHalevy, A., Rajaraman, A., & Ordille, J. (2006). Data integration: The teenage years. In Proceedings of the 32nd VLDB Conference, 9–16.
Survey of why enterprise data integration is structurally hard and why "every new application means another integration project."
Read sourcePanorama Consulting Group (annual). The ERP Report. Denver, CO.
Annual ERP implementation outcomes survey — cost overruns, schedule slippage, benefit shortfalls.
Read sourceReinartz, W., Krafft, M., & Hoyer, W. D. (2004). The customer relationship management process: Its measurement and impact on performance. Journal of Marketing Research, 41(3), 293–305.
Foundational empirical CRM study — operationalises CRM as a process and measures its actual impact on firm performance.
Read sourceWhat if your data platform came with native business apps? Weaver collapses Databricks + Salesforce + ERP + integration plumbing into one platform on a single real-time data backbone.
Keep the QuickBooks ledger your accountant loves. Add CRM, projects, inventory, BI, and AI agents on one data backbone.