Every morning at 6:00 AM Pacific, before I've poured my first coffee, my AI agent has already reviewed every open pull request across 8 client repositories, summarized overnight Slack conversations by client, checked uptime on every production site, audited 7,247 Contentful entries for stale drafts, and queued a prioritized briefing in my DMs. By the time I sit down, I have the situational awareness that used to require a project manager, a DevOps engineer, and a very caffeinated Slack monitor.
This is the Command Center — the operational dashboard I built with Alpha Agent to run Last Rev's day-to-day operations. It's not a concept deck or a demo. It's the actual system I use every day to manage a digital agency with enterprise clients, a distributed engineering team, and a pipeline of inbound leads — mostly by myself.
If you're a COO, ops leader, or solo founder wondering how to scale without adding headcount, this is the playbook.
Running a services company means living in a dozen tools simultaneously. GitHub for code. Slack for communication. Contentful for CMS health. Google Analytics for traffic. Zoom for meetings. A CRM for leads. Uptime monitoring. Deployment dashboards. Calendar for scheduling. Each tool has its own notification system, its own dashboard, its own mental model.
The result? Context switching becomes your full-time job. You're not doing ops — you're checking things. A study by Qatalog and Cornell found that workers spend 59 minutes per day just searching for information across disparate tools.1 For an ops leader managing 8+ platforms, that number is conservative.
I needed a single pane of glass. Not a BI dashboard that required manual data entry — a living system that pulled data from every source, applied intelligence, and surfaced only what mattered.
The Command Center is a custom web application built with Web Components, backed by Supabase for real-time data, and powered by Alpha Agent's AI agent for automated analysis. It's organized into five operational tabs:
The Admin tab is where I start every morning. It contains four modules that give me an instant pulse check:
trigger_queue table. If a client sends a Slack message that needs follow-up, if a PR needs review, or if a content audit flags something — it hits the queue. I can see pending, processing, and completed items at a glance.The Code tab gives me full visibility into our engineering output:
This is where the Command Center earns its keep. The Client Health tab synthesizes multiple data sources into a single health score per client:
/blog/nextjs-tips post recently did), I know to amplify it. No more logging into GA4 and squinting at charts.The Financial tab connects to our lead management system:
Even the personal tab has a purpose: a curated news feed, weather briefing at 6 AM PT, and a daily dev journal generated at 6 PM PT that captures what was accomplished, what's pending, and what needs attention tomorrow. It's the async standup I give to myself.
The Command Center isn't just a dashboard — it's an operating system. Behind the UI are 63 scheduled jobs that continuously feed it data, run analyses, and take action. Here's how they break down by category:
| Category | Jobs | Examples |
|---|---|---|
| 35 | PR/Review/Merge cycle, DRY audit, UX review, per-app code reviews for 20+ apps | |
| 5 | Trigger queue processor (every 1 min), Command Center refresh (every 30 min), Kanban worker | |
| 4 | GitHub PR review check (hourly), weekly PR triage & stale nudger, backlog meeting prep | |
| 4 | Hourly idea generation, skill ideas, weekly web search discovery | |
| 4 | Weather (6 AM), Slack summary by client (6:30 AM), today's meetings (7 AM), daily dev journal (6 PM) | |
| 2 | Lead research calendar scan, DMC research | |
| 1 | Weekly memory hygiene — consolidates AI context files | |
| 8 | Recipe audit & discovery, nightly brainstorm, meme trend refresh, reminders |
The most critical job is the Trigger Queue Processor, which runs every 60 seconds. It polls a Supabase table for pending tasks — anything from "summarize this Zoom recording" to "research this lead" to "deploy this app" — processes exactly one per cycle, and delivers results to Slack. It's the nervous system that connects everything.
Let me walk through an actual morning — today, February 18, 2026:
The technical stack is deliberately simple:
cc-prs, cc-client-health, cc-ga4-alerts, cc-leads, cc-uptime, cc-slack, cc-calendar, etc.) is a self-contained custom element that fetches its own data and renders independently. 27 modules total.sql-sync.js library keeps the frontend in sync.command-center.example.alphaclaw.app. No server. No SSR. Loads in under 1 second.This architecture means the dashboard is indestructible. If a cron job fails, the dashboard shows stale data with a timestamp — it doesn't crash. If Supabase goes down, the JSON files still load. If the AI agent is offline, the last-known-good data persists.
Let's be explicit about the headcount math. Before the Command Center, achieving this level of operational awareness would require:
| Role | What the Command Center Replaces | Estimated Annual Cost |
|---|---|---|
| Project Manager | Client health monitoring, PR triage, blocker escalation, meeting prep | $85,000–$110,000 |
| DevOps Engineer (part-time) | Uptime monitoring, deployment tracking, Lighthouse audits, dependency updates | $60,000–$80,000 |
| Marketing Analyst | GA4 monitoring, content audit, traffic anomaly detection, lead enrichment | $65,000–$85,000 |
| Sales Ops Coordinator | Lead research, CRM maintenance, meeting prep, pipeline reporting | $55,000–$70,000 |
| Executive Assistant | Calendar management, Slack monitoring, daily briefings, follow-up tracking | $50,000–$65,000 |
| Total replaced capacity | $315,000–$410,000/yr | |
I'm not saying fire people. I'm saying that if you're a 10-person agency or a solo founder, you can't afford those five roles. But you still need that operational coverage. The Command Center gives it to you for the cost of a Supabase free tier and an Alpha Agent subscription.
If you want to build something similar, here's what I've learned:
Don't try to build the whole dashboard on day one. Start with one cron job: a morning Slack summary. Once you taste the productivity gain of walking into your day with full context, you'll be motivated to add more modules.
The Command Center uses vanilla Web Components. No framework. No build step. No dependency hell. Each module is a single JavaScript file that fetches JSON and renders HTML. This sounds primitive, but it means any module can be written, tested, and deployed in 15 minutes. The 27 modules in our dashboard are all under 200 lines each.
Not everything needs to be real-time. Client health scores update every 30 minutes. PR data refreshes hourly. GA4 alerts run daily. The only real-time component is the trigger queue (every 60 seconds). Match your refresh rate to the decision cadence — most operational decisions don't need sub-second data.
The simplest integration pattern: a cron job runs, the AI analyzes something, and it writes a JSON file. The dashboard reads the file. No API authentication, no webhook configuration, no error handling for failed API calls. Just files. It's old-school and it works beautifully.
The Command Center uses exactly three alert colors: green (healthy), amber (needs attention), and red (act now). Every module speaks this language. When I glance at the dashboard, I don't read — I see colors. If everything is green, I move on. A red dot anywhere gets 100% of my attention.
Here's what surprised me most: the Command Center gets more valuable over time, not less. Each new cron job adds another data stream. Each new module creates another lens into the business. The nightly brainstorm agent (running at 4 AM PT) generates ideas that reference patterns spotted by the client health module. The lead enrichment system uses talking points informed by our Contentful audit findings. The whole system cross-pollinates.
After three months of operation, we have:
I think so. The traditional model — hire specialists, hold meetings, aggregate information manually — doesn't scale for small teams. And most "dashboarding" solutions (Datadog, Grafana, Tableau) require you to know what you're looking for. The Command Center is different because the AI decides what to surface. I didn't write a query for "flag when a client has 13 stale PRs." The client health module noticed the pattern and raised the alert.
This is the shift from passive dashboards (you look, you find) to active dashboards (it looks, it tells you). And it's available today, not in some future product roadmap.
If you're an ops leader drowning in tabs, or a founder who's been putting off hiring a PM because the budget isn't there — let's talk about building your Command Center.