Accounts and Account Intelligence

Accounts is the account-level source of truth inside Prevenue. It is not a CRM and does not create or edit the customer's commercial record. It consolidates the context needed to understand why an account entered a Funnel, produced an Opportunity, or received a Signal.

Open Accounts in the app.

What the account table shows

The default account table includes:

• Account name and account key.
• Event pulse.
• Plan.
• MRR.
• Grow, Save, Convert, and Watch scores.
• Signal count.
• Last event.
• Saved list membership.

The column selector can add raw Event KPI fields such as sentiment windows, usage quality, friction load, expansion surface, revenue sentiment divergence, momentum quality, evidence band, sample size, known sentiment, negative sentiment, and unknown sentiment. It can also add model intelligence columns for preventability, opportunity window, lead time, half-life, stale-after days, suppression behavior, and model confidence.

Standard account facts

Prevenue tracks a small set of default SaaS account facts for account intelligence and filters:

• Customer signup date from the customer's source system, such as account_created_at, signup_at, or customer_created_at.
• First seen, last seen, first event, and last event timestamps from normalized activity.
• Login activity from login semantic events such as user_logged_in or session_started.
• Plan, subscription status, trial state, trial start/end, billing period, MRR, ARR, and currency from Stripe when connected.
• User count, active user count, seat count, and session counts from account traits or event rollups.

accounts.created_at is the time Prevenue first created the account row. It is not the same as the customer's product signup date.

Event pulse

Event pulse is the default compact account-level read from Event KPI Signals. It chooses the most useful current summary, such as negative sentiment, friction load, momentum quality, or expansion surface.

Use Event pulse to quickly decide which accounts deserve deeper review. Use raw Event KPI columns when you need comparison, audit, or reporting context.

Read Event KPI Signals for field definitions.

Account drawer

Open an account row to review:

• Overview.
• Users and identities.
• Funnels.
• Opportunities.
• Signals.
• Events and activity.
• Saved lists.

The overview includes motion scores, Event KPIs, model intelligence, score basis, saved lists, recommended handling, plan, MRR, signal count, and last event.

Model intelligence

Model intelligence is the daily learned context for an account. It shows whether any current learned pattern applies to the account and includes:

• Lead time: the typical time between the signal appearing and the later revenue movement.
• Half-life: how long the signal usually remains actionable.
• Stale after: when the signal should be treated as stale unless new evidence arrives.
• Preventability: a prioritization score for save motions, not proof of causal lift.
• Suppression: whether outreach should be suppressed, routed to success, or kept internal.
• Model confidence and evidence strength.

Read Intelligence Learning Evidence for the full definitions.

Opening a Funnel, Opportunity, or Signal from the account record keeps the account page in context and opens the relevant detail drawer. Use the Events and Activity tabs for source evidence and the Users tab for people, roles, logins, and authority context.

Account intelligence scores

Grow, Save, Convert, and Watch scores summarize evidence strength for the account. They are account intelligence, not guaranteed outcomes.

Use the score basis to understand:

• Source.
• Target.
• Horizon.
• Evidence confidence.
• Probability when a probability field exists.
• Model confidence when available.

If the drawer says no score has enough evidence yet, improve source data and mappings before acting on the score.

Filters and saved lists

Accounts can be filtered by account fields, plan, subscription status, motion scores, MRR, payment risk, event counts, usage metrics, Event KPI fields, model intelligence fields, source identity, last event date, evidence confidence, owner, and saved list.

Save useful account segments as saved lists. Examples:

• Active accounts with high friction load.
• Trial accounts with upgrade intent.
• Accounts with negative sentiment and usable evidence.
• Accounts with high preventability and high opportunity urgency.
• Accounts whose learned signal is about to go stale.
• Accounts with no recent event activity.
• High Grow score accounts not routed yet.

Read Saved Lists for refresh behavior.

How Accounts fits into the workflow

Use Accounts when:

• A signal needs account context.
• A sales or success team asks why an account was flagged.
• A metric changed and you need account-level examples.
• You want to build a saved list for Funnel enrollment.
• You need to audit identities, evidence, or Event KPI coverage.

Use Opportunities for account-level journey operations. Use Signals for moment-level evidence. Use Accounts for the full customer investigation.