Score C · 5.89/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 15, 2026

Agent Gauntlet

Agent Gauntlet runs a shipped AI copilot through 80 adversarial scenarios and returns a client-ready pass/fail PDF report plus copy-paste guardrail fixes within 24 hours.

One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.

Decide in 20 seconds

The facts that decide whether this is worth thirty days of yours.

Speculative5.89/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach on X and LinkedIn to agency owners who publicly posted in the last 30 days that they shipped or demoed an AI agent for a client, opening with a free Mini Gauntlet failure from their own bot.
Who pays

Owner or lead developer at a 1-15 person AI agency or freelance studio shipping a custom chat copilot to a client in the next 1-3 days, or one whose client just reported the bot said something wrong.

Biggest execution risk

Market demand 4.1/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.8/10.

Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.

Your first 24 hours

12 concrete actions. Tick them off as you go — nothing is saved or sent.

0/12
Entry price
$99
Solo build
5 days
30d base revenue
$3,588
30d hackathon profit
$3,063
Section 1 of 8

Product opportunity and positioning

Target customer

Owner or lead developer at a 1-15 person AI agency or freelance studio shipping a custom chat copilot to a client in the next 1-3 days, or one whose client just reported the bot said something wrong.

Why now

Agencies are shipping client copilots faster than they can test them, and open-source eval frameworks still require a weekend of YAML, API keys and CI wiring that produces nothing a client can read.

Problem

Agencies hand off a copilot after light manual testing, the client finds a data leak, an invented refund policy or a malformed tool call, and the agency absorbs unpaid rework with no evidence the agent was ever tested.

Solution

The buyer submits a system prompt, tool JSON schemas and three transcripts, pays once, and receives an automatically generated PDF with overall pass rate, six category scores, top 10 failures with quoted evidence, one guardrail patch per failure, and a JSONL regression pack.

Differentiation · It sells the finished artifact instead of the test execution: zero setup, fixed price, 24-hour turnaround, and a report that carries the agency's logo and can be forwarded or attached to an invoice.

1. Product opportunity and positioning

Arcten's original bet was that teams building AI copilots would buy infrastructure: an SDK, an edge runtime, RAG, guardrails, observability. That bet needs an enterprise sales team, and this launch has one person. Agent Gauntlet keeps the pain Arcten named, a copilot that behaves unpredictably once real users touch it, and drops the platform entirely. It sells one artifact at one price, produced automatically.

The buyer is the owner or lead developer of a 1-15 person AI agency that ships custom chat copilots to clients on OpenAI, Chatbase, Voiceflow, Lindy, n8n or custom code. The trigger event is date-bound: a client handoff in 1-3 days, or a client who just reported the bot leaked another customer's name, invented a refund policy, or called a tool with malformed arguments. At that moment the agency is absorbing unpaid rework and risking a referenceable account, with no cheap way to prove the agent was tested.

The current workaround is an open-source eval framework such as promptfoo, garak or DeepEval plus a weekend of YAML, API keys and CI wiring, or a 20-minute manual poke-around before the handoff. Both produce evidence the agency cannot forward. Agent Gauntlet's output is the product: a one-page report with an overall pass rate, six category scores, the top ten failures with quoted transcripts, one guardrail patch per failure, and a JSONL regression pack. Higher tiers carry the agency's own logo, so the report can be attached to the invoice or forwarded straight to the client.

Positioning statement: for AI agencies three days from a client handoff, Agent Gauntlet is a $299 fixed-price QA report that turns an untested copilot into a scored, shareable pass/fail PDF in 24 hours, with no setup, no call and no subscription.

JEV scored this concept 58.9 out of 100, band C. Feasibility (7.01) and speed to first revenue (7.77) are the strong criteria; market demand (4.12) and monetization potential (4.69) are the weak ones. The honest risk is therefore not whether the product can be built in five days, but whether enough agencies pay enough, often enough. This plan is built around that: outreach is timed to the handoff trigger and not to a vague quality goal, the free ten-scenario Mini Gauntlet makes every first message about a real failure in the prospect's own bot, and the $999 five-pack creates a repeat-purchase path that a single charge never would.

Section 2 of 8

Smallest sellable MVP

A single paid page: paste system prompt, tool schemas and three transcripts, pay $299 by card, receive a scored PDF report and a JSONL failure pack by email within 24 hours.

