/swot-analysis

Evidence-Cited SWOT — Worked Example

All companies, products, URLs, and figures are fictional. This example uses the same scenario as the chain examples (market-landscape-scan → battle-card-builder): Fieldlight, a scheduling tool for trades businesses, is expanding into field service management (FSM) and needs depth on Wrenchline, the incumbent. Because the June snapshot and July watch report are in session, the skill synthesized instead of re-searching — only the funding/filings sweep was new work.

Invocation: Evidence-cited SWOT on Wrenchline, whole company, from Fieldlight's perspective — supports the decision on how hard to attack the dispatch-led segment in 2027. Snapshot and watch report in session.

SWOT: Wrenchline (whole company)

As-of date: 2026-07-30 Decision supported: how aggressively Fieldlight attacks the dispatch-led segment in 2027 Perspective: Fieldlight, competing with them

1. Strengths (internal, evidenced)

• System-of-record lock-in: payroll, inventory, and fleet modules with multi-year contracts standard — Fact (pricing page, Jul 2026) — ranked #1: switching away means replacing three systems, not one
• Deepest dispatch board in category per reviewer consensus — Fact (review site category report, 2026)
• Distribution moat: 14 years of trade-show presence and a certified-consultant network — Fact (partner directory)
• Reliability reputation recurs across independent reviews — Fact (review mining) — note: their "99.9% uptime" homepage claim alone would be their positioning, not a strength; the independent corroboration is what earns the entry

2. Weaknesses (internal, evidenced)

• Tech-app adoption: largest complaint cluster, 40+ reviews since January ("my techs won't use it") — Inference (review mining; no adoption data published) — ranked #1 by exploitability
• Implementation weight: their own onboarding guide describes 6-10 weeks — Fact (onboarding guide)
• Slowing product velocity: release-note cadence roughly halved year over year — Fact (changelog comparison, Jan-Jun 2026); hiring slowed to backfill-only — Fact (careers page, Jun 2026)
• Entry-tier defense looks bolted on: Essentials launched Jul 2026 without the dispatch board — their differentiator — Fact (tier page); suggests protecting the suite price, not serving the segment — Inference

3. Opportunities (external)

• Payments attach is growing across the category without requiring sticker-price increases — Fact (investor materials citing attach rates) — strong fit to their install base
• The 10-30 tech segment remains underserved by real dispatch tooling — Inference (landscape scan, Jun 2026) — weak fit: their cost structure points upmarket
• AI-drafted quoting is arriving category-wide — Fact (two competitor betas per changelogs) — an opportunity for whoever ships it credibly first, including them

4. Threats (external)

• Adoption-led competitors (Fieldlight, DispatchCrow) attacking from below on tech-app quality — Fact (both companies' positioning and review profiles) — ranked #1: it targets their #1 weakness
• Talent drain to those competitors: two senior dispatch people left for DispatchCrow in July — Fact (announcement post)
• Consolidation at the top of the market could produce a better-funded rival suite — Fact (two acquisitions in 18 months, coverage)

5. The Crossings (the "so what")

• S-O (attack): their install base + payments attach is their best move — lock-in (S1) monetizes attach (O1) without a product race they're losing on velocity — Inference. If they take it, expect pricing pressure to ease and retention spending to rise.
• W-T (exposure): tech-app adoption (W1) is exactly what adoption-led attackers (T1) find first — and their slowed velocity (W3) means the fix is slow to ship. The Essentials tier defends the price point but not this exposure — Inference.
• For your decision: the dispatch-led segment is attackable in 2027, but through the techs, not the dispatcher — their board depth (S2) wins feature comparisons, while their app loses daily-use votes. Attack where the users are, not where the demo is.

Assumptions to Validate

• Tech-app resistance actually drives churn decisions (not just review complaints)
• Their slowed hiring signals retrenchment rather than efficiency (carried from the landscape scan — still open)
• Payments attach economics work at trades-business transaction sizes

Why this example works

• Quadrant discipline held. Every O and T entry is true whether or not Wrenchline acts. "Monetize payments attach" appears only in the crossings, as their candidate move — not parked in Opportunities as a strategy in disguise.
• Claimed vs. evidenced is shown, not just preached. The reliability entry explains why the homepage uptime claim alone wouldn't qualify, and what independent corroboration added.
• Customer voice carried the weaknesses quadrant. Three of four W entries trace to reviews and the company's own published documents — buyers and their own docs, not our wishes.
• The crossings reference specific entries (S1, W1, T1) rather than inventing new analysis, and the decision sentence gives the exec an actual stance: attack through the techs.