01
Accounts and secure access
Sign-in that is safe without being hostile — password reset that works is a surprisingly large win.
What you need
Let customers help themselves.
A good portal removes work from your team by letting customers answer their own questions. A bad one adds a channel nobody monitors and a password everybody forgets. The difference is whether it was designed around the questions people actually ask.
Why it matters
The short version.
A portal is a deflection tool. Every question a customer can answer themselves is a call your team does not take, and the questions people ask are remarkably repetitive — where is my thing, what did I agree to, send me that document again, what is the status. A portal that answers those well pays for itself in recovered hours.
The failure mode is building a portal around what you would like customers to do rather than what they actually contact you about. That produces a well-made product nobody logs into, and a second channel your team now has to monitor. The inbound audit at the start exists specifically to prevent that.
Adoption is the whole game, and it is mostly decided by sign-in. Password reset that works, sensible session length, and no forced re-registration for existing customers. More portals die at the login screen than for any deficiency in what sits behind it.
More portals die at the login screen than for any deficiency in what sits behind it.
Is this you?
You probably need this if…
- Your team answers the same handful of customer questions all day
- Clients phone to ask for documents you have already sent them
- Status updates get chased by email because there is nowhere to look
- You are onboarding customers with a PDF and a lot of hope
What's involved
The actual work.
No two engagements are identical, but this is the shape of it.
02
Self-serve answers
Statements, documents, status and history, available without asking a human.
03
Requests and messaging
A clear path for the things that genuinely need a person, so those do not get lost.
04
Notifications worth keeping on
Timely and relevant, so people do not immediately mute them.
What goes wrong
Mistakes worth
avoiding.
Named plainly, because most of them are easier to avoid than to undo.
-
Building features nobody asked for
The feature list should come from your support inbox, not from a competitor's marketing page.
-
Hostile authentication
Aggressive password rules, short sessions and a broken reset flow will lose more users than any missing feature.
-
Launching silently
A portal nobody knows about gets no traffic and is then judged a failure. Rollout communication is part of the project.
How it runs
Start to finish.
Each phase ends in something you can open, click or read.
-
01
Audit the inbound
What are people actually contacting you about? That list becomes the feature list.
-
02
Design the flows
Especially sign-up and password recovery, where most portals lose people.
-
03
Build securely
Authentication, permissions and data handling appropriate to what you hold.
-
04
Drive adoption
A portal nobody logs into has not solved anything, so rollout is part of the work.
Deliverables
What you walk
away with.
Yours to keep, whatever happens next.
A secure, responsive customer portal
Measurable reduction in repetitive inbound contact
Admin tools for your team to manage it
Source code and infrastructure in your name
Questions
Worth asking.
Anything else — email hello@haddon.software and a human replies the same business day.
Make it the easiest path. If the portal answers the question faster than an email gets replied to, people switch. We also plan the launch communications, because silence guarantees low adoption.
Handled as a design constraint from the start — authentication, least-privilege permissions, encryption in transit and at rest, and Canadian data residency where required. We document what we did so you can answer a client audit.
That is normally the point — a portal reading live data from your core system rather than a separate copy that drifts out of date.
Then the design constraints are tighter and the payoff is larger, because those are exactly the customers currently phoning you. We test with people at the lower end of the confidence range rather than the higher end.
That is the sensible path. Pick the single most common inbound question, solve that thoroughly, measure whether contact drops, and extend from evidence rather than from a roadmap written before launch.
Related
You might also need…
Want to talk it through?
The first call is free, runs about thirty minutes, and you'll get a straight answer about whether we're the right fit — including when we're not.