Cliffhanger Solutions
Get a Demo
Pricing that follows the work.
No public rate card, and we won't pretend to have one. Every utility's stack and starting workflow are different, so pricing is quoted per deal: a per-user subscription, a one-time setup per workflow, and 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 workflow, then expand when it's earned.
1 · Foundation project
A one-time package, priced per workflow, that stands up the first one: 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
A per-user subscription for the people running your first workflow, with standard platform support and reduced-scope contractor access where it applies.
3 · Expansion
When the first workflow proves out: Storm Response, additional districts or regions, office-side review surfaces, and additional connector work, each with its own one-time setup while the subscription grows with the users.
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.
Per-user subscription pricing. One-time setup itemized per workflow, 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 workflow is one you keep, not a throwaway proof of concept.
The lines that aren't on the quote.
Most of the cost in a traditional deployment isn't the software; it's everything wrapped around it. A Logos quote leaves these out on purpose.
Data migration
Logos indexes the systems you already run, in place. Nothing moves, so there's no migration workstream to fund before the first crew sees value.
A contractor bench
The foundation project is a scoped package with milestone acceptance agreed up front. There is no open-ended services engagement to staff.
Shelf-ware licenses
The subscription is per user: you pay for the people using it, and the seat count follows the deployment.
Year-two licensing surprises
The stack is open, widely adopted technology. No proprietary database license is buried in the deal, and your data exports in full whenever you ask.
Get a quote shaped to the work.
Describe the workflow. The quote covers a one-time setup and the per-user subscription, and it grows only when the deployment does.