That title is deliberately dramatic but is it wrong?

I m a scientist who codes as a hobby. In a few weeks, with AI, I ve built more usable web tools than I once imagined creating in years.

And I m not special. Thousands of new websites, calculators, apps and micro-SaaS products now appear for every imaginable problem.

If anyone can turn an idea into software before lunch, building is no longer the barrier. Soon, why maintain old software when an agent can simply rebuild it?

Was updating some backend code straightforward find-and-replace, target text, swap it in, print success. Ran it. Got "PATCHED." Checked the file to confirm the change landed.

Nothing had changed.

I added mine up this month and the total was higher than I'd have guessed. Claude Max, ChatGPT Pro, xAI, and GitHub Copilot which I added recently.

Two of those are top tier plans, which is where most of the damage is. The honest part is that I don't open all of them in a given week. A couple I keep because they're each better at different things, one because it sits in my editor and I forget it's there, and the rest because cancelling feels like a decision I'd only have to make again in two months.

What gets me is that this is only half the bill. Every AI SaaS app I sign up for has to price in its own inference cost, so I end up paying a second time, through their subscription, for models I already pay for directly. The startup can't really avoid it either. They either eat the margin or charge me extra to cover it, and I don't think either side is happy with that.

So what's your number? How many do you actually open in a normal week? And has anyone cancelled one and genuinely not missed it?

Launching on the 10th of Aug. and doing the last round of prep.

I've read plenty of "how to launch" advice, but most of it is written by people selling launch services. I'd rather hear from makers who've actually been through it.

Two specific questions:

1. What did you spend time on before launch day that you'd skip if you did it again?

I won 3rd place in Google and Kaggle AI Agents global Capstone competition. I wanted to share this here in case anyone is interested in discussing the topics learnt there and to further improve my skills. I joined this competition to learn and winning was an amazing bonus.
Here are a few lessons I learned from this experience:
1. Clear guidance matters more than powerful AI
AI can do a lot of the work, but the quality of the outcome depends on how clearly we guide it. The model may generate the output, but humans still need to define the problem, context, constraints, and expected behavior.
2. Fast building still needs strong architecture
There are many ways to execute and build a project. The sustainable path requires a strong structure and architecture from the beginning. Moving fast without structure often creates more rework later.
3. Trust your users before trusting AI
AI can help analyze a problem, but real user behavior tells you whether the problem is worth solving. The strongest products begin with genuine user pain, not an interesting technology looking for a use case.
4. Vibe coding is changing product development
Vibe coding is changing how product development and software development lifecycles work. The real advantage comes from combining rapid AI-assisted development with spec-driven and behavior-driven methodologies.
5. Better structure means fewer tokens and fewer hallucinations
A well-designed project structure helps AI understand what to build, how to build it, and which constraints to follow. This reduces unnecessary context, token usage, hallucinations, and repeated work.
6. Building with AI changes the role of the builder
Building with AI is becoming less about writing every line of code and more about defining the problem, designing the system, setting boundaries, testing behavior, and evaluating outcomes.
There is a lot more advanced topics I learned about agent architecture, MCP, skills, security, evaluations, observability, and building with AI. Feel free to reach out if anyone would like to discuss this.

I tried searching, so if I'm way off...please don't hesitate to delete or move or tell me what I screwed up. Considering doing a launch here soon and was wondering if there's a forum/intro or some other means of getting some feedback or some sort of litmus test before launching? Thanks!

HI voted for a product - it increased by 1 .. then a few hours later it was back to the original number then we when I tried voting again it went down ??? what am I missing?

A funding announcement can make a company look successful, but it does not prove that customers want the product or that the business can sustain itself.

The more durable signal is often simpler: you ship something useful, generate revenue, and use the profit from product one to fund product two. Each product becomes evidence that the next one can exist without another raise.