Operating footprint
Number of sites, site location rules, shift blocks, guards, supervisors, and assignments that must be configured.
Pricing
Sentares prepares a scoped proposal after confirming the sites, users, field workflows, management features, and rollout support required.
Commercial model
Scoped quote
Sentares does not publish a fixed per-seat price that ignores site and rollout requirements.
Core scope
Sites + field work
Site configuration, guards, assignments, check-ins, and incidents form the operating baseline.
Optional scope
Enabled by firm
Messaging, clusters, live map, reporting, evidence storage, and audit-chain access can be enabled by configuration.
Scope Areas
These inputs map to configuration and product behavior that exist in the current system.
Number of sites, site location rules, shift blocks, guards, supervisors, and assignments that must be configured.
Clock-in, patrol, clock-out, incident evidence, offline handling, and location-policy requirements in scope.
Incident review, messaging, live-map visibility, management reports, and audit access required by authorized roles.
Organization setup, invitations, site configuration, policy review, supervised verification, and operating-team support.
Evaluation
A short operational description is enough to begin. Detailed tenant data, credentials, or incident evidence should not be submitted through the public contact form.
Proposal
The commercial proposal should make product scope, implementation work, and terms explicit.
The proposal identifies the firm features and operational workflows that will be enabled.
The proposal separates product access from one-time configuration, onboarding, and rollout work.
Recurring fees, implementation fees, term, and any separately scoped work are stated before approval.
Evaluation
Tell us about the sites, field team, reporting obligation, or incident workflow you are evaluating. We will keep the conversation specific.
Request a demo