Quote and job workflows for UK service businesses

Turn accepted quotes into a process your team can follow

Give every job a status, an owner, a next action and a full customer history, from the first enquiry through to the invoice. Built around how your business actually runs, not how a software company assumed it would.

From £149/moplus VAT, £699 setup. Workflow designed with you, not from a template.

Manchester based, UK wide. This is the system our own repair operation runs on every day.

Every Manchester PC repair goes through this workflowCompany 13356970, VAT registeredConfigured for your operation, not a generic template

The work is fine. Knowing where the work is, that is the problem

Most service businesses do not have a quality problem. The jobs get done properly. What they have is a visibility problem, and it shows up in the same handful of moments every week.

  • A customer rings to ask how their job is going and nobody can answer without walking to the back and looking.
  • Two people have quoted for the same enquiry because neither knew the other had.
  • A job has been sat waiting on a part for nine days and nobody noticed.
  • The customer approved extra work verbally, and now there is a disagreement about what was agreed.
  • Somebody has finished a job and it has not been invoiced, and nobody can say for how long.
  • The whiteboard is out of date by mid-morning, every morning.

None of that is fixed by working harder. It is fixed by the job having a place to live that is not somebody's memory or a wall.

Why whiteboards and spreadsheets stop working at about five people

There is a size at which informal systems quietly stop coping, and most owners pass it without noticing because the failure is gradual.

With two people and a handful of jobs, everybody knows everything. You can shout across the workshop. The whiteboard is accurate because the person who changes it is the person doing the work. This genuinely works, and there is no reason to change it while it does.

The trouble starts when the number of live jobs goes past what one person can hold in their head, or when the people doing the work are no longer in the same room. At that point the informal system has not failed loudly. It has just started leaking: a job here that nobody chased, an approval there that nobody wrote down, a customer who was told something that never made it back to the person doing the work.

The tell is when the owner becomes the database. If work stops moving properly the moment you go on holiday, you are the system, and that is an expensive and fragile thing to be.

The customer feels it before you do

From the outside, a business without job visibility looks like a business that does not care. The customer rings, gets put on hold while somebody goes and looks, and is told "I think it is nearly ready". They ring again two days later and get a different answer from a different person.

You know the work is going fine. They do not, and their impression is built entirely from those two phone calls rather than from the quality of what they eventually collect.

Approvals are where the money leaks

Extra work agreed on the phone and never written down is one of the most common causes of a bad invoice conversation. The technician remembers agreeing it. The customer remembers something vaguer. Nobody has anything in writing, so you either lose the money or lose the goodwill.

Making approvals a step in the workflow, with the customer confirming in writing, removes an entire category of awkward conversation. It is a small change that pays for itself the first time a job goes sideways.

A real workflow, ours, end to end

This is not an illustration. It is the actual path a repair takes through Manchester PC, and it is the system we then adapt to how your business works.

  1. 01

    Enquiry received

    From the phone, the website, chat or the counter. It arrives as a record, not a note.

    How enquiries are captured
  2. 02

    Triaged and reviewed

    What is the device, what is the fault, is it something we should take on at all. Some jobs are politely declined here, which saves everybody time.

  3. 03

    Initial quote prepared

    Built from a library of priced work rather than from scratch, then checked by a person before it goes anywhere near a customer.

  4. 04

    Collection booked

    The customer picks a slot, the route is checked, and a confirmation goes out with a code the driver scans on arrival.

  5. 05

    Diagnosis added

    The technician has the full customer conversation in front of them, so they are not working from a one-line summary.

  6. 06

    Extra work approved

    If the job grows, the customer approves it in writing before anybody touches anything. No verbal agreements to argue about later.

  7. 07

    Return arranged

    Back out on the route, scanned again, and the customer knows when to expect it without ringing to ask.

  8. 08

    Closed and followed up

    Invoiced, closed, and a review request sent at the point the customer is happiest rather than three weeks later.

    Content and campaigns

Why we can say this with a straight face

We did not design this on a whiteboard. We survived our way to it

Every stage in that workflow exists because something went wrong without it. That is worth saying plainly, because process diagrams usually look like somebody sat down and thought it all through in advance. Ours did not happen that way.

