Why Growth Stalls, and the Five Questions Jason Cohen Asks to Diagnose It

Open on YouTube ↗
Overview

Jason Cohen has founded four companies. The last two, including WP Engine, became unicorns; the earlier one was bootstrapped. Cohen has also invested in about 60 startups and has written at A Smart Bear for nearly two decades. In this conversation with Lenny Rachitsky, almost the entire discussion centers on one problem: a product starts working, grows for a while, and then growth stalls.

34 min read

Cohen's answer is not a checklist of tactics. It is an ordered series of diagnostic questions: whether customers are leaving, whether pricing is right, whether existing customers are growing, whether acquisition channels are saturated, and whether the business needs to grow at all. The order matters, he argues, because a problem higher on the list makes fixes further down largely irrelevant. As Rachitsky notes during the conversation, the same sequence works just as well for a company that simply wants to grow faster.

A Writer Who Publishes Only What He's Proud Of

The episode opens with Cohen's writing. By his count he has published roughly 300 to 350 pieces over about 18 years, of which 150 to 200 are ones he is proud of. That is not many for the time span, and he says it is deliberate. Conventional advice when he started blogging, and still today, was to publish on a regular schedule so readers could fit your work into their routine. Cohen never followed it. His rule was to publish only when a piece was the best he could do, and leave it to readers to judge whether it was useful. Some years that meant one or two posts, other years around 40. During that period he was also founding and running companies, which limited how much he could produce.

Rachitsky says he used to tell people that success with online content came from quality plus consistency, and has increasingly concluded that quality is what matters. Cohen agrees but names the cost. Wanting everything to be your best work keeps the bar high, and it can also tip into paralysis. He says he still struggles with that tension.

How Growth Actually Slows

Cohen lists several reasons growth can stall right now: an economy that he suggests is weaker than headline indicators, AI and uncertainty about it, and plain size. Nobody grows 2x a year forever. Sometimes a single event causes a sudden drop, such as an algorithm change. More often, in his experience, growth decelerates gradually. Teams watch growth constantly, so it doesn't catch them off guard, but it feels like "running through mud": the same amount of work produces less and less.

His framework is ordered like a marketing funnel. If one stage is where everything falls apart, tuning a different stage won't help enough. You go to the biggest problem first.

11:42

Question One: Are Customers Leaving?

The first question is about logo churn, meaning the number of customers who cancel. Cohen calls it the worst problem for several reasons. Once a customer is gone, nothing more can be done: no saving them, no expanding their revenue. Churn also tends to come with negative reviews and social media complaints, which suppress growth further.

He also makes an emotional case. Think about the gauntlet a customer went through to become one. They had to hear about you at all, which is improbable. They clicked, didn't bounce off the homepage, reached the pricing page without being scared off, had the budget, bought the product, and spent time onboarding. Almost no one gets through all of that. Someone who did clearly wanted the product to work, and they still left. Cohen's reaction as a product person is that something fundamental is broken: the company is not fulfilling the promise it made, or the one the customer thought it made. That may be a product failure or a communication failure.

13:46

The ceiling that churn imposes

Online debates about acceptable churn rates tend to be abstract, Cohen says. He considers anything above about 3% monthly cancellation terrible, while others argue that 5, 6, or 7% is fine. He prefers a metric that makes the stakes concrete.

It rests on an idea he thinks people underappreciate: cancellations grow automatically as a company grows, and marketing does not. Imagine your customer base tripled overnight with the same kinds of customers. Next month, AdWords, SEO, and your other channels would deliver the same number of new leads, because they don't care how many customers you already have. But with a 5% monthly cancellation rate, the absolute number of cancellations would triple. Marketing grows only as fast as you can improve it, which is hard, roughly linear work. Churn is a percentage of the whole base, so it is exponential. Churn therefore always catches up with marketing eventually.

Rachitsky compares it to a leaky bucket. Cohen adds that the leak widens automatically as the bucket fills.

The ceiling is easy to compute: new customers per month divided by the monthly cancellation rate. A company that adds 100 customers a month with 5% churn will never have more than 2,000 customers. As it approaches that number, growth slows toward zero, because nearly as many customers leave each month as arrive. Cohen presents this as an explanation for why growth slows automatically at SaaS companies in general. The same calculation works in revenue terms. He prefers customer counts because "we will never have more than 2,000 customers" hits harder.

18:30

Why the cancellation survey lies

