05 / Pricing

Pricing, plainly. Sized to the operation.

KozyOps is built for the 30-to-60-person fuel-and-service operation. Pricing scales with seats across departments, customers under management, depots, and which surfaces you are running. We would rather quote you accurately than publish a tier table that doesn't fit your shop. Card processing through Kozy Payments is at-cost; there's no platform markup on payments, by design.

OPERATION · MULTI-DEPOT

Depot

Quote tailored

For multi-depot operations: two or more loading sites, a fleet past fifteen trucks, or shift-coordinated dispatch coverage.

Everything in Route
Multi-depot dispatch board with depot filtering
Cross-depot driver and truck assignments
Shift-coordinated will-call queue
Both tank-monitor adapters (Otodata + Tank Utility)
Sage Intacct integration (deep)
Standard data-migration assist

Talk to usUSAGE FEES BILLED MONTHLY · NO MINIMUMS

OPERATION · HEADLINE

Route

Quote / month base

The default for most operations on KozyOps. Single depot, two fuels, an HVAC service department on the same trucks, AR team feeding a controller, ~30-to-50 seats, customer book in the 5,000-to-15,000 range.

The full web back office (all modules)
KozyServiceman iOS for every driver and technician
Customer portal, branded for your operation
Per-tenant deployment with your own database
All confirmed integrations (Sage Intacct, QuickBooks, both tank monitors)
Eight-level RBAC with segregation of duties
Record-level audit trails
Kozy Payments at-cost

Request a demo USAGE FEES BILLED MONTHLY · NO MINIMUMS

OPERATION · MULTI-BRAND

Terminal

Quote tailored

For multi-brand or multi-state operations: two or three brands under one operator, a customer book past 25,000, or finance teams consolidating against a parent ledger.

Everything in Depot
Multi-brand account numbering and per-brand portals
Cross-brand consolidated reporting
Per-tenant deploy on dedicated DB and S3
Custom feature flags and custom RBAC realms
White-glove migration from Ignite or other legacy MSSQL
Dedicated ops liaison, SLA on response time
Security audit support (RBAC, audit logs)

Contact salesDEDICATED LIAISON · SLA

No public pricing today — numbers above are placeholder until SME sign-off. The structure is final; the dollar figures will be quoted on a call.

06 / What is in each tier

Capabilities, mapped to the tier they unlock at.

Pricing scales with the platform's load (deliveries, tickets, customers). Capability access is gated by tier so a single-depot operation isn't paying for a multi-brand feature it won't use.

Capability	Route	Depot	Terminal
Dispatch & field
Calendar schedules & will-call queue All intake sources, all zones	●	●	●
Degree-day forecasting Per-customer K-factor, baseload, propane variants	●	●	●
Tank monitoring adapters Otodata, Tank Utility	Both	Both	Both
KozyServiceman iOS (drivers + techs)	●	●	●
Multi-depot dispatch (filtering, cross-depot)	—	●	●
Accounting & AR
QuickBooks export	●	●	●
Sage Intacct integration Invoices, payments, deposits, GL	●	●	●
Payroll PDFs, pay-weeks, clock-events	●	●	●
Kozy Payments (at-cost)	●	●	●
Customer experience
Customer portal Bill pay, tune-up, will-call payment, messaging	●	●	●
Twilio SMS conversations + SES email	●	●	●
OnSIP softphone integration	●	●	●
Vertical & platform
Fuel assistance / LIHEAP module	●	●	●
Multi-brand account numbering + per-brand portals	—	—	●
Dedicated DB + S3 + RBAC realms Per-tenant deploy	Shared cluster	Shared cluster	●
White-glove migration assist For Ignite & other legacy MSSQL	Standard	Standard	White-glove

What’s included

Every KozyOps deployment includes all three surfaces. We don’t split the back office, the iOS app, and the customer portal into separate SKUs. That’s not how the product works.

The full web back office (all modules: dispatch, accounting, service, parts, fuel assistance, communications, platform)
KozyServiceman for iOS, for every driver and technician on your team, both 1099 and W-2 rosters
The customer portal, branded for your operation (per-brand if you run multiple brands)
Per-tenant deployment with your own database
All confirmed integrations on the integrations page
Sage Intacct, QuickBooks, or generic GL adapter, your choice
Tank-monitor connectivity to Otodata and Tank Utility
Twilio SMS, AWS SES email
Eight-level RBAC with segregation of duties enforced server-side
Record-level audit trails

Payments

Card processing through Kozy Payments is run at-cost. We don’t make money on payments. Rates land lower than third-party gateways usually charge because we’re not pricing in a margin. For a mid-market AR team processing hundreds of card transactions a week, the margin matters.

Dealers already on NMI or Qualpay can keep running them, with the usual gateway pricing those providers set.

What’s not in the platform price

The card-processing rates themselves: those are processor passthrough on Kozy Payments and whatever your contract says on NMI or Qualpay.
Twilio SMS / voice usage: pass-through.
One-time onboarding and data migration: quoted per project, based on your legacy system.

Operations under ~1,500 customers

Talk to us; we may grow into you. We don’t list a separate “starter” tier because we’d rather have an honest call than ship you a tier that won’t carry your operation a year from now.

Questions we get on the first call.

If your question isn't here, the easiest route is to book a 30-minute call. We answer pricing questions on the call instead of by email.

Why per-tenant pricing instead of per-seat?

KozyOps is a multi-tenant platform with per-tenant deployment: each dealer gets their own database, their own S3 bucket, their own feature flags. Per-seat pricing punishes dealers who put more drivers and technicians in the field, which is the opposite of what we want to optimize for.

What does "usage fees billed monthly" actually mean?

Above the base, we bill on deliveries logged, service tickets posted, and the number of active customer accounts. The unit rates are small and disclosed up front. Most dealers tell us the bill is predictable to within a few percent month-to-month outside of seasonal swings.

Is payment processing extra?

No. Kozy Payments is at-cost. There is no platform markup on payments, by design.

Can I bring my own payment processor?

Yes. Dealers already on NMI or Qualpay can stay on those gateways. The capability matrix is identical from the office team's point of view; the savings differ.

What does migrating off a legacy MSSQL system cost?

For Route, the migration is standard-assist (we run the schema mapping; you validate). For Depot, same standard-assist. For Terminal, we run a white-glove cutover with a dedicated ops liaison.

What is on the roadmap I should know about before signing?

Mobile signatures, AI Route Generation, AI Ask, cylinder fills, in-field tap-to-pay, and customer/job profitability analytics are all on the public roadmap. They are not in the priced tiers; when they ship, they ship to all tenants on the appropriate tier without a separate SKU.