Short answer: open the admin panel in your AICHE Pro account, add the number of seats you need, invite teammates by email, assign roles, and one card pays for everyone. No sales call, no procurement deck, no minimum seat count.
The problem this solves
Most voice-typing apps treat any team larger than one as an enterprise event. You click "Teams" and land on a contact form. A salesperson emails back two days later asking about headcount and procurement timelines. By the time the contract is signed, the four people who actually wanted to use the tool have moved on. AICHE Pro skips that loop: the team plan is the same Pro tier, with an admin panel turned on, billed by seat.
How it works
- Sign up for AICHE Pro, or upgrade from Personal, on any platform (macOS, Windows, Linux, iPhone, iPad, Android).
- Open the web dashboard and switch to the Team tab. The admin panel shows seat count, current members, and the billing card on file.
- Click Add seats. Pick a number. The new total bills on your next cycle, prorated for the current month.
- Invite teammates by email. They get a link, sign up (or sign in), and the seat assigns automatically.
- Assign roles in the member list. Admin can add/remove seats, manage billing, and invite. Member can use AICHE Pro features but doesn't see billing.
- Manage everything later from the same panel: revoke a seat when someone leaves, swap an admin, download invoices, change the card.
- One bill arrives monthly or annually, on the same Pro pricing schedule that applies to individual subscribers.
What's included on every seat
Every team seat is a full AICHE Pro seat. Nothing is held back for a higher tier.
- Up to 10 devices per seat on Pro. Teammates use the same login across their work laptop, home laptop, phone, and tablet. No "work seat vs personal seat" license split.
- Software Development profile. Recognition tuned for code identifiers, CLI flags, library names. Useful when half the team is dictating into Claude Code or Cursor.
- REST API access. Each Pro seat can call the API from scripts and tools. Useful for the one engineer on the team who wants to wire AICHE into a build pipeline or internal CLI.
- Voice Code for AI coding agents. Pause-aware auto-send into Claude Code, Codex, Cursor, Antigravity.
- Priority processing and 24h weekday email support.
- Custom vocabulary, 50 entries per user. Each teammate manages their own dictionary - names, brands, internal jargon, repo identifiers.
Self-serve from day one
AICHE's posture: the admin panel is part of the Pro tier. A four-person team buys four seats the same way one person buys one seat. A forty-person team works the same way. There is no contract gate, no minimum seat threshold, and no enterprise sales motion you have to clear to use the product.
For a small team this matters because it removes a procurement step. For a mid-size team it matters because the admin can add or remove seats the same week someone joins or leaves, without filing a ticket with a vendor. For organizations with mixed OS environments - Office on Windows, design on macOS, engineering on Linux, field staff on iOS and Android - everyone gets the same seat, same features, same admin panel.
Roles and what they can do
The role system is intentionally minimal. Two roles, clearly scoped.
Admin. Sees the team panel. Adds or removes seats. Invites and removes members. Manages the payment method and downloads invoices. Reassigns the admin role if the original buyer leaves. An admin is also a regular Pro user - they have their own seat for using AICHE.
Member. Has a full Pro seat. Doesn't see billing, can't add or remove other seats. Sees their own usage, dictionary, devices, and settings.
Teams with more than one admin are supported. A small team usually keeps one admin (the founder or office manager). A larger team adds a second admin for redundancy, or to delegate billing to finance while keeping operational control with engineering.
Billing and seat changes
- Pricing per seat is the Pro tier price. $9.99/mo or $99.99/yr (regular Pro pricing). No bulk discount tier listed publicly - if you need one for a larger headcount, the admin panel doesn't gate you behind a sales call, but the published price is what you pay.
- Add seats anytime. New seats prorate for the current cycle and roll into the next bill.
- Remove seats anytime. Removed seats credit toward your next bill. Members lose Pro access at the next billing cycle, not immediately, so people don't get locked out mid-day.
- Annual billing available. Switch the team to annual to pay $99.99 per seat per year ($8.33/mo equivalent).
- One invoice. Whatever your seat count, finance gets one PDF per cycle. No reconciliation across individual logins.
- 7-day free trial covers the first seat. Useful for piloting before rolling out.
Privacy posture for teams
The privacy model is the same as the individual product, applied per seat.
- End-to-end encrypted cloud sync. Each member's notes are encrypted on their device with a passphrase only they hold. Admins cannot read teammate notes through the team panel - the team plan is a billing and access layer, not a content access layer.
- Audio processed quickly and discarded. Same processing pipeline as Personal. AES-256-GCM encryption at rest for synced data, Argon2id key derivation.
- Local-first by design on desktop. Nothing leaves a teammate's machine unless they explicitly send it. The team plan does not change this.
- Privacy-first analytics. Firebase Analytics tracks sign-in events and subscription conversions only - no transcription content, no audio, no recordings, no sharing behavior. Desktop diagnostics are user-initiated only (the "Send Diagnostic Report" button, or the OS-level crash share prompt). Android explicitly omits the AD_ID permission.
If a teammate leaves, the admin revokes the seat. The teammate's notes stay with them on their personal device unless they were syncing through a company-managed account; the admin panel doesn't expose note content to admins under any role.
Tips
Start with the people who already use AICHE. If two engineers on the team are already on Personal subscriptions, convert their licenses into team seats first. Cleaner billing, same workflow.
Use one admin for billing, one for ops. On teams larger than ten, split admin duties: finance owns the payment method, an engineering manager owns seat assignment. Both can be admins.
Combine with custom vocabulary rollout. Each seat gets 50 custom vocabulary entries. For a team using the same product names, repo names, and internal jargon, drop a shared list in your wiki so new members populate their dictionary on day one.
Buy annual for predictable budgets. $8.33/mo equivalent per seat on annual versus $9.99/mo on monthly. Finance prefers a single annual line item per team over a recurring monthly variable.
Audit seats quarterly. Open the panel, scan the member list, revoke seats for people who left or moved to a role where they don't dictate. Saves more than the audit costs.
Result: a four-person team is paying for and using AICHE Pro in the time it takes to fill out a typical procurement form.
Try it now: open the AICHE web dashboard, click the Team tab, add a second seat, and invite one teammate by email. They'll be dictating into Claude Code, email, and Slack before the day is over.