Use case · Client portal

Build a client portal without a developer.

"Quick one - any update on the project?" Every agency and services firm knows that email. The answer already exists in your systems; the client just can't see it. A portal fixes that - and with Chromoly, you describe it instead of hiring someone to build it.

What your generated portal includes

For your clients

  • Login on your domain (portal.youragency.com)
  • Magic-link sign-in - no passwords to support
  • Project status, milestones, deliverables
  • Invoices and documents in one place

For you

  • One system - the portal reads what your team writes
  • Invite clients by email; no per-seat cost
  • Your brand, your colors - Chromoly invisible
  • Notifications when clients view or act

Automation built in

  • Status changes update the client view instantly
  • AI-drafted weekly summaries - you approve, client receives
  • Document upload with structured intake
  • Webhooks to and from your other tools

Security by default

  • Database-level isolation - clients see only their data
  • Full audit trail on every access and change
  • EU-hosted, GDPR-ready, DPA available
  • 24/7 monitoring - issues alert you first

Try this exact prompt

Example prompt - paste it as-is

Build a client portal for a design agency. Internally we track Projects (client, status, milestones, deliverables) and Invoices. Each client should log in via magic link on our own domain and see only their projects: current status, upcoming milestones, files we've delivered, and their invoices with paid/unpaid status. When we mark a milestone complete, notify the client by email. Every Friday, draft a status summary per active project for our review - once approved, publish it to the client's portal.

Preview it working in your browser before paying anything. Then refine in plain language - "add a feedback form on each deliverable" - and the dependency map shows what the change touches before it ships.

Why a portal beats status emails

Status emails are written from memory, sent late, and buried in inboxes. A portal is the system of record made visible: always current because it is the data, not a summary of it. For agencies it also changes the client relationship - delivery looks premium, and "log in and check" replaces three update calls a week. If you're currently duct-taping this with shared spreadsheets or Notion pages, see how Chromoly compares vs Airtable - and if you build portals for clients as a service, the agency comparison is for you.

Frequently asked questions

Can clients log in on my own domain?

Yes - every build deploys to a custom domain with auto-SSL. Clients get magic-link login. Your brand; Chromoly invisible.

Do client logins cost extra per seat?

No. End users are included - flat tiers, credit-metered usage. Five clients or fifty, same subscription.

Is each client's data isolated?

Yes, at the database level via row-level security - enforced by the database, not just app logic. Access is audit-logged, EU-hosted, GDPR-ready.

Can the portal update itself?

Yes - it reads the same entities your internal workflows write. Status changes appear instantly; AI can draft weekly summaries for your approval.

Stop answering "any update?"

Describe your portal in plain language. Working preview in your browser - free tier forever, no credit card.

Start free →

Your domain · client logins included · maintained for life