When the job history lives in five places
A service desk may record a device in a spreadsheet, send updates through messages and leave the diagnosis in a technician’s notebook. The next person cannot reliably see what was agreed or what happens next. For installation teams, an old site drawing creates a similar problem: the device on the wall no longer matches the record.
The useful starting point is an agreed workflow: intake, assignment, status, completion and a customer-facing update where appropriate. We identify required fields, who can change them and the history worth retaining. A focused system should make the next action visible without requiring every technician to learn an oversized platform.
Three existing projects to inspect
Serviz is an online repair-shop application with customer records, service tickets, statuses, printable QR/PIN intake receipts and a customer status page. It demonstrates a connected repair workflow rather than a collection of disconnected forms.
Plan addresses a different task: browser-based network and security layouts, devices and cables, camera viewing cones, device history and PNG/PDF export. SelectIT Remote is a Windows application with an Android companion for remote viewing and control after access approval, including chat and file transfer. These are examples you can inspect; they are not a promise that all their capabilities fit one starting-price package.
Start with one workflow, then extend it
A custom web-app MVP starts from €2,490. The written scope defines screens, roles, data and acceptance examples. An intake-to-completion workflow can be a first stage; inventory, payments, integrations or advanced reporting can follow after the core process works.
Migrating old records, device integrations, hosting, SMS, payment fees and ongoing maintenance are specified separately. Remote support also needs explicit access and permission handling. A planning tool records a design; it does not replace the installer’s assessment or a site inspection.
What to send for a useful estimate
Describe one typical job from first contact to completion. Include a blank intake form or anonymised spreadsheet, the roles involved, the number of sites or teams and the systems that must exchange data. Say what currently causes duplicate work, uncertainty or repeated calls.
We agree sample jobs and expected outcomes before implementation. Acceptance can include a ticket changing status, a restricted user seeing only permitted records and an export matching the agreed fields. Testing must also cover incomplete input and a failed external connection where relevant.
Practical questions
Can you adapt an existing workflow instead of replacing everything?
Yes. We first inspect the current system and available access. A targeted fix, export or integration may be enough; a rebuild is scoped only when the existing setup cannot support the agreed task.
Will technicians and customers have the same access?
Not necessarily. Staff roles and a limited customer view can be specified separately. The quote states what each role can view or change and how we will verify those boundaries.
Are the linked projects proof of a particular business result?
They show implemented functionality you can inspect. No revenue increase, time saving or customer outcome is claimed without supporting evidence from that project.
Discuss your project
Describe the workflow you want to improve. We agree the first version, deliverables and price before development.
Discuss your project