Field Service
The field app your people run their day on
An offline-first native app for franchisees and engineers who work out of a van, assembled from accelerator modules that already run in production. Scheduling, quoting, doorstep payments, and job evidence, joined to a franchise layer, and owned by you.
Scheduling, payments, and the franchise layer are production modules, not prototypes. You assemble a platform, you do not gamble on one.
A native React Native app that keeps working with no signal and reconciles cleanly on reconnect. Built for the doorstep, not the desk.
A perpetual source code licence, no per-engineer or per-franchisee fees, and full control of the roadmap and the data.
Three production modules, joined for the field
The hardest parts of a field service platform are solved problems in Talk Think Do accelerators. The field app puts them in the hand of the person doing the work.
Scheduling that never double-books
Recurring schedules, per-occurrence capacity, and serialised capacity checks are proven in the Booking Engine. The same concurrency design underpins job allocation across a field team.
Payments and refunds done properly
Card and online payments, invoices and receipts, and full or partial refunds with over-refund protection are proven in the Billing Engine, with an event-sourced audit trail throughout.
A franchise layer that reconciles itself
A franchisor, franchisee, and site ownership chain, with permissions enforced in the API and every charge attributed to its territory, is proven in the Franchising module.
The full evidence, mapped component by component to live case studies and modules, is on the field service app development page.
Built for the van, not the desk
What we add on top of the proven modules: a native app designed around the realities of working at an address, offline, and getting paid on the spot.
Offline-first by design
The native app reads and writes on-device, queues every action, and syncs on reconnect. Signal in a basement or a rural notspot is not a prerequisite for getting work done.
Native, not a wrapped website
React Native with native modules for camera, card readers, and location, so the app feels like a tool built for the job rather than a browser tab in disguise.
Head office and the field agree
Every completed job, payment, and photo lands against the same record. There is no paperwork to key in later and no reconciliation between the van and the office.
Capabilities in depth
Feature-by-feature detail for evaluators: what each capability does, how it is designed, and the edge cases that decide whether a field app survives contact with a real day.
Job scheduling and routing for field teams
How a field service app plans an engineer's day: territory rules, drive-time ordering, live reassignment, and allocation that cannot double-book, built on proven Booking Engine concurrency.
Quotes and doorstep payments in a field app
How a field app quotes and takes payment at the door: a guided quote wizard, deposit capture, card-present payment, and refunds, on the proven Billing Engine.
Job evidence and compliance capture on site
How a field app captures proof of completion: before-and-after photos, signatures, health and safety forms, and disclaimers, tied to a tamper-evident audit trail.
Offline sync: how a field app works without signal
The engineering behind an offline-first field app: on-device storage, queue-and-forward, conflict resolution, and idempotent sync, so no job data is lost when the connection drops.
Native app, Azure platform, owned by you
The field layer is React Native; the platform behind it is the same .NET on Azure foundation that powers every accelerator module.
React Native
One codebase for iOS and Android, with native modules for camera, card readers, and location, and offline-first storage.
.NET on Azure
C# and .NET on Microsoft Azure. ISO 27001 certified, Cyber Essentials Plus accredited, scaling from a few vans to a national network.
Idempotent by design
Payments and job completions carry idempotency keys, so a retried sync never double-charges or double-books.
Full audit trail
Every job, payment, and evidence capture is recorded with actor, timestamp, and location, event-sourced where it matters.
Part of a connected platform
The Field Service accelerator draws on the same modules that power multi-site and franchise operators, so the field app and head office run on one system.
Booking Engine
Real-time scheduling, capacity, and the serialised concurrency that stops two people claiming the same slot.
Billing Engine
Payments, invoices, and refunds with over-refund protection and a full financial audit trail.
Franchising
The franchisor, franchisee, and site hierarchy, scoped permissions, and per-territory attribution.
Frequently asked questions
Is the Field Service accelerator a single off-the-shelf product?
No. It is a capability assembled from proven accelerator modules (Booking, Billing, and Franchising) plus a native, offline-first field app built for your workflows. Every component runs in production today, so you get an owned platform without building each piece from scratch. We adapt and join them to how your network actually operates.
How does an offline field app avoid two engineers taking the same job?
Job allocation uses the same serialised, per-record capacity design proven in the Booking Engine, where two people cannot claim the last place. When work happens offline, actions are queued and reconciled on reconnect against a clear conflict rule, so a job accepted on a dropped connection resolves to one owner, not two. The offline sync page sets out exactly how.
What happens if a payment succeeds but the sync fails?
The payment is the source of truth, not the sync. A card-present or online payment is confirmed with the provider and recorded locally with an idempotency key. When the device reconnects, that record reconciles to the server without ever taking the money twice, and a replayed sync returns the existing result. This is the same guarded, idempotent pattern used across the Billing Engine.
Do we own the code, or is this another per-seat subscription?
You own it. You hold the source code, the intellectual property, and the Azure subscription, with a perpetual licence to the underlying accelerator modules. There are no per-engineer or per-franchisee fees, so cost does not climb as your network grows. See the franchise platform cost calculator for the economics.
What is the technology behind it?
A React Native app for iOS and Android, backed by a C# and .NET platform on Microsoft Azure. Talk Think Do is ISO 27001 certified and a Microsoft Solutions Partner. Delivery is AI-augmented, running 40 to 50% faster than a traditional team, measured and published in our AI Velocity Report.
See a field service build against your own jobs
Book a consultation and we will walk the proven components, map them to a typical job in your network, and show you what an owned, offline-first field app would involve.
Book a demoor call 01202 006729