The Command Center Every Agency Client Deserves.
How we built a multi-tenant client portal that gives every Automaton client a single branded view of strategy docs, pipeline metrics, approvals, and invoices — without a single status-update email.
The Problem
Delivering fractional CRO and strategy work over email and scattered tools gave clients no unified view of what's new, what's urgent, and what needs their approval. Important documents got buried in threads. Pipeline data lived in HubSpot, not in the client's hands.
The overhead of keeping clients informed was eating into the time available to do the actual work. And clients who felt uninformed — even when work was progressing well — felt anxious.
What We Built
We shipped a multi-tenant Next.js portal on Supabase with Row-Level Security, so each client sees only their organization's data. Magic-link authentication means no password friction.
The portal surfaces strategy documents with scroll-tracked review and approval workflows, pipeline snapshots, market intelligence reports, PR proposals, onsite training schedules, and invoices — all in one branded command center.
“Clients shouldn't have to ask what's happening. They should be able to open a tab and know. That's what the portal is.”
The System Architecture
Next.js application on Vercel. Supabase with Row-Level Security for multi-tenant data isolation. Magic-link auth via Supabase Auth. Multi-format document viewer with scroll-tracking and approval state machine. HubSpot pipeline snapshot integration. Admin panel for org management, document upload, feature toggles, and invoicing.
The Results
Every active Automaton client has a single place to see what's happening, what needs their attention, and what's been completed. The approval workflow reduced back-and-forth on document reviews from days to hours.
Internally, the portal eliminated the overhead of client update emails. Status is always current. Context is always available.