How to Do a Competitor SWOT Analysis (With Examples)

What a competitor SWOT actually tells you (and what it doesn't)

SWOT (Strengths, Weaknesses, Opportunities, Threats) maps where a competitor is strong and weak today, and what's likely to help or hurt them going forward. The first two quadrants are internal to the competitor. The second two are external — the market context they're operating in.

What SWOT does well: forces you to look at the full picture instead of fixating on one feature or price point. It surfaces the gaps you can attack and the threats you'd otherwise miss.

What SWOT doesn't do: tell you what to do next. It's a snapshot, not a strategy. The output of a SWOT should always be one or two decisions per quadrant, not a tidy worksheet that lives in a drive folder.

The four quadrants — what goes in each

Each quadrant captures a different lens. Most SWOT documents put one or two bullets in each and call it done. A useful SWOT puts four to six evidence-backed entries in each, with a source link for every claim.

• Strengths (internal, positive): What the competitor does well that the market values. Strong brand recognition. Integrations you don't have. Fast onboarding. Sales team with deep industry expertise. Generous free tier.
• Weaknesses (internal, negative): Where they fall short. Pricing complexity. Poor customer support reviews. Slow feature shipping cadence. Dated UI. Lock-in concerns from existing customers.
• Opportunities (external, positive): Market shifts they could capitalize on. New regulation creating demand. A competitor of theirs going under. AI commoditizing a feature they used to charge for.
• Threats (external, negative): Things that could damage them. Well-funded new entrant. Customer churn from a price hike. Security incident. Key personnel departures. Dependency on a partner who's pivoting.

Where to find the data (without guessing)

Strengths and weaknesses come from the same surfaces your prospects look at — pricing page, feature pages, customer reviews on G2 and Capterra, app store ratings, support response time on social, public roadmap if they have one, demo videos.

Opportunities and threats require broader context — industry news, funding announcements, hiring patterns on LinkedIn (what they're hiring for tells you what they're betting on), regulatory filings, parent company news.

The mistake most teams make: doing this once, drawing conclusions, then never refreshing. Pricing pages change. Reviews come in. Hiring shifts. A SWOT done in January is partially wrong by March — and badly wrong by July.

Example walkthrough — fictional competitor “AcmeFlow”

Concrete makes abstract useful. Here's what a real SWOT looks like for a fictional B2B SaaS competitor “AcmeFlow” — enterprise competitive intelligence platform, $1,500/mo entry, 4-week implementation.

• Strengths: Enterprise sales motion locked in. 200+ logos on landing page. Deep Salesforce integration. Trained CSMs assigned per account. Their $1,500/mo entry pricing keeps small competitors out of enterprise deals.
• Weaknesses: Four-week implementation. Reviews on G2 frequently mention “overkill” for SMBs. No self-serve trial. Admin UI dates from 2019. English-only support. G2 review velocity dropped from 12/month to 4/month over the last quarter.
• Opportunities: New SOC 2 requirement in their target industry creating short-term demand. One of their two main competitors raised prices 40% last month.
• Threats: Their largest investor is exiting. Two senior engineers recently posted “open to work” on LinkedIn. A well-funded YC company is launching in the same niche this quarter at 10x cheaper.

Read that SWOT and you can write your positioning against AcmeFlow in two minutes: lean hard into self-serve trial, faster implementation, SMB pricing. Their slowing review velocity and personnel turnover are leading indicators — pay attention over the next 90 days.

How to act on the SWOT

This is the part most teams skip. For each quadrant, write down one or two decisions you'll make in the next 30 days.

• From their strengths: “Don't try to win on Salesforce integration. Win on time-to-value.” Update sales deck.
• From their weaknesses: “Build messaging around 5-minute setup. Reference their 4-week implementation indirectly in comparison page.”
• From their opportunities: “If we don't move on the SOC 2 angle in 60 days, they'll own it. Brief team.”
• From their threats: “Monitor their hiring closely. If they cut engineers, expect ship velocity to drop further — opportunity to ship past them on roadmap.”

A SWOT that doesn't produce decisions like these is wasted work.

Why static SWOTs decay (and what to do instead)

Competitors change pricing weekly. Ship features weekly. Hire and fire. Get press. Lose deals. A SWOT is a snapshot. The half-life of a snapshot in a fast-moving market is maybe 60 days.

The fix is not “do a SWOT every quarter.” It's “instrument the inputs so the SWOT updates itself.” Pricing pages, changelog and blog posts, review velocity, hiring posts, news mentions — these are all monitorable. If you can detect changes in any of them, you can re-evaluate the relevant quadrant in real time instead of catching up six weeks later.

How OSA Radar turns a static SWOT into a live one

OSA Radar monitors competitor pricing pages, feature and changelog updates, G2 review activity, hiring signals via news, and messaging shifts on landing pages. Every week you get a digest with only what changed. When a competitor's pricing drops, you know in days, not months. When their G2 rating slides, you know the customer-side weakness is widening. When they post a hiring spike for sales engineers, you know they're pivoting to enterprise.

You still own the strategic decisions. We just keep the SWOT inputs fresh so you're not deciding from a stale snapshot.