Company Emails, Memos & Writing Practices: A Curated Collection

A curated archive of the most influential internal emails, memos, marketing emails, culture documents, copywriting examples, and writing practices from technology companies, venture capital firms, and legendary founders. These documents shaped strategy, culture, and entire industries — and most were never meant to be public.

Why this matters: The most important decisions in business are made in writing. Not in pitch decks, not in meetings, not on Slack — in carefully written memos and emails. Studying how the best companies write is studying how they think.

2. 1. Strategy Memos That Changed Companies

These memos redirected entire organizations. Each one was written for an internal audience, with the raw candor that comes from not expecting the public to read it.

Jeff Bezos’s API Mandate (~2002)

Company: Amazon
Context: Internal directive to all teams

Five rules that created AWS:

All teams will henceforth expose their data and functionality through service interfaces.
Teams must communicate with each other through these interfaces.
There will be no other form of interprocess communication allowed.
It doesn’t matter what technology they use.
All service interfaces, without exception, must be designed from the ground up to be externalizable.

The famous final line: “Anyone who doesn’t do this will be fired.”

This memo only became public in 2011, when Google engineer Steve Yegge accidentally posted an internal rant praising Amazon’s approach to Google+. The directive laid the architectural foundation for Amazon Web Services. A six-sentence email created a $90B+ business.

Bill Gates’s “Internet Tidal Wave” (May 26, 1995)

Company: Microsoft
Length: 5,600 words to executive staff

“The Internet is a tidal wave. It changes the rules.”

“I have gone through several stages of increasing my estimate of [the Internet’s] importance. Now I assign the Internet the highest level of importance… even more important than the arrival of the graphical user interface.”

This memo pivoted the entire company toward the internet, leading to Internet Explorer and Microsoft’s web strategy. It surfaced as DOJ evidence in the antitrust trial. Gates wrote it when Netscape had 80%+ browser market share and most of Microsoft’s leadership didn’t understand why the internet mattered.

Brad Garlinghouse’s “Peanut Butter Manifesto” (2006)

Company: Yahoo
Author: SVP of Communications

“I hate peanut butter. We all should.”

Argued Yahoo was spreading resources too thinly — like peanut butter on bread. Called for focus, clear ownership, and accountability. The memo was forwarded to the Wall Street Journal and published, becoming one of the most-cited examples of a strategic internal critique. Garlinghouse is now CEO of Ripple.

Howard Schultz’s “Commoditization” Memo (February 2007)

Company: Starbucks
Context: To senior management, one year before Schultz’s return as CEO

“Over the past ten years, in order to achieve the growth from less than 1,000 stores to 13,000 stores, a series of decisions led to the watering down of the Starbucks experience.”

Bemoaned automatic espresso machines and decisions that “improved efficiency and increased economies of scale but robbed stores of their essential magic.” A case study in strategic self-awareness — the founder diagnosing what the company he built got wrong.

Google’s “We Have No Moat” (May 2023)

Company: Google
Document: Leaked internal research document

“We Have No Moat, And Neither Does OpenAI.”

Argued that open-source AI would outpace both Google and OpenAI. The most influential leaked AI strategy document of 2023. Sparked global debate about open-source vs. closed AI models and forced both companies to reconsider their strategies.

Tobi Lütke’s AI Mandate (April 2025)

Company: Shopify
Length: ~1,300 words (self-published on X when it started leaking)

“Reflexive AI usage is now a baseline expectation at Shopify.”

“If you’re not climbing, you’re sliding.”

Mandated AI use in performance reviews. Required employees to prove jobs cannot be done by AI before requesting additional headcount. The most concrete example of a CEO embedding AI into company operations policy.

3. 2. CEO Emails That Defined Culture

Email	Company	Year	Key Quote	Impact
Elon Musk’s “Communication Within Tesla”	Tesla	2018	“If, in order to get something done between depts, an individual contributor has to talk to their manager, who talks to a director, who talks to a VP, who talks to another VP… then super dumb things will happen.”	One of the most shared CEO emails on workplace communication. Outlined 6 productivity rules including “excessive meetings are the blight of big companies” and banning jargon/acronyms.
Brian Chesky’s “Don’t Fk Up the Culture”**	Airbnb	2013	“Culture is a thousand things, a thousand times. It’s living the core values when you hire; when you write an email; when you are working on a project.”	Written after Peter Thiel warned (post-$150M investment) that companies at Airbnb’s stage usually “fuck it up.” Became one of the most-cited CEO culture letters ever.
Brian Chesky’s COVID Layoff Letter	Airbnb	2020	“I have a deep feeling of love for all of you.”	Announced 1,900 layoffs. Considered the gold standard of layoff communications: transparent, empathetic, step-by-step reasoning. Created an alumni directory for laid-off employees. Contrasted sharply with Better.com’s Zoom call and Meta’s mass email.
Satya Nadella’s First Day Email	Microsoft	2014	“Our industry does not respect tradition — it only respects innovation.”	Outlined “mobile-first, cloud-first” vision on his first day as CEO. Set the direction for Microsoft’s revival from ~$300B to $3T+ market cap.
Dara Khosrowshahi’s Cultural Norms	Uber	2017	“The culture and approach that got Uber where it is today is not what will get us to the next level.”	Replaced Travis Kalanick’s 14 values with 8 new norms. Noted that Kalanick’s “toe-stepping” value was “too often used as an excuse for being an asshole.” Over 1,200 employees submitted ideas, voted on 22,000+ times.
Brian Armstrong’s “Mission-Focused” Memo	Coinbase	2020	“We don’t engage in broader societal issues… we don’t take on activism.”	Declared Coinbase would not be a forum for political debate. Offered generous severance to anyone who disagreed. Jack Dorsey publicly responded that a crypto exchange is inherently activist.

The Anti-Leak Emails (That Leaked)

A recurring genre in tech:

Mark Zuckerberg (2010) — Subject line: “Please Resign.” Sent after TechCrunch published a story about Facebook “secretly building a phone.” The anti-leak email itself leaked within hours.
Tim Cook (2021) — Wrote that “people who disclose confidential information do not belong at Apple.” The memo about stopping leaks was immediately leaked to the press.

4. 3. Founder & Shareholder Letters

Annual shareholder letters are the only format where CEOs consistently write at length, for a public audience, year after year. The best ones are masterclasses in strategic communication.

