Spotting an acquirer’s kill date: Arc’s shutdown

A founder deciding whether to sell into an acquirer can read a product’s future in the quiet parts of a roadmap. The kill date is often set before the public announcement.

Arc, a browser made by The Browser Company, will end on December 22, 2026. The Browser Company cited rising security costs in the age of AI as the reason for the Arc sunset. Atlassian acquired The Browser Company for $610 million in 2025. The Browser Company ceased building new Arc features in 2025. That sequence matters for founders weighing a sale.

Maintenance signals set the kill date

A browser sunset is easier to read than a product roadmap. A pivot to a successor is the acquirer’s cleaner story. The first sign is usually a feature freeze; the second, a staffing shift; the third, a story about a successor.

Founders often miss these signals because they are looking for a decision. The decision is already being made in release notes, support docs, and budget reviews.

The documents are not secret. Release notes reveal what shipped. Support pages show what users can still do. Job postings show where engineering attention is going. A founder can read all three in an afternoon. The visible pattern is the real evidence.

A product can still be loved while it is being drained. The drain shows up as fewer new users, thinner features, and a migration path that assumes departure. The emotional attachment to the product is not evidence that the product is still strategic.

The ledger turns a shutdown into a checklist

Each item below is a one-minute test. Run it against your own product, a target, or a company you are about to sell into. The test asks whether the product is being built, staffed, explained, costed, or exited.

• Feature freeze. Ask whether new user-facing features stopped after the deal closed. A roadmap that only patches bugs is a maintenance signal.
• Engineering reallocation. Check whether staff, budget, or security work moved to another product. If the team is no longer owned by the product, the product is no longer owned by the team.
• Successor framing. Listen for language that positions the product as a bridge to something else. A successor is a cleaner story for an acquirer than a legacy product.
• Maintenance-cost rationale. Test whether the stated reason is cost, security, or support burden. A cost rationale is a useful sentence for a board, not a roadmap.
• Migration and deletion terms. Read the exit path: sign-in, sync, data removal, and final availability. If users must move before the product stops, the product is already on a clock.

The list works because it follows the order a product is de-prioritized: build, staff, story, cost, exit. Each step is visible before the final date. A founder who can name the step can ask the right question.

The timeline is the clearest lesson

Arc stopped allowing creation of new accounts on October 22, 2026. On November 23, 2026, Arc Search on iOS and Android will drop AI capabilities, and users will lose account sign-in and tab synchronization. On December 22, 2026, Arc will become unavailable on macOS and Windows, Arc accounts will be shut down, and personal data will be removed within 30 days.

The first cut is access, the second is capability, the third is data. Each step narrows the product’s role.

Ask whether the acquirer’s strategy depends on a successor or its cost model depends on security. If so, the legacy product may be a bridge or a liability.

Founders should write the ledger before signing

Write the kill-date ledger before the term sheet. Put the dates, owners, and migration terms in one page. If the acquirer cannot answer them, that is the first signal.

Before signing, ask who owns the roadmap after closing, who owns security, support, and data deletion, and what happens to users who do not migrate. The answers should be concrete, not reassuring.

A sale changes the product’s owner, budget, and story. The founder who reads the ledger early can negotiate for a better exit path, a clearer migration, or a better buyer.