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

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.

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.

Promising6.80/10
MVP build (solo)
4 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Direct outreach in Amazon FBA and Etsy seller communities on Reddit and Facebook, opening with a free one-image compliance check.
Who pays

Solo Amazon FBA or Etsy seller with 3–50 active SKUs in the US, UK or Canada, usually the founder or an operations generalist, triggered by a new SKU launch or a main-image suppression warning.

Biggest execution risk

Monetization potential 4.9/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 4 days; the plan targets a first sale on day 9; 21 sales at $49 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.9/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

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

0/8
Entry price
$49
Solo build
4 days
30d base revenue
$780
30d hackathon profit
$742
Section 1 of 8

Product opportunity and positioning

Target customer

Solo Amazon FBA or Etsy seller with 3–50 active SKUs in the US, UK or Canada, usually the founder or an operations generalist, triggered by a new SKU launch or a main-image suppression warning.

Why now

Marketplace enforcement is automated and unforgiving, background removal is a cheap managed API, and deterministic compositing with Sharp is reliable — so a verified, upload-ready pack is now a minutes-long job rather than a design brief.

Problem

Every marketplace enforces different image rules — pure white RGB 255, pixel minimums, ~85% product fill, no text on the main image, file-size caps — and one spec mistake suppresses a listing or kills conversion.

Solution

The seller uploads a raw product photo, picks marketplace presets, and receives a ZIP of exact-size sRGB images plus a PDF showing pass/fail per rule per channel.

Differentiation · A VA charges $5–$15 per image and still guesses at each spec; Canva and Photoroom return a cutout without a per-channel verdict; ListingGrade returns the files plus the compliance document that answers the rejection email.

ListingGrade — 30-Day Solo Launch Report

Window: Mon 16 Nov 2026 13:00 UTC to Wed 16 Dec 2026 13:00 UTC. One founder, no team, no funding. Revenue counts only if collected inside the window through the Stripe account connected to TrustMRR. No product, no customers and no payments before day 1.

1. Product opportunity and positioning

Marketplace main images are a compliance problem before they are a creative problem. Amazon, Etsy, Walmart and TikTok Shop each publish different minimum dimensions, background requirements, product-fill expectations, file-size caps and text restrictions. A seller running 3–50 SKUs usually has no designer — they have a phone camera, a Canva tab and, at the worst moment, a suppression notice on their best-selling listing.

The wedge is that the work is repetitive, the rules are checkable and the outcome is binary. ListingGrade does not sell "better photos"; it sells an accepted listing. The buyer uploads a raw product photo, picks marketplace presets, and receives a ZIP of correctly sized images on a pure white canvas plus a PDF showing pass/fail for every rule on every channel. That converts an aesthetic judgement into a verification purchase, which is why a $49 one-time pack can be an impulse buy rather than a trust-heavy platform sale.

Against the alternatives: a VA charges $5–$15 per image and still guesses at each spec; Canva and Photoroom produce a cutout but no per-channel, per-rule verdict; a Fiverr gig has the same turnaround problem as the VA. ListingGrade is the only one of those that returns a document the seller can check against the rejection email they already received.

2. Smallest sellable MVP

One product image in, one marketplace-ready pack out, paid for with a Stripe link. The MVP is the $49 Single Pack only: up to six source images for one product, four marketplace presets, a ZIP of exact-dimension sRGB files named by channel and role, and a one-page compliance PDF.

Everything else waits. No Amazon or Etsy API integration, no lifestyle scene generation, no text overlays, no subscription, no mobile app, no Photoshop plugin. Store Pack at $199 goes live on day 12 and Agency Pack at $499 on day 22 — only after the single pack shows it converts.

3. Technical implementation plan

Next.js on Vercel for the app and upload UI. A job is written to Supabase Postgres, the source image goes to Cloudflare R2, Photoroom (remove.bg as fallback) returns a cutout, and Sharp does the deterministic work: bounding box from the alpha channel, scale to the channel fill ratio, centre on a pure white RGB 255 canvas, clean edges, force the sRGB profile, encode to the channel's size cap. pdf-lib builds the report, Resend delivers the ZIP link and PDF, and Stripe Checkout with one-time prices gates every download.

The marketplace rules live in one versioned JSON file — dimensions, fill ratio, background rule, size cap, text rule, accepted formats, per channel. The compositor reads that file; the report reads the same file. That is the whole product: a rules file, a deterministic compositor, a PDF.

The hardest part is cutout quality on reflective, transparent and fuzzy products. Mitigation: pass those jobs into a manual-review flag and say so plainly in the PDF rather than shipping a silently wrong image.

4. Pricing and monetization

