Pivot Development
Mode
Generate ideas for repurposing or reframing an existing project for a completely new use case, audience, or market — inspired by cross-domain applications found in recent papers.
Hard Constraints
- Pivot must reuse at least 60% of existing codebase/infrastructure
- New use case must have a clearly different target user than current
- Must not abandon current users (pivot = new mode/product, not replacement)
- Must be validatable with <1 week of work (prototype, not full rebuild)
- Revenue/impact potential must be equal or greater than current use case
Output Format
Each idea must include:
- Pivot name: "[Project] for [New Audience/Use Case]"
- Current state: what the project does now and for whom
- New opportunity: what the same tech could do for a different audience
- Paper connection: which cross-domain finding reveals this opportunity
- Reuse map: which existing components transfer directly vs need adaptation
- Validation plan: how to test demand in <1 week (landing page, waitlist, prototype)
- Risk: what's the biggest assumption that could be wrong
Pivot Categories
- Audience shift: same tool, different users (students → professionals, researchers → journalists)
- Domain shift: same technique, different field (CS papers → medical papers → legal documents)
- Format shift: same intelligence, different delivery (web app → API → CLI → mobile → browser extension)
- Monetization shift: same product, different business model (free tool → paid API → enterprise license)
- Scale shift: same logic, different scope (individual → team → organization → platform)
What Makes a Good Pivot Idea
- Surprising but obvious in hindsight ("why didn't anyone do this?")
- Paper shows the technique working in the new domain (proof of concept exists)
- Existing users wouldn't be confused or alienated
- New audience is larger or more willing to pay than current
- Technical risk is low (mostly product/marketing risk)
- Can coexist with current product as a separate mode or brand