> For the full site index see https://www.fenwickautomation.com/llms.txt > Every page has a Markdown version at the same URL with .md appended. # Pipeline automation Jobs moved from enquiry to quote to handover on your rules, with the folder, the tasks and the chase raised at each stage. What stays manual. Pipeline automation is a bespoke build that moves each job from stage to stage on your own rules, raising the folder, the tasks and the chase for a person to check. Take on more work with the office you've got. ## The problem A job comes in and somebody creates the folder, names it the way the office names things, and copies the enquiry into it. The quote goes out and somebody writes the chase date on a pad. The client says yes and somebody sets up the job record, raises the tasks, asks for the site details, books the site visit and tells the engineer. The job finishes and somebody remembers, or does not, to send the handover and the invoice. None of those steps is hard. The problem is that each one depends on a person noticing that the previous one has happened. When the office is busy, the noticing slips. A quote sits unchased. A job sits at "accepted" with no folder and no tasks. A handover goes out late because the person who does it was on site all month. The cost is the gaps between the stages: the jobs that stall, the chases that never happen, and the time every morning somebody spends working out what state everything is in. - Fewer jobs sit waiting for somebody to remember the next step. When a job reaches a stage, the build raises what that stage needs on your rules: the folder, the record, the tasks, the chase date. - A job that is missing what the next stage needs is flagged with a list, instead of stalling quietly until somebody asks about it. - Whoever opens the pipeline in the morning sees where every job is, because the state was updated when the job moved, not when somebody got round to it. ## What it does A job reaches a stage and the things that stage needs are raised on your rules: the folder, the tasks, the chase. A job that is missing something goes back to a named person with a list, and the email to the client is drafted for them to send. The build watches the stages a job passes through in the software you already use: enquiry, quote sent, quote accepted, booked, in progress, complete, handed over, invoiced. Your names for them, your order. When a job reaches a stage, the build does what that stage needs on your rules. It creates the folder and names it your way. It raises the tasks and sets the chase date. It drafts the email asking the client for what is still missing, for a person to check and send. It updates the record, so the next person can see where the job is. Where a stage has a checklist, the build checks it before the job moves on. A job that is short of a site address, a purchase order number or a signed quote does not move. It goes back to a named person with the list of what is missing, and the email to the client is already drafted. ## Who it suits A business where jobs follow the same shape most of the time, from enquiry through to handover, and where the office spends a good part of each day pushing jobs from one stage to the next by hand. It suits teams already using job management or CRM software, even loosely, because there is a record to move. It suits less well where every job is run differently, or where the stages exist only in one person's head. Those can still be built, but the first job is writing the stages down, and that is audit work before it is build work. ## What it needs from you Your stages, in order, with what has to be true before a job can move from one to the next. What gets created at each stage and who is told. Your naming for folders and records, which is never as consistent as everyone thinks it is. Two people will describe the pipeline differently, and both will be describing what they actually do. The build follows one version and you agree which. Your records have gaps: jobs with no stage, jobs on two stages at once, jobs that were finished a year ago and never closed. Those come out in the data check, and some of them have to be tidied by a person before the build can trust the record. Signature to live: from 4 weeks, depending on the size of the job. ## What it does not do It does not decide whether to take a job, what to price it at, or who should do it. It moves the job and raises the work. It does not send anything to a client on its own: the emails it drafts wait for a person. It does not fix bad data. A job on the wrong stage stays on the wrong stage until somebody moves it, and the build will then do what that stage asks, so the person still has to be right. Version one will be wrong about some rule that everyone in the office knows and nobody wrote down, and the person who runs the pipeline will spot it early on. That is why it runs alongside the old way first, and why the old way is not switched off until your team says so. This is a Checks build. It checks a job against what the next stage needs and moves it or sends it back. It does not draft a document from scratch, and it does not assemble a pack. Checks One route, signature to live: from 4 weeks, depending on the size of the job and the state of your data. We'll tell you on the audit. ## Where it sits in the process Pipeline automation is one route, built on its own. The free 10-minute call tells you whether it fits and gives you a rough estimate: a range for the first route, not a quote. The paid audit looks at your real documents and your real data, works out what the work costs you a year in your own figures, and writes down what to build first. The fixed price for the build comes from the audit, with three options that cut scope rather than corners. Then the data check, the build, the parallel run, go-live and training, and monthly running. [All nine stages are on the About page](https://www.fenwickautomation.com/about.md#how-it-works). ### Related systems - [Quote to handover gate](https://www.fenwickautomation.com/services/systems/quote-to-handover-gate.md) - [Quote chasing](https://www.fenwickautomation.com/services/systems/quote-chasing.md) See it running: [read the case study](https://www.fenwickautomation.com/work.md). Last updated: 12 October 2026