B.01
Sites under management
Number of operational sites — single, regional, national or international footprint.
›COMMERCIALS
Commercial structure
aligned to operational load.
FieldOps is priced against the shape of your operation — command scope, workflow load, accountability surface, integration depth and tenancy — not against a seat count that has no relation to what the system actually carries. Different sites carry different operational shapes; the commercial envelope is set once both sides understand what is actually being deployed.
COMMERCIAL MODELTIEREDTRANSPARENT
›01WHAT THE COMMERCIAL MODEL IS BASED ON
Twelve operational variables.
Not a seat count.
The commercial envelope reflects the operational envelope. These are the variables that actually determine what the system carries — including how much of the operation lives inside the command layer versus in connected systems around it.
B.02
Contract, SOP & audit burden
Distinct client contracts, SOPs and protocol variants the operation must honour — plus the evidentiary depth, retention and chain-of-custody each one carries.
B.03
Shift & role structure
Coverage model — static, rotating, multi-shift, 24/7 — and the roles (Guard, Dispatcher, Supervisor, Manager, Client) running in parallel on each cycle.
B.04
Live workflow load
Number of live workflows in scope and the inbound operational signal they carry — alarms, calls, field events, client-portal messages, patrols, tasks.
B.05
Client portal scope
Number of clients with scoped access, the depth of their visibility and the evidence classes they may release.
B.06
Tenancy model
Cloud, private or on-premise — selected against jurisdiction, procurement and contractual constraints.
B.07
Integration complexity
Identity, HR, alarm receivers, client systems, insurance and regulatory endpoints bound into the operation.
B.08
Deployment shape
Number of stages and sites in the rollout plan, including stewardship cadence and expansion schedule.
B.09
Ecosystem integration depth
Depth and count of third-party systems the deployment must bind into — Microsoft, Google, Twilio, courier providers and comparable operational endpoints.
B.10
Communication workflows
Structured voice and message escalation paths, monitored inbox flows and two-way messaging volume carried on the command layer.
B.11
Adjacent operational surfaces
Visitor, tenant, parcel and key-control flows deployed alongside the core command layer on a given contract.
B.12
Shared-system dependencies
Calendar, inbox and directory dependencies carried by Microsoft or Google ecosystems on site, and the coordination they must absorb.
Reading the drivers. Role complexity sits in B.03. The number of live workflows in scope sits in B.04. Reporting and audit burden is carried by B.02 (contract and evidentiary depth) and B.05 (client-facing visibility). Integration depth spans B.07 and B.09. Nothing on this page is licensed per seat; every variable above is scoped once, then reflected in the commercial envelope.
›02THREE COMMERCIAL PROFILES
Three shapes of deployment,
one engagement model.
P.01 · Operator
Single-operator deployment
A guarding, facility or industrial operator running FieldOps as the authoritative system of record across their own sites and contracts.
- For
- Guarding and facility operators with one to thirty sites
- Typical scope
- Single operator, one or two client tiers, standardised protocols
- Deployment shape
- Cloud or private tenancy, single-tenant billing, stewardship quarterly
P.02 · Enterprise
Multi-site enterprise
Operators running thirty or more sites, multi-region, with client-specific SOP variants, audit export at scale and consolidated client visibility.
- For
- Enterprise operators with multi-region footprint and client-scale auditability obligations
- Typical scope
- Thirty-plus sites, multi-region, SOP variants per client, cross-site drift review
- Deployment shape
- Private tenancy, multi-wave rollout, stewardship monthly, named operational owner
P.03 · Sovereign
Sovereign / on-premise
Regulated environments — public sector, defence-adjacent, critical infrastructure — where residency, air-gap and sovereignty are contractual constraints.
- For
- Regulated operators with in-country residency or sovereign-infrastructure requirements
- Typical scope
- Dedicated infrastructure, air-gapped where required, custom identity and compliance stack
- Deployment shape
- On-premise or sovereign-cloud, dedicated stewardship, annual third-party review
›03CORE DEPLOYMENT vs EXTENDED SCOPE
Two shapes of scope.
One commercial model.
Every deployment begins with the same core — the command layer and the operational record it holds. What differs is how far the scope reaches around that core: additional operational surfaces, connected systems, integrations into tools the site already runs on. Not every operation needs the extended layer — which is precisely why a flat price list cannot do justice to either kind.
Core deployment · ›03.A
- Command layer — the authoritative system of record for field operations
- Shifts and handovers — reconciled, evidenced, non-improvised
- Patrols — scheduled, ad-hoc and exception-driven, with trace
- Incidents — intake, classification, escalation and closure on protocol
- Tasks — issued, executed and evidenced against role and contract
- Reporting — operational, managerial and contractual in one spine
- Evidence — retained, exportable, admissible where the contract requires it
- Client visibility — scoped portal access where contractually required
Extended scope · ›03.B
- Additional operational surfaces — visitor, tenant, parcel and key-control flows deployed alongside the core
- Site-specific workflow layers — bespoke protocols that extend the core for a given contract or sector
- Connected systems — Microsoft or Google ecosystem integration, identity providers, directory sync
- Communication integrations — Twilio voice, two-way messaging and structured escalation paths
- Parcel and logistics flows — DHL, UPS, FedEx workflows where reception handles shipping on site
- Visitor, key and alarm flows — when they are part of the site’s operational envelope, not an afterthought
A five-site facility running the core on its own and a forty-site multi-region operator running the core plus six connected systems share a category — not a commercial envelope. The shape of scope is what the commercial model actually reflects.
›04WHAT IS INCLUDED IN EVERY ENGAGEMENT
No engagement begins
without these six.
Included regardless of profile. This is what makes an engagement a deployment rather than a software purchase. A deployment with more connected systems and operational surfaces takes a different shape than a clean core deployment — and carries a different commercial profile.
Included · ›04
- Operational assessment — twenty-minute fit conversation followed by a scoped written recommendation
- Deployment scoping — sites, roles, shift patterns, signal sources and protocol variants documented in writing
- Protocol configuration — versioned protocols per client, site and sector, agreed before configuration begins
- Role model setup — Guard, Supervisor, Dispatcher, Manager, Client provisioned against your identity provider
- Training and pilot support — supervisor and dispatch onboarding, pilot observation, reconciled evidence
- Baseline operational review — documented pre-pilot baseline and post-pilot delta against agreed metrics
Expanding scope · ›05
- Large site count — thirty-plus sites across multiple regions or jurisdictions
- High SOP variance — client-specific protocols, sector-specific variants, regulatory overlays
- Multi-role operations on a single site — Guards, Dispatchers, Supervisors and Client visibility operated in parallel
- Regulated evidence — legally or contractually required retention, audit and chain-of-custody obligations
- Custom client-facing reporting — bespoke output formats, cadences and release controls per client tier
- Private or on-premise tenancy — dedicated infrastructure, residency constraints, air-gap requirements
- Custom integrations — identity providers, alarm receivers, client systems, HR and compliance endpoints
- Extended client access — scoped portal access for multiple client tiers, with evidence release controls
- Microsoft or Google ecosystem integration — monitored inboxes, calendars and directory touch-points carrying site coordination
- Shared inbox and calendar dependencies — when site coordination already lives inside the client’s own Microsoft or Google workspace
- Parcel-provider integration — DHL, UPS or FedEx workflows where reception handles shipping as part of site operations
- Communication layer — Twilio voice and two-way messaging paths where the operation requires direct escalation
- Multiple connected operational surfaces beyond the command core — visitor, tenant, parcel and key-control flows deployed together
›06INDICATIVE COMMERCIAL ENVELOPE
What it indicatively costs,
before it is scoped.
We do not publish a flat per-line price list — a five-site reception desk and a forty-site multi-region operation do not share an envelope, and a number that needs a footnote on every line is not a price. What we can publish is the indicative band a single site sits in, and the few things that move it.
$80 per site / month
$450 per site / month
Reception-only — core command layer running light
Full command layer — extended scope, connected systems, evidence at depth
Indicative band, not a quote · every deployment is scoped before priced
›07PARTNERSHIPS
Three partnership lanes.
Each opens a contact channel.
P.01 · Strategic operators
Strategic operator partnerships
Enterprise operators using FieldOps as the operational backbone for their own client base — joint deployment planning, roadmap input and co-development on sector-specific protocols.
Open this lane →P.02 · Implementation partners
Implementation partners
Operational and security consultancies delivering FieldOps deployments under our protocol discipline — certification, joint engagement and recurring stewardship.
Open this lane →P.03 · Regional deployment
Regional deployment partners
Regional partners providing deployment, training and stewardship capacity in jurisdictions where local presence, language or residency are material.
Open this lane →›08WHAT THE OPERATIONAL ASSESSMENT DETERMINES
The assessment maps the operation
before either side proposes anything.
An operational assessment is not a sales call. It is a short, disciplined mapping of what the operation actually carries — the shape from which both deployment plan and commercial profile are then derived. It has a written output, regardless of whether FieldOps turns out to be the right answer.
Operational shape · mapped
- Scope of workflows — which workflows are live today, which are critical, which are drifting
- Role structure on site — which roles run in parallel on each cycle, where accountability lives
- Operational surfaces in scope — command core alone, or extended by visitor, parcel, key, alarm flows
Deployment & commercial shape · proposed
- Integration dependencies — Microsoft, Google, Twilio, parcel providers, identity stack
- Deployment profile — cloud, private or sovereign tenancy, phased rollout where needed
- Commercial profile — the envelope in which the above is then priced, once, in writing
NEXT STEP
Pricing is the last step,
not the first.
Twenty minutes is enough to establish the shape of the engagement — before either side proposes a number.
›FAQPRICING QUESTIONS
What buyers ask
about the commercials.
How is FieldOps priced?
FieldOps is priced against the shape of the operation — its sites, signal load and evidence obligations — not against seats. The indicative recurring band runs from about USD 80 per site / month for light sites to ~450 for full-scope sites. Every deployment is scoped before it is priced.
Is there an onboarding fee?
There is an optional one-time onboarding fee from USD 2,000, scaled to the size of the site and the depth of training. It is strongly recommended but not mandatory — and we can certify a trainer at your organisation so you can onboard further guards and configure additional sites yourselves.
Can we deploy just one site?
Yes. We are happy to deploy a single site per client. Onboarding is optional there too — such clients can configure the site themselves — though guided onboarding is still recommended for a clean start.
Do you offer volume discounts?
Yes. Larger estates — roughly 30 sites and up — are profiled down. The exact reduction is individual and agreed up front as part of scoping.
How much does dedicated or sovereign infrastructure cost?
Dedicated, on-premise and sovereign deployments are priced individually, because the cost depends on the infrastructure and isolation level you require. We agree the commercial shape with you before any commitment.
Why don't you publish a flat price list?
Because a guarding operation with a single reception desk and a 24/7 multi-site contract with strict SLA reporting are not the same product to run. A flat list would either overcharge the simple case or under-serve the complex one. We scope first, then price against the operation.