How The Browser Company builds product by optimising for feelings

Executive overview

Most software teams optimise for metrics — graphs, DAUs, retention curves. The Browser Company deliberately optimises for feelings instead, asking how they want users to feel on the other side of the software.

This isn't romantic: in a commoditised, universal category like browsers, emotional connection is the rational winning strategy. The framework threads through hiring, values, team naming, and shipping cadence — all reinforcing a culture of heartfelt intensity and beginner's mind.

Choosing a category where craft is the moat makes "feelings over metrics" a business strategy, not an ideology.

Metrics philosophy

• Single north-star metric: D5 retention — how many people use Arc at least five days a week
• D5 cohort retention sits in the low-to-mid 30s to low 40s; improving cohort-over-cohort matters more than the absolute number
• Week-over-week growth rate tracked instead of absolute user count
• No growth team; no growth projects — surprise and delight drives word-of-mouth organically
• Metrics are a honesty tool, not a creation tool: use them to verify, not to direct

Optimising for feelings in practice

• At the start of any project, the question is: what do we want this person to feel?
• For the Peek feature (hover-to-preview links), the target feeling was "airy, effortless, light" — not a formal PRD with emotion columns
• Discussion-based at small scale; more formalisation expected as the team grows
• Snapchat succeeded by asking "do people feel closer to friends?" not "how many times did they open the composer?"
• Feeling the right emotion naturally drives the metric — joy and surprise lead to sharing

Company values

• Values emerged organically from year-one check-ins; every phrase came from the team, not the founders
• Published as an essay, "Notes on Road Trips," rather than a corporate values page — to avoid "fortune cookie" propaganda
• Core values:
  1. Heartfelt intensity — show up with fire in your belly; this trumps everything else
  2. Assume you don't know — beginner's mind even for experts; bias to action
  3. Start by asking what could be — push for maximum ambition before scoping down
  4. You're on the hook for the team — collective accountability
  5. Make them feel something — the through-line of all work

Hiring

• Mission of the company is built backwards from the people they want to attract, not from the product
• Goal of every interview: convince the candidate not to join — radical honesty, no pitching
• Senior ICs joining as ICs (Darren Jones, ex-Chrome co-creator; Peter Vidani, SVP Design at Slack; Tara, SVP Product at Vimeo) signal that career-defining work is the draw
• New hires celebrated publicly with personal detail — hiring is treated as a product launch
• Credit flows to makers publicly, not to the CEO; counters Silicon Valley hero-worship
• Deliberate hiring of radically different archetypes on each team to prevent homogeneity

Building in public

• Cameras in board meetings, project retrospectives, and design reviews shared publicly
• Framed as "radical trust building," not radical transparency — the goal is to be known as humans
• Risk acknowledged: gravitational pull toward CEO-centrism in public storytelling
• Trust in tech has eroded culturally; showing imperfections is the antidote to earned distrust
• The podcasting medium itself was an inspiration — parasocial familiarity builds real trust

Unconventional team structures

• Membership team — owns the full member relationship from first touch to last: support, bugs, research, and feedback loops, treated as one continuous relationship
• Storytelling team — three people (editorial, strategy, film) covering all external narrative: marketing, PR, investor comms, content; no functional siloing
• No PM org — "PM" is a verb, not a role; the right person to lead a project depends on the project (engineer for performance work, membership lead for user-facing features)
• Naming teams unusually strips preconceived notions and forces first-principles thinking about purpose

Why craft is the right strategy for browsers

• Browsers are universal: one of the few products used by parents, teenagers, and professionals alike
• Browsers are commodities: nearly all run on Chromium with minor differences
• Browsers are highly lucrative: low marginal cost, owned by Google, Apple, Microsoft
• Win condition: emotional connection and brand preference in a commodity market — craft is not romantic, it is capitalistic
• Contrast: cybersecurity software sold to government agencies has completely different win conditions; this approach doesn't universalise

The internet computer vision

• Everything in computing is moving to the web: apps, files, photos — all URLs
• Hardware is becoming an empty vessel; the real "computer" lives on the internet
• Arc's ambition: be to the web browser what the iPhone was to the cell phone — a new class of device, not just a better browser
• The web is the best development platform (cross-platform, free, open, no 30% tax), but incumbents have perverse incentives to keep it less immersive than native apps
• Google wants pages indexed, not immersive extensions; Apple wants App Store revenue, not web apps
• Long-term bet: Arc as a developer platform on top of the open web — the platform opportunity is larger than the browser itself