I built a text-first expense tracker in a week with zero coding experience — here's exactly how
I want to share how I built TextLedger from idea to live app in about a week as a complete no-code beginner, because I wish someone had written this when I was starting.
THE PROBLEM I WAS SOLVING
I kept texting expenses to my own notes app because it was faster than opening any finance app. Every app I tried either asked for my bank login before giving me any value, or took 30+ seconds to log a single coffee.
I noticed other people doing the same thing — texting themselves expenses, making voice memos, writing in their notes app. Nobody was using the proper tools because the friction was too high. That felt like a real gap worth building on.
THE CONCEPT
One simple idea: what if logging an expense felt exactly like sending a text message?
You type "12 lunch" and it logs it. First number = amount, everything after = the note. No forms, no dropdowns, no categories to select, no bank login ever. Auto-categorizes by keyword, groups your history by day, shows a monthly summary with category breakdown, exports everything to CSV.
HOW I BUILT IT
I have zero coding experience. Here's the exact stack:
- Started prototyping in Base44 to validate the concept quickly
- Moved to Lovable for the production UI
- Supabase for the backend database
- Bought textledger.app for $12 to make it look like a real product
Total cost so far: under $50. Total time: about a week of evenings.
WHAT I LEARNED
The hardest part wasn't building — it was keeping it simple. Every AI builder wanted to add forms, dropdowns, and category selectors. The whole point of the app is that there are NO forms. Getting the AI to respect that took more back and forth than any actual feature.
The second hardest thing was knowing what NOT to build. I had ideas for receipt scanning, bank integrations, budgets, charts, notifications. I cut all of it. The MVP is just: type it, see it, export it.
WHERE I AM NOW
App is live at https://textledger.app and free right now. Looking for my first 10 real users who will actually use it daily and tell me what's broken.
My goal is $2K/month within 90 days at $10/month — that's only 200 users. Feels achievable if I can nail retention.
Happy to answer any questions about the no-code build process, the Lovable + Supabase stack, or the product decisions I made along the way.
What would make you actually use something like this daily?
building something useful in a week with zero coding background is impressive. the text-first approach is smart — lowest possible friction for the user. we took a similar approach with our web analysis tools: paste a URL, get results. no forms, no dashboards, no learning curve. the simpler the input, the more people actually use it. whats your plan for getting the first users who arent friends/family? thats usually the hardest jump. for us it was commenting on IH posts where people described the exact problem our tools solve — way more effective than any launch post.
The "paste a URL, get results" parallel is exactly right — the simpler the input the more people actually use it. That constraint forces you to be really clear about what the core value actually is.
On getting first users who aren't friends or family — honestly it's already happening faster than I expected. I launched 48 hours ago with zero network and have 3 real strangers using it, one of whom logged 6 expenses within minutes of signing up and did it in Spanish which I hadn't planned for at all.
The channels that worked: r/sideprojects hit #1 on launch day which drove the initial traffic. Being genuinely specific in the post about the problem, the stack, and what I learned seemed to matter more than the product itself.
Your IH commenting strategy is interesting — I've been doing that here too and it's how I got posting privileges unlocked by Courtland within a day or so. Finding threads where people describe the exact problem is hunting with a rifle not a shotgun.
The honest next challenge is retention not acquisition. Getting strangers to sign up is one thing. Getting them to log expenses on day 5 and day 10 is what actually matters. Still figuring that part out.