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

Promo Diff

A weekly change-detection report that shows a DTC brand exactly which promotions, discount codes and sitewide sales its named competitors published or removed in the last 7 days — with screenshot evidence.

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.18/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct cold email/DM to founders of independent skincare and supplement brands on Shopify with visibly active sale landing pages, artifact first and price second.
Who pays

Founder, head of growth or ecommerce manager at a Shopify DTC brand doing roughly $1M-$20M annual revenue, 3-50 employees, physical consumer goods, US/UK/EU, currently building a Black Friday and holiday promo calendar.

Biggest execution risk

Monetization potential 4.6/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 13; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.3/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

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

0/13
Entry price
$99
Solo build
5 days
30d base revenue
$2,590
30d hackathon profit
$2,306
Section 1 of 8

Product opportunity and positioning

Target customer

Founder, head of growth or ecommerce manager at a Shopify DTC brand doing roughly $1M-$20M annual revenue, 3-50 employees, physical consumer goods, US/UK/EU, currently building a Black Friday and holiday promo calendar.

Why now

Holiday and Black Friday promo calendars are being finalised in exactly the weeks of the contest, so the buying trigger is live and the sales cycle is one DM plus one reply.

Problem

Competitor discount depth, code names, bundle thresholds and free-shipping cutoffs live on competitor storefronts and change constantly; someone re-checks 6-8 sites by hand every week and still finds out about a 30%-off sale after it has run.

Solution

Customer submits up to 8 competitor URLs once. A daily headless-browser capture of announcement bars, sale pages and /discount pages is normalised into structured promo records, diffed against the previous snapshot, and delivered as a one-page PDF per competitor with before/after screenshots plus a NEW/CHANGED/REMOVED list and a live history dashboard.

Differentiation · Not a consumer coupon site, not affiliate, not cross-retailer price comparison, not cart auditing. It sells change detection with dated evidence to the merchant side of the same public data.

Product opportunity and positioning

Promo Diff sells a weekly, dated PDF diff of competitor promotions to a DTC brand marketer. The buyer is a founder, head of growth or ecommerce manager at a Shopify brand doing roughly $1M-$20M in annual revenue, 3-50 employees, selling physical consumer goods in the US, UK or EU, who is currently assembling a Black Friday and holiday promo calendar.

Today that person does the work by hand: open six to eight competitor storefronts, screenshot the announcement bar, check /discount and sale landing pages, retype code names into a spreadsheet, repeat next week. The failure mode is not effort, it is latency. Brands learn that a competitor ran 30% off after the sale ended, usually from a customer screenshot, and junior staff burn hours copying promo text that is stale by the time it is filed.

The output is fixed and provable: one page per competitor group, before/after screenshots, and a plain list of what is NEW, CHANGED or REMOVED. That artifact is what makes the sales cycle short — it can be generated for a prospect's own named competitors before any payment is requested, so the buyer sees their own evidence rather than a demo.

The same public data powers distribution. The founder runs the product on well-known brands, publishes the resulting teardown, and every published change is simultaneously marketing and proof of the mechanism.

Two honest constraints shape this plan. JEV scored the concept 61.8/100 (band C). Its strongest sub-scores are speed to first revenue at 8.27 and reachable customers at 7.46; its weakest are monetization potential at 4.57 and operational simplicity at 4.61. Second, urgency is seasonal: the promo-planning window sits inside the contest and demand softens in January. Both point the same way — one-time pricing, front-loaded selling, and no subscription the buyer has to remember to cancel.

Positioning deliberately excludes the crowded categories. This is not a consumer deal site, not an affiliate commission business, not cross-retailer price comparison, not cart auditing, not rebate-document parsing and not vendor price-match generation. It is change detection on public promo surfaces, sold to the merchant rather than the shopper. The narrow wedge is the point: eight competitors, one weekly artifact, screenshot evidence on every line.

Section 2 of 8

Smallest sellable MVP

