A quick win in workflow automation is a step your team repeats many times a week, follows a rule they could write down, and starts from information that already arrives complete. Hand those steps to software first. In our experience most businesses can start with the same six, in this order: capture each request once, set up the job from it, book the date, tell people when the stage changes, carry the price to the invoice and bring the customer back. Each one runs from the record the step before it created, which is why the order matters.
We are writing this for the owner or operations lead of an established Irish business who can see the repeat work and wants to know where to start. If you want a definition first, our article on what business process automation is covers it. This one is practical.
How to spot a quick win
We apply three tests to every step before we suggest automating it. A step that passes all three is usually a quick win. A step that fails any of them is a project in its own right, and it can wait.
It is repeated
The step happens many times a week, in much the same way each time. A process that runs four times a year rarely earns the cost of building and looking after an automation.
It follows a rule
The person doing it could write down what they do, and a colleague would do it the same way. If three people handle the same job three different ways, someone has to choose one before anything is built. Software repeats whatever it is given.
Its inputs are already clean
The information the step needs arrives complete and in the same form every time. If someone has to chase a missing address or read a PDF to find a figure, fix the input first. That fix is often the first quick win.
Two examples we use throughout
Phantom is a property marketing firm in Belfast. A single shoot starts with an estate agent asking for photography. It then needs a photographer's time, somewhere for the files, delivery back to the agent and a bill. Phantom runs on Kerb Appeal, software we built and run for property marketing companies.
The second is one of our published studies, for a home heating service. Its enquiries arrive through forms on its website, and each one has to reach an installer who will do the work. Heating is serviced every year, so the first job is only the start of the relationship.
The quick wins, in order
These are the six we would look at first in most businesses. Skip any that do not apply, but keep the order.
- Capture each request once, as one record. At Phantom, requests from estate-agency teams, CSV imports and photographer calendars all create the same thing, one project record per shoot. In Kerb Appeal the agent books through a portal, the address completes itself as they type, and the booking arrives with the details the photographer needs. For the heating service, each website enquiry becomes a lead record that keeps its status from then on. Everything that follows starts from that record instead of someone's inbox.
- Set up the job from the record. At Phantom the record creates the project folders automatically, so nobody builds a folder structure by hand for each shoot. In Kerb Appeal those are Supplied, Edited and Delivered folders, with permissions set on booking.
- Book the date and put it where people look. Photographer calendars connect availability to the project, and the booking is synchronised to the calendar from the record. Kerb Appeal blocks double bookings. For the heating service, the record carries each enquiry into allocation to an installer, and installers open their part through a supplier portal using a sign-in link known as a magic link.
- Tell people when the stage changes. In Kerb Appeal, when a project moves stage the people who need to know are emailed automatically, so the office stops passing messages along. The agent is told when the photographs are ready. For the heating service, transactional email goes out from the same record.
- Carry the price through to the invoice. At Phantom, delivered work connects to a billable record. Client-specific pricing carries from the project into invoicing, so each estate-agency client is billed at its own rates. In Kerb Appeal, completed shoots are invoiced in a batch.
- Bring the customer back. Once a Phantom shoot is delivered, repeat business is prompted automatically from the same record. For the heating service, scheduled jobs send the servicing reminder when the year comes round, on fixed rules, so each year's booking connects back to the original enquiry.
None of these needs anything clever. Each one connects systems the business already uses and applies a rule the team has agreed. In the work we do, that is where most of the gain comes from.
What the result looked like at Phantom
With requests, calendars, folders, delivery and invoicing running from one record, Phantom recorded 45% lower coordination cost per completed shoot. That is measured over the 12 months after launch against the 12 months before, while shoot volume grew. You can read how it was measured on our Phantom project page.
The unit matters. Cost per completed shoot follows the record from request to invoice. Measure your own baseline the same way before anything is built, or you will have nothing to compare against.
Where a person should still approve
Some steps commit the business to something: a price, a refund, a credit note, a contract. Those keep a named person approving them. The automation prepares the decision and records the outcome, and the person makes the call.
In practice this splits cleanly. The rates a client pays are a commercial decision, made by a person. Once they are agreed, software can apply them to every invoice. The same goes for exceptions. When a request changes or arrives incomplete, the rule no longer holds, so the work should stop and wait for an owner. Software follows the agreed rule when its conditions hold, and the responsible person decides when they do not.
What to leave alone for now
Leave out anything where each case is different, or where the judgement is the work itself. A negotiation or a design decision needs a person, and software can only gather what they need. Leave out low-volume steps, however irritating they are. And leave out any step that sits on a process the team has not agreed, until it has.
Messy inputs, such as supplier invoices that arrive as PDFs or emails that need sorting by what they ask for, take more work to automate. They can be worth doing, but they are rarely the first thing to do.
How to find yours
Pick one process that runs often, with a clear start and finish, such as an enquiry becoming a booked job. Follow a few real pieces of work through it, including the emails and spreadsheets nobody mentions in a meeting. Our note on process mapping before automation sets out how we do that. Then mark every step that passes the three tests, and measure what the work costs today.
If you can see the repeat work but not which process to start with, our Diagnostic takes about one week. It looks at how the work runs today and ends with a written recommendation to build, buy, defer or stop.
That is how we approach automation for an established business. The quick wins come first, the approvals stay with people, and the bigger projects wait until the record is in place.
What to ask whoever builds it
Whoever you choose, these questions will tell you quickly whether the order of work has been thought through.
- Which of our steps are repeated, follow a rule and already have clean inputs?
- What single record will every automated step start from?
- Which steps commit the business to something, and who approves them?
- What happens when a request changes or arrives incomplete?
- What will we measure before you start, and per what unit of work?
- Can we keep the manual route until each new step is proven?
If you can see the repeat work in your business and want to start with the steps that pay back first, you can start a project with us.
