Having sat on both sides of the table, here are the 3 biggest unforced errors I see, looking at it as both an investor and now a founder:

1. The market size does not hold.
Many founders use a top-down approach with questionable data sources to claim a massive TAM. In my opinion, a much more credible and defensible approach is to build your market size from the bottom-up.

2. Trying to do too many things.
In the early stages, you can only focus on a few areas, starting with your beachhead market. It is incredibly difficult to juggle product development, consulting, and training revenue simultaneously and still hope the business will scale. Even with AI efficiencies, stretching the team too thin kills momentum.

3. Not thinking deeply enough about the Moat and GTM.
A great product does not automatically equal a great business. If you haven't thoroughly thought through your Go-To-Market strategy and why your business is defensible against competitors, the pitch falls flat.

Do you have any habits or hobbies that keep you from being constantly immersed in work?

Ideally, something that helps you unplug from the internet.

Starting with the end in mind can completely change how you play the game. It sets the rules from day one and gives you clarity on when it s time to step away.

I ve noticed founders fall into two camps:

I ve been improving my site indexing process recently and ran into an interesting limitation.

Google provides APIs for checking URL status, monitoring coverage, and submitting sitemaps. However, the one action many site owners actually want the Request Indexing button in Search Console does not appear to have a general public API.

My current workflow handles everything that can be automated:

• Checking URL indexing status

• Reviewing pages stuck in discovery or crawling stages

• Resubmitting sitemaps

• Creating a shortlist of pages that may need attention

The more responsibilities you take on, the more important it becomes to use your time intentionally. When you are building products, managing different tasks, and trying to make progress every day, productivity becomes less about working longer hours and more about working smarter.

For me, a few things have made a big difference:

• Using AI to speed up research, brainstorming, writing, and repetitive tasks.

• Automating workflows wherever possible instead of doing everything manually.

• Prioritising the tasks that create the biggest impact instead of trying to complete everything at once.

• Using small pockets of time during the day to review ideas, plan, or complete quick tasks.

• Creating systems that make it easier to stay organised when managing multiple projects.

I ve learned that being productive is not about filling every minute with work it s about making sure the time you spend actually moves things forward.

Announcing: Voice Agents course and online community ...

@swyx and I are hosting a month-long technical deep dive into Voice AI and Voice Agents, starting in May.
Our goals are to:
cover all the lessons we've learned over the last two years building realtime, conversational AI,
host fun sessions with all our favorite people who are doing related things,
and
build a long-term online community.
Sign-up link: https://lnkd.in/gnPuHyD4
We'll start announcing free credits for students on Monday. Sign up this weekend with promo code PHUNT for a super-secret Product Hunt community discount.
Last year I signed up for the LLM fine-tuning course taught by Hamel Husain and Dan Becker.
The experience was fantastic in every way. The material was great. The course expanded to cover way more than fine-tuning. It seemed like all of Twitter signed up. I met people in the course Discord that have become online and offline friends. Someone eventually dubbed the course "AI Woodstock." (I think credit for that goes to Swyx.)
We think this is the moment to try to create a similar thing for voice AI.
Voice interfaces are going to be a huge part of the near-future of computing. Voice agents are being deployed at scale today for a wide range of use cases.
collecting patient data prior to healthcare appointments
following up on inbound sales leads,
handling an increasing variety of call center tasks,
coordinating scheduling and logistics between companies, and
answering the phone for nearly every kind of small business.
I'm personally excited about voice interactions for games, realtime video, and voice-enabled programming environments.
https://lnkd.in/gnPuHyD4
Promo code: PHUNT

AI has made building software much more accessible, but it has also raised expectations. Today, users are not only looking for a new idea they expect a smooth, reliable, and valuable experience.

I ve built my own product, and one thing I ve learned is that it s easy to feel ready to launch as soon as something works. But personally, I wouldn t launch a product on Product Hunt if it was still very basic, lacked a clear website or landing page, or hadn t been tested properly with real users.

I believe a strong Product Hunt launch happens when the product is ready to provide real value, not just when the first version exists.

For me, I d feel confident launching when:

Hey Product Hunt community!

For the past few years, my team and I have operated primarily as a software agency building custom products, executing client roadmaps, and solving engineering challenges for others.

Recently, we made a conscious shift to start building and launching our own micro-SaaS products.

Transitioning from "service mode" to "product mode" has been a massive learning curve for us. We quickly realized that building the product is only 20% of the battle; understanding user intent, finding distribution, and defining value proposition are where the real work lies.

When we build products, we usually measure success by features, performance, or growth.

But I've been wondering about something different.

Some products solve a task.

Others change the way people think, work, or make decisions.

When I started building my first product, I thought the hard part would be writing the code.

It turned out the bigger challenge was something else: making hundreds of small product decisions.

Questions like:

• Which feature should come first?

• What should be removed to keep the product simple?

• Which user feedback should be acted on immediately?

• When is a product good enough to launch instead of continuing to polish it?