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

IconGrid Contract Compiler

IconGrid compiles a messy folder of SVGs into one locked, accessible icon package — re-gridded, re-stroked, recolored, plus React/Vue wrappers and a before/after diff report — for indie devs and small agencies shipping a design system.

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.

Speculative6.01/10
MVP build (solo)
5 days
Launch price
$129
Sales to $1,000 revenue
8 customers
First paying customer
Free client-side Icon Consistency Checker distributed in r/webdev, r/UI_Design and r/FigmaDesign, plus direct DMs to small agencies.
Who pays

Design-system owner or lead developer at a 2-20 person SaaS company or digital agency, English-speaking US/EU, triggered by a brand refresh, new client brand kit, or batch of AI-generated/stock SVGs entering the codebase.

Biggest execution risk

Market demand 4.3/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 9; 8 sales at $129 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.4/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
$129
Solo build
5 days
30d base revenue
$2,322
30d hackathon profit
$2,120
Section 1 of 8

Product opportunity and positioning

Target customer

Design-system owner or lead developer at a 2-20 person SaaS company or digital agency, English-speaking US/EU, triggered by a brand refresh, new client brand kit, or batch of AI-generated/stock SVGs entering the codebase.

Why now

AI-assisted coding and AI-generated/stock SVG batches increase the rate at which mismatched icons enter codebases, while accessibility expectations make hand-fixed markup a recurring cost.

Problem

Icons arrive from Figma exports, stock packs and AI generators with different viewBoxes, stroke widths, fill-vs-stroke construction, hard-coded hex colors and no aria handling, so teams ship inconsistent UI or burn a designer-day hand-fixing each SVG.

Solution

Upload a zip, choose a contract (24px grid, 1.5 stroke, currentColor, optical padding, cap/join), and receive icon-contract.zip with normalized SVGs, sprite, React/Vue/Web Component wrappers, Tailwind plugin, contract.json and normalize-report.html.

Differentiation · Icon libraries ship their own catalogue; IconGrid normalizes the buyer's own icons into one deterministic, accessible code package, sold as a one-time build step with a free checker that proves the problem in 30 seconds.

1. Product opportunity and positioning

IconGrid Contract Compiler is a paid build step for teams that already own a messy icon folder. The buyer is a design-system owner or lead developer at a 2-20 person SaaS company or agency. The trigger is concrete: a brand refresh, a new client brand kit, or a batch of AI-generated/stock SVGs entering the codebase. Icons arrive with different viewBoxes, stroke widths, fill-vs-stroke construction, hard-coded hex colors and inconsistent aria handling. The team either ships visually inconsistent UI or spends designer time hand-fixing files, and the problem repeats with every new batch.

The wedge is a free client-side Icon Consistency Checker. A visitor drops a zip and gets counts of off-grid, mixed-stroke and non-currentColor icons in about 30 seconds. The report includes a CTA to compile the full package for $129. The paid output is the same pipeline with the artifact attached: normalized SVGs, sprite, React/Vue/Web Component wrappers, Tailwind plugin, contract.json and normalize-report.html. Differentiation is deterministic normalization of the buyer's own assets, not a catalogue subscription. The buyer is reachable by community posts and DMs; no marketplace cold-start, procurement cycle, SEO ramp or paid ads are required.

JEV scored this concept 60.1/100 (C band), strongest on speed to first revenue (8.37), weakest on market demand (4.28). The weak demand score is a warning, not a fact. The first two weeks test whether the checker earns attention and whether agencies pay $129 without a sales call. The plan deliberately sells a visible, one-time artifact to someone holding broken inputs, with a refund promise tied to the diff report.

Section 2 of 8

Smallest sellable MVP

A $129 one-time compile: upload zip, choose contract, receive icon-contract.zip plus diff report; free checker proves the problem before payment.

