- How does per-organization pricing actually work?
- One annual SaaS fee covers the whole organization. Every staff member, every partner agency user, every executive or elected-official staffer, and every end user. If your case volume or user base doubles next year, the price does not. Implementation is a separate one-time fixed fee. Both numbers are quoted at the engagement stage based on size, integration count, and module scope.
- What happens at the end of the 90-day Pilot Phase?
- You make a call. If the work is meeting expectations, we continue into the full implementation under the signed contract. If it is not, you can invoke the Pilot Risk-Reversal at your sole discretion: we refund 50% of Pilot Phase fees, transition out cleanly within 30 days, and you keep all the work product (configuration, integration code, data conversion, documentation) at no additional cost. The clause exists because we are a newer firm and we want the financial structure to reflect that.
- Which existing systems do you integrate with?
- Anything with a documented REST API or that accepts webhook callbacks. Common integrations across our buyer pool: GIS layers (ESRI ArcGIS Online is first-class), telephony for phone intake, mass-notification platforms, identity providers (Microsoft Entra ID, Okta, Ping), work-order systems (Cityworks, Cartegraph, ServiceNow, others), ERP and finance platforms, knowledge bases, EHR and patient-management systems where applicable, and any internal databases the organization wants to keep authoritative. Where the integration is novel, we scope it during the Pilot Phase.
- How does the change-management practice actually work?
- Three layers run in parallel with the build. (1) Constituent or stakeholder discovery: working sessions with department leads, frontline operators, and field responders to map current workflows and where adoption breaks down. (2) Documentation and training: role-specific training paths, change-impact assessments, and runbooks the client owns. (3) Adoption monitoring: weekly during the Pilot and monthly through go-live, with measured adoption metrics by department or business unit and a written escalation path when adoption stalls. This is the work that determines whether the platform earns its keep, so we include it rather than billing it separately.
- Who owns the data?
- You do. The client owns the data and the data dictionary throughout the engagement and after. We do not retain rights to client data, we do not sell or share it, and we do not use it to train any AI model (vendor or third-party). If you ever decide to take the platform to a different vendor, the open REST API, documented data dictionary, and standard export formats let that happen without our involvement. Architecture portability is contractual, not a marketing claim.