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

Keystone Linesheet

Turns a small apparel brand's sample photos and factory costs into a print-ready wholesale line sheet, boutique order form and margin-checked price list in about 20 minutes.

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.30/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Cold Instagram DM outreach to small apparel brands visibly moving from print-on-demand into cut-and-sew.
Who pays

Owner-operator of a 1-5 person cut-and-sew or small-batch apparel brand (US, UK, EU, Canada), 1-3 years old, selling DTC via Shopify or Instagram, who has just been asked by a boutique for a line sheet.

Biggest execution risk

Monetization potential 4.5/10

Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.

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

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

0/11
Entry price
$99
Solo build
5 days
30d base revenue
$1,666
30d hackathon profit
$1,492
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of a 1-5 person cut-and-sew or small-batch apparel brand (US, UK, EU, Canada), 1-3 years old, selling DTC via Shopify or Instagram, who has just been asked by a boutique for a line sheet.

Why now

Vision models can read garment type, colourway and fabric cues from phone photos for pennies, and small brands are moving from print-on-demand into cut-and-sew right as boutiques place pre-season orders.

Problem

A stockist asks for a line sheet and the founder has none: sample photos in a camera roll, a per-unit factory quote, and a half-built spreadsheet with no defensible wholesale multiple.

Solution

Upload 5-40 sample photos plus factory cost per style; Keystone extracts style attributes into an editable table, applies a wholesale/MSRP multiple with a margin-floor flag, and exports a line sheet PDF, a boutique order form (XLSX + fillable PDF) and an internal margin sheet.

Differentiation · A Canva template still leaves the founder doing wholesale-vs-retail math in a spreadsheet, and a freelance designer takes days; Keystone produces the finished PDF plus a margin check that flags any style selling below cost.

1. Product opportunity and positioning

Keystone Linesheet is not a design tool. It is the document a small apparel brand suddenly needs the moment a boutique says yes.

The buyer is the owner-operator of a 1-5 person cut-and-sew brand, one to three years old, selling direct through Shopify or Instagram. They have already paid for samples and a factory deposit. Then a stockist DMs them: "can you send your wholesale catalogue?" The founder has sample photos in their camera roll, a per-unit cost from the factory, and a spreadsheet they never finished. They must now pick a wholesale price, an MSRP, a size run, colourways, MOQ per style and a lead time, lay it out so it looks like a real brand, and send it before the buyer loses interest. Set the multiple wrong and they either lose the account or sell the season at a loss.

The alternatives are all bad in the same way. A freelance designer takes days and costs more than the first order is worth. A Canva template looks improvised and still leaves the wholesale-vs-retail math in a spreadsheet. A PLM or CAD suite assumes a technical team that a two-person brand does not have. None of them close the loop between "what the factory charges me" and "what I can safely quote a boutique."

What makes this wedge sellable inside 30 days is the trigger. Demand is inbound and dated: the boutique is mid-conversation and needs one specific artifact this week. That removes the education problem, the SEO ramp, the marketplace cold start and the procurement cycle. The output has a fixed shape, so one developer can ship the whole pipeline in days, and the buyer is already spending real money on samples.

The JEV score for this concept is 63/100 (band C, confidence 0.70). Its strongest axis is speed to first revenue at 8.56, which matches the trigger-driven wedge above. Its weakest is monetization potential at 4.5, because a $99 one-time charge tied to one event has no repeat path. This plan addresses that directly: the margin flag is the value anchor (one flagged style pays for the tool many times over), the $199 Pro tier carries multi-stockist brands, and a season-refresh reorder gives repeat revenue without changing the one-time model. December is peak retail, so the pitch is sharpened for founders who are busy: one document, twenty minutes, send it tonight.

Section 2 of 8

Smallest sellable MVP

Photo upload plus factory cost in, one watermarked preview page out free, and a $99 Stripe payment that unlocks the line sheet PDF, boutique order form and margin sheet.

Must-have features

  • Photo upload with Vision-LLM attribute extraction into an editable review table
  • Pricing engine: unit cost to wholesale (2.0x default) to MSRP (2.2x wholesale), with MOQ, case pack, lead time and a per-style margin-floor flag
  • Brand kit form: logo, two colours, about blurb, ordering terms, contact block
  • PDF renderer: cover page plus one page per style
  • Boutique order form export (XLSX and fillable PDF) prefilled with SKUs, size grid and case packs
  • Internal margin sheet XLSX with margin percent and a red-flag list
  • Stripe Checkout gating the download behind a watermarked free preview
  • Hosted read-only share link with a PDF download button