Customer names up to 8 competitor URLs once; the product captures their promo surfaces daily and delivers a one-page PDF per competitor group with before/after screenshots and a NEW/CHANGED/REMOVED list every week, plus a dashboard with full history.

Must-have features

  • Competitor intake: admin stores up to 8 URLs per subscriber with a capture schedule
  • Playwright capture of announcement bar, collection pages, /discount and sale landing pages
  • Single structured LLM extraction call per snapshot into a fixed promo-record schema
  • Diff engine labelling each promo NEW, CHANGED or REMOVED against the previous snapshot
  • Noise suppression for cookie banners, rotating hero copy and currency switchers
  • PDF renderer with side-by-side before/after screenshots and the change list
  • Stripe Checkout for $99 / $199 / $499 plus a magic-link account page with report history
  • Vercel Cron daily capture per subscriber and weekly Resend email with the PDF attached
  • Admin view to add, pause or correct a subscriber's competitor list

Explicitly out of scope

  • No SKU-level price tracking or cross-retailer price comparison
  • No automated coupon-code testing or checkout verification
  • No consumer-facing deal site or browser extension
  • No real-time or intraday alerting — daily capture, weekly report only
  • No Shopify App Store listing
  • No team seats, roles or permissions
  • No rebate-document parsing or procurement workflows
  • No self-serve competitor editing at launch

Demo flow (what the buyer sees)

  1. Prospect replies to a cold email or buys a Season Pass via Stripe Checkout
  2. Founder enters the brand and up to 8 competitor URLs in the admin view
  3. Daily cron captures each competitor's promo surfaces and stores screenshots and HTML
  4. LLM extraction converts each snapshot into validated promo records
  5. Diff engine compares to the previous snapshot and labels NEW / CHANGED / REMOVED
  6. PDF renderer assembles the one-page-per-competitor report with before/after screenshots
  7. Resend delivers the weekly email with the PDF; the account page shows full history
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres and StoragePlaywright via Browserless or Cloudflare Browser RenderingAnthropic or OpenAI structured extraction with a fixed JSON schemaStripe CheckoutResendVercel Cron

Architecture

Cron enumerates active competitors and dispatches a capture job per URL; the job screenshots each promo surface and writes raw HTML plus PNGs to Supabase Storage, recording HTTP status and a page hash. A normaliser sends page text to one LLM call constrained to a schema of surface, verbatim text, discount type and depth, code and stated end date, and only schema-valid records are persisted. The diff engine matches today's records to the previous snapshot by surface and normalised text hash, emits NEW/CHANGED/REMOVED, and drops entries on a noise list. The PDF renderer builds the weekly report from the diff plus stored screenshots, Resend delivers it, and the dashboard reads the same Postgres tables.

Build steps

  1. Create Supabase schema for subscribers, competitors, snapshots, promos and diffs
  2. Build the capture job and prove it on three storefronts
  3. Define the promo-record schema and wire the LLM extraction call with validation
  4. Backfill three stores and hand-check 30 extracted records
  5. Build the diff engine with surface matching and noise suppression
  6. Build the PDF renderer with side-by-side screenshots
  7. Add Stripe Checkout and the magic-link account page
  8. Add Vercel Cron scheduling and Resend weekly delivery
  9. Build the admin view for competitor lists and forced re-runs
  10. Add per-domain retries, a second rendering provider and bot-block alerting
  11. Generate eight real competitor-set reports and publish a sample on the landing page

AI components

  • Single structured extraction call per snapshot that converts page text into promo records (surface, verbatim text, discount type and depth, code, stated end date)
  • Prompt-level classification aid that proposes noise entries (cookie banners, rotating hero copy) for the suppression list, reviewed by the founder
Hardest technical risk: Bot protection returning a challenge page that the normaliser reads as a removed promo, producing a confident but false change line.
Section 3 of 8

Pricing and monetization

Single Teardown

Entry offer
$99 one-time

For Brands testing the product before the season peak

  • 5 named competitors
  • 14-day lookback diff
  • One PDF teardown with before/after screenshots

Season Pass

