The real test of automatic expense tracking: a month I couldn't try

I build an expense tracker. Last month I could not have used one.

Here is what the month looked like. A complete solar system went onto the house, and my savings went with it. Then a car happened: partly planned, mostly not, and the gap between the two got closed by selling things we owned. Furniture left the house so the car could arrive. Every one of those days had money moving in amounts that made my chest tight, and my head was running at its limit the whole time.

I say all this because there is a version of this story where I tell you my app has a beautiful logging flow. Three taps, very fast, lovingly designed. That version is useless. In a month like that, there is no such thing as a quick manual task. There is only what happens on its own and what does not happen at all.

What actually happened

Every time a payment went through, the bank sent its receipt. I shared it to Trail straight from the bank's app: the same share button you use to send a photo to a friend. That was the whole interaction. Two seconds, done in the elevator, done in the parking lot, done mid-conversation with the solar installer.

I did not open the app. Not to log, not to categorize, not to check that it worked. I had nothing left over for checking things.

When I finally did open it, weeks later, everything was there. A folder for the car's lease payments, filling itself with each installment. The solar project, categorized in one place, every payment dated and remembered. A timeline of the most expensive month of my year, assembled while I wasn't looking.

The test of an expense tracker is not the month you're motivated. It's the month you have nothing left to give it.

Why this worked when I couldn't

Two boring pieces of engineering carried the whole month.

The first is that Trail accepts expenses in whatever form they already exist. A shared bank receipt, a forwarded bank SMS, a photo of a paper receipt, a sentence said out loud. You never translate your life into form fields. The receipt you already have IS the log entry.

The second is that Trail learns your routing. The first lease payment, I told it where to file. Every one after that filed itself: same source, same folder, same category, no questions. The app noticed the pattern so I didn't have to maintain one.

Neither of these is impressive to demo. Nobody claps for a share sheet. But they are the difference between a tracking habit that survives real life and one that quietly dies the first hard week and leaves you with a guilt app on your home screen.

The part I didn't expect

The surprise wasn't that the logging worked. I wrote the code; I hoped it would. The surprise was what it did for my head afterwards.

That month generated exactly the kind of financial fog that used to eat me: where did it all go, how much has the car actually cost so far, what did the solar really come to in the end. Questions I would normally answer with an hour of bank statements and a sinking feeling.

Instead I asked the app. Plain words, real answer, drawn from my own receipts. The fog turned out to be optional.

I did not build Trail for the months when life is calm and logging is easy. I built it, it turns out, for exactly the month I just had. I only found that out because it happened to me first.

Trail is on the App Store and Google Play. Free to start: 50 logs and 50 AI questions, no time limit, no card.