Guides

Guide · 6 minute read

What a customer portal should do on day one.

If clients keep asking where things stand, a portal can give them the answer without another email. But a portal is a window into how your team works. Get the first version small and right, and clients will actually use it.

A day-one portal

Six things, on one screen.

Here is what a small first version can look like. Each numbered part is explained below.

Example Co. client portal Good morning, Jordan.

Project status

Office move: new staff setup In progress
  1. Plan
  2. Set up
  3. Test
  4. Done

Next: laptops ready for pickup Thursday · Sam is on it

We need from you

  • Start dates for two new hiresDue Fri
  • Approve the equipment quoteDue Mon

Start a request

New user onboarding Change request Something else

Documents

  • Signed proposal.pdf
  • New hire checklist.docx
Upload a file
Example screen. Example Co., Jordan, and Sam are made up.
  1. Status at a glance.

    What is happening, what comes next, and who is on it. This is the question clients ask most, so it goes at the top.

  2. What we need from you.

    The client's own to-do list, with due dates. Work often waits on the client, and this makes that visible without a reminder email.

  3. Request templates for repeatable work.

    A short form for each request you get again and again, like onboarding a new user. It asks for the right details up front, so nobody has to chase them later.

  4. One place for documents.

    Files go both ways in one spot, so nobody digs through old email threads for the latest version.

  5. Each client sees only their own work.

    Clients sign in with an account they already have, like Microsoft or Google, and see their projects and nothing else.

  6. Email nudges that link back.

    Clients will not remember to check a portal. A short email when something needs them, with a link straight to it, builds the habit.

The part clients never see

A portal is only as current as your team's side.

Every status, due date, and document in the portal has to come from somewhere. If your team still tracks work in spreadsheets and inboxes, someone has to copy it into the portal by hand. That stops happening during the first busy week, the portal goes stale, and clients go back to email.

So day one includes your side too: one place where your team updates the work, and the portal reads from it. If that place does not exist yet, start there. Our spreadsheet guide covers the signs.

From the MSP

The templates did more than the portal.

At one managed IT provider, I set up the client portal. Before that, clients called or emailed to get tickets created, and we went back and forth to collect what we needed.

I worked with most of our clients to set up standard ticket templates for repeatable work like new user onboarding. The template asked for the right information up front. Those tickets moved faster and smoother: we got what we needed, and clients no longer had to dig for details they could not remember.

Roll it out in stages

Start slow. Add the next piece when clients are ready.

You cannot hand a client an entirely new process and expect them to pick it up right away. Move them over in stages, and add the next stage once they are comfortable with the last one.

  1. Standard requests and status

    Start with the requests clients make most and the status they ask about most. Use templates so each request arrives complete.

  2. Change requests

    Once clients are used to submitting requests, move change requests into the portal so approvals and history live in one place.

  3. Contracts and e-signing

    Proposals and agreements can be reviewed and signed where the rest of the work already lives.

  4. Invoicing and billing

    Add invoices last. By then clients trust the portal, and money is the part they are most careful with.

Before you build

Check what you already have.

  • Check whether a tool you already use has a client portal you have not turned on. Many help desk, project, and accounting tools do.
  • List the three questions clients ask most. Your first version should answer those and little else.
  • Pick one or two friendly clients to try it first, and ask what they ignored.
  • Decide who on your team keeps each part current before you launch.

Not sure whether to buy one or build one? Take our build-or-buy checklist.

Tired of "where does this stand?"

Tell us what your clients ask about most. We will help you work out what your first version needs, and what can wait.

Start a project