Arc · Go-to-market · Senior · 45 to 60 minutes
How should Arc go to market?
Arc is a desktop web browser from The Browser Company that redesigns tabs, navigation, and workflows for people who spend much of their day on the web. Answer this product management case and get it graded line by line against a weighted rubric.
- Segmentation
- Positioning
- GTM strategy
- Product sense
- Metrics
The situation
You are the PM leading go-to-market planning for Arc ahead of a broader public push. The product is polished enough to attract attention, but it is not a conventional browser. Its interface and workflows break from long learned patterns like horizontal tabs, and even strong onboarding will not remove all switching friction. Internally, the team believes there is a chance to rethink the browser as something more active and opinionated, but externally the market is dominated by Chrome, whose scale, defaults, and business model make direct head to head competition unrealistic. Josh Miller asks you for a recommendation: who should Arc win first, how should it be positioned, and what launch motion gives it the best chance to grow without becoming just another niche browser experiment. The tension is that a mass market pitch could drive awareness but trigger rejection, while a narrow pitch could build love but limit early reach. The team is also debating whether support should stay a standard reactive function or become a strategic part of acquisition, feedback, and advocacy. Assume the team can fund only one primary GTM motion for the next 2 quarters.
What to produce
A 1 to 2 page go-to-market strategy memo.
Your answer must
- Recommend a primary target segment for the next 2 quarters and explain why that segment is a better starting point than mainstream browser users.
- Define Arc's positioning versus Chrome and other browsers, including the category story you would tell and the core message you would avoid.
- Propose the first 2 go-to-market motions to run, in sequence, and explain how product onboarding, community, and support should or should not be part of the plan.
- Specify 4 to 6 success metrics, including at least 2 leading indicators that go beyond raw installs or downloads.
- Identify the top 3 risks or second-order effects of your plan, with a mitigation for each.
Constraints
- Chrome is entrenched, and most users are satisfied with familiar browser patterns.
- Arc's differentiated UI creates a real learning curve and switching cost.
- Do not assume a paid acquisition budget large enough to compete with major consumer browsers.
- Your plan should work even if incumbents can copy isolated features faster than they can copy Arc's full product philosophy.
Format
Use short sections with headers. A simple table for segment choice, GTM motions, and metrics is welcome.
How Arc actually played it
Explores how The Browser Company positioned Arc against Chrome, with membership-level support and an approach to growth and product.
- Rethink a default product category
- High-touch support can build advocates
- Growth and product choices align
Built from How Arc Grows: Building The New Window Into The Internet by Jaryd Hermann (How They Grow).
Related case studies
- Linear GTM for 1,000 Plus Engineer OrgsLinear · Go-to-market · Mid
- GTM plan for team routing to existing Calendly usersCalendly · Go-to-market · Entry
- Razorpay's Next SMB Market Beyond MalaysiaRazorpay · Go-to-market · Senior
- Zoom AI Premium Packaging and PricingZoom · Go-to-market · Senior
- Grow Headspace sales to employersHeadspace · Go-to-market · Mid
- How should Slack launch to teams?Slack · Go-to-market · Mid