Oji Udezue on Building Products That Spread

TL;DR

Build a great product around a sharp, important problem before trying to manufacture virality. For B2B SaaS, evaluate opportunities by how broadly a workflow applies across departments and how frequently it occurs, then use strategy to move toward frequent, mission-critical usage while grounding product decisions in continuous customer discovery.

Transcript

Products who try to be viral just for what I call synthetic virality that fail. Because in the end, if you're synthetically viral and people get to the product and it sucks, that's it. Slack wasn't even viral, there was no synthetic virality. Slack couldn't even connect to organizations for the longest time. You could be working on the third floor,... Read More

Key Insights

• Sustainable virality is a consequence of product value, not merely a set of sharing mechanics. If a synthetically viral product disappoints new users, distribution cannot preserve its growth because the underlying experience gives people no reason to remain or recommend it.
• A sharp problem is an important and clearly defined customer need that a product can solve exceptionally well. Oji presents this focus as the foundation of both strong product quality and the word-of-mouth behavior that helped Slack spread between workplace groups.
• B2B SaaS opportunities can be evaluated using workflow breadth and workflow frequency. Breadth measures whether a workflow belongs to one department or nearly everyone, while frequency distinguishes activities performed daily or several times a week from those completed only occasionally.
• Frequent workflows used across an entire organization offer substantial potential but are difficult markets to enter. Activities such as email, collaboration, writing, calendaring, and organizational knowledge already attract large companies, including Microsoft, Google, and Atlassian.
• High-frequency niche workflows are a productive area for B2B SaaS companies. Products for engineering, recruiting, marketing, or sales can become valuable businesses because a defined department performs the relevant work repeatedly and may regard the product as essential.
• Low-frequency workflows require a strategy for increasing product importance. A company can identify the department that treats an occasional organization-wide task as mission-critical, then build additional capabilities that support that department's daily responsibilities.
• Workflow categories are strategic positions rather than permanent labels. Companies can move toward more attractive categories by increasing usage frequency, expanding across departments, or developing products for a core group whose needs are more recurring and consequential.
• Customer science is necessary but cannot answer every innovation question. Lean methods, validation, and failing fast improved software development, yet Oji argues that founders must still exercise judgment about the problem space and create solutions that customers may not have proposed themselves.

Questions & Answers

Q: How can a B2B SaaS founder choose a promising problem?

A founder can assess a problem using two dimensions: how many departments perform the associated workflow and how frequently they perform it. Daily or multiple-times-weekly workflows have stronger potential than occasional tasks. Opportunities are especially attractive when the workflow is important across the organization or mission-critical within a specialized department, although organization-wide categories can be harder to enter.

Q: What is a sharp problem in product management?

A sharp problem is an important, specific customer need that a product can solve exceptionally well. The concept emphasizes choosing the underlying problem carefully instead of relying primarily on growth mechanics. When the solution creates obvious value, users have a credible reason to adopt it, continue using it, and tell colleagues about it, creating a stronger basis for growth.

Q: Why does synthetic virality often fail?

Synthetic virality fails when sharing mechanics deliver new users to a weak product. Distribution may increase exposure, but it cannot compensate for an experience that does not solve a meaningful problem. Once people discover that the product is disappointing, the viral loop stops producing durable value. Product quality and problem selection therefore need to precede deliberate virality tactics.

Q: How did Slack demonstrate sustainable product virality?

Slack spread through enthusiastic workplace conversations even when it lacked convenient connections between separate groups in the same organization. People who found it valuable discussed it with colleagues, who then wanted access for their own teams. Oji uses this example to show that a strong solution can generate demand through word of mouth before sophisticated, built-in viral mechanics exist.

Q: What are high-frequency everyone workflows?

High-frequency everyone workflows are activities performed repeatedly by people across many departments, potentially from the doorman to the chief executive. Examples in the discussion include email, collaboration, calendaring, writing, math, and organizational knowledge. These workflows can support valuable products, but entry is difficult because large companies such as Microsoft, Google, and Atlassian already compete in these categories.

Q: What are high-frequency niche workflows?

High-frequency niche workflows are recurring activities concentrated within a particular department or professional function. Oji points to Jira and tools for recruiters, marketers, and sales teams as examples. This category is particularly suitable for B2B SaaS because a focused customer group uses the product repeatedly and may view the workflow as central to completing its work.

Q: How can a low-frequency SaaS product increase its potential?

A low-frequency product can identify the group for which its workflow is most important, then solve more of that group's recurring problems. For example, an activity used occasionally across a company might be connected to a module that a finance department needs every day. This shifts the product toward higher frequency and makes it more mission-critical for a defined customer.

Q: Why should product teams be careful when applying frameworks?

Product frameworks can organize reasoning and reveal patterns, but they should not be treated as static rules that determine a company's fate. The workflow framework is intended to provide predictive guidance while leaving room for strategic movement between categories. Teams still need customer discovery, innovation, and judgment to understand their particular problem and choose an appropriate path.

Summary & Key Takeaways

• Oji Udezue evaluates B2B SaaS opportunities along two dimensions: how many departments use the workflow and how frequently they perform it. Workflows used daily or several times a week offer stronger potential, particularly when they serve either everyone in an organization or a specialized department with an important recurring need.

• The most attractive workflow categories are frequent, organization-wide activities and high-frequency niche activities. The first category includes collaboration, email, calendaring, writing, and knowledge tools, but it is difficult to enter because large companies dominate it. The second includes specialized tools for engineering, recruiting, marketing, and sales teams.

• A company is not permanently trapped in its original workflow category. Strategy can increase its prospects by finding users who consider the product mission-critical, serving more of their recurring needs, and expanding either frequency or organizational reach. Sustainable virality then emerges from solving a sharp problem well enough that customers recommend the product naturally.