The dashboard your business needs, that no platform ships as standard
BigChange runs the operation. JobIQ builds the reporting that sits on top of it, for the parts of your business that are specific to you and were never going to come as a standard feature.
Tailored, brand new, or we find the problem first
Tailor one we have already built
The quickest route. Something close to what you need already exists, and reshaping it to your rules, your customers and your language is a fraction of the work of starting again.
Build a new one from scratch
Nothing close enough? Then we start from the question. Most of what we build has never existed anywhere, because it depends on how your business specifically works.
Work out what you need first
Plenty of people know something is wrong without being able to name it. We look at the data you already hold and come back with what it says, including the awkward parts.
Why these dashboards exist
None of the dashboards on this site began as a product idea. Each one was built because a real field service business could not answer a question, and no standard report was ever going to. We show them because they explain what bespoke means faster than any description.
Installed Base & Replacement
Know which unit needs replacing before the customer does
How much replacement revenue is sitting in the units we have already fitted?
Part & Stock Locator
Find any part, in any van, in seconds
Is that part in another van, and if so which one?
Quotes Outstanding
Every outstanding quote, aged from the day it was sent
Which quotes are going cold, and what were they even for?
Engineer Bonus
Bonus worked out from what actually happened
Can we pay a bonus that people believe, without a day of spreadsheet work?
Connect, calculate, visualise, act
The last one is the line between a report you read and a system that does something.
Five things a dashboard is worth building for
Find the bottleneck
Where work piles up, waits, or goes round twice.
Expose the inefficiency
Work completed and never invoiced. Return visits for a part in another van.
Predict and forecast
Replacement demand from the age of your installed base. Capacity against the pipeline.
Evaluate your people fairly
Performance on real work, and a bonus figure the engineer can check.
Evaluate your customers
Who actually makes you money once travel, rework and payment behaviour are counted.
Sent here by BigChange?
Then you already know what the problem is, which puts you two weeks ahead. BigChange covers the common ground of a field service business thoroughly, and it does it for thousands of companies at once. What no platform can do is anticipate the part of your business that is only yours: the way you price a contract, the way your bonus scheme works, the figure your biggest customer wants in their format.
Nothing gets replaced
You carry on working in BigChange exactly as you do now. We read through the API and, where it is allowed, write back into it.
Your data stays where it is
We are not migrating you anywhere. The platform remains the system of record and the dashboard sits alongside it.
It makes the platform stick
The nuanced question gets answered on top of BigChange rather than in a spreadsheet somebody keeps outside it.
We have solved this for a lot of field service businesses already
Twenty years of building and deploying software, thousands of businesses served, and a long run of work with field service operators specifically. That is why the first conversation is worth half an hour: most of the time we recognise the problem before you have finished describing it.
We know these problems already
The same ones keep turning up. Work completed and never invoiced. Return visits for a part that was in another van. Planned maintenance quietly losing to reactive. You are not explaining your industry to us from scratch.
We have seen how software fails
Two decades of deployments teaches you the build is the easy half. Systems fail because nobody agreed what the number meant, or because the person expected to use it every day was never asked.
Every build is aimed at a number
Before anybody writes code we agree which figure should move: unbilled work recovered, return visits avoided, hours released, quotes converted. The dashboard then reports on that figure too, so the return is something you can check rather than something we claim.
What that means in practice
| No pilot theatre | You see it on your own data early, not on a demo dataset |
| Built for the reluctant | The person who has to use it daily was probably not asked last time. We ask them |
| Built to last | Plain web pages and one database, so it still works in five years |
| Payback in the open | The figure the build is meant to move is on the dashboard, so you can see whether it did |
Start with the free half hour
Tell us the question you cannot answer. If we cannot see a way to help we will say so, which happens often enough to be worth mentioning.