Validate Idea (validateidea.io) platform help — a no-code smoke-test landing-page builder for validating a startup idea before you build it: spin up a validation page in minutes (drag-and-drop, AI, or code editor), point a custom domain, and read real demand from built-in analytics, session replays, and forms/surveys capturing email signups, comments, and feature requests. One-time/lifetime pricing gated by number of ideas (Starter/Growth/Pro); UI-only — NO public API, webhooks, Zapier, or MCP. Use when building a smoke-test or fake-door landing page in Validate Idea, reading its conversion analytics or replays, choosing between the one-time plans, worrying signups are inflated by warm traffic or vanity metrics, or asking how to export data without an API. A signup is interest, not proof — set a go/no-go threshold and escalate to a pre-sale. Do NOT use for the validate-before-building method or comparing idea validators (use /sales-idea-validation), or building a full marketing funnel (use /sales-funnel).
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
sales-validateidea
description
Validate Idea (validateidea.io) platform help — a no-code smoke-test landing-page builder for validating a startup idea before you build it: spin up a validation page in minutes (drag-and-drop, AI, or code editor), point a custom domain, and read real demand from built-in analytics, session replays, and forms/surveys capturing email signups, comments, and feature requests. One-time/lifetime pricing gated by number of ideas (Starter/Growth/Pro); UI-only — NO public API, webhooks, Zapier, or MCP. Use when building a smoke-test or fake-door landing page in Validate Idea, reading its conversion analytics or replays, choosing between the one-time plans, worrying signups are inflated by warm traffic or vanity metrics, or asking how to export data without an API. A signup is interest, not proof — set a go/no-go threshold and escalate to a pre-sale. Do NOT use for the validate-before-building method or comparing idea validators (use /sales-idea-validation), or building a full marketing funnel (use /sales-funnel).
argument-hint
[describe what you need help with in Validate Idea]
Validate Idea (validateidea.io) is a no-code smoke-test landing-page builder for founders,
makers, and vibe coders who want to test demand before writing a line of code. You describe or
design a page (drag-and-drop editor, AI editor that generates a page from a prompt, or a code
editor for custom HTML), get it live on a custom domain in ~5 minutes, drive a little traffic,
and read who's interested, what they care about, and how much demand exists from built-in
analytics (page views, conversion rate, engagement), session replays, and forms/surveys
that capture email signups, user comments, and feature requests.
Its job in the validator market is the opposite of an AI "score my idea" tool: it doesn't grade your
idea — it builds the real demand test (the fake-door / smoke-test landing page). That means the risk
isn't a hallucinated score; it's a landing page that manufactures fake demand if you drive the wrong
traffic or measure the wrong thing. Pricing is a one-time / lifetime purchase (no subscription),
gated by the number of ideas you can run (Starter/Growth/Pro).
Step 1 — Gather context
Ask only what you need to answer well:
What's the goal? Building/designing the page, driving traffic to it, reading the analytics/replays
correctly, choosing a plan, or automating/exporting the data (an API question).
What evidence do they already have? A hunch, an AI validator score, an audience/waitlist. If they
only have an AI score, the landing page is the next rung — the real test.
How will they drive traffic? Cold + targeted (a niche community, a small ad) gives real signal;
friends / their own audience (warm traffic) inflates conversion — flag this early (see Step 4).
What's their go/no-go threshold? If they haven't set one, help them set it before the test (a
commonly cited bar is ~5%+ of targeted visitors taking the action).
Skip-ahead: if the page is already live and they just want to read the numbers, jump to Step 4.
Step 2 — Route or answer directly
"Is my idea validated because the page got signups?" → answer here, then hand the go/no-go to a
real-behavior framing via /sales-idea-validation (a signup is interest, not willingness-to-pay).
Comparing Validate Idea vs AI validators (Validator AI, IdeaProof, DimeADozen, WorthBuild…) →
. Name the split first: those an idea; Validate Idea it.
/sales-idea-validation
score
tests
Building a full marketing funnel / multi-step sales page (upsells, checkout, email automation) →
/sales-funnel (Validate Idea is a single validation page, not a funnel builder).
Driving traffic to the page and growing the pre-launch waitlist → /sales-audience-growth.
Sequencing the signups into outreach → /sales-cadence + /sales-deliverability.
Otherwise answer directly from Step 3 / the platform reference.
Step 3 — Validate Idea platform reference
For the full module list, pricing, the "automate without an API" recipe, and how to read the analytics,
read references/platform-guide.md. The essentials:
Every module is UI-only. No public API, no webhooks, no Zapier/Make/n8n, no MCP were found in
research. The built-in analytics don't export — to get data into a pipeline you inject your own
tracking/form endpoint via the Code Editor (see Step 4 and the guide's Recipe).
Editors: Drag-and-drop, AI editor (generate a page from a prompt), and Code editor (custom
HTML/CSS/JS — the one seam a developer can use).
Signal capture: Analytics (page views, conversion rate, engagement), session replays, and
forms & surveys collecting email signups, comments, and feature requests.
Publishing:Custom domains, live in ~5 minutes; multiple ideas/pages per account.
Pricing:one-time / lifetime, no subscription, gated by number of ideas — Starter (5) /
Growth (20) / Pro (50). Exact dollar figures were not published at research; confirm on the live
pricing page. Because a slot = one "idea", a pivot re-uses a slot — budget slots for iterations.
Step 4 — Actionable guidance
A landing-page signup is interest, not proof — escalate the evidence. The action ladder is
email signup < click on "buy/get started" < a card entered (pre-sale). Keep going up the ladder;
route the willingness-to-pay test and the go/no-go to /sales-idea-validation.
Drive cold, targeted traffic — warm traffic fakes the result. Friends, your existing audience, or
anyone who already knows you convert far above strangers and inflate the rate. Send the exact customer
profile from a channel where they don't know you (a niche subreddit/community, a small targeted ad),
and read the conversion of cold visitors only.
Measure the action, not vanity metrics. Page views, impressions, and replays are context, not
demand — the signal is the conversion rate on the committed action. Don't celebrate traffic or a
full replay; celebrate a stranger giving an email or clicking "buy".
Don't over-optimize the page with CRO tricks. Countdown timers, fake scarcity, and hard-sell copy
measure your marketing, not the idea — an honest page keeps the test valid. Optimize the offer's
clarity, not its pressure.
Set the go/no-go threshold before you run it. Decide the conversion bar (a common one is ~5%+ of
targeted visitors) and the minimum sample up front, so you don't rationalize a weak result after.
There's no API — automate via the Code Editor, not a nonexistent endpoint. The built-in analytics
don't export and there are no webhooks/Zapier. If they need the data in a pipeline, embed their own
form endpoint (a serverless function / a Zapier-or-Make catch-hook form / a Formspree) and their own
analytics/pixel (GA4, Plausible, PostHog) through the Code Editor. See references/platform-guide.md.
When asked Validate Idea vs an AI scorer, frame them as complementary, not rivals — then always
route the comparison out. Say the split first — Validate Idea builds the real demand test (a
landing page that measures stranger behavior) while an AI validator (Validator AI, IdeaProof,
DimeADozen…) emits an LLM opinion / score, not measured demand — then note they work together:
use the AI scorer to sharpen the pitch and find competitors, use Validate Idea to get the actual
evidence. Don't present the AI scorer as merely inferior. End every Validate-Idea-vs-a-validator
answer by pointing the user to /sales-idea-validation for the full head-to-head and the
validate-before-building method — this route is required, not optional.
Present pricing and plan limits as best-effort. One-time/lifetime with Starter/Growth/Pro idea
caps is from research, not a live quote — point the user to validateidea.io for current numbers.
If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.
Gotchas
Best-effort from research (2026-07). Validate Idea is a small indie tool whose live site blocks bots
and whose exact pricing/limits aren't broadly published — verify prices, the idea caps, and any
integration surface against the live site before relying on specifics.
A landing page can manufacture fake demand. Unlike an AI score (which hallucinates), this tool's
failure mode is a real page read wrong: warm traffic, vanity metrics, or CRO tricks produce a
flattering number that doesn't reduce build risk.
Signups ≠ willingness to pay. A waitlist email is the weakest real signal — cheap to give. The
go/no-go should rest on a click-to-buy or a pre-sale, not an inbox of emails.
No API, webhooks, Zapier/Make, or MCP. The only export is what you wire yourself through the Code
Editor — don't hunt for a Validate Idea endpoint.
One-time pricing is gated by number of ideas. Starter/Growth/Pro cap how many pages/ideas you
run; a pivot consumes a slot, so re-validation cycles eat into the cap.
Name confusion. "Validate Idea" (validateidea.io, a landing-page builder) is not the same as
the AI-scoring validators (Validator AI/validatorai.com, ValidateMySaaS, etc.) — don't conflate them.
In particular, validateidea.ai is a near-identical name but the opposite tool: an AI-report
generator (/sales-validateidea-ai), not this smoke-test page builder. Their relationship is
unconfirmed — treat them as separate products.
Custom domain + deliverability. If you collect emails to a domain you'll later send from, warm the
domain before blasting the waitlist (see /sales-deliverability).
Related skills
/sales-idea-validation — The tool-agnostic validate-before-building method: the evidence ladder,
how much conversion is enough, and how Validate Idea (a demand test) compares to AI scorers
(Validator AI, IdeaProof, DimeADozen, WorthBuild). The go/no-go lives here, on real behavior.
/sales-validateidea-ai — ValidateIdea (validateidea.ai), the near-namesake but opposite tool: an
AI-report generator (multi-section research report + a human-expert tier), not this smoke-test page
builder. Route here if the user means the .ai report tool, not the .io demand test.
/sales-funnel — Build a full marketing funnel or multi-step sales page (upsells, checkout, email
automation) — beyond a single validation landing page. Also the home of general landing-page builders.
/sales-audience-growth — Drive targeted traffic to the validation page and grow the pre-launch
waitlist the signups feed.
/sales-cadence — Sequence the captured signups into personalized outreach.
/sales-deliverability — Make sure the launch email to the waitlist lands in the inbox.
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill.
Install: npx skills add sales-skills/sales --skill sales-do -a claude-code
Examples
Example 1: "My Validate Idea page got 300 views and 45 email signups — should I build?"
User says: "45 signups off 300 visitors on my landing page. Validated?"
Skill does: Reframes 15% as promising only if the traffic was cold and targeted — asks where the
300 came from (friends/own audience = warm = discount it) and whether the 45 are emails (interest) vs
"buy" clicks (stronger). Prescribes escalating the evidence: add a "buy / pre-order" action or run a
pre-sale to a pre-set threshold, and read the conversion of cold visitors only. Routes the go/no-go and
the threshold to /sales-idea-validation.
Result: The founder tests willingness-to-pay instead of banking a warm-traffic signup rate.
Example 2: "Validate Idea or Validator AI to check my idea?"
User says: "Which one — Validate Idea or Validator AI?"
Skill does: Names the split — Validate Idea builds the real demand test (a smoke-test landing
page with analytics/replays/forms, one-time/lifetime pricing), while Validator AI scores the idea
with an LLM (market size, competitors, a number). They're complementary: use the AI scorer to sharpen
the pitch and find competitors, then use Validate Idea to get stranger behavior. Routes the full
head-to-head and the validate-first method to /sales-idea-validation.
Result: The user runs the AI score as a gut check and the landing page as the actual evidence.
Example 3: "Can I pipe Validate Idea's signups into my CRM automatically? (developer/automation)"
User says: "I want form submissions to hit HubSpot on submit."
Skill does: States plainly there's no public API, no webhooks, no Zapier/Make, no MCP and the
built-in analytics don't export. The one seam is the Code Editor: embed your own form (a
Formspree / a Make-or-Zapier catch-hook endpoint / a serverless function) and your own analytics
pixel (GA4/PostHog/Plausible) into the page, so submissions flow to your endpoint → HubSpot, not
through Validate Idea. Points to references/platform-guide.md for the embed recipe.
Result: The developer stops looking for a nonexistent endpoint and captures data at their own sink.
Troubleshooting
"The page converted great but I'm not sure the demand is real"
Check three things: traffic source (warm traffic — friends, your audience, existing followers —
inflates conversion; only cold, targeted strangers count), the metric (page views/replays are
context, not demand — the signal is the action rate), and the page (countdown timers / fake scarcity
measure your marketing, not the idea). Re-run with cold targeted traffic and an honest page, then escalate
from an email signup to a "buy" click or pre-sale. See /sales-idea-validation.
"How do I export or automate my analytics and signups?"
There's no public API, no webhooks, no Zapier/Make, no MCP — the built-in analytics stay in the
Validate Idea UI. The only automation seam is the Code Editor: inject your own form endpoint and your
own analytics/pixel so data flows to a sink you control (a serverless function, Formspree, a Make/Zapier
catch-hook, GA4/PostHog). See references/platform-guide.md for the embed pattern.
"Which plan do I need — Starter, Growth, or Pro?"
Pricing is one-time / lifetime (no subscription), gated by the number of ideas/pages — Starter
(5) / Growth (20) / Pro (50) at research (confirm live; treat as best-effort). Pick by how many ideas
and iterations you'll test: a pivot re-uses an idea slot, so if you expect to re-validate the same idea
several times, size up. If you're testing one idea once, Starter is plenty.