Explicitly out of scope

  • No pattern drafting, grading, DXF or tech packs
  • No 3D visualisation or virtual sampling
  • No Shopify app or storefront integration
  • No multi-user accounts, roles or seats
  • No invoicing or payment collection between brand and boutique
  • No stockist marketplace or directory

Demo flow (what the buyer sees)

  1. Founder opens the site and starts a project with brand name and two colours.
  2. Uploads 8 sample photos and types the factory cost per style.
  3. Reviews the extracted table and corrects two or three fields.
  4. Sets wholesale multiple, MOQ, case pack and lead time; sees one style flagged red below the margin floor.
  5. Sees a watermarked preview page and pays $99 via Stripe Checkout.
  6. Downloads the line sheet PDF, order form XLSX/PDF and margin sheet, and shares the read-only link.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres and file storageVision-LLM API (Gemini Flash or GPT-4o-mini) for garment attribute extractionReact-PDF for the line sheet rendererSheetJS for XLSX exportsStripe Checkout for one-time payment gatingResend for delivery and share-link email

Architecture

A Next.js app on Vercel holds all UI. Photos upload straight to Supabase storage; a server route sends each photo to the Vision-LLM with a strict JSON schema and writes the extracted attributes into a Postgres table the founder can edit inline. The pricing engine is pure TypeScript, so margin flags recompute on every edit. On payment, a Stripe webhook flips the project to paid and a background route renders the PDF with React-PDF, builds the XLSX with SheetJS, stores both in Supabase and emails the links via Resend. The share link is a signed read-only route that serves the stored PDF.

Build steps

  1. Day 1: Next.js repo, Supabase schema for projects, styles, assets and payments, deployed skeleton.
  2. Day 2: Photo upload and Vision-LLM extraction into an editable review table, capped at 40 photos per project.
  3. Day 3: Pricing engine with wholesale/MSRP multiples, MOQ, case pack, lead time and margin-floor flagging.
  4. Day 4: React-PDF line sheet: cover page, style grid, one page per style.
  5. Day 5: Order form XLSX and fillable PDF, margin sheet XLSX, signed share link.
  6. Day 6: Watermarked free preview, Stripe Checkout, webhook, Resend delivery email.
  7. Day 7: Landing page with a sample output, then run twelve real builds to harden layout edge cases.

AI components

  • Vision-LLM extraction of style name guess, category, colourways, size range and fabric cues from phone photos
  • Rule-based margin flagging (no model) applied on top of extracted and manually entered costs
Hardest technical risk: PDF layout quality. If the generated line sheet looks improvised, founders will not send it to a buyer and the product has no value; the second risk is Vision-LLM mislabeling garment type or fabric, which the editable table must absorb without friction.
Section 3 of 8

Pricing and monetization

Linesheet Starter

Entry offer
$99 one-time

For Brand with 1-12 styles and one live boutique conversation

  • Print-ready line sheet PDF up to 12 styles
  • Boutique order form XLSX + fillable PDF
  • Margin sheet with margin percent per style
  • Hosted read-only share link

Linesheet Pro

$199 one-time

For Brand pitching a full season or several stockists

  • Everything in Starter up to 40 styles
  • Three tailored line sheet variants
  • Duplicate-and-edit for next season
  • 30 days of founder email support

Model: One-time purchase per line sheet, priced by style count, with a paid Pro tier for multi-stockist brands and a discounted season refresh.

First revenue offer: "Send me your sample photos and your factory cost per style and I will build the line sheet live with you in 15 minutes. You see the finished PDF before you pay; if it is good enough to send to that boutique, it is $99 and you download it before we hang up."

Expected ACV: $119

Upsell path: Blended ARPU rises through (a) Pro at $199 when a brand has multiple stockists, (b) a $49 season refresh that reuses the saved brand kit and pricing for the next drop, and (c) boutique-specific variants at $39 each. All remain one-time charges; no subscription is introduced.

Target customers
45
Revenue model
$4,455
Costs
$150
Profit model
$4,305
Section 4 of 8

First-customer acquisition

