Guides
What belongs in a client portal for a web design agency
Which records a web design agency should put in a client portal, which to keep out, and who gets access, from signed scope to freelancer roles.
What to take away
- Anything a client may need to look up six months from now goes in the portal.
- Signed scope, file versions, and approval timestamps belong inside.
- Rate talk, negotiation, and internal critique stay outside.
- Invite only the people who can approve, and give a freelancer a limited role.
- Build the space before the kickoff call, not after it.
The six-month rule for portal content
One rule decides what a client portal holds: anything a client may need to look up six months from now goes in. Everything else stays in the agency's own tools. A new project manager can apply that rule on day one without asking anyone.
What belongs in the portal
Put it in the portal
- Proposal
- Signed proposal and scope table
- Designs
- Wireframes and comps, listed by version
- Changes
- Change orders with dates and hours
- Launch
- Launch checklist and QA results
- Support
- Support terms and response windows
Keep it out
- Proposal
- Internal rate cards and margin math
- Designs
- Designer critique threads
- Changes
- Subcontractor names and staffing plans
- Launch
- Draft pricing for later phases
- Support
- Anything under an NDA
| Record | Verdict | Why |
|---|---|---|
| Signed proposal and scope table | Put in | The client can check what was agreed |
| Wireframes and comps, listed by version | Put in | Nobody guesses which comp is current |
| Change orders with dates and hours | Put in | Each request sits beside the agreement it changes |
| Launch checklist and QA results | Put in | The client can reread what was tested |
| Support terms and response windows | Put in | The promise is written where the client looks |
| Internal rate cards and margin math | Keep out | It is the agency's own working, not the client's |
| Designer critique threads | Keep out | They were written for the team |
| Subcontractor names and staffing plans | Keep out | They are internal arrangements |
| Draft pricing for later phases | Keep out | Nothing has been agreed yet |
| Anything under an NDA | Keep out | The portal is not the place to share it |
The keep-out rows are where agencies get into trouble, because a forwarded thread can be read out of order. A client who sees a rate card or a critique thread without its context can misread it. Leaving those rows out protects the relationship as much as the margin.
Why an inbox cannot hold those records
An inbox cannot hold these records because it has no login, no permission list, and no named approver. Email works until the third revision. After that, attachments multiply and nobody is sure which comp is current, while a portal keeps one version history per file.
Portal vs email records
Client portal
- Login
- Yes
- Permission list
- Yes
- Named approver
- Yes
- Version history
- One per file
Email inbox
- Login
- No
- Permission list
- No
- Named approver
- No
- Version history
- Attachments multiply
Most US agencies do not build a portal. They configure tools they already pay for, such as Basecamp, Notion, ClickUp, Asana, Trello, Dubsado, SuiteDash, Copilot, or the client area inside Harvest. Whichever tool an agency picks, the list above decides what goes into it.
Who gets access
Give access by role, starting with approvers. Invite only the people who can approve, and label each one as an approver. The portal then shows who agreed to what, which a reply chain with several recipients does not make clear.
If a freelancer needs portal access, give them a limited role. Whether that person is a staff member or a contractor changes payroll and tax handling, and the IRS criteria for independent contractors set the test. The 1099 rules cover the filing side.
Opening the space before kickoff
Open the space before the kickoff call, so the client arrives to a finished page rather than an empty one. Five steps cover it.
- Create the client space and name it with the project code your team already uses.
- Add the signed proposal, the scope table, and an empty change order template.
- Open a brand assets folder with a short written list of what you still need.
- Invite the approvers first, then any limited guests.
- Record a five minute walkthrough and pin it at the top of the space.
Agencies that repeat this structure for every new client spend less time on the first call. The client gets one link instead of six email threads. The wider first weeks sit in the onboarding checklist for small teams.
Change orders, hours and support terms
A portal turns a scope argument into a document. When someone asks for an extra page, the request lands in the portal instead of a reply chain, and the agency opens the scope table to count the revisions already used.
The answer becomes a change order with hours attached, not a debate about who said what in March. The client approves it in the portal, and the timestamp answers any later question about why the launch date moved.
Pull time entries into the portal so clients can check hours without sending a status email. Time tracking is standard practice in professional services, and clients read logged hours as evidence rather than pressure. For maintenance work, publish response windows in the same place, so the client has something to reread on a Sunday night.
