Pricing Built Around Your Dealership Operating Model
Choose the F2 Core capabilities that match your sites, workflows, hardware, vendors, and reporting needs.
Priced around how your group operates
Scoped to location count and workflow depth
Software, hardware, and partner services quoted separately
One conversation to map the right package
Modular by operating lane
Pricing reflects how customers adopt F2: platform foundation, environmental workflows, energy management, facility operations, hardware, and partner workflows.
Platform foundation
System of record across locations, assets, work, vendors, and documents.
Environmental
SPCC, AFMS, waste workflows, labels, and audit readiness.
Energy Management
HVAC, compressed air, dryer, current sensing, and runtime analytics.
Facility Operations
Tickets, work orders, RFQs, approvals, invoices, vendors.
Hardware and devices
AFMS, EO3, compressor, dryer, lift, device health.
Site and portfolio considerations.
Dealer groups may need multi-site dashboards, role-based access, reporting, partner routing, and implementation support.
Pricing scales with the variables that matter most: number of sites, users and roles, devices and assets, and workflow complexity.
Number of sites
Users and roles
Devices and assets
Workflow complexity
No surprise conversation
The page invites a pricing conversation without hiding the variables that affect scope.
Pilot scope
Pilot sites, lanes, and success criteria defined upfront.
Rollout plan
Phased rollout aligned with internal capacity.
Integration needs
Optional integrations identified and timed appropriately.
Support model
Support tier and partner involvement defined upfront.
Pricing questions
No. F2 Core is sold to dealership groups with packaged scope. Pricing depends on site count, lanes, hardware, and rollout — best discussed in a pricing conversation.
No. F2 Core is an enterprise platform sold to dealership groups.
Yes. Most groups start with the lane that hurts most — Environmental, Energy Management, or Facility Operations — and expand once the operating model is in place.
Ready to map the right package?
One conversation to align on scope, lanes, and rollout.