Managing Partner
Lives in the dashboard.
Morning check: what's at risk. Dispatches assignments. Reviews status check responses. Sees workload before assigning.
AeroLex / Product suite / Command Center
Command Center.
Real-time engagement visibility with assignment dispatch. Partners see every active engagement on one screen (who's on it, what's overdue, what's stalled) and turn the dashboard into how work gets assigned, acknowledged, and closed.
Wave 01 / 04 · in active build · ETA Q3 2026
§ 01 — The problem
Engagement state lives in five places at once. None of them talks to the others.
In a firm of 10, 20, or 50 people, engagement state lives across Slack threads, partner inboxes, meeting notes nobody filed, half-updated spreadsheets, and individual heads. Partners reconstruct it by asking the same five questions every Monday.
Project management software solves a different problem. It tracks tasks. Engagement health is a separate layer that PM software was never built for. It tells you what's open; it doesn't tell you what's stalled, who hasn't acknowledged an assignment, or what's blocked waiting on something else.
Command Center is built for the second question. It assumes you already have email, Slack, and a calendar, and it routes through them instead of replacing them.
§ 02 — What it does
What Command Center does, in plain terms.
§ 02.1 Visibility
See every active engagement, with status auto-calculated.
Engagement state is computed from real activity: last action, next deadline, hand-off log. The status is generated from observable signals rather than partner self-reports. Three states surface immediately:
- AT_RISK: next action overdue by 48+ hours
- STALLED: no activity in 7+ days
- ACTIVE: on track
Partners see this in five seconds without chasing anyone.
§ 02.2 Dispatch
Assign work, get acknowledgment, track follow-through.
Open an engagement, create a next action, assign it. Notification routes to the consultant via email (Wave 1) or Slack/Teams (Wave 2a) with full engagement context attached. The consultant responds with one of five options:
Accept
I own this, starting now.
Accept (need help)
I'll do it but need someone else involved.
Accept (later date)
I'll take it, just not by that deadline. Here's when.
Decline
I can't or shouldn't own this. One sentence why.
Request call
I need to talk before I accept. Pause this item.
All responses log to the dashboard. Nothing sits in limbo silently.
§ 02.3 Workload
One page showing who has capacity, before you assign.
Every consultant, their active assignments, and their combined allocation percentage on one screen. Partners see at a glance who has room before dispatching work, instead of finding out after the fact that someone is at 130%.
§ 02.4 Status checks
Async standups with one-tap responses.
Admin sends a structured prompt. Consultant taps once.
Status check: TechCorp Operations Audit
Sent by Sarah Chen · Tuesday 9:00am
[On track] [Need more time] [Blocked] [Need to talk]
If "Blocked" or "Need to talk" → one-sentence follow-up. Admin sees aggregated: "4 of 5 on track, 1 blocked: Elena, waiting on client data delivery."
Design rule: One tap for the common answer. One sentence max for anything else. If it requires more, it becomes a call.
§ 02.5 Dependencies
Action items that know what's blocking them.
Mark Action 3 as blocked by Actions 1 and 2. The system enforces the chain. Blocked assignees are notified but told not to start. When the blocker clears, downstream assignees are auto-notified.
Admins see the full dependency graph before dispatching from a meeting, so nothing gets sent to someone who can't actually start.
§ 02.6 Contract ingest
Upload a PDF. Skip the form.
Drop in a signed contract. Claude extracts client name, engagement type, contract value, start and end dates, and key deliverables, then pre-populates the New Engagement form. Consultant reviews and confirms before saving.
Contract upload is a fast lane. The manual form is always available.
§ 03 — Who uses it
Designed so only partners open the dashboard.
Consultant
Never has to open the dashboard.
Receives notifications. Taps acknowledgments. Logs actions on completion. Participates via whatever tool they're already in.
Analyst
Same as consultant.
Receives, acknowledges, executes. Doesn't need the dashboard. The system meets them where they already work.
A note on positioning
Command Center sits above your existing tools, not in place of them. Tasks themselves stay wherever you already manage them. Client relationships live inside engagements rather than a separate CRM. The dashboard plugs into Slack, Teams, and email so consultants keep working in the tools they already use.
Try it
The live demo shows the visibility layer in action.
The current demo at demo.aerolex.dev is the read-only visibility tool, the foundation Command Center is built on. The dispatch and acknowledgment layer is in active build.
Talk to Noah
Walk through Command Center for your firm.
Twenty minutes. Bring one workflow that's been costing senior hours.