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

FitCard Forge

Paste a dress product URL and get a copy-ready Fit Card plus a prioritized fit-friction audit, so small dress brands can answer size questions before checkout.

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.87/10
MVP build (solo)
5 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Direct Instagram DM to small Shopify/WooCommerce dress brands that launched a collection in the last 30 days, with a 48-hour email follow-up to the same list.
Who pays

Owner/operator of a 1-10 person online dress brand on Shopify or WooCommerce (occasion, bridal, everyday) in the US, UK, Canada or Australia, triggered by a new collection launch or a spike in pre-sale fit questions.

Biggest execution risk

Market demand 3.8/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; 21 sales at $49 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.1/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

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

0/14
Entry price
$49
Solo build
5 days
30d base revenue
$2,890
30d hackathon profit
$2,725
Section 1 of 8

Product opportunity and positioning

Target customer

Owner/operator of a 1-10 person online dress brand on Shopify or WooCommerce (occasion, bridal, everyday) in the US, UK, Canada or Australia, triggered by a new collection launch or a spike in pre-sale fit questions.

Why now

Dress brands are shipping resort and spring collections into the December window, fit questions arrive before checkout, and a 1-10 person team has no spare hours to rewrite size charts by hand across a catalog.

Problem

Product pages show a generic S-XL chart but omit garment measurements, ease, stretch notes, between-size guidance, model fit notes and measurement ranges by body area, so shoppers ask fit questions or order two sizes and the owner has no repeatable way to fix it across styles.

Solution

Paste a dress product URL; the app fetches the rendered page, extracts the size chart, copy, fabric/stretch mentions and model notes, scores twelve fit-friction checks with quoted evidence, and outputs a copy-paste Fit Card HTML/Markdown block with explicit blanks plus a prioritized CSV fix list for that style.

Differentiation · Fit quizzes and size-chart widgets push more questions onto the shopper; FitCard Forge audits and rewrites the merchant's own page content and refuses to invent a measurement it cannot find in the source.

The buyer and the trigger. A 1-10 person dress brand ships a new collection. A shopper messages: 'I am 5'4", 34B, usually a 6 but wide hips - what size?' The owner opens the product page, finds a generic S-XL chart listing bust, waist and hip, and nothing else. No garment measurements. No ease. No stretch note. No between-size guidance. No model fit note. No measurement ranges by body area. She answers by hand, guesses, and waits to see whether the order comes back.

That moment is the whole market entry. The buyer already has product pages and already feels the cost of fit questions. She does not need an integration, an app install, a body-double network or a pattern pipeline. She needs one page to stop generating questions.

What FitCard Forge produces. Paste a dress product URL. The app fetches the rendered page, extracts the size-chart table, product description, fabric and stretch mentions and model fit notes, then scores twelve fit-friction checks and shows the quoted evidence behind each pass or fail. Output is a copy-ready Fit Card HTML block with structured fields - garment measurements, ease, stretch, between-size guidance, model fit note, ranges by body area - plus a prioritized fix list as CSV or Markdown for that exact style.

Where the source page is missing data, the Fit Card prints an explicit blank rather than a number. That constraint is not a limitation to apologise for; it is the reason an owner can trust the output enough to paste it into a live theme. Every number traces back to her own page or her own input.

Why this wedge and not the alternatives. Consumer-facing fit tools move the guessing to the shopper. Made-to-measure services require measurements the brand does not have. A general AI copywriter produces plausible fit language with invented numbers, which is worse than no content. FitCard Forge is one URL in and one concrete artifact out, scoped to a single style, priced so an owner can approve it alone.

What the JEV score says. The concept scored 58.7 (band C, confidence 0.67). Speed to first revenue is the strongest dimension at 8.13/10: a free one-product sample can open a paid catalog audit the same week. Market demand (3.77) and operational simplicity (4.37) are the weakest. The plan responds by narrowing to one artifact, keeping the paid path self-serve with no human review step, starting outreach on day 6 rather than day 20, and refusing any feature whose value only lands after the contest window closes.

Section 2 of 8

Smallest sellable MVP

A single-URL audit: paste a dress product URL, pay $49 through Stripe Checkout, and receive a Fit Card HTML block plus a Markdown/CSV fix list by email within minutes.