$199 one-time

For DTC brands finalising Black Friday and holiday promo calendars

  • 8 named competitors
  • Daily capture and weekly PDF diffs through mid-January
  • Live dashboard with full promo history
  • Screenshot evidence for every reported change

Operator 5-Pack

$499 one-time

For Ecommerce agencies and fractional CMOs managing several brands

  • 5 brand workspaces
  • 8 competitors each
  • Weekly PDFs per brand
  • Shared dashboard access

Model: Three one-time Stripe Checkout tiers sold without a call or subscription, front-loaded into the holiday promo-planning window.

First revenue offer: A free 3-competitor, 14-day teardown PDF generated by the product for the prospect, with the $199 Season Pass checkout link in the same email and no call required.

Expected ACV: $199

Upsell path: $99 Single Teardown buyers are offered the $199 Season Pass with the $99 credited before their next promo cycle; single-brand buyers move to the $499 Operator 5-Pack when they mention a second brand or an agency relationship; Season Pass holders are offered a $99 January renewal to keep history running through the Q1 lull.

Target customers
35
Revenue model
$6,965
Costs
$290
Profit model
$6,675
Section 4 of 8

First-customer acquisition

Primary channel

Direct cold email/DM to founders of independent skincare and supplement brands on Shopify with visibly active sale landing pages, artifact first and price second.

Where to find them

  • Public Shopify storefronts in skincare and supplements with a live sale landing page
  • Founder or head-of-growth names from brand about pages and public LinkedIn profiles
  • r/ecommerce threads where brands discuss competitor discounting
  • Two ecommerce-focused Slack communities
  • LinkedIn ecommerce and DTC founder groups
  • Shopify agency and fractional CMO directories for the 5-Pack

Exact outreach motions

  • Run the product on 20 well-known brands and publish '20 brands, one week of promo changes' with no paywall
  • Send each of 150 founders a 3-competitor, 14-day teardown PDF generated by the product
  • Subject line names a real change found on a competitor's site this week
  • Same email carries the $199 Season Pass checkout link and states no call is required
  • 72-hour follow-up with the single most relevant change and one inline screenshot
  • Convert inbound 'do this for us' community requests into public samples so every prospect sees the artifact
  • Send 30 agency emails offering a free 3-brand sample workspace to pitch the $499 5-Pack

Message template

Subject: your competitor added a 30% sitewide code on Tuesday

Hi {first_name} — I run Promo Diff. I diffed {competitor_1}, {competitor_2} and {competitor_3} over the last 14 days. {competitor_1} added a sitewide 30% code on Tuesday and cut free shipping from $75 to $50. Attached is the PDF with before/after screenshots.

Want the same for your 8 competitors, updated weekly through mid-January? $199 one-time, no call: {checkout_link}

— {founder_name}
Week-one goal: 150-row prospect list built with 3 named competitors per row, 20-brand public teardown published, and 70 personalised teardown emails sent with at least 3 replies.
Section 5 of 8

30-day execution roadmap

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

Schema and capture

  • Scaffold Next.js on Vercel and create the Supabase project.
  • Create tables for subscribers, competitors, snapshots, promos and diffs.
  • Run a Playwright capture against three skincare storefronts via Browserless.

Deliverable: Three store snapshots stored with screenshot URLs and HTTP status.

Day 2Extraction

Promo records

  • Define the promo schema: surface, verbatim text, discount type, depth, code, end date.
  • Wire one structured LLM extraction call per snapshot with schema validation.
  • Backfill three stores and hand-check 30 records.

Deliverable: Validated promo JSON for three stores with an accuracy note.

Day 3Diff engine

Change detection

  • Match promos across snapshots by surface plus normalised text hash.
  • Label NEW/CHANGED/REMOVED and add a noise list for cookie banners and rotating copy.
  • Capture a second day and diff it against day one.

Deliverable: Working diff with a logged false-positive list.

Day 4Report and payments