Must-have features

  • Intake form for system prompt, tool JSON schemas, three sample transcripts and an optional bot URL or OpenAI-compatible endpoint
  • Fixed six-category scenario generator producing 80 deduplicated adversarial cases with severity weights
  • Runner that executes each case against the submitted endpoint or a simulated persona and stores full transcripts
  • Judge layer combining a rubric LLM score with deterministic tool-schema validation and PII/secret regex checks
  • Every failure stored with a verbatim evidence quote; failures without evidence are dropped
  • Single-page HTML-to-PDF report: overall pass rate, six category scores, top 10 failures, one guardrail patch each
  • JSONL fix-pack download containing the failing cases and prompt snippets
  • Stripe Checkout plus webhook that enqueues the job and emails the report through Resend
  • Free ten-scenario Mini Gauntlet mode capped per email address as the outreach hook
  • Logo upload field for the Full and Agency 5-Pack tiers

Explicitly out of scope

  • No continuous monitoring, CI hooks or production traffic analysis
  • No copilot SDK, runtime, hosting or chat widget
  • No self-serve eval authoring UI or scenario marketplace
  • No login, dashboard or account area in v1
  • No SOC 2, SSO, DPA or enterprise security review
  • No human review or consulting deliverable

Demo flow (what the buyer sees)

  1. Buyer opens the intake page and pastes a system prompt and tool JSON schema
  2. Buyer adds three transcripts and, if available, a public bot URL or OpenAI-compatible endpoint
  3. Stripe Checkout collects $299 and the webhook enqueues a job
  4. Generator produces 80 tagged adversarial cases across six categories
  5. Runner executes every case and stores transcripts; the judge scores each one with evidence quotes
  6. Report generator renders the PDF, attaches the JSONL pack, and emails both within 24 hours
Build plan

Technical implementation plan

Stack

Next.js on VercelStripe Checkout plus webhookSupabase Postgres and storage for jobs, transcripts and report blobsOpenAI or Anthropic structured-output API for scenario generation and judgingInngest background jobs for the run queueResend for transactional emailPlaywright for public bot URL capture only

Architecture

Next.js handles intake, Stripe Checkout and signed report download links. A Stripe webhook writes a job row to Supabase and fires an Inngest function that runs three stages: generate 80 cases from the fixed taxonomy, execute each case against the submitted endpoint or a simulated persona while storing transcripts, then score each transcript with the rubric judge plus deterministic checks. A report builder renders HTML to PDF, stores it in Supabase, and Resend emails the signed link plus the JSONL pack. No customer data leaves the job row, and nothing requires a persistently running server.

Build steps

  1. Scaffold the Next.js app and deploy to Vercel; create Supabase jobs, transcripts and reports tables
  2. Write the six-category taxonomy with severity weights and the 80-case generator prompt returning strict JSON
  3. Add deduplication and severity sorting to the generator; validate output against a hand-written fixture
  4. Build the runner with per-case timeout, retry and full transcript capture
  5. Implement the deterministic checks: JSON-schema validation for tool calls, regexes for PII, secrets and card-like strings
  6. Write the rubric judge prompt and require an evidence quote per failure; drop failures without one
  7. Render the report template and convert to PDF; generate the JSONL fix pack from failing cases
  8. Wire Stripe Checkout, the webhook and the Inngest job trigger
  9. Send the finished report and fix pack through Resend with a signed expiring link
  10. Add the free Mini Gauntlet mode with per-email rate limiting and a smaller case set

AI components

  • Scenario generation: one structured-output call per job expanding the taxonomy into 80 tagged cases
  • Simulated persona agent: plays a hostile or confused user when only a prompt is supplied and no endpoint exists
  • Rubric judge: scores each transcript per category and returns a failure flag with a verbatim evidence quote
  • Guardrail patch writer: drafts one prompt snippet or validation rule per top-10 failure
Hardest technical risk: Judge reliability: a false positive or false negative in a paid report turns into a refund and a public complaint, so every failure must be gated by both a rubric score and a deterministic piece of evidence.
Section 3 of 8

Pricing and monetization

Mini Gauntlet

Entry offer
$99 one-time

For Solo indie founder or vibe-coded SaaS builder with one shipped AI feature

  • 20 adversarial scenarios across 3 categories
  • Scored PDF report with top 5 failures and evidence
  • JSONL of failing cases

