Aeion Views for Sales Team Pipeline Workflows

Sales teams of 10-100 AEs need shared pipeline views (everyone sees the same data the same way), personal default views (each rep opens to their own pipeline), manager dashboards (real-time portfolio rollup), and conditional formatting (at-risk deals highlighted). Salesforce List Views + Looker dashboards + Salesforce Reports = $50-100/user/month + per-feature license. Aeion Views is platform-native at $0/user.

The Sales Team Views Problem

`

Sales Team View Patterns

`

Walkthrough — 20-AE B2B SaaS Sales Team

`

FAQ

Salesforce list views are clunky to share (per-org config), don't include dashboard widgets, are limited to specific objects, and require per-user customization. Aeion Views handles per-collection saved views + dashboards + shared/private modes uniformly across all collections + included free at platform tier.

Not via one magically-substituting shared view — each rep gets their own personal saved view instead. Sales ops deploys "My Open Pipeline" to the whole team via the saved-views API: one view per rep, each with that rep's ownerId baked into the filter and marked as their default. Separately, admin-configured collection quick filters do support relative-date tokens ({{today}}, {{tomorrow}}, {{currentUser.id}}, {{NdaysAgo}}) resolved at render time — but that's a collection-level admin setting, not something you type into a saved-view filter.

Per-field, per-value, single-condition rules (field + operator + threshold → background color / text color / icon). Stack multiple rules to approximate compound logic (one rule for "value >= $50K", another for "daysInStage >= 60") — there's no AND/OR/NOT expression builder today.

Yes — saved view sets baseline. User can add/remove filters in current session without saving. "Save changes" button or "Save as new view" preserves modifications.

The admin is responsive, so saved views are reachable from a mobile browser, but there's no dedicated per-device layout adaptation (kanban-to-cards, gantt-to-timeline) yet — that's on the roadmap, not shipped.

There's no dependency-tracking dashboard that auto-detects and migrates saved views when a referenced field is renamed. If sales ops renames a pipeline stage, saved views filtering on the old value need to be updated manually today.

Saved views are scoped to a single tenant; there's no built-in cross-tenant read-only publishing for parent/holding-company setups today. For consolidated reporting across related tenants, use the BI module's cross-tenant rollups instead.

Cursor-based pagination + filter pushdown to PostgreSQL keep saved-view loads fast even on large collections. There's no separate materialized-aggregation cache — the summary footer computes from the loaded page.

CSV and JSON export are supported server-side, respecting the current filter. The admin UI currently wires up CSV for selected rows. Useful for ad-hoc analysis + sharing with non-Aeion stakeholders.

REST API for create/read/update/delete + set-default. Programmatic view creation for tenant-wide deployments. Useful for templating: "Acme Inc preferred view setup" deployable to all 200 reps via API.

Sales pipeline views — finally standardized.