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

Flowproof Audit

Paste in an n8n or Make workflow export and get a scored reliability report plus drop-in patch nodes that stop silent failures, duplicate runs and untyped AI outputs before a client notices.

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.

Promising7.09/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Public replies in the n8n community forum, n8n Discord and r/n8n where builders post workflow JSON or describe silent failures.
Who pays

Owner or lead builder at a 1-10 person AI automation agency or freelance automation consultant who maintains 10-100 client n8n or Make workflows; triggered by a client-reported duplicate record, double-send, or a workflow that silently stopped producing output.

Biggest execution risk

Operational simplicity 5.5/10

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 9; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.7/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

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

0/18
Entry price
$99
Solo build
5 days
30d base revenue
$2,700
30d hackathon profit
$2,479
Section 1 of 8

Product opportunity and positioning

Target customer

Owner or lead builder at a 1-10 person AI automation agency or freelance automation consultant who maintains 10-100 client n8n or Make workflows; triggered by a client-reported duplicate record, double-send, or a workflow that silently stopped producing output.

Why now

Agencies already run client automations in n8n and Make and can export workflow JSON without an integration; one recent client-visible failure creates an immediate reason to buy a sub-$300 audit.

Problem

Client automations fail silently: missing error branches, untyped LLM output, and create-record steps without dedupe keys cause duplicate rows, double emails, and broken runs that the builder discovers only after the client complains.

Solution

Upload a workflow JSON export; a deterministic rule engine runs about 20 checks, an LLM adds severity-ranked edge cases for AI and branching nodes, and the buyer gets a scored Reliability Report, PDF, annotated workflow, and Patch Pack of copy-paste node JSON fragments.

Differentiation · It audits the workflow the buyer already runs instead of asking them to rebuild in a new builder; the output is a fix pack they can paste today, not another dashboard.

1. Product opportunity and positioning

Flowproof Audit is a reliability audit for workflows that already exist. The buyer is a 1-10 person AI automation agency or freelance consultant maintaining 10-100 client n8n or Make workflows. They are not shopping for another builder. They have a live client workflow and a recent failure: a duplicate row, a double-send, a broken LLM-to-CRM handoff, or a workflow that stopped producing output without an alert. The audit converts that panic into a scoped, paid artifact.

The wedge is narrow on purpose. The buyer can export workflow JSON without an integration or OAuth step, upload it to a public page, and pay $99 to $299 without procurement. The deliverable is a scored Reliability Report, a PDF, an annotated workflow, and a Patch Pack of copy-paste node JSON fragments. That is more useful than a generic dashboard because it ends with a fix, not another place to look.

The current workaround is manual node-by-node review, which is slow and inconsistent across 40-node graphs. Agencies also need to protect retainers: one client-visible duplicate can cost more than the audit. The product does not rebuild the workflow or execute it. It checks for missing error branches, absent retry policies, untyped AI output, missing dedupe keys, hardcoded secrets, unbounded loops and unguarded branches, then adds an LLM edge-case pass only for AI and branching nodes. The score, severity ranking and patch fragments make the report shareable inside the agency and with the end client.

Positioning: audit the workflow the buyer already runs, hand back a fix pack they can paste today. The JEV score is 70.9/100 in band B; speed to first revenue is strong, monetization is the weak point, so the launch starts with a single paid audit and only adds packs and monthly plans after the community loop produces replies and payments.

Section 2 of 8

Smallest sellable MVP

A paid no-login page where an agency owner uploads one n8n or Make workflow JSON, pays $99 via Stripe Checkout, and receives a signed report link within two minutes containing a score, per-node findings, PDF, annotated workflow, and copy-paste patch nodes.

Must-have features

  • n8n and Make JSON importer that normalizes nodes and edges
  • Deterministic rule engine with about 20 named checks
  • LLM edge-case pass limited to AI and branching nodes with typed findings
  • Scored Reliability Report rendered as markdown and PDF
  • Patch Pack exporter with copy-paste n8n node JSON fragments
  • Annotated workflow export with per-node findings
  • Stripe Checkout with no-login delivery
  • Public sample-report generator for community proof

Explicitly out of scope

  • Hosted workflow execution or scheduler
  • OAuth connections into n8n, Make or CRM accounts
  • Continuous monitoring, alerting or run-history ingestion
  • Zapier or custom-code workflow support in v1
  • Self-serve free tier or team seats
  • Done-for-you rebuild or human consulting
  • Enterprise SSO, procurement or invoicing
  • Third-party audit API

Demo flow (what the buyer sees)

  1. Buyer clicks a $99 Stripe Checkout link
  2. Buyer uploads an n8n or Make workflow JSON export
  3. Importer builds a normalized node and edge graph
  4. Rule engine returns named findings with node ids and severity
  5. LLM pass adds edge cases for AI and branching nodes only
  6. Report renders as a scored markdown page and PDF
  7. Patch Pack and annotated workflow are emailed as signed links
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres and storageStripe Checkout and webhooksOpenAI or Anthropic APITypeScript deterministic rules engineZod for typed LLM output validationReact-PDF or Playwright for PDF renderingResend for delivery emailSigned URL storage for report access

Architecture

Next.js App Router handles upload, checkout, report pages and sample pages. Supabase stores raw workflow JSON, findings, scores and generated PDFs. The TypeScript rule engine parses n8n and Make exports into a normalized graph and returns named findings. The LLM pass receives only AI and branching node excerpts and returns Zod-validated JSON. Report renderer combines rule and LLM findings into markdown, PDF, annotated export and patch fragments. Stripe webhook marks the order paid and triggers Resend with a signed report link.

Build steps

  1. Scaffold Next.js, Supabase and Stripe test project
  2. Define normalized node and edge schema
  3. Collect 5 n8n and 3 Make export fixtures
  4. Build n8n and Make importers
  5. Implement 20 named rule checks
  6. Add severity weights and score calculation
  7. Add LLM edge-case prompt with Zod validation
  8. Render markdown report page and PDF
  9. Generate Patch Pack and annotated workflow
  10. Wire Stripe Checkout and webhook order state
  11. Send signed report link with Resend
  12. Deploy paid flow and public sample pages

AI components

  • LLM edge-case pass for AI and branching nodes only
  • Typed JSON validation on every LLM finding
  • No LLM in deterministic checks or scoring
Hardest technical risk: Parser drift across n8n and Make export variants; one unhandled shape can produce a false clean report and destroy trust in a small community.
Section 3 of 8

Pricing and monetization

Single Audit

Entry offer
$99 one-time

For Solo automation freelancer or in-house ops builder

  • Reliability Report and PDF for one workflow
  • Patch Pack of drop-in nodes
  • Annotated workflow export

Agency Pack

$299 one-time

For 2-10 person automation agency auditing client deliverables

  • Five workflow audits
  • White-label PDF the agency can send to its client
  • Patch Packs for all five
  • Priority email turnaround

Agency Monthly

$149 / month

For Agencies shipping new client workflows weekly

  • Unlimited audits
  • Report archive with shareable links
  • Rerun an audit after patching

Model: One-time audit credits plus a monthly agency subscription, all sold through Stripe Checkout with no login.

First revenue offer: Send a free audit of one client workflow, then a $99 Stripe link for the full report and Patch Pack on that same workflow.

Expected ACV: $99

Upsell path: $99 single audit -> $299 five-pack for agencies with more than three client workflows -> $149 monthly unlimited audits after the agency ships weekly.

Target customers
70
Revenue model
$10,430
Costs
$160
Profit model
$10,270
Section 4 of 8

First-customer acquisition

Primary channel

Public replies in the n8n community forum, n8n Discord and r/n8n where builders post workflow JSON or describe silent failures.

Where to find them

  • n8n community forum questions with attached workflow JSON
  • n8n Discord help and workflow channels
  • r/n8n posts asking why a workflow duplicated or stopped
  • Make community forum blueprint questions
  • Public n8n template pages with comments
  • LinkedIn posts from automation agency owners mentioning client delivery

Exact outreach motions

  • Reply with 2-3 specific findings from their public JSON and one patch snippet
  • DM 15 worst-scoring posters offering a free full audit of one client workflow
  • Post one public sample report card daily with an anonymized workflow
  • Email 20 small automation agencies from their public sites with a sample audit
  • Follow up day 3 on free audits with the $99 link
  • Offer the $299 five-pack after a second workflow request

Message template

I ran your public n8n workflow through a reliability audit. It flags [node] for a missing error branch and [node] for no dedupe key. I can send the full scored report and two patch nodes free for feedback. Want it?
Week-one goal: Publish 5 sample report cards, reply to 30 relevant posts, deliver 10 free audits, and collect the first $99 payment by day 9.
Section 5 of 8

30-day execution roadmap

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

Importer

  • Scaffold Next.js, Supabase and Stripe test project
  • Define normalized node and edge schema
  • Collect 5 n8n and 3 Make export fixtures
  • Build JSON importer for n8n export

Deliverable: Importer CLI and fixture set

Day 2Rule engine

Checks

  • Implement 20 named checks
  • Add severity and score weights
  • Write tests for 3 broken fixtures
  • Expose /api/analyze

Deliverable: Rule engine with test output

Day 3Edge cases

LLM pass

  • Draft typed edge-case prompt
  • Validate JSON with Zod
  • Limit pass to AI and branch nodes
  • Test on 10 node excerpts

Deliverable: Edge-case findings module

Day 4Report

PDF and Patch Pack

  • Render markdown report page
  • Generate PDF
  • Emit copy-paste n8n node fragments
  • Add annotated workflow export

Deliverable: Sample report and Patch Pack

Day 5CheckoutMVP shipped

Payment and delivery

  • Wire Stripe Checkout
  • Handle webhook and order state
  • Send signed report link with Resend
  • Deploy paid flow

Deliverable: Live $99 checkout

Day 6Sample loop

Public reports

  • Build sample report generator
  • Publish 3 template audits
  • Add CTA to $99 audit
  • Track page views

Deliverable: 3 public sample pages

Day 7Listening

Leads

  • Collect 30 recent forum, Discord and Reddit posts
  • Reply to 10 with specific findings
  • DM 5 worst posters
  • Save lead list

Deliverable: 15 warm leads

Week 2 · Launch & first sale · 7 days
Day 8Soft launch

Community

  • Post sample audit in n8n forum
  • Post in n8n Discord
  • Post in r/n8n
  • Answer every comment

Deliverable: 3 channel posts live

Day 9First saleFirst sale target

Conversion

  • DM 15 free-audit leads
  • Deliver 5 free audits
  • Send $99 links
  • Follow up same day

Deliverable: First paying customer target

Day 10Accuracy

False positives

  • Review 5 audit results
  • Fix two noisy checks
  • Document rule logic
  • Rerun samples

Deliverable: Accuracy log

Day 11Agency pack

$299 offer

  • Build 5-audit credit flow
  • Add white-label PDF toggle
  • Create $299 Checkout
  • Write agency offer page

Deliverable: Agency Pack live

Day 12Outreach

Agencies

  • DM 20 agency owners
  • Email 10 public agencies
  • Offer sample audit
  • Book 5 replies

Deliverable: 5 agency conversations

Day 13Proof content

Teardown

  • Publish one anonymized teardown
  • Share in Discord
  • Add CTA
  • Reply to questions

Deliverable: Teardown post

Day 14Review

Funnel

  • Review visitors, audits and sales
  • Fix top objection
  • Tune message
  • Update lead list

Deliverable: Metrics sheet

Week 3 · Repeat & systematize · 7 days
Day 15Monthly

Subscription

  • Create $149 monthly plan
  • Add report archive links
  • Add rerun-after-patch flow
  • Publish monthly offer

Deliverable: Agency Monthly live

Day 16Referral

Sharing

  • Add shareable report badge
  • Create referral code
  • Email past buyers
  • Ask for one intro

Deliverable: Referral kit

Day 17Distribution

Newsletters

  • List 20 automation newsletter authors
  • Send sample audit pitch
  • Offer free audit
  • Track replies

Deliverable: Outreach list

Day 18Make

Support

  • Test 5 Make blueprints
  • Add Make-specific checks
  • Document limits
  • Publish Make sample

Deliverable: Make audit sample

Day 19Trust

Methodology

  • Publish rule methodology page
  • Add privacy and deletion page
  • State no OAuth requirement
  • Add refund policy

Deliverable: Trust pages

Day 20Case proof

Before and after

  • Anonymize one fixed workflow
  • Publish score change
  • Send to 20 leads
  • Pin in community

Deliverable: Case post

Day 21Pipeline

Objections

  • Review all objections
  • Rewrite offer
  • Follow up 20 leads
  • Update pricing FAQ

Deliverable: Revised sales script

Week 4 · Scale what works · 7 days
Day 22Sample scale

Public audits

  • Generate 10 public audits
  • Schedule daily posts
  • Reply within 2 hours
  • Log inbound leads

Deliverable: 10 report cards

Day 23Monthly push

Repeat agencies

  • Target 10 repeat agencies
  • Offer $149 plan
  • Send archive demo
  • Follow up day 2

Deliverable: 3 monthly conversations

Day 24Refund guard

Scope

  • Add preflight JSON check
  • Clarify supported exports
  • Show sample before pay
  • Update refund terms

Deliverable: Refund policy live

Day 25Cost control

LLM

  • Cache findings by hash
  • Trim prompt tokens
  • Log cost per audit
  • Keep cost under $0.30

Deliverable: Cost dashboard

Day 26SEO

Checklist

  • Publish n8n reliability checklist
  • Add comparison page
  • Link sample reports
  • Submit sitemap

Deliverable: 2 SEO pages

Day 27Direct sales

Close

  • DM 25 warm leads
  • Send $299 pack to agencies
  • Follow up past free audits
  • Log every reply

Deliverable: 5 sales conversations

Day 28Final push

Bundle

  • Email all leads
  • Post last-call sample
  • Offer $99 single or $299 pack
  • Answer objections

Deliverable: Final offer sent

Days 29-30 · Consolidate · 2 days
Day 29Close

Pipeline

  • Follow up all unpaid links
  • Send last-call reminders
  • Ask for referrals
  • Fix delivery issues

Deliverable: Closed pipeline

Day 30Handoff

Metrics

  • Tally verified revenue
  • Document conversion rates
  • Write post-hackathon plan
  • Archive reports

Deliverable: 30-day report

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: 7 paid audits at a $120 blended order value from $99 singles and one $299 pack; one $99 refund; Stripe fees modeled at 4.5% blended (2.9% plus $0.30 per charge); no paid ads.
  • Base: 20 paid orders at $135 blended; one $99 refund; Stripe fees at 4.5%; organic outreach only.
  • Upside: 45 paid orders at $145 blended; two $99 refunds; Stripe fees at 4.5%; $150 paid test only if organic loop works; operating covers OpenAI, Vercel, Supabase, Resend and PDF rendering.
  • All figures are projections from stated assumptions, not verified revenue or existing customers.

Conservative

7 customers
$840
collected revenue · avg payment $120
Refunds
$99
Chargebacks
$0
Payment fees
$38
Paid marketing
$0
Hackathon profit
$703
Operating costs
$45
Business profit
$658

Base case

20 customers
$2,700
collected revenue · avg payment $135
Refunds
$99
Chargebacks
$0
Payment fees
$122
Paid marketing
$0
Hackathon profit
$2,479
Operating costs
$110
Business profit
$2,369

Optimistic

45 customers
$6,525
collected revenue · avg payment $145
Refunds
$198
Chargebacks
$0
Payment fees
$294
Paid marketing
$150
Hackathon profit
$5,883
Operating costs
$260
Business profit
$5,623

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,980
Payment fees (3.9%)
$77
Paid marketing
$0
Hackathon profit
$1,903
Business profit
$1,793

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.

Section 7 of 8

Main risks and validation experiments

Risk 1n8n or Make export schema changes break the parser mid-sprint.

Mitigation

Version-detect exports, keep fixtures, and show a parse error instead of a false clean report.

Validation experiment

Run the importer on 20 public workflow exports and log parse failures.

Kill criteria

If more than 20% of target exports fail to parse after 48 hours of fixes, narrow to one platform.

Risk 2False positives make the scored report look wrong in a small connected community.

Mitigation

Label confidence, document rule logic, and manually review the first 10 free audits.

Validation experiment

Compare 10 generated reports against founder review and count major false findings.

Kill criteria

If 2 of 10 reports contain a major wrong finding that a buyer notices, pause paid sales.

Risk 3Forum and Discord moderators remove report-card posts as promotion.

Mitigation

Answer first, ask mod permission, and keep the first posts useful without links.

Validation experiment

Post 3 value replies and one sample with moderator approval; track removals and inbound replies.

Kill criteria

If 3 posts are removed and no inbound lead appears in 5 days, switch to direct DM-only outreach.

Risk 4Buyers take free community help and never convert to paid audits.

Mitigation

Deliver a partial free finding, then send the $99 full report and Patch Pack link immediately.

Validation experiment

Deliver 15 free audits and measure $99 link clicks and payments after 7 days.

Kill criteria

If 15 free audits produce zero paid orders, change the offer or stop the free-audit loop.

Risk 5Agencies ask for Zapier support and expand scope beyond the 30-day build.

Mitigation

Publish supported formats and offer a waitlist instead of building Zapier.

Validation experiment

Ask 10 leads which platforms they need before paying.

Kill criteria

If more than half require Zapier before any payment, keep the current concept but target only n8n and Make agencies.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Next.js, Supabase and Stripe test project
  • Write normalized node and edge types
  • Save 3 n8n export fixtures

Output: Repo with schema and fixtures

Hours 3-4

  • Build n8n JSON importer
  • Normalize nodes and connections
  • Print graph summary

Output: Working importer CLI

Hours 5-6

  • Implement 8 core checks
  • Add severity and score
  • Run on one broken fixture

Output: First findings JSON

Hours 7-8

  • Render markdown report page
  • Show per-node findings
  • Add sample score header

Output: Shareable sample report

Hours 9-10

  • Create landing page with sample report
  • Add Stripe Checkout test link
  • Test webhook order state

Output: Testable paid flow

Hours 11-12

  • Write 10 community replies with specific findings
  • Post one sample report card
  • DM 5 worst-fit posters

Output: First outreach batch

Complete report

Full 30-day launch report

Read the full generated report

Flowproof Audit — 30-Day Launch Report

Projection-only plan. No customers, revenue, partnerships or sources are claimed.

1. Product opportunity and positioning

Flowproof Audit sells a reliability audit for automations that already exist. The buyer is a 1-10 person AI automation agency or freelance consultant maintaining 10-100 client workflows in n8n or Make. The trigger is concrete: a client reports a duplicate row, a double-send, or a workflow that stopped producing output. At that moment the builder does not want a new platform. They want to know which nodes caused the failure and what to paste in to prevent it.

The product wins by meeting the buyer at the export file. No OAuth, no migration, no scheduler. The buyer uploads JSON, pays $99, and receives a scored report, PDF, annotated workflow, and Patch Pack. The agency can forward the white-label PDF to its client and paste the patch nodes into the existing workflow. JEV scores the concept 70.9/100 in band B; speed to first revenue is the strongest criterion and monetization is the weakest, so the launch sells a narrow paid audit before expanding to packs and monthly plans.

2. Smallest sellable MVP

