How is Vantage different from ChatGPT or Claude?

ChatGPT and Claude are great for one-off generation. Vantage is a full workspace. It connects your tools, tracks dependencies across projects, catches conflicts between products, and surfaces what needs your attention every morning. It also remembers every past decision, so a new PM can query across all projects and get cited answers in seconds.

Do I have to switch away from Notion or Linear?

No. You keep all your tools. Vantage connects to them and builds intelligence on top. When you're ready, you can push tickets to Linear or Jira. But the value starts before you create anything — just by connecting your tools and seeing what the intelligence layer surfaces.

What happens on day one?

You connect your tools — GitHub, Linear, Slack — 2 minutes each. Vantage indexes your existing data overnight. By the next morning, you see your first decision queue: what's stale, what conflicts, what changed. No manual setup. No templates to fill out.

What if I only manage one project?

Vantage works for single projects, but it shines when you manage 3–5 or more. Conflict detection, cross-project memory, and the decision queue are most valuable when you have multiple projects that need to stay in sync. If you manage one project, start with the free tier and see if the cited query engine alone saves you time.

All data encrypted in transit and at rest. We never train on your data — the AI providers we use are contractually barred from it. You can disconnect any integration or delete your account at any time. Pursuing SOC 2 Type II.

How does Vantage keep documents and tickets up to date?

When context shifts, you add the new information and Vantage rebuilds every connected deliverable. Documents, prototypes, and tickets all update. You review the changes, accept or reject each one, and approve. Nothing updates silently, and every change is traceable.

How do I get started?

Sign up free at app.vantageos.tech. Connect your tools, and generate your first grounded document within minutes. No credit card required. Upgrade when you need more projects or features.

How many charts should a product dashboard have?

Aim for 6-10 charts on a primary dashboard. Fewer than 6 may miss important signals. More than 10 becomes hard to parse in a weekly review. Use multiple focused dashboards (activation, retention, feature adoption) rather than one mega-dashboard.

How often should I review the product analytics dashboard?

Weekly as a minimum. Most product teams review core metrics weekly in a standing meeting. Set up automated Slack posts so the team sees the key numbers without needing to remember to open Amplitude.

Is Vantage free to try?

Yes. Vantage offers a free tier with 1 project and 5 AI queries per month.

How-To2026-08-2310 min read

How to Create a Product Analytics Dashboard in Amplitude

An Amplitude dashboard is the single place your product team looks to understand how the product is performing. A well-built dashboard tells a story: adoption is growing, retention is stable, feature X is underperforming. A poorly built dashboard is a collection of unrelated charts that nobody looks at.

This guide covers building a product analytics dashboard in Amplitude that your team actually uses in weekly reviews.

Step-by-step guide

Create a new dashboard from the Amplitude sidebar

In Amplitude, click Dashboards in the left navigation. Click New Dashboard. Give it a clear name such as [Product] Weekly Metrics or Feature Adoption Dashboard. Set the visibility to Team or Organization so all PMs can access it. Use the Description field to document what the dashboard is for and who should own it.

Add a DAU/WAU/MAU chart as the first panel

Click Add Chart and choose Event Segmentation. Select your core active event (project_viewed, session_started, or equivalent). Set the Y-axis to Unique Users. Create three instances of this chart with Daily, Weekly, and Monthly grouping respectively. Arrange them horizontally across the top of the dashboard as the health indicators.

Build a core user funnel chart

Add a Funnel Analysis chart. Define your product activation funnel: Signed Up > Completed Onboarding > Created First Core Object > Returned After 7 Days. Set the conversion window to 7 days. This single chart shows where users drop out of the activation journey. Pin it prominently below the activity metrics.

Add a retention chart for your core action

Add a Retention Analysis chart. Set the A event as your new user anchor (typically Sign Up or First Login) and the B event as the return action (any core engagement). Select N-Day retention with an 8-week lookback. This retention curve shows whether new users are coming back — the most important leading indicator of product health.

Add feature adoption charts for key features

For each major feature shipped in the last quarter, add an Event Segmentation chart showing unique users triggering that feature core event. Use weekly granularity. This shows whether features are gaining or losing adoption over time and whether launches are creating lasting behavior change.

Set up auto-refresh and relative date ranges

At the top of the dashboard, set the date range to Last 30 Days with relative dates enabled so it auto-updates daily. Enable Auto-refresh in Dashboard Settings. Set up an Amplitude Slack integration to post a weekly dashboard snapshot to your product channel every Monday morning automatically.

Add dashboard annotations for launches and experiments

Use the Amplitude Annotation feature to add vertical markers on the timeline for significant events: feature launches, marketing campaigns, pricing changes. Right-click any chart and select Add Annotation. These annotations explain spikes or drops in the data without requiring tribal knowledge from the team.

Common mistakes

Too many charts with no narrative

A dashboard with 20 unrelated charts is not a dashboard — it is a report dump. Each chart should answer a specific question a PM asks in a weekly review. If you cannot articulate why a chart is there, remove it.

Tracking vanity metrics prominently

Total signups and total page views only go up over time and do not reflect product health. Prioritize retention rates, activation rates, and feature engagement depth over raw volume counts.

Using absolute counts instead of rates

If your user base is growing, absolute event counts will always increase. Use rates (activation rate, retention rate, feature adoption percentage) to separate growth from quality signals.

Tips

Create separate dashboards for different audiences: a high-level executive dashboard and a detailed PM operations dashboard

Use Amplitude metric comparison to benchmark the current period against a prior period on every chart

Add a Questions This Dashboard Answers text box at the top to document the dashboard purpose

Schedule a monthly dashboard audit to remove charts that have not been viewed in 30+ days

How Vantage helps

Vantage connects to Amplitude so your analytics data grounds PRD generation. When you create a project in Vantage, relevant Amplitude metrics are pulled in as context — so the AI generates specs that reference your actual funnel conversion rates and retention curves rather than generic assumptions.