Architecting a Zero-Maintenance Command Center
There is a predictable lifecycle for internal operations in growing agencies: You start with a spreadsheet. The spreadsheet breaks. You buy a bloated CRM SaaS product. You spend months configuring it. Then you realize you're paying thousands of dollars a year for a tool where you only use 10% of the features, and your team hates logging into it.
When managing leads across our core business pillars (Launch, Strategy, and Trademarking), I refused to fall into that trap. Operating under the Discipline of Not Building, the goal was to avoid writing custom software unless absolutely necessary. However, relying on disconnected third-party subscriptions creates administrative drag.
The solution was a middle ground: a Zero-Maintenance Command Center built on Next.js, Supabase, and Resend.
The Tech Stack for Lean Operations
We needed an internal CRM that was highly specific to our workflows, completely secure, and required zero infrastructure maintenance.
- Compute & UI: Next.js (App Router) deployed on Vercel.
- Database & Auth: Supabase. This provides a managed Postgres database, Row Level Security (RLS) to ensure data privacy, and built-in authentication.
- Communications: Resend. A developer-first email API for managing inbound leads and automated outbound responses.
Decoupling the CRM from SaaS Bloat
Here is how we architected the system to bypass traditional CRM limitations:
1. Supabase as the Single Source of Truth Instead of syncing data between Webflow forms, Zapier, and HubSpot, we route everything directly into Supabase. Every lead for Launch, Strategy, or Trademarking hits a specific Postgres table. By utilizing Supabase's Edge Functions, we can trigger background tasks immediately upon lead creation without managing a separate server.
2. Next Auth + Row Level Security (RLS) Security in internal tools is usually an afterthought. By pairing Next Auth with Supabase RLS, we ensure that team members only see the leads relevant to their specific pillar. A strategist cannot accidentally access or alter a trademarking lead.
3. The Integrated Resend Inbox The biggest failure of most internal CRMs is forcing users to switch contexts to check their email. By utilizing Resend's API, we built a custom inbox directly into our Next.js dashboard. Resend provides observability features like delivery, bounce, and complaint tracking.
This setup acts as an automated triage system. When a new lead submits a form, Resend parses the data, Supabase stores it, and the Command Center surfaces it.
By building exactly what we needed (and nothing we didn't) on serverless infrastructure, we created a Command Center that scales infinitely, costs fractions of a penny to run, and requires zero DevOps maintenance.