Must-have features

  • Zip upload capped at 250 icons and 10MB
  • SVG normalizer for 24px grid, stroke quantization, currentColor and metadata stripping
  • Contract builder UI saved as reusable contract.json
  • Non-conforming icon detector with visual side-by-side flags
  • Sprite sheet, per-icon files and React/Vue/Web Component wrappers with aria defaults
  • Tailwind plugin and contract.json in the output package
  • normalize-report.html with per-icon before/after diffs
  • Free client-side Icon Consistency Checker
  • Stripe Payment Link checkout with token-gated download and emailed zip

Explicitly out of scope

  • Icon catalogue or marketplace
  • Figma plugin or in-canvas editor
  • Hosted icon CDN or long-term asset storage
  • Team accounts, SSO or admin dashboards
  • AI icon generation
  • Manual design services or bespoke redraws

Demo flow (what the buyer sees)

  1. Visitor drops a zip into the free checker
  2. Checker returns off-grid, mixed-stroke and non-currentColor counts
  3. Visitor clicks compile CTA and selects a contract
  4. Buyer pays $129 through Stripe Payment Link
  5. Serverless compile generates package and diff report
  6. Buyer receives token-gated download and email with icon-contract.zip
Build plan

Technical implementation plan

Stack

Next.js on Vercelsvgo plus custom JS geometry passresvg-js for raster previewsJSZip and Canvas for client-side checkerStripe Payment Links and webhookCloudflare R2 for short-lived zip storageResend for delivery emailPostHog for funnel tracking

Architecture

The checker is static and client-side. The paid compile posts a zip to a serverless function, validates size and count, runs the normalizer, generates wrappers and sprite, renders before/after previews, writes the output zip to R2 with a short expiry, and returns a token-gated URL. Stripe webhook marks the token paid and triggers Resend.

Build steps

  1. Scaffold Next.js app and deploy to Vercel.
  2. Define contract.json schema for grid, stroke, caps, padding and color.
  3. Implement zip parsing with 250-icon and 10MB caps.
  4. Build svgo plus custom viewBox, stroke and color normalization pass.
  5. Add non-conforming icon detector and report reasons.
  6. Build contract builder UI and package generator.
  7. Generate sprite, per-icon SVGs, framework wrappers, Tailwind plugin and contract.json.
  8. Render normalize-report.html with resvg-js previews.
  9. Wire Stripe Payment Link, webhook, R2 token download and Resend email.
  10. Ship free client-side checker with JSZip and Canvas counts.

AI components

  • No LLM in the v1 compile path; transforms are deterministic. The diff report is generated from SVG geometry and raster previews, not model output.
Hardest technical risk: Re-gridding and stroke quantization across mixed fill, stroke and duotone SVGs without visual regressions; filled icons may be flagged, not forced.
Section 3 of 8

Pricing and monetization

Single Contract

Entry offer
$129 one-time

For One dev or designer normalizing one product or client icon set

  • Up to 250 icons compiled against one contract
  • Normalized SVGs, sprite, framework wrappers, Tailwind plugin
  • normalize-report.html diff report
  • Two re-runs within 30 days

Agency 5-Pack

$399 one-time

For 2-20 person agencies running multiple client brands

  • Five icon contracts
  • Saved contract presets for reuse
  • Five diff reports
  • Priority email turnaround

Model: One-time compile packages with an agency 5-pack; no subscription in the first 30 days.

First revenue offer: Send one client icon zip; I return a normalized, accessible package with React/Vue wrappers, sprite, Tailwind plugin and before/after diff for $129. Refund if the diff report does not convince you.

Expected ACV: $129

Upsell path: Sell the $399 Agency 5-Pack after the first successful compile, then ask for one referral per buyer in exchange for a free re-compile; re-runs and new client kits create repeat purchases.

Target customers
18
Revenue model
$2,322
Costs
$100
Profit model
$2,222
Section 4 of 8

First-customer acquisition

Primary channel

Free client-side Icon Consistency Checker distributed in r/webdev, r/UI_Design and r/FigmaDesign, plus direct DMs to small agencies.

Where to find them

  • r/webdev
  • r/UI_Design
  • r/FigmaDesign
  • Small agency directories and public portfolios
  • X searches for design-system icon complaints
  • Indie SaaS launch communities

