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

ExpiryTag

ExpiryTag helps independent grocery stores track product expiry dates and print discount labels for near-expiry items, reducing waste and compliance risk.

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.10/10
MVP build (solo)
5 days
Launch price
$199
Sales to $1,000 revenue
6 customers
First paying customer
In-person visits to independent grocery stores within 5 km of the founder, followed by WhatsApp follow-up.
Who pays

Owner of an independent grocery store (1-3 locations) in urban India who checks expiry dates by hand and handwrites discount stickers.

Biggest execution risk

Market demand 4.3/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

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

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

0/17
Entry price
$199
Solo build
5 days
30d base revenue
$1,990
30d hackathon profit
$1,900
Section 1 of 8

Product opportunity and positioning

Target customer

Owner of an independent grocery store (1-3 locations) in urban India who checks expiry dates by hand and handwrites discount stickers.

Why now

The workflow already exists on paper in every store; replacing a notebook and a marker with a $199 one-time tool needs no hardware, no integrator and no training day.

Problem

Near-expiry dairy, bakery and packaged stock is either sold at full price (food-safety risk) or thrown away; manual date checking is slow and error-prone.

Solution

Staff scan a barcode, enter the expiry date once, see a 3/7/14-day expiry dashboard, and print an Avery-compatible PDF sheet of discount labels with the store name, new price and expiry date.

Differentiation · A spreadsheet cannot produce a shelf-ready sticker; paid retail suites cost more than the waste they save and require onboarding a solo founder cannot deliver.

ExpiryTag — 30-Day Launch Report

Concept: ExpiryTag (v1) · JEV score: 61.0/100 (band C) · Window: 16 Nov 2026 13:00 UTC – 16 Dec 2026 13:00 UTC · Founder: one person.

1. Product opportunity and positioning

ExpiryTag sells one narrow workflow to one narrow buyer: an independent grocery store owner in urban India who walks the aisles with a pen, squints at date codes, and handwrites "10% off" on stickers. That owner has three bad options today — sell near-expiry stock at full price and carry a food-safety risk, throw it away and eat the loss, or spend 45 minutes a day hunting dates by hand. ExpiryTag replaces all three with scan, alert, print.

The JEV score is honest about the shape of this bet. Speed to first revenue (7.98 normalized) and solo build feasibility (7.59) are the strongest criteria: a five-day build and a buyer who can be met in person. Market demand (4.29) and monetization potential (4.69) are the weak spots, and the plan attacks both directly instead of pretending they are not there. The buyer is narrowed to the owner whose near-expiry dairy, bakery and packaged staples are a visible weekly loss, and the price is anchored to the markdown revenue recovered, not to "software".

Positioning: this is not inventory management and not a POS. It is the markdown machine. Staff scan a barcode, type the expiry date once, and the dashboard buckets stock into 3 / 7 / 14-day windows. Anything expiring prints onto an Avery-compatible sheet carrying the store's own name, the new discounted price and the expiry date. The output is physical, shelf-ready, and takes two minutes to demonstrate — which is what matters when you are selling door to door with no brand.

The realistic alternative is a notebook or a free spreadsheet, and neither can produce a sticker. Against paid retail suites, ExpiryTag is $199 once, needs no hardware, no integrator and no training day. That gap is the whole business.

2. Smallest sellable MVP

The sellable unit is: log in, scan a barcode, enter expiry and MRP, see what expires this week, print a sheet of discount labels with the store's name on it. Nothing more is required before an owner hands over $199.

Must ship: phone-camera barcode scan (QuaggaJS) with manual fallback; product record with barcode, name, MRP, expiry date; dashboard with 3/7/14-day buckets sorted by days left; discount presets (10/20/30%) that compute the new price; a PDFKit label sheet on an Avery A4 grid; store profile with name, logo upload and currency formatting; Stripe one-time checkout with licence activation.

Explicitly not built: inventory counts, supplier ordering, POS integration, a customer-facing app, multi-store analytics, thermal printer drivers, automated barcode-to-name lookup (staff type the name once), translated UI, app-store binaries.