PDF plus checkout

  • Render a one-page PDF per competitor with before/after screenshots.
  • Add Stripe Checkout for $99, $199 and $499 plus a magic-link account page.
  • Run a test-mode purchase end to end.

Deliverable: Test order produces a PDF visible in the account page.

Day 5Delivery

Automation

  • Add Vercel Cron daily capture and weekly Resend email with the PDF attached.
  • Build the admin view to add, pause or correct competitor lists and force re-runs.

Deliverable: Weekly report arrives in the founder inbox without manual steps.

Day 6ShipMVP shipped

Hardening and launch page

  • Add per-domain retries, a second rendering provider and a bot-block alert.
  • Generate full reports for eight real competitor sets.
  • Publish the landing page with a sample PDF and live checkout.

Deliverable: Product live at a public URL with a downloadable sample.

Day 7List building

150 skincare and supplement brands

  • Collect 150 Shopify brands with founder name and public email or LinkedIn.
  • Tag three named competitors per prospect and record the source page.

Deliverable: 150-row prospect sheet with competitor mapping.

Week 2 · Launch & first sale · 7 days
Day 8Public teardown

Proof asset

  • Run the product across 20 well-known brands for the last 7 days.
  • Assemble the '20 brands, one week of promo changes' PDF.

Deliverable: Shareable public teardown PDF.

Day 9Distribution

First sends

  • Post the teardown to r/ecommerce, two ecommerce Slacks and LinkedIn.
  • Send 30 personalised emails with a 3-competitor teardown attached.

Deliverable: 30 sends and the first inbound replies.

Day 10Outreach volume

Volume and response

  • Send 40 more personalised emails from the prospect sheet.
  • Answer every reply within two hours with the $199 checkout link.

Deliverable: 70 cumulative sends with reply rate tracked.

Day 11Message iteration

Subject lines

  • Rewrite subject lines around the most surprising change found per prospect.
  • Send the 72-hour follow-up to the day-9 batch.

Deliverable: Two subject-line variants with open and reply data.

Day 12Second batch

Scale outreach

  • Send 40 more emails using the winning subject line.
  • Publish a second sample teardown for a different sub-vertical.

Deliverable: 110 cumulative sends.

Day 13First revenueFirst sale target

Checkout push

  • Send the Season Pass checkout link to every warm replier.
  • Remove friction: one-click Stripe link, no call, no invoice.

Deliverable: Target: first paid Season Pass collected.

Day 14Deliver and learn

Report quality

  • Hand-verify every change line in each new customer's first report.
  • Ask each buyer which three competitors matter next.

Deliverable: First customer reports shipped with zero known false positives.

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

5-Pack groundwork

  • Identify 30 ecommerce agencies and fractional CMOs from LinkedIn and directories.
  • Draft the $499 Operator 5-Pack one-pager.

Deliverable: Agency prospect list and a live 5-Pack page.

Day 16Agency outreach

Multi-brand buyers

  • Send 30 agency emails offering a free 3-brand sample workspace.
  • Pitch the 5-Pack as client-retention reporting.

Deliverable: 30 agency sends logged.

Day 17Upsell

Existing buyers

  • Email existing buyers the 5-Pack upgrade at the price difference.
  • Add a referral line to every report footer.

Deliverable: Upsell emails sent and referral line live.

Day 18Content flywheel

Weekly public post

  • Publish 'what changed in DTC promos this week' from product data.
  • Cross-post to LinkedIn and one ecommerce newsletter.

Deliverable: Weekly public post shipped.

Day 19Second vertical

Home and fitness

  • Build a 75-row list of home and fitness Shopify brands.
  • Map three named competitors per prospect.

Deliverable: 75-row second-vertical sheet.

Day 20Outreach batch three

New vertical

  • Send 50 emails into the second vertical.
  • Follow up on the day-16 agency batch.

Deliverable: 180 cumulative sends.

Day 21Reliability review

Capture success

  • Audit capture success rate per domain and add fallbacks for failures.
  • Tighten noise filters using customer-reported false positives.

Deliverable: Documented capture success rate per domain.

