Custom software
Systems built for how your business actually runs, replacing the spreadsheets and workarounds holding it together.
How it worksAll industries
Services and delivery
The contract promises a response time nobody measures.
Service contracts, technician scheduling, response and resolution against SLA, spares at van and site level, and warranty against serial history.
Where the standard system leaves the cost in place.
Service and maintenance businesses sell an undertaking: that someone competent will arrive within a stated time, carrying the right part, and that the machine will work afterwards. Almost every fact that proves it happens away from the office, in a van or on a customer's floor, and reaches the system as a job card handed in days later. So renewals are negotiated without knowing whether the last contract was honoured, and the spares that decide whether a visit succeeds are wherever a technician last put them. Each of these ends as either a breached obligation, a second visit at your cost, or a renewal priced on guesswork.
- Contract entitlements, covered equipment, and response commitments live in signed documents nobody reads before dispatching a technician.
- Jobs are allocated by phone based on who is thought to be nearby, without reference to skill, certification, or what is already on their route.
- Response and resolution times are recorded on a job card and filed, so SLA performance is asserted at renewal rather than reported.
- Spares in vans and at customer sites are not stock in any system, so a visit fails for want of a part that was in another technician's boot.
- Whether work is covered by contract, covered by warranty, or chargeable is decided at the invoice stage, weeks after the customer formed their own view.
Built for field service and maintenance.
Built on the same core our products run on, extended with the records and rules this sector is actually judged against. These are scopes we build and integrate, not shelf modules with a licence key.
Contracts and covered equipment
Service contracts with the specific assets they cover, entitlements, inclusions and exclusions, response and resolution commitments, and renewal dates, held against the customer rather than in a signed PDF.
Scheduling and dispatch
Jobs assigned against skill, certification, location, and the technician's existing route, with the day's schedule visible to everyone who is going to be asked about it.
Mobile job execution
Job cards completed at the site on a phone, including readings, parts consumed, photographs, and customer sign-off, built to work with no signal and reconcile when there is one. Anything less becomes deferred data entry from paper, which is where field records quietly stop being contemporaneous.
SLA measurement
Response and resolution measured from the entitlement that applied, per job and per contract, with breaches surfaced while they can still be escalated rather than counted afterwards.
Van and site spares
Every van and customer store treated as a stock location with its own balance, consumption booked to the job that used it, and replenishment driven by what the fleet actually consumed.
Warranty, serials and billing
Serialised equipment carrying its full service history, so warranty and contract coverage are determined by the system at the point of the visit, and chargeable work is invoiced from the job rather than reconstructed later.
What it has to be able to prove.
Compliance fails when it is a parallel activity. These obligations are carried by the system that runs the operation, so the evidence exists because of how work was recorded rather than because someone assembled it afterwards.
Contractual obligation evidence
Entitlement, response time, resolution, parts fitted, and customer acceptance retained against each job, which is the evidence a penalty claim or a renewal negotiation turns on.
Technician competence and safety records
Certifications, licences, and expiry dates held against the person, and permit-to-work or safety sign-off captured where the site demands it, so an uncertified technician cannot be dispatched to work that requires one.
Parts movement documentation
Spares moving to vans, to sites, and back generate the statutory movement and invoicing records they need, so a boot full of stock is not an undocumented inventory.
What it runs on.
The sector layer is built. The operational core underneath it is not a proposal: it is running in production with clients today.
ERPMachERPLiveContracts, scheduling, job execution, service billing, and finance, extended with the entitlement and SLA structures a service obligation has to be measured against.See what it does
SIMSMach SIMSLive with clientsSpares as real stock across stores, vans, and customer locations, with serial and batch traceability and the movement history warranty claims are settled from.See what it does
What it returns.
First-visit fix stops depending on luck
The part needed for a job is known to be in a specific van before the technician is dispatched to it.
SLA performance becomes a number you can show
Response and resolution are measured against the entitlement that applied, so renewals are argued from a report rather than from impressions.
Coverage decided at the visit, not the invoice
Contract and warranty status is resolved while the technician is on site, which removes most billing disputes before they start.
Where this normally starts.
Which of these applies depends on how well the constraint is already understood. A review that finds the real one usually turns into a build.
Process automation
Removing the approvals, handoffs, follow-ups, and reconciliation that quietly consume your team's week.
How it worksQuestions we actually get asked.
Our technicians work in basements and remote sites with no signal.
Then the mobile capture has to work offline, and it does. Job cards, readings, photographs, and sign-off are stored on the device and reconciled when a connection returns. The alternative, which is what most operations run today, is transcription from paper at the end of the week, and that is where the traceability is actually lost.
Can van stock genuinely be tracked without the technicians hating it?
Yes, because consumption is booked as part of closing the job rather than as a separate stock transaction. The technician records the part they fitted, which they have to do anyway for the customer, and the van balance follows from that. Nobody is asked to run a stock take in a car park.
We do both contract work and one-off calls. Is that a problem?
No, and mixing them is the normal case. What matters is that the system decides coverage from the contract and the equipment rather than leaving it to whoever raises the invoice, because the difference between covered and chargeable is where the margin and most of the customer friction sit.