Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Jean-Denis says tax customers kept asking for meeting prep and drafted answers, prompting Town to ask why no one had built a great agent for email and calendar. When models became more agentic, that simple workflow focus produced quick product-market fit.

Related Insights

Alex says Town started horizontal so the market could reveal verticals instead of presuming them. Jean-Denis explains that Town interviews power users, groups common routines, and seeds templates for roles like restaurant owners or electricians before AI customization takes over.

Executives across target industries share universal problems: too many emails, meetings, and follow-ups. Start by building a "template" agent that solves these core pain points. Once you deliver that initial value, layer on vertical-specific skills to deepen the product's indispensability.

While sales teams are saturated with AI tools, functions like executive assistants, HR, and junior finance remain underserved. These roles are hungry for technology that eases their email-heavy workflows, making them an ideal beachhead for new AI products to gain a foothold and expand within an organization.

Many voice AI products fail by tackling too broad a problem. April's success came from focusing intensely on a limited set of high-value use cases (email, calendar), which allowed them to build a product that "just works" and feels human-like, driving retention.

Most customers don't know they need an "agentic product." The key to adoption is not marketing the agent itself but solving a user's problem within existing workflows they already understand, such as text messaging or email. This avoids the high friction of teaching users a completely new paradigm.

Initially building a tool for ML teams, they discovered the true pain point was creating AI-powered workflows for business users. This insight came from observing how first customers struggled with the infrastructure *around* their tool, not the tool itself.

Traditional software required deep vertical focus because building unique UIs for each use case was complex. AI agents solve this. Since the interface is primarily a prompt box, a company can serve a broad horizontal market from the beginning without the massive overhead of building distinct, vertical-specific product experiences.

TeamBridge initially built a scheduling tool, but customers revealed the real problem was workflows and automations stuck in spreadsheets *surrounding* the schedule. Pivoting to solve this deeper, systemic pain led to making more money in one month than the previous two years combined.

SaaStr's AI VP of Marketing (10k) and VP of Customer Success (QB) began as basic dashboards and project management tools. They gradually gained more capabilities through iterative development, showing that complex agents can start with simple, focused use cases to solve a specific pain point.

Contrary to the belief that PMs are the earliest tech adopters, go-to-market functions (sales, marketing, support) are leading agent adoption. Their work involves frequently recurring, pattern-based tasks that are a perfect fit for automation, putting them ahead of the curve.