LLenny's Podcast
← All episodes
Josh Miller (CEO)19 March 2023

Competing with giants: An inside look at how The Browser Company builds product

9Frameworks
13Insights

Frameworks in this episode

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Hot Take· 4

Hot Take11:30

Optimize for Feelings, Not Just Metrics

Josh argues that Silicon Valley's obsession with graphs and numbers leaves a lot on the table. At The Browser Company they talk instead about 'optimizing feelings' — deciding what emotion (joy, speed, focus) a feature should evoke. He points to Nike, Disney, and Apple as brands whose founders were designing for feeling, not dashboards, at the moment of creation.

  • Metrics are quantitative and objective but miss a lot of what makes products beloved
  • Ask what feeling the software should evoke before you build the feature
  • Walt Disney, Phil Knight, and Steve Jobs were optimizing for feeling, not numbers
  • Numbers are still useful to keep yourself honest about whether you're hitting the aim

what we do at the browser companies we talk about optimizing feelings how does the software how do we want to make someone feel on…

Josh Miller · 11:30

what do you think Walt Disney was optimizing for when he was crafting Disneyland what do you think Phil Knight was thinking about when he…

Josh Miller · 13:00
#product#metrics#philosophy#design
Hot Take31:00

Interviews Designed to Convince People NOT to Join

Josh reframes the company's real product as its team. In interviews he doesn't pitch — he invites questions and is brutally honest that most people shouldn't want to work there. That intentionality, plus an ambitious prompt and genuine empowerment, is how they've hired senior leaders (including a Chrome co-creator, a Vimeo SVP, and a Slack design SVP) as individual contributors.

  • He views the product as the team, not Arc itself
  • Interviews aim to convince people not to join; no pitching, radical honesty
  • Hired Darren (co-created Chrome, ran it 16 years) as an IC
  • Also hired a former SVP of product at Vimeo and a former SVP of design at Slack as ICs

I view our product as our team

Josh Miller · 31:00

if I have an interview with someone I don't pitch them I say what do you want to ask me anything you want I'll be…

Josh Miller · 32:00
#hiring#team#culture#recruiting
Hot Take41:00

Building in Public as Radical Trust-Building

Josh explains why a browser company films its own board meetings and shares work publicly: a browser holds your most sensitive data, and tech has broken users' trust repeatedly. His bet is that a great privacy policy isn't enough — people trust people, so letting users get to know the humans behind Arc is a deliberate 'radical trust-building' experiment, even at the risk of looking self-important.

  • A browser holds your most sensitive personal and professional data — trust is the product
  • Culturally, users have lost trust in tech brands over the last 5-10 years
  • A privacy policy alone won't earn trust; people trust people they feel they know
  • He worries the approach could tip into 'internet celebrity' and wants to be told if it does

building in public showing you our meetings uncomfortably so is an act in if we were them why should they trust us

Josh Miller · 42:00
#trust#transparency#brand#privacy
Hot Take52:30

No Product Managers — Hire 'Mutts'

The Browser Company has no PM org; instead the PM role floats to whoever fits a given project — an infra engineer on a performance project, a membership person on a member-facing one. Josh, a former Facebook PM himself, wants multi-disciplinary people who identify as 'I make things.' He openly predicts they'll eventually hire PMs anyway, citing Snapchat and Stripe.

  • No PM org; the PM role is picked per project, not per person
  • They hire 'mutts' — multi-disciplinary people who say 'I make things'
  • Example: Rebecca (data scientist, MIT PhD, ex-Stripe engineer) effectively plays PM
  • Josh predicts they'll likely add PMs eventually, as Snapchat and Stripe did

I don't think we will have a PM org or a PM role because again we believe depending on the if you look if you…

Josh Miller · 53:30
#product-management#hiring#org-design#team

Explainer· 4

Explainer06:00

D5/D7: The One Metric Arc Obsesses Over

Despite championing feelings, Arc still tracks one metric religiously: D5/D7 — how many people use Arc at least five days out of seven. Josh explains it captures retention, engagement, and growth in a single un-gameable number, and that they watch week-over-week growth rate rather than absolute counts.

  • D5/D7 = people who turn to Arc at least five days a week (others call it L5/L7)
  • It bundles retention, engagement, and growth and can't be gamed
  • They track week-over-week growth rate, not absolute user numbers
  • Grew 10%+ every week for about eight months; D5/D7 retention sits low-30s to low-40s by cohort

we call it D5 D7 a lot of other companies call it L5 L7 but the human explanation for that is how many people turn…

Josh Miller · 06:00
#metrics#retention#growth#product
Explainer46:30

The 'Odd Teams': Membership and Storytelling

Instead of standard startup orgs, The Browser Company builds teams from first principles. 'Membership' owns the entire relationship with a user full-stack — collapsing support, success, and user research into one ongoing relationship. 'Storytelling' owns the relationship with everyone they don't yet serve — collapsing PR, investor relations, and marketing into telling the company's story.

  • Membership owns the user relationship from first touch onward, replacing support/success/research silos
  • Storytelling owns everyone not yet served — press, investors, marketing as one function
  • Teams are designed by asking 'what could be' and the most direct way to manifest it
  • Josh concedes these unconventional orgs 'break down in 18 ways' as you scale

we start with first principles asking what could be what are we really trying to do here and what is the most direct way to…

Josh Miller · 49:30
#org-design#team#first-principles#culture
Explainer1:10:30

Why a Browser Was the Perfect Category to Pick