Full Gauntlet

$299 one-time

For Agency or studio shipping a copilot to a client this week

  • 80 adversarial scenarios across all 6 categories
  • Client-ready PDF report with category scores and transcripts
  • One guardrail patch per top-10 failure
  • JSONL regression pack

Agency 5-Pack

$999 one-time

For Agency running multiple client handoffs per quarter

  • Five Full Gauntlet reports
  • Agency logo on every report
  • Priority 12-hour turnaround

Model: Three one-time, fixed-price report SKUs sold by card with no subscription, plus a repeat-purchase five-pack for agencies with multiple client handoffs.

First revenue offer: A direct message containing a screenshot of one real failure from the prospect's own public demo bot, plus: full 80-scenario Gauntlet Report with the failure list and guardrail patches, $299, delivered within 24 hours, no call required.

Expected ACV: $299

Upsell path: Offer the $999 Agency 5-Pack at the moment the first report is delivered and forwarded to a client, then re-offer a second report 5 days after each delivery so agencies with several live clients buy repeatedly within the same quarter.

Target customers
30
Revenue model
$8,970
Costs
$220
Profit model
$8,750
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach on X and LinkedIn to agency owners who publicly posted in the last 30 days that they shipped or demoed an AI agent for a client, opening with a free Mini Gauntlet failure from their own bot.

Where to find them

  • X search for 'shipped an AI agent for a client', 'built a copilot for a client', 'handed off the bot' filtered to the last 30 days
  • LinkedIn posts by people listing 'AI agency' or 'automation studio' in their headline who posted a client bot demo
  • Chatbase, Voiceflow, Lindy and n8n community forums where builders link their demo bots
  • Public demo bot links posted in AI builder Discords and Slack communities
  • Indie hacker and r/SaaS launch threads where an agency posts a live copilot URL
  • Reply threads under vendor launch posts where agencies show what they built

Exact outreach motions

  • Run the free Mini Gauntlet on the prospect's public demo bot before any message and save the single clearest failure
  • Send a DM with the failure screenshot, one sentence on what breaks at client handoff, and the $299 fixed-price offer with 24-hour turnaround
  • Follow up once after 72 hours using a different failure category from the same bot, then stop
  • Post the Mini Gauntlet link in two builder communities with one anonymized failure example and no client names
  • Publish a short anonymized failure-pattern writeup after each outreach batch so prospects see the artifact before buying
  • Pitch the $999 5-Pack to every buyer immediately after their first report is delivered

Message template

Hey - I ran your demo bot at [bot url] through 10 adversarial prompts before writing this. Case 4 got it to confirm a refund outside your stated window and case 7 leaked an internal note. Screenshot attached, both are prompt-level fixes. I run 80 of these across 6 categories and email back a scored PDF you can forward to the client, $299, back within 24 hours. Want the full run?
Week-one goal: Mini Gauntlet live, 30 personalized DMs sent each containing one real failure from the recipient's own bot, and at least 6 replies logged by end of day 7.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 1230 days planned
Week 1 · Build & validate · 7 days
Day 1Foundation

Payment rails, repo and data model

  • Open a Stripe account connected to TrustMRR and confirm zero prior customers and payments.
  • Scaffold the Next.js app on Vercel with Supabase jobs and transcripts tables.
  • Write the six-category taxonomy with severity weights.

Deliverable: Deployed skeleton with an empty intake form and a payment-ready Stripe account.

Day 2Scenario generator

80 tagged adversarial cases from one prompt

  • Write the 80-case generator prompt over the fixed taxonomy with strict JSON output.
  • Add deduplication on case text and severity tagging per category.
  • Generate one full set from a fixture agent and hand-review 20 cases.

Deliverable: A reproducible 80-case set stored in Supabase for the fixture prompt.

Day 3Runner and judge

Execute cases and score with evidence

  • Build the runner that executes cases against an OpenAI-compatible endpoint with retries.
  • Store full transcripts with latency and token counts per case.
  • Implement deterministic checks: tool-schema validation plus PII and secret regexes.
  • Draft the rubric judge prompt returning a score and one evidence quote per failure.

Deliverable: Scored transcript set for the fixture agent with evidence quotes on every failure.

