A product-analytics platform built for the people who need the answer, not the query language. Funnels, retention and segments that a PM can build and a CEO can read.
Most analytics tools are built for the analyst. Everyone else waits in a queue for someone who knows the query language to pull a number, and by the time it arrives the decision is already made.
The data isn't the problem. Access to an answer is.
I designed the three questions product teams actually ask as first-class objects: is this feature working (funnels), are people coming back (retention), and who are they (segments). Each one is something a PM builds by clicking, not by writing SQL.
The hard part was density with restraint. A retention grid or a funnel throws a lot of numbers at you, so the job was to make the shape of the answer obvious before the detail.
A tool the whole team opens, not just the data lead. Funnels, retention and segments that read at a glance and share as a link.
On a fictional rollout, report requests to the data team dropped by half in the first month, and non-technical seats tripled.
| Cohort | Users | W0 | W1 | W2 | W3 | W4 | W5 | W6 |
|---|---|---|---|---|---|---|---|---|
| Jun 2 | 3,120 | 100 | 62 | 48 | 41 | 37 | 34 | 32 |
| Jun 9 | 2,980 | 100 | 64 | 51 | 44 | 39 | 36 | — |
| Jun 16 | 3,420 | 100 | 66 | 54 | 47 | 42 | — | — |
| Jun 23 | 3,610 | 100 | 70 | 58 | 50 | — | — | — |
| Jun 30 | 3,880 | 100 | 72 | 60 | — | — | — | — |
| Jul 7 | 4,010 | 100 | 74 | — | — | — | — | — |
People who were active but are slipping: a save-the-account list.
Users who invite a teammate in week one retain 2.3× better at D30. Only 34% get there.
A Very Vinci concept study. Invented brand, real design thinking.