How is Vantage different from ChatGPT or Claude?

ChatGPT and Claude write you a document. Vantage keeps the document, prototype, tickets and roadmap connected to the feedback and decisions behind them, and tells you when one of them changes. You can also bring your Vantage context into Claude or ChatGPT, so you don’t have to choose.

Do I have to move off Notion or Linear?

No. Keep the tools you use and connect them to Vantage. Tickets push to Linear with two-way sync, and you approve every change that comes back.

What can I do in the first ten minutes?

Paste customer feedback or describe a problem, and get a PRD with every requirement linked to its source. You can try the demo on this page without signing up. Connect your tools whenever you’re ready.

I own several projects. What does Vantage do across them?

It briefs you every morning on what needs your call, catches specs that contradict each other, and flags anything that went stale after a decision changed. It works for a single project and earns its keep at two or more.

What if the AI gets something wrong?

Nothing updates silently. Every requirement cites the quote, call or metric behind it, and every change arrives as a diff you accept or reject before it touches your docs, tickets or Linear.

Can I use Vantage from Claude or ChatGPT?

Yes. Connect Vantage’s MCP server to Claude, add the GPT Action in ChatGPT, or use an API key. Then ask about your projects, search your specs, or create tickets from wherever you work.

Start on your own for free. When teammates join, they work from the same context, with admin, editor and viewer roles and private drafts that stay invite-only until you publish.

What does fair use mean on the unlimited features?

Unlimited features are meant for real day-to-day work by one person: up to 50 questions a day on Pro and Business, and on Business up to 10 PRDs, journeys or ticket batches a day. Very few people get close. If your team regularly needs more, talk to us.

Your data is encrypted in transit, and we never train on it. The AI providers we use are contractually barred from training on it too. You can disconnect any integration or delete your account at any time. We’re pursuing SOC 2 Type II.

How much does it cost?

Vantage is free to start with 300 credits and no credit card. Projects are unlimited on every plan, and AI work like generating a PRD or a ticket batch uses credits. Pro is $19 per seat a month billed annually ($25 monthly) with 1,500 credits a month, unlimited questions and prototypes. Business adds a shared team workspace and 4,000 credits per seat a month.

Why are API events missing from session metrics?

Check their session IDs and the documented rules. Events outside a valid session can be excluded.

Does a tab left open mean an active session?

Not necessarily. Session grouping and active-event definitions determine the measurement.

Can we change the session definition?

Yes where supported, but record the change and avoid treating unlike historical definitions as one continuous metric.

Product workflows2026-10-292 min read

Analyze Sessions in Amplitude

Confirm how your integration groups events into sessions before interpreting session counts or duration. Session metrics depend on identifiers and activity settings, not simply on how long a browser tab appears open.

Before you start: Have a known journey and access to the session definition and integration. Include server-side events if they contribute to the workflow.

Worked example: A user starts a task before midnight and finishes after midnight. Check how the session is assigned to the reporting period rather than expecting each event date to produce a separate session.

Step-by-step guide

Read the session definition

Record the current timeout or custom session logic. Keep browser and mobile assumptions separate.

Inspect known journeys

Compare a continuous task with a deliberate break. Verify the grouping against the intended definition rather than intuition.

Check API events

Confirm session information on events sent outside the SDK. Missing or special session IDs can affect inclusion in session metrics.

Check activity semantics

Identify passive events and whether they should count as active behavior. A background event can distort engagement if its role is misunderstood.

Align reporting dates

Review the treatment of sessions spanning period boundaries. Keep the same definition and dates across segment comparisons.

Interpret with task outcomes

Pair session behavior with successful work. A longer session can indicate deeper use or difficulty; inspect context before choosing an explanation.

Common mistakes

Longer equals better

Time can represent friction.

Server events assumed included

Session IDs must be validated.

Cross-day counts guessed

Use the documented session assignment rules.

Tips

Keep session definition changes beside trend charts.

Test one journey with a known break.

Compare session behavior with meaningful completion.

Sources and verification

Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.