I've been thinking about this a lot while building a product and trying to figure out customer acquisition.
For a long time, I thought getting customers was mostly about finding the right companies, identifying the right person, and reaching out to them.
But the more conversations I look at across places like Reddit, LinkedIn, X, Product hunt, Bluesky and different communities, the more I m starting to question that approach.
People constantly talk about problems they re having.
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 launched a consumer health app 3 days ago and I'm at ~100 users, all organic. I know that's a modest number, but it feels like a decent start for the first few days. I'm not planning to do paid acquisition if possible, I care more about building a community around the product than buying installs.
Anyone else feel like making short form content takes twice as long as it should? I spent three hours last night just trimming raw clips and fixing audio pacing. How are you all keeping your post-production workflow sane without spending all day in an editor?
I'm trying to become a strong end-to-end AI product engineer rather than just someone who can build LLM demos.
My goal is to be able to take an AI SaaS idea from zero MVP production paying users, largely as a solo developer, using agentic/multi-agent AI where it actually makes sense.
I'm currently comfortable with software development and have been working with LLMs, RAG, Semantic Kernel/agent workflows and Python, but I want to systematically fill the gaps required to build and operate a real product.
Over the past few months I brainstormed four different startup directions a real-world-asset tokenization platform for crypto holders, a DeFi trust/portfolio dashboard, an algo-trading agent, and a couple of narrower crypto tools (remittance, inheritance planning).
I ran each one through the same structured evaluation: business strategy, market sizing, financial logic, product scope, and risk, treated as separate lenses rather than one combined gut-check.