Plans and packaging draft
This page is a working draft for how lim could package customers into three plans:Startup, Business, and Enterprise.
This is a product draft, not a final pricing or contractual document. Some Enterprise items are
roadmap candidates rather than generally available features.
Packaging principles
- Keep core accounting and AI-native workflows in every plan. Those are the product, not upsells.
- Gate by operational complexity, governance needs, and deployment requirements.
- Make the upgrade path obvious:
Startupfor one company,Businessfor team workflows,Enterprisefor compliance and infrastructure constraints.
Plan summary
Startup
For founder-led teams that need real-time accounting, invoicing, expenses, and AI-assisted
bookkeeping without formal finance operations.
Business
For growing teams that need approvals, deeper controls, payroll and contractor workflows, and
admin-facing APIs.
Enterprise
For larger or regulated organizations that need SSO, audit packages, custom deployment, and
dedicated support.
Proposed feature matrix
Proposed plan definitions
Startup
Use this for the default self-serve plan.- Real-time ledger, journals, reports, and dashboard
- Natural language accounting and judgment-engine learning
- Invoices, expense reports, documents, and bank reconciliation
- Basic employee and contractor data
- One company, small member limit, lightweight permissions
- Best for startups that want the system of record without finance-team workflow overhead
Business
Use this as the first serious upgrade for operating teams.- Everything in
Startup - Multiple companies or business units
- Approval policies, review flows, and stronger audit visibility
- Payroll, contractor payments, and broader back-office operations
- Full API access for internal tooling and accountant / firm workflows
- Priority support and onboarding help
Enterprise
Use this for security, compliance, or infrastructure-driven deals.- Everything in
Business - SSO / SAML, SCIM, and centralized identity controls
- Audit package export, advanced review controls, and compliance configuration
- Dedicated environment or self-hosted deployment
- Custom connectors, migration support, and implementation assistance
- Dedicated support, SLA, and roadmap coordination
Suggested upgrade story
Customers should feel the progression clearly:Startup: “We need bookkeeping and reporting to work without hiring more ops people.”Business: “We now have multiple reviewers, payroll, approvals, and accountant collaboration.”Enterprise: “We need security review, procurement approval, and deployment flexibility.”
Recommended boundaries
The cleanest packaging boundary is not to hide the accounting engine itself. Instead:- Keep the ledger, AI workflows, and reports in all plans.
- Put workflow depth and control depth into
Business. - Put security, deployment, and procurement blockers into
Enterprise.