Week 4 · Scale what works · 7 days
Day 22BFCM peak push

Deadline urgency

  • Send a Black Friday-specific teardown to all 150 unconverted prospects.
  • Subject line names a live code found this week.

Deliverable: 150 BFCM sends dispatched.

Day 23Follow-up

Objection handling

  • Send the 72-hour follow-up with one competitor screenshot inline.
  • Answer price objections with the $99 Single Teardown.

Deliverable: $99 downsell offer live and sent.

Day 24Delivery quality

Week-three reports

  • Ship weekly reports and verify every NEW/REMOVED line against screenshots.
  • Log any miss as a bug with the source URL.

Deliverable: Week-three reports delivered on time.

Day 25Community

Inbound

  • Post an anonymised promo-calendar benchmark excerpt in two communities.
  • Offer a free teardown to every commenter.

Deliverable: Community thread plus inbound leads list.

Day 26Close week

Warm follow-up

  • Email every prospect who opened three or more times without replying.
  • Offer a 48-hour free teardown to convert.

Deliverable: Second conversion wave contacted.

Day 27Retention

Renewal

  • Email Season Pass holders the January renewal at $99.
  • Ask each for one testimonial line.

Deliverable: Renewal offer sent and testimonials requested.

Day 28Numbers

Verified ledger

  • Reconcile Stripe payouts, refunds and fees against TrustMRR.
  • Recalculate unit economics per tier.

Deliverable: Verified profit ledger for the contest window.

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

Last conversions

  • Send the final teardown batch to warm non-buyers.
  • Publish the last public teardown of the contest.

Deliverable: All warm leads contacted and log closed.

Day 30Wrap

Obligations and close

  • Deliver every outstanding report before 13:00 UTC.
  • Freeze scope and publish a short results page with the verified ledger.

Deliverable: All customer obligations shipped and ledger closed.

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 and upside blend $99 Single Teardowns and $199 Season Passes; the upside also includes a small number of $499 Operator 5-Packs, which lifts blended arpu toward $199.
  • Conservative replies come from 70 sends at a 3-5% reply rate with roughly a third of repliers buying.
  • Payment processing assumed at Stripe 2.9% plus $0.30 per transaction, roughly 3.1-3.4% effective on this order mix.
  • Ad spend is $0 in all scenarios because the acquisition channel is organic cold outreach and community posts.
  • Operating cost is managed browser rendering, Supabase, LLM extraction for up to 8 competitors per subscriber per day, Resend and one domain.
  • Refund allowance assumes one refund per roughly 14 customers, mostly from prospects whose competitors showed low activity.
  • No subscription is sold, so no automatic renewals or forgotten-cancel refunds are modelled inside the 30 days.
  • All figures are projections from these assumptions, not verified revenue or existing customers.

Conservative

4 customers
$596
collected revenue · avg payment $149
Refunds
$99
Chargebacks
$0
Payment fees
$20
Paid marketing
$0
Hackathon profit
$477
Operating costs
$45
Business profit
$432

Base case

14 customers
$2,590
collected revenue · avg payment $185
Refunds
$199
Chargebacks
$0
Payment fees
$85
Paid marketing
$0
Hackathon profit
$2,306
Operating costs
$90
Business profit
$2,216

Optimistic

32 customers
$6,368
collected revenue · avg payment $199
Refunds
$398
Chargebacks
$199
Payment fees
$205
Paid marketing
$0
Hackathon profit
$5,566
Operating costs
$180
Business profit
$5,386

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,242

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

Scenario models from stated assumptions, not verified revenue.

Section 7 of 8

Main risks and validation experiments

Risk 1Bot protection or CAPTCHA on some storefronts returns a challenge page that the extractor reads as a removed promo.

Mitigation

Record HTTP status and page hash on every capture, retry through a second rendering provider, and alert the admin on any blocked result so no REMOVED line is emitted from a failed capture.

Validation experiment

On day 3, run the capture job against 40 target domains and record the success rate and block rate per domain.