Three one-time prices, no subscription in the first 30 days. Single Pack $49 (one product, up to six images, four presets, PDF). Store Pack $199 (five products, up to 30 images, batch ZIP plus per-product PDFs). Agency Pack $499 (15 products, white-label reports, priority queue). One-time pricing matches the trigger: a seller fixes a listing when it breaks or launches, not on a monthly cadence.

Processing runs about 5% on Stripe. Delivery cost per pack is the background-removal call plus compute, roughly $0.30–$1.50 depending on image count, so every pack clears its own cost comfortably. Payment fees assume Stripe at 5% blended.

The repeat path is the SKU cycle: a Single Pack buyer with more SKUs is upsold to Store Pack at day 13 and again in post-purchase email; agencies carry the same product across multiple seller clients.

5. First-customer acquisition

One channel: direct outreach in Amazon FBA and Etsy seller communities on Reddit and Facebook. Find threads from the last 14 days containing "main image suppressed", "white background", "image requirements" or "listing rejected". Reply publicly with a one-line diagnosis, then DM offering a free single-image compliance check. Run the check, send the PDF and one fixed image within two hours, then attach the $49 Stripe link. Follow up at 48 hours with the before/after and the Store Pack option.

The free check is the entire sales motion. It is cheap to produce, it is verifiable, and it puts a finished deliverable in front of the buyer before any payment is requested. Paid ads are not used; spend stays at zero unless an experiment on day 24 justifies $150.

6. 30-day execution roadmap

Week 1 (days 1–5): build. Repo, Supabase schema, Stripe prices and the ruleset JSON on day 1; background removal and bounding box on day 2; the white-canvas compositor on day 3; Etsy, Walmart and TikTok Shop presets plus ZIP export on day 4; PDF report, Stripe gate and email delivery on day 5. Day 5 is the MVP deadline and it is a hard gate — production checkout with live keys.

Days 6–7: prove and open the door. Run ten of your own product photos through the pipeline, fix the top three failures, publish a sample pack and the free-check offer.

Week 2 (days 8–14): first revenue. Qualified lead list, 15 DMs, free checks returned within two hours, $49 link attached. Day 9 is the first-sale target. Days 10–14 widen the DM count, patch the top rejection reason, ship Store Pack, and start asking buyers for a one-line testimonial.

Week 3 (days 15–21): correctness and load. Re-verify every preset against current marketplace help pages and version the ruleset, force sRGB and add a checksum manifest, ship batch mode, automate the post-purchase email sequence, widen to Etsy and Walmart communities, and publish a refund policy that covers channel rejection.

Week 4 (days 22–28): margin. Ship Agency Pack, instrument the upgrade from Single to Store Pack, rewrite the landing page around suppression risk, run a third outreach wave of 40 DMs, cut per-pack cost, add a referral code, then a deadline bundle for the final 72 hours.

Days 29–30: close. Reconcile every Stripe charge to a delivered pack, confirm TrustMRR reflects all revenue, issue pending refunds, export the ledger, write the post-mortem.

7. Revenue and profit scenarios (projections only)

These are hypotheses, not verified revenue. Conservative: 4 packs at a $49 blended price, $196 gross, $0 refunds, $0 chargebacks, $10 payment fees, $0 ad spend, $30 operating cost — hackathon profit $186, business profit $156. Base: 12 packs at $65 blended (mix of Single and Store), $780 gross, $38 fees, $0 ad spend, $90 operating — hackathon profit $742, business profit $652. Upside: 30 packs at $78 blended with one Agency Pack, $2,340 gross, $98 refunds, $117 fees, $150 ad spend on one tested experiment, $240 operating — hackathon profit $1,975, business profit $1,735.

Hackathon profit excludes hosting, tooling and API delivery. Business profit includes them. Both are derived from the same inputs and both are projections.

8. Main risks and validation experiments

Cutout quality. Reflective, transparent and fuzzy products will fail. Test on 20 deliberately awkward images in week 3; if the manual-review rate exceeds 30%, narrow the marketing claim to opaque product categories rather than pretending.

Rules drift. A "compliant" report that is wrong is worse than no report. Mitigation is a versioned ruleset with a last-verified date printed in the PDF footer, re-checked every seven days. Kill criterion: a delivered pack rejected on a rule the report marked pass, twice.

Channel bans. Reddit and Facebook groups can restrict outreach. Test three communities in week 2 and track which converts; if all three close, move to seller Discord servers and direct email before spending anything on ads.

Willingness to pay. Sellers may prefer a $5 Fiverr gig. Experiment: offer the free check to 20 sellers and count how many click the $49 link. If fewer than 2 of 20 click, the price or the framing is wrong — not the channel.

9. First 24-hour action plan