3. Technical implementation plan

Stack: Next.js and React on Vercel, Supabase for Postgres and auth, QuaggaJS for scanning, PDFKit server-side for labels, Stripe Checkout for the one-time $199 licence, Resend for the receipt and onboarding email.

Architecture: one Next.js app. Supabase holds stores, products and licence status with row-level security keyed on store_id. The browser scans with QuaggaJS and writes the product row through the Supabase client. The label endpoint is a serverless function: it takes product IDs, renders a PDF with PDFKit onto an A4 Avery-compatible grid, and streams it back. The biggest build risk is grid measurements and margins — labels drift if the print dialog scales above 100%. Stripe Checkout redirects to a webhook that flips licence_active.

Build steps: (1) repo, Supabase schema, auth; (2) scan-to-add product flow; (3) expiry dashboard buckets; (4) label PDF endpoint and print preview; (5) Stripe checkout and activation webhook; (6) deploy to a custom domain on Vercel; (7) smoke test on a real phone with a real milk carton. No LLM is used — barcode decoding is deterministic and the deliverable is a PDF.

4. Pricing and monetization

One tier: Store License, $199 one-time — unlimited label generation, barcode scanning, expiry alerts, lifetime access for that location. A 7-day free trial exists only so the owner can run one real markdown cycle before paying.

Why $199: it is roughly the value of one week of avoided dairy waste in a busy store, and small enough for the owner to approve on the spot without an accountant. The monetization weakness is answered by the upsell path, not a price rise: a second location is a second $199 licence, and every paying store is asked for one introduction to a neighbouring owner. Payment runs through Stripe Checkout (a UPI/Razorpay fallback if Stripe onboarding stalls), connected to TrustMRR from day one, with nothing charged before launch.

5. First-customer acquisition

Primary channel: in-person visits to independent grocery stores within 5 km, followed by WhatsApp follow-up. No ads, no SEO, no marketplace.

Where: kirana clusters around vegetable markets; residential colony main roads; stores already stocking dairy and bakery; stores with visible offer bins; and the local print shop, which is both a referral source and a delivery point for PDFs.

Outreach: walk in between 11:00 and 13:00 and ask for the owner; hand over a pre-printed label sheet already carrying their store name and three of their real products; run the two-minute demo on your phone with a product from their shelf; offer the 7-day trial and take payment on the spot from whoever says yes; WhatsApp the app link and a 60-second screen recording that evening; ask for one neighbouring store name before leaving.

Week-one goal: 20 stores visited, 5 trials started, 1 paid licence.

6. 30-day execution roadmap

Days 1–5 are build only. Days 6–7 produce ten store-specific sample sheets and start visits. Days 8–14 are field days: visit, follow up, close the first paid licence by day 10, refine the label template from real print feedback. Days 15–21 cover a second store cluster, a print-shop export for stores without printers, referral asks, and a target of 5+ licences. Days 22–28 widen to a second neighbourhood, revisit every unconverted trial, and pitch second-location licences. Days 29–30 convert stragglers, reconcile payments against TrustMRR, and write the post-mortem. The day-by-day task list is in the roadmap section above.

7. Revenue and profit scenarios

Projections only — derived from stated assumptions, not verified revenue, not existing customers.

Conservative: 3 licences × $199 = $597 gross, 4.5% Stripe fees $27, no refunds or ads, operating $25. Base: 10 × $199 = $1,990, fees $90, operating $45. Upside: 25 × $199 = $4,975, one refund $199, fees $224, $150 of sponsored retailer-group posts, operating $110. Hackathon profit excludes operating costs; business profit includes them. In the base case that is roughly $1,900 versus $1,855. The spread between conservative and upside is visit volume and conversion, not product scope, which is why days 6–28 are almost entirely field days.

8. Risks and validation experiments

(a) The owner does not care about expiry. Test: on ten visits ask "how much dairy did you throw away last week?" before showing the product. Kill if fewer than three give a number. (b) Labels print misaligned. Test: print the same PDF at three local print shops before day 5; fix margins, do not change the plan. (c) $199 is too high. Test: quote $199 to five stores and $99 to five. Reprice once only if $199 converts 0/5 while $99 converts 3/5. (d) Barcode scan fails on loose produce: manual entry is the mitigation and stays a non-goal.

