LedgerMind AI: Turning a Small Business Owner's Voice Notes into Records They Can Trust

Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle Submission 💸

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle

Most small business owners in Nigeria don't keep proper books. They keep notes: a message to themselves, a page in an exercise book, a voice memo. "Paid the plumber 40,000." "Client owes me 60,000." Those notes hold the real history of the business, but nobody can ask them questions like "how much did I take in this week?" or "who still owes me?"

LedgerMind AI is a configurable business-record and intelligence platform that turns those everyday notes into structured records and honest reports. An owner types or speaks a note. A hosted Gemma model reads it and proposes a draft record. The owner reviews and confirms it. The backend then calculates every figure from the saved records. Only after that does the AI write a plain-language summary of how the business is doing.

Who would pay for it: shop and restaurant owners, small contractors and farmers, who want to know where their money is going without learning accounting software or hiring a bookkeeper.

I'm submitting this unfinished, on purpose, and I want to be clear about what is and isn't done.

I have a written list of 25 specific fixes for these. I chose to publish now rather than miss the deadline, and I will keep fixing them. Any commits after the October 18 deadline are listed in the repository README.

The app runs on Render's free tier, so if it has been idle, the first load can take up to a minute while the server wakes up. Please give it a moment.

GitHub repository: IamClassified9/LedgerMind-Ai

Development began on October 13, 2026. The repository was initialized on October 16, 2026.

Sentry grouped the failures on my AI endpoints into separate issues. In the 14-day view, with everything first seen in the last day or so:

That list taught me four things about my own code:

Next, I'll add exponential backoff with jitter, honor Retry-After, make each attempt its own span, and send the model a smaller snapshot.

I used Gemma through hosted inference, and I want to be upfront that this is a trade-off. Nobody has to own a GPU to use the app, but a customer's note does leave the app to reach the provider. LedgerMind AI does not claim that data stays on infrastructure I control when hosted inference is used.

What the open-weight choice gives me is a way out. When the hosted endpoint returned errors that survived my retries, the fix I can reach for is to configure another provider, or self-host once a business can afford it, rather than wait for one vendor. I can also keep the model on a short leash, since it never writes SQL or saves records and the backend computes every figure. If a better or cheaper model appears, I can replace the narrator without touching the numbers.

The next step where open weights matter most is fine-tuning for how these owners actually write: informal notes, currency amounts, and phrases like "client owes me" where the direction of money changes everything. A general-purpose API handles that poorly, and my own extraction mistakes show it.

Render hosts the deployed LedgerMind AI application, so a business owner can use it from a browser without installing the backend or running a model on their own computer.

The deployment connects the React, TypeScript and Vite frontend to the FastAPI backend. When a user submits a business note, the backend handles the request and calls the hosted Gemma inference service. The model proposes a structured draft, which the user reviews before confirming it. The backend then saves the approved record and calculates the figures used in reports.

Render makes the application accessible, while the external inference service supplies the model capabilities. I do not claim that Gemma itself runs on Render.

Deploying the app exposed a real operational issue: the hosted Gemma service sometimes returns errors or takes too long to respond, and on Render's free tier the server itself can be asleep when the first request arrives. Sentry helped me investigate the Gemma failures. My next improvements are stronger retry handling, clearer error reporting, better response times, and a friendlier "server is waking up" message.

This deployment shows how a small-business AI application can be made available without requiring its users to operate their own model-serving infrastructure.