Automation, AI and custom tools

Automation and AI, pointed at the work that wastes your week.

The waste is rarely one big broken process. It's a dozen small ones that each cost twenty minutes a day, usually done by someone senior enough to know better. We find those, remove the steps that shouldn't exist, and automate what's left. Where AI helps we use it, with a person still reading anything that reaches a customer.

Automation

The weekly retyping, gone

AI

Drafting and summarising, human checked

Internal tools

Something better than the shared spreadsheet

Integrations

Systems that were never meant to talk

Timed before. Timed after.

Where the time goes

Four things we find in almost every business. None of them are anybody's fault, and all of them are cheaper to fix than to live with.

Someone is quietly maintaining a spreadsheet

It runs a real part of the business, one person properly understands it, and everybody has agreed not to think too hard about that.

The same data gets typed in twice

Two or three systems were bought at different moments and never properly introduced, so a person is doing the job an integration should be doing.

AI got trialled and quietly dropped

A few people pasted things into a chat window for a month. Nothing was built into a real process, so nothing stuck.

Handovers run on someone remembering

Work moves between people by message and goodwill. That holds up fine until a week gets busy, and then something falls through the gap.

What we build

Every one of these starts with timing the process by hand, so we can measure the saving.

01

Workflow automation

We connect the routine steps between your CRM, marketing, finance and operations systems, so nobody has to do them by hand again.

02

AI inside real processes

We build research, enrichment, drafting and summarising into a workflow, with a person reading anything customer facing before it goes out.

03

Internal tools

We build a proper small application to replace the spreadsheet that's quietly holding up part of the business.

04

Customer facing apps

We build portals, calculators and quoting tools your customers will want to use.

05

Integrations

We get two systems that were never designed to talk to each other talking reliably, and plan for what happens when something fails.

06

Documentation and handover

Everything is written up in plain language and runs in your own accounts, so none of it depends on us being available.

Four things we won't do.

Worth saying out loud, because most of the disappointing automation work we get called in to repair started with one of them.

01

Add AI to something because it is the thing to say this year.

02

Automate a broken process instead of fixing the process.

03

Put a machine in a position to send something to a customer unchecked.

04

Build anything that only we can maintain.

How it works

We take one process at a time and time it before and after. A small change you can prove beats a big programme nobody can point at afterwards.

01

Find where the hours go

We sit with the people doing the work and map what really happens, including the steps nobody put in the process document.

Week 1
02

Fix it before automating it

Half the time the step shouldn't exist at all. Removing it is cheaper and faster than automating it.

Week 2
03

Build the smallest thing that works

It's live in days, with a human check on anything that reaches a customer.

Weeks 3 to 4
04

Measure it and write it down

We time the process again, write down how it works, then start on the next one. You get the saving as a number.

Then repeat

Questions people ask us

Where should we start?

Start with the process that irritates people most and happens most often. It usually isn't the one on the strategy slide.

Do we have to buy new software?

Usually very little. Most of this runs on tools you already pay for, plus a small automation platform if you don't have one yet.

Is our data going into an AI model?

Only where you've agreed to it and it earns its place. We'll tell you exactly what gets sent, where it goes, and what stops working if you turn it off.

What happens if it breaks after you leave?

It runs in your accounts and it's documented in plain language, so anyone competent can pick it up. We'd rather you didn't depend on us.

Can you work with our IT team?

Yes, and it goes better when we do. They usually know exactly where the problems are.

How will we know it saved anything?

We time the process before we touch it and again once it's live. If it didn't save time, we'll say so.

/CONTACT

Got something that isn't working? Let's talk it through.

Tell us what's going on with your website, CRM or pipeline. You'll get a straight conversation about what we'd do, with no sales deck and no obligation.

TAKING ON NEW CLIENTS RIGHT NOW
Got it, thanks. We'll read it properly and come back to you shortly.
That didn't send. Email hello@runlevel6.co.nz and it'll reach us.