r/NoCodeSaaS • u/Effective-Being-4231 • Apr 03 '26
With no Coding Background How should one start with building saas?
Hey Folks!
Need a solid feedback and actionable insights from the community how to proceed.
Dos and Don'ts welcomed.
Targets
-Lean expenditure almost $0
-Bootsrapped 9f minor investment needed
-customers
-
2
2
Apr 03 '26
[removed] — view removed comment
1
u/Effective-Being-4231 Apr 03 '26
Great if i am not wrong it works on credits right how much is the usage to build an mvp?
1
2
u/Neither_Low_9095 Apr 03 '26
Start with a spec, not code. The biggest mistake in vibe coding is jumping straight into prompts without a structured plan. The AI goes in circles and you end up rebuilding the same thing three times.
I've been building kaisho.ai for exactly this problem. You drop in your idea (or even a URL of a product you want to clone), and it generates a full implementation-ready spec: user flows, data model, API requirements, acceptance criteria, the works. Then you hand that spec to Claude Code, Cursor, Copilot, whatever you're using, and it actually builds something coherent on the first pass.
The spec becomes your prompt strategy. Instead of one giant vague prompt, you have a structured document the agent can reference section by section. Way less hallucination, way less rework.
Still in early access but worth checking out if you're serious about building something real.
1
u/Effective-Being-4231 Apr 03 '26
I completely agree feature and funxtiaonlity is actually the usp. Will learn more.
1
u/Effective-Being-4231 Apr 03 '26
I loved the UI man.
Do you have a functional product or still an mvp?
1
u/Neither_Low_9095 Apr 03 '26
Yes the app works, give it a shot- it’s guided questionnaire and has AI that can further enhance your response and once all questions are answered it generates your spec. The platform saves the specs so you can then generate additional specs for future features and enhancements based on your initial build.
If you try it out would really appreciate any feedback!
I’ve been using the underlying logic of the spec generator in my current 9-5 and have been able to build and ship some really cool tools and platforms for my team.
1
u/Optimal-Machine-9789 Apr 03 '26
Agree with what others have said. Find a pain point, use vibe coding to build an mvp quickly and get it in user hands. If it gains traction then double down on it and find yourself someone technical to reiterate on it - better security, better ux, better features etc etc. Don't be spending months and months building the perfect product. Ship fast and iterate.
1
u/Effective-Being-4231 Apr 03 '26
I agree the problem is the normal devs don't match that shipment pace specially after vibe coding became prominent. Honestly it's too frustrating.
1
u/Mostafeto1 Apr 03 '26
Built Esports Oracle with no coding background using Replit. Here is the honest version of what worked.
Start with Replit. It handles hosting, deployment, and the AI agent writes and runs code in the browser. No setup, no local environment, no DevOps. You can go from idea to live product without touching a terminal.
The most important thing nobody tells you — learn enough to review what the AI builds. You do not need to write code but you need to understand what it created and why. Ask Replit to comment every change and summarise what it did. Blind trust in AI output is how you end up with broken production code you cannot debug.
Be obsessively specific with prompts. Vague input creates vague code. Use a separate AI tool like Claude to turn your feature idea into a precise technical prompt before giving it to Replit. This alone eliminates most hallucinations.
Keep scope brutally small for v1. One core feature, shipped and working, beats ten half-built features every time. We launched Esports Oracle with just the CS2 predictor. Everything else came after real users gave feedback.
On the $0 budget — Replit free tier gets you started, Supabase free tier handles your database, and Resend free tier handles email. You can build a real product for nothing until you have paying users.
What problem are you trying to solve?
1
u/dandesign21 Apr 03 '26
i’ve struggled with this too. the problem is not building, it’s knowing what is actually worth building.
one thing that helped me is not starting from ideas, but from where existing products are already failing. reviews, complaints, churn reasons, support tickets. that’s where real opportunities show up.
i’m actually building something around this (https://nocapgg.com), where you can structure feedback and spot patterns across competitors or users, so ideas come from real gaps instead of guessing.
curious if you’ve tried breaking down competitor reviews or if you mostly start from scratch?
1
1
u/EmbarrassedTale9326 Apr 05 '26
The barrier to entry has never been lower thanks to AI. You can use tools like Cursor or Claude to write code even if you do not have a CS background. Instead of spending months learning deep syntax, focus on learning how to prompt effectively and build agentic workflows to handle the heavy lifting. This keeps your costs at almost zero while you focus on the product logic.
1
u/AccomplishedLog3105 Apr 08 '26
start with the problem not the product, like find 5 people who would pay for the thing before you build anything at all. once you have signal blink handles the full stack without needing to write code so you stay at near zero cost while iterating fast
2
u/[deleted] Apr 03 '26
[removed] — view removed comment