Your competitor just got acquired. Now what?

The press release goes out at 9am. By 9:15 someone in sales has forwarded it to the whole company with the subject line "thoughts?" and by 9:40 there are eleven replies, none of which contain a fact.

That reflex is understandable and mostly useless. An acquisition announcement is a marketing document. It tells you almost nothing about what the merged company will do. But the week around it is unusually rich, because two organisations are quietly reconciling their public surfaces in real time — and neither has finished sanding down the edges yet. Pages get rewritten. Job posts vanish. Docs sprout new brand names. Most of that evidence is gone or normalised within a month.

So the playbook below is time-boxed on purpose. Five working days, then stop.

Day 1: Freeze the evidence before it moves

Before you form a single opinion, capture the current state. Everything you want to compare against in six weeks is being edited right now.

• Save the pricing page — full page, not a screenshot of the tiers. Plan names, seat minimums, and the small print under the enterprise column all move first.
• Pull the current careers page into a file. Roles, locations, team names, and the count.
• Archive the changelog and status page as they stand today.
• Note the exact wording of the homepage headline and the sub-headline. This is the sentence most likely to change and least likely to be noticed changing.
• Record the trust/security page: subprocessors, certifications, data residency claims.

You are not analysing yet. You are creating the "before" half of a diff. Teams routinely skip this and then spend the following quarter arguing from memory about what a competitor's pricing page used to say — a problem worth avoiding, as you can't diff against your memory covers at length.

Day 2: Read the acquirer, not the acquired

The acquired company's public surfaces will keep saying reassuring things for months. The acquirer's surfaces are where the actual plan leaks, because acquirers have to explain themselves to their own investors, employees and customers.

• Read the acquirer's investor page and any earnings commentary that mentions the deal. The framing there — "expands our platform into X" versus "adds a team of N engineers" — is the single clearest tell for product versus acqui-hire.
• Check whether the acquirer's own pricing page has gained a new line item, add-on, or bundled tier. That happens fast when the intent is packaging.
• Look at the acquirer's docs and API reference for new namespaces. Integrations often appear in reference docs weeks before anything is announced.
• Compare positioning language across both homepages. If the acquired product's category word starts appearing in the acquirer's copy, the plan is absorption, not independence.

The gap between "will continue to operate independently" and what the acquirer's own surfaces imply is the most informative thing you will find all week.

Day 3: Map who is actually in play

Acquisitions create a short window where a competitor's customers are genuinely reconsidering — not because the product got worse, but because procurement, security review, and roadmap confidence all reset at once.

• Filter your CRM for closed-lost deals against this competitor in the last 18 months. That list, not your general pipeline, is your outreach set.
• Check the competitor's public community, forum, or subreddit for the specific complaint shape: pricing uncertainty, data handling under new ownership, or a named feature people fear will be sunset.
• Look at G2/Capterra reviews filed in the two weeks after the announcement. Volume matters less than which concern repeats.
• Identify any integration partners that now compete with the acquirer. Those partnerships are the first casualties and the easiest conversations you will have all quarter.

Be honest about scale here. If a competitor has 40 enterprise logos, this is a list of maybe six real conversations, not a campaign.

Day 4: Rewrite exactly one battle card

Resist the urge to update everything. Sales needs one page, and it needs to answer the three questions they are actually getting asked.

• What happens to my contract and my price at renewal? (Answer with what the surfaces show, and say "unknown" where it is unknown.)
• Is the product still being developed? Point at changelog cadence, not sentiment.
• Who owns my data now? Point at the subprocessor list and the trust page, with the date you read them.

Then add the one line most battle cards omit: what would make this card wrong. If the merged company ships a credible roadmap update in six weeks, your "uncertainty" angle expires and continuing to use it makes your team look uninformed. Cards that never state their own expiry date are the ones that quietly go stale and get ignored.

Day 5: Set the watch, then stop looking

The acquisition itself is not the story. The integration is, and it plays out over two to four quarters — which is far longer than anyone's attention span for manual checking.

Decide now what you want to be told about, and be specific:

• Pricing page changes of any kind, including plan renames.
• Careers page: role removals matter more than additions here. A disappearing "Senior Backend Engineer, Platform" post says more than five new sales hires.
• Changelog cadence dropping below its pre-deal baseline for two consecutive months.
• Any change to the subprocessor list or trust page.
• Domain-level changes: redirects, a docs subdomain moving, or the acquired product's site starting to serve the acquirer's nav.

This is the part where tooling earns its keep, and it is worth being precise about what tooling actually does. Seeto monitors public surfaces continuously and surfaces the diffs as discrete change events, so a plan rename or a quietly removed job post shows up as a dated item instead of something you happen to notice in November. It does not read the earnings call for you, and it will not tell you what the change means — that judgment is Day 2 work, and it stays yours. What it removes is the failure mode where the integration proceeds in public for eight months and nobody on your side has a record of it.

The two-week check

Come back once, fourteen days out, and answer one question: did anything on the acquirer's surfaces contradict the official "nothing changes" messaging? If yes, that contradiction is your positioning for the next two quarters. If no, close the tab and let the watch do the work. Both outcomes are fine. What is not fine is a Slack thread that runs for three weeks and produces no artifact anyone can cite in a deal.