Must-have features

  • URL input with server-side rendered fetch of Shopify and WooCommerce product pages
  • Parser for size-chart tables, product description, fabric/stretch mentions and model fit notes
  • Twelve fit-friction checks with pass/fail and quoted source evidence
  • Fit Card generator producing copy-paste HTML and Markdown with explicit missing-data placeholders
  • Prioritized fix-list export as CSV
  • Stripe Checkout for $49, $499 and $199/month with email delivery via Resend
  • Dashboard listing audited URLs with regenerate and download links
  • Disclaimer that no garment measurements are invented and blanks must be filled by the brand

Explicitly out of scope

  • No Shopify app install or automatic theme editing
  • No AI body measurement extraction from photos
  • No custom sewing patterns or production files
  • No return or exchange analytics integration
  • No multi-user team accounts or SSO
  • No body-double peer network or consumer-facing fit quiz
  • No automated re-audit scheduling beyond the monthly tier

Demo flow (what the buyer sees)

  1. Owner pastes a dress product URL
  2. App fetches the rendered page and extracts chart, copy, fabric and model notes
  3. Twelve checks run and display with quoted evidence
  4. Fit Card HTML block renders with explicit blanks for missing fields
  5. Fix list is generated as CSV, ordered by impact
  6. Owner pays via Stripe Checkout and receives email plus dashboard link
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres for audits, checks and ordersBrowserless headless Chrome for rendered page fetchCheerio for HTML table and text parsingOpenAI API with structured outputs for grounded extraction and copy rewritingStripe Checkout and Stripe Billing for the monthly tierResend for transactional email delivery

Architecture

A single Next.js app on Vercel handles the form, the audit API route and the dashboard. The audit route calls Browserless to render the product page, stores the raw HTML in Supabase, parses tables and text with Cheerio, then sends only extracted fragments to OpenAI with a strict schema so the model never invents a measurement. Twelve checks run against the structured result and each stores its evidence quote. The Fit Card template renders from that structured object, printing an explicit blank wherever a field is null. Stripe Checkout webhooks unlock the download and trigger Resend delivery. All artifacts are static HTML, Markdown and CSV, so delivery has no ongoing compute cost.

Build steps

  1. Scaffold Next.js on Vercel and create Supabase tables for audits, audit_checks and orders
  2. Wire Browserless fetch with a 25-second timeout and store raw HTML
  3. Parse size-chart tables, fabric and stretch mentions, and model fit sentences with Cheerio
  4. Send extracted fragments to OpenAI structured output and validate against the schema
  5. Implement the twelve checks with pass/fail plus evidence quote per check
  6. Render the Fit Card HTML/Markdown template with explicit null placeholders
  7. Generate the prioritized CSV fix list from failed checks
  8. Add Stripe Checkout, webhook handling and Resend delivery email
  9. Build the dashboard with audit history, regenerate and download
  10. Add per-platform detection and a manual size-chart paste fallback
  11. Add caching of fetched HTML to control Browserless and API cost

AI components

  • Structured extraction of size-chart rows and fit sentences from messy HTML text
  • Normalising fabric, stretch and model-fit mentions into fixed fields
  • Rewriting fit copy strictly from extracted facts, returning null instead of guessing
  • Ordering the fix list by which missing fields most affect the between-size decision
Hardest technical risk: Product pages whose size chart is an image or whose theme blocks headless browsers, which produces an empty parse and an unusable Fit Card.
Section 3 of 8

Pricing and monetization

Single Style Fit Card

Entry offer
$49 one-time

For Owner testing the output on one product

  • One Fit Card HTML block
  • One style fix list
  • Missing-data checklist

Catalog Fit Audit

$499 one-time

For Brand with 10-50 dress styles preparing a launch or cleaning up fit content

  • Audit of up to 40 product URLs
  • Copy-ready Fit Card blocks
  • Prioritized fix list CSV
  • Missing-measurement checklist by style
  • Email delivery and dashboard access

Monthly Refresh

$199 / month

For Brand launching new styles every month

  • 20 new style audits per month
  • Fit Card blocks
  • Monthly fix list export

Model: One-time audits priced by catalog size, with an optional monthly refresh subscription.

First revenue offer: A free Fit Card for one of their live dress pages, sent as a screenshot of the gaps found plus the copy-paste block; if it is useful, $49 for that style today or $499 for a full catalog audit of up to 40 styles.

Expected ACV: $289

Upsell path: Single Style $49 converts to Catalog Fit Audit $499 with the $49 credited, then to Monthly Refresh at $199/month once new styles ship.

