Have a customer portal built — with roles, not chaos.

Externals should only see and do what they may; your team still needs the full ops view. We build customer and partner portals as lean web apps: login, roles, files, status, next steps — planable for mid-market and B2B teams.

  • Customer · partner portal
  • Roles & rights
  • For companies · scoped
Why this exists

Why email attachments and shared folders fail

Cost of the status quo

Once customers or partners collaborate, versions multiply, approvals blur, and support calls pile up. A portal only works if roles and status are designed first — not bolted on later.

What “done” looks likeA portal where externals see their status and tasks — and your team keeps oversight without shadow IT.
When a portal is worth it

B2B services, trades with project status, partner networks: recurring uploads, approvals, and follow-ups with the same pattern.

Not for you if…

  • You want a full CRM/ERP replacement.
  • Every customer has a totally different process.
  • You expect unlimited self-service without an MVP cut.
  • A public marketing site is the real goal (→ web design).
Use cases

What a solid portal covers

Fewer features, more clarity. Typical MVP building blocks:

/ 01

Access & roles

Customer, partner, internal — separate views, no accidental admin rights.

  • Login / invite
  • Role matrix
  • Least privilege
/ 02

Cases & status

Every case has a state: new, in review, approved, done.

  • Queue
  • Notifications
  • History
/ 03

Files & evidence

Uploads attach to the case — not scattered mailboxes.

  • Upload rules
  • Versions
  • Approval context
/ 04

Internal ops view

Team dashboard alongside the customer view — no double entry.

  • Filters
  • Assignment
  • Export
Delivery

Delivery via dashboard

Request, scope, milestones, and acceptance run in the customer dashboard — same model as all SHELL-AFFECT web apps.

In the package

Typically in scope

01
Core

Portal with roles

Auth, views, cases, and UI for the agreed path.

02
Included

Dashboard project ops

Transparent milestones and acceptance.

03
Optional

Security follow-on

CASP/review when identities and sensitive files matter.

04
Out

Marketplace platform

No multi-vendor marketplace or unscoped feature pile.

Steps

Four steps to a portal MVP

01

Actors & rights

Who may see and trigger what — written in the briefing.

02

MVP cut

One core path live; nice-to-haves as phase 2.

03

Build & review

Reviews with real test users, not only mockups.

04

Acceptance & handover

Checklist, access, docs — your team runs it.

Security

Access is security

Portals touch identities and often confidential files. We build with clear roles; reviews stay separate scopes — honest and optional.

  • Roles and admin paths in scope
  • No “enterprise secure” label without a review scope
  • Link to the cyber security overview
FAQ

Common questions

Customer portal or employee portal?

Same logic (roles + cases). Often we start with the external path; internal admin view ships in the same MVP or phase 2.

What does a portal cost?

Depends on scope — typically custom entry pricing. Orientation under Pricing; concrete band after dashboard briefing.

Do you also build the public company website?

Yes via web design — separate from the portal build so marketing and login surfaces stay clean.

Next step

Describe who should log in — and why.

Structured dashboard request: actors, rights, files, MVP cut.

Scoped process · dashboardNext step
Request a portal