Why Not Buy
Founder, sole architect and builder
Stack
- TypeScript
- Next.js
- Claude Code
- PostgreSQL
- Stripe
- MCP
Numbers
- Live at whynotbuy.ai — intake through report running end-to-end
- Depth-interview rigor at survey reach, against receipt-verified purchases
- Agent-ready: studies queryable in natural language over MCP
Problem
Understanding why people buy a brand — and why they don’t — has always forced a trade-off. Focus groups deliver depth but are slow, expensive, and small. Surveys scale but stay shallow. And both usually rest on claimed behavior, so “why did you buy?” gets answered by people who may never have bought at all.
Approach
Built Why Not Buy end-to-end: an AI moderator conducts structured depth interviews — laddering and probing through a layered protocol grounded in established frameworks like means-end laddering and COM-B — with buyers whose purchases are confirmed by receipt. A separate model audits each transcript for quality rather than trusting the moderator to grade itself, and personal details are encrypted at rest and stripped before analysis. Wave-level synthesis turns the transcripts into a decision-ready report with evidence counts behind every claim. Studies are also exposed over MCP, so AI agents can query the underlying research directly instead of reading a PDF.
Outcome
Live at whynotbuy.ai, running the full pipeline end-to-end: intake and study design, panel recruiting, moderated interviews, audit, synthesis, and delivery — turning a research question into a decision in days rather than the weeks a traditional qualitative study takes. Product teams, marketers, and strategists use it to ground roadmap, messaging, and media-spend decisions in verified buyer behavior instead of stated intent.