Target customers
200
Revenue model
$99,800
Costs
$3,200
Profit model
$96,600
Section 4 of 8

First-customer acquisition

Primary channel

Direct Instagram DM to small Shopify/WooCommerce dress brands that launched a collection in the last 30 days, with a 48-hour email follow-up to the same list.

Where to find them

  • Instagram hashtags: #newcollection, #bridaldesigner, #slowfashiondress, #madeinukdress
  • Instagram brand tags on recent collection launch posts
  • Shopify store product pages discovered through search for dress size guides
  • WooCommerce dress stores found via search for 'size guide' dress pages
  • Brands tagged in occasion-wear and bridal boutique posts
  • Existing buyers' referral intros

Exact outreach motions

  • Pre-generate a free Fit Card for one live page, then DM a screenshot of one specific missing field on that page
  • Angle A for brands with no garment measurements: 'your chart lists body size but not the dress'
  • Angle B for brands with no between-size guidance: 'shoppers between 8 and 10 have to guess'
  • 48-hour follow-up with the three biggest fit-data gaps found on their site
  • Direct price question in the same thread: $49 for this style or $499 for the catalog
  • Post-call written offer with a 24-hour delivery promise

Message template

Hi [name] - I audited your [product name] page and the size chart lists body measurements but not the dress's own bust/waist or stretch. I made a free Fit Card showing exactly what is missing and how it would read on your page. Want me to send it? No charge.
Week-one goal: MVP live on a public URL, 150-brand prospect list built, 20 DMs sent with 10 pre-generated free Fit Cards attached.
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 1Scaffold

Deployed skeleton

  • Create Next.js repo on Vercel with Supabase connected.
  • Define audits, audit_checks and orders tables.
  • Create Stripe products at $49, $499 and $199/mo.
  • Deploy a stub with a working URL input.

Deliverable: Live stub app with form and database.

Day 2Fetch and parse

URL to structured data

  • Wire Browserless to render product pages.
  • Parse size-chart tables with Cheerio.
  • Extract fabric, stretch and model-fit sentences.
  • Run five real dress URLs and store raw output.

Deliverable: Structured JSON for five of five test URLs.

Day 3Fit Friction Score

Twelve checks with evidence

  • Implement twelve checks covering garment measures, ease, stretch, between-size and model notes.
  • Attach a quoted evidence line per check.
  • Use OpenAI structured output for extraction only.
  • Render the scored result page.

Deliverable: Scored audit page for any pasted URL.

Day 4Output and checkout

Artifact plus payment

  • Generate Fit Card HTML and Markdown with explicit placeholders.
  • Export the prioritized fix list as CSV.
  • Wire Stripe Checkout and Resend delivery.
  • Run one paid test transaction end to end.

Deliverable: Paid audit delivered by email.

Day 5MVP launchMVP shipped

Public v1

  • Build dashboard with audit history and downloads.
  • Add disclaimers and the no-invented-measurements notice.
  • Publish landing page with one sample Fit Card.
  • Point the public domain and connect the payment account.

Deliverable: Public MVP live (MVP deadline).

Day 6Prospecting

150 named brands

  • Collect 150 brands from Instagram hashtags and store pages.
  • Filter to 1-10 person brands with a launch in the last 30 days.
  • Record a 40-second screen capture of one audit.
  • Log contact route and one sample URL per brand.

Deliverable: Prospect sheet of 150 brands.

Day 7First outreach

20 DMs with samples

  • Pre-generate ten free Fit Cards for real product URLs.
  • Send 20 DMs with a screenshot of that brand's own gaps.
  • Reply to every response within two hours.
  • Log replies and angles used.

Deliverable: 20 DMs sent, ten samples attached.

Week 2 · Launch & first sale · 7 days
Day 8Volume outreach

50 touches

  • Send 30 DMs and 20 emails.
  • Run two angles: missing garment measurements versus missing between-size guidance.
  • Record which angle earns replies.

Deliverable: 50 touches sent with angle tracking.

Day 9Follow-up

48-hour sequence

  • Follow up with every day 7-8 non-reply.
  • Lead with the three biggest gaps on their site.
  • Send the free Fit Card as a link, not an attachment.

Deliverable: 25 follow-ups sent.

Day 10Conversations

Replies into offers

  • Book three short calls or async voice notes.
  • Send the $499 catalog offer in writing after each.
  • Ask each warm reply a direct price question.

Deliverable: Three written offers out.

Day 11Parser hardening

