| Aspect | Definition |
|---|---|
| Primary Goal | Understand the choice set and decision criteria that app-builders use to choose a login process and tool, and the down-the-road pain that can arise with a wrong choice. |
| Success Signals | • Quantified willingness‑to‑adopt: ≥ 30 % of target users rank the SDK login as their first or second choice in a realistic selection scenario. |
| • Clear split for flagship claims (cross‑app identity, account merging, alias‑based payments). * table stakes functionality (what would kill the product) | |
| Decision Points | (1) Invest, pivot, or kill. |
| (2) If invest → which three features ship in v 0.1. | |
| (3) For each buyer persona (dev vs PM), what initial marketing copy must address. |
| ID | Hypothesis | Type | Metric / Evidence |
|---|---|---|---|
| H1 | “Friction‑free first login” is a priority for ≥ 50 % of small‑team builders. | Confirmatory | % ranking it #1 in card‑sort |
| H1.5 | No-friction initial login creates problems in the future with split accounts, limits to data access, etc that the Product lead suffers. | Exploratory (List of common problems, ideally ranked by pain and frequency) | |
| H2 | Builders will pay (time / money) to lower frictions created via multiple social sign‑ins. | Exploratory → Quant | Qual pain‑intensity codes + Likert price sensitivity |
| H3 | Decision authority skews toward developers in early‑stage teams, but toward PMs in scale‑ups. | Descriptive | Role of final selector vs company headcount |
| H4 | Existing SDKs (Auth0, Supabase, Firebase Auth, WalletConnect, Privy, Magic) leave a gap in cross‑app session continuity. | Gap analysis | Competitor teardown & feature‑parity matrix |
| Week | Stream | Technique | Sample / Artefact | Output |
|---|---|---|---|---|
| 1 | Discovery | • Desk research (market + patents) | ||
| • Extended competitor analysis | 8 competing SDKs & naming services | Desk report + Competitor matrix | ||
| Quant validation survey | Goals and frustrations | n≈50 | Survey analysis plus recruiting screener | |
| 2 | Qual JTBD interviews | 1‑hour remote contextual interviews (recruit payment‑flow builders oversample) | n≈10 builders | Raw transcripts + per‑call TL;DR + Interview report |
| 3 | Insight dissemination | Real‑time Miro wall + weekly 30‑min read‑out | General report | Stakeholder alignment |
| Segment | Rationale | Channels |
|---|---|---|
| Indie web3 dApp devs (3 ppl) | High pain, fast feedback | GitHub Issues, Devpost hackathons, Farcaster, Lens |
| VC‑funded SaaS builders (3 ppl) | Purchasing power, PM involvement | Product‑Led Growth Slack, YC batch forums |
| Enterprise PMs (tier‑5) | Understanding of down-stream pain points | LinkedIn outbound, expert networks |
Incentive:
Competitor teardown sheet
Survey
Semi‑structured interview guide