Datasets:
add field notes from founder interviews: interview quality test and benchmarks
Browse files
README.md
CHANGED
|
@@ -125,6 +125,46 @@ Real framework from $50M+ ARR exits — not vague "talk to users".
|
|
| 125 |
|
| 126 |
---
|
| 127 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 128 |
## 🤝 Work With Iris
|
| 129 |
|
| 130 |
Need 1-on-1 PMF strategy or founder-led interview coaching? Reach out via [Telegram @Iris_carrot](https://t.me/Iris_carrot) or visit [gingiris.tools](https://gingiris.tools).
|
|
|
|
| 125 |
|
| 126 |
---
|
| 127 |
|
| 128 |
+
## 🆕 What's New (July 2026): Field Notes from Founder Interviews
|
| 129 |
+
|
| 130 |
+
Fresh observations distilled from our founder podcast series. They sharpen — not replace — the protocols above.
|
| 131 |
+
|
| 132 |
+
### The One-Line Test for Interview Quality
|
| 133 |
+
|
| 134 |
+
A useless interview looks like an investor pitch: you talk 80% of the time and the user quietly zones out. A good interview looks like a walkthrough: the user shares their screen and drives, showing you their real use cases step by step.
|
| 135 |
+
|
| 136 |
+
The uncomfortable constant behind this test — the user journey you imagined and the journey users actually take are almost never the same. Screen sharing is how you find the gap; talking at users is how you hide it.
|
| 137 |
+
|
| 138 |
+
### "Willing to Pay" Is Not Paying
|
| 139 |
+
|
| 140 |
+
Saying "I'd pay for this" in an interview and actually entering a card number run on two different logics. Interview answers are social; payments are economic. Treat stated willingness as a hypothesis, then validate it with real payment behavior — a paywall, a pre-order, a paid pilot — before you count it as demand.
|
| 141 |
+
|
| 142 |
+
### Benchmark Anchors (Reported)
|
| 143 |
+
|
| 144 |
+
- Gamma, HeyGen, and Lovable reportedly ran on the order of 500–1,000 user interviews within roughly their first 6 months — before scaling spend.
|
| 145 |
+
- The counter-example burn path: skipping that phase and buying growth instead, at tens of dollars per signup and hundreds of dollars per paying user, with no compounding insight to show for it.
|
| 146 |
+
|
| 147 |
+
The order matters: interviews first, scale second.
|
| 148 |
+
|
| 149 |
+
### The Feedback Loop That Drives Retention
|
| 150 |
+
|
| 151 |
+
One pattern kept recurring among teams with strong retention:
|
| 152 |
+
|
| 153 |
+
1. A deep user writes a 2,000-word review with screenshots.
|
| 154 |
+
2. The whole team breaks it down together, issue by issue.
|
| 155 |
+
3. Every issue gets fixed within 1–2 months.
|
| 156 |
+
4. Someone goes back and tells the user: "your issue is fixed."
|
| 157 |
+
|
| 158 |
+
Step 4 is the one most teams skip — and it is the step that closes the loop and drives retention. Feedback that visibly changes the product turns reviewers into advocates.
|
| 159 |
+
|
| 160 |
+
### Trust Benchmark (Self-Reported)
|
| 161 |
+
|
| 162 |
+
One founder's report: daily frontline chats with users built more trust in 2 months than colleagues had accumulated in over a year. Trust with users compounds at the speed of contact, not tenure.
|
| 163 |
+
|
| 164 |
+
*Distilled from 12 founder podcast interviews (2024–2026); figures are self-reported or reported.*
|
| 165 |
+
|
| 166 |
+
---
|
| 167 |
+
|
| 168 |
## 🤝 Work With Iris
|
| 169 |
|
| 170 |
Need 1-on-1 PMF strategy or founder-led interview coaching? Reach out via [Telegram @Iris_carrot](https://t.me/Iris_carrot) or visit [gingiris.tools](https://gingiris.tools).
|