Kill criteria

If fewer than 70% of target domains capture reliably, narrow the vertical to working storefronts rather than rebuilding the crawler.

Risk 2False-positive change detection from cookie banners, rotating hero copy and currency switchers erodes trust after the first report.

Mitigation

Maintain a noise suppression list and hand-verify every change line in every customer's first report before delivery.

Validation experiment

On day 3, hand-label 100 diff lines from three stores and measure the false-positive rate.

Kill criteria

If false positives remain above 15% after tuning, ship the PDF as an unfiltered evidence montage with screenshots and no NEW/CHANGED labels.

Risk 3Holiday urgency is what sells this; demand likely collapses in January.

Mitigation

Sell one-time only, front-load every sales push into days 9-28, and keep the $499 Operator 5-Pack for agencies with year-round reporting needs.

Validation experiment

Ask every buyer during onboarding whether they would renew for a second season, and tally the answers by day 27.

Kill criteria

If fewer than 25% of buyers say they would renew, do not build a subscription in month two.

Risk 4One founder's cold-outreach volume caps the number of conversations possible in 30 days.

Mitigation

Generate prospect-specific emails from product output so personalisation costs one minute per send, and cap volume at 60 sends per day to protect quality.

Validation experiment

Track reply rate across the first 70 sends on days 9-11.

Kill criteria

If reply rate stays below 1% after 150 sends, shift effort into community-posted public teardowns and inbound.

Risk 5Codes that live only in competitors' email or SMS are invisible, creating a perceived completeness gap.

Mitigation

State the captured surface list on the landing page and in every report footer, and never imply inbox coverage.

Validation experiment

Include the scope statement in the first 30 outreach emails and count objections about missing coverage.

Kill criteria

If more than a third of repliers raise coverage as a blocker, re-scope the offer to announcement-bar and sale-page monitoring explicitly.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Vercel, Supabase and Browserless accounts.
  • Scaffold the Next.js repo and deploy a skeleton.
  • Create the five Postgres tables.

Output: Live skeleton URL and an empty but queryable schema.

Hours 3-5

  • Build the Playwright capture job for announcement bar, collection page and /discount page.
  • Run it against three skincare storefronts.

Output: Screenshots and raw HTML stored with HTTP status per surface.

Hours 6-8

  • Write the promo-record schema and the structured extraction prompt.
  • Run extraction on the three stores and hand-check 30 records.

Output: Promo JSON for three stores plus a written accuracy note.

Hours 9-11

  • Build the diff engine with surface matching and a noise list.
  • Build the PDF renderer with before/after screenshots.

Output: One real teardown PDF built from two real capture days.

Hours 12-14

  • Publish a landing page with the sample PDF.
  • Wire a live $199 Stripe Checkout link and test one purchase.

Output: A public URL that can be sent to a prospect.

Hours 15-18

  • Build a 30-row skincare founder prospect list with three competitors each.
  • Send the first 10 personalised teardown emails.

Output: 10 sends dispatched and the reply clock started.

Complete report

Full 30-day launch report

Read the full generated report

Promo Diff — 30-Day Public Launch Report

Concept version 1. Scored by JEV at 61.8/100 (band C). Every revenue figure below is a projection from stated assumptions, not verified revenue. No customers, partnerships or traction exist at the start.

1. Product opportunity and positioning

Promo Diff sells a weekly, dated PDF diff of competitor promotions to a DTC brand marketer: a founder, head of growth or ecommerce manager at a Shopify brand doing $1M-$20M, 3-50 employees, physical consumer goods, US/UK/EU, currently assembling a Black Friday and holiday promo calendar.

Today that person opens six to eight competitor storefronts by hand, screenshots announcement bars, checks /discount pages, retypes code names into a spreadsheet and repeats next week. The failure is latency, not effort: brands learn a competitor ran 30% off after it ended, usually from a customer screenshot.

The output is fixed and provable — one page per competitor group with before/after screenshots and a list of what is NEW, CHANGED or REMOVED. That artifact shortens the sale, because it can be generated for a prospect's own competitors before any payment is requested.