The approval step exists because we once did several hundred pounds of extra work on a verbal yes and then had a conversation nobody enjoyed. The triage step exists because we used to take on jobs we should have refused, and losing money slowly on a hopeless repair is a particular kind of miserable. The scan-on-collection step exists because we had a device go missing between a customer's hallway and our bench, and there was no record of who had it.

The quote library exists because building every quote from nothing was taking a quarter of an hour, and quarter-hours add up to whole days across a month. The follow-up exists because we used to do beautiful work and then never ask the customer for a review, which meant winning the next three jobs the hard way.

So when we build a workflow for another business, we are not applying a theory. We are asking which of these failures you have already had, and which ones you have simply not had yet.

Every step in our workflow is a scar. That is why we can tell you which ones matter and which are just process for the sake of it.

Read the whole story

What your workflow would look like

Yours will not be a repair workflow, and it should not be. The shape stays similar; the stages, fields and rules come from your operation.

The first thing we do is map what happens now, including the bits that only exist in somebody's head. That conversation is usually the most valuable part of the project, and several clients have made changes off the back of it before we built anything at all.

Then we agree the stages. Most service businesses need somewhere between five and nine, and the temptation is always to add more. We push back on that, because a workflow with fourteen stages is one nobody keeps up to date, and an out-of-date workflow is worse than none.

Who sees what

An engineer on site needs a different view from the person in the office and a different one again from whoever is chasing money. Everyone seeing everything sounds egalitarian and in practice means nobody finds anything.

We set the views up per role, and the field views are built for a phone screen because that is where they will actually be used, usually in poor light with one hand.

What the customer sees

A surprising amount of inbound phone traffic is people asking where their job is. Giving customers a way to see that for themselves removes those calls entirely, and it makes you look considerably more organised than the competitor who cannot answer the question.

You control exactly how much detail is visible. Some businesses show the full history, others only the stage and an expected date.

Where a person still decides

The workflow moves information around and remembers things. It does not decide whether a job is worth taking, what to charge, or how to handle an unhappy customer. Those stay with people, and we would be suspicious of anybody selling you software that claims otherwise.

What changes is that when a person makes those calls, they are doing it with the full picture in front of them rather than from memory.

The four things a job workflow has to get right

We have built a lot of these now, for our own operation and for other people's. The ones that stick all do the same four things, and the ones that get abandoned usually fail at the same four.

One place where the truth lives

The moment there are two places to look, there are two versions of reality and staff learn not to trust either. That means resisting the urge to keep the old whiteboard going alongside the new system during a changeover, however comforting it feels.

We usually recommend a hard switch on a quiet week rather than running both. It is uncomfortable for about four days and then it is done. Running two systems in parallel for a month tends to end with people using neither properly.

Updating has to be faster than not updating

This is the rule that decides whether a workflow survives contact with a busy Friday. If moving a job forward takes four taps, it happens in the moment. If it takes a form with eleven fields, it happens at five o'clock from memory, badly, or not at all.

So we deliberately keep required fields to the minimum and let the system fill in whatever it can work out for itself: who, when, which job, which customer. The person supplies only what genuinely needs a human.

It has to tell you what is stuck

A list of jobs is not management information. What you need is the exception: which jobs have not moved in a week, which are waiting on somebody else, which are past their promised date. Everything healthy can stay quiet.

Our own version surfaces about five things each morning. That is the whole daily management routine, and it takes a couple of minutes rather than a meeting.

The customer has to feel the difference

Internal tidiness is worth something, but the return comes from what the customer notices: being told when the job will be ready without having to ask, getting the approval request in writing, hearing that the part has arrived.

Those messages are cheap to send and they are the difference between a customer who feels looked after and one who feels ignored while perfectly good work happens out of sight.

Pricing, and why this one cannot be self-service

All prices plus VAT, month to month. This is the one part of what we do that genuinely requires configuration before it is worth anything, so every tier includes us building it with you.

Quote Workflow

£699 setup£149/mo

Getting quotes out of the inbox and into a pipeline

  • Quote pipeline with up to five stages
  • Staff assignments
  • Follow-up reminders
  • Full customer history
  • Up to three users
  • Standard reporting
Ask about this
Most popular

Quote to Job

£1,500 setup£249/mo