Author	Company	Span	Key Practice	Notable Detail
Warren Buffett	Berkshire Hathaway	1965–present	Writes as if to his sister Doris. Uses “you” 50+ times per letter. Conversational prose for complex financial concepts.	60 years of letters. The gold standard of investor communication. Google’s founders modeled their IPO letter after Buffett’s “Owner’s Manual.”
Jeff Bezos	Amazon	1997–2020	Attached the original 1997 letter to every subsequent annual letter as a reminder of long-term philosophy.	“It’s All About the Long Term” — 23 years of consistency. The 1997 letter established “we will continue to focus relentlessly on our customers” as Amazon’s north star.
Mark Zuckerberg	Facebook	2012 (S-1)	Introduced “The Hacker Way” as management philosophy.	“Facebook was not originally created to be a company. It was built to accomplish a social mission.” Coined “Move fast and break things.”
Larry Page & Sergey Brin	Google	2004 (IPO)	The “Owner’s Manual for Google Shareholders,” explicitly modeled on Berkshire Hathaway.	Included “Don’t be evil” and: “We will optimize for the long term rather than trying to produce smooth earnings for each quarter.”
Daniel Ek	Spotify	2018 (Direct Listing)	Defined the direct listing as an alternative to the IPO circus.	“Normally, companies ring bells… We’re not raising capital, and our shareholders and employees have been free to buy and sell our stock for years.”

Paul Graham’s Essays as Corporate Communication

Not shareholder letters but functionally equivalent: Paul Graham’s 200+ essays at paulgraham.com form the intellectual backbone of Y Combinator and Silicon Valley startup culture. Key essays:

“Do Things That Don’t Scale” — the single most influential essay on early-stage startup strategy
“Maker’s Schedule, Manager’s Schedule” — gave language to a universal frustration
“Write Like You Talk” — advocates spoken language in writing for clarity
“How to Start a Startup” — launched the template for startup advice essays

5. 4. Culture Documents & Handbooks

Netflix Culture Deck (2009)

Format: 125–127 slides
Title: “Netflix Culture: Freedom and Responsibility”
Took: 10 years to write (Reed Hastings & Patty McCord)
Views: 20+ million on SlideShare

Sheryl Sandberg called it “the most important document ever to come out of the Valley.”

Seven pillars including:

Talent density: hire “stunning” colleagues, adequate performers get a generous severance
Candor: “Say what you think with positive intent”
Freedom: remove controls like vacation policies and expense approvals
Context, not control: provide the strategic context, then trust people to make decisions

Used as an onboarding document — Hastings and McCord met with every 10 new employees to discuss it in their first months.

Valve’s “Handbook for New Employees”

“A fearless adventure in knowing what to do when no one’s there telling you what to do.”

Explains Valve’s flat organizational structure: no managers, employees choose their own projects, desks have wheels so people can physically move to join teams. Available in 8 languages. One of the most radical public employee handbooks ever published.

GitLab’s 10,000+ Page Handbook

Everything documented in a public handbook. One of the largest all-remote organizations in the world. Asynchronous communication is the default. Conclusions of all offline conversations must be written down. The handbook is open to external feedback.

Bridgewater’s “Principles”

Ray Dalio’s “Principles” — originally a 123-page self-published document in 2011, later a bestselling book. Born from a 1993 incident where three top lieutenants told Dalio his radical truthfulness was “hurting people’s morale.” Rather than rejecting the feedback, he built a culture of “thoughtful disagreement” and “idea meritocracy.” Over 300 principles governing every aspect of company behavior. All meetings are recorded and anyone at Bridgewater can watch.

6. 5. Writing-as-Management: Company Practices

Some companies don’t just write well — they use writing as the primary management tool. These are the most deliberate writing cultures in technology.

Amazon: The 6-Page Memo

Started: June 9, 2004
Rule: No PowerPoint. All meetings begin with silent reading of 6-page narrative memos.

“The narrative structure of a good memo forces better thought and better understanding of what’s more important than what.”

Participants receive printed copies and silently read for ~30 minutes at the start of every meeting. For new products, the first page is a press release written as if launching tomorrow (“Working Backwards”); the next 5 pages are FAQs. Bezos said great memos “should take a week or more” to write. PowerPoint “gives permission to gloss over ideas, flatten out any sense of relative importance, and ignore the interconnectedness of ideas.”

Stripe: Footnoted Emails & Decision Logs

Practice: Writing-first decision-making. Pre-meeting memos mandatory. No real-time brainstorming.

CEO Patrick Collison’s internal emails include academic-style footnotes, which became common practice company-wide. Written project documentation is required before launching any initiative, outlining goals, risks, assumptions, and metrics. Many teams published decision logs into Slack channels — even for small decisions. Nothing important lived only in Slack; conversations were moved to structured documents.

As David Singleton (Stripe’s former CTO) put it: “Investing extra time to communicate an idea through clear, precise writing delivers outsized results because vastly more people consume the writing than produce it.”

Collison noted the culture partly comes from early Stripe employees being “misanthropic introverts” who communicated in written form “because it’s less oppressive than having to talk to each other.”

Basecamp/37signals: Writing First, Meetings Last

Published a formal Guide to Internal Communication. Key principles:

Long-form writing over meetings, video, and chat
Company-wide announcements on message boards, not email — “so everyone sees and hears the same thing, including future employees”
40-hour work weeks (32 in summer), 6-week cycles
Asynchronous communication as the default

Intel: Andy Grove’s OKR System (1970s)

Andy Grove formalized Objectives and Key Results as a management framework, documented in his 1983 book High Output Management. Used “Operation Crush” with OKRs to realign Intel against Motorola. The system spread from Intel to Google via John Doerr and became the dominant goal-setting framework in tech.

7. 6. Internal Communication Frameworks: RFCs, PRDs, Design Docs

Beyond memos and emails, the best companies have formalized how they write about decisions, products, and architecture. These frameworks turn writing from a skill into a system.

Amazon’s PR/FAQ (“Working Backwards”)

Beyond the 6-pager, Amazon uses PR/FAQs — a mock press release and FAQ document written before building anything. The press release is written from the customer’s perspective, followed by FAQs addressing both external customer questions and internal stakeholder concerns. This forces product teams to articulate the value proposition before writing a single line of code.

Basecamp’s Shape Up Pitch Format

Every project pitch has exactly five ingredients:

Problem — what needs solving
Appetite — how much time is this worth? (not “how long will it take?”)
Solution — the proposed approach
Rabbit Holes — risks identified in advance
No Gos — things explicitly out of scope

