Today, I wanted to see how far an AI agent could go if I gave it a real business instead of a predefined automation. I entered binayah.com into Awish.ai. Binayah is a real estate company, and instead of telling Awish.ai exactly what workflow to build, I asked it to analyze the business first and find an automation opportunity. It suggested a customer acquisition funnel, which I reviewed and approved. Around 10 minutes later, the automation was ready. Step-by-step: 1. I entered binayah.com into Awish.ai. 2. Awish.ai agents analyzed the website and how the business operates. 3. Awish.ai identified customer acquisition as an area that could be automated. 4. It suggested a funnel designed to capture and qualify potential leads. 5. I reviewed the suggestion and approved it. 6. Awish.ai created the workflow and connected the required steps. 7. The funnel was ready to use in around 10 minutes. What I find most interesting is that I didn’t start by designing a workflow. The system first understood the business, found an opportunity, suggested what should be automated, and built it only after I approved. That feels much closer to having an automation consultant inside the product than using a traditional workflow builder.

I built Lumi, an HR assistant in French, with Claude Code in about two hours. It was an experiment: could Claude Code build a working product from a plain brief while being left completely alone? Employees ask questions, and Lumi answers using their company’s own HR documents. Each company has its own space, and HR can see which questions the documents couldn’t answer. Step-by-step: 1. I set up one window with Claude Code on one side and the files appearing on the other. I didn’t write code, but I could always see what was being built. 2. I described the product in plain language. I dictated my brief out loud, typos included: who pays, who uses it, the problem, a demo client, keeping clients separate, the admin view, the language, and the price. 3. I let Claude Code build the product and make every call. Thirty-four minutes later, the first version had 47 files and 3,949 lines. It even invented a fictional client company with a full HR handbook so I could demo it immediately. 4. I put the product online. Claude Code wrote a setup guide for Supabase and Vercel. I followed it one step at a time and sent a screenshot whenever something broke. 5. I improved it with feedback. I told Claude Code that the design looked like it had been created by a junior designer. Eighteen minutes later, it came back with a name, a design system, pricing plans, and everything in French. 6. I checked security, although I had skipped this during the build. When I asked for a full security review eleven weeks later, it took less than six minutes and found three serious problems, including a database function that allowed anyone to read a company’s documents. Claude Code fixed all three. Run `/security-review` before sharing the link and before each new change. The full write-up, including the unedited prompts: https://www.theaithinker.com/p/how-to-build-a-saas-product-with