Unseen Engine
All case studies

Agency Operations / Client Portal

Client OS

Unseen Engine's own app for running client work — every prospect and client on one hub, from the first website request to approval, with agents that draft and a person who releases.

Client OS

Client OS, the product we built

The challenge

Unseen Engine ran each client by hand. The work sat in a notes vault, Gmail, Stripe scripts, Figma, and email, and nothing moved unless Emmanuel opened a terminal. He counted about 20 hours spent collecting and sharing updates, answering email, and keeping up with prospects — none of it building.

Clients could not see where their project stood, and every agent started cold because the context lived in files, not in a record it was given.

Our solution

We built Client OS as one hub per client: an admin app that holds every prospect and every client, and a signed-in portal where each client sees only what has been released to them.

A request on myunseenengine.com files straight onto a prospect's hub. The audit and intro-call chats collect the details, book the call, and open the client's portal with the answers saved.

Agents draft; a person releases. No draft reaches a client until someone releases that version, an approval is the signed-in client's act on one version, and an agent may draft only when its latest eval scores 100%.

Technology used

  • FastAPI
  • Next.js
  • PostgreSQL
  • gRPC agent server
  • AWS Fargate
  • Vercel
  • Resend

The results

  1. Live at app.myunseenengine.com, with the server on AWS in the United States.

  2. Every request from myunseenengine.com now lands on a hub, not an inbox.

  3. Built test-first: each ticket's acceptance criteria are tests approved before the code, and every change passes the same checks locally and on GitHub.

Start a similar project

Let's discuss how we can deliver similar results for your business.