Exact outreach motions

  • Post the checker with the angle: drop a zip and see how off-grid your icon set is.
  • Reply to every comment with one specific icon tip and a checker link.
  • DM 10 agencies with the $129 compile offer and checker link.
  • Follow up after 72 hours with a rendered before/after preview of their icons.
  • Ask every buyer for one referral to another agency for a free re-compile.

Message template

Hi [Name] — I built a free SVG icon consistency checker. If you send one client icon zip, I will return a normalized 24px/currentColor package with React wrappers and a before/after diff for $129. Refund if the diff does not convince you. Want the checker link?
Week-one goal: Ship checker by day 3, publish three community posts, send 25 agency DMs, get 3 paid-intent replies; first sale target 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

Scaffold app and contract schema

  • Create Next.js repo and deploy to Vercel.
  • Define contract.json schema for grid, stroke, caps, padding, color.
  • Add sample SVG fixtures for stroke, fill and duotone icons.

Deliverable: Deployed app shell and contract schema.

Day 2Normalizer core

Build SVG compile pipeline

  • Implement zip parsing with 250-icon/10MB cap.
  • Run svgo plus custom viewBox/stroke/color pass.
  • Log unfixable icons with reasons.

Deliverable: CLI compile on fixture zips.

Day 3Free checker

Ship client-side consistency checker

  • Build JSZip and Canvas checker for off-grid, mixed-stroke, non-currentColor counts.
  • Add report summary and CTA to compile.
  • Deploy checker at /checker.

Deliverable: Live free checker.

Day 4Package output

Generate buyer deliverable

  • Add contract builder UI.
  • Generate per-icon SVGs, sprite, React/Vue/Web Component wrappers, Tailwind plugin, contract.json.
  • Render before/after diff with resvg-js.

Deliverable: Downloadable icon-contract.zip.

Day 5PaymentsMVP shipped

Wire checkout and delivery

  • Create Stripe Payment Link for $129 Single Contract.
  • Connect Stripe to TrustMRR and add webhook plus token-gated download.
  • Send zip via Resend and test end-to-end.

Deliverable: Paid compile path live; MVP deadline.

Day 6Proof assets

Create before/after demos

  • Compile 6 fixture sets covering stroke, fill, duotone.
  • Capture 3 before/after screenshots from fixtures.
  • Write 1 short demo page and GIF.

Deliverable: Demo assets for posts and DMs.

Day 7First post

Launch free checker in r/webdev

  • Post checker with zip-drop angle.
  • Reply to every comment with a specific tip.
  • Track sessions in PostHog.

Deliverable: Live post and first session data.

Week 2 · Launch & first sale · 7 days
Day 8Community distribution

Post in two more subreddits

  • Post in r/UI_Design with before/after fixture.
  • Post in r/FigmaDesign with agency angle.
  • Collect objections in a log.

Deliverable: Three community posts live.

Day 9Direct outreachFirst sale target

Send first 10 agency DMs; target first sale

  • Build list of 30 agencies from public portfolios.
  • DM 10 with $129 offer and checker link.
  • Offer one manual compile to close first buyer.

Deliverable: First paid compile target or 3 quote conversations.

Day 10Follow-up

Convert replies and deliver

  • Follow up 72-hour no-replies with rendered preview.
  • Deliver any paid compile within 24 hours.
  • Ask buyer for one referral.

Deliverable: Delivery checklist and referral ask.

Day 11Quality fixes

Fix normalizer flags

  • Patch top 3 unfixable-icon reasons.
  • Add clearer report explanations.
  • Update demo page with fixes.

Deliverable: Improved compile pass rate.

Day 12Proof post

Publish synthetic before/after teardown

  • Write teardown using fixture icons, no customer names.
  • Post to r/webdev and X.
  • Link checker and $129 offer.

Deliverable: Teardown post and tracked clicks.

Day 13Outreach wave 2

DM 15 agencies

  • Find 15 agencies with mixed client icon sets.
  • Send personalized one-line offer.
  • Log replies and objections.

Deliverable: 15 DMs sent.

Day 14Week review