Primary channel

Cold Instagram DM outreach to small apparel brands visibly moving from print-on-demand into cut-and-sew.

Where to find them

  • Accounts posting factory sample boxes, cut-and-sew tags or '#smallbatchapparel' / '#cutandsew'
  • Brands whose captions say 'wholesale available', 'stockists wanted' or 'DM for wholesale'
  • r/streetwearstartup threads asking how to price wholesale or find a pattern maker
  • Shopify DTC apparel stores with 2-15 products and an 'About' page naming a small factory
  • Sewing TikTok and Reels creators who sell their own small-batch drops

Exact outreach motions

  • Build a 150-account list in a sheet with handle, brand size signal, and whether they mention wholesale.
  • DM 30-40 accounts per day with the line-sheet question, no link in the first message.
  • Book 15-minute live builds with anyone who replies, generate their line sheet on the call from their own public photos.
  • Ask for payment at the end of the call only if they say the PDF is sendable.
  • Post a 30-second screen recording of photo-to-PDF in r/streetwearstartup and two small-batch apparel threads.
  • Follow up once at day 4 with a screenshot of a line sheet built from that brand's public photos, plus the margin flag.

Message template

Saw you're doing cut-and-sew - if a boutique asks you for a line sheet this week, do you have one ready? I built a tool that turns your sample photos and factory cost per style into a print-ready line sheet and boutique order form in about 20 minutes. Want me to build yours live on a 15-min call so you can see it before deciding anything?
Week-one goal: 150 accounts listed, 210 DMs sent across days 8-14, at least 12 replies and 5 booked live builds.
Section 5 of 8

30-day execution roadmap

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

Repo and data model

  • Create Next.js repo and deploy an empty app to Vercel.
  • Define Supabase tables for projects, styles, assets and payments.
  • Sketch the three output artifacts on paper.

Deliverable: Deployed skeleton with working database.

Day 2Extraction

Photo to editable table

  • Build multi-photo upload to Supabase storage.
  • Wire Vision-LLM call returning strict JSON per style.
  • Build the editable review table with inline save.

Deliverable: Extraction working on five real garment photos.

Day 3Pricing

Multiples and margin floor

  • Implement unit cost to wholesale to MSRP with editable multiples.
  • Add MOQ, case pack and lead time per style.
  • Add margin percent calculation and red-flag list.

Deliverable: Pricing table that flags an under-margin style.

Day 4Line sheet PDF

Renderer

  • Build cover page with brand kit fields.
  • Build style grid page and one page per style.
  • Test layout with 3, 12 and 40 styles.

Deliverable: A print-ready PDF generated from test data.

Day 5Exports

Order form and margin sheet

  • Generate order form XLSX with SKUs, size grid and case packs.
  • Generate fillable order form PDF and margin sheet XLSX.
  • Add signed read-only share link.

Deliverable: All three artifacts exportable end to end.

Day 6PaymentsMVP shipped

Gate the download

  • Add watermarked preview page shown free.
  • Wire Stripe Checkout and the webhook that unlocks downloads.
  • Send the delivery email via Resend.

Deliverable: MVP complete and payable.

Day 7Launch prep

Evidence and list

  • Build landing page with one anonymised sample line sheet.
  • Run twelve real builds on public brand photos and fix layout breaks.
  • List 80 target accounts.

Deliverable: Launch-ready site plus a live list.

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

First 30 DMs

  • Send 30 DMs using the line-sheet question.
  • Book the first live builds.
  • Log every reply and objection in the sheet.

Deliverable: 30 DMs sent, at least 1 build booked.

Day 9Live builds

Concierge demos

  • Run 3 live 15-minute builds from founder photos.
  • Fix the top layout complaint found on calls.
  • Send 35 more DMs.

Deliverable: 3 line sheets built for real brands.

Day 10First conversion

Close the first payer

  • Ask every completed build for the $99 payment.
  • Remove the biggest friction found in checkout.
  • Send 30 more DMs.

Deliverable: First Stripe payment attempt in progress.

Day 11Community

Public proof

  • Post the 30-second screen recording in r/streetwearstartup.
  • Answer three wholesale-pricing threads with real numbers.
  • Follow up with everyone who replied but went quiet.

Deliverable: Public post live with at least 3 substantive comments.

Day 12First sale targetFirst sale target

