Playbooks
What one system changes: each step hands the next one what it needs
Joining up your tools means each step of a job hands the next one what it needs, so nobody retypes, chases or hunts for the latest version. We follow two jobs end to end to show what that looks like. Both are worked examples, not client results.
By Seb Lawson · 10 November 2026 · 6 min read
When your tools are joined up, each step of a job hands the next one exactly what it needs. Nobody retypes the address, nobody chases the engineer for their hours, and nobody asks which spreadsheet is the current one. The clearest way to see what that changes is to follow a job from the first message to the money arriving, so below are two: an emergency plumbing call-out and a new accountancy client. Both are worked examples, built from the kind of work we see every week. They aren’t results from a named client.
A burst pipe goes from WhatsApp to paid without anyone retyping it
It’s 7.40pm on a Tuesday. A customer in St Clement sends a WhatsApp message to a plumbing firm’s business number: water coming through the kitchen ceiling, photo attached.
Without a joined-up system, the owner sees it on his phone over dinner. He rings the customer back, writes the address on the back of an envelope and phones round to find out who’s on call. The engineer goes out, fixes it and texts a photo of the parts he used. Two days later someone in the office types up a job sheet from the texts, works out the hours, creates the invoice in Xero and emails it. The customer pays a fortnight later, after one reminder. The photos are still on the engineer’s phone, so if the insurer asks for them in March, someone has to go looking.
With one system, the same evening goes like this.
- The WhatsApp message lands in the system as a new enquiry, with the customer’s number, the photo and the time. If they’re an existing customer, their address and history come up with it.
- The system shows who’s on call tonight. The owner taps once to send the job to that engineer, and the customer gets a reply with the engineer’s name and when to expect him.
- The engineer opens the job in ServiceM8 on his phone. The address, the photo and the customer’s notes are already there.
- On site, he logs his hours and the parts from the van, adds before and after photos, and the customer signs on the screen.
- When he marks the job complete, the invoice is raised in Xero from the job, with the parts priced from the firm’s price list and GST added, and sent to the customer with a link to pay by card.
- The customer pays that night or the next morning. Xero matches the payment and the job closes.
- The photos, the signature and the notes are filed against the customer and the property, so the insurer’s question in March takes a minute to answer.
Nobody typed the address twice or rebuilt a job sheet from text messages, and the invoice went out the same evening the work was done.
The tools stayed the same and the gaps between them closed
WhatsApp, ServiceM8 and Xero are all still there. What changed is that they now pass the job from one to the next, with a record at each step. For the owner, that means cash comes in sooner because invoices go out when the work is finished, and Thursday afternoons are no longer spent typing up the week’s job sheets. It also means there’s a complete record of every job if a customer disputes a bill or an insurer asks questions.
A new accountancy client goes from ID checks to signed-off accounts in one record
A small accountancy practice in St Helier takes on a new client: a Jersey company with two directors that needs annual accounts and a tax return.
Without a joined-up system, the partner emails the directors for ID and proof of address. The documents trickle in over three weeks, some by email and one by post. Someone saves them to a shared drive and ticks a column in the take-on spreadsheet. The engagement letter is a Word template, edited by hand and emailed for signature. The client’s details are typed into the practice’s client list, then into Xero, then into the tax software. At year end the team emails for bank statements and invoices, chases twice and builds the accounts from whatever arrives. The partner reviews a printed pack, and the final sign-off is a scanned signature on a PDF that someone will have to find again next year.
With one system:
- The enquiry comes in through the website and creates a client record. The client types their details once.
- Each director gets a secure link to upload ID and proof of address and answer the due diligence questions the practice needs for its anti-money-laundering checks. The system tracks what’s in and what’s missing, and sends polite reminders so the team doesn’t have to.
- A named person in the practice reviews the documents and records their decision, with their name and the date. Nothing moves on until that’s done.
- The engagement letter is generated from the practice’s own template with the client’s details filled in, and sent for e-signature. Once signed, it’s filed against the client.
- The client record flows into Xero and the practice’s other tools, so nobody retypes the company name, number or year end.
- At year end, the system sends the client a checklist of what’s needed, tracks what’s arrived and chases what hasn’t. The team can see at a glance which clients are ready to start.
- The draft accounts go to the partner for review inside the system, with comments and changes recorded. The client signs off online, and the signed accounts are filed with everything else for that client and that year.
The practice can see where every client is without asking
The biggest change is visibility. Which ID checks are outstanding, which engagement letters are unsigned, which year ends are waiting on the client: it’s all on one screen instead of in people’s heads. The second change is the record. When the practice’s anti-money-laundering checks are reviewed, the evidence of who checked what and when is already there, created as the work happened. The system keeps that record. The practice stays responsible for the checks themselves.
The value is in the hand-offs
Both examples use tools the businesses already had. The difference is in the hand-offs, the moments where work passes from one person or tool to the next. That’s where details get retyped, where jobs sit in someone’s inbox and where things go missing. A joined-up system is mostly a set of good hand-offs, each with a record of what happened.
Start with the hand-off that hurts most
You don’t need to join up everything at once. Pick the hand-off that costs you most, which is usually wherever the same details get typed twice, and fix that first. We explain how to find it in spreadsheets aren’t the problem, retyping is, and how to switch over in stages in going live a piece at a time.
If you’d like to see what your own version of these examples would look like, book a review. It’s a free 30-minute call, and we’ll walk through one of your jobs from first message to paid. You can also build your system first to show us what you use today.