Hours 1–2: scaffold the Next.js repo, deploy to Vercel, create the Supabase project and tables. Hours 3–5: write the marketplace ruleset JSON for all four channels and create the three Stripe one-time prices. Hours 6–8: integrate background removal and get a cutout back from a test image. Hours 9–12: implement the bounding box and white-canvas compositor for Amazon dimensions and verify fill ratio on three photos. The day ends with a deployed skeleton, a ruleset, and one correctly composed Amazon image — the two things everything else in the 30 days depends on.

Disclaimer: all revenue and profit figures above are projections built from stated assumptions, not verified revenue, customers or traction.

Section 2 of 8

Smallest sellable MVP

A paid $49 Single Pack: one product, up to six source images, four marketplace presets, a ZIP of exact-dimension sRGB files and a pass/fail compliance PDF, delivered by email after Stripe Checkout.

Must-have features

  • Upload a single image or ZIP and select Amazon, Etsy, Walmart or TikTok Shop presets
  • Background removal via managed API
  • Product bounding-box detection from the alpha channel
  • Deterministic compositor: pure white canvas, centering, fill-ratio enforcement, edge cleanup, sRGB export
  • Exact pixel dimensions and file-size caps with files auto-named by channel and role
  • Rule-based compliance PDF with pass/fail reasons per marketplace
  • Stripe Checkout with one-time pack credits and email delivery of ZIP plus report
  • Before/after preview page showing original, cutout and final image

Explicitly out of scope

  • Lifestyle scene generation or AI model photoshoots
  • Competitor ad cloning or ad creative generation
  • Text-overlay infographics or A+ content design
  • Amazon, Etsy, Walmart or TikTok Shop API integration
  • Subscription billing in the first 30 days
  • Mobile app or Photoshop plugin
  • Team accounts, SSO or approval workflows

Demo flow (what the buyer sees)

  1. Buyer uploads a raw phone photo or flat image
  2. Buyer selects marketplace presets (Amazon, Etsy, Walmart, TikTok Shop)
  3. System removes background and detects the product bounding box
  4. Compositor centres the product on a pure-white canvas at the channel fill ratio and exports at exact dimensions and size cap
  5. pdf-lib generates the pass/fail compliance report per channel
  6. Buyer pays $49 via Stripe Checkout
  7. ZIP and PDF are emailed and downloadable from the return page
Build plan

Technical implementation plan

Stack

Next.js on VercelStripe CheckoutPhotoroom API with remove.bg fallbackSharpCloudflare R2Supabase PostgresResendpdf-lib

Architecture

The Next.js app accepts an upload, writes a job row to Supabase and stores the original in R2. A serverless job calls the background-removal API, gets the cutout back, and Sharp derives the bounding box from the alpha channel. A single versioned ruleset JSON supplies per-channel dimensions, fill ratio, background rule, size cap and text rule; the compositor reads it to render each output and the report generator reads the same file to score pass/fail. Outputs are zipped into R2 with an expiring signed URL. Stripe Checkout webhooks mark a pack credit as paid and unlock delivery; Resend emails the ZIP link and the PDF.

Build steps

  1. Scaffold Next.js app with TypeScript and deploy to Vercel
  2. Create Supabase tables for jobs, orders, pack credits and deliverables
  3. Create three Stripe one-time prices and the checkout session endpoint
  4. Write the marketplace ruleset JSON for all four channels with a version field
  5. Integrate Photoroom background removal with remove.bg fallback
  6. Implement bounding-box detection and the white-canvas compositor with Sharp
  7. Add per-channel presets, file naming, ZIP packaging and R2 signed URLs
  8. Generate the compliance PDF with pdf-lib from the same ruleset
  9. Gate delivery behind the Stripe webhook and send ZIP plus PDF via Resend
  10. Build the before/after preview page and a public sample pack

AI components

  • Managed background-removal model (Photoroom, remove.bg fallback) for subject isolation
  • Deterministic geometric compositing with Sharp — no generative model in the output path
  • Optional lightweight text-presence heuristic to flag main images that may fail the no-text rule
Hardest technical risk: Background removal accuracy on reflective, transparent and fuzzy products — a bad cutout makes the whole pack unusable and cannot be fixed by compositing.
Section 3 of 8

Pricing and monetization

Single Pack

Entry offer
$49 one-time

For Seller fixing one product listing

  • 1 product
  • Up to 6 source images
  • 4 marketplace presets
  • Compliance PDF report

Store Pack

$199 one-time

For Seller launching or repairing 5 products

  • 5 products
  • Up to 30 source images
  • 4 marketplace presets
  • Batch ZIP and per-product compliance PDFs

Agency Pack

$499 one-time

For Small e-commerce agency managing multiple seller clients

  • 15 products
  • Up to 90 source images
  • White-label compliance reports
  • Priority processing queue

Model: One-time packs priced by product count, sold as credits through Stripe Checkout, with no subscription in the first 30 days.