Real-world pages

  • Fix the top three parse failures from outreach pages.
  • Add manual size-chart paste fallback.
  • Cache fetched HTML to cut Browserless cost.

Deliverable: Parser v2 with fallback shipped.

Day 12First saleFirst sale target

Close payment

  • Send checkout links to the warmest prospects.
  • Promise delivery within two hours of payment.
  • Call the top three repliers if no sale by 16:00.

Deliverable: First Stripe payment received.

Day 13Deliver

Fast paid delivery

  • Deliver the paid bundle within 24 hours.
  • Ask what was missing and what they would pay monthly.
  • Fix the biggest output complaint same day.

Deliverable: Delivered bundle plus written feedback.

Day 14Proof

Delivery into evidence

  • Ask the first buyer for a short testimonial.
  • Ask for one intro to another dress brand.
  • Publish the testimonial on the landing page.

Deliverable: Testimonial or referral request sent.

Week 3 · Repeat & systematize · 7 days
Day 15Self-serve

Remove the call

  • Make the $49 path fully self-serve with instant delivery.
  • Add a confirmation page with download buttons.
  • Target delivery under five minutes.

Deliverable: Self-serve $49 purchase live.

Day 16Batch samples

Free Fit Cards at scale

  • Batch-run 20 free Fit Cards for top prospects.
  • Send each with one screenshot of a missing field.
  • Cap free samples at three per day.

Deliverable: 20 samples sent under a documented cap.

Day 17Bridal slice

Occasion and bridal brands

  • Send 40 DMs to bridal and occasion dress brands.
  • Use the between-size angle for made-to-order gowns.
  • Track this reply rate separately.

Deliverable: 40 bridal DMs sent with separate tracking.

Day 18Non-buyer sequence

Recover sample recipients

  • Send a three-email sequence to non-buying sample recipients.
  • Email one: three missing measurements; two: a fixed page; three: $499 offer.
  • Stop the sequence on any reply.

Deliverable: Sequence live to all sample recipients.

Day 19Catalog conversions

Close $499

  • Run four follow-up conversations with catalog-sized brands.
  • Send a two-page example audit on their own catalog.
  • Offer a 30-minute delivery walkthrough.

Deliverable: Two catalog offers in negotiation.

Day 20Subscription

Ship $199 monthly

  • Add Stripe subscription for Monthly Refresh.
  • Add regenerate links for returning buyers.
  • Email existing buyers the upgrade.

Deliverable: Monthly tier live and offered.

Day 21Review

Cut what fails

  • Compare reply rate by angle and brand size.
  • Delete the two weakest outreach variants.
  • Update the landing page with anonymised real output.

Deliverable: Updated outreach playbook and landing page.

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

Buyer-driven intros

  • Ask every buyer for one intro to another brand.
  • Offer $50 credit per intro that becomes paid.
  • Track referrals in the dashboard.

Deliverable: Referral asks sent to all buyers.

Day 23International

UK, CA, AU

  • Send 40 DMs to UK, Canadian and Australian brands.
  • Adjust examples to their collection calendars.
  • Schedule follow-ups by timezone.

Deliverable: 40 international DMs sent.

Day 24WooCommerce

Second platform

  • Test ten WooCommerce dress product pages.
  • Patch the variation-table parser.
  • Add platform detection to the fetch step.

Deliverable: WooCommerce pages audit correctly.

Day 25Upsell

Single to catalog

  • Email every $49 buyer the catalog upgrade with credit applied.
  • Send a one-page comparison of one Fit Card versus a full catalog fix.
  • Set a 48-hour reply window.

Deliverable: Upsell email sent to all single buyers.

Day 26Public proof

One teardown

  • Publish an anonymised before/after Fit Card teardown on LinkedIn and X.
  • Link to a free audit request form.
  • Reply to every comment with an offer to audit their page.

Deliverable: Public teardown live with request form.

Day 27Automation

Cut delivery time

  • Build a batch URL runner for 40 URLs.
  • Add an error report for failed URLs.
  • Measure founder time per catalog audit.

Deliverable: Batch runner shipped, time measured.

Day 28Final push

Last full outreach day

  • Send 50 DMs and emails with a 16 December delivery guarantee.
  • State that audits bought after 14 December deliver same day.
  • Push $199 monthly to anyone hesitating on $499.

Deliverable: 50 final touches sent with deadline language.

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

