I’ve been chasing the dream of building a successful SaaS as a solo founder for years now. To be honest, I haven’t made a single sale yet.
But I haven’t given up either. That counts for something, right?
Where It Started
When I first got into this, I had to teach myself how to code. That alone took a while, but I eventually got good enough to build things. So I did what a lot of us do—I jumped right into building a SaaS product.
Auth? Check. Multi-tenancy? Check. Stripe integration? Check.
I launched it... and nothing happened.
No users. No traction. Just crickets.
That’s when I learned the hard truth: you can’t just build in the dark and expect people to show up. I had zero audience, no feedback loop, and no real clue about marketing or sales.
Learning to Share
Earlier this year, I decided to change that. I started a YouTube channel focused on something I know well and use daily: E2E testing with Rails and Cypress.
That got a bit of traction, and from the feedback I received, I decided to broaden the niche from just Cypress to E2E testing in general, especially for Rails developers. (There’s definitely a gap there.)
I’ve really started to enjoy creating content, and I plan to keep going. But deep down, I still want to build a SaaS.
The New SaaS Idea
Lately, I’ve been exploring all kinds of ideas in the E2E testing and DevOps space. The one I’m most excited about right now is this:
A SaaS platform that automatically optimizes E2E test parallelization in CI to cut test runtime by 30–75%.
The problem:
Manually distributing E2E tests across CI nodes is inefficient, and test suites grow over time, making things worse.
The solution:
My idea is to analyze test duration, memory/CPU usage, and group tests intelligently, optimizing how they run across CI workers. It would integrate with GitHub Actions, GitLab CI, or Jenkins, and continuously adapt as your test suite evolves.
Basically: set it and forget it, and your CI gets faster over time.
Interested? I’m collecting early feedback and signups here: https://wonderful-souffle-fcd787.netlify.app/
Why I’m Sharing This
I know I still have a long way to go, but I want to build this in the open, not in isolation like before. So if this idea sounds interesting to you—or if you’ve struggled with long test times in CI—I’d love your thoughts.
- Would you use something like this?
- What features would make it a no-brainer?
- Are there tools you currently use that already solve this for you?
Thanks for reading—and if you're building your own thing too, keep going. We’ll get there.
Top comments (0)