Account

Usage and billing

How Seena meters usage, what each plan includes, how per-seat billing works, and how to top up when you need more.

Seena meters work in usage. Each interview, briefing, Librarian chat, and analysis step draws on a single percentage bar tied to your subscription. The bar refreshes every billing cycle. If you need more before the next refresh, top up — those top-ups land in a reserve that never expires.

This page covers plans, the usage meter, and how per-seat billing works once your team is bigger than one.

Plans

Explorer (free)

For getting started. A handful of interviews to confirm the install and feel the loop.

  • Starter usage on signup — enough to run a few sessions and see real output.
  • Personal workspace only — sharing with teammates requires Pro or higher.
  • All core features available.

Pro ($49/month per paid seat)

For light ongoing research — occasional interviews, weekly briefings, and modest traffic. Suitable for products running roughly 20–50 interviews per month.

  • Monthly usage refreshes each billing cycle.
  • Up to 3 paid seats and 5 viewer seats per workspace.
  • 3 sites (marketing site, web app, prototype, etc.).
  • 5 interview agents across those sites.
  • Agentic triggers (coming soon), goals-mode questions (coming soon), and the option to drop the Seena logo from agents.

The workspace owner counts as one paid seat. Viewer seats are free and read-only.

Max ($199/month per paid seat)

For active research — regular interviews across meaningful traffic, daily briefings, multiple teammates. Suitable for products expecting more than 100 interviews per month.

  • Everything in Pro.
  • 5× the monthly usage of Pro.
  • Unlimited paid seats and unlimited viewer seats.
  • Unlimited sites, apps, and prototypes.
  • Unlimited interview agents.

Enterprise

Custom pricing, invoiced billing, and procurement-friendly terms for larger orgs. Contact sales.

Reserve top-ups

On any plan, click Add Usage on the billing page to add a dollar amount to your reserve. The reserve is consumed only after your monthly bar reaches 0% and never expires — so if you anticipate a spike, top up in advance instead of jumping a tier.

Choosing a plan

Interview frequency is the biggest cost driver. Everything else (insights, briefings, the Librarian, crawling) is modest by comparison. A useful rule of thumb:

  • Expect under 10 interviews a month? Start on Explorer or Pro.
  • Expect 10–100 a month? Pro is usually right.
  • Expect more than 100? Max gives you the room and lets your team grow without bumping into the Pro seat caps.

What runs your usage down

Most usage is interviews. Briefings, the Librarian, and analysis all pull from the same bar but add up to far less.

You don't need to budget per action — the usage meter abstracts the per-action accounting. If you're curious about how usage scales, the rough order is:

  • Interviews — by far the largest line item; longer interviews use more.
  • Briefings — small per generation per user; daily and weekly each have their own cadence.
  • Librarian conversations — small per question; deep multi-tier questions cost a bit more than quick lookups.
  • Site crawling — tiny one-time cost when a site is first added.
  • Question generation (goals mode, coming soon) — small additional charge per agent run in goals mode. Specific-mode agents add nothing.

Who's charged for what

Usage is per-user, per-workspace — every member of a workspace has their own balance, and your balances in two different workspaces are independent. Which user gets charged depends on the action:

  • Interviews — charged to the person who created the site where the interview happens. Usually the workspace owner or whoever onboarded that site.
  • Insights and clustering — charged to the site creator. Other workspace members can read insights at no cost.
  • Daily and weekly briefings — charged to each user individually. Briefings are personalized, so each person's briefing is its own generation.
  • Librarian conversations — charged to you when you chat. Your teammates are never billed for your questions.
  • Site crawling and question generation — charged to whoever triggers the action.

The effect is that running cost is distributed naturally. If the workspace owner is paying for the interview-heavy work and the rest of the team mostly reads briefings and chats with the Librarian, those costs land on the individual users who do them.

Per-seat billing

On Pro and Max, the workspace owner invites paid teammates from Settings → Team. Each acceptance adds $49 (Pro) or $199 (Max) to the monthly subscription, prorated for the remainder of the current billing cycle.

Viewer seats are free and read-only — they can see insights, briefings, and interview transcripts, but can't create or edit anything. Pro is capped at 5 viewer seats; Max has no viewer cap. If your team needs more than 5 viewers, upgrade to Max for unlimited.

When you run out

If both the monthly meter and the reserve hit zero, automated work (insights, briefings, clustering) pauses and you're notified. Top up the reserve or wait for the monthly refresh to resume.

Your teammates are not affected — they have their own balances. The only shared consequence is that analysis on sites you created pauses until you top up. Interviews already in progress complete normally; new interviews on sites you created are paused until usage is available again.

Downgrading

Before going from Pro to Explorer, or from Max to Pro, remove paid teammates so the new tier can fit them all. The workspace owner can't remove themselves directly — transfer ownership to another paid member first, then leave.

Monthly usage vs. reserve

Your subscription comes with a monthly allocation that resets each billing cycle. Unused monthly usage does not roll over.

The reserve never expires and is only consumed once your monthly allocation is exhausted. If you anticipate a burst of research activity, top up in advance — it's the cheapest way to cover a spike without changing tier.

What to read next

  • Sites — what creating a site costs (very little) and what runs on it.
  • Workspaces and members — how usage interacts across workspace boundaries and team roles.