The client portal we built for ourselves, then ran the agency on
An in-house agency-to-client portal on NestJS and Next.js: boards from milestone to subtask, deliverable reviews, and client rooms that show only what's been shared.
01The challenge
With seven client engagements running across brand, build and campaigns, status sat in chat, files sat in Drive, and approvals sat in someone's memory. No tool we could buy let a client see exactly what we chose to share and nothing more, so we built one.
02Our approach
Start from our own workflow
The scope came straight from how the agency already works: projects, milestones, tasks, deliverables and approvals.
Two surfaces, one product
The team works in an internal board; clients get a portal limited to the work that has been shared with them.
A layer for selling it
Companies, plans, seats and trials sit above the workspace, so the product can be sold as well as used.
Run on it every day
Every Forjwell engagement moved onto the portal, which is how its gaps were found and closed.
03Inside the work
04What ships on forjwellone.com
- Internal BoardProject down to subtask
- Client PortalOnly what has been shared
- Sign InInvite-only access
- ProductWhat the portal does
- AboutBuilt for bolder brands
- ContactSay hello
05The outcome
Forjwell One is live at forjwellone.com and runs every Forjwell engagement. Each client sees their own projects, the work marked visible and the deliverables sent to them, and nothing beyond that.
