Why I Left Enterprise Software to Build a SaaS for Freelancers

Ten years of enterprise software, and one recurring pattern

I spent over a decade building software for insurers, consultancies, and international organizations — including a stint at the United Nations. The systems I worked on had a lot in common: clearly defined processes, every tool talking to the next one, and a business analyst somewhere whose entire job was making sure nothing fell through the cracks between departments.

Then I started paying closer attention to how freelancers and small businesses actually run their client work, and I noticed the opposite. A quote built in one app. A contract template sitting in a folder somewhere, copy-pasted and edited by hand for every new client. An invoice generated in a completely separate tool. A spreadsheet — always a spreadsheet — trying to track who actually paid and who didn't.

Nobody had designed this workflow. It had just accumulated, one "good enough for now" tool at a time.

The gap enterprise software doesn't have

In enterprise systems, disconnected tools are treated as a defect to be fixed — an integration project, a data migration, a line item in next year's budget. Freelancers and small businesses don't get that luxury. They're the business analyst, the developer, and the end user all at once, with no time to build the integration themselves and no budget for someone else to build it for them.

That gap is what convinced me to build Contractly Pro. Not because freelancers needed another individual tool — they already have quote generators, contract templates, invoicing apps, and payment processors, often several of each. What they needed was for those four things to be the same system, so a quote becoming a contract, and a contract becoming an invoice, didn't require re-typing anything or trusting a spreadsheet to stay in sync.

Why now, and why this shape

Two things made this the right time to build it. First, the tooling I'd use to build a real SaaS — Angular on the frontend, .NET and Azure on the backend, mature libraries for e-signatures and payments — had matured to the point where a solo founder could realistically ship something production-grade, not just a prototype. Second, regulatory shifts like France's 2026 e-invoicing mandate were about to make "figure out compliance yourself" a much more expensive default for freelancers than it used to be.

I didn't want to build a generic project-management tool with invoicing bolted on, or an invoicing tool with a contracts feature nobody asked for. I wanted the actual sequence — quote, contract, invoice, payment — to be one connected flow, built by someone who has spent a career caring about what happens when systems don't talk to each other.

"The gap wasn't a missing feature. It was the space between four separate tools that were never going to talk to each other on their own."

What building it solo has confirmed

Every enterprise system I ever worked on had one non-negotiable rule: the boring parts — sequencing, record-keeping, compliance — have to be correct, because that's what everything else depends on. That rule didn't change just because I was building for freelancers instead of insurance claims processors. Invoice numbering still has to be sequential. Records still need to persist somewhere durable, not on a laptop. A contract still needs to mean something legally.

Freelancers deserve software held to that same standard — not a lighter version of enterprise rigor, just applied to a smaller, faster-moving business. That's the premise Contractly Pro is built on, and it's still early days. I'm building it the way I'd want it if I were freelancing myself: carefully, with real users, one improvement at a time.

Try Contractly Pro free →