+- noahrevoy -- 2mo ----------------------------------------------------------------------------------------------[...]+ | | | I built an entire SaaS product that is roughly comparable to Kajabi in less than a week using Claude Code in the | | terminal. | | | | It includes features Kajabi does not have that I specifically need, and it omits features Kajabi has that I do not. | | | | I finished it, ran it locally, and while reviewing it, realized I wanted a few additional features. I described them | | to Claude. Claude thought about it, proposed an implementation, I agreed, and it built the features. Fifteen minutes | | later, I was testing them. | | | | If I ask a traditional SaaS company for a feature I need, the odds of it being implemented are close to zero. The | | odds of it being implemented on a timeline that matters to me are effectively zero. In that model, my product has to | | adapt to the platform. Here, the platform adapts to my product. | | | | I do not know whether every reader could get the same results. I am not a programmer either. But I am very good at | | describing exactly what I want, and just as importantly, what I do not want. | | | | In this case, I gave Claude a governing document describing the business logic, followed by a nine step development | | plan. Each step was several pages long, and Claude was instructed to work through them one step at a time. | | | | If you can clearly describe what you want, how it will be used, and how your business logic works, this approach can | | produce extraordinary results. If you go to Claude and say, “Make me a website,” it will make you something. It will | | probably look good. But it will not necessarily be what you want. | | | | This method only works if you are good at thinking clearly and describing your intent precisely. | | | +-- reply --------------------------------------------------------------------------------------------------------- ---+I built an entire SaaS product that is roughly comparable to Kajabi in less than a week using Claude Code in the terminal. It includes features Kajabi does not have that I specifically need, and it omits features Kajabi has that I do not. I finished it, ran it locally, and while reviewing it, realized I wanted a few additional features. I described them to Claude. Claude thought about it, proposed an implementation, I agreed, and it built the features. Fifteen minutes later, I was testing them. If I ask a traditional SaaS company for a feature I need, the odds of it being implemented are close to zero. The odds of it being implemented on a timeline that matters to me are effectively zero. In that model, my product has to adapt to the platform. Here, the platform adapts to my product. I do not know whether every reader could get the same results. I am not a programmer either. But I am very good at describing exactly what I want, and just as importantly, what I do not want. In this case, I gave Claude a governing document describing the business logic, followed by a nine step development plan. Each step was several pages long, and Claude was instructed to work through them one step at a time. If you can clearly describe what you want, how it will be used, and how your business logic works, this approach can produce extraordinary results. If you go to Claude and say, “Make me a website,” it will make you something. It will probably look good. But it will not necessarily be what you want. This method only works if you are good at thinking clearly and describing your intent precisely.
thread · root 17a5b1cc…532a · depth 1 · · selected 17a5b1cc…532a
thread
root 17a5b1cc…532a · depth 1 · · selected 17a5b1cc…532a
I built an entire SaaS product that is roughly comparable to Kajabi in less than a week using Claude Code in theterminal.It includes features Kajabi does not have that I specifically need, and it omits features Kajabi has that I donot.I finished it, ran it locally, and while reviewing it, realized I wanted a few additional features. I describedthem to Claude. Claude thought about it, proposed an implementation, I agreed, and it built the features.Fifteen minutes later, I was testing them.If I ask a traditional SaaS company for a feature I need, the odds of it being implemented are close to zero.The odds of it being implemented on a timeline that matters to me are effectively zero. In that model, myproduct has to adapt to the platform. Here, the platform adapts to my product.I do not know whether every reader could get the same results. I am not a programmer either. But I am very goodat describing exactly what I want, and just as importantly, what I do not want.In this case, I gave Claude a governing document describing the business logic, followed by a nine stepdevelopment plan. Each step was several pages long, and Claude was instructed to work through them one step at atime.If you can clearly describe what you want, how it will be used, and how your business logic works, this approachcan produce extraordinary results. If you go to Claude and say, “Make me a website,” it will make you something.It will probably look good. But it will not necessarily be what you want.This method only works if you are good at thinking clearly and describing your intent precisely.
