Pricing shaped by current CMMS and procurement-adjacent signals

Price the controls layer, not the technician seat.

DistrictOps sits between facilities operations and finance. The tiers below are designed to be procurement-friendly, export-first, and right-sized for a district pilot before a district-wide rollout.

PO-friendly pilot invoicing, annual billing options, pilot credit toward rollout, and security review support are available for district buyers.

Export-first setup
No invasive live integrations to start
Least-privilege reviewer access
Sample dashboard + starter kit available
Evaluate

Free

$0
/month

Best for internal evaluation and seeded product tours.

  • 1 workspace, 1 reviewer seat
  • Seeded demo data and guided product tour
  • 1 campus, CSV upload only
  • Basic leak summary and CSV export
Recommended

Pilot

$1,500
/month

Best for 30–90 day district pilot with real exports and weekly reconciliation.

  • Up to 3 campuses and 5 reviewer seats
  • CMMS + ERP + invoice lanes
  • Reviewer-in-the-loop matching
  • Weekly Leak Report and vendor evidence packs
  • Guided onboarding and email support
Custom

District

From $6,000
/month

Best for district-wide rollout, procurement alignment, and controls designed to support audit preparation.

  • District-wide campus coverage
  • Unlimited reviewer roles
  • SFTP intake and policy configuration
  • Exports designed to support audit preparation and reviewer-checked external sharing
  • Priority support and rollout planning

Feature ladder

CapabilityFreePilotDistrict
Single-campus CSV uploadIncludedIncludedIncluded
Reviewer-in-the-loop matchingIncludedIncludedIncluded
Advanced policy packsLockedIncludedIncluded
Multi-campus exportsLockedIncludedIncluded
SFTP automationLockedLockedIncluded

Why these tiers

  • Public CMMS pricing often starts in the mid-teens to mid-double-digits per user per month.
  • School and procurement-adjacent tools frequently shift to quote-led pricing once they touch controls, compliance, or district-wide workflows.
  • DistrictOps should be priced as a reviewer-and-campus control layer, not as a field-tech seat replacement.
  • Research notes and source links are documented in docs/pricing-research.md.

Procurement reassurance

  • Pilot launch can often start from CSV upload or district-managed SFTP, depending on export quality and district review timing.
  • District pilots can be invoiced annually and credited toward district rollout when scope, contracting path, and procurement timing align.
  • Security review support, privacy notes, and export templates are available before kickoff.
  • See the read-only seeded workspace before you request access.

Fixed-scope pilot boundaries

  • One vendor or contractor book in the opening wave.
  • Up to three campuses, five reviewer seats, and a 30–60 day proof window.
  • Success metrics agreed before kickoff: spend leakage found, exception cycle time reduced, and vendor/SLA evidence exported.

Built for the buying unit

  • Economic buyer: CBO / COO / Assistant Superintendent for Finance & Operations.
  • Operational champion: Facilities Director or Maintenance & Operations leader.
  • Power user: AP analyst or business office reviewer who owns the exception trail.