9. First 24-hour action plan

Hours 1–2: Supabase project, schema, auth. Hours 3–5: Next.js scaffold deployed to Vercel with working login. Hours 6–8: QuaggaJS scan flow working on a physical phone. Hours 9–11: product entry form plus expiry dashboard query. Hours 12–14: PDFKit label endpoint with Avery measurements. Hours 15–18: Stripe checkout and licence webhook. Hours 19–21: end-to-end smoke test with three real products. Hours 22–24: draft the first printed sample label sheet.

Section 2 of 8

Smallest sellable MVP

A paid licence to scan a barcode, record an expiry date, see a 3/7/14-day expiry dashboard, and print an Avery-compatible discount label sheet carrying the store's own name.

Must-have features

  • Phone-camera barcode scanning via QuaggaJS with manual barcode/name fallback
  • Product record: barcode, name, MRP, expiry date
  • Expiry dashboard bucketed at 3, 7 and 14 days, sorted by days left
  • Discount presets (10/20/30%) that compute the new shelf price
  • PDFKit label sheet on an Avery-compatible A4 grid
  • Store profile with store name and logo on the label
  • Stripe one-time checkout with licence activation webhook

Explicitly out of scope

  • Inventory counts
  • Supplier ordering
  • POS integration
  • Customer-facing app
  • Multi-store analytics
  • Thermal printer drivers
  • Automated barcode-to-product-name lookup
  • Translated UI
  • iOS/Android app-store binaries

Demo flow (what the buyer sees)

  1. Founder opens the app on a phone and logs into the store's account
  2. Scans a milk carton barcode from the owner's own shelf
  3. Types expiry date and MRP once
  4. Dashboard shows the item in the 3-day bucket
  5. Selects 20% discount preset
  6. Prints or WhatsApp-exports the label PDF carrying the store name
  7. Owner sees a shelf-ready sticker in under two minutes
Build plan

Technical implementation plan

Stack

Next.jsReactVercelSupabase (Postgres + auth + row-level security)QuaggaJSPDFKitStripe CheckoutResend

Architecture

One Next.js app on Vercel. Supabase stores stores, products and licence status with row-level security keyed on store_id; the browser writes product rows directly after a QuaggaJS scan. A serverless label endpoint takes product IDs, renders an A4 Avery-compatible PDF with PDFKit and streams it back. Stripe Checkout redirects to a webhook that flips licence_active for the store.

Build steps

  1. Create repo, Supabase project, tables (stores, products, licences) and auth
  2. Build scan-to-add product flow with manual fallback
  3. Build expiry dashboard bucketed at 3/7/14 days
  4. Build PDFKit label endpoint and print preview page
  5. Add discount presets that recompute price from MRP
  6. Wire Stripe Checkout and licence activation webhook
  7. Deploy to custom domain on Vercel
  8. Smoke test on a real phone with three real products from a store
  9. Print the same PDF at three print shops and correct grid margins

AI components

  • None — barcode decoding is deterministic and the deliverable is a PDF; no LLM inference cost.
Hardest technical risk: Avery grid alignment: labels drift when the print dialog scales above 100%, so the PDF must be fixed at exact millimetre positions and tested on real printers before day 5.
Section 3 of 8

Pricing and monetization

Store License

Entry offer
$199 one-time

For Independent grocery store owner (1-3 locations)

  • Unlimited discount label generation
  • Barcode scanning
  • Expiry alerts at 3/7/14 days
  • Store name and logo on labels
  • Lifetime access for that location

Model: Single one-time Store License at $199 per store location, no subscription.

First revenue offer: 7-day free trial, then $199 once for lifetime access to that store location — pitched in person with a pre-printed sample label sheet carrying the store's own name and three of its real products.

Expected ACV: $199

Upsell path: Each additional store location is a second $199 licence; every paying owner is asked for one introduction to a neighbouring store owner, turning one closure into a referral chain rather than a new tier.

