One dashboard, five ways to build it.
Working concepts for the NewCo Executive Command Center, built directly from Jason's updated RFP of Aug 10 - a first ladder of five, then a combined direction from the two that won. Every requirement in the email - the five executive views, the four operating layers, the integration waves, the API gateway, the agent fabric, and the NewCo-owned reporting lakehouse - appears in every concept. What changes across the ladder is how much surface area the executive sees at once.
Click everything. Every number, chip, and heat cell drills to the underlying items, and every item opens a record with a timestamped history. Nothing is face-value.
One data story. Same company state in all five: $18.4M cash with one aging bank exception, an AP approval bottleneck, one Red workstream, 94 days to TSA exit.
Three skins. The switcher in every header swaps Inframark, NewCo, and DataRipple branding live - same product, white-labeled per client.
Round 2 · The combined direction
Concepts 1 and 5 won the first pass. These two merge them: Concept 1's calm, plain-English layout carrying Concept 5's Ask bar, countdown, and heat wall - organized as the RFP's five Core Dashboard Tabs, named exactly as stated. Every item carries an italic via [system] tag, and a capture strip at the bottom of each page lists the full required-integration list.
CONCEPT 6A · COMBINEDThe Command Brief · Tabs
Five true tabs - 1. CEO / President View through 5. Carve-Out Readiness View - each written like the Morning Brief: a one-line verdict, then clean rows. Ask NewCo sits above every view; the EBITDA bridge lives on the CEO tab, the heat wall and what-ifs on Carve-Out.
Proves: the RFP's exact tab architecture can feel as calm as a briefing note, with every line tagged to the system it captures.
Open
CONCEPT 6B · COMBINEDThe Command Brief · One Page
The same five views as one continuous morning read, in the RFP's order. The tab bar stays pinned and jumps to each view, so it reads top to bottom like Concept 1 but still shows the requested tab structure at all times.
Proves: one scroll covers all five views without losing the tab map - the closest thing to "the whole company in one sitting."
Open
Round 1 · The original ladder
Simple to complex. Each is a complete, presentable dashboard; they differ in philosophy, not coverage.
CONCEPT 1 · SIMPLESTThe Morning Brief
The daily executive briefing as the whole product. One scrolling page that reads like a note from a chief of staff: the short version, five things needing attention, then every domain in plain English.
Proves: executives get the answer in 90 seconds without learning a tool. The RFP's "daily executive briefing" ask, made primary.
Open
CONCEPT 2 · SIMPLEThe Scoreboard
Everything on one screen: six headline numbers, four domain boards, a decisions rail, and live system health. No tabs, no scrolling story - a glanceable wall for a Monday standup or the office TV.
Proves: the whole company fits on one screen and still drills to every underlying item.
Open
CONCEPT 3 · INTERMEDIATEThe Command Center
The RFP's architecture, verbatim: CEO/President, Operations, Financial, Data & AI, and Carve-Out Readiness as five full views, with the EBITDA bridge, workstream table, critical path, and integration strip.
Proves: the exact "Core Dashboard Tabs" structure from the email, working. The natural one to present first.
Open
CONCEPT 4 · COMPLEXThe Command Center Pro
Concept 3 plus the layer the RFP called the biggest missing item: a Platform view (integration waves, API gateway, data lineage, KPI dictionary, lakehouse) and an Agent console (live activity, escalation queue, handoffs), plus an alert center.
Proves: the integration and agent orchestration fabric is a first-class, visible part of the product - not plumbing.
Open
CONCEPT 5 · MOST COMPLEXMission Control
The whole company on one wall: a live event ticker, TSA countdown, the carve-out heat wall, the profit bridge, what-if scenarios, and "Ask NewCo" - type a question and the agent fabric answers with sources cited.
Proves: the ceiling. Agents that read every system and answer executive questions, not just display them.
Open
Start with Concept 3. It mirrors the RFP's own five-view architecture, so it is the natural first read.
Concept 4 is the full Wave 1 delivery. The same dashboard plus the gateway, lakehouse, and agent console it runs on.
Concept 5 shows the ceiling. The AI layer answering executive questions directly, with sources cited.
The Morning Brief pairs with any of them. It ships alongside any option as the daily 6 AM habit.
Requirement coverage, line by line
Every ask in the Aug 10 email, and where it lives in each concept. ✓ = present with drill-downs · ● = present as a dedicated view or feature.
| Requirement from the RFP | C1 | C2 | C3 | C4 | C5 |
|---|---|---|---|---|---|
| CEO / President viewCommunities, revenue, EBITDA bridge, cash, AR/AP aging, service volume, AI savings, carve-out risks, migration readiness, critical vendor status | ✓ | ✓ | ● | ● | ● |
| Operations viewVantaca action items, resident requests, violations, ARC, work orders, SLA aging, manager capacity, HOAi/STAN throughput, board packets, bottlenecks | ✓ | ✓ | ● | ● | ● |
| Financial viewNetSuite/BC financials, StrongRoom AP + cycle time, TechCollect AR + recovery, Avalara tax, bank reconciliation (AAB, Pinnacle, SouthState), treasury, fund accounting | ✓ | ✓ | ● | ● | ● |
| Data / AI viewAgent activity, completion rates (HOAi & STAN), escalations, error rate, approval queues, handoffs, knowledge gaps, automation ROI, SharePoint doc intelligence, Graph activity | ✓ | ✓ | ● | ● | ● |
| Carve-Out Readiness viewmonday.com workstreams + RAG + owners, blockers, critical path, SharePoint evidence, Azure/O365 + SSO + Dayforce + data migration, TSA exit + Box files, vendor deliverables, board actions, launch readiness | ✓ | ✓ | ● | ● | ● |
| Daily executive briefing"Produce a daily executive briefing" - Azure AI agents section | ● the whole concept | ✓ | ✓ | ✓ | ✓ |
| Every number drills to source recordsImplied by "real-time operating intelligence" - each item opens with its history | ✓ | ✓ | ✓ | ✓ | ✓ |
| Integration waves 1 / 2 / 3 + sunset exclusions"Please price these in waves" + the exclude list (Nolan ABR, Adaptive, FloQast, Medius, Concur, Navan, Percipio, ServiceNow, IPS SSRS, Workday) | strip + drills | strip + drills | strip + drills | ● Platform view | ● Platform wall |
| API gateway / integration layerCentral API management, credential vault, webhooks, retries, audit logs, data lineage, real-time + batch sync | drills | ✓ | drills | ● Platform view | ● Platform wall |
| Agent fabric / orchestration layerMicrosoft Graph + Azure AI agents reading, acting, escalating, summarizing across the stack | ✓ | ✓ | ✓ | ● Agent console | ● + Ask NewCo |
| Lakehouse / semantic model / KPI definitionsNewCo-owned reporting architecture: lakehouse, semantic model, KPI definitions, security model, refresh architecture, historical archive | drills | drills | drills | ● KPI dictionary | ● Platform wall |
| Ask questions of Vantaca / NetSuite / StrongRoom"Ask Vantaca/NetSuite/StrongRoom questions... draft action plans... route issues to owners" | - | - | - | - | ● Ask NewCo bar |
| Client skins (white-label)Inframark brand pulled from inframark.com · NewCo placeholder until the brand decision · DataRipple | ✓ | ✓ | ✓ | ✓ | ✓ |
The skin concept
Same product, three identities. A skin is a token overlay - colors, type, logo - applied at login per client, the same pattern DataRipple uses for client-branded consoles. Use the switcher in any header to change it live; your choice sticks across all five concepts.
Inframark
Built from inframark.com's live palette
Type: Mulish (stand-in for Mr Eaves Modern) · lime primary action, navy identity
NewCo
Neutral placeholder until the brand decision lands
Type: Inter · the Comms & Brand workstream's final identity drops into this slot in a day
DataRipple
The platform's own identity
Type: Ubuntu · what the product looks like as DataRipple's own
Sample data only. Every figure on these pages is invented to make the concepts concrete - one bank exception, one Red workstream, an AP bottleneck - so the dashboards read the way they would in production, not as a wall of green. No Inframark, Azuria, or NewCo data was used.
Built by DataRipple · concept review only · not indexed.
Built by DataRipple · concept review only · not indexed.