Once churn is identified as the problem, you have to learn why people cancel, and customers who are already leaving don't want to spend time explaining. Cohen tells a story from his earlier company, Smart Bear. Its cancellation form had a dropdown of reasons ("too expensive," "project ended," and so on), and one reason was chosen more often than the others. It was first on the list. When the company randomized the order, every option was chosen about equally. The data had been noise. He says other companies have seen the same thing.

His first recommendation is to use open-ended questions. Most people won't answer, but the answers you do get come from the customer. Phrasing matters too. Instead of "Why did you cancel?", ask "What made you cancel?", which points the customer toward what about the product or situation caused it. He took this from Groove, which published a case study: its cancellation email got 10% usable responses asking "why," and 20% after switching to "what made you cancel."

20:39

"Too expensive" is never the reason

Cohen says "too expensive" is usually one of the top reasons in cancellation data, and he considers it never the real one. The customer already saw the homepage, understood the promise, looked at the pricing page, and bought. Their actions show the price was acceptable for what they believed they were getting. Something else happened: the product didn't deliver what they thought it would, or something didn't work. They may have lost their budget, but that is a different reason from the product being too expensive.

He compares this to medicine, where a death certificate records the proximate cause and doctors also try to capture the underlying one. "Stopped breathing" corresponds to "too expensive." Asking further might lead to a car hitting a telephone pole, then to the driver passing out at the wheel, then to undiagnosed diabetes, which is much more useful. Cohen stops to say he dislikes the idea of a single "root cause." Complex systems have many interlocking factors, each of which could be detected earlier or changed. In the medical example, a healthcare system that isn't preventive and a patient who didn't see a doctor both play a part. A good analysis should produce an array of contributing causes, which he jokingly calls "rooter causes." He is also wary of the "five whys" technique for the same reason, since it implies one cause at the bottom.

In a software example, the real reason might be that the product integrates with Jira but the customer uses Linear. Whether to build that integration is a separate decision, but that is the reason, not the price.

"Project ended" gets similar treatment. Cohen mentions seeing a founder on an entrepreneur forum say that more customers were citing it and nothing could be done. Cohen disagrees. If the product had been more useful, would the project have continued? And did the company choose a segment, such as small businesses or consumers, where projects end often because small entities have high variance? That could be a mistake in choosing the ideal customer profile. None of this proves the market should change, he adds, but saying nothing can be done closes the door on options that might be right, and the chosen segment has a lot to do with retention.

26:00

Catch customers before they leave, and invest in onboarding

Cohen also recommends talking to customers who are in trouble but haven't canceled yet. They can sometimes be saved, and they are still willing to talk. The warning signs depend on the product: never uploading data, calling support too often, not calling support at all, not logging in for a while. With enough data you can statistically correlate behaviors with cancellation. Without it, you can form a theory, act on it, and revise it as data comes in.

Rachitsky mentions the long-sought product that watches metrics and flags customers about to churn. Cohen separates two things. Talking to struggling customers doesn't require scale; statistically identifying the predictive behaviors does. He also refines a common piece of advice. People say to find what good customers have in common, but much of that is shared with bad customers because it's simply what all customers do. What matters is what distinguishes the good ones from the bad ones, and in churn analysis, what distinguishes customers who actually cancel.

His default when unsure where to start is onboarding. Most companies see far more cancellations in the first day, 30 days, or 90 days than in the rest of a customer's life, and small onboarding changes can have large effects. He uses his own YouTube videos as an analogy. About 50% of viewers leave in the first 30 seconds, and roughly 20% remain at the end of a longer video. Improving the late part of the video barely changes the final number. Raising early retention from 50% to 55% could raise end-of-video retention from 20% to about 25%, an increase of 20 to 30% in the final outcome. In SaaS, early churn is also the most unprofitable kind, because the company paid to acquire those customers and they didn't stay long enough to pay that back. Even when you know what else to work on, Cohen says, he would still bet on onboarding.

Cohen also treats this first question as a threshold rather than something to keep polishing. For small and midsize businesses, he says 2% monthly churn is good. There is a floor below which churn can't reasonably go, and if you're near it, churn is probably not what's holding growth back.

Where AI fits in analyzing feedback

Asked whether AI could summarize cancellation feedback, Cohen answers carefully. In his experience, LLMs are good at identifying themes and bad at surfacing the specific, actionable details. His explanation is that an LLM predicts the most likely output, which makes it something like an averaging machine: useful when you want the average, weak at finding what is unusual. And the themes are usually predictable anyway, such as "couldn't figure out this integration." The specific details are what make a person think, "Wait, that means we should do this."