Target customers
25
Revenue model
$4,975
Costs
$60
Profit model
$4,915
Section 4 of 8

First-customer acquisition

Primary channel

In-person visits to independent grocery stores within 5 km of the founder, followed by WhatsApp follow-up.

Where to find them

  • Kirana clusters around local vegetable markets
  • Residential colony main roads with 5+ grocery stores
  • Stores with visible dairy and bakery cabinets
  • Stores with an existing 'offer' bin or handwritten discount shelf
  • The local print shop where stores already print signage
  • Neighbouring store names collected from each paying owner

Exact outreach motions

  • Walk in between 11:00 and 13:00 and ask for the owner or manager
  • Hand over a pre-printed label sheet already carrying their store name and three of their real products
  • Run a two-minute demo on your phone using a product pulled from their own shelf
  • Offer the 7-day trial and take payment on the spot from anyone who says yes
  • WhatsApp the app link plus a 60-second screen recording the same evening
  • Ask for one neighbouring store owner's name before leaving

Message template

Namaste — I built ExpiryTag for stores like yours. The sheet I left carries your own store name; it prints discount stickers for items expiring this week in under a minute. 7 days free, then $199 once, no monthly. Can I show you for 2 minutes on Thursday?
Week-one goal: 20 stores visited, 5 trials started, 1 paid $199 licence collected.
Section 5 of 8

30-day execution roadmap

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

Scaffold and data model

  • Create Next.js repo and deploy to Vercel
  • Create Supabase project with stores, products, licences tables
  • Add auth with one account per store

Deliverable: Deployed skeleton with working login on a custom domain

Day 2Scanning

Barcode capture

  • Integrate QuaggaJS on the phone camera
  • Add manual barcode and name fallback
  • Write scanned product rows to Supabase

Deliverable: Scan-to-add product flow working on the founder's phone

Day 3Dashboard

Expiry visibility

  • Build product list with expiry date and MRP entry
  • Add 3/7/14-day buckets sorted by days left
  • Add edit and delete on product rows

Deliverable: Expiry dashboard showing real expiring stock

Day 4Labels

PDF output

  • Build PDFKit endpoint on an Avery-compatible A4 grid
  • Add 10/20/30% discount presets that recompute price
  • Render store name and logo on every label

Deliverable: Printable sheet of 24 discount labels

Day 5MonetizationMVP shipped

Take money

  • Wire Stripe Checkout at $199 one-time
  • Add licence activation webhook and gated access
  • Smoke test end to end with three real products

Deliverable: Live paid product accepting $199

Day 6Sales prep

Physical proof

  • Print 10 store-specific sample sheets with real store names
  • Include milk, bread and biscuit label examples
  • Print the same PDF at two print shops to confirm alignment

Deliverable: 10 printed sample packs ready to hand out

Day 7Field day 1

First conversations

  • Visit 5 stores between 11:00 and 13:00
  • Ask how much dairy was thrown away last week
  • Log objections and trial signups

Deliverable: 5 conversations and at least 2 trial accounts

Week 2 · Launch & first sale · 7 days
Day 8Field day 2

Volume

  • Visit 6 more stores in a second cluster
  • Demo with a product pulled from each shelf
  • Record every objection verbatim

Deliverable: Objection log with 10+ entries

Day 9Follow-up

Trial activation

  • WhatsApp every trial store the app link and a 60-second recording
  • Call back the two warmest owners
  • Fix any login or scanning blocker found

Deliverable: 8 follow-ups sent, all trials able to log in

Day 10First saleFirst sale target

Close

  • Return to the warmest store with a printed label sheet
  • Take $199 payment on the spot and onboard staff in 10 minutes
  • Ask for one neighbouring store introduction

Deliverable: First $199 licence collected and activated

Day 11Product polish

Real print feedback

  • Adjust label template from the paying store's notes
  • Add store logo upload
  • Add a one-page print instructions sheet

Deliverable: Label template v2 shipped

Day 12Field day 3

