Pilot pricing for pre-close transaction clarification.
CloseChase is still pre-launch and built for controlled design-partner pilots with fake/demo-safe data during the hackathon. These packages frame how solo bookkeepers, small bookkeeping and accounting firms, and outsourced finance teams could pay once billing exists; this build does not collect payment information, create subscriptions, or route visitors into checkout.
Pilot
For a bookkeeping firm willing to run one messy close with white-glove setup and direct feedback.
Free or symbolic
Design-partner pilot
Planned packaging only; billing is not active.
- Time-boxed workflow review
- Founder-assisted setup
- Feedback required
- No checkout in this build
Starter
For a solo bookkeeper or small firm that needs a repeatable way to collect transaction context.
$39/month
Planned small-firm package
Planned packaging only; billing is not active.
- CSV import for unclear transactions
- Private passwordless request batches
- Client explanations and receipts together
- CSV export for close notes
Growth
For firms running more recurring client close batches and needing cleaner review visibility.
$89/month
Planned growing-firm package
Planned packaging only; billing is not active.
- Everything in Starter
- Higher planned batch volume
- Review status visibility
- Founder-led workflow tuning
Concierge
For firms that want workflow mapping, migration help, and hands-on support during pilot rollout.
$199+/month
Planned white-glove package
Planned packaging only; billing is not active.
- Everything in Growth
- White-glove setup
- Workflow mapping
- Migration and support help
What is available today
The current product is a working narrow close-chase loop, not a broad bookkeeping platform. The boundaries below are intentional so firms and judges can evaluate the current build honestly.
| Capability | Status |
|---|---|
| CSV import/export | Supported for transaction lists and close-note exports. |
| Client portal links | A private passwordless client portal link is returned once at batch creation. |
| Explanations and receipts | Clients can explain charges and upload fake receipts together in the Production demo workflow. |
| Review workflow | Supported for reviewing answers and fake receipt metadata before month-end close. |
| Receipt storage | Production demo receipt binaries use private S3-compatible storage; DynamoDB stores receipt metadata only. |
| Persistence | DynamoDB-backed persistence is used in the hosted Production demo workflow. |
| Operator access | Production demo operator access uses Clerk Organizations. A temporary shared-key fallback exists only when explicitly enabled for transition, emergency, or demo use. |
Planned before real onboarding
These items are product direction, not live capabilities. They are listed to show the commercial path without overstating the current build.
| Planned area | Boundary |
|---|---|
| Billing | Billing is not active; Stripe, checkout, and payment collection are not implemented. |
| Broader roles and teams | Future work before real customer onboarding. |
| Tenant permissions | Future work; production-grade tenant isolation is not claimed. |
| Real customer receipt readiness | Fake receipt upload/download is demo-proven; malware scanning, retention, deletion, and audit policy are not implemented. |
| QuickBooks write-back | QuickBooks write-back is not implemented. |
| AI categorization | AI categorization is not implemented. |
| Email reminders | Real email reminders are not implemented. |
No checkout in this build
The pricing page is packaging and positioning only. It does not create subscriptions, collect card details, enforce usage, or route visitors into payment setup. Stripe is not wired and active billing is not available.
Operator auth boundary
Production demo operator access uses Clerk Organizations. DynamoDB stores workflow state and receipt metadata, receipt binaries are stored separately in private S3-compatible storage, and client portals use private bearer links. The temporary shared-key fallback works only when explicitly enabled for transition, emergency, or demo use, and is not production-grade auth. Client portal pages remain public to anyone with the recipient link. Broader team roles and tenant permissions remain future work.