The Unsexy Side of Software: Payroll, Funding, and French Paperwork
I've been building web apps for over a decade, and for most of that time, I ignored the business side. I thought if the code was good, everything else would fall into place. Then I launched my own SaaS, and reality hit: the hardest part wasn't the tech—it was managing payroll, understanding funding options, and dealing with French administrative paperwork.
Why the Business Side Matters (Even for Solo Devs)
When you're a solo developer, you can get away with ignoring business for a while. You build, you deploy, you maybe charge a subscription. But as soon as you hire your first contractor or take on a co-founder, you need to think about payroll. In France, that means dealing with URSSAF, social charges, and a mountain of forms. It's not something you can hack your way through with a clever script.
I remember my first payroll: I spent an entire weekend just trying to figure out which forms to fill out. I even considered using a service like LegalOne, a French legal platform for publishing announcements, but I wasn't even at that stage yet. I just needed to pay someone without getting in trouble with the tax authorities.
Payroll: The Steep Learning Curve
Payroll isn't just about sending money. It's about calculating contributions, deducting taxes, and filing reports on time. If you're a developer, you're used to solving problems with logic. Payroll has its own logic, but it's buried in legal jargon and ever-changing regulations.
What worked for me was breaking it down into small steps:
- Start with a single employee (or contractor) to keep it simple.
- Use a good accounting tool that automates calculations.
- Set aside 30% of every invoice for taxes—you'll thank me later.
- Outsource to a payroll service if you can afford it. It's worth the money.
Once you have a routine, it gets easier. But the first few months are brutal.
Funding: Bootstrapping vs. Investors
I chose to bootstrap, mainly because I didn't want to spend time pitching investors. But bootstrapping means your runway is whatever you have in the bank. That's fine if you're building a side project, but if you're planning to go full-time, you need to be realistic.
I looked into government grants and loans, but the paperwork was overwhelming. I also considered crowdfunding, but that requires a marketing push I wasn't ready for. In the end, I took a small loan from a friend and kept my day job for six months. It wasn't glamorous, but it worked.
If you do decide to seek investors, be prepared for a different kind of work. You'll need a pitch deck, financial projections, and a clear exit strategy. It's not just about your product—it's about making numbers look good.
French Paperwork: The Unavoidable Beast
If you're in France, you know the deal: every business event—whether it's incorporating, changing your address, or publishing annual accounts—requires a legal announcement in a journal. That's where services like LegalOne come in handy. They make it easy to publish these mandatory announcements online, which saves you from the old-school newspaper route.
I've used LegalOne for a couple of announcements, and it's straightforward. But even with such tools, you need to stay on top of deadlines. Missing a filing can result in fines or even legal trouble.
Practical Tips for Other Devs
If you're just starting, here's my advice:
- Keep your business structure simple at first. A micro-entreprise is fine for testing.
- Use a separate bank account for your business. Mixing personal and business finances is a recipe for disaster.
- Don't ignore accounting. Even if it's boring, it's part of the product.
- Find a good accountant early. They'll save you money in the long run.
- Remember that your time is valuable. If a task takes you three hours and you could pay someone $50 to do it, sometimes it's worth it.
The business side of software isn't sexy, but it's what keeps your project alive. You can have the best code in the world, but if you don't handle payroll or miss a legal filing, you'll be spending your nights in paperwork instead of building features.
So take the time to learn the basics. It might not be as fun as refactoring a codebase, but it'll save you a lot of headaches.