Pipeline

  • Visit 6 stores with sample sheets
  • Quote $199 to five and $99 to one test store
  • Collect 2 more trials

Deliverable: 14 total stores visited, 4+ trials

Day 13Proof

Evidence from the paying store

  • Ask the paying store to count items marked down this week
  • Record a short quote on WhatsApp
  • Photograph a shelf with ExpiryTag labels

Deliverable: One quote and one shelf photo usable in every pitch

Day 14Review

Week 2 numbers

  • Count visits, trials, paid licences
  • Rework the pitch around the strongest objection
  • Decide whether day 15-21 visits go to cluster two or three

Deliverable: Written pitch v2 and visit list for week 3

Week 3 · Repeat & systematize · 7 days
Day 15Print shop mode

Stores without printers

  • Add single-page PDF export shareable via WhatsApp
  • Test the flow from a print shop
  • Document the one-line print instruction

Deliverable: Export path that works without a store printer

Day 16Field day 4

Cluster two

  • Visit 6 stores in a new market cluster
  • Lead with the shelf photo and quote
  • Offer the trial to every owner who stops

Deliverable: 6 visits and 2 trials

Day 17Referrals

Warm intros

  • Ask every paying and trial store for one neighbour introduction
  • Send the intro message the owner can forward
  • Log which referral source produces visits

Deliverable: 3 warm introductions from existing contacts

Day 18Field day 5

Closing

  • Revisit all trials older than 3 days
  • Take payment on the spot where possible
  • Note any store that still has not printed a label

Deliverable: 2 additional paid licences or documented reasons

Day 19Retention

Activation

  • Check label print counts per paying store
  • Call any store with zero prints and walk them through it
  • Log the single blocker that stops printing

Deliverable: Every paying store has printed at least one sheet

Day 20Field day 6

Volume

  • Visit 6 stores, half from referrals
  • Pitch second-location licences to multi-outlet owners
  • Collect two more trials

Deliverable: 20+ cumulative visits, 5+ paid licences

Day 21Review

Week 3 numbers

  • Recompute conversion rate per cluster
  • Cut the weakest cluster if conversion is zero
  • List the top three objections again

Deliverable: Cluster ranking and revised visit plan

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

Second neighbourhood

  • Pick one adjacent neighbourhood with 15+ grocery stores
  • Prepare 8 store-specific sample sheets
  • Start the visit round

Deliverable: 8 sample sheets for the new area

Day 23Field day 7

New area

  • Visit 6 stores in the new neighbourhood
  • Use the print-shop export as the hook
  • Take trials on the spot

Deliverable: 6 visits, 2 trials

Day 24Field day 8

Pipeline depth

  • Visit 6 more stores
  • Follow up all unconverted trials by WhatsApp
  • Ask for referrals at every yes

Deliverable: 12 visits in the new area, 1 more paid licence

Day 25Product

Remove friction

  • Fix the most common blocker from days 15-24
  • Add bulk expiry entry for owners with 100+ SKUs
  • Rebuild and deploy

Deliverable: Friction fix shipped and deployed

Day 26Proof

Case study

  • Ask each paying store for one written line and one shelf photo
  • Compile into a single-page PDF
  • Send the PDF to every open trial

Deliverable: One-page proof sheet sent to all trials

Day 27Organic reach

Local retailer groups

  • Post the 60-second demo in two local retailer WhatsApp groups
  • Offer the sample sheet to anyone who replies
  • Log inbound replies as leads

Deliverable: 2 posts live and an inbound lead list

Day 28Upsell

Second locations

  • Pitch second-location licences to every multi-outlet owner
  • Collect payment where agreed
  • Ask each paying store for one referral name

Deliverable: At least 1 second-location licence or 5 referral names

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

Stragglers

  • Revisit every unconverted trial in person
  • Offer the 7-day trial one last time
  • Take payment on the spot

Deliverable: All possible late conversions closed

Day 30Reconcile

Numbers and post-mortem

  • Reconcile payments against TrustMRR
  • Count licences, refunds and support tickets
  • Write the post-mortem and next-30-day decision

