TheySaid
See how users will react, right where you build.
What is TheySaid?
Validation Debt is the cost of decisions you shipped without asking a customer. Every month your team ships more decisions: designs, tickets, PRs. The ability to check them with customers hasn't moved in a decade: schedule interviews, recruit a panel, wait two weeks. The gap fills with guesses, and guesses compound. Validation can't be a project anymore. It has to be infrastructure, running every time you ship.
See how users will react, right where you build. Put what you're building in front of real customers — or synthetic users trained on them when you need an answer in minutes — without leaving Claude, Cursor, or Jira. Nothing ships on a guess.
Features
🤖 Synthetic Audiences: Synthetic testers trained on your customer data really use the product, on screen and out loud. Every one starts from a model trained on 100,000+ hours of real usability sessions. Then it's tuned to your customers with the data you choose: call recordings, surveys, support tickets, CRM.
✨ AI Companion: Use TheySaid just like Claude Design or Claude Code. Tell Companion what you want it to do, and it does the work for you.
📊 Experience Hub: Monitor and score all of your business's critical experiences, then get recommendations on how to improve the customer experience.
🔌 TheySaid MCP: Get instant feedback (plus a prompt to fix problems) in Claude Design, v0, Replit, Bolt, and Lovable designs.
🎫 Jira Ticket Testing: In Jira (or your other ticketing tool like Linear, ClickUp, Monday), when tickets finish design status, a validation step triggers automatically, with feedback and recommendations for what to improve. No one has to remember to ask.
👥 Audiences: Create human and synthetic customer audiences that mirror your actual customers, and reuse them automatically anytime you use MCP to launch tests.
🧩 Unified Test Builder: Create a user test, interview, survey, or poll, all in one place with a simplified interface and controls.
🧠 Skills: Create and edit reusable prompts for work in the product, like executive summaries and advanced cohort analysis. Build it once. Run it forever.
📱 Mobile Testing: Get feedback on websites and mobile prototypes, plus Android and iOS apps.
🎬 Clips & Highlight Reels: Create short clips of the important moments in your videos, or stitch several together into a highlight reel.
🛡️ Screeners and Response Quality Monitor: Screeners make sure only your desired audience gives you feedback. The Response Quality Monitor uses AI to review every video and response and decide if it's good enough to include in your analysis.
🎨 UI 4.0: A beautiful, modern redesign with dozens of visual and UX enhancements.
And more: advanced intercepts, auto-translation, intro videos, and matrix questions.
Stop shipping decisions nobody validated. 🚫
Try 4.0 FREE → https://www.theysaid.io/v4
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
If you reach out to a content creator and their email is at sunsetagency.com or something — any agency sounding, you're too late. Those agencies exist to eliminate the alpha that you are trying to create. If they have a Gmail in their bio and they have 5-10K followers, good engagement, that's a really nice sweet spot.
Hire content creators, not influencers — Gmail in the bio beats agency.com
Zack's tactical screen for creators: look at the bio email. Agency emails mean the creator's pricing and earnings are already optimized against you. Gmail addresses on 5-10K-follower accounts with strong engagement are undermonetized, high-output, and willing to actually create — the real growth alpha.
the highest chance of feature adoption and customer retention comes from features that align with the job that the customer needs to do with the tool... features that did something outside that scope were often ignored and complained about like we considered integrating other systems that they may have used or building communication features between teachers but those things were underused or unused at all
Build only features aligned to the specific job-to-be-done your tool exists for
Audit every feature request against the single job your tool solves. FeedbackPanda existed to help teachers ship written student feedback faster. "Communicate with other teachers" sounded reasonable but had zero adoption — outside the job. "Share feedback templates across teachers" sat directly inside the job and exploded adoption + network effects. The pull to add adjacent features is always there; the discipline is to refuse anything that doesn't make the core job faster or easier.
There's a play for whatever you're stuck on.
Read all 2722 playbooks