Pricing · Proposed launch plans

A clear allowance. Room to get things done.

Choose the shape of help you need. These are proposed monthly plans for a product in development. Subscriptions are not on sale, and joining the waitlist does not start a paid plan.

Personal

$29/ month

A little help with the everyday.

  • 1 seat
  • 60 voice session minutes
  • 200 task credits
  • Voice, writing & coding assistance
  • User-approved memory
  • Selected connected tools
  • Planned approval and activity controls
  • Planned access revocation and memory controls
Join the waitlist

Teams

$199/ month

A shared allowance for a small team.

  • 3 seats included
  • 600 shared voice session minutes
  • 1,500 shared task credits
  • Shared workflows
  • Workspace administration
  • Team activity visibility
  • Planned approval and activity controls
  • Planned access revocation and memory controls
Join the waitlist

Enterprise

Custom

A defined workflow, access, and budget.

  • Seats scoped to your needs
  • Voice allowance agreed in advance
  • Task budget agreed in advance
  • Larger deployments
  • Custom integration requirements
  • Defined deployment and support scope
  • Planned approval and activity controls
  • Planned access revocation and memory controls
Share your requirements

Proposed prices in USD per month, before tax. Personal and Pro include one seat; Teams includes three seats sharing one allowance. Final plans, billing terms, and availability will be confirmed before purchase.

Two kinds of usage

Conversation and task work, measured separately.

A voice session creates a continuous conversation. A task may involve planning, tool calls, checking results, and another reasoning step. Both need an honest budget.

Voice session minutes

The proposed meter counts the time an active session is open, including silence and backend waits. It does not only count your speaking time. Idle sessions should close automatically; these plans do not include continuous listening.

Task credits

One proposed task credit allows up to $0.03 of metered backend AI spend. Each task uses at least one credit, with total AI spend rounded up in $0.03 units. A credit is a usage budget, not a guarantee that every request finishes in one step.

Long context, screenshots, retries, and multi-step computer tasks can use multiple credits. The planned experience shows an estimate before a longer task, lets you approve a maximum budget, and stops safely at the allowance without silently charging overages.

A shared foundation

Control belongs in every plan.

Every proposed tier includes the same baseline requirements for approvals, activity visibility, access revocation, and user-controlled memory. Larger allowances should not change those boundaries.

Approve important actions

Review sending, purchases, destructive changes, and other consequential actions before execution.

Inspect the work

See the request, plan, tool activity, and verified outcome. Failed work should be visible too.

Change your mind

Pause a task, revoke connected access, and inspect or remove saved memory.

Before you join

A few practical answers.

Can I subscribe today?

No. Vynce is in development. The waitlist records early-access interest; it does not take payment or promise an access date.

Are the Teams allowances per person?

No. The proposed Teams plan includes three seats sharing 600 voice session minutes and 1,500 task credits each month.

What happens when an allowance runs out?

The proposed policy is to stop safely at the allowance and show the available options. Any paid overage or plan change would need clear terms and an explicit choice before charging.

How were these allowances estimated?

They use GPT-Live 1 at $0.05 per session minute, with a reserve of $0.055, and a proposed backend AI budget of $0.03 per task credit. A sample 4,000-input-token and 1,000-output-token Claude Sonnet 5.5 call costs $0.018 at the researched standard rates; longer tasks need more budget. Voice and task costs are additive. The forecast also reserves budget for shared hosting, tool execution, and payment processing. These estimates must be checked against real workloads before launch; they do not assume unlimited computer use.

Read the proposed usage assumptions
Does my Claude subscription cover this usage?

No such entitlement is assumed. The proposal uses separately metered first-party APIs. Personal Claude subscriptions and unreceived promotional credits are not included in the allowance calculation.

In development

Help shape what comes next.

Tell us the work you would like Vynce to help with. Join the waitlist for early-access updates.