I used to assume that building a SaaS product meant finding a developer before I could make meaningful progress. I pictured technical specifications, lengthy discussions, and a budget that would grow every time I changed my mind. AI app builders have changed how people can approach the earliest stages of that process. With Greta.sh, for example, you can explore a product idea by creating a working prototype from a natural-language description. That gives you something concrete to review before deciding how much engineering the project needs. Cursor and Claude can also help with code-related tasks when you're ready to work more directly with implementation. But a prototype and a production-ready SaaS application aren't the same thing. Authentication, permissions, database design, payments, testing, and deployment all require careful attention. The advantage is that you may be able to validate the idea and clarify requirements before committing to a larger development effort. If you're a founder exploring how to build a SaaS product with AI, begin with the smallest useful workflow. Test whether people understand it, whether it addresses a real problem, and whether they would use it. You don't necessarily need to build the entire business on day one. You need enough evidence to decide what deserves to be built next.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)