“Writing things out makes you consider them at a deeper level.”

The pitch format forces the author to present their case uninterrupted — “the person making the pitch can’t be interrupted and is guaranteed to present their story completely.”

Figma’s Three-Phase PRD

VP of Product Yuhki Yamashita structures PRDs into three phases matching their Product Review types:

Problem Alignment — the PM articulates the problem clearly enough that the reader can “imagine possible solution directions and get a very rough sense of project scope”
Solution Alignment — embeds Figma design files, presents solutions as user flows because “user flows are the easiest way for readers to understand the project because it shows how the customer will ultimately experience it”
Launch Readiness — outlines cross-functional dependencies

These are living documents built in Coda, not static specs.

Intercom’s One-Page “Intermission”

“The longer the doc, the less it gets read. The longer the doc, the less it gets remembered… If you’re forced to limit the brief to one page, you will get much better at describing the problem you’re solving.”

— Paul Adams, VP of Product

Intercom invented the Job Story format as an alternative to user stories: “When [situation], I want to be able to [motivation], so I can [expected outcome].”

Google’s Design Doc Structure

Created before coding begins by the primary authors of a system. Documents the high-level implementation strategy and key design decisions “with emphasis on trade-offs.” Typical sections: Context and Scope, Goals and Non-Goals, The Actual Design (system architecture, APIs, data storage), Alternatives Considered, and Cross-cutting Concerns.

Spotify’s DIBB Framework

DIBB stands for Data, Insight, Belief, Bet. Start with Data (observable facts), distill an Insight from it, form a Belief (hypothesis), and define a Bet (action to test the belief). People can read a DIBB document and challenge it at any layer. Used across Spotify for aligning engineering and product decisions.

Sourcegraph’s RFC Template

Metadata first: recommender’s email, date, status, decider, input providers, and approvers with deadlines. Then a one-paragraph summary. The background section is strictly factual — no opinions allowed. The problem section must justify why the problem is worth solving now. Sourcegraph describes their RFCs as “intended to be lightweight, low-process, and effortless to create.”

Architecture Decision Records (ADRs)

Michael Nygard’s 2011 format: a short text file with five sections — Title, Status (Proposed/Accepted/Deprecated/Superseded), Context (forces at play), Decision (the response), and Consequences (what happens after). Thoughtworks put ADRs in the “Adopt” category of their Technology Radar. AWS and Azure both recommend them.

8. 7. Marketing Emails That Made History

Famous Cold Emails

Email	Company	Result	Key Insight
Craigslist Poaching Emails	Airbnb (2009–2010)	Built the entire initial supply side of the marketplace	Systematically emailed vacation property owners on Craigslist, suggesting they cross-list on Airbnb. Acknowledged as spam, but it worked. Arguably the most famous growth hack email in startup history.
Tim Ferriss’s VIP Template	Personal brand	Became the gold standard for reaching CEOs and VIPs	“I know you are very busy and get a lot of email so this will only take 60 seconds to read.” One specific question. Always offers an easy out: “I totally understand if you’re too busy to reply.”
The “Donuts and Puns” Email	Gong	Closed the deal after deep LinkedIn research	“I donut want my message to get lost in your inbox.” The sender researched the recipient’s LinkedIn, discovered they cared most about their kids, and sent personalized donuts. Deeply personalized emails see reply rates 142% higher than generic outreach.
Customer Development Email	Groove HQ	Talked to 500 customers in 4 weeks. Built Groove to $5M/year.	CEO Alex Turnbull emailed every customer personally asking for development interviews. Also built an influencer outreach list of ~250 names with ~90% response rate.

Legendary Launch Emails

HEY Email Launch (Basecamp, 2020)

“It feels great to get an email from someone you care about. Or a newsletter you enjoy. Or an update from a service you love. That’s how email used to feel all the time.”

“Now email feels like a chore, rather than a joy. Something you fall behind on. Something you clear out, not cherish. Rather than delight in it, you deal with it.”

“HEY is a redo, a rethink, a simplified, potent reintroduction of email.”

50,000+ people requested invites on launch day.

Superhuman’s Exclusive Waitlist

Instead of a traditional launch email, Superhuman flipped the funnel. Applicants filled out a 15–20 question survey, received a follow-up email, then got a 30-minute onboarding video call. The waitlist hit 180,000+ people. People happily paid $30/month for email in a world where Gmail is free.

Harry’s Pre-Launch Referral Email (2013)

Employees sent personal emails to friends announcing “Harry’s is coming.” The referral sharing copy: “Shaving is evolving. Don’t leave your friends behind.” Milestone-based rewards: 5 referrals = free shave cream, 10 = free razor, 25 = premium razor, 50 = free shaving for a year.

Result: 100,000 email signups in one week, with 77% coming from referrals.

Product Hunt Began as an Email List (2013)

Ryan Hoover created an MVP using Linkydink, invited a few startup friends to contribute, wrote a quick blog post, and had an MVP within 20 minutes. The entire product started as a curated email list before becoming the platform we know today. Proof that a major tech platform can start as nothing more than an email list.

Investor Update Emails

Buffer’s Transparent Updates

Buffer pioneered radical transparency in investor updates, sharing not just wins but detailed lowlights, exact metrics, and honest assessments of what went wrong. Structure:

TL;DR at the top with biggest wins
Highlights — 3–5 key wins
Lowlights — what didn’t work (never hide bad news)
Key Metrics — same metrics every month (MRR, churn, CAC, runway)
Asks — specific, actionable requests (intros, hires, advice)

Investors say startups that send monthly updates are more likely to get follow-on funding.

9. 8. Onboarding Email Sequences

Welcome emails have 86% higher open rates than regular marketing emails. Sending a series of onboarding emails generates 51% more revenue than a single welcome email.

Company	Approach	Key Detail
Slack	Action-based, not calendar-based	Only sends action-triggered emails apart from the welcome email. No fixed drip sequence (day 1, day 3, day 7). Emails are triggered by user behavior — what they have actually done or not done. Pioneered behavior-triggered onboarding over calendar-based drips.
Duolingo	Passive-aggressive escalation	Day 1: “Learning Spanish requires daily practice.” Lapsed: “We haven’t seen you in a while.” Guilt trip: “You made Duo sad.” Nuclear option: “Hi, this is Duo. These reminders don’t seem to be working. We’re going to stop sending them for now.” That last email was their most effective notification ever.
Notion	Segmented by use case	Personal account version talks about templates for personal use. Teams version highlights exec templates and collaboration. Same product, different onboarding paths based on signup data.
Superhuman	High-touch human onboarding	“Welcome to Superhuman Mail, the fastest email experience ever made! We’re delighted you’re here, and are excited to help you move faster, save hours every week, and spend more time on what matters.” Originally required a personal onboarding call before you could use the product.