Measure funnel and adjust

  • Review checker sessions, CTA clicks, DMs, sales.
  • Cut the weakest message angle.
  • Set week 3 target.

Deliverable: Funnel review note.

Week 3 · Repeat & systematize · 7 days
Day 15Agency pack

Add 5-Pack checkout

  • Create $399 Agency 5-Pack Payment Link.
  • Add saved contract presets for repeat compiles.
  • Update pricing page copy.

Deliverable: 5-Pack live.

Day 16Checker conversion

Improve in-report CTA

  • Add dynamic CTA with icon-break counts.
  • Capture optional email before download.
  • A/B test CTA copy.

Deliverable: Higher-intent checker CTA.

Day 17Outreach wave 3

DM 15 agencies and 5 design-system leads

  • Search X for design-system icon complaints.
  • Send 20 DMs with preview offer.
  • Follow up all prior replies.

Deliverable: 20 new conversations.

Day 18Report polish

Make diff report sell itself

  • Add per-icon break badges and fix summary.
  • Add accessible markup check.
  • Export printable HTML.

Deliverable: Sharper normalize-report.html.

Day 19Referral loop

Ask every buyer for one intro

  • Email buyers a referral ask.
  • Offer free re-compile for intro.
  • Track referrals in sheet.

Deliverable: Referral tracking sheet.

Day 20Objection handling

Address trust and scope objections

  • Add privacy note: delete zips after 7 days.
  • Add FAQ on fill/duotone limits.
  • Add refund policy.

Deliverable: Updated checkout and FAQ.

Day 21Week review

Double down on converting channel

  • Compare subreddit vs DM conversion.
  • Prepare 3 reusable DM variants.
  • Set week 4 sales target.

Deliverable: Channel decision note.

Week 4 · Scale what works · 7 days
Day 22Agency proof

Build 5-Pack pitch

  • Create one-page 5-Pack offer.
  • Compile 2 agency-style fixture kits.
  • Add before/after samples.

Deliverable: 5-Pack pitch page.

Day 23Outreach wave 4

DM 20 agencies

  • Use agency portfolio trigger examples.
  • Offer 5-Pack with one paid trial compile.
  • Log all replies.

Deliverable: 20 DMs and 5-Pack interest list.

Day 24Support efficiency

Reduce compile support time

  • Build checklist for common buyer mistakes.
  • Add auto-validation before checkout.
  • Add status page for delivery.

Deliverable: Support playbook.

Day 25Second follow-up

Re-engage no-replies with preview

  • Render preview on 5 prospect icon sets.
  • Send preview follow-up.
  • Book calls for 5-Pack.

Deliverable: 5 preview follow-ups sent.

Day 26Community post 2

Post agency angle

  • Post 5-Pack angle in agency communities.
  • Share fixture before/after.
  • Answer scope questions.

Deliverable: Second community post.

Day 27Social proof

Request permission-based quotes

  • Ask buyers for one-line quote.
  • Add quotes only with written permission.
  • Add case-study snippet with no customer name.

Deliverable: Permissioned quote block or none.

Day 28Checkout optimization

Reduce drop-off

  • Add sample output preview before pay.
  • Add 30-second demo video.
  • Simplify payment page.

Deliverable: Updated checkout page.

Days 29-30 · Consolidate · 2 days
Day 29Final push

Close pipeline

  • DM all warm leads.
  • Offer final compile slots.
  • Ask for referrals.

Deliverable: Final sales push sent.

Day 30Close and reconcile

Wrap contest

  • Reconcile Stripe payouts and refunds.
  • Export sales and traffic report.
  • Write next-step decision memo.

Deliverable: Final contest 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: 4 paid Single Contract compiles from checker CTA and DMs.
  • Base: 18 paid compiles, one $129 refund absorbed.
  • Upside: 24 Single Contracts at $129 plus 3 Agency 5-Packs at $399, one $399 refund.
  • Payment processing assumes Stripe at 2.9% + $0.30 per transaction; fees are calculated on collected gross revenue.
  • No paid marketing in any scenario; ad_spend_usd is 0 because acquisition is organic posts and DMs.
  • Operating costs cover Vercel, Cloudflare R2, Resend, domain and resvg rasterization; founder time and salaries are excluded.
  • Chargebacks assumed 0 in all scenarios.
  • All scenarios are projections from stated assumptions, not verified revenue, customers or traction.