Deliverable: Verified revenue count and written post-mortem

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

  • All scenarios use one price point: $199 one-time Store License (no subscription).
  • Payment processing assumed on Stripe at roughly 4.5% effective (2.9% + $0.30 plus currency cost) — Conservative/Base/Upside.
  • Ad spend is zero in Conservative and Base; Upside assumes $150 of sponsored posts in local retailer groups — Upside only.
  • Operating costs cover Vercel, Supabase, domain and PDF rendering; there is no LLM inference cost because scanning is deterministic.
  • Refunds assumed at zero in Conservative and Base; one $199 refund in Upside given 25 licences.
  • Chargebacks assumed zero across all scenarios because licences are sold in person.
  • All figures are projections from stated assumptions, not verified revenue.

Conservative

3 customers
$597
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$27
Paid marketing
$0
Hackathon profit
$570
Operating costs
$25
Business profit
$545

Base case

10 customers
$1,990
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$90
Paid marketing
$0
Hackathon profit
$1,900
Operating costs
$45
Business profit
$1,855

Optimistic

25 customers
$4,975
collected revenue · avg payment $199
Refunds
$199
Chargebacks
$0
Payment fees
$224
Paid marketing
$150
Hackathon profit
$4,402
Operating costs
$110
Business profit
$4,292

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,990
Payment fees (3.9%)
$78
Paid marketing
$0
Hackathon profit
$1,912
Business profit
$1,867

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, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Store owners do not see expiry tracking as a real cost and never convert.

Mitigation

Lead every visit with a loss question and the printed store-specific label sheet instead of a feature pitch.

Validation experiment

On 10 visits ask 'how much dairy did you throw away last week?' before showing the product.

Kill criteria

Abandon if fewer than 3 of 10 owners can name a waste number after 20 visits.

Risk 2Label PDFs print misaligned at local print shops, making the output useless.

Mitigation

Fix the grid at exact millimetre positions and ship a one-line print instruction at 100% scale.

Validation experiment

Print the same PDF at three print shops and one store printer before day 5.

Kill criteria

Do not sell until one real store prints a usable sheet; fix, do not abandon.

Risk 3$199 is above what a single-store owner will approve without an accountant.

Mitigation

Anchor the price to one week of avoided waste and allow payment on the spot.

Validation experiment

Quote $199 to 5 stores and $99 to 5 stores and compare conversion.

Kill criteria

Reprice once only if $199 converts 0/5 while $99 converts 3/5.

Risk 4Barcode scanning fails on loose produce and unlabelled items, stalling the demo.

Mitigation

Manual name and barcode entry is always one tap away and is demonstrated in every pitch.

Validation experiment

Run 20 real barcodes from a single store through the scanner on a mid-range phone.

Kill criteria

If more than half of packaged barcodes fail, switch to manual-first entry before selling.

Risk 5The founder's city does not contain enough independent grocery stores to reach 25 licences.

Mitigation

Two neighbourhood clusters plus referral introductions extend reach without ads.

Validation experiment

Map 40 candidate stores within two neighbourhoods before day 6.

Kill criteria

If fewer than 40 candidates exist in reach, widen the radius rather than the product.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Supabase project
  • Define stores, products and licences tables with row-level security

Output: Working database schema and auth configuration

Hours 3-5

  • Scaffold Next.js app
  • Add login and deploy to Vercel on a custom domain

Output: Live URL with working store login

Hours 6-8

  • Integrate QuaggaJS camera scanning
  • Add manual barcode entry fallback
  • Test with a real milk carton

Output: Scan-to-add flow working on a physical phone

Hours 9-11

  • Build product entry form with expiry date and MRP
  • Query products into 3/7/14-day buckets

Output: Expiry dashboard listing real scanned products

Hours 12-14

  • Build PDFKit label endpoint on an Avery-compatible A4 grid
  • Add 10/20/30% discount presets

Output: Downloadable label PDF with computed prices

Hours 15-18

  • Wire Stripe Checkout at $199 one-time
  • Add licence activation webhook and gated access

Output: Paid checkout path ready for TrustMRR-connected payments