Paid customer

  • Run 4 live builds.
  • Send payment link to each.
  • Send 40 more DMs.

Deliverable: First verified paid line sheet.

Day 13Proof

Testimonial and example

  • Ask each buyer for one sentence and permission to anonymise output.
  • Publish a second example line sheet on the landing page.
  • Add the strongest objection answer to the page.

Deliverable: One testimonial and two public examples.

Day 14Review

Message iteration

  • Count DMs, replies, builds and sales in the sheet.
  • Rewrite the DM opener based on what got replies.
  • Fix the single biggest drop-off in the flow.

Deliverable: Revised outreach copy and funnel numbers.

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

50 DMs a day

  • Send 50 DMs in two batches.
  • Post a second screen recording on TikTok.
  • Run 3 live builds.

Deliverable: 50 DMs and 3 builds logged.

Day 16Field requests

Fibre, care, origin

  • Add fibre composition, care instructions and country of origin fields.
  • Push them into the PDF and order form.
  • Announce the update to prior contacts.

Deliverable: Buyer-requested fields shipped.

Day 17Pro tier

Multi-stockist variant

  • Build duplicate-and-edit for a second season.
  • Ship three tailored line sheet variants per project.
  • Set the $199 Pro checkout.

Deliverable: Pro tier live and purchasable.

Day 18Referrals

Warm intros

  • Ask each buyer for one brand intro.
  • DM every referral with the buyer's name.
  • Run 2 live builds.

Deliverable: At least 5 warm referral conversations.

Day 19Follow-up

Day-4 screenshot

  • Send the day-4 follow-up with a line sheet built from their own public photos.
  • Send 50 new DMs.
  • Log which follow-up converts best.

Deliverable: Follow-up sequence running on autopilot scripts.

Day 20Trust

Handle refunds

  • Refund any build the buyer would not send.
  • Publish a plain 'what this is not' note on the page.
  • Collect two more testimonials.

Deliverable: Clean refund record and clearer page.

Day 21Review

Mid-point numbers

  • Recompute customers, revenue, fees and refunds.
  • Cut the outreach angle with the worst reply rate.
  • Set the week-four target.

Deliverable: Mid-point ledger and revised target.

Week 4 · Scale what works · 7 days
Day 22Season angle

Reorder pitch

  • Script the season-refresh offer for prior buyers.
  • Send it to every past customer.
  • Send 50 new DMs.

Deliverable: Season refresh offer in market.

Day 23Bundling

Raise average order

  • Offer boutique-specific variants at $39 to Pro buyers.
  • Add the bundle to checkout.
  • Run 3 live builds.

Deliverable: Bundle live with at least one attempt.

Day 24Case study

Before and after

  • Write a short post showing one photo set and the finished PDF.
  • Publish it on the site and in two threads.
  • Answer every comment same day.

Deliverable: One case study published.

Day 25Volume

60 DMs

  • Send 60 DMs in two batches.
  • Follow up day-4 on all earlier sends.
  • Run 3 live builds.

Deliverable: 60 DMs plus a full follow-up sweep.

Day 26Urgency

Window closing

  • Add a plain note that live builds end December 15.
  • Message everyone who replied but never bought.
  • Run 4 live builds.

Deliverable: Final-call message sent to the whole pipeline.

Day 27Communities

Facebook and forums

  • Post the case study in three small-batch apparel groups.
  • Answer five pricing questions with real margins.
  • Handle inbound replies within an hour.

Deliverable: Three community posts live.

Day 28Review

Close the pipeline

  • List every warm lead and their last touch.
  • Send a one-line payment link to each.
  • Reconcile Stripe payouts against builds delivered.

Deliverable: Closed pipeline and reconciled ledger.

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

Last builds

  • Run any booked builds.
  • Send the last follow-up to non-buyers.
  • Fix only bugs that block a sale.

Deliverable: Final builds delivered.

Day 30Reconcile

Report

  • Export Stripe revenue, refunds and fees.
  • Compute hackathon profit and business profit separately.
  • Submit the report and archive the ledger.

