Manzar Anjum.

Work/Agency platform

An agency's operating platform, with client portals and a CRM that Claude can work in

An agency wanted one command centre for its team, its clients and its partners. I built the app they sign in to, and each of them sees only what is theirs.

Role
Design and build
Built
2026
Stack
Node.js, OAuth 2.0 with Google, MCP, Caddy, Linux
TeamClientsPartnersOne web appinvites / roles / tenantseach sees only what is theirsGoogle sign-in broker11 products, read or writeCRMClaude works in it via MCPProbetests a connection
Fig. 03 One app for an agency's team, its clients and its partners, and what sits behind the loginDiagram

The problem

An agency's own tools are usually the last thing it builds.

This one wanted its leads, builds, tasks and client work in one place, and its clients' Google access ran through a third party's connector.

What I built

  • Logins, invites and roles.

    Nobody can sign up on their own. People are invited, each with a role, and a session can be revoked. Every protected action checks the role in code.

  • A portal per client.

    Each client is its own tenant and sees only its own connected accounts. Partners get a scope of their own.

  • A sign-in broker for Google.

    Clients connect Gmail, Calendar, Drive and eight more Google products through the agency's own consent screen, with read or write access chosen per product and a Test connection button on each connected product.

  • A CRM that Claude can work in.

    A pipeline board for leads, and an MCP connection so the team can read and update the CRM from Claude Desktop or Claude Code.

How I know it works

  • A connected product can be tested from its own card: a probe reads through the connection once.
  • Releases were walked through signed in, page by page, with screenshots.
  • Client users see only their own integrations page. Internal pages stay internal.

In numbers

  • 11Google products behind one sign-in broker
  • 3kinds of users in one app: team, clients, partners

My part

I designed it and built it, and ran it with the agency's team.

  • Node.js
  • OAuth 2.0
  • MCP
  • Caddy
  • Linux

The agency and its clients are not named, and no screen of the real system is shown: this page is a diagram and a description.