Why We Built Toki a Client Portal (and Why More Businesses Should)

A client portal earns its place the moment a business is repeatedly answering the same "where are we up to?" question over email or WhatsApp — it turns status updates, documentation and handover material into something a client can check themselves, on their own time, instead of waiting on a reply. We built one for Toki for exactly that reason: to give clients a single place to see where their build stands, pick up their handover documentation, and find training resources after launch, rather than digging back through old email threads.

I'm Jack Lenton, a ClickUp Verified Consultant and Zapier Silver Solutions Partner running Toki, an automation consultancy based in Norwich. This isn't a sales pitch for portal software — it's the reasoning behind building our own, and why I think most businesses that deliver ongoing work for clients are missing something similar.

What problem does a client portal actually solve?

Three specific ones. Repeated status-chasing — the same question asked a different way each week, because there's nowhere for a client to check for themselves. Documentation scattered across email, Slack and a shared drive, so nobody, including you, can find the current version of anything quickly. And no single source of truth once a project's handed over — the client's only record of what was built and why becomes whatever they can find in their inbox.

What should a client portal actually include?

Kept deliberately simple, it needs project and build status that's genuinely current, the key documents a client actually needs again — the original proposal, the handover document, training material — and a clear route to support if something needs attention after launch. The temptation is to build something that tries to do everything; the useful version is the one that answers the three or four questions a client actually asks.

Why did Toki build its own instead of using an off-the-shelf client portal tool?

Plenty of client-portal products exist, and for a lot of businesses one of those is the right call. For us, building a lightweight version meant it could mirror exactly how we already work with clients — the same shape I describe in every engagement: a discovery conversation, a proposed structure to review, the build itself walked through on Loom, live training, and a plain-English handover document — rather than forcing that process into a template built for a different kind of business. It's not a claim that building your own is always the right answer; it's what made sense for how we work.

What does this mean for other businesses?

If your business ends every project by handing over documentation, and there's no natural home for a client to come back to when they need it again, that's the specific gap a portal closes. It doesn't need to be complicated to be worth it — a single, clearly organised page with current status and the right documents attached often does more for a client relationship than a sophisticated tool nobody quite trusts to be up to date.

Frequently asked questions

Do I need custom software to build a client portal?
Not necessarily. The starting point is having one current, organised place for status and documents — that can be as simple as a well-maintained shared page before it's ever worth a custom build.

What should a client portal include at minimum?
Current project or build status, the key documents a client is likely to need again, and a clear way to reach support — kept to what clients actually ask for rather than everything you could possibly show them.

Is a client portal only useful for automation consultancies?
No. Any business that delivers a project or ongoing service and finds itself repeating the same status update by email is a candidate — the format changes, the underlying problem doesn't.

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.