Request a controlled CloseChase pilot
CloseChase is for solo bookkeepers, small bookkeeping and accounting firms, and outsourced finance teams that want to stop chasing transaction explanations and receipts before close. The pilot focuses on one tracked client request batch, then review, export, and closeout.
Safe request path
This page does not store lead details, upload files, or create a public request-access database. Pilot access is coordinated privately through the hackathon submission and testing instructions.
- Use fake/demo-safe data only during the hackathon pilot.
- Do not send client names, bank data, receipt files, or sensitive financial details in the request.
- Billing, checkout, Stripe, QuickBooks/Xero write-back, AI/OCR, and real email reminders are not active.
- The workflow is production-shaped, but not compliance-ready for real customer receipt data yet.
Best pilot fit
- Solo bookkeepers
- Small bookkeeping and accounting firms
- Outsourced finance teams
Pilot workflow
- One tracked client request batch for unclear transactions
- Client explanations and fake/demo-safe receipt metadata review
- Operator review, CSV export, and explicit portal close or revoke
- Founder-assisted workflow feedback during the pilot
Trust 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. Client portal access uses private bearer links. Real customer receipt readiness still requires malware scanning, retention/deletion policy, audit logging, and legal/privacy review.
Built for controlled design-partner pilots with fake/demo-safe data during the hackathon. The workflow is production-shaped, but not compliance-ready for real customer receipt data yet.