Why I Built MemwaMind

My mother has run an accounting practice in South Florida for over twenty years. Quinlan Accounting Consulting and Taxes is not a large firm. It is the kind of practice where the founder knows every client by name, remembers which ones file extensions, and can tell you from memory that Garcia's maintenance expense spiked last October. It is also the kind of practice where that memory lives in one person's head.

I watched her work for years before I understood what I was seeing. The work itself was not the problem. She is excellent at the work. The problem was everything around it: the scattered files in three different folders and two email accounts, the commitments made in phone calls that nobody wrote down, the anomalies that only surfaced when a return was half-finished, the meeting prep that took an hour of pulling up old notes and trying to remember what was discussed last time.

None of this was laziness or disorganization. It was the natural consequence of running a practice that runs on human memory. Every small firm works this way. The institutional knowledge — who promised what, which client changed banks, which engagement is waiting on a W-2 — lives in the practitioner's head and nowhere else. When the practitioner is busy, things slip. When they are not available, the knowledge is not available either.

The name MemwaMind begins with memwa — a Haitian Creole word rooted in the French mémoire, meaning memory. It is the word my family uses for remembering. When I set out to build a system that could carry the operational memory of a small firm, the name felt inevitable: the firm's memory, made operational.

I did not build MemwaMind to replace accountants. The idea that software can replace the judgment of someone who has spent twenty years learning her clients is, frankly, absurd. I built it to carry the operational load that has nothing to do with judgment: noticing that a number is unusual, remembering that a deadline is approaching, preparing the context for a meeting, surfacing the document that was uploaded last week but never reviewed. The accountant does the thinking. MemwaMind does the noticing, remembering, and preparing.

Every feature in the product traces back to something I watched my mother do manually. The morning briefing exists because she would spend the first thirty minutes of every day pulling up notes from yesterday. The anomaly alerts exist because she would catch variances by feel — and sometimes miss them when the volume was high. The suggestion engine exists because client files arrive and nobody reviews what changed until tax season. The commitment tracker exists because “I told Garcia I'd send that by Friday” lived only in a phone call.