Jennifer Tejada (CEO, PagerDuty): How Selling Sunny Delight and Software are Similar (Video + Transcript)

Editorial note: This title reflects the original SaaStr video-and-transcript context, where Jennifer Tejada was discussed as CEO of PagerDuty. PagerDuty announced on May 11, 2026, that John DiLullo became CEO and Tejada transitioned to Executive Chair. The leadership lessons, however, remain as bright and surprisingly useful as a refrigerator shelf full of Sunny Delight.

At first glance, selling Sunny Delight and selling enterprise software look about as similar as a grocery aisle and a cloud architecture diagram. One involves convincing retailers to give orange-colored beverage bottles precious shelf space. The other involves helping technology teams manage incidents, reduce digital chaos, and keep modern businesses from melting down when software decides to have a dramatic little moment at 2:17 a.m.

But Jennifer Tejada’s story makes the comparison click. Before she became a major technology executive, led PagerDuty through growth and public-company milestones, and became one of the more recognizable voices in digital operations leadership, she learned foundational sales and marketing lessons in consumer goods. The famous Sunny Delight story is not just a cute career anecdote. It is a practical masterclass in customer empathy, market fit, B2B2C selling, and the danger of falling in love with your own features.

In other words, the grocery store was a classroom. The customer was the final exam. The beverage was orange. The lesson was evergreen.

Who Is Jennifer Tejada?

Jennifer Tejada is widely known for her tenure leading PagerDuty, a software company focused on digital operations management, incident response, automation, and operational resilience. PagerDuty helps organizations detect issues, mobilize the right teams, and resolve problems before customers experience serious disruption. In a world where every bank, airline, retailer, streaming service, and food delivery app is basically a software company wearing a different hat, that mission matters.

Tejada’s background is unusual in the best possible way. She did not begin her career by writing code in a hoodie while whispering to a Linux server. She started in consumer products and marketing at Procter & Gamble, where she learned how people discover, evaluate, and buy products. She later moved into technology leadership roles at i2 Technologies, Mincom, Keynote Systems, and eventually PagerDuty. That blend of consumer marketing, enterprise strategy, product thinking, and global operations gave her a rare lens: the ability to see software not merely as a technical solution, but as a human solution.

The Sunny Delight Lesson: Sell the Problem, Not the Bottle

The Sunny Delight story works because it is simple. A salesperson walks into a grocery environment with a product that consumers might like. The pitch is energetic. The product has benefits. The shelf space, however, belongs to the retailer. And the retailer does not care only about what consumers might enjoy. The retailer cares about margins, turnover, logistics, category performance, and whether this new beverage is worth the trouble.

That is where the lesson begins. It is not enough to explain why the end user likes the product. You must also explain why the buyer, distributor, partner, or decision-maker should care. In enterprise software, this is the same puzzle with more dashboards and fewer juice bottles.

Developers may love a tool because it reduces alert noise. Operations leaders may value it because it improves response time. Executives may buy it because downtime costs money and damages trust. Finance may approve it because it protects revenue and reduces inefficiency. Security may care because incidents increasingly cross technical, operational, and compliance boundaries. One product, many stakeholders. One solution, many definitions of value.

That is the B2B2C reality Tejada highlights. Whether the product is Sunny Delight or software, the seller must balance the needs of the user, the buyer, and the business. Miss one of those audiences and the deal gets wobbly. Miss all three and the cart rolls directly into the cereal display.

From Product-Market Fit to Solution-Market Fit

Startups love the phrase “product-market fit.” It sounds tidy, investor-friendly, and just technical enough to impress people at conferences. Tejada’s Sunny Delight lesson pushes the idea further: the real question is not only whether a product fits a market. The question is whether a solution fits a painful, urgent, underserved problem.

This distinction matters. Product-focused teams often obsess over features. They launch a new button, a prettier dashboard, a shinier integration, or a feature name that sounds like it was assembled during a caffeine emergency. But customers rarely wake up thinking, “I hope someone sells me a feature today.” They wake up thinking, “Why is my team drowning in alerts?” “Why did customers see an outage before we did?” “Why does every incident turn into a group chat with 47 people and no owner?”

