Ecommet
·

From Solo Developer to SaaS Founder: The New Age of Software Entrepreneurship

From Solo Developer to SaaS Founder: The New Age of Software Entrepreneurship

You’ve probably seen one at a fair or on a busy street corner. A big drum strapped to his back, a harmonica clipped near his mouth, a guitar in his hands and cymbals tied to his knees. One person, making the noise of a whole band.

It’s impressive. It’s also slightly exhausting to watch. And it raises a fair question: can one person really be the whole orchestra?

That’s the question I keep asking about software. My hunch is that AI coding assistants, automation tools and cloud platforms now let a single developer build and run a software business that used to need a whole team. That’s my view, not a proven trend.

Building it is the easy part now. Maybe.

The rise of the solo founder: one laptop, one person, one big question

Let’s start with the word you’ll see everywhere. SaaS (short for “software as a service”) is software you rent online, usually with a monthly subscription, instead of buying it once in a box. Think of how you pay for a music app or cloud storage every month. That’s SaaS.

So here’s the big question: can one developer now build a profitable SaaS product on their own, and what still gets in the way?

I’ll be upfront. Nobody has handed me a neat chart that answers this. I don’t have numbers on how many one-person software businesses exist or how many make money. This post is me thinking out loud, with you.

Before and now, roughly

Building software used to be a team sport. You needed people who could write code, people who could design screens, someone to look after the servers, someone to handle billing, someone to sell it and someone to answer customer emails. Even a small product touched a lot of different skills.

Now, many of those jobs have a tool attached. AI can help write code, cloud platforms handle a lot of the server work, and payment services handle the money. The skills haven’t vanished. They’ve just become easier for one person to borrow.

Here’s how I see the split. This is my view, not a survey:

JobTraditional teamAI-powered solo founder
Writing codeDevelopersYou, plus an AI coding assistant
DesignA designerYou, plus templates and AI help
ServersAn operations personA cloud platform does the heavy lifting
BillingA finance or billing setupA payment service
MarketingA marketing teamYou. Mostly just you.
Customer supportA support teamYou, plus some automation

Notice the last two rows. Tools can cover a lot of the building. They cover much less of the selling and helping. Keep that in mind; it comes back later.

Meet the toolbox: what a one-person stack might look like

A tech stack is simply the set of tools you use to build and run an app, like the set of pots, pans and burners in a kitchen. Here’s one possible stack for a solo developer. It’s a reasonable starting point, not an official recommendation backed by data.

  • Claude Code: an AI coding assistant, a tool you describe what you want to in plain words, and it helps write the code. Think of a very fast typist who knows a lot of programming.
  • Cursor: a place to write code with AI built in. If code is a document, this is the word processor, with an assistant sitting beside you.
  • Next.js: a framework, which is a ready-made skeleton for building websites and web apps, so you don’t start from an empty plot of land.
  • Supabase: a ready-made storeroom for your app’s data, built around a database (an organised filing cabinet for things like user accounts and orders).
  • AWS: a cloud platform, meaning you rent computing power over the internet instead of buying and running your own machines.
  • Stripe or Razorpay: the cash counter. These handle taking payments from customers. If your customers are in India and paying in ₹, Razorpay is the familiar local option.
  • Automation tools: little helpers that run repetitive chores for you, like sending an email whenever something happens.

There’s also a whole family of no-code tools, which let you build apps by dragging and dropping blocks instead of writing code. They’re worth knowing about if you don’t code at all.

What does all this cost?

Honest answer: it depends. Prices change, plans change, and most of these tools charge based on how much you use them. A tiny side project and a busy app can have very different bills.

I’m not going to throw made-up numbers at you. If you want to know what my own setup looks like, DM me and I’ll walk you through it.

What can one person actually build?

Quite a lot, in theory. Here are the main categories, each with a made-up example so you can picture it. These are illustrations, not real products.

  • SaaS platforms. Say, a booking tool for a local yoga studio, where students pick a class and pay online every month.
  • Mobile apps. Say, a simple app that reminds a family to water their plants and logs who actually did it.
  • AI tools. Say, a helper that turns a shopkeeper’s handwritten notes into a tidy product list.
  • Developer utilities. Small tools that save other programmers time, like a checker that spots a common mistake before it goes live.
  • Niche products. Software for one very specific group, say, tuition teachers managing fee reminders. Small market, but a problem people really feel.

The common thread? Small, focused and solving one clear problem. A one-person band plays a tight set, not a full symphony.

Building a product vs building a business

Here’s the heart of it. An app with no customers is a very nice hobby.

Think of it like food. Cooking one brilliant dish is a skill. Running a restaurant is a completely different job: you need people to find you, you need prices that make sense, you need to handle complaints, and you need diners to come back next week.

Software works the same way. Once the app is built, five other jobs show up:

  • Marketing: telling people your product exists and why they should care.
  • Customer acquisition: turning strangers into paying users. Marketing gets attention; acquisition gets sign-ups.
  • Pricing: deciding what to charge. Too high and nobody tries it. Too low and you can’t keep the lights on.
  • Support: answering questions, fixing problems, replying to that email at 11 pm.
  • Retention: keeping customers subscribed month after month, because a subscription that gets cancelled in month two isn’t much of a business.

My opinion: AI probably helps most with the coding part. I haven’t seen solid evidence on how much it speeds things up, so treat that as a hunch. But even on the most generous guess, no AI is going to make strangers trust your product for you.

That’s the second job. It’s still the hard one.

Should you worry? The not-so-glamorous side of going solo

Not worry, but plan. Going solo has real risks, and none of them are reasons to quit. They’re reasons to go in with your eyes open.

Security: you’re the only guard at the gate

In a team, someone usually owns security. When you’re alone, that someone is you. If you skip a basic safety check because you’re busy, there’s nobody behind you to catch it. And your customers are trusting you with their data.

Maintenance and technical debt

Software isn’t “done” once it launches. Tools update, things break and users find bugs you never imagined.

Then there’s technical debt: shortcuts you take today that you pay interest on later. A quick fix saves an evening now, but every future change has to work around it. Pile up enough of them and the app becomes painful to touch.

Competition

If tools make it easier for you to build something, they make it easier for everyone else too. A good idea might attract copycats faster than before. Your edge is less “I can build it” and more “I understand these customers better than anyone”.

Burnout

This is the one people underestimate. When you’re the developer, the marketer, the support desk and the accountant, the work never really stops. The one-person band can play a great set, but nobody can play all day, every day.

What does the future look like?

Here’s the open question: will we see far more solo founders, or will companies simply keep their engineering teams but make them smaller?

Nobody I can point you to has a definitive answer, so this is pure speculation on my part. My guess is a bit of both. Some people will build small, focused products entirely alone. Others will join small teams where each person does the work of several. The one-person band and the small ensemble can both fill a room.

What I’m fairly confident about is the shape of the problem. Tools keep making the building cheaper and faster. The business side (finding customers, earning their trust, keeping them happy) still needs a human who understands people.

So, if you had to build a SaaS alone today, what would you create? Tell me in my DMs, and follow @itsecommet. I’ll be in the crowd, clapping for your one-person band.

Have a project in mind?

Tell me what you need, even in a few lines, and I’ll come back with questions or a quote.