GhostFit Model Lock
Turns a reseller's flat-lay garment photos into a consistent on-model image pack using one locked model identity, so every listing looks like a real brand shoot.
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.
Solo apparel resellers and micro-boutiques of 1-3 people doing 30-200 listings per month on Depop, Grailed, Vinted, Poshmark, eBay or a small Shopify store, triggered by a new inventory drop of 20+ pieces that needs photos this week.
Operational simplicity 4.5/10
Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.
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; 53 sales at $19 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.5/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.
Product opportunity and positioning
Target customer
Solo apparel resellers and micro-boutiques of 1-3 people doing 30-200 listings per month on Depop, Grailed, Vinted, Poshmark, eBay or a small Shopify store, triggered by a new inventory drop of 20+ pieces that needs photos this week.
Why now
Image-edit and background-removal APIs are cheap enough that a 30-garment pack can be delivered for a few dollars, and resellers already publish the exact flat-lay input publicly every day, so a prospect list and a free sample can be produced without ads, brand equity or partnerships.
Problem
Model-and-photographer shoots cost more per garment than the garment sells for, so resellers shoot flat on a bed; flat-lay listings underperform on-body ones, and one-off AI tools invent a different body, light and crop on every generation, so the storefront looks inconsistent.
Solution
Seller uploads flat-lay photos, picks a garment type, enters size-chart fields and selects one stored Model Lock; the pipeline removes the background, builds a garment mask, drapes the garment onto the locked model and returns a fixed 4-render set (front, back, 3/4, fabric detail) in 1:1 and 4:5 crops under 2MB, plus a listing CSV with filenames, alt text and a size-normalized fit note, delivered as a ZIP by email.
GhostFit Model Lock — 30-Day Public Report
1. Product opportunity and positioning
A reseller with 40 new pieces on a bed does not have a branding problem. They have a photo problem. A model-and-photographer shoot costs more per garment than the garment sells for, so the seller shoots flat on a sheet. Flat-lay listings underperform on-body listings, and every listing looks like a different store.
Generic AI image tools make this worse, not better. Each generation invents a new body, a new light and a new crop, so a 40-SKU catalog looks like 40 different shops and the seller re-does the images by hand. The missing primitive is not a better generator. It is a stored identity that is reused every time.
GhostFit Model Lock sells a fixed artifact instead of a creative tool. One stored model reference per account is reused for every generation, and the buyer receives a defined deliverable: four renders per garment on that same model, in two crops, plus a listing CSV. The buyer is a one-to-three-person apparel reseller doing 30-200 listings a month on Depop, Grailed, Vinted, Poshmark, eBay or a small Shopify store, triggered by a new drop that needs photos this week.
The JEV score for this concept is 66/100 (band B, confidence 0.64). Its strongest criteria are speed to first revenue (8.46 normalized) and reachable customers (8.13): resellers post flat-lays publicly, daily, with the exact garment visible, so the prospect list builds itself and the first paying customer needs no procurement cycle, no integration and no brand. Its weakest criterion is operational simplicity (4.49). The plan answers that by removing human retouching, team seats, per-garment model choice and any manual-QA promise from the sold deliverable, and by keeping every component on managed services.
The positioning line to use in every message: one locked model, one fixed pack, priced per drop.
2. Smallest sellable MVP
The product must be sellable on day 5, not day 15. The minimum artifact a stranger will pay $19 for is: upload one flat-lay, choose a garment type, enter chest and length, receive four renders on one stored model in 1:1 and 4:5 under 2MB, plus one CSV row with filename, alt text and fit note. Batch queueing, redo handling and account history can be a spreadsheet and an email the founder sends by hand during week one. Selling before the queue exists is a feature, not a shortcut.
3. Technical implementation plan
Next.js on Vercel serves the app and landing page. Supabase holds auth, Postgres job rows and image storage. fal.ai (Replicate as backup) handles background removal and the image-edit call that drapes the masked garment onto the account's stored model reference. Sharp does deterministic crops and compression, because output geometry must never drift between garments. Stripe Checkout with a webhook writes a credits ledger. Resend delivers the ZIP link.
Pipeline: upload, normalise to sRGB at max 2048px, remove background, build garment mask, call image-edit with the locked model reference and a garment-type prompt variant, return four outputs, crop to 1:1 and 4:5, assemble ZIP and CSV, email a signed URL.
The hardest technical risk is fidelity on logos, dense patterns and garment length. The answer is a per-garment-type prompt variant plus an explicit length field, with a logged pass rate per variant, so failures become a measured queue rather than a surprise refund.
4. Pricing and monetization
Three prices, card at checkout, no call. Sample Pack $19 for 3 garments and 12 renders. Drop Pack $99 for 30 garments, 120 renders, both crops, CSV with alt text and fit notes, one free redo batch. Restock Monthly $149 for 50 garments per month with Model Lock persisted.
The $19 pack exists to convert a DM into a card, not to make money. The $99 Drop Pack is the business. The $149 monthly is pitched only to someone who has already bought twice. Delivery cost per pack is bounded by garments times four renders at a fixed per-image API price, and the $99 price must stay comfortably above that bound; selling under cost would disqualify the product.
5. First-customer acquisition
One channel: direct DM to resellers who posted a flat-lay or hanger photo in the last seven days. Sources are r/Depop, r/Grailed, r/Vinted, r/Flipping, Facebook reseller groups, and Instagram hashtags #depopseller and #grailed. The opener names their specific garment and offers a free 3-garment sample rendered from their own photos with no signup. Deliver inside 24 hours with a side-by-side of their original. Then present the $99 Drop Pack, and follow up once at 72 hours. Log every handle, garment, reply and rejection reason in one sheet; the rejection taxonomy is the pricing and prompt roadmap.
6. 30-day execution roadmap
Days 1-5 are build only: repo, uploader, job queue, generation pipeline, Model Lock table, crop and ZIP assembly, Stripe credits, landing page with before/after built from garments the founder owns. Day 5 is the MVP deadline and the day a stranger could pay.
Days 6-9 are the first-sale sprint: the free sample path, 100-row prospect list, launch posts in r/Depop and r/Grailed, 40 DMs, samples delivered under 24 hours, first sale targeted for day 9.
Days 10-21 are conversion and hardening: prompt variants for the worst garment types, batch reliability, a DM script rewritten around the best-performing opener, a $129 price test against $99, a referral link, and a mid-point profit recomputation on day 14.
Days 22-30 are scale and close: Restock Monthly offers to repeat buyers, a 60-second demo screen recording, 100-120 DMs per day, chargeback prevention copy at checkout, one small paid test, a last-week re-DM to warm leads, and a day-30 reconciliation of Stripe against TrustMRR into a final profit statement.
7. Revenue and profit scenarios
All three scenarios are projections from stated assumptions, not verified revenue. Conservative: 6 buyers at a $78 blended ARPU, $468 gross, $426 hackathon profit, $386 business profit. Base: 22 buyers at $92, $2,024 gross, $1,799 hackathon profit, $1,669 business profit. Upside: 45 buyers at $99, $4,455 gross, $3,799 hackathon profit, $3,514 business profit. Hackathon profit deducts refunds, chargebacks, Stripe fees and paid ads only; business profit additionally deducts hosting, domain, tooling and image-API delivery cost.
8. Risks and validation
Fidelity failure on patterns and logos is the top refund driver and is tested with a 10-garment pass-rate sheet before any DM goes out. Channel bans are tested by posting in two communities under two formats in week one. API pricing changes are capped by measuring real cost per pack on five packs before scaling outreach. Chargebacks are reduced by attaching render thumbnails to the delivery email and stating the redo policy before checkout. Support backlog is avoided by templating the five most common questions by day 25.
9. First 24 hours
Hours 1-2: domain, Vercel project, Supabase, Stripe account connected to TrustMRR before any payment can be taken. Hours 3-6: uploader, job table and Sharp preprocessing. Hours 7-12: one garment through background removal and the image-edit call to four renders. Hours 13-18: Model Lock table, crops, ZIP, CSV and Resend delivery. Hours 19-24: landing page with three before/after pairs from the founder's own garments.
Smallest sellable MVP
A paid flow where a reseller uploads flat-lay photos, receives four renders of each garment on one stored model in 1:1 and 4:5 crops under 2MB, plus a CSV of filenames, alt text and fit notes, delivered as a ZIP email link.
Must-have features
- Flat-lay JPG/PNG uploader with garment-type selector and size-chart fields
- Background removal and garment-mask step via a managed image API
- One stored Model Lock reference per account, reused for every generation
- Fixed 4-render output per garment (front, back, 3/4, detail) in 1:1 and 4:5, sRGB, under 2MB
- ZIP plus listing CSV (filename, alt text, fit note) delivered by email link
- Stripe Checkout with a credits ledger metered per garment, account connected to TrustMRR before launch
- Landing page with before/after pairs built only from garments the founder owns
Explicitly out of scope
- No video, 360 spin or AR try-on
- No multi-model catalogs or per-garment model choice
- No Shopify app, OAuth or marketplace integration
- No human retouching or manual QA service
- No team seats, brand training or enterprise accounts
- No trend, pricing or sales analytics
Demo flow (what the buyer sees)
- Seller uploads 1-30 flat-lay photos
- Selects garment type and enters chest/length size fields
- Confirms the stored Model Lock for the account
- Job queue removes background and builds garment masks
- Image-edit call drapes each garment onto the locked model
- Sharp crops each render to 1:1 and 4:5 and compresses under 2MB
- ZIP plus CSV assembled and emailed as a signed link
- Seller downloads the pack and pastes alt text into listings
Technical implementation plan
Stack
Architecture
A single Next.js app owns upload, job creation and status. Supabase stores the account, its one Model Lock reference image, job rows and output objects. A background worker picks up queued jobs, calls background removal then the image-edit model with the locked reference and a garment-type prompt variant, writes four renders, runs Sharp for the fixed crop spec, then assembles a ZIP and CSV and hands a signed URL to Resend. Stripe webhooks only add credits; credits only gate job submission.
Build steps
- Create Next.js repo on Vercel, buy domain, provision Supabase project and storage bucket
- Build upload form with garment-type selector and size-chart fields
- Add Sharp preprocessing to sRGB at max 2048px and write job rows to Postgres
- Wire background removal and garment-mask step, store the mask
- Wire image-edit call using the account Model Lock reference plus garment-type prompt variant
- Store four render outputs and add retry with backoff on failed generations
- Implement Sharp crop spec to 1:1 and 4:5 under 2MB and verify with a size check
- Assemble ZIP plus listing CSV with filename, alt text and fit note
- Send delivery email through Resend with a signed download URL
- Add Stripe Checkout for three tiers, webhook credits ledger, and gate jobs on credits
- Publish landing page with before/after pairs from founder-owned garments
- Connect payment account to TrustMRR and run one end-to-end paid test before launch
AI components
- Background-removal model for isolating the flat-lay garment
- Image-edit/generative model that drapes the masked garment onto the stored Model Lock reference
- Prompt-variant selection logic keyed to garment type
- Alt-text generation for the listing CSV
Pricing and monetization
Sample Pack
Entry offerFor First-time buyer testing on 3 real garments
- 3 garments
- 12 renders (4 per garment)
- Listing CSV with alt text
Drop Pack
For Reseller processing a new inventory drop of 20-30 pieces
- 30 garments
- 120 renders
- 1:1 and 4:5 crops
- Listing CSV with alt text and fit notes
- One free redo batch
Restock Monthly
For Reseller listing continuously across months
- 50 garments per month
- Model Lock stored across months
- Listing CSV export
Model: Per-pack one-time pricing metered by garment count, with a monthly pack for continuous listers.
First revenue offer: A free 3-garment sample rendered from the reseller's own listing photos, delivered within 24 hours with a side-by-side, followed by the $99 Drop Pack with one free redo batch.
Expected ACV: $99
Upsell path: Sample Pack ($19) to Drop Pack ($99) to Restock Monthly ($149) offered only after a second Drop Pack purchase; add a second pack at the same price rather than discounting.
First-customer acquisition
Direct Instagram and Reddit DMs to resellers who posted flat-lay or hanger garment photos in the last 7 days.
Where to find them
- r/Depop recent image posts
- r/Grailed recent listings
- r/Vinted and r/Flipping threads
- Facebook reseller and flipping groups
- Instagram hashtags #depopseller and #grailed filtered to flat-lay posts
- Poshmark and eBay seller profiles with flat-lay thumbnails
Exact outreach motions
- Log 100 handles daily: garment, platform, post date, photo type
- DM naming the exact garment and offering a free 3-garment sample from their own photos
- Deliver the sample within 24 hours with a side-by-side comparison image
- Send the $99 Drop Pack link with the redo guarantee in the same thread
- Follow up once at 72 hours with a second garment rendered free
- Record every reply and rejection reason in one sheet for prompt and copy fixes
Message template
Hey — saw your deadstock Carhartt jacket on Depop. I built a tool that puts flat-lays on one consistent model so a whole drop looks like the same shoot. Want me to run 3 of your pieces free from the photos you already posted? No signup, I'll just DM back the images tomorrow.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Accounts, repo, domain
- Buy domain and deploy a Next.js skeleton on Vercel
- Provision Supabase project, Postgres and storage bucket
- Open Stripe and connect the payment account to TrustMRR
Deliverable: Live skeleton at the domain with Supabase and TrustMRR-connected Stripe ready.
Uploader and job queue
- Build upload form with garment-type selector and size fields
- Normalise uploads with Sharp to sRGB at max 2048px
- Create job rows and a status polling view
Deliverable: Founder can upload a flat-lay and see a queued job in the database.
Background removal to renders
- Call background removal and store the garment mask
- Call image-edit with the model reference and garment-type prompt
- Record real per-image API cost on five garments
Deliverable: One garment produces four renders end to end with a measured cost per render.
Model Lock, crops, ZIP, CSV
- Add Model Lock table with one stored reference per account
- Implement Sharp crops to 1:1 and 4:5 under 2MB
- Assemble ZIP plus listing CSV and email a signed link via Resend
Deliverable: A complete ZIP and CSV delivered by email from a single upload.
Checkout and landing page
- Add Stripe Checkout for all three tiers with a credits ledger
- Gate job submission on credits and test the paid path end to end
- Publish landing page with before/after pairs from founder-owned garments
Deliverable: Live paid flow: a stranger can buy and receive a pack today.
Free samples and prospect list
- Add a no-signup 3-garment sample path
- Shoot and render 10 founder-owned garments for the page
- Build a 100-row prospect sheet from r/Depop and r/Grailed
Deliverable: 20 free-sample renders and a 100-row prospect sheet.
First outreach wave
- Post a value-first thread in r/Depop and r/Grailed
- Send 40 DMs naming specific garments
- Publish three before/after posts on Instagram
Deliverable: 40 DMs sent, 5 replies, launch posts live.
Week 2 · Launch & first sale · 7 days
24-hour turnaround
- Deliver 15 free samples within 24 hours
- Log every rejection reason in the sheet
- Fix the top fidelity bug surfaced by samples
Deliverable: Sample delivery log with a ranked rejection taxonomy.
Convert replies to card
- DM 60 more resellers with the best sample attached
- Put the $19 Sample Pack link in every open thread
- Send the $99 Drop Pack offer to all repliers
Deliverable: First paying customer and first Stripe receipt.
Patterns, logos, length
- Add a pattern/logo guard prompt variant
- Add an explicit garment-length control field
- Re-run the 10 worst samples and log pass rate
Deliverable: Prompt variant v2 with a measured pass rate per garment type.
Volume
- Send 80 DMs across Reddit and Instagram
- Post in two Facebook reseller groups
- Comment on 20 recent flat-lay posts with specific garment notes
Deliverable: 80 DMs and 20 comments logged with handles and garment names.
Second purchase and proof
- Email every buyer the Restock Monthly upgrade
- Add a self-serve one-free-redo request flow
- Ask three buyers for permission to quote their before/after
Deliverable: Three usable testimonials and upgrade offers sent.
Reactivate non-responders
- Re-message 30 non-responders with a second garment rendered free
- Add checkout link to delivery email signature
- Track reply-to-paid rate by message variant
Deliverable: Reply-rate report and updated paid-customer count.
Profit and copy
- Recompute verified profit from Stripe and TrustMRR
- Cut the worst-converting message variant
- Rewrite the DM opener around the best performer
Deliverable: Profit sheet plus a new DM script.
Week 3 · Repeat & systematize · 7 days
New communities
- Post a flat-lay to on-model comparison in r/Flipping and r/eBaySellers
- Test two hashtag sets on Instagram
- Log which community produced replies, not just views
Deliverable: Two new community posts live with reply attribution.
Batch reliability
- Add retry with backoff on failed generations
- Cap concurrency and add job status emails
- Run a full 30-garment pack unattended
Deliverable: A 30-garment pack completes without manual intervention.
EU and Vinted sellers
- Send 100 DMs to US/UK resellers
- Send 25 DMs to Vinted/EU sellers in their timezone
- Update the rejection taxonomy in the sheet
Deliverable: 125 DMs sent and a codified rejection taxonomy.
$99 vs $129
- Create a second checkout link at $129 for new traffic
- Keep $99 for existing conversations
- Measure click-to-checkout on 50 landing visits
Deliverable: A price test result on 50 visits with a decision.
Crop and fit note accuracy
- Spot-check 100 renders against the original garments
- Fix crops on dresses and long coats
- Document the fit-note logic in the CSV generator
Deliverable: QA sheet with pass rate by garment type.
Buyer-driven leads
- Add a give-a-friend-3-free-garments link to delivery emails
- Ask five buyers to post their before/after
- Track referral clicks in the sheet
Deliverable: Referral link live and five asks sent.
Reallocate effort
- Recompute verified profit and cost per pack
- Identify the three best DM openers by reply and paid rate
- Set day 22-30 targets per channel
Deliverable: Revised plan with numeric targets for the final nine days.
Week 4 · Scale what works · 7 days
Restock Monthly
- Offer $149/mo to any buyer with two or more packs
- Enable recurring checkout and a failed-payment email
- Publish a short FAQ on Model Lock persistence
Deliverable: Recurring checkout live and offers sent to qualified buyers.
60-second proof
- Record a screen capture of a flat-lay becoming an on-model pack
- Publish it and pin it to the profile
- Add it as the first link in DM follow-ups
Deliverable: Demo video live and used in outreach.
Volume plus replies
- Send 120 DMs
- Comment on 30 recent Grailed listings
- Reply to every open thread within four hours
Deliverable: 120 DMs sent and a zero-unanswered-thread state.
Templates
- Write template answers for the top five questions
- Auto-attach redo instructions to delivery email
- Close all open support threads
Deliverable: Zero open support threads and a reusable answer library.
Expectation setting
- Add a render-sample disclaimer before checkout
- Attach render thumbnails to the delivery confirmation email
- Require email confirmation on Drop Pack purchase
Deliverable: Disclaimer and confirmation emails live.
Small ad experiment
- Run $50 of Instagram story ads on reseller interests
- Measure cost per checkout against organic
- Decide to keep or kill paid for the final three days
Deliverable: Ad result with a measured cost per checkout.
Last-week offer
- Re-DM 40 warm leads with launch pricing ending
- Offer remaining free sample slots
- Refresh the two best-performing before/after posts
Deliverable: 40 re-DMs sent and new paid count recorded.
Days 29-30 · Consolidate · 2 days
Maximum outreach
- Send 100 DMs
- Push the Sample Pack to every unanswered thread
- Publish two additional before/after posts
Deliverable: Final outreach batch logged with reply counts.
Reconcile and write
- Export Stripe revenue, refunds and fees
- Reconcile against TrustMRR verified figures
- Write a post-mortem with the next 30-day plan
Deliverable: Final profit statement and post-mortem.
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/Base/Upside: paid customers are acquired by DM and community posts, never by a marketplace.
- Conservative/Base/Upside: ARPU is a blend of Sample Pack ($19), Drop Pack ($99) and Restock Monthly ($149); the more buyers, the closer ARPU gets to $99.
- Payment processing assumed at Stripe rates near 2.9% + $0.30 per transaction, roughly 3.3-3.8% of collected revenue.
- Operating cost assumes delivery at or below $0.04 per render (4 renders per garment), plus roughly $20-30 per month of domain, hosting, database and email tooling.
- Base: 22 paid customers in 30 days from about 1,200 targeted DMs at a low single-digit paid rate.
- Upside: 45 paid customers requires roughly 1,500 DMs plus 5-8 community posts and daily sample delivery inside 24 hours.
- Refunds are budgeted at 5-6% of gross revenue in Base and Upside; no refunds assumed in Conservative.
- Chargebacks are 0 in Conservative and Base, and modeled only in Upside where volume and impulse DM buyers increase dispute risk.
- Paid marketing is 0 in Conservative, $60 in Base (one small retargeting test) and $250 in Upside (Instagram story ads).
- All three scenarios are projections from stated assumptions, not verified revenue, customers or traction.
Conservative
6 customers- Refunds
- $25
- Chargebacks
- $0
- Payment fees
- $17
- Paid marketing
- $0
- Hackathon profit
- $426
- Operating costs
- $40
- Business profit
- $386
Base case
22 customers- Refunds
- $99
- Chargebacks
- $0
- Payment fees
- $66
- Paid marketing
- $60
- Hackathon profit
- $1,799
- Operating costs
- $130
- Business profit
- $1,669
Optimistic
45 customers- Refunds
- $198
- Chargebacks
- $60
- Payment fees
- $148
- Paid marketing
- $250
- Hackathon profit
- $3,799
- Operating costs
- $285
- Business profit
- $3,514
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $418
- Payment fees (3.9%)
- $16
- Paid marketing
- $60
- Hackathon profit
- $342
- Business profit
- $212
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 scenario projections built from the stated assumptions, not verified revenue, existing customers or real traction.
Main risks and validation experiments
Risk 1Garment fidelity fails on logos, dense patterns and long silhouettes, causing refunds and redo batches.
Per-garment-type prompt variants, an explicit length field, and a logged pass rate before outreach scales.
Render 10 of the hardest garments the founder owns and score each on print scale, logo legibility and length; publish the pass rate in the DM.
If fewer than 6 of 10 hard garments pass without a redo after two prompt iterations, narrow the wedge to solids and denim only.
Risk 2Reddit and Facebook groups remove or ban promotional DMs, removing the primary channel.
Split volume across Reddit communities, Instagram DMs and direct replies to recent listing comments; never post the same copy twice.
Post in two communities under two formats in week one and record removals, replies and DMs received per community.
If two of the three communities ban or remove posts within seven days and DM reply rate stays under 5%, pivot acquisition to Instagram only.
Risk 3Image API price changes or rate limits break the per-pack delivery cost assumption.
Measure real cost per render on day 3, cap pack size at 30 garments, and keep a second provider integration ready.
Run five full 30-garment packs and compute actual API cost per pack against the $99 price.
If delivery cost per pack exceeds 25% of price after switching providers, cut pack size or raise the Drop Pack price.
Risk 4Impulse DM buyers file chargebacks that reduce verified profit.
Render thumbnails in the delivery email, a pre-checkout disclaimer, and a stated free redo instead of a refund as the first remedy.
Track refund and dispute rate against buyers who received the disclaimer versus those who did not.
If chargebacks plus refunds exceed 12% of gross revenue, require email confirmation and drop the $19 entry pack.
Risk 5Model Lock consistency degrades across garment types, forcing manual per-garment tuning that a solo founder cannot sustain.
Store the lock reference and prompt variant per account, and treat any per-garment manual override as a logged bug.
Generate the same 12 garments across three garment types and have three people judge whether the model looks like the same person.
If reviewers cannot agree the model is consistent across types, reposition the product as a per-garment-type pack rather than a single lock.
Risk 6Support backlog from packs plus redos overwhelms one person inside 30 days.
Template the five most common replies, cap daily accepted orders, and make redo requests self-serve.
Track minutes spent per customer per day for the first ten customers.
If support exceeds 20 minutes per customer and defects are not falling, temporarily cap intake rather than promising faster turnaround.
Hour-by-hour: the first 24 hours
Hours 1-2
- Buy the domain and create the Next.js repo on Vercel
- Open Stripe and connect the payment account to TrustMRR before any payment is possible
Output: Deployed skeleton and a live TrustMRR-connected payment account.
Hours 3-6
- Provision Supabase project, Postgres and storage
- Build the upload form with garment-type selector and size-chart fields
- Add Sharp normalisation to sRGB at max 2048px
Output: Working uploader that writes a normalised image and a job row.
Hours 7-12
- Wire background removal against one garment
- Call the image-edit model with a hardcoded model reference
- Store and display the four returned renders
Output: One garment rendered end to end with a measured per-render cost.
Hours 13-18
- Add the Model Lock table with one reference per account
- Implement Sharp crops to 1:1 and 4:5 under 2MB
- Generate the listing CSV and send the ZIP link via Resend
Output: A complete emailed pack from a single upload.
Hours 19-24
- Add Stripe Checkout for the Sample and Drop Packs
- Gate job submission on a credits ledger
- Publish the landing page with three before/after pairs from founder-owned garments
Output: A live, paid, end-to-end product that a stranger could buy on day two.
Full 30-day launch report
Read the full generated report
GhostFit Model Lock — 30-Day Public Report
1. Product opportunity and positioning
A reseller with 40 new pieces on a bed does not have a branding problem. They have a photo problem. A model-and-photographer shoot costs more per garment than the garment sells for, so the seller shoots flat on a sheet. Flat-lay listings underperform on-body listings, and every listing looks like a different store.
Generic AI image tools make this worse, not better. Each generation invents a new body, a new light and a new crop, so a 40-SKU catalog looks like 40 different shops and the seller re-does the images by hand. The missing primitive is not a better generator. It is a stored identity that is reused every time.
GhostFit Model Lock sells a fixed artifact instead of a creative tool. One stored model reference per account is reused for every generation, and the buyer receives a defined deliverable: four renders per garment on that same model, in two crops, plus a listing CSV. The buyer is a one-to-three-person apparel reseller doing 30-200 listings a month on Depop, Grailed, Vinted, Poshmark, eBay or a small Shopify store, triggered by a new drop that needs photos this week.
The JEV score for this concept is 66/100 (band B, confidence 0.64). Its strongest criteria are speed to first revenue (8.46 normalized) and reachable customers (8.13): resellers post flat-lays publicly, daily, with the exact garment visible, so the prospect list builds itself and the first paying customer needs no procurement cycle, no integration and no brand. Its weakest criterion is operational simplicity (4.49). The plan answers that by removing human retouching, team seats, per-garment model choice and any manual-QA promise from the sold deliverable, and by keeping every component on managed services.
The positioning line to use in every message: one locked model, one fixed pack, priced per drop.
2. Smallest sellable MVP
The product must be sellable on day 5, not day 15. The minimum artifact a stranger will pay $19 for is: upload one flat-lay, choose a garment type, enter chest and length, receive four renders on one stored model in 1:1 and 4:5 under 2MB, plus one CSV row with filename, alt text and fit note. Batch queueing, redo handling and account history can be a spreadsheet and an email the founder sends by hand during week one. Selling before the queue exists is a feature, not a shortcut.
3. Technical implementation plan
Next.js on Vercel serves the app and landing page. Supabase holds auth, Postgres job rows and image storage. fal.ai (Replicate as backup) handles background removal and the image-edit call that drapes the masked garment onto the account's stored model reference. Sharp does deterministic crops and compression, because output geometry must never drift between garments. Stripe Checkout with a webhook writes a credits ledger. Resend delivers the ZIP link.
Pipeline: upload, normalise to sRGB at max 2048px, remove background, build garment mask, call image-edit with the locked model reference and a garment-type prompt variant, return four outputs, crop to 1:1 and 4:5, assemble ZIP and CSV, email a signed URL.
The hardest technical risk is fidelity on logos, dense patterns and garment length. The answer is a per-garment-type prompt variant plus an explicit length field, with a logged pass rate per variant, so failures become a measured queue rather than a surprise refund.
4. Pricing and monetization
Three prices, card at checkout, no call. Sample Pack $19 for 3 garments and 12 renders. Drop Pack $99 for 30 garments, 120 renders, both crops, CSV with alt text and fit notes, one free redo batch. Restock Monthly $149 for 50 garments per month with Model Lock persisted.
The $19 pack exists to convert a DM into a card, not to make money. The $99 Drop Pack is the business. The $149 monthly is pitched only to someone who has already bought twice. Delivery cost per pack is bounded by garments times four renders at a fixed per-image API price, and the $99 price must stay comfortably above that bound; selling under cost would disqualify the product.
5. First-customer acquisition
One channel: direct DM to resellers who posted a flat-lay or hanger photo in the last seven days. Sources are r/Depop, r/Grailed, r/Vinted, r/Flipping, Facebook reseller groups, and Instagram hashtags #depopseller and #grailed. The opener names their specific garment and offers a free 3-garment sample rendered from their own photos with no signup. Deliver inside 24 hours with a side-by-side of their original. Then present the $99 Drop Pack, and follow up once at 72 hours. Log every handle, garment, reply and rejection reason in one sheet; the rejection taxonomy is the pricing and prompt roadmap.
6. 30-day execution roadmap
Days 1-5 are build only: repo, uploader, job queue, generation pipeline, Model Lock table, crop and ZIP assembly, Stripe credits, landing page with before/after built from garments the founder owns. Day 5 is the MVP deadline and the day a stranger could pay.
Days 6-9 are the first-sale sprint: the free sample path, a 100-row prospect list, launch posts in r/Depop and r/Grailed, 40 DMs, samples delivered under 24 hours, first sale targeted for day 9.
Days 10-21 are conversion and hardening: prompt variants for the worst garment types, batch reliability, a DM script rewritten around the best-performing opener, a $129 price test against $99, a referral link, and a mid-point profit recomputation on day 14.
Days 22-30 are scale and close: Restock Monthly offers to repeat buyers, a 60-second demo screen recording, 100-120 DMs per day, chargeback prevention copy at checkout, one small paid test, a last-week re-DM to warm leads, and a day-30 reconciliation of Stripe against TrustMRR into a final profit statement.
7. Revenue and profit scenarios
All three scenarios are projections from stated assumptions, not verified revenue. Conservative: 6 buyers at a $78 blended ARPU, $468 gross, $426 hackathon profit, $386 business profit. Base: 22 buyers at $92, $2,024 gross, $1,799 hackathon profit, $1,669 business profit. Upside: 45 buyers at $99, $4,455 gross, $3,799 hackathon profit, $3,514 business profit. Hackathon profit deducts refunds, chargebacks, Stripe fees and paid ads only; business profit additionally deducts hosting, domain, tooling and image-API delivery cost.
8. Risks and validation
Fidelity failure on patterns and logos is the top refund driver and is tested with a 10-garment pass-rate sheet before any DM goes out. Channel bans are tested by posting in two communities under two formats in week one. API pricing changes are capped by measuring real cost per pack on five packs before scaling outreach. Chargebacks are reduced by attaching render thumbnails to the delivery email and stating the redo policy before checkout. Support backlog is avoided by templating the five most common questions by day 25.
9. First 24 hours
Hours 1-2: domain, Vercel project, Supabase, Stripe account connected to TrustMRR before any payment can be taken. Hours 3-6: uploader, job table and Sharp preprocessing. Hours 7-12: one garment through background removal and the image-edit call to four renders. Hours 13-18: Model Lock table, crops, ZIP, CSV and Resend delivery. Hours 19-24: landing page with three before/after pairs from the founder's own garments.
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 →Main Image Passport
A batch fixer that turns a seller's raw product photo into a marketplace-compliant main image and returns a per-SKU compliance report showing exactly which image rules now pass.
ListingGrade
Turns one raw product photo into a marketplace-ready image pack — exact dimensions, pure-white background, correct product fill, and a pass/fail compliance report for Amazon, Etsy, Walmart, and TikTok Shop.
Champion Brief
Turns a prospect's reply and your product page into a forwardable one-page business case PDF for the buyer's boss.