PagerDuty’s rise reflects that kind of solution thinking. The company built its reputation around helping technical teams respond to unplanned events, coordinate action, and protect digital experiences. As businesses became more dependent on software, incidents stopped being back-office annoyances. They became brand moments. When an app fails, the customer does not blame Kubernetes, an API dependency, or a deployment pipeline. The customer blames the brand. That is why operational resilience has become a boardroom issue, not just an engineering concern.

Why “Shiny Object Syndrome” Can Hurt SaaS Sales

One of Tejada’s most useful warnings is about shiny object syndrome. In consumer goods, the shiny object might be a new ingredient, a brighter label, or a flavor that tastes like a committee meeting. In software, it might be artificial intelligence, automation, a slick user interface, or a new integration that looks fantastic in a demo but does not solve the customer’s core pain.

There is nothing wrong with innovation. PagerDuty itself has expanded into AI-powered operations, automation, and broader digital resilience. The danger comes when teams lead with novelty instead of value. Customers do not buy software because the vendor is excited. They buy because the product helps them survive Monday.

Good SaaS sales keeps returning to the customer’s original problem. What is broken? What is slow? What is expensive? What creates risk? What causes customers to complain? What makes employees quietly update their resumes? Once those questions are clear, features become proof points rather than confetti.

Human Communication Still Matters in Enterprise Software

Modern software companies often dream of frictionless product-led growth. A user signs up, clicks around, invites teammates, upgrades the account, and somewhere in the distance a revenue bell rings. Product-led growth is powerful, especially when users can quickly experience value on their own.

But Tejada’s lesson adds nuance. Bigger, more complex deals still require real human communication. Enterprise buyers need trust. They need to understand implementation, risk, security, change management, procurement, and return on investment. They also need to believe the vendor will be there when something goes wrong.

This is where selling software starts to look a lot like selling into retail. A grocery manager wants confidence that the product will move, fit the category, and justify its space. An enterprise buyer wants confidence that the platform will integrate, scale, reduce risk, and justify its budget. Both are asking the same basic question: “Why should I bet on this?”

Time Is the Most Valuable Currency

In SaaS, everyone talks about money. Revenue. ARR. CAC. LTV. Pipeline. Conversion. Expansion. Churn. The acronyms march across slide decks like tiny corporate ants. But Tejada’s broader point is that time may be the most precious currency in the market.

Customers are busy. Developers are overloaded. Operations teams are tired of noisy alerts. Executives are juggling budgets, risk, competition, and the occasional meeting that could have been a three-line email. If your sales process wastes time, your product feels expensive before pricing even appears.

Great selling respects time. It gets to the point. It connects the product to a real problem. It shows the buyer why action matters now, not someday in the magical land of “next quarter.” It also reduces cognitive load. The best sales conversations do not make customers feel like they need a decoder ring. They make the path forward obvious.

PagerDuty as the Modern Example

PagerDuty’s business sits at the center of a modern truth: digital systems are messy, interconnected, and mission-critical. A single incident can move from engineering to customer support to legal to communications to the executive team faster than someone can type “any updates?” in Slack.

The company’s Operations Cloud and AI-first direction show how incident response has evolved. The market is no longer just about waking up the right engineer. It is about understanding signals, reducing noise, automating repeatable work, coordinating teams, learning from incidents, and helping organizations become more resilient. That makes Tejada’s Sunny Delight comparison even more relevant today. The more complex the product becomes, the more important it is to explain the simple human problem it solves.

For PagerDuty customers, that problem is reliability. Can the business keep running? Can teams respond quickly? Can customers trust the brand? Can leadership understand operational risk before it becomes front-page embarrassment? In enterprise software, the best pitch often sounds less like “look at our feature list” and more like “here is how we protect what your customers already expect from you.”

What Founders and Sales Teams Can Learn

1. Understand Every Stakeholder

The user is not always the buyer. The buyer is not always the approver. The approver is not always the person who feels the pain every day. Strong sales teams map the entire decision chain and translate value for each audience.

2. Sell Outcomes Before Features

A feature is useful only when it points to an outcome. Faster resolution, fewer incidents, lower operational cost, happier customers, and more focused teams are outcomes. A dashboard is a dashboard. Please do not ask the dashboard to carry the whole pitch on its tiny rectangular shoulders.

