# Can you build a customer portal without replacing our whole business system?

Canonical URL: https://newphysician.org/can-you-do-this/build-a-customer-portal/

Yes. A portal can expose a carefully selected part of an existing process, such as progress, documents, or requests, while leaving the underlying system in place. The important boundary is what each customer may see and change.

What a solution might involve

Define the customer journey and authoritative source for each field. Add authenticated access, customer-level isolation, clear status explanations, and notifications where useful. Start with the most frequent customer question rather than reproducing every internal screen.

What needs care

Hiding a link is not access control. Customer separation must be enforced on the server, including downloads and exports. Internal notes should not become public by accident, and the design must account for staff changes, revoked access, and incorrect invitations.

How we would judge whether it works

One customer cannot retrieve another customer's records, including by changing a URL. Staff can revoke access. Displayed status matches the source system, and customers understand how to ask for help when the portal does not answer their question.

Likely engagement

Business Engine: $5,000 to $15,000. This is a likely starting tier, not a quote. Scope, access, dependencies, and responsibility for operation need agreement first.

Discuss Business EngineWhat to send first

List the three things customers repeatedly ask for and show a redacted example of the information they should receive.

Send me the messy version.

Experience and scope

Selected builds documents the currently authorized public proof. This page describes a proposed approach, not a claim of a completed client engagement in this exact workflow.

Related problems

Can you replace our email-based intake with a structured system?

Can you make document handoffs less chaotic?



[Send me the problem](https://newphysician.org/send-me-the-problem/)