16 August 2026
Updated 16 August 2026 · Beech Product Education Team
What a seat is, Starter through Business, trial and expiry, payment, and how Admins export (or delete) firm data.
Intent: Explain billing, seats, and export in a way that a new team member can follow without prior Beech context.
Who this helps: Architecture studio admins, managers, and contributors who need a repeatable operational workflow.
Every plan has the same product. Plans differ by seat count, active project limit, and bundled Vault — not by feature flags. A seat is an active Admin, Manager, or Contributor.
Plans and trial
- Starter — up to 8 seats · 30 active projects · 50 GB Vault.
- Professional — up to 25 seats · 60 active projects · 125 GB Vault.
- Business — up to 60 seats · 200 active projects · 250 GB Vault.
Need more than Business? Contact support — there is no separate Enterprise checkout SKU. New firms get 30 days full access with no card. Early-adopter firms (first 25) can subscribe from Firm settings → Billing (Admin) via Razorpay; later firms contact support. Monthly or annual; annual shows the rupee saving on the pricing page. GST applies; receipts come from Razorpay when you pay in-app.
Vault add-ons
Need more than the bundled Vault? Admins buy one monthly storage add-on from Firm settings → Vault. First payment is prorated to your Beech billing day; then the full monthly amount. Billing shows Vault next charge next to Beech renews.
If the plan lapses
The app sends you to renewal. Settings stay available so an Admin can pay. Contact support if you need a short extension.
Export and delete
Admins download a ZIP of JSON, Excel, and Vault files from Firm settings → Data & Privacy → Export firm data (projects, drawings, tasks, users, vendors, reviews, and Vault folders when storage is configured — not password hashes). Delete firm requires typing the exact name, then a 7-day grace period you can cancel. After that, data and files are gone.
Prerequisites
- Confirm you can access the project and the page referenced in this workflow.
- Collect any drawing references, due dates, and ownership details before you start.
Expected outcome
By the end of this workflow, your team has one visible, repeatable process and cleaner handovers.
Common mistakes and prevention
Mistake 1: Skipping context fields (owner, due date, status notes), which makes follow-up harder.
Mistake 2: Treating chat updates as source of truth instead of recording the update in Beech.
Troubleshooting checklist
- 1Troubleshooting step 1
If a control is missing, verify your role has permission for the action.
- 2Troubleshooting step 2
If results look wrong, check filters and refresh to confirm latest synced data.
Full reference: Plans & Billing in the user guide
Related guides: Roles and permissions playbook · Security controls for admins · Exporting data for audit or handover