First revenue offer: Free single-image compliance check plus one fixed image delivered within two hours, followed by the $49 Single Pack Stripe link for the rest of that product's images across all four marketplaces.

Expected ACV: $65

Upsell path: Single Pack buyers with more SKUs are offered Store Pack ($199) at the 48-hour follow-up and again in the post-purchase email; multi-client agencies move to Agency Pack ($499) with white-label reports.

Target customers
50
Revenue model
$2,450
Costs
$190
Profit model
$2,260
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach in Amazon FBA and Etsy seller communities on Reddit and Facebook, opening with a free one-image compliance check.

Where to find them

  • Reddit r/FulfillmentByAmazon, filtered to the last 14 days
  • Reddit r/EtsySellers and r/AmazonSeller
  • Reddit r/ecommerce and r/eBaySellers threads about image rejections
  • Facebook groups matching "Amazon FBA" and "Etsy Sellers"
  • Seller Discord servers for Amazon and Etsy operators
  • Public marketplace help pages for Amazon, Etsy, Walmart and TikTok Shop image requirements

Exact outreach motions

  • Reply publicly to a suppression or image-requirements thread with a one-line diagnosis of the likely failing rule — no pitch.
  • DM the poster: offer to run a free compliance check on their main image and return the PDF plus one fixed file.
  • Deliver within two hours, then attach the $49 Stripe link for the remaining images across four marketplaces.
  • Follow up at 48 hours with the before/after pair and the $199 Store Pack option.
  • Ask every buyer for a one-line testimonial and one referral to another seller.
  • Post a before/after case thread in the community that converts best, once per week.

Message template

Hey — saw your post about the main image issue. Most Amazon rejections on that are the background not being pure RGB 255 or the product sitting under ~85% of the frame. I built a free checker that tells you exactly which rule your image fails and hands back a fixed version at the right size for Amazon, Etsy, Walmart and TikTok Shop. Want me to run your main image? No charge, I'll send the report back today.
Week-one goal: Landing page live, sample pack published, five free compliance checks delivered and 15 qualified DMs sent before day 8.
Section 5 of 8

30-day execution roadmap

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

Repo, data model, Stripe, ruleset

  • Scaffold Next.js app with TypeScript and deploy to Vercel.
  • Create Supabase tables for jobs, orders, pack credits and deliverables.
  • Create three Stripe one-time prices at $49, $199 and $499.
  • Write the marketplace ruleset JSON for all four channels.

Deliverable: Deployed skeleton with Stripe test checkout and a versioned ruleset file.

Day 2Cutout pipeline

Background removal and bounding box

  • Integrate Photoroom background removal with remove.bg as fallback.
  • Compute the product bounding box from the alpha channel with Sharp.
  • Store originals and cutouts in R2 with signed URLs.
  • Add a job status polling endpoint.

Deliverable: Upload to cutout to bounding box working end to end.

Day 3Compositor

White canvas, fill ratio, exact dimensions

  • Build the white-canvas compositor with configurable fill ratio.
  • Add edge cleanup and centering offsets.
  • Export at Amazon preset dimensions and file-size cap.
  • Write unit tests for fill-ratio tolerance.

Deliverable: Amazon-compliant output from a raw phone photo.

Day 4Presets and packaging

Four channels, ZIP, naming

  • Add Etsy, Walmart and TikTok Shop presets.
  • Name output files by channel, role and dimensions.
  • Zip outputs and store to R2 with an expiry.
  • Build the ZIP download page keyed by job token.

Deliverable: Four-marketplace ZIP per product.

Day 5MVP deadlineMVP shipped

Report, checkout, delivery

  • Generate the pass/fail PDF with pdf-lib from the ruleset.
  • Gate delivery behind the Stripe Checkout webhook.
  • Email the ZIP and PDF via Resend.
  • Deploy to production with live Stripe keys.

Deliverable: A paid $49 pack deliverable running in production.

Day 6Self-test

Ten real photos, fix failures

  • Run ten of your own product photos through the pipeline.
  • Log every failed check and fix the top three.
  • Build the before/after preview page.
  • Publish a sample pack PDF as a public download.

Deliverable: Known-issue list and a public sample pack.

Day 7Soft launch

Landing page and free-check offer

  • Write the landing page: what you get, what it checks, sample report.
  • Post the free compliance-check offer in two seller subreddits.
  • Add a refund policy and a support email.
  • Set up a tracking sheet for outreach, checks and revenue.

Deliverable: Live landing page and the first free-check requests.

Week 2 · Launch & first sale · 7 days
Day 8Lead list

Qualify and first DMs

  • Collect 100 recent threads matching suppression and image keywords.
  • Qualify 40 sellers with an active main-image question.
  • Draft three DM variants.
  • Send the first 15 DMs.

Deliverable: 40-qualified-lead list and 15 DMs sent.

Day 9First sale targetFirst sale target