Day 4Report

The artifact the buyer pays for

  • Render a one-page HTML report with pass rate, six category scores and top 10 failures.
  • Embed evidence quotes and one guardrail patch per failure.
  • Export the PDF and build the JSONL fix-pack download.

Deliverable: A finished Gauntlet Report PDF and JSONL pack for the fixture agent.

Day 5MVP liveMVP shipped

Stripe to emailed PDF, end to end

  • Wire Stripe Checkout to the webhook that enqueues the run job.
  • Send the report and fix pack by Resend within 24 hours of payment.
  • Run one test purchase end to end and fix every break.

Deliverable: MVP open for payment: intake to emailed report in one automated flow.

Day 6Prospect list

60 trigger-matched agency owners

  • Search X and LinkedIn for shipped-client-agent posts from the last 30 days.
  • Log 60 owners with handle, bot URL and post date.
  • Flag which targets expose a public demo bot versus a private endpoint.

Deliverable: A 60-row prospect sheet with bot URLs flagged public or private.

Day 7Free hook

Mini Gauntlet as the outreach weapon

  • Ship the free ten-scenario Mini Gauntlet capped per email address.
  • Run it on 20 public demo bots and save each clearest failure.
  • Publish one anonymized failure pattern publicly.

Deliverable: Live free hook page plus 20 saved failure screenshots for outreach.

Week 2 · Launch & first sale · 7 days
Day 8Outreach v1

First 25 personalized sends

  • Send 25 DMs each containing one real failure from the recipient's own bot.
  • Offer $299 for the full 80-scenario report in 24 hours, no call.
  • Log every send and reply with a follow-up date.

Deliverable: 25 personalized sends with replies logged.

Day 9Outreach v2

Volume and message testing

  • Send 25 more using a different opening failure category.
  • Rewrite the first line based on any day-8 replies.
  • Post the free hook in two builder communities.

Deliverable: 50 cumulative sends and two community posts.

Day 10Follow-up

Second touch, then stop

  • Send the 72-hour follow-up to day-8 non-responders using a second failure.
  • Reply to every inbound within two hours with no extra pitch.
  • Build a reply-rate table by message variant.

Deliverable: Follow-up pass complete with a reply-rate table.

Day 11White label

Make the artifact client-facing

  • Add logo upload to checkout for Full and 5-Pack tiers.
  • Confirm the logo renders on page one of the PDF.
  • Fix the two most common objections seen in replies.

Deliverable: Logo-ready report template in production.

Day 12First saleFirst sale target

Collect real money

  • Close the first $299 payment through Stripe Checkout.
  • Deliver the report inside 24 hours and hand-verify each top-10 failure.
  • Ask the buyer what would make a five-report pack worth $999.

Deliverable: First collected payment and one verified delivered report.

Day 13Quality audit

Judge calibration on a real report

  • Audit every failure claim in the delivered report for false positives.
  • Tighten the judge prompt using the audit findings.
  • Record turnaround time and API cost per report.

Deliverable: Calibration notes and a measured cost per report.

Day 14Second batch

25 new trigger-matched sends

  • Send 25 new DMs from the prospect sheet.
  • Re-offer the $299 report to the 10 most engaged prospects.
  • Remove anyone who asked to stop.

Deliverable: Batch two sent with an engaged-prospect re-offer list.

Week 3 · Repeat & systematize · 7 days
Day 155-Pack push

Raise average order value

  • Pitch the $999 Agency 5-Pack to every buyer with a delivered report.
  • Add the 12-hour turnaround promise to 5-Pack checkout.
  • Run the pipeline on a second fixture agent to test generality.

Deliverable: 5-Pack live in checkout and one generality test run.

Day 16Community

Find bots in public

  • Post the failure taxonomy in two AI-builder communities that allow sharing.
  • Reply to every comment with a concrete example and no link drops.
  • Collect 10 new public bot URLs from commenters.

Deliverable: Two published posts and 10 new bot URLs.

Day 17Volume

Sustain 30 sends per day

  • Send 30 personalized DMs.
  • Send the 72-hour follow-up to batch two.
  • Tally which failure category produces replies.

Deliverable: 30 sends, follow-ups done, category reply tally.

Day 18Endpoint support

