What 5 makers on MakerMap learned about it, in their own words: their best posts on X, filed under Building & shipping.
I used Claude to write the first version of Kiiwi's sound engine. Not proud, not ashamed. It got me a working prototype in a weekend instead of a month.
The UI, the pricing, the launch, all me. AI just closed the gap between idea and something I could actually test.
SaaS is not a new idea.
The first ones were called ASPs in the late 1990s. Mostly web apps sold to big companies.
What changed for me as a solo founder is simple:
- one copy of the app serves every customer
- nothing to install on their side
- I ship a fix once and everyone has it in minutes
That last point is the one I value most. No version 2.3 that half of users never download.
I'm building Rawnd and Loudship this way, alone.
When you run a SaaS, what takes the most of your time: support, billing, or shipping updates? I'd like to know how other solo founders split their week.
Honest take: if you’re still hand-typing every boilerplate function, you’re moving at the speed of a typewriter in a smartphone world.
I haven’t manually written a standard loop or fought a linter for almost a year now (and it used to be my hobby).
My workflow now is prompt, iterate, and ship. While teams spend half a sprint in refinement meetings debating Clean Architecture abstractions, I’m putting working full-stack features into production in days.
That doesn’t mean fundamentals don't matter, but obsessing over textbook design patterns often just makes teams slow.
At the end of the day, users and stakeholders don’t buy your test suite, they buy speed, execution, and outcomes.
Doing a quick AMA today for devs trying to adapt their workflow to modern AI tooling without losing their minds.
Drop your questions below.
#builtInPublic #solopreneur
Stop overcomplicating deploys for a solo Micro-SaaS.
I don't need Kubernetes. I need:
one Hetzner box
Docker Compose
a reverse proxy
backups that actually restore
Ship → restart container → check logs.
That's the whole release train.
What's your boring deploy stack right now?
I built a bidkaro without writing everything from scratch.
Here's the stack:
→ Grok — building + debugging
→ GitHub — code
→ Vercel — deployment
→ Supabase — database
→ Razorpay — payments
→ Datfast — analytics
idea → code → payments → database → analytics → live
with a laptop and a bunch of AI-powered tools.
We're living through a pretty weird time to be a solo builder.