Pricing & proposals

Every proposal is built for one operation.

PRO Enterprise is quoted per engagement. The platform fee follows how many office and field people you run. The implementation scope follows how many branches, integrations and years of history have to come with you.

ProposalPrepared after discovery
Platform · office seats
Platform · field seats
Implementation · configuration and workflows
Data migration · customers, sites, units, contracts, history
Integrations · accounting, payments, telematics
Training · on-site or remote
Optional · FieldTracer Harness, Diamond Reports, Premium Support
Amounts appear once we have mapped your branches and users.

Illustrative proposal structure. Your scope and fees are prepared after discovery.

How pricing works

Two numbers, quoted together.

A monthly platform fee and a one-time implementation scope. Both come out of the same discovery call.

Platform fee

Billed per user, every month. Office seats and field seats are priced differently because they do different jobs. Add a branch and the fee grows with the people in it. Seat changes and billing dates follow your agreement.

Implementation and migration

Paid once, before go-live. It covers configuration, your data moving in, and training your team. The scope is set by how many branches you run, which systems we connect to, and how much history you want to keep.

Your proposal includes the monthly platform fee and implementation scope. Branches, service divisions, integrations and the history you need to retain determine the work involved.

Who this is for

Built for operators with more than one yard.

Multi-branch regionals

Several yards and service divisions, with branch permissions and reporting scoped to your operating structure.

Acquirers and roll-ups

You bought a company and inherited its data. We migrate its customers, sites, units and contracts into a new or existing PRO deployment, with the rollout and acceptance checks agreed before cutover.

Outgrowing entry-level tools

Your current system was fine for one truck and a spreadsheet. It struggles with dispatch across counties, custom billing rules, and a controller who needs the numbers to tie.

Running a smaller crew? FieldTracer is built for that, with published pricing and self-serve checkout.

See FieldTracer plans

What happens next

From first call to a signed plan.

1

Discovery call

Thirty minutes. We map your branches, your users, and the systems you run today.

2

Proposal

Platform fee and implementation scope in one document, with the migration plan attached.

3

Go-live plan

Dates for data migration, training and cutover, agreed before anything is signed.

Request a proposal

Tell us about your branches, your team, and the systems you run today. We come back with a scoped proposal.