Two constraints shape the plan. JEV scored this concept 61.8/100 (band C), strongest on speed to first revenue at 8.27 and reachable customers at 7.46, weakest on monetization potential at 4.57 and operational simplicity at 4.61. And the urgency is seasonal: the promo-planning window sits inside the contest. Both point the same way — one-time pricing, front-loaded sales, no subscription the buyer must cancel.

Positioning excludes the crowded categories: not a consumer coupon site, not affiliate, not price comparison, not cart auditing. It is change detection sold to the merchant.

2. Smallest sellable MVP

Five build days. The sellable unit: a customer names up to eight competitor URLs, the product captures their promo surfaces daily, and delivers a one-page PDF per competitor with before/after screenshots and a NEW/CHANGED/REMOVED list, weekly, plus a dashboard with history.

Must exist: competitor intake (admin-entered at launch), Playwright capture of announcement bars, collection pages and /discount and sale pages, one structured LLM extraction call per snapshot, the diff engine with noise suppression, the PDF renderer, Stripe Checkout, a magic-link account page, daily cron, weekly email and an admin view to add or pause competitors.

Not built: SKU price tracking, checkout code testing, consumer deal pages, a browser extension, real-time alerts, an App Store listing, team seats, rebate parsing. Each would cost build days without raising first-sale probability.

3. Technical implementation plan

Next.js on Vercel; Supabase Postgres for snapshots and promo records plus Storage for screenshots; Playwright via Browserless or Cloudflare Browser Rendering; one LLM structured-extraction call per snapshot against a fixed JSON schema; Stripe Checkout; Resend; Vercel Cron.

Flow: cron enumerates active competitors, capture writes raw HTML and PNGs to Storage, the normaliser sends page text to the LLM against a schema of surface, verbatim text, discount type and depth, code and stated end date, validated records land in Postgres, the diff engine matches by surface and normalised text hash and labels NEW/CHANGED/REMOVED while dropping known noise (cookie banners, rotating hero copy, currency switchers), the PDF renderer builds the weekly report, and email delivers it with the PDF attached.

Build order: schema, capture, extraction, diff, PDF, payments, cron, admin. Hardest risk: bot protection returning a challenge page that reads as a removed promo. Every capture records HTTP status and page hash; a blocked page must fail loudly and retry, never emit a REMOVED line.

4. Pricing and monetization

Three one-time tiers sold by Stripe link, no call.

Single Teardown $99 — five competitors, 14-day lookback, one PDF; the objection handler. Season Pass $199 — eight competitors, daily capture, weekly PDFs through mid-January, dashboard, screenshot evidence; the default offer and arpu anchor. Operator 5-Pack $499 — five brand workspaces, eight competitors each, weekly PDFs, shared dashboard.

The 5-Pack answers JEV's monetization weakness without changing the pipeline: it lifts arpu and sells to agencies and fractional CMOs who need client reporting year-round, not just at BFCM.

Upsell path: $99 buyer to $199 Season Pass with the $99 credited before their next promo cycle; single-brand buyer to $499 when they mention a second brand or an agency; Season Pass holders offered a $99 January renewal to carry history across the Q1 lull. No subscription at launch — one-time converts better under a deadline and produces no forgotten-cancel refunds.

5. First-customer acquisition

One channel: cold email/DM to founders of independent skincare and supplement brands on Shopify with visibly active sale landing pages. No ads, no SEO, no marketplace.

Build 150 rows by browsing public storefronts and capturing founder name plus public email or LinkedIn, tagging three named competitors each. Then run the product on 20 well-known brands and publish '20 brands, one week of promo changes' in r/ecommerce, two ecommerce Slacks and LinkedIn.

Outreach is artifact first, price second: a three-competitor, 14-day teardown PDF generated by the product for that prospect, a subject line naming a real change, the Season Pass checkout link in the same email, one follow-up at 72 hours. Targets: 30 sends on day 9, 110 cumulative by day 12, first paid Season Pass on day 13, 180 total including 30 agency emails by day 21.

