A customer portal first release opens one job to the outside. Order status, a document download, or a request. All three in the same launch crowd the screen and push an internal note out. The brief names the job the customer already asks for by email.
Pick the sentence you hear
If the sentence is where is the shipment, open status. If it is send the invoice again, open documents. HED Creative reads a month of those emails in discovery and writes one sentence. The second job is named and waits. Discovery can run from Berlin or Ankara.
Who signs in
Each customer account is separate. A shared link is out of release one. The user sees their own order or their own document. Another customer, your margin and the internal note are absent from that login. The first wave is a count you set.
An internal record can exist before the portal. Field work, quotes and dispatch become one record inside. The outside is the field of that record you choose to show.
Fields that stay shut
Cost, the discount rule, a staff note and a draft quote stay shut. The list of visible fields is agreed before build. Without a list, someone guesses a field open. That is not a risk release one accepts.
The record stays inside
The portal does not invent a second order world. The system of record remains the one you already run. The external screen reads it. If the chosen job writes back, it writes to the same identity. Two numbers do not appear.
Name the job on web app development. A dealer order is one kind of door: a dealer order screen. The team that keeps the door after launch is a software partner.