Build

Bespoke software built around how you actually work

Most businesses end up running on a spreadsheet somebody built years ago, a WhatsApp group and a filing cabinet, and it works until it does not. We build the application that replaces all three: one database behind it, one sign in with the Microsoft 365 accounts you already have, and every person seeing only the part of the business that is theirs, at a desk or out on site. It is custom software development for one business: yours.

What you get

Role based access, by department and level
Role based access control: what each person can see and change is set by their role, not by who they happened to ask. A fitter sees today's jobs, a supervisor the whole week, the office the invoicing and the director the numbers.
Sign in with your Microsoft 365 accounts
Single sign on through Microsoft Entra ID, the sign in system behind Microsoft 365, so your team uses the accounts they already have and nobody gets another password. Turn off a leaver's Microsoft account and they can no longer sign in to this either.
Works on site, even with no signal
Built as a progressive web app, which installs on a phone or tablet like any other app. Field staff record jobs, photos and signatures with no signal, and it all syncs to the office once they are back in coverage.
One database, one version of the truth
A proper relational database replaces the spreadsheets, so a job is one record, entered once, with an audit trail of who changed what and when. Dashboards, reports and exports all read from that one place.
Joined to the software you already run
Integrations through APIs link it to your accounting, payments, calendars and Microsoft 365. Figures move between systems on their own instead of being copied across by hand.
Hosted, backed up and yours
Cloud hosting with backups, and personal data handled so you can meet your UK GDPR obligations. You own the code, the data and the documentation, and you are not renting access to your own operation.

In practice

What this looks like

One record, four roles

  • Job 1042

    Fitter

    On a phone, on site, today

    Site
    Unit 4, Bilston
    Start
    08:00
    Work
    Replace two roller shutters
    Photos
    4 added
    Sign off
    Customer signature

    Cannot see what the job is worth, or the rest of the week

  • Job 1042

    Supervisor

    The week, every crew

    Crew
    Dan and Marek
    On site
    Since 08:12
    This week
    14 jobs, 2 unassigned
    At risk
    One job waiting on parts
    Can change
    Who goes, and when

    Cannot see invoices and payment

  • Job 1042

    Office

    Paperwork and invoicing

    Signed off
    14:40
    Sheets in
    4 of 4
    Order number
    PO-8842
    Invoice
    Ready to raise
    Reminder
    Day 14 if unpaid

    Cannot see staff pay and the crew board

  • Job 1042

    Director

    The numbers, not the records

    Jobs this month
    96
    Running late
    3
    Waiting to invoice
    5
    Days to invoice
    3 on average
    Repeat work
    2 jobs in 5

    Cannot see individual job sheets and photos

One job record, four roles. The figures are an example, made to show how the permissions work.

On the two screens it lives on

In the van, on a phone

14:38

Job 1042

On site

Unit 4, Bilston

  • Shutter one replaceddone
  • Shutter two replaceddone
  • Photos added, 4 so fardone
  • Customer signatureto do

Send to the office

At the desk, in the office

Jobs, this week

  • 1040WillenhallInvoiced
  • 1041WalsallOn site
  • 1042BilstonSigned offopen
  • 1043DudleyBooked

Job 1042, Unit 4, Bilston

Signed off
14:40
Photos
4 attached
Signature
Captured on site
Invoice
Ready to raise

Filled in on site with gloves on, and read at a desk a second later. One record, not a sheet of paper that has to survive the drive back.

The same record, two screens. An example, drawn to show how one job looks from each end.

Process

How it works

  1. Discovery with your team

    Mostly listening and asking awkward questions, with the people who will actually use it. We map what really happens, who needs to see what, and the exceptions.

  2. A written scope

    What it does, who can see and change what, what it connects to and what it costs, in writing before any code. If an off the shelf product would do, we say so.

  3. Data and roles designed first

    The database and the permissions are designed around how your business is structured, then the screens for each role, on desktop, tablet and phone.

  4. A working version early

    A first working version arrives early, so you are reacting to something real rather than a description. We build out from there.

  5. Tested by your team

    The people who will use it every day try it on real work, and we change it when they tell us what we got wrong.

  6. Launch, handover and ownership

    Your existing records are moved across from the old spreadsheets and your team is shown how it works. You own the code, the data and the documentation.

Who this is for

Right for you if

Organisations with real internal process. Departments, permissions, people in the field, information that has to be collected once and seen by several teams.

Probably not us if

You want an off the shelf product configured. That is a good option and a cheaper one, and we will say so rather than build you something you did not need.

From £5,000, because these are scoped around one business rather than installed. See the full pricing

What people actually build