Conservative

4 customers
$516
collected revenue · avg payment $129
Refunds
$0
Chargebacks
$0
Payment fees
$16
Paid marketing
$0
Hackathon profit
$500
Operating costs
$25
Business profit
$475

Base case

18 customers
$2,322
collected revenue · avg payment $129
Refunds
$129
Chargebacks
$0
Payment fees
$73
Paid marketing
$0
Hackathon profit
$2,120
Operating costs
$65
Business profit
$2,055

Optimistic

27 customers
$4,293
collected revenue · avg payment $159
Refunds
$399
Chargebacks
$0
Payment fees
$137
Paid marketing
$0
Hackathon profit
$3,757
Operating costs
$140
Business profit
$3,617

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,322
Payment fees (3.9%)
$91
Paid marketing
$0
Hackathon profit
$2,231
Business profit
$2,166

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 1Community posts flop and the checker never reaches 300 sessions.

Mitigation

Publish by day 7, track PostHog events, and shift to agency communities if subreddits do not respond.

Validation experiment

Publish in r/webdev, r/UI_Design and r/FigmaDesign within 5 days and measure sessions and CTA clicks.

Kill criteria

If fewer than 80 checker sessions and fewer than 3 DM replies after 120 DMs by day 14, change the headline and channel mix.

Risk 2Normalizer handles stroke icons but looks weak on filled or duotone sets.

Mitigation

Flag unfixable icons with clear reasons and narrow the copy to stroke-based design systems if needed.

Validation experiment

Compile 20 fixture icons across stroke, fill and duotone styles and inspect flagged rate.

Kill criteria

If more than 30% of common design-system fixtures are unfixable after two improvement passes, narrow the product promise.

Risk 3Buyers expect a Figma plugin or live editor and bounce at zip upload.

Mitigation

Add an export guide and sample Figma-to-zip workflow; keep the compiler focused on code-ready output.

Validation experiment

Track DM and comment objections for 10 days and count Figma requests.

Kill criteria

If more than half of qualified replies demand a Figma plugin before paying, re-scope the wedge or add a lightweight export helper.

Risk 4A buyer treats the compile as design consulting and asks for open-ended revisions.

Mitigation

State fixed scope, flag unfixable icons, refund manual redraw requests and keep support under 15 minutes per sale.

Validation experiment

Review all buyer emails and count revision requests outside the two included re-runs.

Kill criteria

If consulting requests dominate support time across three sales, raise price or restrict the offer to agencies with clean contracts.

Risk 5Payment holds or verification delays block cash recognition inside the contest window.

Mitigation

Connect Stripe to TrustMRR before launch, complete verification early and test a live $1 payment internally.

Validation experiment

Run a live $1 test transaction on day 5 and confirm payout status.

Kill criteria

If payouts are held past day 10, switch to an already verified processor or pause paid traffic until resolved.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Next.js repo and deploy app shell to Vercel.
  • Register domain and write contract.json schema.

Output: Deployed shell and schema.

Hours 3-4

  • Implement zip parsing.
  • Run first normalizer pass on five fixture icons.

Output: Command-line compile on fixtures.

Hours 5-6

  • Build static contract builder UI.
  • Build free checker skeleton with JSZip and Canvas counts.

Output: Local checker page.

Hours 7-8

  • Generate sample icon-contract.zip with SVGs, sprite and React wrapper.
  • Add basic diff report.

Output: Sample deliverable.

Hours 9-10

  • Create Stripe test Payment Link.
  • Add token-gated download route and Resend template.

Output: End-to-end test purchase.

Hours 11-12

  • Write r/webdev post draft.
  • Capture three before/after fixture screenshots and set up PostHog events.

Output: Launch assets ready.

Complete report

Full 30-day launch report

