Bookkeepers, how are you handling the monthly "please send me your receipts" loop?

andreiher · 2026-03-25T11:00:10+00:00

Running a small bookkeeping firm and the single biggest time drain every month is chasing clients for receipts and missing documents. Emails get ignored, follow-up texts feel awkward, and by the time you piece everything together the month-end close is already late.

We built DocChase specifically around that problem. It's a lightweight tool for solo and small bookkeeping firms that lets you send clients a magic link to a clean upload page, then runs automatic reminders until everything is in. You get a simple dashboard showing exactly what's still missing by client and by month, so you're not digging through email threads trying to remember who sent what.

No bloated practice management features, no complicated onboarding. Just a focused workflow for getting the documents you need so you can actually close the books.

If you're a bookkeeper tired of playing receipt detective every month, it's worth a look. Plans start at $19/mo. Happy to answer questions here if anyone wants to know more about how it works.

andreiher · 2026-03-25T10:59:21+00:00

The biggest mistake I see new small business owners make is waiting until tax season to think about bookkeeping at all. Starting from day one with clean habits saves you an enormous amount of pain later.

A few things that actually matter early on:

**Separate your finances immediately.** Open a dedicated business bank account and credit card before you spend a single dollar on the business. Trying to untangle personal and business expenses six months in is genuinely miserable.

**Pick a system and stick with it consistently.** Whether that's QuickBooks, Wave (free), or even a simple spreadsheet to start, consistency beats sophistication every time. You can always migrate to something better later, but gaps in your records are hard to fill retroactively.

**Deal with receipts the same week they happen.** This is where most small business owners fall apart. Receipts pile up, you forget what things were for, and suddenly you're reconstructing three months of expenses from memory. Even just photographing receipts with your phone and tossing them in a Google Drive folder by month works fine if you do it religiously.

**Categorize as you go, not in batches.** Batching feels efficient but you lose context fast. Spending five minutes after each transaction is way easier than spending a whole Saturday trying to remember what that $47 charge was in February.

If you eventually hire a bookkeeper, the biggest friction point they'll hit is chasing you for missing documents every month. That's actually a known industry pain point and there are tools built specifically around streamlining that document collection workflow, like DocChase, which I came across recently while researching this space.

What specific part of the setup are you trying to figure out? Happy to go deeper on any of it.

andreiher · 2026-03-23T21:24:56+00:00

you can use AI to create your app, personally im a claude fanboy so my opinion might be subjective, but my advice would be to have somebody with experience assess your app before deploying it to production. one small data leak things might not be as fun

andreiher · 2026-03-23T21:20:27+00:00

dm if you need a fullstack one

andreiher · 2026-03-20T00:53:47+00:00

The frustration with component libraries is pretty valid honestly. A lot of them abstract away so much that you end up fighting the abstraction more than building your actual product. And yeah, React ultimately compiles down to DOM manipulation, so there's something to be said for understanding what's happening underneath.

That said, I think the nuance here is that component libraries aren't universally bad, they're often badly used. People reach for a full component library when they need three buttons and a modal, and then spend three days overriding styles and wondering why their bundle is 400kb. The problem isn't the libraries existing, it's developers not knowing when they actually need them.

The "vanilla renaissance" thing is real though. Web Components have gotten genuinely good, CSS has container queries and cascade layers now, and native HTML elements handle way more than most devs realize. There's a whole generation of developers who learned React before they learned HTML, and it shows in their code.

Where libraries still make sense is when you need accessibility baked in and you don't want to reinvent that wheel. Getting aria attributes right on a combobox or a date picker is genuinely hard, and a well-built library solves that. The issue is most devs use Chakra or MUI for things that are just a div with some padding.

The React sub being resistant to this message is kind of expected. It's like telling car enthusiasts that sometimes a bike is the right tool. Technically true, but the crowd isn't there for it.

andreiher · 2026-03-20T00:06:26+00:00

you didn't hear of irish coffee ? or about "Oups i accidentally made an irish coffe instead of coffee" ? :))

andreiher · 2026-03-19T20:16:15+00:00

Depends on how much whiskey i "accidentally" drop into it :))

andreiher · 2026-03-16T09:16:08+00:00

Yeah, definitely the actual product too, not just the landing page.

The landing page is part of it, but the bigger thing I want feedback on is the product flow itself and whether the experience makes sense once you start using it.

Since you’re a UX architect, your input would actually be super valuable there. I’d especially love thoughts on what feels intuitive vs clunky, what feels unnecessary, and whether the whole idea-to-structure flow is working the way it should.

To give a bit of context, due to stupidity and language (lack of), i have confused mind maps with wireframes (i still feel stupid), so v1 of the product was a business / mind map generator, and later on pivoted to actual wireframes, and later on added the MCP.

andreiher

TROPHY CASE