Make live runs reliable

  • Harden OpenAI-compatible endpoint runs with timeouts and partial-result handling.
  • Add an explicit simulated-run label to prompt-only reports.
  • Document exactly what a buyer must supply for a live run.

Deliverable: Reliable endpoint handling and a clear intake spec.

Day 19Repeat revenue

Second report to existing buyers

  • Offer a second report to any buyer whose first was delivered over 5 days ago.
  • Send 25 new DMs.
  • Track revenue split across Mini, Full and 5-Pack.

Deliverable: Repeat-offer pass and a revenue-by-tier tally.

Day 20Publish

Show the artifact publicly

  • Publish one anonymized report excerpt as a sample artifact.
  • Send 25 DMs referencing the sample.
  • Ask two buyers for a public quote about their delivered report.

Deliverable: Public sample page plus two quote requests.

Day 21Midpoint review

Funnel math and pricing decision

  • Compute sends, replies, sales and conversion by message variant.
  • Kill the weakest variant and rewrite the best one.
  • Decide whether $299 holds or the entry tier moves.

Deliverable: A one-page funnel table and a pricing decision.

Week 4 · Scale what works · 7 days
Day 22Scale outreach

Run the winning variant

  • Send 30 DMs using the winning message variant.
  • Run Mini Gauntlet on every public bot in the new batch before sending.
  • Clear the inbound inbox once per day.

Deliverable: 30 sends and a cleared inbound queue.

Day 23Scale outreach

Keep the cadence

  • Send 30 DMs.
  • Send the follow-up pass to the day-22 batch.
  • Fix any report defect a buyer reports within 24 hours.

Deliverable: 60 cumulative sends this week and no open defects.

Day 24Content

Answer the free-tool objection

  • Publish a short writeup of one failure category with a transcript excerpt.
  • Send 20 DMs using that category as the hook.
  • Add a checkout FAQ answering why not just use promptfoo.

Deliverable: One published writeup and an updated checkout FAQ.

Day 255-Pack close

Convert warm buyers upward

  • Send a direct 5-Pack offer to all buyers and warm prospects.
  • Send 25 new DMs.
  • Confirm 12-hour turnaround is deliverable before promising it again.

Deliverable: 5-Pack pipeline list and 25 sends.

Day 26Turnaround

Protect the 24-hour promise

  • Batch generation and judging to cut median turnaround.
  • Send 30 DMs.
  • Refund any report that misses the stated turnaround without debate.

Deliverable: Measured median turnaround under 24 hours.

Day 27Quality

Hold the trust surface

  • Re-audit a random sample of 20 delivered failures for false positives.
  • Publish nothing using client names or invented numbers.
  • Send 30 DMs.

Deliverable: Audit sheet with a false-positive rate and 30 sends.

Day 28Final push prep

Set up the closing window

  • Send 30 DMs framed around the 16 December payment cutoff.
  • Email every past prospect one last time with a new failure example.
  • Prepare the Stripe-to-TrustMRR reconciliation sheet.

Deliverable: Final-batch sends and a reconciliation template.

Days 29-30 · Consolidate · 2 days
Day 29Last call

Convert the backlog

  • Send 40 last-call messages across X, LinkedIn and email.
  • Deliver every open order the same day.
  • Stop selling anything that cannot be delivered before the cutoff.

Deliverable: All open orders delivered and closed.

Day 30Close and reconcile

Verified numbers only

  • Close final sales before 13:00 UTC on 16 December.
  • Reconcile revenue, refunds, chargebacks, fees and ad spend in Stripe.
  • Submit the verified profit figure and archive every report.

Deliverable: Reconciled contest figures and a submitted entry.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.

Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).

The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.

Stated assumptions

  • Conservative: 3 Full Gauntlet sales at $299, assuming a 3% conversion on roughly 100 personalized outreach touches.
  • Base: 12 Full Gauntlet sales at $299, assuming a 4-5% conversion on roughly 270 touches plus one repeat buyer.
  • Upside: 28 purchases at a blended $335 ARPU (24 Full at $299, 2 Agency 5-Pack at $999, 2 Mini at $99), assuming 6-8% conversion on 450+ touches.
  • Payment fees assume Stripe at approximately 3.0% conservative and 3.5% base and upside, including international card mix.
  • Operating costs cover domain, Vercel and Supabase, Resend, tooling and LLM delivery at roughly $3-5 of API spend per 80-scenario report.
  • Ad spend is paid promotion only; organic DM outreach is assumed at $0.
  • Refund allowances assume one Full Gauntlet refund in base and two in upside for judged-report disputes.
  • All figures are projections built from stated assumptions, not verified revenue, not existing customers and not signed contracts.

Conservative

3 customers
$897
collected revenue · avg payment $299
Refunds
$0
Chargebacks
$0
Payment fees
$27
Paid marketing
$0
Hackathon profit
$870
Operating costs
$45
Business profit
$825

Base case

12 customers
$3,588
collected revenue · avg payment $299
Refunds
$299
Chargebacks
$0
Payment fees
$126
Paid marketing
$100
Hackathon profit
$3,063
Operating costs
$130
Business profit
$2,933

Optimistic

28 customers
$9,380
collected revenue · avg payment $335
Refunds
$398
Chargebacks
$0
Payment fees
$328
Paid marketing
$400
Hackathon profit
$8,254
Operating costs
$320
Business profit
$7,934

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,188
Payment fees (3.9%)
$46
Paid marketing
$100
Hackathon profit
$1,042
Business profit
$912

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

Scenario models from stated assumptions, not verified revenue. No customers, revenue or traction exist at launch; these are projections only and may not materialize.

Section 7 of 8

Main risks and validation experiments

Risk 1Market demand is the weakest JEV criterion (4.12): agencies may not pay $299 for a report artifact they believe they can generate themselves.

Mitigation

Time every message to a live handoff trigger, lead with a real failure from the prospect's own bot, and keep the offer to one price and one turnaround.

Validation experiment

Send 40 trigger-matched offers by day 14 and count paid conversions, not replies.

Kill criteria

Fewer than 2 paid sales by day 18: drop the Full tier to $99 and re-target indie SaaS builders with one shipped AI feature.

Risk 2Judge reliability: a single false positive or false negative in a paid report triggers a refund and a public complaint.

Mitigation

Require both a rubric score and a deterministic evidence signal before flagging a failure, and hand-audit every top-10 failure in the first ten paid reports.

Validation experiment

Audit all reported failures across the first 10 paid reports and record the false-positive rate per category.

Kill criteria

False-positive rate above 20%: stop selling the 12-hour tier and add a manual review gate before any report is emailed.

Risk 3Free open-source tools (promptfoo, garak, DeepEval) already execute these tests, so the artifact premium may not hold.

Mitigation

Sell the forwardable PDF and the zero-setup promise explicitly, and answer the free-tool objection on the checkout page rather than in DMs.

Validation experiment

Ask the first 10 prospects what they used to test their last agent and whether they forwarded the output to the client.

Kill criteria

If 7 of 10 already produce and forward their own reports, reposition to a client-facing QA sign-off pack or abandon the wedge.

Risk 4Many client agents sit behind authentication, forcing prompt-only simulated runs that buyers may dismiss as not testing the real system.

Mitigation

Label simulated runs explicitly, include the full scenario list so the buyer can rerun it, and price the simulated tier the same to avoid signalling lower value.

Validation experiment

Offer the prompt-only run to 10 prospects with private endpoints and measure acceptance versus live-endpoint prospects.

Kill criteria

If prompt-only acceptance stays under 15% across 10 offers, restrict the product to agents with a reachable endpoint.

Risk 5Automated probing of third-party public bots may breach vendor terms or hit rate limits, breaking the free outreach hook.

Mitigation

Probe only public demo bots at one request per second, honour rate-limit headers, and fall back to a prompt-only Mini run when blocked.

Validation experiment

Run 20 Mini Gauntlets on prospect bots and log block or rate-limit rates per platform.

Kill criteria

If more than half of targets block probing, replace the hook with a self-serve Mini Gauntlet link sent without a pre-run failure.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Read the official hackathon rules page and note the payment window boundaries.
  • Open a Stripe account connected to TrustMRR and confirm zero prior customers and payments.

Output: A payment account with a verified zero-transaction history.

Hours 3-5

  • Scaffold the Next.js repo and deploy a placeholder page to Vercel.
  • Create the Supabase jobs and transcripts tables with the intake schema.

Output: A deployed skeleton with an empty intake form and database tables.

Hours 6-8

  • Write the six-category taxonomy with severity weights and the strict-JSON generator prompt.
  • Generate one full 80-case set from a fixture agent prompt and dedupe it.

Output: A stored 80-case set for a fixture agent.

Hours 9-11

  • Build the runner against a single OpenAI-compatible endpoint with timeout and retry.
  • Store full transcripts with per-case metadata.

Output: Transcript capture working end to end on the fixture agent.

Hours 12-14

  • Draft the rubric judge prompt plus deterministic tool-schema and PII checks.
  • Hand-score 10 fixed transcripts and compare against model output.

Output: A calibration note listing the first disagreements and fixes.

Hours 15-17

  • Start the prospect sheet by finding 20 agency owners who posted a shipped client agent in the last 30 days.
  • Record handle, post date and any public demo bot URL.

Output: A 20-row prospect sheet ready for day-2 Mini Gauntlet runs.

Complete report

Full 30-day launch report

Read the full generated report

Agent Gauntlet - 30-Day Launch Report

Solo founder. Contest window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. Every number in this report is a projection, not verified revenue.

1. Product opportunity and positioning

Arcten tried to sell copilot infrastructure, an SDK, an edge runtime, RAG and guardrails, to product teams. That motion needs an enterprise sales team this launch does not have. Agent Gauntlet keeps the pain and drops the platform: a copilot that misbehaves after handoff, sold as a single paid artifact.

The buyer is the owner or lead developer of a 1-15 person AI agency shipping a client copilot in 1-3 days, or one whose client just complained that the bot leaked a name or invented a refund policy. Their alternative today is promptfoo, garak or DeepEval plus a weekend of YAML and CI wiring, or a 20-minute manual poke before the handoff. Neither produces something a client can read.

The wedge is the artifact, not the test execution. A scored PDF with quoted transcripts, one guardrail patch per failure and a JSONL regression pack travels to the client or onto the invoice. Price is $299, the decision happens the week a handoff is due, and delivery is automated.

JEV scored this concept 58.9 out of 100, band C. Feasibility (7.01) and speed to first revenue (7.77) are strong; demand (4.12) and monetization (4.69) are weak. Treat that demand score as the plan's main adversary: no broad AI-quality marketing, only trigger-timed outreach, plus repeat purchase through the five-pack.

2. Smallest sellable MVP

One page, one payment, one email. The customer pastes a system prompt, tool JSON schemas and three transcripts, optionally a public bot URL or an OpenAI-compatible endpoint, pays $299 by card, and receives a PDF report plus a JSONL failure pack within 24 hours. Ship exactly that before anything else. No login, no dashboard, no CI hooks. The free ten-scenario Mini Gauntlet runs on the same pipeline with fewer cases and a capped output; it is the outreach hook, not a product surface.

3. Technical implementation plan

Next.js on Vercel handles intake, checkout and signed download links. Supabase stores jobs, transcripts and report blobs. Inngest carries the queue so an 80-case run survives function timeouts. OpenAI or Anthropic structured outputs drive generation and judging. Resend delivers. Playwright exists only for capturing public bot URLs.

Build order is taxonomy, generator, runner, judge, report, payment. The generator is one structured-output call over the fixed six-category taxonomy returning 80 deduplicated cases with severity tags. The runner executes sequentially with retries and stores full transcripts. The judge combines a rubric score with deterministic checks, JSON-schema validation of tool calls and regexes for PII, secrets and card-like strings, and every failure must carry a verbatim evidence quote or it is dropped.

The hardest risk is judge reliability, not infrastructure. A false positive in a paid report is a refund and a public complaint. The mitigation is a two-stage evidence gate plus a manual audit of the first ten paid reports before anything reaches a buyer.

4. Pricing and monetization

Three one-time SKUs: $99 Mini with 20 scenarios and top 5 failures, $299 Full with 80 scenarios, patches and logo, $999 Agency 5-Pack with priority turnaround. No subscription in the first 30 days; a monthly plan at this price invites churn and a support queue.

Repeat purchase matters more than entry price, because monetization scored lowest. Push the 5-Pack at delivery time, when the buyer has just forwarded an artifact to a client and trust is highest. One agency with three live clients can absorb several reports a quarter.

5. First-customer acquisition