Read the full generated report

IconGrid Contract Compiler — 30-Day Launch Report

This is a planning artifact for a solo founder in the $100K Hackathon by Ship or Die (Nov 16-Dec 16, 2026). IconGrid Contract Compiler has no customers, revenue or partnerships; all financials are projections. JEV scored the concept 60.1/100 (C band), strongest on speed to first revenue (8.37), weakest on market demand (4.28). The plan creates a free diagnostic, then sells a visible one-time artifact to a buyer who already owns broken inputs.

1. Product opportunity and positioning

IconGrid Contract Compiler is not another icon library. It compiles the buyer's own SVGs into one locked, accessible package. The buyer is a design-system owner or lead developer at a 2-20 person SaaS company or agency. The trigger is a brand refresh, a new client brand kit, or a batch of AI-generated/stock SVGs entering the codebase. Icons arrive with different viewBoxes, stroke widths, fill-vs-stroke construction, hard-coded hex colors and inconsistent aria handling. The team ships inconsistent UI or burns designer time hand-fixing files, and the problem repeats with every new batch.

The wedge is a free client-side Icon Consistency Checker. A visitor drops a zip and gets counts of off-grid, mixed-stroke and non-currentColor icons in about 30 seconds. The report includes a CTA to compile the full package for $129. The paid output is the same pipeline with the artifact: normalized SVGs, sprite, React/Vue/Web Component wrappers, Tailwind plugin, contract.json and normalize-report.html. Differentiation is deterministic normalization of the buyer's assets, not a catalogue subscription. The buyer is reachable by community posts and DMs; no marketplace, procurement, SEO ramp or ads are required. JEV's weak market-demand score is a warning, not a fact. The first two weeks test whether the checker earns attention and whether agencies pay $129 without a call.

2. Smallest sellable MVP

One paid compile flow: upload a zip capped at 250 icons and 10MB, choose a contract (24px grid, 1.5 stroke, currentColor, optical padding, cap/join), pay $129, and receive icon-contract.zip by token-gated download and email. The zip contains normalized SVGs, sprite.svg, per-icon files, React/Vue/Web Component wrappers with aria defaults, a Tailwind plugin, contract.json and normalize-report.html with before/after diffs. The free checker is part of the MVP because it is the acquisition loop, but it runs entirely in-browser and stores no files. Out of scope: icon catalogue, Figma plugin, hosted CDN, team accounts, SSO, admin dashboards, AI generation, manual redraws and design services. Icons that cannot be normalized are flagged, not forced.

3. Technical implementation plan

Stack: Next.js on Vercel, svgo plus a custom JS geometry pass for re-gridding and stroke quantization, resvg-js for raster previews, JSZip and Canvas for the checker, Stripe Payment Links with webhook, Cloudflare R2 for short-lived zip storage, Resend for delivery and PostHog for funnel tracking. The checker is static and client-side. The paid compile posts a zip to a serverless function, validates size and count, runs the normalizer, generates wrappers and sprite, renders before/after previews, writes the output zip to R2 with a short expiry, and returns a token-gated URL. Stripe webhook marks the token paid and triggers Resend. Hardest risk: re-gridding mixed fill, stroke and duotone SVGs without visual regressions. Mitigation: normalize stroke icons confidently, flag filled or duotone glyphs with reasons, and explain every change in the report. No LLM is used in the v1 compile path; correctness comes from deterministic geometry.

4. Pricing and monetization

One-time pricing. Single Contract is $129 for up to 250 icons, one contract, wrappers, sprite, Tailwind plugin, diff report and two re-runs within 30 days. Agency 5-Pack is $399 for five contracts, saved presets, five diff reports and priority email turnaround. Expected ACV is $129 because the base case counts only Single Contracts. First offer: send one client icon zip; receive a normalized, accessible package with React/Vue wrappers, sprite, Tailwind plugin and before/after diff for $129; refund if the diff report does not convince you. Upsell is the 5-Pack after a successful compile, plus referrals and re-runs for new client kits. No subscription in the first 30 days.

5. First-customer acquisition

