Feature Investment Advisor

# Example: Feature Investment Advisor Conversation Flow

This shows a full conversation using the feature-investment-advisor skill.

---

## Scenario: Evaluating a Time Tracking Add-On

### Step 0: Initial Request

**User:**
"Should we build time tracking as a paid add-on to our project management tool?"

---

### Step 0: Context Gathering

**Agent:**
"Let's evaluate the financial impact of this feature investment. Please provide:

**Feature description:**
- What's the feature? (1-2 sentences)
- Target customer segment (SMB, mid-market, enterprise, all)

**Current business context:**
- Current MRR/ARR
- Current ARPU/ARPA
- Current monthly churn rate
- Gross margin %

**Constraints:**
- Development cost estimate (team size × time)
- Any ongoing COGS or OpEx implications?

You can provide estimates if you don't have exact numbers."

---

**User:**
"Here's our context:

**Feature:**
Time tracking add-on with start/stop timers, time reports, and invoice export. Target all segments.

**Business context:**
- MRR: $2M (1,000 customers)
- ARPA: $2,000/month
- ARPU: $200/month (average 10 users per account)
- Monthly churn: 3%
- Gross margin: 80%

**Development:**
- 2 engineers × 3 months = ~$100K dev cost
- No significant ongoing COGS (minimal compute cost)
- Might add 10-20 support tickets/month"

---

### Step 1: Revenue Connection

**Agent:**
"How does this feature impact revenue? Choose the option that best describes the revenue connection:

1. **Direct monetization (new revenue stream)** — We'll charge for this (new pricing tier, paid add-on, usage-based fee)
2. **Retention improvement (reduce churn)** — Addresses key churn reason; keeps customers from leaving
3. **Conversion improvement (trial-to-paid)** — Helps convert free/trial users to paid customers
4. **Expansion enabler (upsell/cross-sell)** — Creates upsell path or drives usage-based expansion
5. **No direct revenue impact** — Table stakes, platform improvement, or strategic value only

Choose a number, or describe a custom revenue connection."

---

**User:**
"1 — Direct monetization. We'll charge $5/user/month as an add-on."

---

**Agent:**
"Got it. You're planning to charge $5/user/month for time tracking.

**Follow-up questions:**

1. **How many users do you have total?**
   - Current: 1,000 accounts × 10 users/account = 10,000 users

2. **What adoption rate do you expect?**
   - Conservative (10-15%)
   - Base case (20-25%)
   - Optimistic (30-40%)
   - Or provide your own estimate

3. **Have you validated willingness-to-pay?**
   - Surveyed customers
   - Prototype tested
   - No validation yet"

---

**User:**
"We have 10,000 users total.

I'll go with base case: 20% adoption (2,000 users).

We've surveyed 50 customers and 30% said they'd pay $5-10/user for time tracking, so 20% feels conservative."

---

**Agent calculates:**
```
Total Users: 10,000
Adoption Rate: 20%
Users Adopting: 2,000
Price: $5/user/month

Monthly Revenue: 2,000 × $5 = $10,000/month
Annual Revenue: $120,000/year
Gross Profit: $120,000 × 80% = $96,000/year
```

**Agent:**
"Great! Based on 20% adoption at $5/user:

**Revenue Impact:**
- Monthly: $10,000 MRR
- Annual: $120,000 ARR
- Gross profit (80% margin): $96,000/year

Now let's look at costs."

---

### Step 2: Cost Structure

**Agent:**
"You mentioned:
- Dev cost: $100K (2 engineers × 3 months)
- COGS: Minimal
- Support: 10-20 tickets/month

Let me confirm the full cost picture:

**One-time development:** $100,000

**Ongoing monthly costs:**
- COGS (compute, storage): $___
- Support (est. 15 tickets/month × $50/ticket): $750/month = $9K/year
- Total ongoing: $9K/year

Does this look right?"

---

**User:**
"Yes, that's right. COGS is negligible (maybe $100/month for compute), and support is probably $750/month."

---

**Agent calculates:**
```
Development Cost (one-time): $100,000

Ongoing Annual Costs:
- COGS: $100/month × 12 = $1,200/year
- Support: $750/month × 12 = $9,000/year
- Total: $10,200/year

Net Annual Profit:
$120,000 revenu