competitive-analysis

Start by framing your product, target customer, and known competitors, then expand the set using G2 alternatives pages and category searches. Build a dossier per competitor covering pricing, strengths, weaknesses, and funding, then synthesize into a feature matrix and positioning map with specific recommendations.

Try curl on the competitor's homepage and JS bundle to extract meta tags, pricing, and feature copy from SPAs. Then check App Store and Play Store listings, search in the local market language, and finally ask the user for key facts, since empty results often mean low SEO footprint rather than no competitor.

Use April Dunford's positioning method starting from competitive alternatives, Wardley Mapping for platform and infrastructure competition, feature comparison matrices weighted by lost-deal notes, and Kano analysis to classify competitor features as basics, performance, or delighters.

Yes, fetch the homepage with curl to find the JS bundle filename, then grep the bundle for quoted strings matching pricing and feature keywords. This reveals plan names, prices, and marketing copy embedded in compiled React or Vue apps that webFetch cannot read.

G2 and Capterra skew toward mid-market US SaaS with thin coverage of enterprise, consumer, and non-English markets. SimilarWeb traffic estimates are unreliable for sites under roughly 50,000 monthly visits, so flag such data as low-confidence.

Choose a channel in priority order: Slack RSS feeds, Teams RSS connector, or Google Alerts by email. The skill generates ready-to-click alert URLs, a bookmark bundle per competitor, and a competitor-monitoring.md file with a 30-minute monthly ritual checklist.