Every one of these started as a spreadsheet, a clipboard or somebody’s memory.

  • Job management and scheduling. What is booked, who is on it, what happened and what is outstanding. Assignment, completion and sign off, in one place.
  • Vehicle and fuel tracking. Fleet records, mileage, fuel spend per vehicle, service intervals, MOT dates and the reminders that stop one being missed.
  • Inspections and health and safety forms. Filled in on a phone at the site, with photos, timestamps and a signature attached. Findings raised as actions and chased until they are closed.
  • Stock and assets. What is held, what is out on a job, what needs ordering and what a given van is carrying right now.
  • Approvals. Anything that currently needs somebody to say yes by email. Purchase requests, time off and quotes above a threshold, with a record of who approved what and when.
  • Employee records. Staff details, certifications and their expiry dates, training, holiday and performance.
  • Reporting. The numbers the directors want, generated from what the business already collects rather than assembled by hand on the last Friday of the month.

Most businesses need a few of these joined together rather than all of them. Because they share one database, the inspection, the job, the van and the person who did the work are all linked, and nobody has to match them up afterwards.

What these systems are made of

The technical terms, and what each one means for the people using it.

  • Role based access control. Permissions come from a person’s role rather than being set one by one. Each department and each level sees and does only what it should, so a fitter cannot open the invoicing and a new starter cannot see the directors’ figures.
  • Single sign on with Microsoft Entra ID. Entra ID is the part of Microsoft 365 that holds your staff accounts. Connecting to it means one login for everything, the multi factor authentication you already use protecting this too, and leavers removed in one place. If you are not on Microsoft 365, the application gets its own secure sign in instead.
  • A progressive web app with offline support. A website that installs on a phone or tablet and behaves like an app, with no app store involved. It keeps working in a basement, on a rural site or anywhere else with no signal, holds on to what was entered, and syncs when the connection comes back.
  • Integrations through APIs. An API is the published way one piece of software lets another read and write its data. Most accounting packages, payment providers and calendars offer one, as does Microsoft 365, so information moves between them without anyone retyping it.
  • A relational database as the single source of truth. Data held in linked tables, so a customer, a job, a vehicle and an invoice all point at each other and each exists once. No copy of the spreadsheet with FINAL in the file name sitting on somebody’s desktop.
  • Audit trails. Every change recorded with who made it and when. When a figure is questioned, the answer is in the history rather than in somebody’s memory.
  • Dashboards, reports and exports. Live figures for whoever is allowed to see them, and exports to Excel or CSV when your accountant or an auditor asks.
  • Cloud hosting and backups. Hosted in the cloud rather than on a machine in the office, with backups taken automatically, so a stolen laptop or a flooded office does not take the business with it.
  • UK GDPR. Personal data about staff and customers limited to the roles that need it, kept only as long as there is a reason to, and easy to find, export or delete when someone asks for theirs. It is built in from the start so you can meet your obligations, not bolted on afterwards.

Why these start at £5,000

Because nothing about them is off the shelf, and the honest answer to “why does it cost that” is the work that happens before anybody writes any code.

We sit down with the business and map what actually happens, which is almost never what the process document says. What information gets collected, by whom, on what. Where it goes next. Who needs to see it and who must not. What the exceptions are, because every business runs on exceptions. What has to work on a phone with no signal.

Then it is designed around that, built, tested with the people who will actually use it, and changed when they tell us what we got wrong.

A cheaper version of this exists. It is called configuring an off the shelf product, and for plenty of businesses it is the right answer. If that is your situation we will tell you, because selling somebody a bespoke build they did not need is a good way to never get a referral.

And if what you need turns out to be a form, a list and a notification, Microsoft 365 may already do it with the licences you pay for. We will point you there first.

One we run ourselves

Detailing Sanctuary, Patrick’s own mobile detailing business in Wolverhampton, runs on DS Central, an application built for it. It is the one project where we can show you everything, and it is written up on our work page.

Whatever we build for you, you own it at the end. The code, the data and the documentation.

We work face to face across Wolverhampton, Bilston, Wednesfield, Willenhall, Walsall, Dudley, Cannock, Telford, Stafford and Birmingham, and remotely with businesses anywhere in England. Most of it happens over email and video either way, so where you are matters less than whether we are the right fit. How a build actually runs

Tell us what you need

Tell us what you do and what you want to change, and we will come back with something useful. We read every enquiry ourselves. We reply within one working day.

Boxes marked are needed. The rest are optional.

What is it about? tick anything that applies

We use your details to reply to your enquiry, prepare your free concept and quote for the work. We do not sell them or use them for marketing, and we only share them with the services that run our business. The one exception is the optional box about Google adverts: if you tick it, Google gets only what the box describes, never your name, email, phone number or message. Privacy policy

Send an enquiryCall