Hours 19-21

  • Run an end-to-end smoke test with three real products
  • Print one sheet at a local shop

Output: Verified buy-to-print flow and a physical label sheet

Hours 22-24

  • Draft the first store-specific sample label sheet
  • List 20 target stores within 5 km

Output: One printed sample sheet and a ranked visit list

Complete report

Full 30-day launch report

Read the full generated report

ExpiryTag — 30-Day Launch Report

Concept: ExpiryTag (v1) · JEV score: 61.0/100 (band C) · Window: 16 Nov 2026 13:00 UTC – 16 Dec 2026 13:00 UTC · Founder: one person.

1. Product opportunity and positioning

ExpiryTag sells one narrow workflow to one narrow buyer: an independent grocery store owner in urban India who walks the aisles with a pen, squints at date codes, and handwrites "10% off" on stickers. That owner has three bad options today — sell near-expiry stock at full price and carry a food-safety risk, throw it away and eat the loss, or spend 45 minutes a day hunting dates by hand. ExpiryTag replaces all three with scan, alert, print.

The JEV score is honest about the shape of this bet. Speed to first revenue (7.98 normalized) and solo build feasibility (7.59) are the strongest criteria: a five-day build and a buyer who can be met in person. Market demand (4.29) and monetization potential (4.69) are the weak spots, and the plan attacks both directly instead of pretending they are not there. The buyer is narrowed to the owner whose near-expiry dairy, bakery and packaged staples are a visible weekly loss, and the price is anchored to the markdown revenue recovered, not to "software".

Positioning: this is not inventory management and not a POS. It is the markdown machine. Staff scan a barcode, type the expiry date once, and the dashboard buckets stock into 3 / 7 / 14-day windows. Anything expiring prints onto an Avery-compatible sheet carrying the store's own name, the new discounted price and the expiry date. The output is physical, shelf-ready, and takes two minutes to demonstrate — which is what matters when you are selling door to door with no brand.

The realistic alternative is a notebook or a free spreadsheet, and neither can produce a sticker. Against paid retail suites, ExpiryTag is $199 once, needs no hardware, no integrator and no training day. That gap is the whole business.

2. Smallest sellable MVP

The sellable unit is: log in, scan a barcode, enter expiry and MRP, see what expires this week, print a sheet of discount labels with the store's name on it. Nothing more is required before an owner hands over $199.

Must ship: phone-camera barcode scan (QuaggaJS) with manual fallback; product record with barcode, name, MRP, expiry date; dashboard with 3/7/14-day buckets sorted by days left; discount presets (10/20/30%) that compute the new price; a PDFKit label sheet on an Avery A4 grid; store profile with name, logo upload and currency formatting; Stripe one-time checkout with licence activation.

Explicitly not built: inventory counts, supplier ordering, POS integration, a customer-facing app, multi-store analytics, thermal printer drivers, automated barcode-to-name lookup (staff type the name once), translated UI, app-store binaries.

3. Technical implementation plan

Stack: Next.js and React on Vercel, Supabase for Postgres and auth, QuaggaJS for scanning, PDFKit server-side for labels, Stripe Checkout for the one-time $199 licence, Resend for the receipt and onboarding email.

Architecture: one Next.js app. Supabase holds stores, products and licence status with row-level security keyed on store_id. The browser scans with QuaggaJS and writes the product row through the Supabase client. The label endpoint is a serverless function: it takes product IDs, renders a PDF with PDFKit onto an A4 Avery-compatible grid, and streams it back. The biggest build risk is grid measurements and margins — labels drift if the print dialog scales above 100%. Stripe Checkout redirects to a webhook that flips licence_active.

Build steps: (1) repo, Supabase schema, auth; (2) scan-to-add product flow; (3) expiry dashboard buckets; (4) label PDF endpoint and print preview; (5) Stripe checkout and activation webhook; (6) deploy to a custom domain on Vercel; (7) smoke test on a real phone with a real milk carton. No LLM is used — barcode decoding is deterministic and the deliverable is a PDF.

4. Pricing and monetization

