This is a follow-up to my last post on rebuilding Invoicepedia. If you missed it, the short version: I had a broken invoice app, decided to fix it instead of abandoning it, spent a week cleaning the internals before touching any new features. That post is here.
So the foundation is fixed. The codebase is no longer something I am scared to touch. Good.
Now comes the harder question.
Is there actually a reason to build this? Not "I think freelancers would find this useful" kind of reason. A real one. The kind you find when you stop reading landing pages and start reading Reddit threads.
So that is what I did.
What Reddit Actually Says About Invoice Software
I spent a few days going through r/QuickBooks, r/waveapps, r/Bookkeeping, r/smallbusiness. Not looking for validation. Looking for the truth, which is usually buried in the comments of a frustrated post from someone who has had enough.
Here is what I kept reading.
QuickBooks: $30+ a month for a product that makes people feel like they are sitting in an airplane cockpit when all they want to do is send one invoice a week. The word that came up the most was "overwhelmed." One person called it unnecessary complexity for someone who is not running a full accounting department.
FreshBooks: accounts blocked days after payment. Payment information trapped inside the platform. One user literally wrote "I advise small businesses to steer clear." That is not a review. That is a warning with capital letters behind it.
Wave: used to be free and slowly started charging for things that used to be free. The free tier cannot fully automate recurring invoices anymore. An August 2025 thread had someone writing "Wave is in serious trouble" and switching to Zoho just to get reliable bank feeds. That is not confidence-inspiring.
Invoice Ninja: I tried it once. Opened the app, felt genuinely confused by the number of options, closed the tab. The Reddit threads confirm this. Long-term paying customers upgrading to enterprise and not getting what they paid for. One person writing AVOID AT ALL TIMES in capitals.
The pattern underneath all of these complaints is the same. People are not asking for more features. They are asking for the basics to work. No surprise blocks. No fee hikes halfway through the year. No UI that needs a tutorial to navigate. Just create an invoice, send it, track who paid.
The gap is real.
But Is It a Gap or a Graveyard
Here is the uncomfortable part.
The freelancer invoicing space has been "disrupted" many times already. Wave was supposed to fix this. Invoice Ninja was supposed to fix this. FreshBooks started with exactly this promise. Every one of them started simple and grew into the thing they were supposed to replace.
So the question is whether this is a genuine unsolved problem or a space where many products have already tried and quietly failed and nobody talks about the graves.
I sat with that for a while. I do not have a clean answer.
What I have is this: the complaints are recent. August 2025. People are still actively looking for exits from these tools. The cycle has not stopped. Which either means the gap is still open because nobody has held the line on staying simple, or it means the market is just exhausted and no solution will ever fully satisfy it.
Probably some of both.
What I decided is that I would rather try and find out than sit here theorising about it.
The Sprint
My partner and I are treating this like a hackathon. Intense, time-boxed, ship something that works end to end. We will write messy code probably. But the point is to have something real.
PDF generation, because an invoice app that cannot produce a PDF is just a form with extra steps. Email sending, so you never have to download a file and attach it to Gmail manually. A dashboard that shows three actual useful numbers the moment you log in: paid this month, outstanding, overdue. That is information you actually need. Not decorative charts.
Five real users. That is the goal for this first version. Not five hundred. Five people who use it and tell me what is wrong.
The Question I Keep Not Answering
This is the part that does not fit neatly into a project update post. But I am writing it here because this is my blog and I would rather be honest than polished.
I am an economics student. Not a CS degree. I have been building things, teaching myself, getting better every month. But I have been watching what is happening in the tech job market and there is a quiet dread underneath all the building. The kind you do not say out loud because it sounds like you are making excuses before you have even tried.
I watched a video recently by Harnoor Singh. If you do not know him, he has been building seriously for years, has company names on his resume that the industry respects, genuinely good developer. And he was talking about how even with all of that, finding work right now is actually difficult. Not "I have to apply to more places" difficult. Actually difficult.
I have been following his journey for a while. And if someone with his experience and credentials is navigating this with that kind of friction, the question that sits in my head is: what does that mean for me? With no CS degree. No company brand. Just a bunch of projects built out of curiosity and stubbornness.
I do not have a clean answer for that either.
The Shift I Think Is Happening
There was a version of the path that was clear for a long time. Learn DSA. Build projects. Crack the interview. Land the big job. That script worked for a generation.
I think it is being rewritten now. AI compressed the timeline faster than anyone expected. The bar moved. Recruiters who used to want projects now want end-to-end product experience, even from freshers. Not a to-do app. An actual shipped product that a real person used.
The wave seems to be shifting toward building. Micro SaaS. Indie. Real products at any scale. And maybe that is a good thing, maybe it is just a different kind of pressure, but it is the direction things seem to be moving.
What rebuilding Invoicepedia is giving me that no tutorial ever did is product thinking. Not just code. The question of why a feature should exist. Who it is actually for. What it should deliberately not do. That last one is the hardest and nobody teaches it.
Where I Actually Am
I do not know if this app will get users. I do not know if it will make enough to cover server costs. I do not know if building it helps me get a job or an internship or anything that pays.
What I know is that I am learning how to ship. How to think about a real problem instead of just the interesting technical parts. How to do research even when the research does not give clean answers. How to work under time pressure.
Maybe the credential era is giving way to a shipped-things era. Maybe it already has. I am betting on that not because I am confident but because it is the option I actually have access to right now.
Keep your head down. Build the thing. Ship it even if it is not perfect. See who shows up.
The more technical side of this, with the specific market research data and product decisions, is up on my Dev.to. If you are building in the freelancer tools or indie SaaS space, that post might be useful: link here
And if you are figuring out how to build a career in tech without the traditional path, I would genuinely like to hear how you are thinking about it. Ping me on my sociala