More enquiries won't fix a leaky system

Kia ora e te whānau,

Getting more people to reach out feels like the answer. But if what happens after they reach out is slow and manual, more volume just means more people slipping through the cracks.

A pattern keeps showing up in our hui. A team wants more people coming through. More enquiries, more referrals, more sign-ups. So the kōrero jumps straight to getting noticed: ads, a campaign, posting more, pushing harder.

It's a fair instinct. But before we talk about bringing more people in, we look at what happens to the people who already reach out. Because if that part leaks, more volume doesn't help. It just means more people slipping through, and a tired team working harder to keep up.

What a leaky system looks like

You usually can't see the leak from the outside. It hides in the handovers.

An enquiry lands in an inbox. Someone copies it into a spreadsheet. A referral gets passed on in the hallway and remembered later, or not. A form comes in and nobody's sure who's chasing it. A follow-up depends on one person's memory on a busy day.

None of that is anyone's fault. It's just what happens when the steps between "someone reached out" and "someone helped them" live in too many places.

Why more volume makes it worse

Spending to get more people in, whether that's money on ads or energy on a campaign, is like turning up the tap on a bucket with holes in it.

The holes scale faster than the wins. Double the enquiries and you double the copying, the chasing, and the dropped follow-ups. The cost goes up, the stress goes up, and the number of people who actually get helped barely moves.

That's why we'll sometimes say: let's not spend more on reach yet. Let's fix what happens after someone reaches out first.

Map the journey first

Before changing anything, map the journey. From the moment someone reaches out, to the moment they get what they came for.

Where does it slow down? Where does it get handed from one person to another? Where does the same information get typed in twice? Where do things get dropped when someone's away?

You don't need software to do this. A whiteboard and an honest team will show you the leaks in an afternoon.

Fix the handovers, then turn up the volume

Most of the wins are small and unglamorous.

One form that drops straight into your system instead of an inbox. One reminder that doesn't rely on memory. One clear owner for each step, so nothing sits in the gap between two people. One view everyone can see, so "who's chasing this?" always has an answer.

Fix a couple of those and the same number of enquiries quietly turns into more people helped. Then, when you do spend to bring more people in, the system can actually hold them.

You don't have to rip everything out

Closing the leaks rarely means new software or starting again.

More often it's connecting and automating the tools you already use, one pathway at a time. We layer the automation over what's there rather than replacing it all at once, and we go slow enough that your team learns it and owns it.

A system the team understands beats a flash one they're scared to touch.

The Hono way

We'd rather help you keep the people you're already reaching than help you spend to reach more and lose them on the way through.

More reach is a good problem to have, once the journey behind it is solid. So we start with the leaks. They're cheaper to fix than they are to feed.

If you're about to spend on getting more people in the door, it's worth thirty minutes first on what happens after they walk through it.