Dispatcher
Assigns and resequences against real capacity, and sees which commitments are at risk while there is still a morning left to fix them.
One job record, from dispatch to the invoice.
Field work goes wrong between systems: the schedule in one place, the proof in a photo on a phone, the exception in a message thread. The answer is one record all four roles write to.
A practical delivery path
- 01Schedule
- 02Dispatch
- 03Execute
- 04Confirm
- 05Report
Prove it on one team or one region first. A dispatch board nobody trusts does not improve by covering more of the network.
One record the office and the van both write to.
Field service software gives the planner a live view of jobs, people, skills, and capacity; gives the technician the instructions, parts, and forms on site, including where the signal drops; and returns completion, photos, signatures, and exceptions to the same job record. Nothing is re-keyed at the boundary, because there is no boundary—the office and the field read one record through two views.
Signals that a purpose-built system is the right answer.
- 01
The schedule and the day stop matching by mid-morning
Work is assigned on a call or in a spreadsheet without skills, location, priority, or the commitment made to the customer in view. The plan drifts, and only the dispatcher knows by how much.
- 02
The evidence stays on the technician’s phone
Checks, notes, photos, and the customer’s signature are captured in chat or on paper and reach the office separately—by which point the one photo that would settle a dispute is the one nobody took.
- 03
Billing is reconstructed rather than produced
Time, materials, travel, and approved variations are pieced together from three sources at month end, so invoices go out late, short, or with a line the customer can argue about.
The processes this has to carry end to end.
- 01
A day that reschedules itself honestly
An urgent job takes priority by rule and goes to whoever has the skill, the parts, and the travel time to make it—while every job it displaces gets a new window and a customer who was told about it, rather than a silent slip.
- 02
Scheduling, evidence, and invoicing on one job
Pixelity built Wazzan Holding a short-term-rental cleaning operations platform where scheduling respects conflicts, travel, and leave, and completion is evidenced by photo before the job moves into VAT invoicing.
- 03
An exception that becomes work, not a phone call
A locked site or a fault outside scope is recorded against the job with evidence, which opens the follow-up visit, holds the billing line, and puts the case in front of a named coordinator instead of one person’s memory.
Screens from a related demonstration.
Captured from Pixelity's fictional product demonstrations. Organizations, people, and records shown are synthetic.
What the system has to do well to be worth building.
- 01
Dispatch against real constraints
Skills, territories, travel, leave, and the window promised to the customer decide who gets the job—and a reschedule updates everyone it affects.
- 02
Mobile execution that survives a bad signal
Checklists, photos, notes, and parts used captured on site and queued when connectivity drops, so the record is complete whether or not the basement had coverage.
- 03
Evidence attached to the job
Photos, readings, signatures, and timestamps stored against the job they belong to—which is what answers a question about it months later.
- 04
Completion that produces the invoice
Signed work, time, materials, and approved variations become the billing line directly, so what was done and what was charged cannot drift apart.
Different people need different views of the same operation.
Field technician
Works from the job on a phone, records evidence as part of finishing rather than as paperwork afterwards, and flags what falls outside scope.
Service manager
Reads backlog, utilization, repeat visits, and which exceptions keep recurring—usually the signal that the standard job is scoped wrong.
Connections designed around who owns which record.
- 01
CRM or contract system for the customer, asset, and entitlement context that decides what a visit is allowed to cover.
- 02
Inventory or warehouse for parts reservation and van stock, so a job is not dispatched without what it needs.
- 03
Billing or ERP, so a completed job and its invoice are one event rather than two entries.
- 04
Mapping and routing where travel time is a real limit on what the day can hold.
Controls that protect the operation and the data inside it.
- 01
Mobile sign-in and session handling suited to shared devices and personal phones alike.
- 02
Customer detail minimized on the device, encrypted in transit and at rest.
- 03
Photos and signatures written to the job record with tamper-evident linkage, since that is the evidence a dispute turns on.
- 04
Role permissions separating what the field sees from contract, pricing, and financial detail.
Operations Command Center
A fictional operating product holding the same parts: capacity against commitments, the exceptions blocking work, and the reporting above them.
Open the demonstrationRelated concept demonstration
- 01Schedule
- 02Assign
- 03Execute
- 04Exception
- 05Report
Delivered one working workflow at a time, not one long build.
- 01
Map the workflow
Document users, records, decisions, exceptions, integrations, and the smallest release that creates measurable operational value.
- 02
Shape the product
Prototype the real screens, permissions, and rules so stakeholders react to a visible system before engineering scope hardens.
- 03
Build in focused releases
Deliver one dependable workflow at a time with testable data, ownership, and reporting—not a long hidden build cycle.
- 04
Release and evolve
Train users on the live workflow, monitor exceptions and adoption, and extend the platform only when the foundation is stable.
Business situations that often lead here.
Articles that help frame the decision.
Tell us the process everyone works around.
Describe it in a sentence or two. We will come back with what we would build first, what it would take, and whether you actually need us for it.