Josh reveals the strategic logic behind choosing browsers. The category is uniquely universal-consumer, a commodity (near-identical chromium clones), and hugely lucrative. In a commodity market, you win on emotional connection and brand — which happens to be exactly what The Browser Company is built to do. He frames 'obsess over experience' not as anti-revenue but as the practical way to win this specific market.

  • Browsers are one of the most universal consumer products, used across every generation
  • They're commodities — near-identical chromium clones — yet extremely high-margin
  • In a commodity market you win on emotional connection and brand, not features
  • Focusing on brand and experience IS the growth-and-revenue strategy, not a trade-off against it

we have a product that everyone in the world uses where they're all identical essentially interchangeable commodities and if you can get people to use…

Josh Miller · 1:11:00

we in fact picked a category of software we're focusing on brand and user experience is how you get growth and revenue

Josh Miller · 1:12:30
#strategy#market#brand#product
Explainer1:16:00

The 'Internet Computer' Vision Behind Arc

Josh lays out the company's real ambition: not a browser but an 'internet computer.' As everything — apps, files, photos — moves to the cloud, hardware becomes an empty shell and your true computer lives on the internet. Arc aims to be to the web browser what the iPhone was to the cell phone, and eventually a development platform more valuable than the first-party product itself.

  • Everything is moving to the cloud; your files are already URLs, not local objects
  • Hardware is commoditizing into empty vessels; the real computer lives on the internet
  • Arc aims to be the interface to that internet computer — 'the iPhone for the internet'
  • The long-term value is Arc as a development platform, not the browser itself

what we are building at the browser company is an internet computer

Josh Miller · 1:19:00

we want to be to the web browser what the iPhone was to the cell phone

Josh Miller · 1:19:30
#vision#strategy#cloud#platform

Story· 2

Story13:30

What Facebook's Metrics Missed About Snapchat

Josh recalls Facebook debating the Snapchat threat by tracking an acronym seared into his memory — OBPS (posts per week). He argues the right question was whether people felt closer to friends and family, which is what Snapchat actually got right by designing for something human rather than a composer-open count.

  • Facebook measured its Snapchat response via OBPS — shares/posts per week
  • The better question was whether people felt closer to friends and family
  • Snapchat succeeded by chasing a human feeling, not a composer-open count
  • Use metrics to stay honest, but don't let them define what you're building

I think that's what Snapchat got so right they weren't obsessing about something like how many people put an image into the composer and hit…

Josh Miller · 14:30
#metrics#facebook#snapchat#product
Story23:30

Company Values as a Mirror: The Road Trips Essay

Josh admits he hated corporate values and resisted them for two years. The unlock came when he noticed the team already shared organic traits; they interviewed everyone one-by-one and wrote the values back as a mirror. Rather than a landing page of titles, they published an essay called 'notes on road trips' — a semi-fictional story that carries the values without feeling like propaganda.

  • He resisted corporate values for ~2 years as 'fortune cookie' propaganda
  • Values emerged organically before anyone named them
  • They interviewed the whole team one-by-one; nearly every value is a team member's own words
  • Published as an essay, 'notes on road trips', instead of a values landing page — took ~3 months

the secret is I hate corporate values I've never resonated with them

Josh Miller · 23:30

let's write a manual for how to take a road trip so we wrote an essay called notes on road trips

Josh Miller · 25:30
#culture#values#team#storytelling

Tool· 1

Tool1:14:00

Tuple: The Tool Josh Can't Stop Recommending

In the lightning round and mid-conversation, Josh repeatedly plugs Tuple. Nominally a pair-programming tool that lives in your menu bar, he says the real use is talking to a colleague fast, and it delivers the best audio quality he's ever experienced in a communication tool — better than Zoom — wrapped in a beautifully simple design.

  • Tuple is ostensibly a pair-programming tool that lives in the menu bar
  • Josh uses it as the fastest way to talk to a colleague, not for pairing
  • He rates its audio quality above Zoom
  • Beautiful, simple design is part of why it wins for him

it is the best audio quality I have ever experienced in a communication tool better than Zoom

Josh Miller · 1:14:30
#tools#software#collaboration#recommendation

Takeaway· 2

Takeaway37:00

Hiring Someone Is a Product Launch

Because the team is the product, The Browser Company celebrates every hire and every shipped feature publicly — naming the individuals who did the work. Josh contrasts this with Silicon Valley's CEO hero-worship and insists Arc's magic accrues to the makers, not him. It creates a reinforcing cycle where great people feel genuinely wanted and recognized.

  • Announcing a new hire is treated as a product launch
  • Shipped features credit the specific people who built them, publicly
  • Deliberate rejection of CEO hero-worship — 'I don't make Arc'
  • Public recognition becomes a recruiting flywheel

when our first designer joins we want to tell everyone about it that's a product launch that is the product launch

Josh Miller · 37:00
#culture#hiring#recognition#team
Takeaway1:05:30

Give Things a Made-Up Name to Shed Assumptions

One tactical trick Josh recommends: rename teams, roles, and features to escape inherited baggage. Calling something a 'browser history feature' means everyone already knows what it should be — the downside of a shared name. He cites Airbnb briefly calling PMs 'producers' to force intentional thinking about the role, and uses invented names like 'storytelling team' to get to true first principles.

  • A familiar name imports preconceived notions of what a thing must be
  • Made-up names force first-principles thinking about the actual goal
  • Airbnb once called PMs 'producers' to signal producing beautiful experiences
  • It's a low-risk, two-way-door experiment — revert if it doesn't work

when you give something a new name it sheds a lot of preconceived notions

Josh Miller · 1:05:30
#product#naming#first-principles#tactics