10. 9. Newsletter Formats & Writing Styles

Newsletter	Format	Voice	Scale
Morning Brew	36 mostly curated items with little original reporting. 3 larger editorial articles without external links, then roundups that invite click-through. 5 short bullet-point features covering current news, future news, and light-hearted trivia.	Simple, businesslike. Sparing use of bold text and bullet points. Headline-image-body format.	Millions of subscribers. Acquired by Business Insider for $75M.
The Hustle	Conversational daily business news. Every piece of copy must be “entertaining or educational.”	Shaped by: “How would we write to our really smart friends?” Inspired by David Ogilvy and Joseph Sugarman. Maintained a style guide specifying approved and banned words.	2M+ subscribers. Acquired by HubSpot.
Lenny’s Newsletter	Hook (1–2 sentences with a blunt insight), Context (2–3 sentences), Tactical Breakdown (3–5 bullets of exactly what was done, what worked, what didn’t).	“Casual, tactical, and fluff-free — 1:1 writing from a smart operator to peers.”	One of the highest-earning newsletters on Substack.
Stratechery	Long-form, single-topic deep dives. One well-argued essay per email rather than curated roundups.	Analytical, structured argumentation. Strategy and business of technology and media.	Pioneered the premium individual newsletter model.

11. 10. Apology & Crisis Emails

Buffer’s Security Breach (2013) — The Gold Standard

“I wanted to get in touch to apologize for the awful experience we’ve caused many of you on your weekend. Buffer was hacked around 1 hour ago, and many of you may have experienced spam posts sent from you via Buffer. I can only understand how angry and disappointed you must be right now.”

Followed by actionable steps: remove spam postings, your passwords are not affected, no billing information was exposed. They disclosed the root cause: a backdoor through their partner MongoHQ. Buffer came out of the crisis with increased trust.

Travis Kalanick’s Uber Apology (2017)

“To say that I am ashamed is an extreme understatement. My job as your leader is to lead… and that starts with behaving in a way that makes us all proud. That is not what I did, and it cannot be explained away.”

“This is the first time I’ve been willing to admit that I need leadership help and I intend to get it.”

Despite being well-written, it was criticized as too little too late. Kalanick resigned months later.

Zuckerberg’s Cambridge Analytica Apology (2018)

“This was a breach of trust, and I’m sorry we didn’t do more at the time.”

“I promise to do better for you.”

Published as full-page ads in The New York Times, Washington Post, Wall Street Journal, and several UK newspapers. Facebook’s value had already plunged by ~$50 billion. The Washington Post documented “14 years of Mark Zuckerberg saying sorry, not sorry.”

Patterns in Crisis Communication

Element	Good (Buffer)	Bad (Most others)
Speed	Disclosed within 1 hour	Days or weeks of silence
Specificity	Exact root cause named	Vague “we take this seriously”
Accountability	CEO takes personal responsibility	Passive voice, blame shifted
Actionability	Tells users exactly what to do	Generic “we’re investigating”
Follow-up	Ongoing updates until resolved	One statement, then silence

12. 11. Win-Back & Churn Prevention Emails

Netflix’s Win-Back Machine

Netflix’s winback emails fall into three categories: content updates highlighting new shows, value reminders (“watch whenever,” “always commercial-free”), and social proof.

The critical insight: across 30+ winback emails analyzed, not a single one included a discount, promo code, or limited-time deal. Netflix assumes you haven’t seen the right title yet, not that you need a price cut. Emails never sent before 10 AM or after 5 PM, max one per day.

Duolingo’s Reverse Psychology

Progressive escalation from “We haven’t seen you in a while” to “You made Duo sad” to the famous: “Hi, this is Duo. These reminders don’t seem to be working. We’re going to stop sending them for now.”

The “stop sending” email was their most effective win-back message. The reverse psychology of threatening to go away brought users back.

Spotify Wrapped & Grammarly Year-in-Review

Spotify Wrapped turns listening data into a personalized story. Instead of “You listened to 14,310 minutes,” Spotify reframes data as identity: “You’re in the top 1% of Taylor Swift fans!” The copy transforms raw usage data into ego-boosting, shareable narratives. Became the most shared email-to-social campaign in history.

Grammarly’s Year-End Recap shows words checked, vocabulary variety, tone distribution, and groups users into categories like “Confident Communicators” or “Productivity Pros.”

13. 12. Referral & Viral Growth Emails

Company	Year	Mechanism	Result
PayPal	2000	Both referrer and new user received $20 (later $10, then $5) for signing up, confirming email, and adding a credit card. “Cash was universal — no points, no vague discounts, just spendable money.”	10% daily growth rate. 1M to 5M users in 6 months. PayPal spent $60–70M on referral rewards with no revenue. The internet’s first major viral referral program.
Dropbox	2008–2010	Instead of “Invite your friends,” Dropbox framed it as “Get more space.” Both sides received 500MB of free storage. Offered Gmail/Yahoo/AOL contact sync to lower friction.	3,900% growth in 15 months (100K to 4M users). By early 2010, users sent 2.8 million invites per month.
Harry’s	2013	Employees sent personal emails. Milestone-based referral rewards (5 = cream, 10 = razor, 25 = premium, 50 = year free). “Shaving is evolving. Don’t leave your friends behind.”	100,000 email signups in one week, 77% from referrals. Personal emails from employees, not press outreach, drove the growth.

14. 13. Email Subject Lines That Became Case Studies

Obama Campaign’s “Hey” (2012)

Most of the $690 million raised online came from email. A staff of 20 full-time email writers constantly A/B tested different versions, sending to small lists first before rolling out.

Subject Line	Result
“Hey” (used 5 times)	Consistently high open rates
“I will be outspent”	$2.5M from a single send
“Some scary numbers”	~$1M projected
“Join me for dinner?”	The famous $3 dinner ask

The casual, low-key subject lines massively outperformed formal ones.

Ramit Sethi — $20M/year from 800K Subscribers

Subject lines like:

“REJECTED: Guy at farmers’ market shuts me down”
“Earnable closes @ midnight — did you decide?”
“This email might change your life”

Still uses plain text for almost all emails. People say: “Sometimes I’ll be reading your emails and think ‘Did he write this to just ME?’”

Charity:Water — Story-First Approach

Rather than asking for donations, charity:water sends videos and stories. Increased donations by $800,000 by switching to video-based emails. Progress report emails show donors exactly where their money went — something most charities never do.

Subject Line Data

Analysis of 115 million emails: subject lines with numbers get 45% higher open rates. Open rates peak with 1–5 word subject lines. Title case outperforms other formatting.

15. 14. Landing Page Copy & Taglines

The Headlines

Company	Headline	Why It Works
Slack (2013)	“Be less busy”	Promises a feeling, not a feature. Stewart Butterfield proposed the line almost verbatim.
Stripe	“Payments infrastructure for the internet”	Five words. Positions as foundational (infrastructure) not transactional (payments processor).
Vercel	“Develop. Preview. Ship.”	Three imperatives. Three periods. Maps directly to the three steps of their workflow. Works as both description and instruction.
Linear	“The issue tracker you’ll enjoy using”	Dares to use the word “enjoy” in enterprise tooling. Positions against the drudgery of Jira.
Superhuman	“The fastest email experience ever made”	Superlative claim. “Experience” not “client” — sells speed as a feeling.

Basecamp’s Problem-Recognition Pattern

Their homepage uses a series of pain-point headlines:

“Team super busy, but running in circles? It’s time for Basecamp.”
“Finding stuff easy to start, but hard to finish? It’s time for Basecamp.”
“Things taking longer than they should? It’s time for Basecamp.”
“Subscription fees keep adding up? It’s time for Basecamp.”

Each identifies a pain point the reader already feels and positions Basecamp as the singular answer.

The Great Taglines

Tagline	Company	Origin
“1,000 songs in your pocket”	Apple (iPod, 2001)	Written by James Vincent at Chiat/Day. Jobs pulled the iPod from his jeans pocket at the launch event and said it. The line existed months before the name “iPod” was chosen.
“Think Different”	Apple (1997)	Created by Craig Tanimoto at Chiat/Day. Grammatically incorrect on purpose — “Different” (adjective) instead of “Differently” (adverb) positions thinking itself as the object, not the method.
“Move fast and break things”	Facebook (2012)	Coined by Zuckerberg. In 2014 he changed it to “Move fast with stable infrastructure” — which nobody remembers, proving that the sharp edges of the original are what made it stick.
“Don’t be evil”	Google (2000)	Featured in the 2004 IPO prospectus. In 2015, Alphabet quietly replaced it with “Do the right thing” — the blander replacement is itself a case study in how hedging kills copywriting.
“Increase the GDP of the internet”	Stripe	Patrick Collison: “It’s our mission statement but also, importantly, our strategy. Zero sum games are bad.” Works because it is simultaneously grandiose and precise.
“Work hard. Have fun. Make history.”	Amazon	Three imperatives, escalating scope: personal discipline, team culture, civilizational ambition.
“Your AI pair programmer”	GitHub Copilot	Four words. Borrows a term (“pair programmer”) developers already trust, prefixes with “AI,” makes it personal with “Your.”

Stripe’s 7 Lines of Code

Stripe’s original landing page (2011) featured a code snippet showing how to accept a payment in just 7 lines of code. The README-as-marketing approach — showing the product is the code example — became the template for every developer-tools company that followed.

16. 15. Error Messages, Microcopy & 404 Pages

The best brand voices show up in the places nobody expects copy to matter: loading screens, error pages, send confirmations, and empty states.

Company	Where	Copy	Why It Works
Mailchimp	Send confirmation	A cartoon chimp arm gives you a high five. “High fives! Your campaign is in the queue and will be sent shortly.” Followed by: “Take a breather — you’ve earned it.”	Acknowledges the anxiety users feel before hitting send on an email to thousands of people.
GitHub	404 page	“This is not the web page you are looking for.”	Star Wars reference with a parallax illustration. Disarms frustration with nerd humor that matches the audience.
Slack	Loading messages	Short, friendly quips attributed to “Your friends at Slack.” You can add up to 150 custom loading messages per workspace.	Turns a loading state into a moment of personality. The feature itself is the microcopy innovation.
Stripe	Error messages	47 distinct decline code messages, each in plain language. Every error includes a human-readable `message` field, a `doc_url` linking to docs, and a `request_id` for debugging.	Designed to be shown to end users, not just developers. Instead of “Error 402,” returns specific text explaining what happened.
Lego	404 page	“Oh bricks!” with a scared Emmet minifigure	Family-friendly expletive substitute that is perfectly on-brand.
Spotify	404 page	“404s and heartbreaks” next to a spinning record	A pun on Kanye West’s 808s & Heartbreaks that speaks directly to the music-loving audience.
Pixar	404 page	Sadness from Inside Out says: “It’s just a 404 error!”	On-brand because the company literally makes characters for a living.
Notion	Empty states	Minimal prompt. New blank pages invite you to start typing with subtle placeholder text. Getting Started: “Type ‘/’ for slash commands.”	Succinct, colloquial, and reassuring. Teaches core actions through a functional checklist.

17. 16. Brand Voice & Tone in Practice

Mailchimp’s Paired Traits

Mailchimp defines their voice with paired constraints:

FUN but not childish
FUNNY but not goofy
POWERFUL but not complicated
HIP but not alienating
EASY but not simplistic
TRUSTWORTHY but not stodgy
INFORMAL but not sloppy

On Freddie the chimp: “He likes to crack jokes, but when the situation is serious, the funny business is out the window. He smiles, winks, and sometimes high-fives, but he does not talk. Don’t write in his voice.”

The voice/tone distinction: “Our voice doesn’t change much from day to day, but our tone changes all the time. Consider the reader’s state of mind.”

Slack’s Copy Principles

Brand personality: “Creative, professional, thoughtful, respectful, purposeful and curious; we are smart, humble, hardworking and collaborative.”

The voice: “Clear, concise and human, like a friendly, intelligent coworker.” Guiding philosophy: “We are humans, speaking to humans.”

Twilio’s “Ahoy”

Twilio uses “Ahoy” as their developer community greeting across all documentation, blog posts, and developer events. A single word that gives the entire developer experience a nautical personality.

18. 17. Product Naming Conventions

