Fieldforce

$10B+

assets managed

50%

faster deployment

75%

higher quality

50%

better efficiency

As published on getfieldforce.com, 2023.

Software that shows screens is being replaced. Software that holds the record is not.

Deployment and operations still run on spreadsheets, email threads, vendor portals and tools that each hold part of the truth.

Agents cannot act on a record that does not exist. The companies that benefit from AI first will be the ones whose infrastructure is recorded, reconciled and governed in one place.

That is what Fieldforce is for.

A lattice telecom tower with antennas, against an overcast sky
Annotations illustrative · Photograph: Farhan Adriyansyah, Unsplash

The record is organised the way infrastructure is built.

Interface sketches · illustrative

  1. 01

    Projects and deployment

    Plans from templates, dependencies and approvals; acquisition, permits, construction surveys, close-out packages.

  2. 02

    Sites, leases and permits

    Every location with its history; lease builder, abstraction, escalations, renewals; permits with expiry; GIS.

  3. 03

    Assets and inventory

    Assets by serial number from warehouse to truck to site; barcode capture; repair and return; reconciliation to the fixed asset register.

  4. 04

    Field operations and maintenance

    Work orders and queues; preventive and corrective maintenance from the asset record; site access, dispatch, timesheets; mobile app with offline mode.

  5. 05

    Tenant billing

    Charges derived from what is recorded on the site, reconciled technically and financially, posted to SAP.

  6. 06

    Analytics and reporting

    Dashboards by role, custom reports, SQL access to the record, scheduled distribution; Athena Insight for plain-language questions.

  7. Mobile app for the field, with offline mode, on iOS and Android.

    Platform page →

The ERP records the money. Fieldforce records the site. They stay reconciled.

Fieldforce integrates with SAP and Oracle for fixed assets, purchase orders and invoicing; with procurement systems such as Coupa; with remote management systems and the NOC for alarms, power and site telemetry; and with enterprise identity through single sign-on.

Integrations are one-way where they should be. Fieldforce reads from your financial systems of record and writes back only where you authorise it.

Integrations page →

The recordsites · assets · leases · work orders · crews · chargesevery change: timestamp · actor · justification
  • SAPInvoices and billing documents out · master data in⇄ Out and in
  • OracleFixed asset register · reconciliation⇄ Two-way
  • CoupaApproved requisitions and purchase orders · read-only→ Into the record
  • Remote management systemsAlarms, power and site telemetry · raised as work orders→ Into the record
  • OSS, NOC and EMSInventory, faults, performance, tickets⇄ Two-way, by configuration
  • IdentityOkta, OIDC, OAuth 2.0 · the same identity on every action, AI included→ Into the record

→ one-way into the record← one-way out of the record⇄ two-way, by configurationAlso: BI and data (dashboards, warehouses, CSV ⇄) · API and MCP (REST, MCP connector for AI assistants ⇄)

Rooftops crowded with satellite dishes and antennas

Rooftop dishes and antennas, Kyiv · Photograph: Nadin Nandin, Unsplash

In production, on customer data.

  • Crusoe
  • Enfrashare
  • GTA
  • Kelly Telecom
  • DISH Network
  • VEON
  • Teleworld Solutions
  • SmartSky Networks
  • Zain
  • NEOM
  • Jazz
  • Net1 Indonesia
  • New Sun Road
  • Hybrico

Configured on your data, in weeks, not quarters.

  1. 01Diagnostic

    Workflows, data sources and integrations mapped.

  2. 02Configuration

    Templates, approvals and the data model on your real data.

  3. 03First release

    One workflow live with its integrations.

  4. 04Scale

    Further workflows, billing and agents.

Dedicated instance per customer. No underlying platform licence.