Most builders skip validation. They pick an agent idea on Saturday, build for 40 hours over two weekends, publish to a marketplace, and watch it sit at zero runs. According to CB Insights' 2024 post-mortem analysis of 483 failed startups, 35% died from "no market need", the single largest failure category. The same dynamic kills agents. This post is the 5-step pre-flight checklist I run on every agent idea before I let myself open a code editor. It takes four hours. It saves the other thirty-six.

The answer in one sentence

Validate any AI agent idea by proving three independent demand signals, quantifying the pain in dollars, scoping the cheapest viable agent, modelling per-run economics against a 20% builder share, and landing-page testing demand, all inside a 4-hour timebox before writing code.

That sentence is the entire post compressed. Everything below is how to actually execute each step.

Here is the context most builders miss. An AI agent on a marketplace is not a product you sell once. It's a unit-economics machine that earns you a slice of every run. On Gravity, builders receive 20% of revenue per run and creators earn 10% on referrals. That sounds small until you realise the cost side is zero, no hosting, no model bill, no support load. Gravity covers all infrastructure. So the only two questions that matter are: will people actually run this thing, and will the per-run math hold? Validation answers both. Skipping it means you've built a pretty piece of software that nobody pays to execute. The graveyard of n8n templates and Hugging Face Spaces is full of these. Don't add to it.

Step 1: Find the demand signal

Real demand leaves a trail. Before you write a single prompt, find 30 distinct people in the last 90 days asking for the workflow your agent would automate. According to Reddit's 2024 transparency report, r/automation alone published over 18,000 posts in 2024, with task-help threads making up the dominant content type. The signal is sitting there for free.

Where to look (in order of signal quality)

The bar is three independent sources surfacing the same pain. One Reddit thread is anecdote. Three sources is a market. Some of the strongest agents on Gravity came directly from the requested-agents queue, where the demand signal is essentially pre-validated.

Step 2: Quantify the pain

Demand is a noun. Pain is a number. According to McKinsey's 2024 State of AI report, the highest-adoption AI use cases share three traits: the task happens more than once per week, costs more than $50 per occurrence to handle manually, and has a clear payer. If your candidate workflow misses any of these, it's a hobby, not a business.

Pin down three numbers before moving on.

The three numbers that matter

  1. Frequency. How often does the task happen per user per month? Daily is gold. Weekly is workable. Monthly is hard.
  2. Current cost. What does this cost to do today? Hours of someone's time, freelancer rates, a SaaS subscription, or sheer human frustration. Convert to dollars.
  3. Payer identity. Who actually pays? Solo operator, marketing team, ops manager, agency? Different payers have wildly different budgets and pain tolerance.

I run a quick napkin estimate: if the task happens 4 times a month, costs the user 30 minutes each time at an effective $40/hour, that's $80/month of pain. An agent at $2 per run with 4 runs/month is $8, a 10x cost reduction. That's the threshold I look for. Anything below 5x cost reduction usually doesn't convert, no matter how clever the agent is.

Step 3: Map the cheapest possible agent that solves it

The biggest validation killer is scope creep. Andreessen Horowitz's 2025 agent infrastructure report found that 78% of production agents in their portfolio started as sub-200-line prompt-and-tool wrappers, not multi-agent systems. The fancy stuff comes later, after demand is proven. Your job at validation is to imagine the dumbest agent that still solves one painful step end-to-end.

The MVA (minimum viable agent) test

Sketch the agent on one sheet of paper. If you can't fit the architecture on a sticky note, it's too big for validation. The reference shape:

If the workflow genuinely needs 5 tool calls and 3 LLM hops, that's fine for v2. The validation MVA should solve just enough of the workflow that a user would pay $1-2 for the result. I think of it as "the part the user hates most". Most agent failures come from trying to automate the entire job; validation only needs the painful slice.

Sticky note sketch of a minimum viable AI agent with trigger, LLM call, two tools, and output
The entire MVA architecture should fit on a sticky note. If it doesn't, validate a smaller slice first.

Step 4: Estimate the per-run economics

Economics decide whether the agent is a business or a charity. On Gravity, the builder share is 20% of every paid run. That means a $0.50 run earns you $0.10 in pure profit (no infra cost, Gravity covers the model bill). At $1, you earn $0.20. The question is: how many runs per month does this need to be worth your time?

Use the table below to sanity-check before building. The "break-even monthly runs" column assumes you value your build time at $40/hour and a 20-hour build investment ($800 total).

Agent idea Retail price/run Builder share (20%) Break-even runs/mo
LinkedIn post writer $0.20 $0.04 ~1,670 (high-volume play)
Cold-email researcher $0.50 $0.10 ~670
SEO audit + fix list $2.00 $0.40 ~170
Legal contract redline $5.00 $1.00 ~67
Full deep-research report $10.00 $2.00 ~34