Free checks delivered fast

  • Run free compliance checks for every requester.
  • Send the PDF plus one fixed image within two hours.
  • Attach the $49 Stripe link to each reply.
  • Log objections verbatim.

Deliverable: Ten free reports delivered with the $49 link attached.

Day 10Follow-up

Momentum and patch top failure

  • Follow up the 48-hour list.
  • DM 25 more sellers.
  • Patch the most common rejection reason found in free checks.
  • Add a text-presence warning for main images.

Deliverable: 25 more conversations and a patched rule warning.

Day 11Quality

Hard products and honest limits

  • Flag reflective and transparent failures for manual review.
  • Add a 'needs manual attention' block to the PDF.
  • Test 20 heterogeneous product images.
  • Document known limitations on the site.

Deliverable: Failure taxonomy reflected in product and copy.

Day 12Store Pack

Second tier live

  • Ship the $199 Store Pack behind the same pipeline.
  • Add multi-product upload for up to five products.
  • Post one before/after case thread in a seller community.
  • Offer Store Pack to every multi-SKU requester.

Deliverable: Store Pack live and one public case thread.

Day 13Proof and payouts

Testimonials and payment sync

  • Email 48-hour follow-ups with before/after pairs.
  • Ask every buyer for a one-line testimonial.
  • Publish testimonials only where consent exists.
  • Confirm Stripe payouts sync to TrustMRR.

Deliverable: Verified payment sync and first consented testimonials.

Day 14Week 2 review

Measure and refill pipeline

  • Count free checks, DMs, replies and paid packs.
  • Cut the outreach variant with the lowest reply rate.
  • Set a week 3 target of 12 paid packs.
  • Refill the lead list with 60 new threads.

Deliverable: Week 2 metrics sheet and week 3 plan.

Week 3 · Repeat & systematize · 7 days
Day 15Rules hardening

Re-verify every preset

  • Re-verify each preset against current marketplace help pages.
  • Version the ruleset with a changelog.
  • Print a last-verified date in the PDF footer.
  • Add per-rule explanation text to the report.

Deliverable: Ruleset v1.1 shipped with verification date.

Day 16Export correctness

Colour profile and caps

  • Force the sRGB profile on every export.
  • Validate JPEG quality against each channel size cap.
  • Add dual PNG and JPEG output where accepted.
  • Add a checksum manifest inside the ZIP.

Deliverable: Verified sRGB exports with a manifest.

Day 17Batch mode

Up to 10 products

  • Build the multi-product upload UI for up to 10 products.
  • Queue jobs with per-product status.
  • Generate one PDF per product inside a master ZIP.
  • Load-test 10 concurrent products.

Deliverable: Batch mode shipped for Store and Agency packs.

Day 18Lifecycle email

Post-purchase sequence

  • Write a three-email sequence: delivery, 48-hour check-in, Store Pack offer.
  • Add Resend templates and triggers.
  • Add a one-click re-run link for the same product.
  • Instrument open and click events.

Deliverable: Automated post-purchase sequence live.

Day 19Proof

Real case material

  • Collect and publish consented before/after pairs.
  • Add a numbers block: images processed, checks failed then fixed.
  • Write one short case note per consenting buyer.
  • Refresh the landing page hero with a real example.

Deliverable: Case page built from consenting buyers only.

Day 20Channel widening

Etsy and Walmart communities

  • Post in two Etsy and one Walmart seller community.
  • Answer 20 image-rule questions without pitching.
  • Offer a free check in each thread.
  • Track which community converts best.

Deliverable: Channel conversion table with three rows.

Day 21Support burden

Self-serve and refund policy

  • Write an FAQ covering the ten most common questions.
  • Add an in-app job status page.
  • Cap manual review at 15 minutes per pack.
  • Publish a refund policy covering channel rejection.

Deliverable: FAQ and refund policy published.

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

Third tier and agency outreach

  • Ship the $499 Agency Pack with 15 products.
  • Add a white-label toggle that removes the logo from reports.
  • List 20 small e-commerce agencies with seller clients.
  • Send 10 agency DMs.

Deliverable: Agency Pack live and 10 agency conversations started.

Day 23Upsell

Single to Store conversion

  • Email Single Pack buyers a Store Pack upgrade offer.
  • Add an in-app upgrade button.
  • Track upgrade rate per cohort.
  • Test one bundle: two Store Packs for $349.

Deliverable: Upsell path instrumented and one bundle tested.

Day 24Conversion

Landing page v2

  • Rewrite the headline around suppression risk.
  • Add a three-step how-it-works with real screenshots.
  • Place the sample PDF above the fold.
  • Test the headline on 20 seller messages.

Deliverable: Landing page v2 shipped.

Day 25Outreach wave 3