3. Respect the Customer’s Business Model

Freddie the grocery manager cares about shelf economics. The CIO cares about resilience, cost, security, and scale. The CFO cares about measurable return. The engineering team cares about whether the product actually works. Speak each language without sounding like you swallowed a consulting dictionary.

4. Avoid Feature Theater

Feature theater happens when a company performs innovation instead of delivering value. Customers can tell. They may smile politely during the demo, but inside they are wondering who approved this circus. Stay close to the problem.

5. Make the Buying Journey Easier

Clear messaging, simple proof, useful case examples, and honest implementation guidance reduce friction. The easier it is to understand value, the easier it is for customers to move.

Additional Experience: Applying the Sunny Delight Lesson in Real Business

The most practical way to apply Jennifer Tejada’s lesson is to imagine yourself standing in two places at once: in front of the end user and in front of the economic buyer. Many young companies fail because they only know how to speak to one of them. They build a product users enjoy but cannot justify to management, or they create an executive pitch that sounds strategic but leaves actual users wondering whether anyone has met a real human being before.

In a software startup, this often appears during early sales calls. The founder demos every feature because every feature feels like a beloved child. The customer nods politely. The meeting ends with “This is interesting,” which in sales language can mean anything from “send pricing” to “I have already spiritually left this call.” A stronger approach begins with discovery. What happens when the system fails? Who gets interrupted? How long does resolution take? What does downtime cost? What does the team do manually today? Where does leadership lose visibility?

Once the problem is clear, the sales conversation becomes sharper. Instead of saying, “Our platform has intelligent escalation workflows,” the seller can say, “Your team currently loses 40 minutes finding the right owner during high-priority incidents. This workflow cuts that delay by routing the issue immediately.” Same feature, better framing. The customer hears a business result, not a product brochure wearing a blazer.

The same principle works outside software. A local bakery selling wholesale to cafes should not only say, “Our croissants are delicious.” That is lovely, but the cafe owner also cares about delivery reliability, margin, shelf life, customer demand, and whether the pastry flakes all over the counter like a tiny buttery snowstorm. A fitness app should not only say, “We have workout plans.” It should explain how it improves consistency, reduces decision fatigue, and helps users stay engaged long enough to see results. A cybersecurity vendor should not only say, “We detect threats.” It should show how it reduces alert fatigue, prioritizes urgent risks, and helps teams act before damage spreads.

Tejada’s Sunny Delight-to-software bridge is powerful because it strips selling down to fundamentals. Know the market. Understand the customer’s customer. Respect the buyer’s constraints. Solve a painful problem. Communicate in plain language. Keep the pitch focused on value, not vanity. Whether the product sits in a grocery cooler or a cloud platform, the job is the same: earn trust, prove relevance, and make the customer’s decision easier.

That is also why the story remains useful for leaders. Strategy can become abstract, especially in fast-growing technology companies. Teams chase trends, competitors, analyst categories, and whatever phrase is currently glowing in the market. But the best leaders keep dragging the conversation back to the customer. Who are we serving? What pain are we solving? Why are we uniquely qualified to solve it? Why now?

In that sense, Sunny Delight was not a detour from Tejada’s software career. It was preparation. It taught the discipline of market empathy before the market involved incident response, AI operations, and public-company leadership. The package changed. The lesson did not.

Conclusion

Jennifer Tejada’s comparison between selling Sunny Delight and selling software is funny because it feels unlikely. It is valuable because it is true. Great selling is not about shouting features louder than competitors. It is about understanding the customer’s world deeply enough to explain why your solution deserves attention, budget, and trust.

For SaaS companies, the message is especially clear. Do not let shiny features distract from painful problems. Do not confuse users with buyers. Do not assume technical brilliance automatically becomes business value. And please, for everyone’s sake, do not make customers sit through a 47-slide demo before explaining what problem you solve.

From a grocery aisle to the PagerDuty Operations Cloud, the best sales lesson is refreshingly simple: sell the outcome, balance the stakeholders, respect the customer’s time, and keep the solution tied to a real problem. The bottle may change. The buyer psychology does not.