Feature one
Customer portals
A logged-in space where customers submit, track, review and collect, connected to the systems where the truth is kept.

What a portal from us contains
Every portal starts with the same small set of questions: who logs in, what do they come to do, and where does the answer live today. From there we decide the screens. Most of our portals include some combination of the following.
- Request intake
- Structured forms that turn a customer's request into a complete brief: deliverable type, deadline, audience, reference files, budget owner. Conditional questions keep it short.
- Tracking
- A list of the customer's requests with status, owner and next step, drawn from your project system rather than maintained by hand.
- Review and approval
- Versioned proofs with comments attached to a specific version, a clear approve or request-changes action and a recorded decision.
- Library
- Approved assets, templates and guidelines, filtered by brand, region or product, with only current versions available to download.
- Accounts and roles
- Invitations, organisation-level access, and roles such as requester, approver and viewer. Optional single sign-on where your customers need it.
- Notifications
- Email at the moments that matter, such as needs your approval or ready to download, and no others. Every notification links to the exact item.
What we need from you
Real examples of requests, the current list of statuses your team uses (even if informal), access to a test environment of the systems we connect to, and a named product owner who can make decisions within a working day or two. Without that last one, projects slow down regardless of who builds them.
Tradeoffs worth deciding early
Build on your project tool, or alongside it? Writing statuses back into your existing tool keeps the team in one place but ties the portal to that tool's API limits. A separate data store is more flexible but means two places to look. We set out both with costs.
Customer self-registration or invitation only? Invitations are slower to roll out but give you control. Self-registration needs domain verification and moderation.
Single sign-on. Valuable for large customers with their own identity provider, unnecessary overhead for small ones. It can be added later if the account model is designed for it.
What you receive
- The working portal in your hosting account
- Source code in your repository, with a readme a new developer can follow
- An admin guide for your team and a short help page for customers
- A written record of integrations, credentials ownership and data flows