Money inside the window

  • Re-send checkout links to every verbal yes.
  • Confirm all payments land in the connected account.
  • Queue delivery for every outstanding audit.

Deliverable: All outstanding payments requested.

Day 30Close

Finish and record

  • Stop selling before 13:00 UTC and deliver the last audits.
  • Reconcile Stripe payouts against the TrustMRR dashboard.
  • Write a one-page retro on reply rates and delivery cost.

Deliverable: Reconciled revenue figure and retro.

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 paid customers from roughly 250 direct touches, blended ARPU $199 (two $49 single-style, one $499 catalog audit).
  • Base: 10 paid customers, blended ARPU $289 (four $49, five $499, one $199 monthly).
  • Upside: 24 paid customers, blended ARPU $349 (six $49, fifteen $499, three $199 monthly).
  • Payment processing assumed at 4.0% of gross revenue via Stripe Checkout with a mixed domestic/international card base; this is an assumption, not a verified statement.
  • No paid marketing in Conservative and Base (organic Instagram DM and email only); Upside spends $400 on sponsored newsletter placements and boosted launch posts.
  • Operating costs cover Vercel, Supabase, Browserless, OpenAI and Resend, sized at roughly $0.60-$2.50 per audited URL plus fixed monthly tooling.
  • Refunds: none in Conservative, one $49 refund in Base, one $499 refund in Upside; no chargebacks assumed in any scenario.
  • Free sample Fit Cards are given away manually and are never counted as customers, revenue or traction.
  • All three scenarios are projections built from stated assumptions, not verified revenue.

Conservative

3 customers
$597
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$24
Paid marketing
$0
Hackathon profit
$573
Operating costs
$35
Business profit
$538

Base case

10 customers
$2,890
collected revenue · avg payment $289
Refunds
$49
Chargebacks
$0
Payment fees
$116
Paid marketing
$0
Hackathon profit
$2,725
Operating costs
$180
Business profit
$2,545

Optimistic

24 customers
$8,376
collected revenue · avg payment $349
Refunds
$499
Chargebacks
$0
Payment fees
$335
Paid marketing
$400
Hackathon profit
$7,142
Operating costs
$420
Business profit
$6,722

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$490
Payment fees (3.9%)
$19
Paid marketing
$0
Hackathon profit
$471
Business profit
$291

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.

All figures are projections derived from stated assumptions, not verified revenue, customers or traction. Contest ranking uses hackathon profit (gross revenue minus refunds, chargebacks, payment fees and paid ad spend); business profit additionally subtracts operating costs.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM conversion lands far below the plan and 30 days ends with no repeatable paid demand.

Mitigation

Send 50 touches in the first three outreach days, track reply rate per angle, and stop building features while the reply rate is unmeasured.

Validation experiment

Send 50 DMs to 50 named brands and count replies and price questions within 96 hours.

Kill criteria

Fewer than 5% replies after 100 touches and zero paid customers by day 20 means switch to assisted manual delivery only; still zero by day 26 means the concept does not work in this window.

Risk 2Size charts published as images, or themes that block headless browsers, break the parser and produce empty Fit Cards.

Mitigation

Ship a manual paste-the-chart fallback, platform detection, and an explicit blank instead of a guessed value.

Validation experiment

Run the parser across 20 real target-brand URLs and record the auto-parse success rate.

Kill criteria

If automatic parsing succeeds on fewer than 40% of target URLs, restrict positioning to standard Shopify themes and price the work as assisted delivery.

Risk 3Owners read the output as content advice rather than software worth $49 or $499.

Mitigation

Lead every message with a screenshot of a specific missing field on their own page, and show the finished block rather than describing it.

Validation experiment

After each free sample, ask one question: would you pay $49 for this page today?

Kill criteria

If fewer than two of five sampled owners say yes, rewrite the offer around the catalog tier or reduce scope to a single deliverable.

Risk 4Fit guidance is treated as advice and creates liability if a shopper relies on incomplete data.

Mitigation

Never invent a measurement, print explicit blanks, cite the source sentence behind each field, and show a disclaimer on every Fit Card.

Validation experiment

Review five delivered Fit Cards against their source pages and confirm every number traces to the page or owner input.

Kill criteria

Any delivered card containing an unsourced number triggers a stop-and-fix before further sales.

Risk 5Manual delivery of free samples and paid audits becomes the bottleneck as replies increase.

Mitigation

Cap free samples at three per day, ship the batch URL runner by day 27, and keep time per catalog audit under ten minutes.

