How this runs
We built the software this runs on.
PH7 Mobility does not run on spreadsheets and phone calls. The scheduling that places every job, the app the worker carries, the app the customer books on and the payments underneath them are all ours — built, running, and in use on real work today. It is the connective tissue between the verticals.
Why it matters
The difference between busy and bigger.
A field-service business does not usually fail at the work. It fails at the coordination around the work — who was supposed to go where, whether they went, whether the customer was told, and whether the invoice matches what happened.
Every one of those is a person’s job until somebody builds software for it. That is the cost that grows fastest and shows up last, and it is why an operations company with its own systems is a different proposition from one with the same crews and a spreadsheet. We built ours because the model we sell — a workforce and a vehicle as one managed unit — is only affordable if the coordination is automatic.
What we built
Four systems, one operation.
01
Optimised scheduling
Every job has to land on a day, in a slot, with a worker who can actually get there. Done by hand it is a morning’s work that gets worse as the business grows, and it is the reason most field operations stop scaling at the size of one coordinator. Ours is decided by software, which is why adding customers does not mean adding planners.
02
The worker app
Each worker opens a phone and sees their day: where to go, in what order, what the visit needs, and what to record when it is done. Instructions stop travelling by phone call, and the day stops depending on somebody remembering to pass them on.
03
The customer app
Customers book, see what is scheduled, follow the visit and keep the history — including the proof that each visit happened. Nearly every support call a service business takes is somebody asking whether anyone is coming; this is the answer to that question, given before it is asked.
04
Payments
One-time payments and recurring subscriptions run inside the same system that holds the schedule. What was done and what was charged are one record rather than two that have to be reconciled, which is where money quietly goes missing in an operations business.
Two apps
One for the worker. One for the customer.
The worker’s phone holds the day: the visits in order, the route between them, and what to record at each. The customer’s phone holds the booking: the day it is scheduled for, the confirmation, and the proof afterwards that it happened.
Both talk to the same schedule, so the question that generates most of a service company’s support calls — is anyone coming? — is answered on a screen before it is asked.
Not slideware
You can go and use it.
Software described on a pitch deck and software that runs are different things, and nobody evaluating a company should have to take the difference on trust. The customer side of all of this is public: booking, scheduling, tracking and payment are live on ph7autocare.com, taking real bookings from real customers.
The internal side — the scheduling console and the worker app — is not shown on this site and is not screenshotted anywhere on it. Those screens contain real customers, real addresses and real workers, and a marketing page is not where any of that belongs. We will walk anyone with a reason to see it through a live demonstration instead.
Technical diligence
Ask to see it running.
Investors, partners and franchise prospects can see the scheduling engine and the worker app running, on a call, against a real day of work.