One tier: Store License, $199 one-time — unlimited label generation, barcode scanning, expiry alerts, lifetime access for that location. A 7-day free trial exists only so the owner can run one real markdown cycle before paying.

Why $199: it is roughly the value of one week of avoided dairy waste in a busy store, and small enough for the owner to approve on the spot without an accountant. The monetization weakness is answered by the upsell path, not a price rise: a second location is a second $199 licence, and every paying store is asked for one introduction to a neighbouring owner. Payment runs through Stripe Checkout (a UPI/Razorpay fallback if Stripe onboarding stalls), connected to TrustMRR from day one, with nothing charged before launch.

5. First-customer acquisition

Primary channel: in-person visits to independent grocery stores within 5 km, followed by WhatsApp follow-up. No ads, no SEO, no marketplace.

Where: kirana clusters around vegetable markets; residential colony main roads; stores already stocking dairy and bakery; stores with visible offer bins; and the local print shop, which is both a referral source and a delivery point for PDFs.

Outreach: walk in between 11:00 and 13:00 and ask for the owner; hand over a pre-printed label sheet already carrying their store name and three of their real products; run the two-minute demo on your phone with a product from their shelf; offer the 7-day trial and take payment on the spot from whoever says yes; WhatsApp the app link and a 60-second screen recording that evening; ask for one neighbouring store name before leaving.

Week-one goal: 20 stores visited, 5 trials started, 1 paid licence.

6. 30-day execution roadmap

Days 1–5 are build only: schema and auth, scanning, dashboard, label PDF, then Stripe and a live paid product by end of day 5. Days 6–7 produce ten store-specific sample sheets and start visits. Days 8–14 are field days: visit, follow up by WhatsApp, close the first paid licence by day 10, then refine the label template from the paying store's print feedback and capture one quote and one shelf photo. Days 15–21 add a print-shop export for stores without printers, cover a second store cluster, run referral asks, and target 5+ licences with every paying store printing at least one sheet. Days 22–28 widen to a second neighbourhood, ship one friction fix, and pitch second-location licences to multi-outlet owners. Days 29–30 convert stragglers, reconcile payments against TrustMRR, and write the post-mortem.

7. Revenue and profit scenarios

Projections only — derived from stated assumptions, not verified revenue, not existing customers.

Conservative: 3 licences × $199 = $597 gross, 4.5% Stripe fees $27, no refunds or ads, operating $25. Base: 10 × $199 = $1,990, fees $90, operating $45. Upside: 25 × $199 = $4,975, one refund $199, fees $224, $150 of sponsored retailer-group posts, operating $110. Hackathon profit excludes operating costs; business profit includes them. In the base case that is roughly $1,900 versus $1,855. The spread between conservative and upside is visit volume and conversion, not product scope, which is why days 6–28 are almost entirely field days.

8. Risks and validation experiments

The owner does not care about expiry: on ten visits ask "how much dairy did you throw away last week?" before showing the product, and abandon the positioning if fewer than three give a number. Labels print misaligned: print the same PDF at three local print shops before day 5 and correct the grid rather than the plan. $199 is too high: quote $199 to five stores and $99 to five, and reprice once only if $199 converts 0/5 while $99 converts 3/5. Barcode scan fails on loose produce: manual entry is the mitigation and stays a non-goal. Not enough stores in reach: map 40 candidates across two neighbourhoods before day 6 and widen the radius rather than the product.

9. First 24-hour action plan

Hours 1–2: Supabase project, schema, auth. Hours 3–5: Next.js scaffold deployed to Vercel with working login. Hours 6–8: QuaggaJS scan flow working on a physical phone, tested on a milk carton. Hours 9–11: product entry form plus the 3/7/14-day dashboard query. Hours 12–14: PDFKit label endpoint with Avery measurements and discount presets. Hours 15–18: Stripe Checkout at $199 and the licence activation webhook. Hours 19–21: end-to-end smoke test with three real products and one printed sheet. Hours 22–24: draft the first store-specific sample label sheet and a ranked list of 20 stores within 5 km.

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 →