Project status
Current stage, progress, next action and important dates in one understandable view.
CUSTOMER PORTALS & DASHBOARDSGive every project
Give every project
one place to live.
Simple account foundations only at add-on levelSubstantial portals are custom scopedMulti-company platforms use advanced pricing
Portals are most useful when they reduce fragmented communication: project state, approvals, messages, files, invoices and support can share the same authenticated customer context.
CUSTOMER SIDEShow the right information.
Show the right information.
Protect the rest.
A portal should not expose the whole database. Each customer should see only the projects, files, approvals, payments and Care information they are authorised to access.
Approvals
Design, content or launch decisions stay attached to the correct project and version.
Messages & files
Keep project communication and customer-supplied material connected to the work.
Quotes & payments
Show approved commercial information and payment state without mixing customers.
Care Centre
Health, requests and ongoing support can continue after launch.
Admin control
The business sees the operational view, queues and priority signals customers do not need.
WHEN A PORTAL IS WORTH ITUse accounts when the relationship
Use accounts when the relationship
continues after the form.
A login is not automatically valuable. It becomes useful when customers return to check status, approve work, upload information, pay, request support or manage an ongoing service.
01
Projects last for days or weeks
A portal gives the customer a stable place to see what is happening instead of asking for updates through separate messages.
02
Approvals affect the next stage
Structured approval records reduce ambiguity around which version was accepted or what change was requested.
03
Customers return after launch
Care, subscriptions, support or recurring service can justify a persistent account experience.
04
The admin side needs a different view
The client sees their own project; the business sees queues, scheduling, financial state, operational signals and exceptions.
SECURITY PRINCIPLELogin is only the front door.
Login is only the front door.
Permissions do the real work.
Authenticated accounts still need project ownership checks, role separation and protected admin actions. Sensitive admin operations should not become accessible just because someone is signed in.
CLIENTSee only authorised project data.
ADMINSeparate privileged operations
Operational controls stay behind admin authorization.
RECORDSOne source of truth
Approvals, files and payments stay attached to the right project.
CAREContinue after launch
Ongoing service remains inside the customer relationship.
QUESTIONS
Before adding customer accounts.
No. If the relationship ends after an enquiry or purchase, a portal can add unnecessary cost and friction. It is most valuable when customers return for project status, files, approvals, payments or ongoing service.
Yes. The public website, client portal and admin dashboard can share project data while presenting different permissions and interfaces to each role.
Only when it is a tightly bounded foundation on a supported website. A substantial portal with several user types, business workflows, reporting or custom integrations is a custom software project and the estimator will move it above ordinary £599 website territory.
Yes. A legacy project can be imported and linked after the customer registers and the prior-work claim is reviewed, rather than automatically granting access from an email match.