His workaround is to ask the model for themes, then ask it to list every specific detail under each theme with which customer said it and a link to the source, so a person can read the specifics. AI can also clean up bad grammar. But he would not rely on it to do the thinking, and he suggests just reading the feedback. Rachitsky adds that outside large consumer apps, the volume of cancellation responses is usually small enough to read directly.

35:53

Question Two: Is the Pricing Right?

The second question is whether pricing is correct. Cohen quotes Patrick Campbell, whom he describes as having data on 4,200 startups: "Your prices are way too low because you just guessed and you haven't changed them." Many companies, Cohen says, copied a competitor or adjusted a number for vague reasons.

People fear raising prices partly because of the textbook demand curve: higher price, lower demand. Cohen says that often isn't what happens. Frequently, a price increase leaves signups unchanged, or signups rise. He says this happens even to solopreneurs on Twitter who raised prices nervously and found that sales went up.

37:39

The founder who charged $300 a year

Cohen tells the story of a founder, whom he declines to name, who sold to enterprise and government customers for $300. Cohen assumed that meant per month; it was per year. The product got one or two signups a week, which is normal for a startup selling to enterprises. Cohen suggested changing the price from per year to per month, a 12x increase. The founder did, and signups stayed at one or two per week.

The founder's next plan was to use the new revenue to hire an engineer and invest in marketing. Cohen stopped them: the next step was to raise prices again. A 12x increase with no visible change means the company still hadn't found the right price. It didn't have to be another 10x, maybe 2x or 50%, but pricing wasn't finished. Cohen notes that this hadn't occurred to the founder even then.

39:04

Pricing selects the market

Cohen's explanation is that price determines which market you're in. At the bottom are customers with small budgets who get limited value, and they do behave like the textbook curve: raise prices and they leave. But a company with a thousand employees and $400 million in revenue, looking at a product priced at $2 or even $100 a month, concludes it can't be good enough. The vendor must be immature, support must be weak, governance policies must be missing. Whether or not that's true, the product looks low quality and aimed at small businesses, so these companies don't buy.

For those buyers, demand rises once the price enters a range that makes sense for what they need, stays up across that range, and falls again at some high point; nobody will pay $10 million a year for it. Cohen describes the resulting shape as more like a mesa than the downward line in textbooks. Only the lowest end of the market, the part that is also worst on most metrics, behaves as the microeconomics curve predicts. Raising prices moves you into a different market, which is why signups can rise. And higher-paying customers, Cohen says, tend to retain better and improve other metrics too.

He adds that pricing is as much art as science, and that the market changes over the years even after you get it right. Price also includes structure: per site, per use, per seat, and so on. The same product at the same price can feel fair or unfair depending on how it's structured.

41:56

Double Down: 8x the revenue from repositioning

Cohen's main illustration is the case in the episode description of repositioning a product to charge eight times as much. He says it's based on something that happened to him, simplified because the real details are complicated and uninteresting.

A fictional company, Double Down, makes AdWords spending more efficient and advertises "cut your AdWords cost in half." A customer spending $40,000 a month on AdWords would save $20,000, but won't pay all $20,000 to Double Down, because then they'd save nothing. Suppose they pay a quarter of the savings, $5,000 a month, and net $15,000. Everyone is reasonably happy, and nothing is wrong with the business.

Cohen then imagines the CMO or chief product officer reporting to the CEO at year end. "We saved money" is welcome. But a CEO would rather hear about growth, which he calls healthier for the company, better competitively, and more valuable. So the pitch changes. The company currently pays $200 per lead. If Double Down halves the cost per lead, the same budget buys twice as many leads. The pitch becomes "double your leads." The company is already willing to spend $40,000 a month for its current leads, so it would be willing to spend $40,000 more to double them. Double Down now earns $40,000 instead of $5,000 for the same product. The CEO, told that leads doubled at the same customer acquisition cost, asks how to get more of it.

Cohen acknowledges he's exaggerating to make the point. The lesson for product managers is to sell more of what the customer company already values, whether growth, customer retention, or competitiveness, rather than cost or time savings. Savings are real value, but they cap what the customer perceives as your worth. Delivering more of what they value raises that cap by perhaps an order of magnitude, in Cohen's estimate.