Volume on the best variant

  • Send 40 new DMs with the best-performing variant.
  • Follow up every unanswered thread once.
  • Re-run free checks for anyone who stalled.
  • Log every stated reason for no.

Deliverable: 40 DMs sent and the objection list updated.

Day 26Cost and speed

Unit economics

  • Measure per-pack API cost and processing time.
  • Cache cutouts for re-runs of the same source image.
  • Reduce redundant image re-encode passes.
  • Keep per-pack delivery cost under $1.50.

Deliverable: Costed per-pack unit economics.

Day 27Referral

Cheap second-order reach

  • Add a referral code worth $20 off for both sides.
  • Ask every buyer to share it with one other seller.
  • Post the offer in the two best communities.
  • Track referral-attributed packs.

Deliverable: Referral mechanic live and tracked.

Day 28Final push

Deadline bundle

  • Announce the contest deadline with a 72-hour bundle.
  • Email the full contact list one last time.
  • Post in every active community.
  • Answer inbound questions within 30 minutes.

Deliverable: Final-week campaign sent across all channels.

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

Revenue and fees

  • Match every Stripe charge to a delivered pack.
  • Confirm TrustMRR reflects all revenue.
  • Issue any pending refunds.
  • Export the revenue and fee CSV.

Deliverable: Reconciled revenue ledger.

Day 30Close

Post-mortem

  • Write the post-mortem: what sold, what stalled, unit cost.
  • Decide post-contest pricing.
  • Publish a public build summary.
  • Tag a release and archive the ruleset.

Deliverable: Post-mortem, tagged release and public summary.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • Conservative: 4 Single Packs at $49 with no refunds and no paid marketing.
  • Base: 12 packs at a $65 blended price, roughly nine Single and three Store Packs.
  • Upside: 30 packs at a $78 blended price including one Agency Pack.
  • All scenarios assume Stripe at about 5% blended processing fees.
  • Operating costs cover Vercel, domain, Supabase, R2, Resend and background-removal API credits only; they are not deducted from hackathon profit.
  • Paid marketing is zero except the upside case, where $150 is spent on one tested experiment.
  • Per-pack delivery cost is roughly $0.30 to $1.50, so no pack is sold below cost.
  • One founder can fulfil up to 30 packs in the window at under 20 minutes of hands-on time each.
  • No customers, revenue or traction exist before launch; every figure is a projection.

Conservative

4 customers
$196
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$10
Paid marketing
$0
Hackathon profit
$186
Operating costs
$30
Business profit
$156

Base case

12 customers
$780
collected revenue · avg payment $65
Refunds
$0
Chargebacks
$0
Payment fees
$38
Paid marketing
$0
Hackathon profit
$742
Operating costs
$90
Business profit
$652

Optimistic

30 customers
$2,340
collected revenue · avg payment $78
Refunds
$98
Chargebacks
$0
Payment fees
$117
Paid marketing
$150
Hackathon profit
$1,975
Operating costs
$240
Business profit
$1,735

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$588
Payment fees (3.9%)
$23
Paid marketing
$0
Hackathon profit
$565
Business profit
$475

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 scenarios are projections built from stated assumptions, not verified revenue, customers or traction. Hackathon profit excludes hosting, tooling and API delivery costs; business profit includes them.

Section 7 of 8

Main risks and validation experiments

Risk 1Background removal fails on reflective, transparent or fuzzy products, producing unusable cutouts.

Mitigation

Flag those jobs for manual review and state the limitation in the PDF and on the site instead of shipping a silently wrong image.

Validation experiment

Run 20 deliberately awkward product images through the pipeline in week 3 and count the manual-review rate.

Kill criteria

If more than 30% of real customer images need manual rescue, narrow the marketing claim to opaque product categories or stop.

Risk 2Marketplace rules change or are interpreted inconsistently, so a pass in the report is wrong.

Mitigation

Keep one versioned ruleset with a last-verified date printed in every PDF and re-verify weekly.

Validation experiment

Track every buyer-reported rejection against the report's verdict for the first 15 packs.

Kill criteria

Two delivered packs rejected on a rule the report marked pass, with no rule update in between.

Risk 3Sellers prefer a free Canva or Photoroom cutout, or a $5 Fiverr gig, over a $49 pack.

Mitigation

Lead with the per-channel verdict document rather than the image, since free tools do not produce a compliance artifact.

Validation experiment

Offer the free check to 20 sellers and count clicks on the $49 link.

Kill criteria

Fewer than 2 of 20 click through after receiving a free report — repricing or reframing required.

Risk 4Reddit and Facebook communities restrict direct outreach, starving the only acquisition channel.

Mitigation

Contribute answers before pitching, keep DMs short, and spread across three communities plus seller Discord servers.

Validation experiment

Post in three communities in week 2 and record replies and removals per community.

Kill criteria

