Feature Vs Product Test

Feature vs. Product Test

Determine whether a startup idea is a standalone product that can become a company, or a feature that will be absorbed by larger platforms.

When to Use

• Evaluating a startup idea before committing
• Assessing competitive risk from big tech platforms
• Due diligence on investment opportunities
• Deciding whether to build, buy, or partner
• Analyzing why a startup failed (post-mortem)

Inputs

Core Framework

Marc Andreessen's insight: "If you're just building an inventory tracking tool, you're a feature. Shopify or Toast will add that in six months."

Features get absorbed by platforms that have:

• Existing user base
• Adjacent functionality
• Distribution advantage
• Engineering resources

Products become companies because they have:

• Standalone value proposition
• Network effects or data moats
• Distinct buyer/user relationship
• Defensible technical depth

Workflow

Step 1: Identify Adjacent Platforms

List all larger platforms that operate in the same space:

Ask: Who has users that would want this functionality?

Step 2: Apply the "Six Month Test"

Could a platform add this functionality in 6 months?

Step 3: Assess Defensibility

Evaluate the claimed moat:

Step 4: Check Platform Economics

Would a platform be economically motivated to build this?

Step 5: Assess Standalone Viability

Could this be a successful standalone company?

Step 6: Render Verdict

Based on the analysis, classify:

FEATURE - High absorption risk, recommend against PRODUCT - Standalone viability, can become a company BORDERLINE - Could go either way, depends on execution and speed

Outputs

Feature vs. Product Assessment

## Feature vs. Product Test: [Idea Name]

### Summary
**Classification:** FEATURE / PRODUCT / BORDERLINE
**Platform Risk:** High / Medium / Low
**Recommendation:** [Build as company / Pivot / Don't pursue]

### Adjacent Platform Analysis

| Platform | Proximity | Would They Build? | Timeline |
|----------|-----------|-------------------|----------|
| [platform] | [close/medium/far] | [yes/no/maybe] | [months] |

### Six Month Test
**Could a major platform build this in 6 months?**
[Yes/No with reasoning]

### Defensibility Assessment

| Claimed Moat | Reality Check | Durability |
|--------------|---------------|------------|
| [moat claim] | [actual status] | [high/medium/low] |

### Platform Economics
**Would platforms be economically motivated to build this?**
[Analysis of incentives]

### Standalone Viability
| Factor | Assessment |
|--------|------------|
| Sell without platform | [Yes/No] |
| Own customer relationship | [Yes/No] |
| Independent pricing | [Yes/No] |
| Value without platform | [Yes/No] |

**Standalone Score:** X/4

### Verdict

[Clear statement with reasoning]

### Recommendations

**If Pursuing:**
- [how to build defensibility]
- [what to do before platforms notice]

**If Pivoting:**
- [direction to consider]
- [how to find product not feature]

Constraints

• Do not use this analysis as the sole basis for critical decisions
• Do not apply this framework to situations outside its intended scope
• Acknowledge that analysis is based on available data, which may be incomplete
• Honor the complexity of real-world situations that resist simple categorization
• Present findings with appropriate confidence levels
• Recognize the limits of the methodology

Example

Input:

Idea: AI tool that summarizes Slack conversations and creates action items
Adjacent platforms: Slack, Microsoft Teams, Notion, Asana
Moat claims: "Better AI than competitors", "First mover advantage"

Output:

Feature vs. Product Test: Slack AI Summarizer

Summary

Classification: FEATURE Platform Risk: Critical (9/10) Recommendation: Do not pursue as standalone company

Adjacent Platform Analysis

Six Month Test

Could a major platform build this in 6 months?

Yes. In fact, they already have. Slack announced Slack AI in 2023 with conversation summaries and action item extraction. Microsoft Copilot in Teams does the same. This is core platform functionality, not a standalone business.

Defensibility Assessment

Platform Economics

Would platforms be economically motivated to build this?

Absolutely. This is a premium feature that:

• Drives platform stickiness (users stay in Slack)
• Enables premium pricing (Slack AI is paid add-on)
• Uses their proprietary data (conversation history)
• Improves core metrics (engagement, retention)

Slack and Microsoft have every incentive to build this and have already done so.

Standalone Viability

Standalone Score: 0/4

Verdict

This is a textbook feature. It has:

• Zero standalone viability
• No defensible moat
• Direct platform competition already in market
• Complete dependency on platforms that are building the same thing

The claimed moats ("better AI", "first mover") are not real. Any AI quality advantage is temporary and likely illusory given everyone uses the same foundational models.

Recommendations

Do Not Pursue as currently conceived.

If Pivoting:

• Look for workflow that platforms WON'T build (cross-platform, controversial, vertical-specific)
• Consider: cross-platform meeting intelligence (Zoom + Slack + Docs)
• Consider: vertical-specific compliance summarization (legal, healthcare)
• Find the use case platforms are economically DISincentivized to build

Error Handling

Integration

This skill integrates with the marc-andreessen expert. The assessment should be delivered with characteristic bluntness - if it's a feature, say so clearly.

Related skills:

• software-disruption-analysis - For understanding platform dynamics
• product-market-fit-diagnosis - For evaluating execution
• tam-expansion-analysis - For market sizing if product potential