The MVP is a no-login paid audit flow. The buyer uploads one n8n or Make workflow export, pays $99 through Stripe Checkout, and gets a signed report link by email. The report includes a score, per-node findings, a PDF, an annotated workflow and copy-paste patch node JSON. The rule engine must ship with about 20 named checks. The LLM pass only covers AI and branching nodes and must return typed JSON. No dashboard, no OAuth, no hosted execution, no free self-serve tier.

3. Technical implementation plan

Next.js on Vercel handles upload, checkout and report pages. Supabase stores raw JSON, findings and PDFs. A TypeScript rule engine parses n8n and Make exports into a normalized graph and returns named findings. The LLM pass sends only AI and branching node excerpts and validates output with Zod. A renderer produces markdown, PDF, annotated workflow and patch fragments. Stripe webhook confirms payment; Resend sends a signed URL. The hardest risk is parser drift across export variants, so every unknown shape must produce a visible parse error, not a clean report.

4. Pricing and monetization

Prices are $99 for one audit, $299 for a five-audit Agency Pack, and $149 per month for unlimited audits. The first offer is a free audit of one client workflow followed immediately by a $99 link for the full report and Patch Pack. The $299 pack is for agencies with more than three client workflows. The monthly plan comes after the agency ships weekly. All charges run through Stripe Checkout. No paid marketing is assumed in the conservative or base case.

5. First-customer acquisition

The primary channel is public replies in the n8n community forum, n8n Discord and r/n8n where builders post workflow JSON or describe silent failures. The founder answers with 2-3 specific findings from the public JSON and one patch snippet. The same day, the founder DMs the worst-scoring posters with a free full audit offer. After delivering the free audit, send the $99 Stripe link. Week-one goal: 5 public sample report cards, 30 replies, 10 free audits, first $99 payment by day 9.

6. Detailed 30-day execution roadmap

Days 1-5 build the importer, rule engine, LLM pass, report, patch pack and Stripe delivery. Day 5 is the MVP deadline. Days 6-9 launch the sample-report loop, collect 30 community posts, reply to 10, and push for the first payment by day 9. Days 10-14 fix false positives, launch the $299 Agency Pack, DM 20 agencies, publish one teardown and review the funnel. Days 15-21 add the $149 monthly plan, referral kit, trust pages, Make samples, a before-and-after case and a revised sales script. Days 22-30 scale public reports, push monthly plans, add refund guards, control LLM cost, publish two SEO pages, run direct sales and close the pipeline. Daily work is one deliverable per day, with no extra platform scope.

7. Revenue and profit scenarios

All numbers are projections, not verified revenue. Conservative: 7 orders at $120 blended, $840 gross, $99 refunds, $38 processing fees, $0 ads, $45 operating. Base: 20 orders at $135, $2,700 gross, $99 refunds, $122 fees, $0 ads, $110 operating. Upside: 45 orders at $145, $6,525 gross, $198 refunds, $294 fees, $150 ads, $260 operating. Hackathon profit deducts refunds, chargebacks, processing fees and ad spend only. Business profit also deducts operating costs.

8. Main risks and validation experiments

Parser drift is the top technical risk; test 20 public exports and fail visibly. False positives are the top trust risk; review the first 10 free audits manually and pause paid sales if 2 of 10 contain a major wrong finding. Community moderation is the top distribution risk; answer first, ask mod permission, and switch to DM-only if three posts are removed with no inbound lead. Free-to-paid conversion is the top commercial risk; deliver a partial finding, then send the $99 link immediately. Zapier scope creep is the top focus risk; publish supported formats and keep a waitlist instead of building it.

9. First 24-hour action plan

Hours 1-2: scaffold the repo, schema and three fixtures. Hours 3-4: ship the n8n importer and graph summary. Hours 5-6: implement eight core checks and score output. Hours 7-8: render a markdown sample report. Hours 9-10: create the landing page, Stripe test link and webhook test. Hours 11-12: write 10 community replies, post one sample report card and DM five worst-fit posters. The day ends with a working sample report, a testable checkout and the first outreach batch.

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 →