One channel: direct outreach on X and LinkedIn to agency owners who posted in the last 30 days that they shipped or demoed an AI agent for a client. Build a list of 60-100. Before contacting anyone, run the free Mini Gauntlet on their public demo bot and put one real failure in the message.

Message shape: a failure screenshot, one sentence on what breaks at handoff, one line with price and turnaround, no calendar link. Follow up once after 72 hours with a different failure, then stop. From day 8, target 25-30 personalized touches per day, roughly three hours alongside delivery.

Publish anonymized failure patterns after each batch so prospects see the artifact before buying. Never publish client names or invented statistics.

6. 30-day execution roadmap

Days 1-5 build the pipeline and take a live payment end to end. Day 5 is the MVP deadline; run the whole flow on a fixture agent before opening checkout.

Days 6-7 build the prospect list, run 20 Mini Gauntlets on real public bots, and publish the free hook page.

Days 8-11 run the first two outreach batches, the single follow-up, and white-label logo upload, because the first replies will ask for it.

Day 12 is the first-sale target. From here the week splits roughly 60/40 between delivery and outreach.

Days 13-21 deliver every report inside 24 hours, audit each one for false positives, pitch the 5-Pack to every buyer, and publish two anonymized failure writeups.

Days 22-30 hold 25-30 touches per day, run the last-call push before the 16 December cutoff, and reconcile Stripe against TrustMRR on the final morning. No new features after day 21 except judge accuracy.

7. Revenue and profit scenarios (projections only)

These are projections from stated assumptions, not verified revenue and not existing customers.

Conservative: 3 Full Gauntlet sales at $299, $897 gross. Refunds $0, chargebacks $0, fees $27, ad spend $0, operating $45. Hackathon profit $870; business profit $825.

Base: 12 Full Gauntlet sales, $3,588 gross. One refund of $299, no chargebacks, fees $126, ad spend $100 on one sponsored post, operating $130 for API, domain, email and tooling. Hackathon profit $3,063; business profit $2,933.

Upside: 28 purchases at a blended $335 average (24 Full at $299, 2 five-packs at $999, 2 Mini at $99), $9,380 gross. Refunds $398, chargebacks $0, fees $328, ad spend $400, operating $320. Hackathon profit $8,254; business profit $7,934.

The spread between conservative and base is almost entirely outreach volume and reply rate, both testable inside the window. Under every scenario the $100K ceiling is out of reach; the realistic outcome is a profitable low-four-figure launch and a validated wedge to expand from.

8. Main risks and validation experiments

Demand (JEV 4.12). Agencies may not pay $299 for an artifact they think they can prompt out themselves. Test: 40 trigger-matched offers by day 14, counting paid conversions rather than replies. Kill: fewer than 2 paid sales by day 18 means dropping the Full tier to $99 and re-targeting indie builders.

Judge reliability. One false positive in a paid report is a refund and a public complaint. Test: hand-audit every reported failure in the first 10 paid reports. Kill: above a 20% false-positive rate, add a manual gate and stop selling 12-hour turnaround.

Free-tool substitution. promptfoo and garak already run tests. Test: ask the first 10 prospects what they used last and whether they forwarded the output to the client. If most already forward their own reports, the price is wrong.

Simulated runs. Many agents sit behind auth, so the report may be prompt-only. Test: offer the prompt-only run to 10 prospects with private endpoints and measure acceptance. Mitigation: label it explicitly and ship the scenario list so the buyer can rerun it live.

Probing third-party bots. Automated probing may breach vendor terms or hit rate limits. Mitigation: public demo bots only, one request per second, honour rate-limit headers, prompt-only fallback.

9. First 24-hour action plan

Hours 1-2: read the official rules, open a Stripe account connected to TrustMRR, confirm zero prior payments.

Hours 3-5: scaffold the Next.js repo, deploy to Vercel, create the Supabase jobs and transcripts tables.

Hours 6-8: write the six-category taxonomy and the 80-case generator prompt; produce one full case set from a fixture agent.

Hours 9-11: build the runner against a single OpenAI-compatible endpoint with transcript capture.

Hours 12-14: draft the judge rubric and compare model scoring against 10 hand-scored transcripts.

Hours 15-17: start the prospect sheet with 20 agency owners who posted a shipped client agent in the last 30 days.

End of day one: a pipeline that can score a fixture agent, and twenty named prospects.

This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.

Related ideas

All ideas →