Validation experiment

Time one full catalog audit end to end and log each manual step.

Kill criteria

If a catalog audit takes more than 90 minutes, cut the catalog tier to 20 URLs before taking another order.

Risk 6Payments arrive after the contest window closes and do not count.

Mitigation

Sell card payment only through the connected checkout, push deadline language from day 28, and stop selling before 13:00 UTC on day 30.

Validation experiment

Reconcile the payment dashboard against delivered audits every evening from day 26.

Kill criteria

Any order that cannot settle by 12:00 UTC on day 30 is refunded rather than delivered late.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 0-2

  • Create the Next.js repo on Vercel and the Supabase project.
  • Create audits, audit_checks and orders tables.

Output: Deployed stub URL with a working URL input.

Hours 2-5

  • Wire Browserless fetch with a 25-second timeout.
  • Parse size-chart tables and product copy with Cheerio on five live dress URLs.

Output: Structured parse output saved for five real pages.

Hours 5-8

  • Implement the twelve fit-friction checks with evidence quotes.
  • Build the Fit Card HTML template with explicit null placeholders.

Output: One complete Fit Card rendered from a real page.

Hours 8-11

  • Wire Stripe Checkout for $49 and $499.
  • Add Resend delivery and run one paid test transaction.

Output: End-to-end paid audit delivered by email.

Hours 11-14

  • Publish the landing page with one sample Fit Card.
  • Add the disclaimer that no measurements are invented.

Output: Public landing page and disclaimers live.

Hours 14-20

  • Build the first 40-brand list with one sample URL each.
  • Pre-generate five free Fit Cards for the strongest fits.

Output: Prospect sheet of 40 brands with five samples.

Hours 20-24

  • Send the first ten DMs with screenshots attached.
  • Reply to anything that comes back within the hour.

Output: Ten DMs sent and a reply log started.

Complete report

Full 30-day launch report

Read the full generated report

FitCard Forge - 30-Day Launch Report

Solo founder. Contest window: 16 November 2026 13:00 UTC to 16 December 2026 13:00 UTC. Every financial figure below is a projection from stated assumptions, not verified revenue. No customers, partners or testimonials exist yet.

1. Product opportunity and positioning

A 1-10 person dress brand ships a new collection. A shopper messages: 'I am 5'4", 34B, usually a 6 but wide hips - what size?' The owner opens a page that lists bust, waist and hip for S-XL and nothing else. No garment measurements. No ease. No stretch note. No between-size guidance. No model fit note. She answers by hand, guesses, and waits to see whether the order comes back.

FitCard Forge turns that page into a structured artifact. Paste a dress URL; the app fetches the rendered page, extracts the size chart, product copy, fabric and stretch mentions and model notes, scores twelve fit-friction checks with quoted evidence, then emits a copy-paste Fit Card block and a prioritized fix list for that exact style. Where the source page has no data, the Fit Card prints an explicit blank. The product never invents a garment measurement. That constraint is also the sales argument: every number in the block traces to the brand's own page or its own input.

The JEV score of 58.7 (band C, confidence 0.67) is candid about the weak points. Speed to first revenue is the strongest dimension at 8.13/10, because it is one URL in and one artifact out for $49. Market demand (3.77) and operational simplicity (4.37) are the weakest. The plan responds accordingly: one narrow artifact, a self-serve paid path with no human review step, outreach starting on day 6 rather than day 20, and no feature whose value only lands after the window closes.

2. Smallest sellable MVP

Four things and nothing more: a URL input that returns a scored audit, a Fit Card generator with explicit placeholders, a CSV fix list, and Stripe checkout with email delivery. The MVP is sellable the moment one real dress page produces a Fit Card an owner would paste into her theme. Explicitly out of scope for the 30 days: Shopify app installs, automatic theme editing, photo-based body measurement, pattern or production files, team accounts, and any consumer-facing fit quiz. The demo runs in one pass: paste URL, fetch, twelve checks with evidence, Fit Card plus fix list, pay, receive email and dashboard link. Build target is five days.

3. Technical implementation plan

Next.js on Vercel; Supabase Postgres for audits, checks and orders; Browserless for rendered fetch; Cheerio for table and text parsing; OpenAI structured outputs for extraction and copy rewriting grounded strictly in source text; Stripe Checkout and Billing; Resend for delivery. Build order runs scaffold and schema, fetch and parse, twelve checks with evidence, Fit Card and CSV export, checkout and email, dashboard, then hardening. The hardest risk is a size chart published as a JPEG or a theme that blocks headless browsers. The mitigation is a manual paste-the-chart fallback and platform detection, not a promise of universal parsing. Every audit stores the fetched HTML so any disputed Fit Card can be traced back to its source.

