Case Study: Automating a Norwich Signage Firm's Enquiry-to-Invoice Chain

The headline: a Norwich signage company went from doing invoices at the kitchen table to raising them with about ten minutes of input — and started booking more work with the same team, because quotes now go out faster. Here's exactly what we changed and why it worked.

I'm Jack, founder of Toki, a Norwich automation consultancy and Zapier Silver Solutions Partner. This is one of my favourite builds to talk about, because nothing exotic happened. No AI wizardry, no custom software. Just a messy manual process, mapped properly and connected using tools the business already paid for.

The situation: a paper business drowning in admin

The company did excellent work and had happy customers. The problem lived entirely in the back office. Job details lived on paper. The schedule lived in someone's head and a wall planner. Invoicing meant copying numbers between a diary, a spreadsheet, and an accounts package — in the evening, after the actual work was done. The reward for a busy week was a longer admin night.

This is the most common shape of problem I see: the business isn't broken, the handoffs are. Every time work passed from one place to another — quote to job, job to schedule, job done to invoice — a human had to retype something. Those retype moments were eating evenings.

Step one: map before touching a tool

We spent the first session on a whiteboard, not in software. We drew the whole journey: enquiry in, quote out, job scheduled, job completed, invoice raised, payment chased. Then we marked every point where information got copied by hand. Those copy points became the target list. If you want the method itself, it's the same one in my workflow playbook.

Step two: build the standard path

Using the tools the business already had, connected with Zapier, we automated the spine of the process:

• New job sheets generated automatically instead of handwritten.
• A shared team calendar that updated itself, replacing the wall planner and the owner's memory.
• Invoicing triggered from job completion, so the numbers flowed into the accounts package instead of being retyped at night.

Crucially, we built the standard case first and tested it with real jobs before adding any clever edge-case handling. Building the exceptions first is how people end up with automations nobody can debug.

The result: the same team, more jobs

Two things changed. First, the admin collapsed — invoicing went from an evening job to roughly ten minutes of input. Second, and more valuable, quotes started going out faster, which meant more jobs got booked. The team didn't grow; its capacity did. That's the pattern I see again and again: automation doesn't replace people in a small business, it removes the part of their week they resented and gives that time back to actual work.

Why it worked when other automation attempts fail

Three reasons. We mapped before building, so we automated the real process, not an imagined one. We used existing tools, so there was nothing new for the team to learn or resent. And we started with one clean path rather than trying to automate everything at once. None of that is technically difficult. All of it is easy to skip — which is why so many DIY automation projects quietly die.

Frequently asked questions

How long did this build take? A focused build like this typically lands within a couple of weeks including testing, not months. The mapping is the slow part; the building is fast once you know exactly what you're building.

What did it cost? Builds of this size at Toki typically start around £750–£2,000 depending on how many processes are involved. Measured against the evenings it gave back and the extra jobs booked, it cleared its cost quickly.

Could a business do this themselves? The tools are DIY-friendly, yes. What a consultant adds is the mapping discipline and knowing which handoffs to automate first — which is most of what separates automation that sticks from automation that gets switched off.

Almost done! When you're ready, here are four ways I can help you:

1. Read it. A guide on how to use ClickUp and actually make it work for you.
2. Connect it. Let's be LinkedIn pals. I make funny videos sometimes.
3. Workshop it. Book a 30-minute chat to talk processes and build a Miro together.
4. Go for it. Fill in my contact form — let's talk ClickUp or Automations. Whatever tickles your pickle.

Wanna hear from the unfiltered version of me? Sign up to my newsletter. The Working Notes. 2 minute reads. Behind the scenes. Hopefully helpful. Maybe funny.