Product funnel dashboard for founders & teams

Three views, one page

Most founders end up reading the same three numbers every Monday — engineering throughput, product funnel conversion, pipeline health — across three different tools. Each tool has a perfectly fine dashboard. None of them sit next to each other, and stitching them is a Monday-morning tax.

This example replaces the tax. A weekly snapshot of the CRM’s activity, upcoming meetings, and pipeline counts; a rolling-14-day product funnel built from Mixpanel events you specify; the Linear issues tagged with a label you choose so engineering work-in-flight sits beside the outcome numbers. One page, refreshed when you open it.

Dashboard overview and product funnel

The Dashboard page pulls last-week CRM activity, upcoming meetings, and the current pipeline counts in one fetch. The Product Funnel page renders a configurable funnel — pick which Mixpanel events count as funnel stages, see unique users per step over the last 14 days, and the Linear issues labelled with whatever label you’ve chosen as the funnel-improvement marker.

Both surfaces are read-only — they don’t write back to Linear or Mixpanel. The workspace pulls the numbers fresh when you open the page; you spend the time reading, not refreshing.

What the dashboard pulls and how

1. You open the Dashboard page. A backend fetch reads last week’s CRM activity counts, upcoming meetings from the workspace’s deal model, and the current pipeline state — all from the workspace’s own entities, no external calls involved.
2. You open the Product Funnel page. A second backend fetch queries Mixpanel for unique-user counts at each funnel stage over the rolling 14-day window, using the events you’ve configured as the funnel definition.
3. Linear issues join in. The same fetch lists Linear issues tagged with the workspace’s configured label so engineering work tied to the funnel appears alongside the conversion numbers, not in a separate tab.
4. You change what counts. The funnel definition (which Mixpanel events, which Linear label) is a single configurable record. Editing it changes the dashboard the next time someone opens it — no rebuild, no redeploy.

Funnel events, Linear label, time window

• Funnel stages — the ordered Mixpanel events that define a step in the funnel (e.g. visited marketing page → signed up → completed onboarding → created first artefact). Stored as a single configurable record on the workspace; rename / reorder / replace at any time.
• Linear label — the label name used to tag Linear issues you want listed beside the funnel view. Pick a label your team already uses (e.g. onboarding, activation), or create a new one in Linear and configure it here.
• Time window — the funnel page defaults to a rolling 14 days; widen to capture longer conversion cycles or narrow for high-traffic products.
• Pipeline-health refresh cadence — the CRM-derived snapshot recomputes whenever the page is opened. For teams running monthly reviews, this is the page they live on.

Funnel definition, declared once

The reason this dashboard doesn’t exist as a SaaS product is that everyone’s funnel definition is slightly different. Mixpanel won’t guess your events; Linear won’t guess your label; the CRM snapshot only makes sense in the context of how you sell. The pitch here is that the pieces are declarative — events, label, snapshot fields — and the workspace builds the dashboard from them. When your funnel changes, you change the definition, not the code.