Cliffhanger Solutions
Get a Demo
Pricing that follows the lane.
No public rate card, and we won't pretend to have one. Every utility's stack and lane are different, so pricing is quoted per deal: module by module, with services and software as separate, visible line items.
Four building blocks. One at a time.
Deals follow the same shape as deployments: prove one bounded lane, then expand when it's earned.
1 · Foundation project
A one-time package that stands up the first lane: workflow discovery and scoping, data-readiness and asset-mapping review, bounded Smallworld-centered integration setup, mobile and offline configuration, training, baseline metric capture, and go-live support. Milestone-based acceptance, agreed up front.
2 · Core software
Recurring software for the Field Ops workbench and the operation of your bounded lane, with standard platform support and reduced-scope contractor access where it applies.
3 · Expansion
When the first lane proves out: Storm Response, additional districts or regions, office-side review surfaces, and additional connector work, each priced as its own package.
4 · Higher-touch support
Optional: sync monitoring, exception triage, release and change coordination, and managed expansion support for teams that want us closer to the wheel.
Rules we hold ourselves to.
Module-by-module pricing. Implementation services itemized separately, never buried in a lump sum. Milestone-based acceptance language. Clear boundaries on what triggers a change order. Pilots are paid and production-intent: the first lane is one you keep, not a throwaway proof of concept.
Get a quote shaped to your lane.
One bounded lane: one district or circuit, one crew program. Your data and your systems, a baseline captured on day one, and gains you can measure in weeks or months. Not years.