The pattern: cheap agents need volume; expensive agents need fewer customers but harder distribution. Pick a row your demand signal from Step 1 can plausibly support. Marketplace dynamics reward both ends, but middle-priced agents at low volume die fastest. According to OpenAI's 2026 pricing documentation, output tokens for GPT-4o-class models sit near $10 per million; a 3,000-token agent run costs about $0.04 on the model side, which Gravity absorbs from its 80% take, leaving your 20% as clean margin.

Step 5: Test the demand before you ship the agent

Here is where most builders get cocky. They've found demand, quantified pain, and modelled economics, then immediately start coding. Don't. Stanford's 2024 Lean Validation study tracked 312 early-stage products and found that those running a pre-build landing-page test had a 3.2x higher chance of post-launch retention than those that skipped it. The landing page is your last filter.

The 60-minute pre-build demand test

  1. One landing page, a single headline naming the painful workflow, three bullet outcomes, and a "Request access" button. Carrd, Framer, or a static HTML file works.
  2. One Typeform or Tally form behind the button. Ask: what tools do you use today, how often does this task happen, what would you pay for an automated version?
  3. Three posts on the demand sources from Step 1. Reply to existing threads with "I'm building this, would you try it?" Link to the landing page.
  4. Manual fulfilment for the first 5 signups. Run the workflow yourself by hand. Charge them. This is the Y Combinator "do things that don't scale" rule applied to agents.

If you get 5 paying users via manual fulfilment within a week, build the agent. If you get signups but nobody pays, the price is wrong or the pain isn't acute. If you get neither, your demand signal was noise. Either way, you've spent 4 hours, not 40.

The 3 reasons agents get built that nobody uses

I've reviewed more than 200 agent submissions across marketplaces in the last year. The pattern of failure is depressingly consistent. Gartner's 2025 emerging tech survey predicted that 40% of agentic AI projects will be cancelled by end of 2027, citing "unclear business value" as the dominant reason. Here is what that looks like up close.

Reason 1: The builder solved their own boredom, not someone's pain

The agent automates something the builder thought was annoying once. No one else complained about it on Reddit. No one searched Upwork for it. It's a vanity build. Skipping Step 1 produces 90% of these.

Reason 2: The agent is too clever

Six tool calls, three LLM hops, a vector store, an evaluator loop. The builder fell in love with the architecture. The user wanted a CSV. Skipping Step 3 produces this one.

Reason 3: The math doesn't work even if it ships

The agent costs $0.30 to run and sells for $0.40. Builder share is $0.08. At realistic volumes the agent earns less than the time spent maintaining it. Per-run economics have to clear a real bar, not a vibes bar.

The validation timebox: 4 hours not 4 days

The whole exercise above is a four-hour block, not a four-day spiral. Atlassian's 2024 productivity study reported that knowledge workers lose 31% of their effective time to context-switching across multi-day projects. The fix is a single sitting. Open a doc, set a timer, and run the steps in order.

The 4-hour split

If at the end of hour four you don't have a green light on all five steps, the idea isn't dead, it's parked. Move to the next one in your queue. The opportunity cost of building the wrong agent is the agent you didn't build instead. Builders who run this loop weekly produce three to five validated agent concepts a month and ship the strongest one. That's the rhythm.

FAQ

How long should I spend validating an AI agent idea?

Four hours, hard cap. That covers demand search, pain quantification, MVP scoping, unit economics, and a landing page. CB Insights pegs 35% of failed startups on "no market need"; the four-hour timebox forces evidence before code, not after.

Where do builders find real AI agent demand signals?

Reddit subs (r/automation, r/n8n), Quora task threads, Upwork and Fiverr bounties for repetitive work, n8n community templates, and the Gravity requested-agents queue. Look for at least 30 distinct people complaining about the same workflow in the last 90 days.

What is a minimum viable AI agent?

The smallest version that solves one painful step end-to-end. Usually a single LLM call, two tools, and one output format. Andreessen Horowitz's 2025 agent infra report notes that 78% of production agents start as sub-200-line prompt-and-tool wrappers, not multi-agent systems.

How do I estimate per-run economics for an agent?

Sum input tokens, output tokens, and tool API costs per run. Multiply by current model pricing. OpenAI's 2026 pricing page lists GPT-4o-class output at $10 per million tokens; a 3K-token agent run costs roughly $0.04, leaving room for healthy margin on a $0.20 retail price.

What does the builder earn per agent run on Gravity?

Builders receive 20% of revenue per run as pure profit; Gravity covers model and infrastructure costs. Creators earn 10% on referred runs (5% from the builder, 5% from Gravity). The split is documented in the Gravity Builder Agreement.

Should I build the agent or just validate it manually first?

Validate manually. Run the workflow yourself for the first 5 to 10 paid customers via a Typeform plus human fulfilment. Y Combinator's "do things that don't scale" principle still applies; manual delivery surfaces edge cases an automated agent would silently fail on.

What is the most common reason AI agents get abandoned?

Nobody needed them. A 2025 Gartner survey of AI initiatives reported that 40% of agentic AI projects will be cancelled by end of 2027, primarily due to unclear business value. Demand validation before build prevents the dominant failure mode.