Deliverable: Verified ledger and submitted entry.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • Base case: 14 paid customers over 30 days from roughly 700-900 cold DMs and community touches, a projected 1.5-2% conversion of replies. Projection, not validated.
  • Conservative: 4 customers, driven by below-1% DM reply rates and December retail distraction.
  • Upside: 34 customers with a real Pro mix, lifting blended ARPU to about $128.
  • Payment fees assume Stripe at 2.9% + $0.30 domestic, blended to roughly 4.5% with international cards and Stripe Tax. Base and upside use 4.5%; conservative uses 4.5% rounded.
  • Ad spend is paid marketing only; all outreach here is organic DM and community posting, so the conservative and base cases carry $0. The upside case carries $150 for two boosted posts.
  • Operating costs cover Vercel, Supabase, domain, Resend and $1-3 of vision API usage per customer; hosting and AI costs are not deducted from hackathon profit.
  • Refunds are assumed at roughly one per 15 customers in the base and upside cases; chargebacks assumed zero because delivery is immediate and verified.
  • All figures are projections built from stated assumptions, not verified revenue or existing customers.

Conservative

4 customers
$396
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$18
Paid marketing
$0
Hackathon profit
$378
Operating costs
$30
Business profit
$348

Base case

14 customers
$1,666
collected revenue · avg payment $119
Refunds
$99
Chargebacks
$0
Payment fees
$75
Paid marketing
$0
Hackathon profit
$1,492
Operating costs
$70
Business profit
$1,422

Optimistic

34 customers
$4,352
collected revenue · avg payment $128
Refunds
$198
Chargebacks
$0
Payment fees
$196
Paid marketing
$150
Hackathon profit
$3,808
Operating costs
$140
Business profit
$3,668

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,386
Payment fees (3.9%)
$54
Paid marketing
$0
Hackathon profit
$1,332
Business profit
$1,262

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.

These are projections built from the stated assumptions. They are not verified revenue, existing customers or real traction, and they must be labelled as projections wherever they appear.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM reply rates for small brand accounts come in far below 1%, so 45 sales are unreachable solo.

Mitigation

Front-load 210 DMs in week two and switch to community posting plus warm referrals if replies stall.

Validation experiment

Send 40 DMs on day 8 and count replies within 48 hours.

Kill criteria

If fewer than 2 replies per 100 DMs after 150 sends, stop DM-only acquisition and pivot to Reddit, Facebook groups and referral intros.

Risk 2The generated PDF is not good enough for a founder to send to a real buyer, so nobody pays.

Mitigation

Show the finished preview before payment on live calls and fix the top layout complaint daily.

Validation experiment

Show three founders a line sheet built from their own public photos and ask 'would you send this tonight?'

Kill criteria

If 0 of 3 say yes twice in a row, stop outreach and rebuild the template before spending more DMs.

Risk 3Vision extraction mislabels garment type, colour or fabric and erodes trust in the whole document.

Mitigation

Keep the review table editable, default to manual entry on low-confidence fields, and never hide the correction step.

Validation experiment

Run 20 real garment photos and count how many fields each style needs corrected.

Kill criteria

If more than 40% of styles need three or more corrections, ship a manual-first table and treat extraction as a prefill only.

Risk 4It is a one-time purchase tied to a single event, so revenue does not repeat.

Mitigation

Sell the $199 Pro tier and a $49 season refresh that reuses the saved brand kit and pricing.

Validation experiment

Offer the season refresh to the first five buyers and record intent.

Kill criteria

If zero of five express interest, raise Starter to $149 and bundle a second variant rather than chasing volume.

Risk 5Boutiques demand fibre composition, care instructions and country of origin, forcing manual edits and refund requests.

Mitigation

Add those three fields plus a notes block to the PDF and order form by day 16.

Validation experiment

Ask every live-build call what their buyer requested beyond the sample PDF.

Kill criteria

If more than half of buyers add fields by hand after day 20, treat missing fields as a delivery defect and block the sale instead.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js repo, deploy to Vercel and connect Supabase.
  • Write the projects, styles, assets and payments schema.

Output: Deployed skeleton with a live database.

Hours 3-5

  • Build the brand kit form: name, logo, two colours, about blurb, terms, contact.
  • Store brand kit JSON per project.

Output: Brand kit saved against a project.

Hours 6-9

  • Build multi-photo upload to Supabase storage.
  • Call the Vision-LLM with a strict JSON schema on one image.

Output: One photo producing structured style attributes.

Hours 10-14

  • Build the editable review table with inline save.
  • Test on five real garment photos and note errors.