Company	Pattern	Examples	Evolution
Apple	The “i” prefix	iMac (1998), iBook (1999), iPod (2001), iPhone (2007), iPad (2010)	Ken Segall proposed “iMac”: “the ‘i’ meant internet. But it also meant individual, imaginative.” Since Apple Watch (2015), dropped the “i” for all new products — “Apple [Noun]” or standalone names (AirPods, HomePod).
Stripe	Evocative single words	Atlas (incorporation — the titan), Radar (fraud — scanning), Sigma (analytics — summation), Connect, Terminal, Billing, Tax, Identity, Climate	Each name metaphorically describes the function. A mythology of products.
AWS	Descriptive acronyms + CS references	S3 = Simple Storage Service. EC2 = Elastic Compute Cloud. Lambda = lambda calculus. SQS = Simple Queue Service.	Systematic but the sheer volume (200+ services) makes it opaque to outsiders.
Google	Naming chaos	Google Talk (2005) → Hangouts (2013) → Hangouts Meet + Hangouts Chat (2017) → Google Meet + Google Chat (2020) → Hangouts discontinued (2022)	Five names for the same product category in seven years. The canonical example of naming confusion.

19. 18. Documentation as Competitive Advantage

Stripe’s API Docs

Three-column layout: navigation tree (left), explanations (center), live code samples (right). Switch all code samples between Python, Node, Ruby, Go with one click. When logged in, your test API keys are automatically injected into code samples. Stripe Shell lets you make live API calls from the docs page.

“While other APIs document functions and what’s possible, Stripe documents outcomes and shows developers the exact path that 90% of developers take.”

Result: 85% developer satisfaction, significantly higher than PayPal, Square, and Adyen.

Twilio’s Documentation-First Developer Experience

Pioneered automatically generating API reference pages from specifications and providing tested code samples developers can copy, paste, and run. Documentation is embedded in tutorials so developers “get answers quickly without disrupting workflow.” Philosophy: developers “can read less and build more.”

Best README Files on GitHub

The most effective READMEs answer three questions immediately: what (what does this do), why (why should I care), and how (how do I start).

htmx — “high power tools for HTML.” Positions a JavaScript library as an HTML tool. The phrase borrows from hardware language, making the library feel physical.
FastAPI — “FastAPI framework, high performance, easy to learn, fast to code, ready for production.” Five claims separated by commas. Immediate benchmark comparisons and minimal code example.

20. 19. Company Blogs as Strategic Weapons

Company	Strategy	Result	Key Insight
Intercom	Blog as main distribution channel from $1M to $50M ARR. Company-wide contributions — engineering, marketing, sales, finance, product, design, customer support all wrote.	5X qualified traffic from 35K to 220K monthly uniques in 1.5 years using JTBD framework.	Their post “Why cards are the future of the web” still generates hundreds of views weekly years later. They also published books on Jobs-to-be-Done and customer engagement.
HubSpot	Found that 27,000+ people monthly search for “how to use Excel” and wrote a post that ranked #1 for it. Multiple posts per day.	4.5 million monthly readers. Blog generates 20% of all organic leads.	The blog targets educational keywords their audience searches, even if tangentially related to the product.
Cloudflare	Lightweight approval process for technical posts. Philosophy: “the bigger problem is lack of posts or vague, high-level content, not revealing too much.”	Created multiple generations of employees who joined because of a blog post and now write for the blog themselves.	Famous posts: the lava lamp randomness/cryptography piece, and detailed postmortems. An engineer joined specifically because of their 4th-gen servers post.
Buffer	Radical transparency as content. Published all employee salaries with name, role, location, and exact dollar amount, plus the formula.	229% increase in job applications. Public revenue dashboard at buffer.com/metrics.	Publishing exact salaries (not ranges) in 2013 was radical and bridged an HR culture story with a tech trend story.
Stripe Press	Started their own publishing house in 2018. Books, a documentary, a podcast.	Published Nadia Eghbal’s Working in Public, Martin Gurri’s Revolt of the Public, Scaling People.	If Stripe’s growth is limited by the number of successful startups, publishing books that inspire founders is a rational investment.

Dan Luu on Good vs. Bad Corporate Blogs

After interviewing people at companies with compelling blogs (Cloudflare, Heap, Segment) and lame blogs (unnamed), the key difference was the approval process. Good blogs: easy approval, not many sign-offs. Bad blogs: one company’s process took months, with so many iterations that “multiple people vowed to never write another blog post.” At one company, reforming the blogging process required all 14 “stakeholders” to sign off.

21. 20. Changelogs & Release Notes as Content

Linear’s Manifesto: “Startups, Write Changelogs”

“Remember to write about things that are interesting to a human. Don’t include everything you do. Writing about database migrations is not that interesting unless it results in some performance gains or improves the user experience.”

Over 1,000 people follow and interact with Linear’s changelog updates, achieving 10x more engagement than the industry average. Key practices:

Bug fixes go in dropdowns to avoid clutter
Natively embedded videos explain changes
User-focused language: “Your dashboard now loads 2x faster” not “Optimized query performance”

The changelog doubles as recruiting — “most candidates had followed their changelog posts before applying.”

Raycast’s Biweekly Release Notes

Published every two weeks with a focus on brevity (no fluff), feature spotlighting (standout features get dedicated attention), product area prefixing (updates grouped by area), and visual engagement (images and screenshots for key features).

22. 21. Sales Decks & Proposal Writing

Zuora’s “Greatest Sales Deck Ever”

Analyzed by Andy Raskin, whose analysis went viral and became the template for B2B sales narratives across Silicon Valley. Tien Tzuo coined the term “Subscription Economy” before anyone else. The deck follows five elements in order:

Name the Change — an undeniable shift that creates stakes and urgency
Show Winners and Losers — the change will create both
The Promised Land — a new future state, NOT your product
Magic Gifts — your features as tools to overcome obstacles
Evidence — proof you can deliver

The critical insight: “The Promised Land is a new future state, not your product or service.”

23. 22. Customer Service Writing

Apple’s A.P.P.L.E. Framework

Every Apple Store interaction follows a five-step acronym:

Approach with a personalized, warm welcome (use the customer’s first name)
Probe politely to understand all the customer’s needs
Present a solution for the customer to take home today
Listen for and resolve any issues or concerns
End with a fond farewell and an invitation to return

Apple learned its service model from the Ritz-Carlton. The Genius Bar is described as “a loving knockoff of a Ritz-Carlton concierge counter.”