4. Pricing and monetization

Three prices, one-time first: $49 Single Style Fit Card, $499 Catalog Fit Audit for up to 40 URLs, and $199 per month for a Monthly Refresh of 20 new styles. The $49 tier exists to remove the trust barrier and to be bought inside a DM thread. The $499 audit is the real unit of work and matches a launch budget an owner can approve alone. The upgrade path is explicit: single to catalog with the $49 credited, then to monthly refresh once new styles keep shipping.

5. First-customer acquisition

One channel: direct Instagram DM to small Shopify and WooCommerce dress brands that launched a collection in the last 30 days, with a 48-hour email follow-up to the same list. Build 150 named brands by hand, pre-generate a free Fit Card for one of their live pages, and open with a screenshot of a specific missing field on that exact page rather than a pitch. Send 50 touches in week two, follow up at 48 hours with the three biggest gaps, and ask for $49 or $499 in the same thread. No ads, no SEO, no marketplace. Week-one goal: MVP live, 150-brand list built, 20 DMs sent with 10 free Fit Cards attached.

6. 30-day execution roadmap

Days 1-5 build and ship the public MVP, with the deadline on day 5. Days 6-7 build the prospect list and send the first 20 DMs with pre-generated samples. Days 8-11 are volume outreach, 48-hour follow-ups and parser hardening against real pages. Day 12 is the first-sale target; days 13-14 deliver fast and convert delivery into a testimonial and a referral ask. Days 15-21 add self-serve $49 checkout, batch free samples, a bridal and occasion slice, a non-buyer email sequence, the $199 subscription and a cut-what-fails review. Days 22-28 push referrals, international brands, WooCommerce coverage, single-to-catalog upsells, one public teardown and a batch runner to cut delivery time. Days 29-30 collect outstanding payments, confirm they landed in the connected account, stop selling at 12:00 UTC on 16 December and write the retro. Each day carries exactly one deliverable; no day ends with 'in progress'.

7. Revenue and profit scenarios

All projections. Conservative: 3 customers at a blended $199, $597 gross, $24 in fees, $35 operating, giving $573 hackathon profit and $538 business profit. Base: 10 customers at a blended $289, $2,890 gross, one $49 refund, $116 in fees, $180 operating, giving $2,725 hackathon profit and $2,545 business profit. Upside: 24 customers at a blended $349, $8,376 gross, one $499 refund, $335 in fees, $400 of paid marketing and $420 operating, giving $7,142 hackathon profit and $6,722 business profit. The concept's original 200-customer target is treated as a ceiling that assumes a 10% sample-to-paid conversion; the base case assumes roughly 4% of 250 touches. Contest ranking uses hackathon profit, which does not deduct hosting or API costs; business profit does.

8. Risks and validation experiments

Five risks matter. Cold DM conversion may sit far below plan: test by sending 50 DMs in three days and counting replies before writing another feature. Image-based size charts may break the parser: test 20 real target URLs and record the auto-parse rate. Owners may read the output as advice rather than software: after each free sample ask one question, would you pay $49 for this page today, and require two yes answers out of five. Manual delivery may become the bottleneck: cap free samples at three per day and time one full catalog audit end to end. Payments may land after the window: sell card payments only through the connected checkout and stop selling before 13:00 UTC on day 30. Kill criteria are explicit - under 5% reply after 100 touches with zero paid customers by day 20 means stop building and go assisted-only; still zero by day 26 means the concept does not work in this window.

9. First 24-hour plan

Hours 0-2: create the repo, Vercel project and Supabase schema; the deliverable is a deployed stub. Hours 2-5: Browserless fetch plus Cheerio size-chart parsing tested on five live dress URLs. Hours 5-8: the twelve checks with evidence and the Fit Card HTML template. Hours 8-11: Stripe Checkout, Resend delivery and one paid test run on a real page. Hours 11-14: landing page with one sample Fit Card and the no-invented-measurements disclaimer. Hours 14-20: build the first 40-brand list and pre-generate five free Fit Cards. Hours 20-24: send the first ten DMs with screenshots attached and reply to anything that comes back.

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 →