Businesses where the work continues long after the quote

  • Custom quote stages
  • Quote converts straight into a job
  • Job workflow with owners and due dates
  • Automatic customer updates
  • Written approval for additional work
  • Calendar and task board
  • Five users, basic time tracking
Start with this

Operations Workflow

From £3,000 setup£399/mo

Multiple job types, field teams and real operational complexity

  • Multiple job types with different rules
  • Team roles and permissions
  • Field worker and driver views
  • QR code actions where useful
  • Support tickets
  • Custom customer communication
  • Management reporting, up to ten users
  • Monthly optimisation
Ask about this

Larger implementations are quoted individually after we have mapped the operation, because guessing at that scale helps nobody. Data migration from an existing system is always scoped separately.

Frequently asked questions

How is this different from a CRM?

A CRM is mostly about the customer relationship before the sale. This is about the work after it. They overlap, and in our platform they are the same system, but the value here is in what happens once a quote is accepted and there is an actual job to deliver.

We already use job sheets. Why change?

If the job sheets are working and nothing falls through, do not change. The question worth asking is what happens when somebody is off, or when a customer rings about a job the person in front of them did not do. If the answer involves walking to the back and looking, there is something to gain.

How long does it take to build?

A quote workflow is usually two to three weeks. A full quote-to-job build is longer, typically four to six, and most of that is agreeing how it should work rather than building it. We would rather spend an extra week on the mapping than build the wrong thing quickly.

Will my engineers actually use it?

Only if it is faster than not using it. That is the whole design constraint for the field views. If updating a job takes more than a few taps, people will do it at the end of the day from memory, which defeats the point.

Can it handle parts and stock?

Basic parts against a job, yes. Full stock control is a different problem and we will tell you honestly if you need a dedicated system for it rather than stretching this one out of shape.

What if our process changes?

It will, and that is expected. Stages, fields and rules can be adjusted. On the monthly plans that is part of the service rather than a change request with a price on it.

Does it connect to our accounts software?

Usually. Integration depends on what your accounting package allows, and we scope it separately once we know what you use. Getting invoices out of the workflow and into the accounts without retyping is normally one of the first things worth automating.

What happens to jobs already in progress when we switch?

We normally load the live jobs and leave the completed history where it is. Migrating years of finished work sounds thorough and rarely earns its cost, because nobody looks at it. Live jobs need to move because people need to work from them on day one, and that is usually an afternoon of entry rather than a project.

Can customers see their own job?

Yes, and it removes more inbound phone calls than almost anything else we do. You decide how much is visible. Some clients show the full history and the technician notes, others show only the current stage and an expected date. Either way the customer stops having to ring to find out whether anything has happened.

We work on site, not in a workshop. Does that change things?

It changes the views rather than the principle. Field work needs a phone-first screen, offline tolerance where signal is poor, and far fewer fields than an office user sees. The underlying workflow, quote to job to approval to completion, is the same shape whether the work happens on your bench or in somebody's loft.

What it costs you to carry on as you are

Worth doing the sum before you spend anything, because for some businesses the honest answer is that the current mess is affordable.

There are four costs to a business without job visibility, and only one of them appears anywhere in your accounts. The invisible three are usually larger.

The first is time. Somebody walking to the back to check on a job, twice a day, five days a week, is most of a working week over a year. That person is usually the owner or the most experienced technician, which makes it the most expensive time in the building.

The second is work that stalls. A job waiting on a part that nobody chased for nine days is nine days of a customer getting quietly annoyed and a bay occupied for nothing. Nobody notices because there is no list of things that have stopped moving.

The third is money agreed and never collected: extra work approved verbally and then written off to keep the peace, jobs finished and invoiced late or not at all. Every business we have looked at has some of this, and almost none of them know how much.

The fourth is the one that actually appears in the accounts, and it is the smallest: the customer who leaves because they could not get a straight answer about their job. You will feel that one and misattribute it to price.

If you cannot make those four numbers add up to more than the monthly fee, do not buy this yet. We would rather tell you that now than have you cancel in four months.

Show us how a job moves through your business

The free systems review is mostly us listening while you describe what happens between an accepted quote and an invoice. Most owners find the exercise useful on its own, whether or not we build anything.

All prices plus VAT. No minimum term on any plan.

Book a free systems review