Output: Working extraction plus a correction log.

Hours 15-24

  • Draft the 150-account outreach list with wholesale signals.
  • Write the DM opener and the 15-minute live-build script.
  • Draft the landing page copy and sample PDF brief.

Output: Outreach list started, scripts written, page copy ready.

Complete report

Full 30-day launch report

Read the full generated report

Keystone Linesheet — 30-Day Launch Report

Contest window: 16 Nov 2026 13:00 UTC to 16 Dec 2026 13:00 UTC. One founder, one product, revenue counted only if collected inside the window through a TrustMRR-connected payment account.

1. Product opportunity and positioning

Keystone Linesheet is not a design tool. It is the document a small apparel brand suddenly needs the moment a boutique says yes.

The buyer is the owner-operator of a 1-5 person cut-and-sew brand, one to three years old, selling direct through Shopify or Instagram. They have already paid for samples and a factory deposit. Then a stockist asks for a wholesale line sheet. The founder has sample photos in a camera roll, a per-unit cost from the factory, and a spreadsheet they never finished. They must choose wholesale price, MSRP, size run, colourways, MOQ and lead time, make it look like a real brand, and send it before the buyer loses interest. Set the multiple wrong and they either lose the account or sell the season at a loss.

The alternatives are all bad in the same way. A freelance designer takes days and costs more than the first order is worth. A Canva template looks improvised and still leaves the wholesale-versus-retail math in a spreadsheet. A PLM or CAD suite assumes a technical team a two-person brand does not have. None of them connect what the factory charges to what the brand can safely quote.

The JEV score for this concept is 63/100, band C, confidence 0.70. Speed to first revenue scores 8.56 and matches the trigger-driven wedge: demand is inbound and dated, so there is no education problem, no SEO ramp, no marketplace cold start and no procurement cycle. Monetization scores 4.5, the weakest axis, because a $99 one-time charge tied to one event has no repeat path. This plan answers that with three levers: the margin flag as the value anchor, the $199 Pro tier for multi-stockist brands, and a $49 season refresh that reuses saved data. All remain one-time charges; no subscription is introduced.

December is peak retail, so the pitch stays narrow: one document, twenty minutes, send it tonight.

2. Smallest sellable MVP

The sellable unit is one flow: upload sample photos and factory costs, correct the extracted table, see a watermarked preview, pay $99, download the line sheet PDF, boutique order form and margin sheet.

Must-have: photo upload with Vision-LLM extraction into an editable table; pricing engine from unit cost to wholesale at 2.0x to MSRP at 2.2x with MOQ, case pack, lead time and a margin-floor flag; brand kit form; PDF renderer with cover and one page per style; order form in XLSX and fillable PDF; margin sheet XLSX; Stripe Checkout gating the download; signed read-only share link.

Out of scope by design: no pattern drafting, grading, DXF or tech packs, no 3D, no Shopify app, no accounts or seats, no invoicing between brand and boutique, no stockist marketplace. Each of those would double build time and none is required to close the first sale.

Build time is five days, with day six reserved for payment gating.

3. Technical implementation plan

Stack: Next.js on Vercel, Supabase for Postgres and file storage, a Vision-LLM (Gemini Flash or GPT-4o-mini) for attribute extraction, React-PDF for rendering, SheetJS for XLSX, Stripe Checkout, Resend for email.

Flow: photos upload to Supabase storage; a server route sends each image to the Vision-LLM with a strict JSON schema and writes attributes into a Postgres table the founder edits inline. The pricing engine is plain TypeScript so margin flags recompute on every keystroke. A Stripe webhook flips the project to paid, a background route renders the PDF and builds the XLSX files, stores them, and emails links. The share link is a signed read-only route serving the stored PDF.

Order of work: repo and schema, extraction, pricing, PDF, exports and share link, payment gating, landing page and twelve real builds.

The hardest technical risk is PDF layout quality. If the line sheet looks improvised, founders will not send it to a buyer and the product is worth nothing. The second risk is extraction accuracy on phone photos, which the editable table must absorb without adding friction.

4. Pricing and monetization

Starter is $99 one-time for up to 12 styles. Pro is $199 for up to 40 styles, three tailored variants, duplicate-and-edit and 30 days of founder support. Blended ARPU is modelled at $119 in the base case and $128 upside once Pro appears.

