I built CloseBook to simplify cash advance reconciliation for small teams
I kept seeing the same operational problem: someone receives a cash advance or temporary project budget, records expenses across spreadsheets, notebooks, receipts, and messages, then struggles to determine how much money should remain.
Most accounting tools are too complex for this specific workflow, so I built CloseBook.
The process is intentionally simple:
Money received → Expenses recorded → Expected balance calculated → Actual cash counted → Shortage or surplus explained → Book closed.
CloseBook is designed for small businesses, project teams, nonprofits, field workers, and anyone responsible for temporary funds.
The product is now live, but I am still validating the market. My focus is no longer adding major features. I want to understand who experiences this problem frequently enough to adopt a dedicated tool instead of continuing with spreadsheets.
You can see it here:
Have you ever managed a cash advance or temporary project budget? How did you reconcile it at the end?
What caught my attention is that you're not really competing with accounting software.
You're competing with the point where a recurring workflow becomes important enough that people stop treating it as "just another spreadsheet." That's a very different threshold than replacing an existing tool.
That’s a great way to frame it. CloseBook isn’t trying to replace accounting software; it’s built for the point where recurring advance tracking and reconciliation become too important and error-prone to keep treating as “just another spreadsheet.”
The real challenge now is proving that this threshold happens often enough for teams to adopt a dedicated tool.
I'm glad it resonated.
I'd be interested in continuing the conversation by email if you're open to it. What's the best email to reach you on?
Thanks for reaching out. I prefer not to share personal contact details publicly, so I’d be happy to continue the conversation here on Indie Hackers. Could you share what you’d like to discuss?
Fair question.
I'm not looking to give product feedback or consulting. There were a couple of strategic decisions behind CloseBook that caught my attention, and I'd rather discuss those by email than try to unpack them in a public thread.
If you're comfortable sharing it, what's the best email to reach you on?
Thanks for clarifying. I’m not comfortable sharing my email or moving the conversation outside Indie Hackers. If there’s anything you can discuss publicly, you’re welcome to share it here. Otherwise, I’ll leave it there. Thanks for understanding.
Nice niche — cash advance reconciliation is surprisingly painful. Curious if this is more of a one-off fix or something users end up needing every month?
That’s exactly the key question. CloseBook is not intended as a one-off calculator. The recurring use case is for teams that issue advances regularly — monthly field expenses, project cash, travel advances, procurement, or petty cash.
Each new advance creates another cycle of tracking, reconciliation, and closeout, so the value grows when the workflow repeats.
That makes a lot of sense — repeated cycles are where tools like this really compound in value.
The interesting part is usually the first transition from ‘we can manage this manually’ → ‘we need a system.’
Are most users coming in already feeling that pain, or discovering it after trying to track a few cycles themselves?
That’s exactly what I’m trying to validate right now. CloseBook is still early, so I don’t have enough usage data yet to say which path is more common.
My current hypothesis is that teams usually reach this point after a few repeated cycles — missing receipts, unexplained differences, or closeouts that become difficult to verify. But I’m watching closely whether users arrive already feeling that pain or only recognize it after trying the workflow a few times.
That distinction will shape both the onboarding and how CloseBook is positioned.
From what I’ve seen, teams don’t search for this until something breaks — but once it does, they want it solved immediately, not explored.
If you can surface the “hidden cost” (time lost per cycle / unreconciled cash risk), you’ll pull people in earlier.
Happy to help you frame that if you want — this is one of those products that sells way easier with the right angle.
That’s a strong point. The hidden cost may be a better angle than simply describing the workflow — especially the time lost rebuilding records, delayed closeouts, and the risk of unexplained cash differences.
I’d genuinely be interested in how you would frame that message. Feel free to share your take here.
I’m already working your suggestions ^_^
Great, do you have an email i can send you my results on?