All three communities remove posts or ban the account within 72 hours, with no alternative channel producing replies.

Risk 5Manual QA per pack becomes a bottleneck above expected volume.

Mitigation

Cap review at 15 minutes per pack, automate the pass/fail scoring and reserve hands-on work for flagged jobs only.

Validation experiment

Time five consecutive packs end to end and record hands-on minutes per pack.

Kill criteria

Average hands-on time exceeds 45 minutes per pack while volume is still under 10 packs per week.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Scaffold the Next.js app with TypeScript and deploy to Vercel.
  • Create the Supabase project and the jobs, orders and deliverables tables.

Output: Live deployment URL and a migrated database schema.

Hours 3-5

  • Write the marketplace ruleset JSON for Amazon, Etsy, Walmart and TikTok Shop.
  • Create the three Stripe one-time prices and the checkout session endpoint.

Output: Versioned ruleset file and a working Stripe test checkout.

Hours 6-8

  • Integrate the Photoroom background-removal API with a remove.bg fallback.
  • Store the original and the cutout in Cloudflare R2 with signed URLs.

Output: A verified cutout returned from one real product photo.

Hours 9-12

  • Implement bounding-box detection from the alpha channel.
  • Build the white-canvas compositor and export one Amazon-dimension image.

Output: One correctly composed, correctly sized Amazon main image produced by the pipeline.

Complete report

Full 30-day launch report

Read the full generated report

ListingGrade — 30-Day Solo Launch Report

Window: Mon 16 Nov 2026 13:00 UTC to Wed 16 Dec 2026 13:00 UTC. One founder, no team, no funding. Revenue counts only if collected inside the window through the Stripe account connected to TrustMRR. No product, no customers and no payments before day 1.

1. Product opportunity and positioning

Marketplace main images are a compliance problem before they are a creative problem. Amazon, Etsy, Walmart and TikTok Shop each publish different minimum dimensions, background requirements, product-fill expectations, file-size caps and text restrictions. A seller running 3–50 SKUs usually has no designer — they have a phone camera, a Canva tab and, at the worst moment, a suppression notice on their best-selling listing.

The wedge is that the work is repetitive, the rules are checkable and the outcome is binary. ListingGrade does not sell "better photos"; it sells an accepted listing. The buyer uploads a raw product photo, picks marketplace presets, and receives a ZIP of correctly sized images on a pure white canvas plus a PDF showing pass/fail for every rule on every channel. That converts an aesthetic judgement into a verification purchase, which is why a $49 one-time pack can be an impulse buy rather than a trust-heavy platform sale.

Against the alternatives: a VA charges $5–$15 per image and still guesses at each spec; Canva and Photoroom produce a cutout but no per-channel, per-rule verdict; a Fiverr gig has the same turnaround problem as the VA. ListingGrade is the only one of those that returns a document the seller can check against the rejection email they already received.

2. Smallest sellable MVP

One product image in, one marketplace-ready pack out, paid for with a Stripe link. The MVP is the $49 Single Pack only: up to six source images for one product, four marketplace presets, a ZIP of exact-dimension sRGB files named by channel and role, and a one-page compliance PDF.

Everything else waits. No Amazon or Etsy API integration, no lifestyle scene generation, no text overlays, no subscription, no mobile app, no Photoshop plugin. Store Pack at $199 goes live on day 12 and Agency Pack at $499 on day 22 — only after the single pack shows it converts.

3. Technical implementation plan

Next.js on Vercel for the app and upload UI. A job is written to Supabase Postgres, the source image goes to Cloudflare R2, Photoroom (remove.bg as fallback) returns a cutout, and Sharp does the deterministic work: bounding box from the alpha channel, scale to the channel fill ratio, centre on a pure white RGB 255 canvas, clean edges, force the sRGB profile, encode to the channel's size cap. pdf-lib builds the report, Resend delivers the ZIP link and PDF, and Stripe Checkout with one-time prices gates every download.

The marketplace rules live in one versioned JSON file — dimensions, fill ratio, background rule, size cap, text rule, accepted formats, per channel. The compositor reads that file; the report reads the same file. That is the whole product: a rules file, a deterministic compositor, a PDF.

The hardest part is cutout quality on reflective, transparent and fuzzy products. Mitigation: pass those jobs into a manual-review flag and say so plainly in the PDF rather than shipping a silently wrong image.

4. Pricing and monetization

Three one-time prices, no subscription in the first 30 days. Single Pack $49 (one product, up to six images, four presets, PDF). Store Pack $199 (five products, up to 30 images, batch ZIP plus per-product PDFs). Agency Pack $499 (15 products, white-label reports, priority queue). One-time pricing matches the trigger: a seller fixes a listing when it breaks or launches, not on a monthly cadence.