Ritz-Carlton’s Gold Standards

Every employee carries the Credo Card on their person. Motto: “Ladies and Gentlemen serving Ladies and Gentlemen.” Three Steps of Service: (1) warm and sincere greeting using the guest’s name, (2) anticipation and fulfillment of each guest’s needs, (3) fond farewell using the guest’s name.

The $2,000 Rule: every employee is empowered to spend up to $2,000 per incident (not per year) to rescue a guest experience, without seeking supervisor permission.

Zappos’s “Deliver WOW”

Longest customer service call record: 10 hours, 51 minutes (mostly talking about living in Las Vegas, which eventually led to a sale of Ugg boots). A customer who ordered boots for her recently deceased father was told not to bother returning them and received a bouquet of flowers the next day. Customer service emails are identifiably written by a single human — no corporate templates.

24. 23. Incident Reports & Postmortems

GitLab’s Database Deletion (January 31, 2017)

An engineer accidentally ran rm -rf on the primary database instead of the secondary, destroying 300GB of data. Terminated the process a second later, but the damage was done: 5,000 projects, 700 user accounts, and 6 hours of data lost. Recovery took 18 hours.

The real disaster: automated pg_dump backups had never actually run due to misconfiguration, and failure alerts were silently rejected by DMARC email settings. They were saved only because an engineer had taken a manual snapshot 6 hours before for testing. GitLab live-streamed the recovery on YouTube and posted real-time updates. The result was not ridicule but respect — GitLab gained goodwill from the worst outage in their history because of radical transparency.

Cloudflare’s Regex Outage (July 2, 2019)

A single WAF rule with a poorly written regular expression caused catastrophic CPU exhaustion across the entire network for 27 minutes. The offending pattern contained nested wildcards like .*.* that caused exponential backtracking. Fix: switching to re2/Rust regex engines with runtime guarantees, and implementing staged rollouts for WAF rules.

Google SRE Postmortem Template

Structure: Summary (executive overview), Timeline (minute-by-minute “screenplay”), Root Cause (technical and process failures), Action Items (each with an owner, categorized as Investigate, Mitigate, Repair, Detect, or Prevent). Includes a unique section: “Where we got lucky” — identifying risks that could have made the incident worse.

John Allspaw’s Blameless Postmortem Philosophy (Etsy)

“One option is to assume the single cause is incompetence and scream at engineers to make them ‘pay attention!’ or ‘be more careful!’ Another option is to take a hard look at how the accident actually happened, treat the engineers involved with respect, and learn from the event.”

This framing shifted the industry standard from blame to learning.

25. 24. OKR Writing

Andy Grove’s Original Formula (Intel)

“I will [Objective] as measured by [set of Key Results].” Grove’s grading was binary: yes or no, did you meet it?

Google’s Refinement

Maximum 5 objectives per cycle, each with 3–5 measurable key results. Google uses a 0.0–1.0 scale. The “sweet spot” is 0.6–0.7 — consistently achieving 1.0 means goals aren’t ambitious enough.

Key results must be impact-focused: not “Launch Foo 4.1” but “Improve sign-ups by 25%.”

Chrome’s OKR Example

Year	Target	Achieved	Score
2008	20M users	20M	1.0
2009	50M users	38M	0.76
2010	111M users	Exceeded	1.0+

The escalating ambition of each cycle demonstrates the “stretch goal” philosophy in practice.

26. 25. Job Postings as Writing

Stripe’s Mission-Driven Language

Every role opens with: “Help increase the GDP of the internet.”

“We have a staggering amount of work ahead.”

“If your experience doesn’t precisely match the job description, your skills and passion will stand out — especially if your career has taken some extraordinary twists and turns.”

On impact: employees can “point to specific, high-impact things that didn’t exist until you created them.”

27. 26. Terms of Service & Legal Copy

Basecamp / 37signals

Their entire policy set is open-sourced on GitHub under Creative Commons Attribution license. The opening defines terms in plain language:

“When we say ‘Company’, we mean 37signals LLC.”
“When we say ‘Services’, we mean our websites.”
“When we say ‘You’ or ‘your’, we are referring to the people or organizations that own an account.”

“We try to make all our policies as clear, fair, and readable as possible.” Anyone can fork their policies on GitHub and adapt them — hundreds of companies have done so.

Creative Commons’ Three Layers

Every Creative Commons license has three layers:

The Legal Code — the lawyer-readable version
The Commons Deed — the “human-readable” summary with icons
The Machine-Readable Code — metadata for search engines

The Commons Deed is the copywriting innovation. It translates legal terms into sentences like: “You are free to share — copy and redistribute the material in any medium or format” and “You are free to adapt — remix, transform, and build upon the material.”

28. 27. Public Style Guides & Writing Guidelines

Company	Guide	Scope	Notable Detail
Mailchimp	Content Style Guide	Voice, tone, grammar, web, social media, email, legal, accessibility, translation	Open-sourced on GitHub. The most-referenced content style guide in the industry.
Google	Developer Documentation Style Guide	Technical writing: tone, formatting, accessibility, code samples, terminology	The de facto standard for developer documentation across the industry.
Microsoft	Writing Style Guide	Whitepapers, apps, websites, documentation	One of the few complete technical writing guides covering both product and marketing content.
Shopify	Polaris Content Guidelines	Voice, tone, grammar, product terminology for Shopify admin	Part of Shopify’s open-source design system.
Atlassian	Design System Content Guidelines	Values, design principles, voice and tone across Jira, Confluence, Trello	Open-source system used across a multi-product portfolio.
DigitalOcean	Technical Writing Guidelines	Procedural tutorials, conceptual articles, task-specific articles	Single-page, focused, practical — a good template for developer content teams.
Apple	Human Interface Guidelines	Writing and content guidelines for iOS, macOS, and all Apple platforms	Sets the standard for product copy in consumer software.
Intuit	Content Design System	Language advice and content pattern library for TurboTax, QuickBooks, Mint	Goes beyond style into reusable content patterns.

29. 28. Leaked Memos & Legal Discoveries