Rachitsky mentions Jen Abel's observation from an earlier episode that enterprises typically buy SaaS contracts in the $75K to $150K range, and that selling becomes easier once a product fits there.

Pricing can't be changed in isolation

Cohen warns against treating price as a separate knob. A new market brings new requirements: SOC 2, governance features, integrations with systems you didn't know about, professional services. Your competitive advantage may exist only in your current market. The reason may also be cultural. His example is Buffer, which he says could move upmarket but decided it is a company for small users, doesn't want to build for large companies, and finds its current work fulfilling. Changing prices is a decision about the whole strategy, not just a number.

52:25

Question Three: Are Existing Customers Growing?

The third question returns to the churn math. Marketing can't keep pace with cancellations because it doesn't scale with the customer base. What does scale is revenue from existing customers. If 2% of customers leave but some of the remaining 98% upgrade, pay more through usage, or otherwise expand, that growth is proportional to size, and it triples if the base triples.

The metric is net revenue retention (NRR): take current revenue from existing customers and see what it becomes one year later, excluding new customers. Cancellations and downgrades lower it, upgrades raise it, and it can end above 100%.

Cohen explains why NRR alone isn't enough and why he still ranks logo churn first. If NRR looks healthy but too many customers leave, not enough remain to upgrade. He also uses an investment analogy. A $100 stock that falls 20% is worth $80; a 20% gain from there brings it to $96, not $100. Recovering from a 20% loss takes a 25% gain. NRR treats a 20% loss from cancellations as offset by 20% from upgrades, which Cohen says overstates the situation. He recommends tracking both metrics while remembering that NRR is somewhat less favorable than it looks.

His evidence that NRR is essential for scale: if churn really caps growth, large public SaaS companies should almost all have NRR above 100%. He says that of more than a hundred public SaaS companies, about two have NRR below 100%, and those have poor financials and valuations. He cites the median NRR of SaaS companies at IPO as 119%.

He considers the tactics for raising NRR (new features, tiers, usage- or seat-based pricing) fairly obvious. The principle he emphasizes is that customers should agree they're getting more value when they pay more, ideally far more: if the price doubles, they should feel they're getting five times the value. So companies should measure the value customers receive, not just usage statistics that are easy to collect. If that value can be a single number, it might be a North Star metric. If not, use proxy metrics and qualitative conversations. He says many important things aren't numbers, giving market differentiation as an example. Most people, he notes, have left a product they loved when its price rose faster than the value they felt.

He summarizes it as creating more value for the customer and then splitting it with them. The company isn't a charity and is entitled to a share, but it has to create the value first.

Rachitsky raises land-and-expand and Jen Abel's point that a low initial price becomes a reference point that's hard to move from; a customer who started at $10K will resist a jump to $100K. Cohen agrees and adds that you may not deserve the increase. Investors and other forces that aren't the customer can push companies toward policies that are bad for customers. His test for any internal proposal is whether it is actually good for the customer, and whether the customer would say so. Proposals are often framed as if they are when they only benefit the company. His standard is that a change must be good for both. Companies that don't hold to it may succeed short term, he says, but it isn't a good long-term strategy.

Does this apply outside B2B SaaS?

Rachitsky asks whether expansion revenue is harder in consumer products. Cohen agrees it's harder, but says the rules come from the financial mechanics of any business, so they still apply. If you can't find an expansion lever, move to the next question, but a product manager who does find one creates far more value. As a consumer, Rachitsky doesn't want to pay AT&T more, since it offers no more value, but Cohen points to Amazon as a company that does. A second product sold to the same customers is another route, common in consumer goods; Rachitsky mentions AG1 adding a sleep supplement, and Duolingo's many small paid upgrades.

Cohen adds another lever that scales with the customer base: existing customers bringing in new ones through referrals and word of mouth. This is common in consumer products and harder in B2B, where "a midsize company" doesn't refer a friend the same way. The question of how the existing base can drive growth is the same; the answer depends on the segment.

1:06:59

Question Four: Are Your Acquisition Channels Saturated?

The fourth question is whether marketing channels have hit their limits. When growth stalls, Cohen says, the usual reaction is to push the AdWords team for more leads and the SEO team for more searches. But channels have real limits. Magazine advertising called it "inventory": there are only so many searches in your category, and you can appear only once per keyword. There's a theoretical maximum and a lower practical one, and you may be near it.

1:08:07

The elephant curve