6. Detailed 30-day execution roadmap

Days 1-5 build: schema and capture, LLM extraction, diff engine with noise filters, PDF plus Stripe and magic link, then cron, email and admin view. Day 6 hardens retries and bot-block alerts and ships the landing page with a sample PDF. Days 7-8 build the 150-row prospect list and the 20-brand public teardown.

Days 9-14 are outreach: 30 emails on day 9, 40 on day 10, subject-line iteration on day 11, 40 on day 12, a checkout push on day 13 with a first-revenue target, and day 14 hand-verifying every change line in new customers' first reports.

Days 15-21 open the agency wedge — 30 agency emails, the $499 5-Pack page, upsell to existing buyers — start a weekly public 'what changed in DTC promos' post, and repeat list building in a second vertical (home and fitness, 75 brands). Day 21 audits capture success rate per domain.

Days 22-28 are the BFCM peak push: a Black Friday teardown to all 150 unconverted prospects, a $99 downsell for price objections, verified week-three reports, community posting, direct contact with three-time openers, a January renewal offer, and a Stripe-to-ledger reconciliation.

Days 29-30 ship every outstanding report before the 13:00 UTC close and publish a results page. Day-by-day tasks are in the structured roadmap above.

7. Revenue and profit scenarios

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

Conservative — 4 customers at $149 blended arpu = $596 gross; refunds $99; fees $20 (Stripe 2.9% plus $0.30, about 3.4%); ad spend $0; operating $45. Hackathon profit $477; business profit $432.

Base — 14 customers at $185 blended arpu = $2,590 gross; refunds $199; fees $85; ad spend $0; operating $90. Hackathon profit $2,306; business profit $2,216.

Upside — 32 customers at $199 arpu with a few $499 5-Packs = $6,368 gross; refunds $398; chargebacks $199; fees $205; ad spend $0; operating $180. Hackathon profit $5,566; business profit $5,386.

Operating cost is managed browser rendering, Supabase, LLM extraction for eight competitors per subscriber per day, email and one domain — under $75/month at 35 subscribers. With zero paid marketing, revenue minus fees is ranked profit. The variable that decides which scenario happens is personalised-teardown reply rate; below 2%, the base case does not hold.

8. Main risks and validation experiments

Bot protection. Challenge pages will appear. Mitigation: record HTTP status and page hash, retry through a second renderer, alert the admin. Validation: capture 40 target domains on day 3. If success is under 70%, narrow the vertical to working domains instead of rebuilding the crawler.

False positives. Cookie banners and rotating hero copy create fake changes. Mitigation: a noise list plus hand-verification of every line in every first report. Validation: label 100 diff lines on day 3. Above 15% false positives after tuning, ship the PDF as an unfiltered evidence montage rather than a wrong change list.

Seasonality. January demand collapses. Mitigation: one-time pricing only, all sales front-loaded, the 5-Pack for agencies with year-round need. Validation: ask every buyer whether they would renew. Under 25% yes means no subscription in month two.

Outreach ceiling. One person caps volume. Mitigation: prospect emails generated from product output, 60 sends per day maximum. Validation: reply rate across the first 70 sends. Below 1%, shift effort into community-posted public teardowns.

Coverage objection. Codes living only in competitors' email or SMS are invisible. Mitigation: state the captured surface list on the landing page and in every report footer.

9. First 24-hour action plan

Hours 1-2: Vercel, Supabase and Browserless accounts, repo scaffold, skeleton deploy. Hours 3-5: capture job runs against three skincare storefronts; screenshots and HTML in storage. Hours 6-8: extraction schema and prompt; promo JSON for those stores; 30 records hand-checked. Hours 9-11: diff engine and PDF renderer; one real teardown PDF. Hours 12-14: landing page with that PDF and a live $199 Stripe link. Hours 15-18: 30-row prospect list and the first 10 personalised emails.

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 →