Processing runs about 5% on Stripe. Delivery cost per pack is the background-removal call plus compute, roughly $0.30–$1.50 depending on image count, so every pack clears its own cost comfortably.

The repeat path is the SKU cycle: a Single Pack buyer with more SKUs is upsold to Store Pack at the 48-hour follow-up and again in the post-purchase email; agencies carry the same product across multiple seller clients.

5. First-customer acquisition

One channel: direct outreach in Amazon FBA and Etsy seller communities on Reddit and Facebook. Find threads from the last 14 days containing "main image suppressed", "white background", "image requirements" or "listing rejected". Reply publicly with a one-line diagnosis, then DM offering a free single-image compliance check. Run the check, send the PDF and one fixed image within two hours, then attach the $49 Stripe link. Follow up at 48 hours with the before/after and the Store Pack option.

The free check is the entire sales motion. It is cheap to produce, it is verifiable, and it puts a finished deliverable in front of the buyer before payment is requested. Paid ads are not used; spend stays at zero unless an experiment on day 24 justifies $150.

6. 30-day execution roadmap

Week 1 (days 1–5): build. Repo, Supabase schema, Stripe prices and the ruleset JSON on day 1; background removal and bounding box on day 2; the white-canvas compositor on day 3; Etsy, Walmart and TikTok Shop presets plus ZIP export on day 4; PDF report, Stripe gate and email delivery on day 5. Day 5 is the MVP deadline and a hard gate — production checkout with live keys.

Days 6–7: prove and open the door. Run ten of your own product photos through the pipeline, fix the top three failures, publish a sample pack and the free-check offer.

Week 2 (days 8–14): first revenue. Qualified lead list, 15 DMs, free checks returned within two hours, $49 link attached. Day 9 is the first-sale target. Days 10–14 widen the DM count, patch the top rejection reason, ship Store Pack, and ask buyers for a one-line testimonial.

Week 3 (days 15–21): correctness and load. Re-verify every preset against current marketplace help pages and version the ruleset, force sRGB and add a checksum manifest, ship batch mode, automate the post-purchase email sequence, widen to Etsy and Walmart communities, and publish a refund policy covering channel rejection.

Week 4 (days 22–28): margin. Ship Agency Pack, instrument the Single-to-Store upgrade, rewrite the landing page around suppression risk, run a third outreach wave of 40 DMs, cut per-pack cost, add a referral code, then a deadline bundle for the final 72 hours.

Days 29–30: close. Reconcile every Stripe charge to a delivered pack, confirm TrustMRR reflects all revenue, issue pending refunds, export the ledger, write the post-mortem.

7. Revenue and profit scenarios (projections only)

These are hypotheses, not verified revenue. Conservative: 4 packs at a $49 blended price, $196 gross, $0 refunds, $0 chargebacks, $10 payment fees, $0 ad spend, $30 operating cost — hackathon profit $186, business profit $156. Base: 12 packs at $65 blended (mix of Single and Store), $780 gross, $38 fees, $0 ad spend, $90 operating — hackathon profit $742, business profit $652. Upside: 30 packs at $78 blended including one Agency Pack, $2,340 gross, $98 refunds, $117 fees, $150 ad spend on one tested experiment, $240 operating — hackathon profit $1,975, business profit $1,735.

Hackathon profit excludes hosting, tooling and API delivery. Business profit includes them. Both come from the same inputs and both are projections.

8. Main risks and validation experiments

Cutout quality. Reflective, transparent and fuzzy products will fail. Test 20 deliberately awkward images in week 3; if the manual-review rate exceeds 30%, narrow the marketing claim to opaque product categories.

Rules drift. A "compliant" report that is wrong is worse than no report. Keep a versioned ruleset with a last-verified date in the PDF footer, re-checked every seven days. Kill criterion: two delivered packs rejected on a rule the report marked pass.

Channel bans. Reddit and Facebook groups can restrict outreach. Test three communities in week 2 and track which converts; if all three close, move to seller Discord servers and direct email before spending anything on ads.

Willingness to pay. Sellers may prefer a $5 Fiverr gig. Offer the free check to 20 sellers and count clicks on the $49 link. If fewer than 2 of 20 click, the price or the framing is wrong — not the channel.

9. First 24-hour action plan

Hours 1–2: scaffold the Next.js repo, deploy to Vercel, create the Supabase project and tables. Hours 3–5: write the ruleset JSON for all four channels and create the three Stripe one-time prices. Hours 6–8: integrate background removal and get a verified cutout back from a real test image. Hours 9–12: implement bounding-box detection and the white-canvas compositor, and export one correct Amazon main image. The day ends with a deployed skeleton, a ruleset, and one correctly composed image — the two things the remaining 29 days depend on.

Disclaimer: all revenue and profit figures above are projections built from stated assumptions, not verified revenue, customers or traction.

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 →