The offer that goes out this week: send sample photos and factory cost per style, get a line sheet built live in 15 minutes, see the finished PDF before paying, then $99 to download. Showing the artifact before asking for money is the whole conversion mechanism for a document this visual.

Repeat revenue comes from a $49 season refresh and $39 boutique-specific variants, both one-time. A typical buyer spends $299 on samples before they ever reach this decision, so $99 against a live boutique order is easy to justify. One red-flagged style that would have sold at a loss pays for the tool many times over, and that is the line used in every follow-up.

5. First-customer acquisition

One channel: cold Instagram DM to small apparel brands visibly moving from print-on-demand into cut-and-sew. Accounts posting factory sample boxes, using #smallbatchapparel or #cutandsew, or writing wholesale available or stockists wanted.

Build a 150-account list with handle, size signal and wholesale signal. Send 30-50 DMs a day from day 8. Opener is a question, not a pitch: if a boutique asks for a line sheet this week, do you have one? Anyone who replies gets a 15-minute live build using their own public photos. Payment is asked for only after they say the PDF is sendable. Follow up once at day 4 with a screenshot built from their photos plus the margin flag. In parallel, post a 30-second screen recording in r/streetwearstartup and answer pricing threads with real numbers.

Week-one goal: 150 accounts listed, 210 DMs sent, 12 replies, 5 booked builds.

6. 30-day roadmap

Days 1-7 build: schema, extraction, pricing engine, PDF, exports and share link, payment gating, then landing page and twelve real builds. MVP deadline is day 6.

Days 8-14 sell: outreach starts, three live builds, first paid conversion targeted at day 12, public post on day 11, testimonial and second example by day 13, funnel review on day 14.

Days 15-21 add depth: volume at 50 DMs a day, fibre/care/origin fields shipping on day 16, Pro tier live on day 17, referral asks, day-4 follow-up sequence, refunds handled cleanly on day 20, mid-point ledger on day 21.

Days 22-28 widen the order: season refresh offer, $39 boutique variants, a published case study, 60-DM day, final-call message, three community posts, pipeline reconciliation.

Days 29-30 close and report: remaining builds delivered, Stripe revenue, refunds and fees exported, hackathon profit and business profit computed separately, entry submitted.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue.

ScenarioCustomersARPUGross revenueRefundsFeesAd spendOperating
Conservative4$99$396$0$18$0$30
Base14$119$1,666$99$75$0$70
Upside34$128$4,352$198$196$150$140

Hackathon profit equals gross revenue minus refunds, chargebacks, payment fees and ad spend: $378 conservative, $1,492 base, $3,808 upside. Business profit subtracts operating costs as well: $348, $1,422, $3,668. Hosting and AI delivery costs are excluded from hackathon profit by rule, but they are small and covered by every single sale, so no unit is sold below cost.

Payment fees assume Stripe at roughly 4.5% blended with international cards and tax. Ad spend is zero in two cases because all acquisition is organic.

8. Risks and validation experiments

Low DM reply rate. Test with 40 sends on day 8 and count replies in 48 hours. If fewer than 2 replies per 100 sends after 150 DMs, pivot to communities and referrals.

PDF quality below send-worthy. Show three founders a line sheet built from their public photos and ask if they would send it tonight. If 0 of 3 say yes twice, rebuild the template before more outreach.

Extraction errors. Run 20 real garment photos and count corrections per style. If over 40% need three or more fixes, ship manual-first entry and keep extraction as prefill only.

One-time purchase with no repeat. Offer the season refresh to the first five buyers. If none show interest, raise Starter to $149 and bundle a second variant instead of chasing volume.

Missing buyer fields. Ask every call what their stockist requested beyond the sample. If more than half add fields by hand after day 20, treat it as a delivery defect.

9. First 24-hour action plan

Hours 1-2: repo, Vercel deploy, Supabase schema. Output: live skeleton.

Hours 3-5: brand kit form and storage. Output: brand kit saved per project.

Hours 6-9: multi-photo upload plus the first Vision-LLM call with a strict schema. Output: one photo producing structured attributes.

Hours 10-14: editable review table, tested on five real photos. Output: extraction plus an error log.

Hours 15-24: start the 150-account list, write the DM opener and live-build script, draft landing page copy. Output: outreach list, scripts, page copy.

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 →