Before I've had my first cup of coffee, my AI agent has already reviewed every open PR across 8 client repos, summarized overnight Slack threads by client, checked uptime on all our production sites, audited over 7,000 Contentful entries for stale drafts, and dropped a prioritized briefing in my DMs. I sit down and I already know what's going on. That used to take a PM, a DevOps person, and someone whose entire job was monitoring Slack.
I call it the Command Center. I built it with Alpha Agent to actually run Last Rev's operations — not as a proof of concept, not as a demo for a sales deck. This is what I open every morning to manage our agency, our clients, our engineering team, and our pipeline. Mostly by myself.
If you run ops at a small company, or you're a founder doing way too many jobs at once, this is what I'd tell you to build.
You know the drill. GitHub for code. Slack for everything else. Contentful for CMS stuff. GA4 for traffic. Zoom for meetings. Some kind of CRM. Uptime monitoring. Deployment dashboards. Calendar. Every single one has its own notifications, its own UI, its own way of showing you things.
At some point you realize you're not actually doing ops — you're just checking things. Qatalog and Cornell did a study that found people spend about an hour a day just searching for information across their tools.1 If you're managing 8+ platforms, it's way more than that.
I needed one place to look. Not a BI tool where I have to manually set up reports — something that pulls from everywhere, figures out what matters, and just shows me.
It's a web app — Web Components, Supabase for the data, Alpha Agent running the analysis in the background. Five tabs. Here's what's in each one.
Four things I check first:
Each client gets a health score pulled from multiple sources:
News feed, weather at 6 AM, and a daily journal at 6 PM that captures what got done, what's still pending, and what needs attention tomorrow. It's basically a standup I give to myself.
The dashboard is just the front end. Behind it are 63 scheduled jobs that keep everything fed with data:
| 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 important one is the Trigger Queue Processor. Runs every 60 seconds. Picks up tasks — "summarize this Zoom recording," "research this lead," "deploy this app" — processes one per cycle, and sends results to Slack. It's what connects everything together.
Here's an actual morning — February 18, 2026:
The tech stack is simple on purpose:
cc-prs, cc-client-health, cc-ga4-alerts, etc.) is its own custom element. Fetches data, renders itself. 27 modules total.The nice thing about this architecture: it's basically indestructible. If a cron fails, the dashboard shows stale data with a timestamp — it doesn't crash. If Supabase goes down, the JSON files still work. If the AI agent is offline, you still see the last-known-good state.
Here's the honest math. To get this level of awareness without the Command Center, you'd need:
| Role | What It Handles | Annual Cost |
|---|---|---|
| Project Manager | Client health, PR triage, blocker escalation, meeting prep | $85K–$110K |
| DevOps Engineer (part-time) | Uptime monitoring, deploy tracking, Lighthouse, dependency updates | $60K–$80K |
| Marketing Analyst | GA4, content audits, traffic anomalies, lead enrichment | $65K–$85K |
| Sales Ops | Lead research, CRM, meeting prep, pipeline reports | $55K–$70K |
| Executive Assistant | Calendar, Slack monitoring, briefings, follow-ups | $50K–$65K |
| Total | $315K–$410K/yr | |
I'm not saying you should fire anyone. I'm saying if you're running a 10-person shop or you're a founder wearing too many hats, you probably can't hire for all five of those roles. But you still need that coverage. This gives it to you.
Don't try to build the whole thing at once. Set up one cron job that summarizes your Slack channels every morning. Once you see how much time that saves, you'll want to add more.
We use vanilla Web Components. No framework. No build step. Each module is a single JS file that fetches JSON and renders HTML. Sounds basic, but any module can be written and deployed in 15 minutes. All 27 of ours are under 200 lines each.
Client health updates every 30 minutes. PR data refreshes hourly. GA4 runs daily. The only thing that's truly real-time is the trigger queue at 60 seconds. Match your refresh rate to how fast you actually make decisions.
Simplest pattern there is: cron runs, AI does its thing, writes a JSON file. Dashboard reads the file. No API auth, no webhooks, no error handling for network failures. Just files. Old-school and it works great.
Three colors: green (good), amber (look at this), red (fix now). Every module uses the same language. When I glance at the dashboard, I'm not reading — I'm looking for color. All green? Move on. Red anywhere? That gets my full attention.
The thing that surprised me most: it compounds. Every new cron job feeds more data in. Every new module gives you another angle on the business. The nightly brainstorm agent generates ideas based on patterns the client health module spotted. The lead enrichment pulls from findings in the Contentful audit. Everything starts connecting to everything else.
After three months:
I think so. The old model — hire specialists, have meetings, manually pull data together — just doesn't work for small teams. And most dashboard tools (Datadog, Grafana, Tableau) need you to already know what to look for. The difference here is the AI decides what to surface. I didn't write a rule that says "alert me when a client has 13 stale PRs." The system noticed the pattern and told me.
That's the real shift. Going from dashboards where you have to look and find things, to a system that looks for you and tells you what needs attention. And this isn't some future thing — it's what I'm using right now.
If you're drowning in tabs and you've been putting off hiring because the budget isn't there — let's talk about building yours.