Worse, channels decline. People describe channel growth as an S-curve that rises and then plateaus, followed by optimization. Cohen says the curve actually sags after the plateau. He named this the "elephant curve": a trunk rising, then the back sloping down. He says any marketer has stories about it.

He gives several reasons. Audiences saturate: people who have already seen your message many times and didn't act mostly won't act later. Channels themselves decline without telling you. When he bought magazine ads, publications reported rising circulation every year until they shut down. Conferences reported strong attendance until they went out of business. He says the same decline happens with AdWords, Facebook ads, SEO, and affiliate programs. On AI's effect on channels, he says he doesn't know how it will play out now or in two years, only that it won't make every channel grow.

For Cohen, this reinforces his first point: a company can't rely on marketing indefinitely. There are a limited number of channels your customers use, and they sag over time.

1:11:14

What to do about it

He asks listeners whether they know right now which of their channels are saturated. If not, the answer may be all of them. In that case, adding a small feature and pushing marketing harder won't work, however good the feature. He says this is often what companies do anyway, so the question isn't just whether you know this but whether you're acting on it.

Adding indirect channels to direct ones, or vice versa, is one option, but Cohen says, without data, that products that sell well through direct advertising often don't do well through social and SEO, and that SEO-driven products often find ads expensive and ineffective. Rachitsky's view is that most companies get some results from many channels but usually one channel (sales, word of mouth, or ads) drives most growth.

Cohen suggests getting more creative about what counts as a channel. Constant Contact, which sold email marketing to small businesses before modern tools existed, restarted stalled growth by holding in-person workshops in cities, teaching restaurant owners and dentists email marketing using Constant Contact. It seemed impossible that in-person events could pay off for a roughly $20-a-month product, but Cohen says it worked, partly because the company recruited power users who were also agencies to run them. HubSpot tested selling through agencies instead of only direct, and Cohen says that became 50% of revenue after four or five years. At WP Engine, many sites were sold through agencies that build WordPress sites.

The alternative is a new product or market. Cohen mentions a framework he has written about for these expansion decisions. The idea is to keep one foot planted in an existing strength or asset while moving the other into riskier territory with high upside. When acquisition channels are full, he says, these larger bets become necessary because pushing marketing isn't an option.

Rachitsky mentions upcoming or published posts on new growth channels, including Emily Kramer's on ecosystems as a channel, with a quote from Wiz's head of growth about starting with an existing audience of 10,000 rather than zero, and a post on ChatGPT's app store as a possible channel.

1:19:09

Question Five: Do You Actually Need to Grow?

The last question assumes the previous four have been answered satisfactorily: do you need to grow? Sometimes the answer is that this product in this market doesn't need to grow, and the company needs a new product or market. Or the goal can change from revenue to profit. Cohen points to 37signals and many bootstrapped companies that hit a limit and found it acceptable, with founders earning millions a year in dividends. Growing larger might mean running an organization they don't like or serving customers they don't want to serve.

He then takes up the saying "if you're not growing, you're dying," asking whether it's true or just something investors say to push founders to grow when they shouldn't. His view is that it is fairly relevant even for bootstrapped companies that reject growth at all costs. In a company stagnant for years, is the founder fulfilled doing the same thing every day? Do employees get to advance their careers, learn, and innovate? For some people, such as a CPA with a stable client base, stability may be what they want. But he thinks many people drawn to building products and starting companies don't want to repeat the same work for 20 years.

He suggests reading the saying as being about the person, not only the company. Many people, he says, have spent their whole lives in "grow, get promoted, do more" mode without asking whether it makes them happy, or have gotten stuck pursuing growth without stepping back. He points to people who say they hate work but decline after retiring once they lose their purpose. If the business is truly stagnant after everything else has been tried, something drastic may need to change: leaving, restructuring, selling, changing jobs. He calls this question existential rather than another metric, and says you should ask it at least yearly, not only at the end of this sequence. It applies at every scale, he adds; plenty of public companies aren't growing either.

Rachitsky relates this to his newsletter: he'd be sad if it stopped growing, but it has already given him a great life. Cohen extends the point to how you grow. There are probably ways to grow the newsletter that Rachitsky wouldn't be proud of, and success lets you refuse them. Early on, Cohen says, people may work to a looser standard, for example copying other bloggers' styles, and that's fine for getting started. After 20 years, having no voice of your own would be a problem. His conclusion: "if you're not growing, you're dying" is fair, but it has to come with limits, and the more successful you are, the more seriously you can hold to them.

Deciding When to Quit, and the Limits of Probability

