Analyze User Request:

Analyze User Request: A Tool for Product Teams to Test Demand Before Building

This is a simple, no-frills tool for product teams who want to validate whether their idea is worth building before committing time and resources. It’s for founders, engineers, and product managers who need to answer:

• "Should we build this?"
• "How much demand exists before we start?"
• "What’s the fastest way to test without overpromising?"

It’s not a sales funnel, a pitch deck, or a hype machine. It’s a way to measure real interest from people who would actually use what you’re considering—without misleading them or overcommitting.

---

What You Get (If You Sign Up)

• Transparency: You’ll see exactly how many people are interested, where they’re coming from, and what they’re saying.
• No BS: No fake metrics, no inflated claims. Just raw data on whether your idea has traction.
• Actionable Insights: If the numbers are strong, we’ll help you decide next steps. If not, you’ll save time and avoid building something no one wants.

This isn’t about collecting emails for a newsletter or feeding a CRM. It’s about testing demand with honesty—so you can make smarter decisions faster.

---

Who This Is For (And Who It’s Not For)

✅ You if:

• You’re building something new and want to validate demand before coding.
• You’re a solo founder or small team with limited time/resources.
• You’d rather fail fast and cheaply than waste months on a product no one needs.

❌ Not for you if:

• You’re looking for a way to generate leads for your existing product.
• You want to pre-sell a product you’re already building.
• You’re uncomfortable with the idea of shutting something down if it doesn’t gain traction.

---

What Happens Next

If you’re interested in testing your idea, we’ll:

1. Publish a simple landing page on our domain (no third-party tools, no tracking beyond what’s necessary).
2. Share it in 3 relevant communities and 2 newsletters (no spam, just targeted exposure).
3. Post daily organic updates (Twitter, LinkedIn, or other platforms where your audience hangs out).
4. Track responses honestly—no hiding bad news.

After 7 days, we’ll review the results:

• If there’s clear demand, we’ll discuss next steps (could be building, pivoting, or killing the idea).
• If not, you’ll walk away with a definitive answer—and no wasted effort.

---

Why This Exists

Most product ideas fail because teams assume demand exists. This tool flips that script: prove it first, then build.

No hype. No guesswork. Just a straightforward way to answer: "Should we do this?" before writing a single line of code.

### Before acting on a user request, run this 3-item check:

1. **Restate the intent.** Paraphrase the request back to the user. If the meaning shifts, you’ve hit a communication gap early.

2. **Separate the problem from the proposed solution.** Users often describe how they want things to work; the real need is usually the underlying pain point.

3. **Check for existing coverage.** Quick search your docs, roadmap, or past tickets. Duplicate work wastes time and frustrates users.

If all three align, you’re ready to move forward. If not, pause and clarify.