Portfolio analytics
Every product. One deck.
Deckview is the cockpit for a small portfolio of software products: who signed up, what they did, what each product earns, and what wants a person next — in one place, on your own server.
Private beta. No session replay. Nothing leaves your cluster.
One person, not one account
Every other analytics tool counts accounts. A person can be dormant in one product and paying in another, and the two rows never meet.
Deckview joins the accounts by the address behind them, so the People page shows one human with every product beside them. Open a name and the whole history is in one place: sign-ups, deals, stage changes, tasks, notes and mail, oldest first.
It is the unit the portfolio is actually about. A product page cannot answer “which of these is worth another month”; a person can.
A queue, not a dashboard
A dashboard tells you what happened. It does not tell you what to do about it. Deckview opens with the short list of things that want a person: an account that never used the product, a trial ending this week, a mail that did not arrive, a collector that is stale.
Each line can be done, snoozed for seven days, or marked not ours. The first visible line is the next thing to do. Hidden items stay reachable, so the queue can be emptied without being lied to.
The modules
Seventeen surfaces, grouped by the job they do. The public site and the app read the same registry, so a module cannot be described here and missing there.
Sell
- PipelineThe board from first contact to won or lost.
- TasksWhat is due today, and what was promised.
- PeopleOne person across every product, not one account.
- MailEvery mailbox and every reply, in one thread.
- Reach outA first mail to a person, with the facts and the draft.
- OutreachCampaigns, hot leads and what they cost.
Measure
- OverviewWhat changed, what is stuck, what is broken.
- TrafficWhere visitors came from and what they read.
- ReportsRetention, activation and the funnel, per product.
- ExploreAsk the events a question without writing SQL.
Act
- FlagsTurn a feature on for one person or one product.
- ExperimentsA hypothesis, two arms, and the result.
- SurveysAsk the people who stayed, and the ones who left.
Run
- MoneyRevenue, cost and margin per product.
- HealthCollectors, freshness, and what is stale.
- ErrorsBrowser errors, grouped and resolvable.
- InstallThe snippet that starts the measurement.
It refuses to collect what it does not need
A portfolio tool holds customer mail, revenue and errors. The least it can do is not also hold a recording of the screen.
The tracker records events, not the screen. There is no recording to leak, because none is made.
Where a product holds customer content, the tracker can record the shape of the page and never its text.
Every fact lands in your Postgres. There is no third-party analytics account in the path of the numbers.
Running more than one product? Tell me what you run and what you want to see. Access is limited while the portfolio model is proven.
Request access