Rachitsky mentions advice from Matt MacInnis of Rippling that if a startup hasn't clicked after four or five years, it may be time to move on. Cohen says his next book will be about decisions under uncertainty: whether to quit, move cities, marry someone, or launch a company. The standard advice is to use probability and expected value, but Cohen argues we don't know the probabilities or their distributions, so expected value can't actually be calculated. And even if it could, an individual either sells the company or doesn't; statistics about many cases don't apply to one life. He says probability isn't the right tool for these decisions, though he doesn't yet say what is. Rachitsky notes it raises more questions than it answers, and Cohen agrees.

Hidden Multipliers and the Common Thread

Cohen's first book, Hidden Multipliers, was available for preorder at the time of recording. The title refers to small actions or decisions with large effects on revenue and profit, such as reducing cancellations from 5% to 4% or focusing on onboarding instead of later stages. He says the goal is to go deep enough with examples and specific steps that readers who already "know" these ideas actually act on them. He calls it his best work.

Asked for a final takeaway, Cohen says the common thread is customer value: the product promises the right thing, delivers it, customers can onboard and use it, they recognize the value, and the company measures it. If the North Star is creating value the way customers understand it and in their language, then good pricing and good retention become much more achievable, though not automatic. He acknowledges this sounds like a platitude and that platitudes aren't very actionable, but says it's a reasonable summary given how much detail they've covered. Rachitsky adds that the value may already exist but be aimed at the wrong customers or positioned poorly. Cohen agrees: all of these things have to be right, including communicating the value clearly enough that a visitor understands it on the homepage.

AI Corner: Turning Charts into Data

For his writing, Cohen wants real data, but much of it on the internet exists only as images. He's found AI, especially Gemini, good at converting a chart image into a table he can paste directly into Google Sheets. This lets him gather ten examples to test a theory where previously it was too much work.

1:34:49

Contrarian Corner: A/B Testing Mostly Doesn't Work

Cohen's contrarian view is that A/B testing works poorly and doesn't apply to most things. It can't test strategy, vision, or insight, which he considers the things that matter most. "You don't A/B test whether Uber is a good idea." When teams do test details, they try verb after verb and ad after ad, adopt the seventh or eighth "winner," and repeat. A year later, stacked wins should mean 50–100% improvement, but conversion rates are unchanged. His explanation is that the tools are often not statistically accurate, and that even an accurate tool produces many false positives when real effects are rare. He says real effects are rare in typical A/B testing, so most "wins" are false positives. Unless a team is very sophisticated, he considers it a large waste of time. He uses the poker saying: if you don't know who the sucker at the table is, it's you.

Rachitsky says A/B testing has been useful in his career at scales where small percentage gains mean millions of dollars, while agreeing most people don't work at that scale. Cohen responds with an earlier episode featuring Shopify's CTO, who described a team of about 100 people keeping holdout groups and finding that roughly a third of measured effects disappeared on follow-up. Cohen's point is that if you're working at that level, good for you, and if not, he's skeptical.

Lightning Round

Cohen recommends William Zinsser's On Writing Well ("on my best day I write like that") and Geoffrey Moore's Crossing the Chasm, which he says many people know only from a diagram without having read it. He values Moore's definition of a market, which includes that people in a market respect each other's opinions. That explains why moving to a new market is hard: your case studies stop working. Rachitsky summarizes Zinsser's lesson as "cut," and they recall Zinsser on a panel with an amateur writer who said he never knew writing could be hard, to which Zinsser replied he never knew writing could be easy.

Cohen's favorite show is ER, which he's watching with his 16-year-old daughter, now around season 13; he takes her view that it holds up as evidence that it's good. His favorite products are Wispr Flow for dictation and Anker chargers. His motto is "Be yourself; everyone else is taken," commonly attributed to Oscar Wilde, though while checking citations for the book he found no evidence Wilde said it, and no evidence of who did. He adds that people who like your work want you to be yourself, because that's what they like.

The award on his desk is the 2017 Ernst & Young Entrepreneur of the Year for Central Texas, which he shared with WP Engine CEO Heather Brunner. Cohen calls her a "late-joining co-founder," borrowing how Reid Hoffman described Jeff Weiner at LinkedIn, given her impact over 11 years as CEO. He notes that co-winners are rare enough that he can't think of another case.

Cohen closes by noting that all his articles at A Smart Bear are free, with no ads or courses, and that the book is the only thing he has charged for.