Built for your business
Client Portals
Give customers a private place to follow the work you are doing for them. A client portal can bring updates, messages and documents together without turning your public website into a shared filing cabinet.
Request a quoteWhat a client portal is
A client portal is a signed-in area where a customer can see information related to their own work with your business. Instead of searching through separate email threads for the latest update, they have a place to return to. The public website explains your services; the portal supports the relationship once someone becomes a customer.
The useful parts depend on your business. You might want customers to check project progress, exchange messages or download documents. Those are options to discuss, not a promise that every portal needs every feature. We define what your team manages, what customers can see and what should remain private before agreeing on the build.
Who a client portal is for
A portal can suit a small business with work that continues across several conversations or stages. Contractors, property businesses and professional service providers may have updates and documents that customers need to revisit. If your team often resends the same information, a shared project view may be worth discussing.
It is not always the right first step. If customers only need a telephone number and a short enquiry form, a clear public website may be enough. Tell us how you communicate now, who handles customer questions and where information gets lost. We can help separate a genuine customer need from a feature that would add more work for you to maintain.
What is included in the portal scope
We agree on the customer sign-in journey, the information each account can access and the tools your team needs to keep it current. Project updates, messages and private files can be included where they fit the agreed scope. Access needs to be considered for the information itself, not just for what a screen happens to hide. We review those boundaries as part of the build.
The surrounding project includes mobile-friendly design, a private project portal for working with us, a handover guide and walkthrough, and 30 days of support after launch. Your quote describes the actual customer portal functions and any connection to your existing website. If you already have customer records elsewhere, tell us what can be exported. Data migration is discussed and scoped before anything is moved; you review the result before launch.
How discovery, design, build, launch and support work
Discovery begins with a real example of how a customer moves through your business. We identify the stages, the information being exchanged and the people who need access. Then we agree on scope and a quote. During design, we map the customer view and the working view for your team so each side has the information it needs without unnecessary clutter.
During the build, you review a preview and try the agreed customer tasks. We check sign-in, access boundaries and the planned message or file flows before launch. Handover puts the code and accounts in your name, with full ownership transferring after final payment. The first 30 days of support cover fixes to work as built and small text or photo changes. Larger changes and new features are quoted separately; ongoing care is optional.
Frequently asked questions
Can each customer have their own private view?
Yes, a portal can be scoped so each signed-in customer sees the information assigned to them. We agree on access rules and check them as part of the build rather than relying only on hidden links or screens.
Can the portal work alongside my public website?
Yes. Tell us how your existing website is managed and what you want customers to do after signing in. The quote will explain how the public site and portal fit together and any work needed to connect them.
Can we bring records from another system?
We can discuss migration using data you provide and have permission to use. Tell us the current system, available exports and what needs to move. The scope is agreed first, and you review the imported data before launch.
Who owns the portal after handover?
You own the source code and your accounts after final payment. We provide a handover guide and walkthrough. Support for the first 30 days covers fixes to work as built and small text or photo changes; ongoing care is optional.