Avyayalaya/pm-skills-arsenal / skills/competitive-market-analysis
competitive-market-analysis
UnverifiedUse when performing competitive analysis, market entry assessment, moat evaluation, positioning strategy, build/buy/partner decisions, or responding to a competitor move. Encodes 7 Powers, Aggregation Theory, Christensen Disruption, JTBD, Wardley Mapping, and evidence-tier standards. Produces a Competitive War Map artifact.
| File | Kind | Size |
|---|---|---|
| FEEDBACK.md | markdown | 2.2 KB |
| README.md | markdown | 2.6 KB |
| SKILL.md | skill md | 97.7 KB |
| benchmark/README.md | markdown | 19.5 KB |
| examples/USE_CASES.md | markdown | 65.6 KB |
| examples/sample.md | markdown | 10.0 KB |
| manifest.yaml | config | 1.4 KB |
| requirements.txt | manifest | 14 B |
| scripts/competitive_scorer.py | script | 11.9 KB |
| scripts/market_sizing.py | script | 8.0 KB |
examples/USE_CASES.md
View on GitHub# Use Cases: Competitive & Market Analysis
> Three real-world scenarios demonstrating the transformation from generic AI output to skill-powered structural analysis. Each use case showcases different frameworks and capabilities from the Competitive & Market Analysis skill (v1.3.0).
---
## Use Case 1: "Fintech Startup Evaluating Compete-vs-Partner After Stripe Launches a Competing Product"
### Scenario
You are the Head of Product at Ramp, a corporate card and spend management platform with $300M ARR. Stripe has just announced "Stripe Spend Management" — a native expense tracking and card issuance product bundled into Stripe's existing payments infrastructure. Your CEO has called a board meeting in 48 hours and wants a structural assessment: should Ramp compete head-on, pivot positioning, or pursue a partnership/integration strategy with Stripe?
### The Prompt
> Stripe just announced a spend management product that directly competes with Ramp. We have $300M ARR and 25,000 customers, mostly mid-market. Stripe already processes payments for 60% of our customer base. Our board meets in 48 hours. Analyze whether we should compete, reposition, or partner — and what our moat actually looks like now.
### Without the Skill (Generic AI)
**Stripe's Entry Into Spend Management: Competitive Analysis**
Stripe's launch of a spend management product represents a significant competitive threat to Ramp. Here's how to think about this situation:
**Key Competitive Factors:**
Stripe brings several advantages to this market. They have an established brand in payments, deep relationships with finance teams, and the ability to bundle spend management into their existing payments infrastructure at little or no additional cost. Their developer ecosystem is also a major asset, as many companies already have Stripe integrated into their tech stack.
However, Ramp has some important advantages. Your product is purpose-built for spend management, which typically means deeper functionality. You have 25,000 customers who have chosen Ramp specifically for expense tracking and card management. Your team has been focused on this problem for years, giving you domain expertise that Stripe would need time to develop.
**Potential Strategies:**
1. **Compete directly:** Continue building the best spend management product. Emphasize your depth of features and domain expertise. This could work if customers value best-of-breed over bundled solutions.
2. **Reposition:** Shift focus toward areas Stripe is unlikely to prioritize, such as advanced analytics, AI-powered spend insights, or multi-entity financial operations. This reduces direct overlap.
3. **Partner:** Explore an integration or white-label arrangement with Stripe. This would leverage Stripe's distribution while preserving Ramp's product capabilities.
**Recommendation:**
A hybrid approach may be best. Continue competing on product depth while actively seeking partnership opportunities with Stripe. The key risk is that Stripe could bundle spend management for free, which would make it difficult to compete on price alone. Focus on demonstrating ROI through cost savings that justify a standalone purchase, and ensure your product integrates seamlessly with Stripe's payments infrastructure regardless of the competitive dynamic.
### With the Skill
**Competitive War Map: Ramp vs. Stripe Spend Management**
> **Confidence band:** M (40-70%) | **Staleness window:** Reassess if Stripe announces pricing or bundle terms
**Executive Summary**
Stripe's spend management launch is a classic Aggregation Theory move: a payments aggregator commoditizing an adjacent category by bundling it into their existing user relationship. Ramp's moat is narrower than the board assumes — switching costs are moderate and customer-created (expense data, policy configurations), but Stripe's distribution advantage is structural and compounds. Competing head-on is a losing strategy within 24 months. **Ramp should reposition as the multi-rail financial operations platform (not card-first spend management) and build integration depth with Stripe's payments layer rather than competing against it.**
**Step 0b: Framework Selection**
| Question type | Primary frameworks | Supporting | Skipped |
|---|---|---|---|
| Competitive response to incumbent move | 7 Powers, Aggregation Theory, Disruption + COAP, Roger Martin | Switching Cost Decomposition, Wardley | Blue Ocean (not seeking uncontested space), Crossing the Chasm (market already mainstream) |
**7 Powers Heat Map**
| Power | Stripe | Ramp | Evidence |
|---|:---:|:---:|---|
| Scale Economies | 🟢 Strong (T1) | 🟡 Moderate (T1) | Stripe processes $1T+ annually (T1: SEC filings). Marginal cost to add spend management to existing payment flow is near-zero. Ramp's unit economics require standalone sales motion at ~$15K ACV (T1: public revenue/customer estimates). |
| Network Effects | 🟢 Developer ecosystem NE (T1) | 🔴 None (T6: inferred) | Stripe's 3.4M developer accounts create integration gravity (T1: API usage data). Ramp has no same-side or cross-side network effects — each customer deployment is independent. |
| Counter-Positioning | 🔴 None (T6) | 🟡 Possible but narrow (T3) | Stripe cannot be counter-positioned on payments bundling — it IS their model. Ramp could counter-position with multi-rail (non-Stripe payment sources), but this requires rebuilding positioning entirely (T3: Stratechery analysis of bundling dynamics). |
| Switching Costs | 🟢 Payments infrastructure (T1) | 🟡 Expense data + policy config (T2) | Stripe's switching costs are workflow/integration type embedded across the customer's entire revenue stack (T1: API integration depth). Ramp's switching costs are data/migration type — real but surmountable in 30-60 days (T2: customer migration surveys). |
| Branding | 🟢 "Payments infrastructure for the internet" (T1) | 🟡 "Save money with smart cards" (T1) | Stripe's brand carries trust with CFOs for financial infrastructure decisions (T1: NPS data). Ramp's brand is strong in mid-market but positioned around savings, not infrastructure (T1: marketing positioning). |
| Cornered Resource | 🟢 Payment data on merchant spending patterns (T1) | 🟡 Spend category intelligence (T3) | Stripe sees both sides of every transaction across their merchant base — they know what companies spend on before Ramp's card is swiped (T1: data access). Ramp has deep category-level spend data but only post-transaction (T3: analyst assessment). |
| Process Power | 🟡 Moderate (T3) | 🟡 Moderate (T3) | Neither company has multi-decade process advantages. Stripe has engineering culture advantages; Ramp has finance domain expertise (T3). |
**Decision point:** Stripe holds 4 Strong powers vs. Ramp's 0. This is not a fair fight on the current playing field. Ramp must change the playing field or lose.
**Aggregation Theory Assessment**
| Question | Finding | Evidence |
|---|---|---|
| Who owns the user relationship? | **Stripe** — 60% of Ramp's customers already have Stripe as their payments processor (T1: stated in prompt) | Stripe owns the financial infrastructure layer; Ramp is an application layer sitting on top |
| Marginal costs approaching zero? | Stripe: yes — spend mgmt is incremental to existing infrastructure. Ramp: no — each customer requires dedicated onboarding and card issuance (T3) | Stripe's cost to serve a spend mgmt customer who already uses Stripe Payments is near-zero (T6: inferred from architecture) |
| Which layers are commoditizing? | Spend management features are commoditizing. Financial infrastructure remains integrated. (T3: COAP analysis) | When the infrastructure owner bundles an application-layer feature, the application layer commoditizes — this is the canonical Aggregation Theory pattern |
**COAP Analysis (Christensen's Conservation of Attractive Profits):**
The value chain is inverting:
```
[Payment rails] --> [Card issuance] --> [Expense tracking] --> [Spend policy] --> [Financial insights]
^ ^
| |
Integrating (Stripe) Commoditizing (Stripe bundles it)
```
Profits are shifting FROM standalone spend management (Ramp's current position) TOWARD integrated financial infrastructure (Stripe's position). Building a better expense tracker is building on the commoditizing layer. **This is the single most important finding for the board: Ramp's current product category is being structurally commoditized, not just competitively challenged.**
**Roger Martin — Revealed Strategy Test**
| Dimension | Stripe says | Resource allocation reveals | Gap |
|---|---|---|---|
| Where to play | "Increase the GDP of the internet" (T5: press) | 70%+ revenue from online payments; spend mgmt is a retention/expansion play, not a new business (T3) | Stripe does not need spend mgmt to win — they need it to prevent churn to vertical platforms |
| How to win | "Best developer experience" (T5) | Bundling free/cheap adjacent products to increase switching costs on payments core (T1: pricing page shows bundled discounts) | They win on lock-in, not product excellence in any single category |
**Key insight:** Stripe's spend management product does not need to be better than Ramp's. It needs to be good enough and free (or deeply discounted) as a bundle. This is not a product competition — it is a business model asymmetry. Ramp charges for what Stripe gives away. [EVIDENCE-LIMITED: validate Stripe's actual pricing model before acting]
**Strategic Recommendations (O->I->R->C->W Cascade)**
**Recommendation 1: Reposition from "Smart Corporate Card" to "Multi-Rail Financial Operations Platform"**
- **Observation** [T1, T3]: Stripe's bundling commoditizes single-rail card-based spend management. 60% of Ramp's customers are already Stripe merchants.
- **Implication**: Competing on card-based expense management against a payments aggregator is structurally unwinnable. The only defensible position requires serving financial operations that span multiple payment rails (ACH, wire, check, multi-provider cards) — something Stripe cannot offer without undermining their single-rail value proposition.
- **Response**: Rebrand product positioning within 90 days. Accelerate multi-rail capabilities (bill pay, AP automation, procurement) that create workflow switching costs Stripe cannot match. Owner: CPO + CMO. Timeline: positioning in 30 days, product capabilities in 90-180 days.
- **Confidence**: M — assumes Stripe bundles spend mgmt at low/no cost. If Stripe prices it as a premium standalone product, direct competition remains viable longer.
- **Watch**: Stripe's pricing announcement. If Stripe charges >50% of Ramp's ACV for spend management standalone, confidence in repositioning drops to L and direct competition becomes viable.
**Recommendation 2: Build Integration Depth INTO Stripe, Not Away From It**
- **Observation** [T1]: 60% customer overlap means fighting Stripe is fighting your own distribution channel.
- **Implication**: Ramp's spend management features add value ON TOP of Stripe's payments data. The integration play turns Stripe's distribution into Ramp's distribution, rather than competing against it.
- **Response**: Ship a deep Stripe integration within 60 days that makes Ramp demonstrably better when used WITH Stripe than Stripe's native spend management alone. Create a "Ramp + Stripe" narrative, not "Ramp vs. Stripe." Owner: Head of Partnerships + Head of Integrations.
- **Confidence**: H — this is a low-regret move regardless of Stripe's competitive posture.
- **Watch**: Stripe's API access policies. If Stripe restricts API access to spend management competitors, this strategy is dead. Monitor developer documentation weekly.
**Recommendation 3: Accelerate Enterprise Upmarket Before Stripe Does**
- **Observation** [T3, T6]: Stripe's spend management targets SMB-mid-market (their existing base). Enterprise financial operations require compliance, multi-entity, approval workflows, and ERP integrations that Stripe has not built (T6: inferred from product scope).
- **Implication**: Enterprise is the segment where best-of-breed beats bundled, because CFOs at $1B+ companies will not consolidate financial operations onto a payments processor's add-on product.
- **Response**: Accelerate enterprise sales motion. Hire 5 enterprise AEs in Q1. Build SOX compliance, multi-entity support, and NetSuite/SAP integrations. Owner: CRO. Timeline: Q1-Q2.
- **Confidence**: M — assumes enterprise buyers differentiate between payments-bundled and purpose-built. If enterprise CFOs treat Stripe's offering as "good enough," this strategy fails.
- **Watch**: Enterprise win rates vs. Stripe in deals >$100K ACV. If Ramp loses 3+ enterprise deals to Stripe Spend Management in Q1, reassess.
**Assumption Registry**
| # | Assumption | Framework | Confidence | Evidence | Invalidation signal |
|---|---|---|---|---|---|
| 1 | Stripe will bundle spend management at low/no additional cost | Aggregation Theory, COAP | H | Stripe's historical pattern with Billing, Tax, Identity — all bundled or heavily discounted (T1) | Stripe prices spend management as a premium standalone product at >50% of Ramp's ACV |
| 2 | Mid-market customers will accept "good enough" bundled spend management over best-of-breed | Disruption Theory | M | Christensen's theory predicts this for over-served markets, but spend management may still be under-served (T3) | Customer churn to Stripe remains <5% after 6 months of Stripe availability |
| 3 | Enterprise segment values purpose-built financial operations over bundled | Roger Martin (Where to Play) | M | Pattern from ERP/HCM markets where best-of-breed wins upmarket (T4: Gartner) | Enterprise win rate vs. Stripe drops below 50% |
**Adversarial Self-Critique**
**Weakness 1: We may be overweighting Aggregation Theory.** Stripe has historically been a payments infrastructure company, not a financial applications company. Their track record with bundled application-layer products (Stripe Atlas, Stripe Capital) is mixed — these are small businesses, not category leaders. Spend management may require more product depth than Stripe is willing to invest, making the "good enough bundled product" scenario less certain than Aggregation Theory predicts. If Stripe's spend management is mediocre, Ramp's direct competition strategy remains viable.
**Weakness 2: The repositioning timeline may be unrealistic.** Pivoting from "smart corporate card" to "multi-rail financial operations platform" in 90 days is a marketing narrative shift, not a product reality. Building genuine multi-rail capabilities (AP automation, procurement, bill pay) requires 12-18 months of engineering investment. During that window, Ramp is vulnerable — neither positioned clearly as a card product nor credible as a financial operations platform.
**Weakness 3: The partnership strategy assumes Stripe cooperates.** If Stripe views Ramp as a direct competitor, they have strong incentives to restrict API access, degrade integration quality, or make the "Ramp + Stripe" experience worse than "Stripe standalone." This analysis assumes Stripe maintains open API access, which is an assumption that Stripe controls, not Ramp.
### What Changed
- **Structural moat scoring replaced "Ramp has some important advantages" with a quantified 7 Powers heat map** showing Stripe holds 4 Strong powers to Ramp's 0 — transforming a vague sense of threat into an existential clarity about the competitive asymmetry.
- **COAP (Conservation of Attractive Profits) analysis identified that Ramp's product category is being structurally commoditized**, not just competitively challenged. The generic output treated this as a feature competition; the skill revealed it as a value chain inversion where Ramp's layer is losing its economic viability.
- **Aggregation Theory decomposed the business model asymmetry**: Stripe charges zero marginal cost for what Ramp charges $15K ACV. The generic output mentioned bundling risk in one sentence; the skill made it the central finding with evidence-tiered backing.
- **Roger Martin's Revealed Strategy test exposed that Stripe does not need to win spend management** — they need it to prevent churn from their payments core. This reframes the entire competitive dynamic: Ramp is not fighting a product battle, it is collateral damage in a retention strategy.
- **O->I->R->C->W cascades turned each finding into a specific, timed, owned action** with explicit confidence levels and watch indicators that tell the board exactly when to reassess. The generic output offered three vague strategy buckets with no triggers, owners, or timelines.
---
## Use Case 2: "Mid-Market HR Tech Company Assessing Moat Durability After Workday Announces a Free Tier"
### Scenario
You are VP of Product at Lattice, a $200M ARR performance management and people analytics platform. Workday has just announced "Workday Essentials" — a free tier of their HCM platform that includes basic performance reviews, goal tracking, and engagement surveys for companies under 500 employees. This directly targets Lattice's core mid-market segment. Your investors want to know whether Lattice's moat can survive a free substitute from the market's dominant enterprise HCM platform expanding downmarket.
### The Prompt
> Workday just announced a free tier ("Workday Essentials") targeting sub-500 employee companies with performance reviews, goals, and engagement surveys. This is our core market at Lattice. We have $200M ARR and 5,000+ mid-market customers. Assess whether our moat survives this. What structural advantages do we actually have, and what should we do in the next 6 months?
### Without the Skill (Generic AI)
**Impact Assessment: Workday Essentials Free Tier on Lattice**
Workday's launch of a free tier targeting sub-500 employee companies is a notable competitive development for Lattice. Here's a breakdown of the impact and potential responses:
**Threat Assessment:**
The free tier is concerning because it removes the most basic barrier to entry — price. Companies evaluating performance management solutions will now have a zero-cost option from a well-known enterprise brand. Workday's brand recognition with HR leaders is strong, and "free" is a powerful acquisition tool.
However, there are reasons this threat may be more limited than it first appears. Free tiers from enterprise vendors often have significant limitations in functionality. Workday's core competency is in enterprise HCM, and their product design is built for large, complex organizations. A stripped-down version may not deliver the user experience that mid-market companies expect from modern performance management tools.
**Lattice's Advantages:**
1. **Purpose-built product**: Lattice was designed from the ground up for mid-market performance management. The UX is tailored for companies of this size.
2. **Customer relationships**: With 5,000+ customers, Lattice has deep relationships and institutional knowledge about mid-market HR needs.
3. **Integration ecosystem**: Lattice integrates with the HRIS tools that mid-market companies actually use (BambooHR, Rippling, etc.), not just enterprise platforms.
4. **Culture and engagement focus**: Lattice has expanded beyond pure performance reviews into engagement, compensation, and career development — areas where Workday's free tier likely won't compete.
**Recommended Response:**
1. **Don't panic on pricing**: Avoid a race to the bottom. Your value proposition is product depth and UX quality, not price.
2. **Accelerate differentiation**: Invest in areas Workday won't include in a free tier — advanced analytics, AI-powered insights, compensation management.
3. **Strengthen customer success**: Ensure existing customers are fully utilizing the platform and seeing ROI. High engagement is the best defense against free alternatives.
4. **Consider a free tier of your own**: Evaluate whether offering a limited free product could preempt Workday's entry into your pipeline.
5. **Monitor closely**: Track pipeline changes, competitive mentions in deals, and customer inquiries about Workday Essentials over the next two quarters.
The bottom line is that while Workday's move is worth taking seriously, free enterprise products have historically underperformed in markets where UX and purpose-built functionality matter. Lattice's strongest defense is continuing to be the best product for its target market.
### With the Skill
**Competitive War Map: Lattice Moat Durability vs. Workday Essentials**
> **Confidence band:** M (40-70%) | **Staleness window:** 2026-08-20 or upon Workday Essentials GA release, whichever is first
**Executive Summary**
Lattice's moat is real but thinner than the investor narrative assumes. Switching costs are moderate and concentrated in workflow/integration and data types — both of which Workday can replicate by owning the HRIS layer underneath. The structural threat is not Workday's free product quality — it is Workday's ownership of the customer relationship via the HRIS system-of-record. When the platform owner offers performance management for free, the standalone vendor must demonstrate value that exceeds the friction of running a separate system. **Lattice should not compete on price or launch a free tier; instead, Lattice should build the "people intelligence layer" that requires data Workday's free tier cannot access — compensation benchmarks, market data, and cross-company talent analytics — making Lattice's value increase with network scale in a way Workday's single-tenant architecture cannot match.**
**Step 0b: Framework Selection**
| Question type | Primary frameworks | Supporting | Skipped |
|---|---|---|---|
| Moat assessment + competitive response | 7 Powers, Switching Cost Decomposition, Aggregation Theory, Disruption + COAP | JTBD, Roger Martin (Revealed Strategy) | Blue Ocean (not seeking new market), Crossing the Chasm (market is post-chasm), Data Content Loops (not applicable to B2B SaaS), Win/Loss (no loss data yet from Workday Essentials) |
**Switching Cost Decomposition — The Core of This Analysis**
This is a moat durability question. Switching cost decomposition is the load-bearing framework, not 7 Powers alone.
| Cost Type | Lattice | Workday Essentials | Evidence |
|---|:---:|:---:|---|
| Financial/Contractual | ████░░░░░░ 4/10 (T3) | ██████████ 0/10 (T5) | Lattice: annual contracts at ~$6-12/user/month, typical 1-year term (T3: pricing analysis). Workday Essentials: free eliminates financial barrier entirely (T5: press announcement). Financial switching costs are Lattice's weakest moat dimension. |
| Data/Migration | ██████░░░░ 6/10 (T2) | ███░░░░░░░ 3/10 (T6: inferred) | Lattice: 2-5 years of performance review history, goal data, 1:1 notes, calibration records are the customer's institutional memory (T2: customer interviews indicate this is a top-3 retention driver). Workday Essentials: new product, no migration path exists yet, but Workday owns HRIS data which reduces migration scope (T6: inferred). |
| Workflow/Integration | ███████░░░ 7/10 (T2) | █████░░░░░ 5/10 (T6: inferred) | Lattice: embedded in the review cycle, calibration workflow, manager 1:1 habits, Slack/Teams integrations, BambooHR/Rippling HRIS syncs (T2: usage data shows average customer has 4.2 integrations active). Workday Essentials: native HRIS integration eliminates the biggest integration pain point — but mid-market customers using BambooHR or Rippling, not Workday HRIS, gain no integration benefit from Essentials (T6: inferred). |
| Identity | █████░░░░░ 5/10 (T3) | ██░░░░░░░░ 2/10 (T6) | Lattice: "modern people management" brand resonates with mid-market HR leaders who see themselves as progressive (T3: community engagement, Lattice Resources hub traffic). Workday: perceived as enterprise/legacy by mid-market HR practitioners (T6: sentiment inference from G2 reviews). |
| Learning/Procedural | ██████░░░░ 6/10 (T2) | ██░░░░░░░░ 2/10 (T5) | Lattice: HR admins have invested 20-40 hours learning configuration, template building, cycle setup (T2: onboarding data). Workday Essentials: "simplified" positioning implies lower learning curve, but Workday's historically complex UX undermines this claim (T5: announcement vs. T3: G2 usability scores for Workday core product). |
| Relational/Trust | █████░░░░░ 5/10 (T2) | ███░░░░░░░ 3/10 (T4) | Lattice: dedicated CSMs for mid-market accounts build relationship capital (T2: NPS by segment). Workday: free tier unlikely to include dedicated CS (T4: standard freemium model implies self-serve). |
| Social/Community | ████░░░░░░ 4/10 (T3) | █░░░░░░░░░ 1/10 (T6) | Lattice: active HR community (Lattice Resources), peer networking, content ecosystem (T3: community metrics). Workday: no mid-market community exists for Essentials (T6: product is not yet launched). |
**Key insight:** Lattice's strongest switching costs are customer-CREATED — review history, workflow configuration, manager habits, community participation. These compound with usage and are durable. But they are concentrated in the *workflow/integration* and *data/migration* categories, both of which Workday can structurally undermine by owning the HRIS system-of-record underneath them. **The real question is not "will customers switch to Workday Essentials?" but "will NEW customers ever adopt a standalone performance tool when their HRIS offers it for free?"** Lattice's moat protects the installed base. It does not protect the pipeline. (H)
**7 Powers Heat Map**
| Power | Workday | Lattice | Evidence |
|---|:---:|:---:|---|
| Scale Economies | 🟢 Strong (T1) | 🟡 Moderate (T1) | Workday: $7.2B revenue, R&D amortized across full HCM suite (T1: SEC filings). Lattice: $200M ARR, all R&D concentrated on performance/people mgmt vertical (T1). Marginal cost for Workday to add performance features: near-zero. For Lattice to add HRIS features: prohibitive. |
| Network Effects | 🟡 Data NE nascent (T6: inferred) | 🔴 None currently (T6) | Neither company has true network effects today. Workday has potential data NE from aggregated workforce analytics across their 10,000+ enterprise customers. Lattice has 5,000+ mid-market customers but has not built cross-company benchmark capabilities. **This is Lattice's biggest missed opportunity.** |
| Counter-Positioning | 🔴 None (T6) | 🟡 Possible: "people intelligence" vs. "HRIS add-on" (T6) | Workday cannot be counter-positioned on price — free tier is their move. Lattice CAN counter-position on cross-company intelligence: "We see performance data across 5,000 companies; Workday sees only yours." This requires Lattice to BUILD this capability — it does not exist yet. |
| Switching Costs | 🟢 HRIS lock-in (T1) | 🟡 See decomposition above (T2) | Workday's switching costs are HRIS-level — deeply embedded in payroll, benefits, compliance. Lattice's switching costs are application-level — real but shallower. |
| Branding | 🟢 Enterprise trust (T1) | 🟡 Mid-market affinity (T3) | Workday brand carries CFO/CHRO trust for HR infrastructure decisions (T1: brand recognition surveys). Lattice brand is strong with mid-market HR practitioners but not with C-suite buyers (T3: market positioning analysis). |
| Cornered Resource | 🟢 HRIS system-of-record data (T1) | 🟡 Performance review corpus (T2) | Workday owns employee master data — the foundation for any people analytics. Lattice owns performance-specific data (reviews, goals, feedback) but lacks the employee record underneath it. |
| Process Power | 🟡 Enterprise HCM (T3) | 🟡 Mid-market perf mgmt (T3) | Both have domain expertise in their respective segments. Neither has a decisive process advantage. |
**Decision point:** Workday holds 3 Strong powers, Lattice holds 0. But Workday's powers are concentrated in the *infrastructure* layer, not the *intelligence* layer. Lattice's counter-positioning opportunity exists in building data network effects across its 5,000-company corpus — something Workday's single-tenant architecture makes structurally difficult for them to replicate.
**Disruption Vector Analysis (Christensen)**
| Vector | Applicable? | Assessment |
|---|:---:|---|
| Low-end | 🟢 Yes — this is the primary threat | Workday Essentials is a textbook low-end disruption play: "good enough" performance reviews at zero cost for customers who are over-served by Lattice's full feature set. Detection signal: customers saying "we only use 30% of Lattice" — validate with usage analytics (T6: hypothesis). |
| New-market | 🟡 Partial | Workday Essentials may bring performance management to companies that have never used a dedicated tool (non-consumers). This expands the category but routes new entrants to Workday, not Lattice. |
| COAP | 🟢 Yes — critical | The performance management application layer is commoditizing. Value is shifting to the HRIS infrastructure layer (where Workday sits) and the intelligence/analytics layer (where nobody sits yet). **Lattice must move to the intelligence layer or get squeezed between free HRIS add-ons and enterprise suite bundles.** |
**"Isn't Good Enough" / "More Than Good Enough" Test:**
Mid-market performance management is "more than good enough" for most buyers — the category has matured, features are converging, and many customers use a fraction of available capabilities (T3: industry analyst commentary on feature bloat in HR tech). This means modular/cheaper architectures win. Workday's free modular offering is structurally favored in this market state. (M)
**Cross-Framework Contradiction**
| Contradiction | Framework A says | Framework B says | Resolution |
|---|---|---|---|
| Moat protection vs. disruption vulnerability | Switching Costs (7 Powers): Lattice has moderate switching costs that protect the installed base (workflow + data types score 6-7/10) | Christensen COAP: The application layer is commoditizing — switching costs erode when the infrastructure owner bundles the application for free | **Weight COAP more heavily.** Switching costs protect existing customers for 12-24 months. But pipeline dries up faster than churn accelerates. Lattice's installed base is a melting ice cube, not a fortress — valuable today, depreciating steadily. The urgency is pipeline, not retention. |
**Strategic Recommendations (O->I->R->C->W Cascade)**
**Recommendation 1: Build Cross-Company People Intelligence (The Network Effects Moat Lattice Doesn't Have Yet)**
- **Observation** [T2, T6]: Lattice has anonymized performance, compensation, and engagement data across 5,000+ mid-market companies. This data is not being used to create cross-company benchmarks, talent market intelligence, or predictive analytics. Workday's single-tenant enterprise architecture makes cross-company benchmarking structurally harder for them.
- **Implication**: The only defensible position against a free HRIS-bundled substitute is intelligence that gets better with more customers on the platform. This creates data network effects — each new Lattice customer makes the benchmarks more valuable for every other customer. Workday cannot replicate this without fundamentally changing their data architecture.
- **Response**: Launch "Lattice Intelligence" — anonymized, cross-company benchmarks for compensation bands, performance distribution, engagement drivers, and attrition risk by role/industry/geo. Ship V1 within 6 months. Make it the anchor feature in every renewal and new deal. Owner: CPO. Timeline: V1 in 6 months, full product in 12 months.
- **Confidence**: M — assumes customers will opt in to anonymized data sharing and that the resulting benchmarks are differentiated enough to justify a paid product vs. free Workday. If opt-in rates are below 40%, the data network effects are too thin to matter.
- **Watch**: Opt-in rate for anonymized data sharing among existing customers. Pilot with 100 customers in Q1; if <30% opt in, the strategy needs reworking.
**Recommendation 2: Lock In the Installed Base Before Churn Begins**
- **Observation** [T2]: Lattice's switching costs are moderate (composite 5.3/10) and concentrated in workflow and data types that erode over time as Workday Essentials matures.
- **Implication**: There is a 12-18 month window where existing customer switching costs are high enough to prevent mass churn. After that window, Workday's product will improve, migration tooling will appear, and the switching calculus changes.
- **Response**: Offer 2-3 year renewal contracts at a 15-20% discount to any customer renewing in the next 6 months. Prioritize the 60% of customers in the sub-500 employee segment that Workday Essentials directly targets. Accept margin compression now to lock in revenue for 24-36 months. Owner: CRO + CFO. Timeline: immediate.
- **Confidence**: H — this is a low-regret move. Locked-in customers buy time for Recommendation 1 to mature.
- **Watch**: Renewal rate in the sub-500 segment. If renewal rate drops >5pp quarter-over-quarter before lock-in contracts are offered, accelerate timeline.
**Recommendation 3: Reposition Upmarket — Own "People Operations for Scaling Companies" (500-5,000 Employees)**
- **Observation** [T3, T6]: Workday Essentials targets sub-500. Workday's enterprise product targets 5,000+. The 500-5,000 employee segment is underserved by both — too complex for the free tier, too small for Workday enterprise pricing.
- **Implication**: The 500-5,000 segment has the highest willingness to pay for purpose-built performance management and the lowest exposure to Workday Essentials cannibalization.
- **Response**: Shift ICP and sales focus to 500-5,000 employee companies. Build the features this segment needs that sub-500 does not (multi-level calibration, manager effectiveness analytics, org-wide talent reviews). Deprioritize features that only serve the sub-200 segment. Owner: CPO + CRO. Timeline: ICP shift in Q1, product roadmap adjustment in Q2.
- **Confidence**: M — assumes the 500-5,000 segment is large enough to sustain $200M+ ARR growth trajectory. If TAM analysis shows <$2B in this segment, the growth math does not work.
- **Watch**: Pipeline ASP and deal size. If average deal size does not increase by 30%+ within two quarters of the ICP shift, the upmarket move is not working.
**Assumption Registry**
| # | Assumption | Framework | Confidence | Evidence | Invalidation signal |
|---|---|---|---|---|---|
| 1 | Workday Essentials will be "good enough" for basic performance management in sub-500 companies | Christensen Disruption | M | Pattern from free tiers in adjacent categories (Slack free, Zoom free, HubSpot free CRM) (T3) | Workday Essentials G2 reviews average below 3.0/5 for usability after 6 months of GA |
| 2 | Lattice's 5,000-company data corpus is large enough to build meaningful cross-company benchmarks | Data Network Effects (7 Powers) | M | Comparable to Glassdoor's early dataset when they began employer benchmarks (T6: analogy, not direct evidence) | Pilot benchmark product receives <3.5 NPS from test customers due to insufficient data granularity |
| 3 | Mid-market HR buyers will pay for a standalone performance tool when a free HRIS-bundled option exists | Aggregation Theory | L | Historical precedent is mixed — some categories (CRM, marketing automation) sustained standalone tools alongside free suite add-ons; others (basic email, calendar) were fully absorbed (T3) | New pipeline from sub-500 companies declines >30% YoY in the two quarters following Workday Essentials GA |
**Adversarial Self-Critique**
**Weakness 1: The "People Intelligence" strategy assumes data network effects that may be asymptotic.** Cross-company benchmark data has diminishing returns — the 5,000th company's data adds less marginal value than the 50th. If the benchmark product is useful at 500 companies, Workday could replicate it with their enterprise base alone (10,000+ customers). The counter-positioning may be narrower than this analysis assumes.
**Weakness 2: This analysis underweights the "do nothing" scenario.** Workday's free tier may underperform, and mid-market customers may continue to buy purpose-built tools. The HR tech market has shown surprising resilience of best-of-breed tools against suite bundling (Greenhouse vs. Workday Recruiting, Culture Amp vs. Qualtrics). If Workday Essentials is as mediocre as most enterprise free tiers, the existential framing of this analysis is overblown and the recommended strategic shifts are costly overreactions.
**Weakness 3: The upmarket repositioning assumes Lattice can compete at 500-5,000 without an HRIS of its own.** Companies in this segment increasingly want consolidated platforms, not point solutions. Moving upmarket without owning the system of record may trade one vulnerability (free tier commoditization at the low end) for another (platform consolidation pressure at the high end).
### What Changed
- **Switching Cost Decomposition replaced "Lattice has deep relationships" with a 7-type quantified breakdown** showing that Lattice's moat is concentrated in workflow/integration (7/10) and data/migration (6/10) — the two types most vulnerable to an HRIS owner bundling from below.
- **COAP analysis identified that the entire application layer is commoditizing**, transforming the question from "how do we compete with a free product?" to "how do we escape a layer that is structurally losing its ability to capture value?" The generic output never questioned whether the category itself was viable.
- **The cross-framework contradiction between Switching Costs (moat is real) and COAP (moat is melting) surfaced the critical insight**: the installed base is protected for 12-18 months, but the pipeline is drying up now. This time-bound framing changes the urgency and sequence of every recommendation.
- **The counter-positioning opportunity (cross-company intelligence/data network effects) was identified and assessed honestly** — including the assumption that it does not yet exist and the specific conditions under which it fails. The generic output listed "advanced analytics" as a vague differentiator without explaining why it would be structurally defensible.
- **Evidence tiers exposed which claims are well-supported (T1-T2) and which are speculative (T6)**, preventing the board from treating hypotheses as findings. The generic output presented all claims with equal implicit confidence, giving no basis for distinguishing facts from guesses.
---
## Use Case 3: "AI-Native Analytics Startup Deciding Where to Play Against Tableau, Power BI, and Looker"
### Scenario
You are the co-founder and CPO of a Series A AI-native analytics startup ($8M ARR, 400 customers). Your product lets business users ask questions of their data in natural language and get automated dashboards, insights, and anomaly detection — no SQL required. You have raised $40M and need to decide your positioning strategy. Tableau (Salesforce), Power BI (Microsoft), and Looker (Google) all have massive installed bases and are adding AI/NL features. Your board wants to understand where you have a structural right to win and where you are walking into a kill zone.
### The Prompt
> We're a Series A AI-native analytics company ($8M ARR, 400 customers). Users ask data questions in natural language and get auto-generated dashboards and anomaly detection. Tableau, Power BI, and Looker are all adding AI features to their products. Where do we have a structural right to win? Where are we in a kill zone? What is our positioning strategy?
### Without the Skill (Generic AI)
**Competitive Positioning Analysis: AI-Native Analytics vs. Incumbents**
This is a classic "David vs. Goliath" competitive situation. Here's how to think about positioning against the three major incumbents:
**Competitive Landscape:**
The BI market is dominated by three players with massive distribution advantages:
- **Tableau (Salesforce):** Market leader in visual analytics with a large and loyal user base. Recently added "Tableau GPT" for natural language queries.
- **Power BI (Microsoft):** Dominant in enterprises with Microsoft 365 deployments. Copilot integration brings AI capabilities natively.
- **Looker (Google):** Strong in data-forward companies with BigQuery integration. Gemini-powered features expanding.
**Your Advantages:**
1. **AI-native architecture:** Your product was built from the ground up around AI, not retrofitted. This typically means a better user experience for natural language interactions.
2. **Speed of innovation:** As a startup, you can iterate faster than large organizations constrained by backward compatibility.
3. **Simplicity:** Traditional BI tools require significant technical skill. Your natural language approach could democratize analytics.
4. **Focus:** While incumbents serve broad use cases, you can optimize for specific workflows where AI excels.
**Kill Zone Risks:**
The biggest risk is that incumbents add "good enough" AI features that eliminate your differentiation. Microsoft is particularly dangerous because Power BI is already bundled with Microsoft 365, and adding Copilot-powered analytics makes it a zero-additional-cost option for most enterprises.
**Positioning Strategy:**
1. **Don't compete on dashboards.** You will lose a feature-by-feature comparison with Tableau or Power BI on traditional BI capabilities.
2. **Own "AI-first analytics."** Position as the tool for business users who have never used a BI tool — not a replacement for analysts who already use Tableau.
3. **Target specific use cases.** Focus on 2-3 use cases where natural language analytics is dramatically better than traditional BI (e.g., ad-hoc questions, anomaly detection, executive reporting).
4. **Build integrations, not walls.** Integrate with existing data warehouses and BI tools rather than trying to replace them. Be the AI layer on top of the data stack.
5. **Land in teams, not IT departments.** Sell to business teams directly (product-led growth) rather than competing in enterprise procurement cycles where incumbents have structural advantages.
**Bottom Line:**
Your best strategy is likely to position as a complement to existing BI tools rather than a replacement. Target non-technical business users who can't or won't use Tableau/Power BI, and make the AI-native experience so much better for specific use cases that it justifies a separate purchase. Avoid head-to-head enterprise deals where Microsoft and Salesforce will leverage their existing relationships and bundling power.
### With the Skill
**Competitive War Map: AI-Native Analytics — Where to Play Against Tableau, Power BI, and Looker**
> **Confidence band:** M (40-70%) | **Staleness window:** 2026-08-20 or upon next major AI feature release from any incumbent
**Executive Summary**
The AI analytics market is at a structural inflection point where the rules that defined BI competition for 15 years are breaking. Incumbents built moats around technical users who write queries and build dashboards. AI makes those skills less scarce, which erodes incumbent switching costs from the demand side even as incumbents add AI features from the supply side. The startup's right to win exists in exactly one structural position: serving the 80% of business users who are non-consumers of analytics today — people who have data questions but have never opened a BI tool. This is a new-market disruption opportunity, not a competitive substitution play. Competing against Tableau on dashboards or Power BI on enterprise distribution is suicide. **The startup should position as the "analytics layer for operators" — embedded in the workflow tools (Slack, email, CRM) where decisions happen, not as a standalone BI destination.**
**Step 0b: Framework Selection**
| Question type | Primary frameworks | Supporting | Skipped |
|---|---|---|---|
| Market entry + positioning + kill zone assessment | JTBD, Blue Ocean, Crossing the Chasm, 7 Powers | Disruption + COAP, Aggregation Theory, Wardley | Win/Loss (insufficient data at $8M ARR), Roger Martin (better applied after positioning is chosen), Data Content Loops (no content-SEO play) |
**JTBD Competitive Landscape — The Demand-Side View**
The generic approach lists competitors by product similarity. JTBD reveals the actual competitive set by listing everything customers "hire" for the analytics job.
| Job to be Done | Current Solutions Hired | Satisfaction | Opportunity |
|---|---|---|---|
| **"Help me understand what happened last quarter"** (Functional) | Tableau/Power BI dashboards, analyst-built reports, Excel exports | Over-served (H) — dashboards exist for this; the problem is answered | 🔴 Do not compete here. Incumbents own this job. |
| **"Answer my specific question about the data right now"** (Functional) | Ask an analyst, wait 2-5 days; write SQL (if technical); give up (if not) | Severely under-served (H) — 80% of business users cannot self-serve ad-hoc questions | 🟢 Primary opportunity. Non-consumption is the main competitor, not Tableau. |
| **"Alert me when something unusual happens"** (Functional) | Manual threshold alerts, analyst monitoring, discovered by accident in monthly reviews | Under-served (M) — existing tools require manual setup for each alert | 🟢 Secondary opportunity. AI anomaly detection is genuinely novel, not a retrofit. |
| **"Make me look data-driven in front of my team"** (Social/Emotional) | Copy-paste charts from analyst decks, screenshot dashboards, build slides manually | Moderately served but painful (M) | 🟡 Tertiary opportunity. Auto-generated narratives and shareable insights. |
| **"Help me build a dashboard for my team"** (Functional) | Tableau, Power BI, Looker, Metabase, Grafana | Over-served (H) — dozens of competent tools for this job, including free ones | 🔴 Kill zone. Do not compete here under any circumstances. |
**Key insight:** The startup's right to win is concentrated in the "answer my specific question right now" job — a job that is UNDER-served for 80% of business users and where the current solution is "ask an analyst and wait" or "give up." Tableau/Power BI/Looker do not serve this job well because they require the user to build a dashboard first. The startup's NL interface solves this job natively. **Non-consumption is the primary competitor, not incumbents.** (H)
**Blue Ocean Analysis — Strategy Canvas**
The industry competes on a set of factors that all serve the same user (the analyst/power user). The strategy canvas reveals convergence:
| Factor | Tableau | Power BI | Looker | AI-Native Startup (Recommended) |
|---|:---:|:---:|:---:|:---:|
| Dashboard building depth | High | High | High | **Eliminate** |
| Query language power (SQL/DAX/LookML) | High | High | High | **Eliminate** |
| Data modeling capabilities | High | Medium | High | **Reduce** (auto-model) |
| Visual customization | High | Medium | Medium | **Reduce** |
| Enterprise admin controls | High | High | High | **Reduce** (start with team-level) |
| Time-to-first-insight | Low (hours/days) | Low (hours/days) | Low (hours/days) | **Raise** (seconds) |
| Non-technical user accessibility | Low | Low | Low | **Raise** (core differentiator) |
| Embedded in workflow tools (Slack/email/CRM) | None | Low (Teams only) | None | **Create** |
| Proactive anomaly detection | None | None (manual) | None | **Create** |
| Auto-generated narrative insights | None | Basic (Copilot) | None | **Create** |
**ERRC Grid:**
| Eliminate | Reduce | Raise | Create |
|---|---|---|---|
| Dashboard builder UI (T6: inferred — building dashboards is the incumbents' battlefield) | Data modeling complexity (auto-infer schemas) | Time-to-first-insight from hours to seconds (T6: this is the core value proposition) | Workflow-embedded analytics (Slack bot, email digests, CRM-embedded) |
| SQL/query language requirement | Visual customization options (good defaults, not infinite control) | Non-technical user accessibility (NL-first, zero training required) | Proactive anomaly detection and push notifications |
| Enterprise procurement complexity (PLG-first) | Enterprise admin features (right-size for mid-market) | | Auto-generated narrative explanations ("Revenue dropped 12% because...") |
**Decision point:** The Strategy Canvas shows all three incumbents competing on the same value curve — they are fighting over the same 20% of users (analysts and power users). The startup's value curve is fundamentally different: eliminate the analyst-oriented factors, create operator-oriented factors. This is a Blue Ocean position — but it must be defended with 7 Powers or competitors will follow within 18 months.
**Crossing the Chasm — Adoption Stage Assessment**
| Question | Finding |
|---|---|
| TAL position | AI-native analytics is in the **Early Adopter** stage. The 400 existing customers are visionaries and tech-forward teams who bought on the promise of NL analytics. The Early Majority has not arrived. (M) |
| Chasm status | **Pre-chasm.** The product has Early Adopter traction but no Early Majority beachhead. Pragmatist buyers are not yet purchasing because: no industry-specific references, no "whole product" for any single use case, and the technology is perceived as unreliable for business-critical decisions. (H) |
| Whole product gap | For the Early Majority, the startup needs: (1) data accuracy guarantees / confidence scores on every answer, (2) industry-specific data models and benchmarks, (3) integration with at least 2 major data warehouses with zero-config setup, (4) audit trail showing how every AI answer was derived, (5) SOC2 / enterprise security baseline. (H) |
| Bowling alley head pin | **Revenue Operations teams at B2B SaaS companies (200-2,000 employees).** Rationale: (a) acute pain — RevOps teams field 30+ ad-hoc data questions per week from sales leaders and cannot keep up (T2: customer interviews); (b) reachable whole product — Salesforce + data warehouse + 10 common metrics covers 80% of questions; (c) accessible references — SaaS RevOps is a tight community where references travel fast; (d) adjacent niches — after RevOps, expand to Marketing Ops, then Finance teams. (M) |
**7 Powers Heat Map**
| Power | Tableau (Salesforce) | Power BI (Microsoft) | Looker (Google) | AI-Native Startup |
|---|:---:|:---:|:---:|:---:|
| Scale Economies | 🟢 Strong (T1) | 🟢 Strong (T1) | 🟢 Strong (T1) | 🔴 Weak (T1) |
| Network Effects | 🟡 Community/templates (T3) | 🟡 M365 ecosystem (T1) | 🟡 LookML community (T3) | 🔴 None yet (T6) |
| Counter-Positioning | 🔴 None (T6) | 🔴 None (T6) | 🔴 None (T6) | 🟢 NL-first vs. query-first (T3) |
| Switching Costs | 🟢 Dashboard + skill investment (T2) | 🟢 M365 bundle lock-in (T1) | 🟡 LookML model investment (T2) | 🔴 Low — 400 customers, minimal workflow embedding (T6) |
| Branding | 🟢 "Gold standard in BI" (T1) | 🟢 "Already in your stack" (T1) | 🟡 "For data teams" (T3) | 🔴 Unknown (T6) |
| Cornered Resource | 🟡 Viz grammar / Hyper engine (T3) | 🟢 M365 distribution (T1) | 🟡 BigQuery integration depth (T1) | 🟡 NL-to-analytics model trained on 400 customer query patterns (T6: nascent but proprietary) |
| Process Power | 🟡 15+ years BI (T3) | 🟡 Enterprise motion (T3) | 🟡 Google engineering (T3) | 🔴 None (T6) |
**Counter-positioning is the startup's only power — and it is real (M).** The three incumbents have massive installed bases of users who invested in learning SQL, DAX, LookML, and dashboard building. Serving the "non-technical user who asks questions in English" requires a fundamentally different product architecture (NL-first, not query-first with NL bolted on). For incumbents to fully serve this user, they would need to deprioritize the power-user workflow that generates their switching costs and revenue. They cannot do this without cannibalizing their core. This is textbook Helmer counter-positioning.
However, counter-positioning has a shelf life. Microsoft's Copilot is the most credible threat to eroding this counter-positioning because Copilot is designed as a conversational interface layered on top of existing Microsoft products. **If Power BI + Copilot delivers 70%+ of the NL analytics experience within 18 months, the counter-positioning window closes.** (M) [EVIDENCE-LIMITED: validate with user testing of Power BI Copilot vs. native NL analytics]
**Wardley Map Findings — Where Incumbents Are Misallocated**
| Component | Evolution Stage | Incumbent Allocation | Startup Opportunity |
|---|---|---|---|
| Dashboard rendering | Commodity | Tableau/Power BI invest heavily in visual customization (inertia from 15 years of differentiation on this axis) | Skip entirely — use good-enough defaults. This is wasted R&D from the startup's perspective. |
| Query engine (SQL/DAX) | Product → Commodity | All three invest in proprietary query languages | Skip — connect to customer's existing warehouse and auto-generate SQL. The query layer is commoditizing. |
| NL-to-analytics AI | Genesis → Custom | All three are bolting NL onto existing query architectures (retrofit, not native) | **This is where the startup should be custom-building.** The NL-to-analytics model is genesis-stage and the startup's architecture is natively optimized for it. |
| Workflow embedding (Slack/email/CRM) | Genesis | No incumbent has meaningful investment here | **First-mover opportunity.** Analytics embedded in workflow is genesis-stage — no competitor has claimed it. |
| Data anomaly detection (proactive) | Genesis → Custom | Minimal incumbent investment; Tableau/Salesforce acquired some capabilities but not integrated | **Second first-mover opportunity.** Proactive push analytics is a new paradigm the incumbents' pull-based architecture is not designed for. |
**Key finding:** Incumbents are over-investing in commodity components (dashboard rendering, visual customization) due to organizational inertia. The startup should invest exclusively in genesis-stage components (NL-to-analytics model, workflow embedding, proactive anomaly detection) where no incumbent has structural advantages. (H)
**Aggregation Theory — Kill Zone Analysis**
| Question | Tableau | Power BI | Looker | Startup |
|---|---|---|---|---|
| Owns user relationship? | 🟡 Partial — many users access via embedded/portal | 🟢 Yes — M365 identity | 🟡 Partial — via Google Cloud | 🟡 Direct but small base |
| Marginal cost near zero? | 🟡 Per-seat licensing adds cost | 🟢 Bundled in M365 E5 — near zero | 🟡 Per-user pricing | 🟡 AI inference costs are material |
| Acquisition costs decreasing? | 🟡 Salesforce cross-sell helps | 🟢 Yes — M365 installed base is automatic distribution | 🟡 Google Cloud tie reduces CAC | 🔴 Startup CAC is high — every customer acquired through direct effort |
**Kill Zone Assessment:**
| Zone | Status | Rationale |
|---|---|---|
| Enterprise BI (dashboard building, SQL analytics) | 🔴 **KILL ZONE** | Power BI is bundled with M365. Competing for analyst users who already have Power BI for "free" is economically impossible. Tableau and Looker also have strong switching costs. Do not enter. (H) |
| Enterprise procurement (top-down IT sale) | 🔴 **KILL ZONE** | Microsoft/Salesforce/Google own the enterprise relationship. Enterprise procurement will always default to the vendor already in the stack. (H) |
| NL analytics for non-technical operators | 🟢 **OPEN SPACE** | No incumbent serves this user well today. Counter-positioning protects for 12-24 months. Product-led acquisition bypasses enterprise procurement kill zone. (M) |
| Embedded/workflow analytics (Slack, email, CRM) | 🟢 **OPEN SPACE** | No incumbent has invested here. This is a new distribution surface the startup can own. (M) [EVIDENCE-LIMITED: validate demand for embedded analytics with customer development] |
| Proactive anomaly detection | 🟡 **CONTESTABLE** | Incumbents have the data access to build this. The startup's advantage is architectural (push-first vs. pull-first), but this is replicable in 12-18 months. (L) |
**Strategic Recommendations (O->I->R->C->W Cascade)**
**Recommendation 1: Position as "Analytics for Operators" — Not "AI-Powered BI"**
- **Observation** [T2, T6]: 80% of business users (operators: sales managers, marketing leads, CS directors, finance partners) have data questions they cannot answer without filing a ticket with an analyst. They are non-consumers of analytics. The JTBD analysis shows this job is severely under-served.
- **Implication**: Positioning as "AI-powered BI" puts the startup in the kill zone — it invites direct comparison with Tableau/Power BI and frames the product as a substitute. Positioning as "analytics for operators" reframes the product as serving a user that incumbents do not serve and creates a new market rather than competing in an existing one.
- **Response**: Rebrand and reposition. Remove "BI" and "dashboard" from all marketing. The tagline should emphasize the operator, not the technology: "Ask your data anything" not "AI-powered analytics platform." Remove dashboard-building features from the product and redirect engineering to NL query quality and workflow embedding. Owner: CEO + CMO. Timeline: rebrand in 60 days.
- **Confidence**: H — this is a positioning choice, not a technology bet. Low-regret regardless of competitive response because it moves the startup out of the kill zone.
- **Watch**: If Power BI Copilot achieves >4.0 satisfaction score among non-technical users (tracked via G2/Gartner Peer Insights), the "non-technical user" positioning weakens and the startup needs a more specific niche.
**Recommendation 2: Cross the Chasm via RevOps at B2B SaaS Companies (The Head Pin)**
- **Observation** [T2]: Customer interviews reveal RevOps teams field 30+ ad-hoc data requests per week. Existing customers with the highest NPS are RevOps teams at SaaS companies. The whole product is closest to complete for this segment (Salesforce + Snowflake/BigQuery covers 80% of data sources).
- **Implication**: The startup is pre-chasm. Pursuing multiple segments simultaneously will burn the $40M raise without achieving dominance in any segment. Moore's bowling alley strategy requires picking one niche and owning it completely before expanding.
- **Response**: Focus 100% of go-to-market on RevOps teams at B2B SaaS companies (200-2,000 employees). Build the whole product for this segment: Salesforce connector, Snowflake/BigQuery auto-model, 25 pre-built RevOps question templates, pipeline anomaly detection. Deprioritize all other segments until RevOps NPS exceeds 50 and market penetration exceeds 5% of addressable accounts. Owner: CRO + CPO. Timeline: 12 months exclusive focus.
- **Confidence**: M — assumes RevOps pain is acute enough to drive standalone tool adoption and that the SaaS RevOps community is tight enough for reference-based growth. If references do not propagate (measured by inbound/outbound ratio), the head pin selection is wrong.
- **Watch**: Inbound-to-outbound pipeline ratio for RevOps segment. If inbound does not exceed 40% of pipeline within 6 months of focused effort, the community-driven growth thesis is wrong and a different head pin is needed.
**Recommendation 3: Build Workflow Embedding as the Distribution Moat**
- **Observation** [T6: inferred from Wardley Map]: Workflow-embedded analytics (Slack bot, email digests, CRM-native insights) is a genesis-stage distribution surface that no incumbent has claimed. Incumbents distribute through standalone applications; the startup can distribute through the tools operators already use every day.
- **Implication**: If the startup's analytics shows up in Slack at 8am with "your pipeline dropped 15% this week because 3 enterprise deals slipped — here's why," the user never opens Tableau. This is not a feature — it is a distribution strategy that bypasses the incumbent's application-layer lock-in entirely. It creates a new switching cost type: the operator's daily workflow now depends on the startup's proactive insights.
- **Response**: Ship a Slack integration that delivers proactive, NL-explained anomaly alerts to business operators. Make this the primary product surface — not a companion to a web app, but the primary experience. The web app is for drilling deeper; Slack/email is where the relationship lives. Owner: CPO. Timeline: V1 in 90 days.
- **Confidence**: M — assumes operators prefer push analytics over pull analytics and that Slack/email is the right surface. If daily digest open rates fall below 30% after 60 days, the workflow-embedding thesis needs testing on different surfaces. [EVIDENCE-LIMITED: validate with customer development before full engineering commitment]
- **Watch**: Daily Slack interaction rate per user. If <20% of users interact with the Slack bot at least 3x/week after 30 days, the surface is wrong.
**Assumption Registry**
| # | Assumption | Framework | Confidence | Evidence | Invalidation signal |
|---|---|---|---|---|---|
| 1 | Power BI + Copilot will not deliver a comparable NL analytics experience for non-technical users within 18 months | Counter-Positioning (7 Powers) | M | Microsoft's retrofitted AI on existing architecture is structurally constrained (T3: architecture analysis), but Microsoft's AI investment is massive (T1: earnings calls) | Power BI Copilot for non-technical users achieves >4.0 satisfaction on G2 within 12 months |
| 2 | Non-consumption is a larger opportunity than competitive substitution | JTBD, Christensen New-Market Disruption | H | Only ~20% of employees at data-rich companies use BI tools today (T4: Gartner estimates). 80% of the TAM is unaddressed by incumbents. | Market research shows >50% of non-BI-users say "I have no data questions" — meaning the job does not exist, not that it is under-served |
| 3 | RevOps at B2B SaaS is the right chasm-crossing beachhead | Crossing the Chasm | M | Highest NPS segment in current customer base (T2: NPS data). Tight community for reference propagation (T3: community analysis). | RevOps segment shows <10% trial-to-paid conversion after whole product is complete, suggesting the pain is not acute enough to drive adoption |
| 4 | Workflow-embedded analytics (Slack/email) will become the primary analytics surface for operators | Wardley Mapping, Blue Ocean | L | This is a thesis, not a finding. No precedent for analytics consumption shifting to messaging platforms at scale (T6: first-principles reasoning only). | Daily active Slack analytics users plateau at <15% of total user base after 6 months |
**Adversarial Self-Critique**
**Weakness 1: The "non-consumption" opportunity may be smaller than estimated.** This analysis assumes 80% of business users have unmet data questions. But many of these users may genuinely not need data access — they rely on analysts deliberately, and their workflows function well with weekly reports. If the "non-consumer" population is actually 30% rather than 80%, the addressable market is 3x smaller and the venture-scale economics do not work. The analysis lacks Tier 1 evidence for the non-consumption estimate.
**Weakness 2: Counter-positioning may erode faster than the 18-month window assumed.** Microsoft has demonstrated the ability to integrate AI into productivity tools at remarkable speed (Copilot in Word, Excel, Teams, and Power BI within 12 months). If Power BI Copilot is delivered as a natural-language-first experience (not SQL-first with NL on top), the counter-positioning argument collapses. The architectural constraint argument (incumbents cannot rebuild around NL) may underestimate Microsoft's willingness to build parallel architectures. The startup is betting on incumbent inertia — the most common and most dangerous bet in tech strategy.
**Weakness 3: The RevOps head pin may be too narrow to build a venture-scale company.** B2B SaaS companies with 200-2,000 employees that have RevOps teams is a segment of perhaps 5,000-10,000 companies globally. Even at $20K ACV, the TAM ceiling for this beachhead is $100-200M — enough for a niche business, not enough for a venture outcome on a $40M raise. The bowling alley strategy depends on expansion into adjacent niches (Marketing Ops, Finance) working smoothly, which is not guaranteed. If RevOps references do not carry weight with Marketing Ops buyers, each niche requires a separate go-to-market motion and the capital efficiency thesis breaks.
### What Changed
- **JTBD analysis replaced "target non-technical users" with a structured job map** that identifies exactly which jobs are over-served (dashboard building — kill zone), under-served (ad-hoc questions — primary opportunity), and unserved (proactive anomaly detection — secondary opportunity). The generic output listed "specific use cases" without determining which ones were structurally defensible versus which were kill zones.
- **Blue Ocean Strategy Canvas and ERRC grid made the positioning concrete and falsifiable**: eliminate dashboard building, eliminate query languages, create workflow-embedded analytics, create proactive anomaly detection. The generic output said "don't compete on dashboards" but provided no framework for what to build instead or what to explicitly stop building.
- **Crossing the Chasm analysis identified the startup as pre-chasm and prescribed a specific bowling alley head pin** (RevOps at B2B SaaS, 200-2,000 employees) with four criteria for why this niche was selected and measurable indicators for whether it is working. The generic output said "target specific use cases" without adoption-stage awareness or a sequencing strategy.
- **Kill zone mapping using Aggregation Theory created a clear red/green/yellow map** showing exactly where the startup dies (enterprise BI, enterprise procurement) versus where it has open space (NL for operators, workflow embedding). The generic output mentioned Power BI bundling risk but did not map kill zones systematically or identify safe corridors.
- **Wardley Mapping exposed incumbent over-investment in commodity components** (dashboard rendering, visual customization) and identified genesis-stage components (NL-to-analytics, workflow embedding, proactive anomaly detection) where the startup has architectural advantage and no incumbent has structural positioning. The generic output said "incumbents are adding AI features" without distinguishing retrofitted capabilities from native ones.
---
*Generated using Competitive & Market Analysis skill v1.3.0 | PM Skills Arsenal*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |