A customer portal for shared work, requests and updates.

Choose the job the portal must do

A portal might show project milestones, collect a customer request or share approved documents. Define the smallest useful journey first: who signs in, what they see, what they can change and who responds.

An illustrative renovation portal could show approved milestones and let a customer request a change. That does not automatically include scheduling, payments, document signing or integration with your project software. Each needs its own scope.

When existing software is the better fit

If your project-management or customer-service software already provides the required roles and workflows, configuring it may be simpler than building a separate portal. Compare the subscription, export options, customer experience and constraints before commissioning custom software.

A custom build becomes worth investigating when the required journey cannot be configured reliably, several systems need an agreed connection, or the customer experience needs substantial tailoring. Discovery should establish that need rather than assume it.

Access and data isolation are project requirements

Agree authentication, account recovery, customer and staff roles, and what happens when access is removed. Define how records belonging to one customer are isolated from another. Role checks need to be enforced on the server, not just by hiding buttons.

Document sharing needs rules for file types, permissions, retention and deletion. A backup plan should specify coverage, recovery steps and who tests restoration. These are requirements to design and verify for each project, not a security certification for every future portal.

• Customer, staff and administrator permissions.
• Data sensitivity and minimum required collection.
• Session handling, account recovery and access revocation.
• Retention, export, deletion, backups and incident responsibilities.

Bring the systems and constraints into discovery

Identify where the source records live, which system remains authoritative and whether the provider permits the required API access. We need to understand sync frequency, error handling and conflicts before promising a connection.

Use anonymized examples for initial discussions. Do not upload regulated or sensitive customer data to a prototype. Requirements involving health, financial or other regulated data need separate assessment; no HIPAA, SOC 2 or other compliance claim is made here.

What drives the scope and quote

Portal development is separately quoted. Scope depends on roles, authentication, data models, workflows, integrations, file handling and the amount of administration required. A portal is not included in the $899 informational website package.

Hosting, storage, email providers and third-party subscriptions have ongoing costs. Agree budgets, maintenance, ownership and handover responsibilities in writing. Custom deliverables transfer after full payment; provider licences and accounts remain subject to their terms.

Start with a short portal brief

Describe the customer task, the staff task and what information each role needs. List your current tools and the point where the process breaks down. We can then discuss whether an existing product, a small integration or a custom portal is appropriate.