Document	Company	How It Surfaced	Key Content
Steve Jobs’s “Top 100” Strategy Email	Apple	Court documents	Heralded the “Post PC era,” vowed “Holy War with Google,” promised to “further lock customers into our ecosystem,” warned Apple was “in danger of hanging on to old paradigm too long.” Written one year before his death.
Steve Jobs’s No-Poach Email to Eric Schmidt	Apple / Google	Antitrust lawsuit	Forwarded a Google recruiter’s contact to Schmidt with a terse demand to stop recruiting Apple employees. Led to the Silicon Valley no-poach agreement scandal and a $415 million settlement.
Steve Yegge’s Google Rant	Google	Accidentally posted publicly instead of internally	Praised Amazon’s API mandate while criticizing Google’s platform strategy. Made Bezos’s API mandate public for the first time.
Sam Altman’s Superintelligence Memo	OpenAI	Leaked to press	Warned that OpenAI’s “long-term survival depends on doubling down on the pursuit of superintelligence.” Projected agents doing “real cognitive work” by 2026 and “novel insights” by 2027.
Microsoft Antitrust Emails (2001)	Microsoft	DOJ antitrust trial	Internal emails revealing competitive strategy against Netscape, Java, and Linux. One of the largest troves of internal corporate communications ever made public.
Epic vs. Apple Emails	Apple / Epic Games	Court discovery	Internal Apple emails discussing App Store economics, competition concerns, and strategic decisions around developer relations.

30. 29. VC Investment Memos & Portfolio Letters

Sequoia Capital’s “RIP Good Times” (October 2008)

56-slide presentation shared with portfolio founders. “Cuts are a must” and “Get Real or Go Home.” Became legendary in VC circles. Sequoia repeated the format with “Coronavirus: The Black Swan of 2020” in March 2020, and again with a 52-page deck in 2022. Three crises, three decks, one franchise.

Roelof Botha’s YouTube Investment Memo (2005)

Internal Sequoia memo proposing seed investment in YouTube. Argued YouTube could become “the primary outlet of user-generated video content on the Internet.” One of the only public VC investment memos from a top firm — surfaced as testimony in the Viacom vs. YouTube/Google case. YouTube was acquired for $1.65B. Now worth $300B+.

31. 30. Public Collections & Archives

Collection	URL	Contents
Sriram Krishnan’s Memos	sriramk.com/memos	The best single collection. Steve Jobs ebook negotiations, Schultz’s Starbucks memo, Katzenberg’s Disney memo, YouTube investment memo, Gates’s Tidal Wave, Garlinghouse’s Peanut Butter Manifesto, McElroy’s P&G memo that invented brand management.
Internal Tech Emails	techemails.com	Substack covering internal tech industry emails from public records and court cases. Microsoft antitrust emails, Jobs/Schmidt exchanges, Musk’s OpenAI emails, Epic/Fortnite discovery.
awesome-memos (GitHub)	github.com/anrosent/awesome-memos	Curated GitHub collection of memos from celebrated businesspeople.
Will Lethain’s “Great Memos”	lethain.com	Commentary and analysis of the best business memos, building on Krishnan’s collection.
Alexander Jarvis	alexanderjarvis.com	Detailed analysis of famous memos: Yahoo Peanut Butter Manifesto, Starbucks Commoditization, Jobs’s secret meeting agenda, Sequoia’s YouTube memo.
NFx Founders’ List Podcast	podcast.nfx.com	Audio readings and analysis of famous founder letters: Chesky’s culture letter, Garlinghouse’s Yahoo memo, Google’s IPO letter.
CultureGene	culturegene.ai	Curated collection of the best public company culture decks: Netflix, LinkedIn, HubSpot, Hootsuite, Valve, Patreon, and others.
Berkshire Hathaway Letters	berkshirehathaway.com	60 years of Warren Buffett’s shareholder letters. The complete archive, free.
designdocs.dev	designdocs.dev	Over 1,000 design doc examples and templates from 40+ leading engineering organizations.

32. 31. Lessons: What Great Business Writing Looks Like

Patterns that emerge across every document in this collection:

Structure

Lead with the conclusion. Bezos’s API mandate starts with the rule, not the reasoning. Gates’s Tidal Wave opens with “the Internet is a tidal wave.” Garlinghouse opens with “I hate peanut butter.”
One idea per document. The best memos have a single thesis. Schultz: Starbucks is being commoditized. Armstrong: Coinbase is mission-focused. Musk: communication should flow freely.
Specific over abstract. “From less than 1,000 stores to 13,000 stores” beats “we grew rapidly.” Numbers, names, and dates make writing credible.

Tone

Write for a person, not an audience. Buffett writes to his sister. Chesky writes to “you.” The Hustle writes “to our really smart friends.” The best corporate writing doesn’t sound corporate.
Candor over diplomacy. Garlinghouse: “I hate peanut butter.” Khosrowshahi: the old value was “used as an excuse for being an asshole.” Lütke: “if you’re not climbing, you’re sliding.”
Acknowledge reality. Chesky’s layoff letter works because it doesn’t pretend the situation is okay. Schultz’s memo works because the founder admits the company he built went wrong. Buffer’s breach email works because they disclosed within an hour.

Copy

Brevity wins. The most memorable lines are 3–7 words: “Be less busy,” “Develop. Preview. Ship.,” “Don’t be evil,” “1,000 songs in your pocket.”
Feelings over features. Slack sells being less busy. Superhuman sells speed as an experience. Linear sells enjoyment. None of them lead with a feature list.
Personality in the margins. The best brands show up in places nobody expects: loading screens (Slack), error pages (GitHub, Lego, Spotify), send confirmations (Mailchimp), and terms of service (Basecamp).
Plain language is a competitive advantage. Basecamp open-sourcing legal policies, Creative Commons creating “human-readable deeds,” Stripe writing error messages for end users — all treat clarity as a product feature.

Impact

Great memos create action, not agreement. Bezos’s API mandate ends with “anyone who doesn’t do this will be fired.” Armstrong offers severance to dissenters. The best memos don’t seek consensus — they declare direction.
Writing forces thinking. Amazon banned PowerPoint because slides let you hide fuzzy thinking behind bullet points. Stripe requires pre-meeting memos because real-time brainstorming rewards charisma, not quality of thought. Intercom limits PRDs to one page because “the longer the doc, the less it gets read.”
The medium is the message. Companies that write well think well. Amazon, Stripe, Basecamp, and GitLab all use writing as a competitive advantage — not because writing itself is magic, but because the discipline of writing forces the discipline of thinking.
Naming is positioning. Apple’s “i” prefix created a product language. Stripe’s single-word metaphors create a mythology. Google’s constant renaming creates confusion. The name is the first piece of copy a user encounters.