Seven business shapes. One platform.
Every persona below uses the same codebase, same price, same login. The feature grid on /features lists every module. This page is for the "which subset do I actually care about?" question.
SaaS founder with MRR to bill
You invoice 30–200 customers monthly, half INR half USD / EUR, and you'd like the "chase-and-reconcile" loop to run without a human. You also wanted a lightweight sales CRM so deals stop living in a Notion board.
DSO drops 15–20 days in the first quarter. You stop copy-pasting into Gmail. CRM + invoicing speak the same customer id, so "converted a lead" becomes a one-click action.
UAE trading company (free-zone + mainland)
You move inventory between a JAFZA entity and a mainland UAE entity. Your buyers want bilingual Tax Invoices, your accountant wants the VAT-201 CSV without a three-hour spreadsheet dance, and you need to be PINT-AE-ready before Jan-2027.
Filing day becomes a CSV download instead of three days of Excel. Your accountant stops calling you on Thursday nights. The Jan-2027 mandate is a config change (wire the ASP) rather than a product rebuild.
Indian textile / electronics exporter
You ship to US / EU / UAE, file under LUT (so outputs are zero-rated), and the finance team hates that "realised vs unrealised gain" lives in a separate spreadsheet that never matches the invoice ledger.
FX lines reconcile themselves. Export-side GSTR-1 tables match the invoice ledger to the paise. Refund claims stop getting kicked back for schedule mismatches.
CFO at a logistics / distribution mid-market
You're building the finance function, not a point tool. You need an INSERT-only audit log your auditor will bless, RBAC your COO won't fight, bank reconciliation that doesn't need 4 accountants, and a platform that scales across 3 entities and 7 branches.
Your auditor asks one question, reads `audit_logs`, stops asking. Month-end close shrinks from 12 days to 4. Branch-level P&L lands without the per-entity spreadsheet merge ritual.
Accountant / CA firm
You file GSTR-1 and GSTR-3B across dozens of clients, reconcile GSTR-2B against purchase bills manually, and spend an unhealthy amount of time on TDS deduction tables. You want automation where the engine is right, supervision where it isn't.
You handle 3× the client load with the same team. GSTR-2B mismatch triage goes from days to hours. Junior accountants stop making AI-resolvable mistakes.
Hospitality / retail (POS + invoicing)
You run a café chain or retail chain with 3–50 counter locations, need a POS that doesn't charge per-seat like mad, and want the B2B side (supplier invoices, catering contracts) in the same system.
Per-seat POS vendor-lock dies. B2B and retail sides share one customer ledger, one tax engine, one dashboard. Franchise-style multi-branch rollup works out of the box.
Saudi Arabia business (ZATCA-compliant)
ZATCA wave-by-wave e-invoicing is already live. You need Phase 2 XML generation + TLV QR + bilingual Arabic Tax Invoices yesterday, and you'd like the same platform to work if you expand to UAE or India.
ZATCA wave readiness is a config change. The same platform covers UAE when you cross the border. Books close on time, not after.
Don't fit any of these?
Every module ships with every plan. Sign up free and turn on only what you need — the rest stay out of your sidebar until you do.