Technical Service Management Software
For firms that service what they sell. One record from the call to the invoice, written by the engineer who was there.
What a Service System Has to Do
A service business is a chain of handovers. Everything below is about the places where the chain usually breaks.
One Record per Job, From Call to Invoice
The call comes in, the job is opened, an engineer is assigned, parts and hours go on it, the customer signs. One record carries all of it instead of a notebook, a WhatsApp thread and a handwritten slip.
Engineers Who Work From the Phone
The job list, the address, what the machine is and what was done to it last time, in the engineer's hand before they knock on the door. The report is written there rather than typed up that evening.
The Machine's Whole History
Every visit, every part, every fault on that serial number in one place. The engineer walking in knows what the last three people did, which is usually the difference between one visit and three.
Warranty Decided by the System
Whether a job is covered is a question of sale date, model and contract, not of who is asked. The system answers it when the job is opened, so the argument never reaches the invoice.
Parts Leaving the Van Are Counted
The part fitted on site comes out of the engineer's van stock, not out of thin air. What they carry, what they used and what needs replacing is a record rather than a monthly guess.
Contracts That Remind You
Periodic service under a contract has a date, and a date nobody is watching gets missed. The system raises the visit before the customer does and before the penalty clause does.
Where Are You Starting From
Both situations are routine for us. Tell us which one applies and we will shape the first call around it.
From First Call to Project Start
The process runs in five steps, in the same order on every project. You can stop after any of them.
Short Phone Call
15 MinutesYou outline what you service, how a job reaches you and who goes out. We ask a few questions and tell you whether this is a job worth doing. If a ready-made product already covers it, you hear that on the same call.
Technical Review
45-60 MinutesWe go through the detail together. How jobs are recorded today, what the engineers carry, which accounting program you use, how warranty is decided and who logs in.
Scope Preparation
Before Any CommitmentYou receive a document that states what will be built, in what order, on what timeline, and at what cost. You read it before anyone signs anything.
Agreement Signing
One DocumentThe agreed scope becomes a signed contract. The confidentiality and intellectual property terms are set out in the same document, rather than in a separate one or at a later stage.
Project Start
Same MonthWork starts and we deliver at regular intervals. A preview environment goes up within the first week, so you follow progress in the application itself rather than in a status report.
Start with a Call
What You Get From It
You do not need the technical side to judge this. Here is what changes on the business side.
The Office Stops Chasing Engineers
What happened on a job arrives when the job closes rather than when someone rings to ask. The afternoon that went into collecting reports goes somewhere else.
Jobs Get Invoiced
Work that was done, parts that were fitted and hours that were spent stop falling through the gap between the van and the accounts. What was earned is what gets billed.
You Can See Which Jobs Lose Money
Which customer, which model, which engineer, which contract. When every job carries its own parts and hours, the unprofitable ones stop hiding inside the average.
Fewer Second Visits
An engineer who arrives knowing the history and carrying the right part finishes it the first time. The second visit is the most expensive thing in this business and it is mostly avoidable.
Customers Stop Ringing to Ask
Where is the engineer, is the part in, what is this going to cost. When the customer can see the job, your office answers that once instead of all day.
The Business Stops Living in One Head
Which machine belongs to whom, what was done to it and what it is owed. When that is written down rather than remembered, the person who knows can take a holiday.
Choosing the Firm That Builds It
The questions to put to anyone who offers this work, and the commitments we make on each of them.
We Start With the Engineer, Not the Office
A system the field does not use produces nothing for the office. We design the phone screen first and let the back office follow from what the engineer can realistically type on a job.
We Say When You Do Not Need This
With two engineers and a shared calendar, a system costs more than it returns. We would rather say that on the first call than sell it.
It Connects to the Accounting You Have
Invoices and stock live in the program you already run. We connect to it rather than asking you to move, and we check during the review that the connection is possible.
Scope Before Signature
You know the scope, the timeline and the price before you commit. We would rather lose the project at the scoping stage than argue about what was included halfway through it.
Code Ownership in Writing
Who owns the code, and whether we may name the work as a reference, are both settled in the contract before the first line is written.
You Keep the Keys
The server, the domain and the data stay in your name. We work with access you grant and can withdraw, so leaving us never means losing the service history.
Our Development Technologies
We create modern solutions using cutting-edge technologies
Next.js
Production-grade React applications with SSR
Laravel
Elegant PHP framework for web artisans
React
Building interactive and responsive user interfaces
PostgreSQL
Relational database design, migration and tuning
MongoDB
Document database modelling and aggregation pipelines
PHP
Custom applications and legacy system modernisation
Node.js
Server-side JavaScript for scalable applications
Python
Backend development and data processing solutions
Vue.js
Progressive JavaScript framework for modern web UIs
TypeScript
Type-safe JavaScript for enterprise applications
JavaScript
Modern web development with React, Next.js, and Node.js
Tailwind CSS
Modern utility-first CSS framework
Frequently Asked Questions
A service business loses money in the gaps rather than in the work. Between the call and the engineer, between the engineer and the invoice, between what was fitted and what was counted. Each gap is somebody remembering to pass something on, and each one is where a job quietly stops being profitable.
Which system you need depends on what the business does either side of the service work. Where you also sell the parts you fit, the catalogue belongs with spare parts software and the two share it. Where the machines are your own and the work is planned rather than called in, that is maintenance management instead. Which of those your project really is becomes clear on the first call.
A Fifteen-Minute Call Is Enough to Start
Tell us how a job reaches you and who goes out. If a ready-made product already covers it, you will hear that on the first call.
Technical Service Services by City
Find our Technical Service services in 150+ locations
We reply the same working day