Most dashboards break the week after you build them. Someone renames a column, someone rewires a webhook, and by Monday your chart is lying to you. The dashboard is still there. The numbers are still there. They just don’t mean what you think they mean anymore.
Today we’re launching Views — live dashboards built and maintained by your AI colleagues, not by you. Every View has an owner. That owner is the colleague responsible for keeping it correct.
TL;DR
- Views are self-maintaining dashboards. Every chart has an AI colleague as its owner. When the underlying data drifts — column renames, new SKUs, definition changes — the colleague fixes the View and annotates what changed.
- Four built-in Views ship with this launch: Pipeline (Lisa), Revenue (Mark), Support (Casie), Activity (Ruby).
- Custom Views take three steps: describe what you want, pick an owner, ship. The colleague drafts, you nudge, they maintain it forever.
- Available today for every Eluu workspace.
What are Views?
Views are dashboards with an AI colleague as the named owner of every tile. The colleague:
- Watches for upstream data changes (renames, schema shifts, new categories).
- Updates queries, definitions, and segments without being asked.
- Annotates the View with what changed and why, so you have an audit trail.
- Adds new tiles when you ask, and inherits maintenance for those too.
The View stays alive because someone is alive inside it.
What this looks like when something breaks
Two scenarios from our own use of Views over the last six weeks:
- Your CRM renames “Closed-Won” to “Won.” The Pipeline View’s “Deals closed this week” tile drops to zero. The colleague who owns the View notices within the next update cycle, traces the definition back to the CRM field, updates the query, and annotates: “CRM renamed Closed-Won → Won on April 8.” You see the annotation. The chart is correct again. Nobody paged anyone.
- A new product SKU launches. The Revenue View’s “Revenue by product” chart is now missing 8% of revenue because the new SKU isn’t in the chart. The owner notices the total-vs-sum mismatch, adds the new SKU, and annotates the change. The chart is right before you notice it’s wrong.
This is the whole design: Views drift because data drifts, and a colleague’s job is to close the gap before you do.
What ships in the launch
Four built-in Views, each owned by a specific Eluu colleague out of the box:
| View | Owner | What it tracks |
|---|---|---|
| Pipeline | Lisa | Deals, stages, at-risk accounts, handoffs |
| Revenue | Mark | ARR, MRR, new vs. expansion, churn, segments |
| Support | Casie | Ticket volume, response time, top issues, customers at risk |
| Activity | Ruby | What every colleague did this week, what’s blocked, what’s pending approval |
Each one is fully editable. You can add tiles, change time windows, filter by team — and the owning colleague picks up responsibility for everything you add. Ask Lisa to add “Pipeline by rep this quarter” and from that point on, that tile is part of her rounds.
How to create a custom View
If none of the built-ins match what you need, you can create one yourself in three steps:
- Open Views and click “New View.”
- Describe what you want to track, in a single sentence. (“Outbound replies by sequence, last 30 days.”)
- Pick a colleague to own it.
The owner drafts the View — usually three to five tiles they think match your intent — and shows it to you. You nudge it into shape in chat (add X, remove Y, group by Z). When you’re happy, it’s live and the colleague takes over maintenance from that point forward.
This works because Eluu colleagues already understand your tools and your data — the same memory architecture we wrote about in building AI colleagues that remember is what lets a colleague know what “outbound replies” means in your workspace, not in general.
Why self-maintaining dashboards matter
The cost of a stale dashboard is almost never zero. Someone makes a small decision based on a chart that’s wrong, and the cost is invisible until a quarter later when the trend line didn’t mean what everyone thought.
The reason dashboards go stale isn’t that people are lazy. It’s that maintaining them is boring, adjacent to the actual job, and easy to defer until next sprint. “Next sprint” then never arrives, because a slightly-wrong dashboard is functional enough to ignore.
Views is our bet that “next sprint” for dashboard maintenance should be “the next scheduled check your AI colleague runs.” Not because AI colleagues are smarter than humans at understanding charts — they aren’t, yet — but because they will do the maintenance reliably, at 2am, without reminders, forever.
The economics flip the moment maintenance becomes free.
FAQ
What are Eluu Views? Views are live dashboards in Eluu where every chart is owned by a named AI colleague. The colleague is responsible for keeping the underlying queries, definitions, and segments correct as your data changes.
How are Views different from Looker, Metabase, or Mode dashboards? Traditional BI dashboards are static — when data drifts, they silently break and a human has to notice and fix them. Views have a built-in maintainer (the AI colleague) who detects drift, updates the View, and annotates what changed.
Who owns a View? Every View has exactly one Eluu colleague as the owner. Pipeline → Lisa, Revenue → Mark, Support → Casie, Activity → Ruby. For custom Views, you pick the owner at creation time.
Can I edit a View after it’s created? Yes. Views are fully editable. You can add tiles, change time windows, and filter by team or segment. The owning colleague inherits maintenance for anything you add.
How much do Views cost? Views are included in every Eluu plan. There’s no add-on charge.
When can I use Views? Today. Views is live for every Eluu customer as of this post. Open the Views tab in your workspace.
If you’re not yet using Eluu, book a demo and we’ll walk you through it. We’d love to hear what you build.