Building a $10k/mo B2B SaaS boilerplate for multi-tenant
apps
After getting a taste for enterprise development, Alexandro Martinez took his learnings and built SaaSRock, a React Router B2B SaaS boilerplate focused on multi-tenant solutions. It's currently bringing in an average of $10k/mo, and that isn't including his other projects and freelance revenue.
Here's Alexandro on how he's doing it. 👇
Flexibility baked in
I'm a full-stack SaaS founder and developer based in Guadalajara, Mexico.
A big part of the reason I became a founder was seeing my dad’s lifestyle. He’s a software developer too, and while he never pushed me into the field, I always admired how he had control over his own time. He could work from home, be there for the family, and not be tied down to a rigid 9-to-5 office routine. If he needed to travel for work, he could fly out and back the same day.
That kind of flexibility really inspired me. I wanted that same freedom.
My career started 12 years ago when I migrated his Enterprise Resource Planning system from older tech (Informix 4GL, terminal-based) to a more modern stack (.NET Windows Forms). That project taught me a lot about building enterprise modules — invoicing, accounting, inventory management, etc. — and it remains a stable part of my income.
Currently, I focus mainly on SaasRock, my React Router B2B SaaS boilerplate that helps devs build multi-tenant apps. All my new custom development projects are built on top of SaasRock. This paid boilerplate has reached around 1,500 users, and it has averaged $10k+ per month for the past 3.5 years.
Since building that, I also experimented with launching RockStack, a Next.js and SvelteKit version of the boilerplate, aiming for a bigger market. But with just 120 sales, it didn’t gain the same traction, so I happily went back to React Router.
Building a boilerplate
Building the initial version of SaasRock was all about channeling what I learned from creating an ERP into a flexible SaaS boilerplate. Early on, I realized that in enterprise software, a huge part of the core structure revolves around:
Managing users with their corresponding granular permissions
Separating admin
Account/tenant dashboards
Handling subscription billing (recurring, one-time, or usage-based)
And designing it to be production-ready out of the box for a SaaS environment
My main tech stack is centered around React/TypeScript:
React Router v7 (formerly known as Remix v1 and v2): The best full-stack web framework for me.
Tailwind CSS: Granular control over the design while keeping everything consistent and easy to customize.
shadcn/ui: One of the design system foundation standards nowadays.
Prisma: Mainly paired with Postgres, but sometimes with SQL Server for clients married with Microsoft/Azure, or SQLite for quick MVPs.
Deployment: I usually deploy on Fly.io, but sometimes I use Vercel, DigitalOcean, or even dedicated servers with a static IP for certain clients. My go-to databases are typically Postgres, either self-hosted or on AWS Lightsail or Supabase when I need a managed solution.
Environment: I code on a 16" MacBook Pro + Cursor (Oscura theme) + Claude Code CLI (Max plan).
The timing was perfect. The year I started was the year Tailwind CSS really took off. I’d never been fully convinced by Bootstrap or Material UI for my own design style, but Tailwind really clicked for me. It made me excited about building user interfaces.
I still have nightmares about building Windows Forms on Visual Studio. You can read more about my Windows Forms to web transition here.
Spec-driven development + Claude Code
One major improvement in my workflow this year has been using Claude Code combined with a Spec-Driven Development approach. Here’s the process I follow:
Project context: Explain your project structure through a directory of .md files.
Feature Building: Ask Claude to plan the feature and document the PRD in a new .md file, e.g., FEATURE_CALENDARS.md.
Accept or Reject changes: Test the feature. If it works, stage your changes with Git; if not, undo and iterate.
Update documentation: Ask Claude to update the PRD with
[x]checkmarks for completed items, and project context files if applicable.
I repeat steps 1–4 for every feature, keeping everything documented in an LLM-friendly way while accelerating development and maintaining clarity.
A hybrid model
SaasRock uses a one-time license pricing model:
MVP edition $249: Most affordable, polished, and stripped-down edition.
Core edition $499: Adds more features like the form builder.
Pro edition $1,999: Includes advanced tools like the widgets project.
I also offer custom SaaS development via MVP-as-a-Service:
Packages range from $6k for quick setups to $48k for full 3-month builds.
Most clients fall into the $10k–$16k per month range.
This combination of product licenses and custom development drives steady, sustainable revenue growth.
A mix of content, value, and reputation
I’ve used a mix of strategies over the years:
SEO: Early on, I invested heavily in creating content, writing detailed blog posts after every release, maintaining a public changelog, and an actively updated public roadmap. Even though I eventually stopped, the effort still pays off: SaasRock gets about 30k impressions per month on Google Search.
YouTube: I launched a channel and uploaded around 45 videos covering SaaS development, tutorials, and behind-the-scenes content. I haven’t posted in about seven months, but people still reach out after discovering my videos.
GitHub: I’ve created and shared several open-source repositories around Remix/React Router. These projects provide some value and put my name out there.
Word of mouth: A significant portion of my custom development clients comes from referrals and recommendations by existing customers, complemented by my MVP-as-a-service page where I list my SaaS development services.
X: I used to tweet actively but stopped because I didn’t want to sound like a “snake oil salesman” selling the SaaS dream.
I think this mix of content, open-source value, and personal reputation has been the foundation of SaasRock’s steady growth.
Salient advice
Here's my advice
Be resilient and patient: The indie hacker dream often looks like you build a side project, launch it, and instantly make MRR or hit a big exit. In reality, you need to put in a lot of hours, or be pretty effective with them. Prepare yourself for a long game. And remember that it’s much easier to stay motivated when you care about the problem you’re solving.
Keep failing until something sticks: It sounds cheesy, but persistence wins. Every “failure” is progress toward the thing that finally clicks.
Let go: I still have “alive dead projects,” quietly paying $10 a month for domain/database/hosting just because I don’t want to shut them down, even if nobody uses them. It's the eternal promise of "I'll improve/rebrand/re-launch it when I have the time."
Don’t over-engineer: Often, I find myself building abstractions nobody asked for. It’s something I keep working on, trying to simplify and focus on what’s actually needed. Build MVPs as if you're in a hackathon. Build a reusable workflow that works.
Avoid Meetings if possible (but meet to build trust): In my case, when working with clients, a short Loom video is more effective than a meeting: feedback, feature delivery, and questions. With that said, when you're starting out, seeing your face helps the relationship start.
Watch out for burnout: For me, it often happens when my expectations grow faster than my results, even when those results are actually great.
What's next?
From here, I plan to:
Maintain SaasRock (low income, long-term): Keep improving my boilerplate, focusing on B2B multi-tenant solutions.
Grow my Agency (high income, short-term): Grow my custom development agency to manage up to five clients per month. Once I reach that point, I would consider hiring a developer to help me.
Build a successful SaaS (high income, long-term): I would love to launch a SaaS product that takes off!
I’m not actively writing blog posts, tweeting, or making videos anymore, but you can join my Discord server to start a public discussion or DM me directly. And check out SaaSRock!
Leave a Comment
I agree with the comment from below. Sharing your wins and losses encourages me to keep trying when something doesn't work.
Really appreciate how you shared both the wins and the misses. The part about experimenting with RockStack but returning to React Router hit home, reminds me that sticking to what you know well can often be more powerful than chasing the bigger market. Thanks for putting this out there, super insightful!
For someone looking for a free and open source alternative in Next.js, Next.js Boilerplate
With everything you need to build your multi tenant apps
Awesome stuff!
nice
This is so insightful. Keep up the great work!
Really appreciate you being transparent with the numbers... makes the journey feel more real. Curious, what was the hardest lever to actually move the needle on growth?
awesome!
This really resonates, Alejandro! The boilerplate -> custom dev -> SaaS progression makes total sense. I'm on a similar path - built UI components (Unframe) and now running a B2B2C SaaS (Habitloop).
Your spec-driven development with Claude Code is smart. I use Cursor + MCPs for similar workflows - the documentation-first approach keeps things scalable when you're solo.
The "alive dead projects" comment hit home 😅. I've got domains quietly running that I keep promising to revive "when I have time."
Question: How do you handle client scope creep in your $10k-16k monthly packages? That price range seems like the sweet spot, but managing expectations at that level can be tricky.
Congrats on the 3.5 years of consistent $10k+ months - that's real sustainability.
This is genuinely inspiring! It's amazing to see how you translated your enterprise development experience into a focused, valuable product like SaaSRock. And the emphasis on flexibility as the core motivator really resonates. $10k/mo from a boilerplate is serious validation of the quality and need for what you've built. Wishing you the best as you grow the agency and launch your own successful SaaS!
Real Nice, I am also building something, but I am at very initial stage, would love to have you guys by my side in this journey.
Successful Recovery of Stolen Bitcoin Funds-APEX INTERVENTION LTD
I experienced a devastating loss when my entire life savings — approximately $213,811 in Bitcoin (BTC) — were stolen in a cryptocurrency scam. Initially, I was informed by several sources that recovery was impossible, and I had nearly given up hope.
Fortunately, I came across an article referencing APEX INTERVENTION LTD, a reputable recovery specialist known for assisting victims of scams and fraudulent transactions. Despite my initial skepticism, I decided to reach out and engage their services.
To my astonishment, they successfully recovered the full amount that had been taken from me. I am sharing this information in the hope that it may assist others who have experienced similar financial losses.
A $10k/mo B2B SaaS boilerplate requires scalable architecture, streamlined onboarding, strong security, and flexible integrations to ensure businesses save time, reduce costs, and grow quickly.
Really inspiring journey, Alexandro! I love how you combined your enterprise experience with a practical boilerplate approach. The mix of SaaS licenses and MVP-as-a-service is a smart way to build sustainable revenue. As a fellow SaaS founder (building Zamdit, an ATS for startups), I completely agree on keeping things simple and avoiding over-engineering, it’s easy to get lost in abstractions when building reusable workflows.
B2B SaaS boilerplates require scalable architecture, secure billing, and user-focused features to ensure consistent growth, customer retention, and predictable recurring revenue.
Superb
You're really good at identifying user needs! Do you think users prefer AI coding tools or template products? I'm working on an AI coding tool (autocoder) that generates both the front-end and back-end, but the front-end generation isn't quite up to par yet, and the back-end generation also has some issues. I feel like AI is more flexible, but templates offer more control.
Building a $10k/month B2B SaaS boilerplate for multi-tenant apps starts with a scalable architecture, reusable code, and robust security. Focus on tenant isolation, flexible billing, and modular features to accelerate development. Integrate analytics, user management, and API capabilities from the start. With a well-designed boilerplate, developers can rapidly launch multi-tenant SaaS products, reduce time-to-market, and create a solid foundation for generating consistent recurring revenue.
That's impressive - hitting $10k MRR with a B2B SaaS boilerplate sounds a solid niche. I just launched my first SaaS too (OptiGain a profit optimization tool), though I'm still early figuring out how to grow . Curious - what have been your main channels for finding those early B2B customers?
Really inspiring to see how you’re building a $10k/mo SaaS boilerplate 👏. The whole multi-tenant setup is something I’ve been curious about, especially in terms of scalability.
On a smaller scale, I recently built a micro-SaaS tool (a free UAE gratuity calculator) to help employees quickly figure out their end-of-service benefits. It’s nowhere near a boilerplate-level project, but the process of getting real users to test it has been eye-opening.
Curious — in your experience, do you think even niche, single-feature tools (like calculators or checkers) can benefit from a multi-tenant structure, or is that overkill until they scale?
hmm pretty good writing skills you got man
In James Fleischmann's guide, he outlines how to build a $10k/month multi-tenant SaaS boilerplate, covering architecture, scalability, and best practices for quickly launching and monetizing SaaS products.
Super cool niche, shipping a multi-tenant B2B boilerplate that handles the unsexy parts (auth, RBAC, billing, tenant isolation, audit logs) lets founders spend week one on their actual product. The opinionated defaults + docs are the moat here.
Two things I’d double-down on next:
“SOC-2-friendly by default”: logs, SSO/SAML, backups, data residency knobs.
Upgrade path: codemods + migration guides when frameworks change, so teams don’t fear lock-in.
Curious: what’s the single activation that best predicts a paid team — first tenant created, first role-permission matrix shipped, or metered billing live? And which channel is bringing paying users right now; marketplace/search, founder showcases, or SEO for “multi-tenant boilerplate”?
P.S. I’m with Buzz; we build conversion-focused Webflow sites and pragmatic SEO for dev tools and SaaS launches. Happy to share a tight 10-point launch-page checklist if useful.
great work!
very inspiring post
Very interesting post, I like how you recognised your initial idea wasn't working and segued to something else. "Keep failing until something sticks" really resonated with me, best of luck
Great work!
It really motivates me seeing people achieve something that I thought wouldn't be possible. But the only thing I have trouble choosing is the pricing part. How do you come up with the pricing for your features? A ratio on profit/cost ?
Truely inspiring and really thoughtful journey I must say
keep up the good work
Great work, Alexandro! SaaSRock's success shows the power of solving real problems with a focused, flexible boilerplate. Love the spec-driven approach with Claude Code—smart way to streamline development. Keep it up!
Really impressive work! SaaSRock not only streamlines multi-tenant SaaS development but also shows how thoughtful tooling and workflow choices can save countless hours for developers...an approach more founders should consider.
Interesting read, and very relatable, my key takeaway is the ability to let go. I still have a bunch of projects I have not come to terms with letting go, somewhere in my mind I believe I would make out time to come back and work on them.
Thanks
I particularly appreciate how he adopted a standards-driven approach in development and combined it with Claude Code to enhance efficiency. This approach is worth learning from.
Really inspiring journey! I like how you turned enterprise lessons into a boilerplate that not only saves devs time but also powers your own projects. The hybrid model (product licenses + custom dev) is super smart — steady recurring income with bigger one-off deals to smooth things out.
The advice about persistence and not over-engineering hits home too. It’s easy to get stuck polishing instead of shipping. Thanks for sharing so openly — lots of takeaways here for anyone trying to build sustainable SaaS.
The part about your dad really hit me it’s cool how you took that inspiration and built something so practical and profitable mixing boilerplate sales with custom work feels like a clever balance I don’t see often
Really inspiring to see how Alexandro turned his enterprise experience into SaaSRock. The way he focused on flexibility and reusability really stood out to me.
I’m working on something in a totally different space — content instead of SaaS — but with a similar mindset. Most birthday wish sites felt repetitive, so I started birthdaywishfriends .com to make messages more personal and unique.
Of course, it’s a much smaller project, but the lesson feels the same: spot the gap, create value, and grow step by step.
Really inspiring read! I like how you’ve combined product licensing with custom SaaS services—it’s a smart way to diversify revenue while keeping cash flow steady. Your approach with spec-driven development and Claude Code is also a great reminder of how documentation and process can speed things up. Curious—what’s been your biggest challenge in balancing product updates with client work?
Really impressive execution on turning enterprise experience into a profitable boilerplate! Your spec-driven development approach with Claude is fascinating - treating PRDs as living documentation seems like a brilliant way to maintain clarity while leveraging AI effectively. The tiered pricing model (MVP $249 → Core $499 → Pro $1,999) paired with custom development services creates excellent revenue diversification. Your point about patience resonates - 3.5 years of consistent $10k/mo shows the power of sticking with what works rather than chasing the next shiny framework. Thanks for sharing the honest insights about 'alive dead projects' - we all have those!
Turning ERP scars into a developer boilerplate is a great example of packaging hard-won primitives (auth, perms, tenants, billing) instead of chasing a shiny app. The stack choices read like speed multipliers, but the real unlock is the spec-driven loop with an LLM—docs as the interface for the code, not just an afterthought.
Big takeaways I’m stealing: price models to match reality (one-time license plus “build it for me” ladder), let evergreen assets compound (SEO, YouTube, open repos) even when you stop posting, and guardrail yourself against over-engineering with a “hackathon by default” rule. Also appreciated the honesty on “alive dead projects” and burnout...expectations racing ahead of results is the trap. Simple playbook for other founders: productize your reusable primitives, document first, ship small, sell time boxes, and keep the meetings to Looms unless trust requires face time.
This is such valuable insight into building a sustainable SaaS business! Your approach to spec-driven development with Claude is particularly interesting - documenting features as PRDs before development seems like a game-changer for maintaining clarity while accelerating development. The hybrid model of boilerplate sales + custom development is brilliant - it creates multiple revenue streams while the boilerplate work feeds into your agency projects. Really appreciate you sharing the specific tech stack and pricing tiers too. The advice about being patient for the long game resonates deeply - it's easy to get caught up in the overnight success stories but real SaaS growth takes time and persistence.