Primary channel: free checker in r/webdev, r/UI_Design and r/FigmaDesign, plus direct DMs to small agencies found through public portfolios and agency directories. Post angle: drop a zip of your SVGs and see how off-grid your icon set is. Reply to comments with a concrete tip and checker link. DMs use a one-line offer with a rendered before/after preview of the prospect's own icons where possible. Follow up once after 72 hours. Ask every buyer for one referral in exchange for a free re-compile. Week one target: checker live by day 3, three community posts, 25 agency DMs, three paid-intent replies; first sale targeted day 9.

6. Detailed 30-day execution roadmap

Days 1-5 build: scaffold Next.js, define contract.json, implement zip parsing and normalizer, ship free checker, add contract builder and package generator, then wire Stripe, webhook, token download and Resend. MVP deadline day 5. Days 6-7: create before/after proof assets from fixtures and post the checker in r/webdev. Days 8-14: post in r/UI_Design and r/FigmaDesign, send 25 agency DMs, deliver any paid compile within 24 hours, fix normalizer flags, publish a synthetic teardown, review funnel. First sale target day 9. Days 15-21: add $399 5-Pack, improve in-report CTA, run second DM wave, polish diff report, add privacy and refund FAQs. Days 22-28: build 5-Pack pitch page, send 20 more DMs, reduce support time, follow up with rendered previews, post agency-angle update, optimize checkout. Days 29-30: close warm leads, ask for referrals, reconcile Stripe payouts and refunds, export traffic and sales data, write next-step memo. JSON contains day-by-day tasks.

7. Revenue and profit scenarios (projections only)

Projections, not verified revenue. Conservative: 4 Single Contracts at $129, gross $516, no refunds, $16 payment fees, $0 ad spend, $25 operating costs. Base: 18 Single Contracts at $129, gross $2,322, one $129 refund, $73 fees, $0 ad spend, $65 operating costs. Upside: 24 Single Contracts at $129 plus 3 Agency 5-Packs at $399, gross $4,293, one $399 refund, $137 fees, $0 ad spend, $140 operating costs. Stripe assumed at 2.9% plus $0.30 per transaction. Hackathon profit is gross revenue minus refunds, chargebacks, payment fees and ad spend. Business profit also subtracts operating costs. On these inputs, projected hackathon profit is $500, $2,120 and $3,757; projected business profit is $475, $2,055 and $3,617. Treat as hypotheses.

8. Main risks and validation experiments

Risk 1: community posts flop and checker never reaches 300 sessions. Validation: publish by day 7 and check PostHog. If fewer than 80 checker sessions and fewer than 3 DM replies after 120 DMs by day 14, change headline and shift to agency communities. Risk 2: normalizer looks weak on filled or duotone sets. Validation: compile 20 fixture icons across styles. If more than 30% are flagged unfixable, narrow copy to stroke-based design systems. Risk 3: buyers expect a Figma plugin. Validation: track objections. If more than half of replies ask for Figma, add an export guide, not a plugin. Risk 4: consulting scope creep. Mitigation: fixed scope, flag unfixable icons, refund manual redraw requests. Kill or re-scope if open-ended revisions dominate. Risk 5: payment holds. Mitigation: connect Stripe to TrustMRR before launch, complete verification early, test a live $1 payment internally.

9. First 24-hour action plan

Hours 1-2: create Next.js repo, deploy app shell to Vercel, register domain, write contract.json schema. Output: deployed shell and schema. Hours 3-4: implement zip parsing and first normalizer pass on five fixture icons. Output: command-line compile on fixtures. Hours 5-6: build static contract builder UI and free checker skeleton with JSZip and Canvas counts. Output: local checker page. Hours 7-8: generate sample icon-contract.zip with SVGs, sprite, React wrapper and basic diff report. Output: sample deliverable. Hours 9-10: create Stripe test Payment Link, token-gated download route and Resend template. Output: end-to-end test purchase. Hours 11-12: write r/webdev post draft, capture three before/after fixture screenshots, set up PostHog events. Output: launch assets ready.

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 →