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

SameStreet Drop

Turns a just-finished home-service job into a print-ready neighborhood door-hanger drop with a unique QR code per door and a live scan-alert feed, so the pro sees exactly which neighbor is interested.

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.09/10
MVP build (solo)
4 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach to local exterior-trade pros on Google Business Profile who posted a job photo in the last 14 days, with a free pre-built drop attached.
Who pays

Owner-operators of 1-3 person residential exterior trades (roofing, painting, pressure washing, gutters, fencing, window cleaning, landscaping) in US suburbs, found on Google Business Profile with 10-100 reviews and job photos posted in the last 14 days.

Biggest execution risk

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

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

0/15
Entry price
$99
Solo build
4 days
30d base revenue
$2,530
30d hackathon profit
$2,450
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operators of 1-3 person residential exterior trades (roofing, painting, pressure washing, gutters, fencing, window cleaning, landscaping) in US suburbs, found on Google Business Profile with 10-100 reviews and job photos posted in the last 14 days.

Why now

A solo founder can ship this in four days on serverless infrastructure, and the pro can walk the street the same afternoon — no procurement, no integration, no SEO ramp, no marketplace cold-start.

Problem

The 25-40 homes that just watched the pro work are the cheapest leads available, but activating them requires designing a flyer, guessing a discount, printing, and hand-delivering with no feedback on whether any of it worked.

Solution

The pro uploads 1-3 job photos plus the address and a price range; the app returns a print-ready PDF of 25-40 door hangers each with its own QR code, a public proof page, a quote request form, and SMS alerts naming the door that scanned.

Differentiation · Marketplace leads charge per click for strangers; blank print-shop hangers report nothing. SameStreet Drop is one flat fee aimed at neighbors who watched the job happen, and it reports scan time and door code back to the pro.

1. Product opportunity and positioning

SameStreet Drop sells one physical-adjacent artifact: a coded door-hanger drop for the street a pro just finished working on. The buyer is the owner-operator of a 1-3 person exterior trade — roofing, painting, pressure washing, gutters, fencing, window cleaning, landscaping — with 10-100 Google reviews and public job photos. The trigger is concrete and recurring: a job just wrapped on a residential street and 25-40 neighbours watched it happen.

That is the cheapest lead pool a pro will ever touch, and today it goes cold within a week. Activating the street means designing a flyer, guessing a discount, printing, walking the doors, and getting zero feedback. The alternatives are worse in different ways: marketplace leads (Angi, Thumbtack) bill per click for strangers, and print shops sell blank hangers with no attribution. SameStreet Drop's entire claim is attribution — every door carries its own QR code and short code, so the pro learns which house scanned and when, which paper door hangers have never done.

Positioning is deliberately narrow: not a CRM, not a website builder, not a lead marketplace, not a photo-to-quote SMS bot. One flat fee per street, one same-day deliverable, one measurable outcome. The pro prints at home or at a copy shop; nothing ships, nothing is stored, no human touches fulfillment.

Answering the JEV critique. JEV scored this concept 60.9/100 (band C). Its two weakest criteria were monetization potential (3.97) and market demand (4.19). The response is not to broaden the product. It is (a) a three-street bundle at $249 that lifts order value without adding build scope, (b) a repeat-street motion where every delivered drop ends with a request for the next job's street, and (c) anchoring the price against a single marketplace lead, not against software. What the concept scores well on — speed to first revenue (8.66) and solo build feasibility (7.79) — is exactly what a 30-day contest rewards, so the plan below spends its risk budget on outreach volume, not on features.

Honest ceiling. At $99-$249 per street, this is a fast first-dollar concept, not a $100K contender. The plan aims to prove the repeat-purchase loop works; if it does, the recurring version is the real business, and that is a post-contest problem.

Section 2 of 8

Smallest sellable MVP

A paid, working drop: job intake form, a 25-40 door PDF with one unique QR code per door, a public proof page with a quote form, and SMS scan alerts — unlocked by a $99 Stripe Payment Link.

Must-have features

  • Job intake: 1-3 photos, address, trade, offer text, price range
  • PDF generator outputting 25-40 uniquely coded door hangers, 4-up on letter sheets
  • Per-door QR redirect that logs scan timestamp and forwards to the proof page
  • Public proof page per job with before/after photos and a quote request form
  • SMS + email scan alert naming the door code with a map link
  • Stripe Payment Link checkout that unlocks the PDF and the scan feed for 30 days
  • Pro dashboard listing each drop with scan count and quote requests

Explicitly out of scope

  • Print fulfillment or shipping
  • CRM, scheduling, invoicing, or collecting payment for the pro's customers
  • Inbound SMS/WhatsApp bot or AI quoting
  • Website builder, SEO tooling, Google Business Profile sync
  • Marketplace, directory, or consumer-facing app
  • Team accounts, roles, enterprise features

Demo flow (what the buyer sees)

  1. Founder opens the intake form and uploads two photos from a pro's public Google Business Profile job post
  2. Enters the street address, trade, offer sentence and price range
  3. App geocodes the address and synthesizes 25-40 neighbouring door codes
  4. App renders the 4-up letter-sheet PDF with one QR code and short code per hanger
  5. Founder downloads the PDF, scans one code on a phone, the proof page opens
  6. Scan is logged and an SMS alert fires to the pro's number within seconds
  7. Pro sees the alert, opens the dashboard, and sees the drop with 1 scan and 1 quote request
Build plan

Technical implementation plan

Stack

Next.js 14 on VercelSupabase (Postgres + storage for job photos)Stripe Payment Links + webhookReact-PDF for the door hanger layoutVercel Edge function for QR redirect and scan loggingTwilio SMS for scan alertsResend for transactional emailGoogle Geocoding API for address to door-list expansion

Architecture

A single Next.js app on Vercel. Supabase holds jobs, drops, doors and scans. The pro submits a job through a server action that writes photos to Supabase storage and geocodes the address into a list of door codes. A React-PDF route renders the PDF from the door list at request time. Each door code resolves through an edge function at /d/[code], which writes a scan row and 302-redirects to the job's public proof page. A Postgres trigger on scans calls a small API route that fires Twilio SMS and Resend email to the drop owner. Stripe Payment Links handle checkout; a webhook flips drops.status to active and stamps the 30-day alert window. The dashboard is a server-rendered list of drops scoped by a per-purchase magic-link token.

Build steps

  1. Scaffold Next.js + Supabase, deploy the empty app to Vercel
  2. Create schema: jobs, drops, doors, scans, purchases, with row-level tokens
  3. Build the job intake form with photo upload to Supabase storage
  4. Geocode the address and generate 25-40 door records with unique short codes
  5. Render the 4-up letter PDF with React-PDF, QR per door via a server-side QR library
  6. Ship the edge redirect at /d/[code] that logs scan time, UA and door code
  7. Build the public proof page with before/after photos and a quote request form
  8. Add Stripe Payment Link plus webhook that unlocks the PDF and scan feed for 30 days
  9. Wire Twilio SMS and Resend email scan alerts from the scans table
  10. Ship the token-scoped pro dashboard with scan counts and quote requests
  11. Instrument funnel events: sample_sent, page_view, checkout_started, paid
  12. Load-test PDF generation at 40 doors and cache the result per job

AI components

  • One optional LLM call drafts the hanger headline and offer sentence from trade + address + job photos; the MVP ships with a template fallback so the product does not depend on it
Hardest technical risk: QR code density and print quality: 40 distinct codes on 4-up letter sheets at home-printer resolution can render unscannable, which silently kills the entire tracking story. Generate QR at high error correction, enforce a minimum module size, and test with three real phone cameras on a printed sheet before day 5.
Section 3 of 8

Pricing and monetization

One Street Drop

Entry offer
$99 one-time

For Solo pro who just finished a job and wants the surrounding 25-40 homes

  • Print-ready PDF with 25-40 uniquely QR-coded door hangers
  • Live proof page for the job
  • SMS scan alerts for 30 days
  • Quote request inbox

Three Street Bundle

$249 one-time

For Pro running back-to-back jobs in one suburb

  • Three separate coded drops, up to 120 doors
  • 90 days of scan alerts
  • Combined scan and quote dashboard

Model: One-time purchase per street drop, with a discounted three-street bundle; no subscription and no per-lead fees.

First revenue offer: "Here is a door hanger drop for the Elm St job you posted two weeks ago — 32 doors, each with its own QR code, already built. The PDF is yours free. If you want the live version that texts you when a door scans, it is $99 for this street."

Expected ACV: $99

Upsell path: At delivery of every drop, ask for the next street the pro is working and offer the three-street bundle at $249. Every delivered drop ends with a one-line ask, so repeat purchase is built into the delivery message rather than a separate sales motion.

Target customers
55
Revenue model
$5,445
Costs
$180
Profit model
$5,265
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to local exterior-trade pros on Google Business Profile who posted a job photo in the last 14 days, with a free pre-built drop attached.

Where to find them

  • Google Maps search for 'pressure washing', 'roof cleaning', 'exterior painting', 'gutter cleaning', 'fence staining' within 60 miles
  • Google Business Profile listings with 10-100 reviews and a photo posted in the last 14 days
  • Local Services Ads results for those trades (pros already paying for leads)
  • Nextdoor and local Facebook town groups where pros post finished-job photos
  • Copy-shop counter conversations where pros print their own flyers

Exact outreach motions

  • Build the sample drop from their own published photos and street address, then send the finished PDF before asking for anything
  • Email with subject 'A door hanger drop for the Elm St job you posted' and the PDF attached, one paragraph, no pitch deck
  • Text only to published business mobile numbers, with a single line and the PDF link
  • 72-hour follow-up with one line: '32 doors covered, offer copy is yours to keep either way'
  • At delivery, ask for the next street and quote the three-street bundle
  • Ask every buyer for one other pro on the same street and send that pro a sample too

Message template

Subject: A door hanger drop for the Elm St job you posted

Hi Dave — saw the driveway job you posted on Elm St. I built you a door hanger drop for that street: 32 homes, each with its own QR code, so you can see which door looks. The PDF is attached and it is yours free, no strings. If you want the live version that texts you when a door scans, it is $99 for this street. Either way, print it and use it.

— [Founder], SameStreet Drop
Week-one goal: 120 qualified pros logged and 50 free sample drops built and sent, with at least 6 replies and at least 1 paid $99 drop by day 8.
Section 5 of 8

30-day execution roadmap

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

Skeleton and schema

  • Scaffold Next.js and Supabase, deploy to Vercel.
  • Create jobs, drops, doors, scans and purchases tables.
  • Set up a Stripe test Payment Link and webhook route.

Deliverable: Deployed app with schema live

Day 2Build

Job intake

  • Build the intake form: photos, address, trade, offer, price range.
  • Wire photo upload to Supabase storage.
  • Geocode the address and generate door records.

Deliverable: Working intake producing 25-40 doors

Day 3Build

PDF generation

  • Build the React-PDF 4-up letter layout.
  • Embed a unique QR and short code per door.
  • Test print quality with three phone cameras.

Deliverable: Downloadable coded PDF

Day 4Build

Tracking

  • Ship the /d/[code] edge redirect with scan logging.
  • Build the public proof page with before/after photos.
  • Add the quote request form.

Deliverable: Scannable QR resolving to a proof page

Day 5BuildMVP shipped

Paywall and alerts

  • Wire Stripe webhook to unlock PDF and scan feed for 30 days.
  • Fire Twilio SMS and Resend email on each scan.
  • Ship the token-scoped pro dashboard.

Deliverable: Paid end-to-end drop, MVP live

Day 6Outreach

Prospect list

  • Build a 120-row list of GBP pros in target trades within 60 miles.
  • Filter to 10-100 reviews and a photo in the last 14 days.
  • Log contact channel and the exact job photo to use.

Deliverable: 120-row prospect list

Day 7Outreach

First 25 samples

  • Build 25 sample PDFs from prospect photos and addresses.
  • Send 25 emails with the PDF attached.
  • Record send time and open status.

Deliverable: 25 free sample drops delivered

Week 2 · Launch & first sale · 7 days
Day 8OutreachFirst sale target

Second wave plus first sale

  • Send 25 more sample drops.
  • Reply to every response within one hour.
  • Offer the $99 link to any pro who engages.

Deliverable: First paid drop (target day)

Day 9Product

Fix what the first buyer hits

  • Reproduce every issue the first buyer reported.
  • Ship fixes to PDF layout and alert copy.
  • Re-test the scan flow end to end.

Deliverable: Patched build, buyer unblocked

Day 10Outreach

Volume

  • Send 30 sample drops.
  • Follow up at 72 hours on the first 50.
  • Log reply rate by trade.

Deliverable: 80 cumulative samples sent

Day 11Outreach

Reply conversion

  • Run every live reply into a checkout link.
  • Add a one-screen demo video to the email.
  • Record objections verbatim.

Deliverable: Objection list with 5+ entries

Day 12Product

Bundle checkout

  • Add the three-street bundle at $249.
  • Let one purchase carry three drops.
  • Extend the alert window to 90 days for bundles.

Deliverable: Bundle tier purchasable

Day 13Proof

Public case study

  • Ask the first buyers for permission to use scan counts.
  • Publish a landing page with one before/after example.
  • Add the sample request form.

Deliverable: Live landing page

Day 14Review

Funnel math

  • Compute samples sent, reply rate, paid conversion.
  • Cut the weakest trade vertical.
  • Rewrite the outreach opener from real replies.

Deliverable: Funnel sheet with day-15 targets

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

New metro

  • Rebuild the prospect list in a second metro.
  • Send 30 sample drops.
  • Track reply rate against metro one.

Deliverable: Second-metro results

Day 16Outreach

Follow-ups

  • Follow up on all unanswered samples older than 72 hours.
  • Send 25 new samples.
  • Log every unsubscribes request immediately.

Deliverable: Follow-up pass complete

Day 17Retention

Repeat purchase

  • Message every past buyer asking for their next street.
  • Quote the bundle at delivery.
  • Log take rate.

Deliverable: Repeat-purchase data on all buyers

Day 18Outreach

Organic trade groups

  • Post the free-sample offer in two trade Facebook groups.
  • Reply to every comment with a built sample.
  • Link the landing page.

Deliverable: 20 inbound sample requests

Day 19Product

Sample automation

  • Script the sample build from a CSV row.
  • Cut per-sample time below four minutes.
  • Add a template library by trade.

Deliverable: Automated sample pipeline

Day 20Outreach

Volume

  • Send 40 samples via the automated pipeline.
  • Email the 30 best non-responders a second angle.
  • Track which trade replies fastest.

Deliverable: 150 cumulative samples sent

Day 21Review

Conversion check

  • Compare scan rate of delivered drops against assumptions.
  • Decide whether the tracking story holds.
  • Set day-22 through day-30 targets.

Deliverable: Go/no-go note on the core claim

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

Volume

  • Send 40 samples.
  • Follow up on all bundle quotes.
  • Log every payment received.

Deliverable: 60 replies cumulative

Day 23Product

Alert quality

  • Rewrite the scan SMS to name the street and door code.
  • Add a scan-to-quote conversion line on the dashboard.
  • Ship a one-tap copy of the offer text.

Deliverable: Improved alert and dashboard

Day 24Outreach

Reactivation

  • Re-contact every pro who replied but did not buy.
  • Offer a single street at the bundle rate.
  • Close as many as possible today.

Deliverable: Reactivation revenue

Day 25Retention

Second street push

  • Message all buyers for the next street.
  • Offer bundles only to buyers with a live drop.
  • Log the bundle take rate.

Deliverable: Bundle revenue attempt complete

Day 26Outreach

Volume

  • Send 40 samples.
  • Test a shorter two-line message on half the list.
  • Record which opener converts.

Deliverable: A/B result on the opener

Day 27Paid test

Small spend

  • Spend up to $100 sponsoring one local trade group post.
  • Send every responder a sample.
  • Measure cost per reply.

Deliverable: Paid channel read

Day 28Review

Numbers

  • Recompute hackathon profit from collected revenue.
  • Verify every refund and fee.
  • Decide if the paid test repeats.

Deliverable: Reconciled profit sheet

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

Final closes

  • Send 40 samples to the warmest remaining prospects.
  • Call every unanswered bundle quote.
  • Close outstanding checkout links.

Deliverable: Final-week revenue

Day 30Wrap

Reconcile and document

  • Reconcile Stripe payouts against the contest window.
  • Document repeat-purchase rate and scan rate.
  • Write the post-contest plan for the recurring version.

Deliverable: Final profit record and next-step memo

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: 6 paid drops, mostly $99 singles with one $249 bundle, blended ARPU $115.
  • Base: 22 paid drops at the same blended $115, driven by 150+ free samples sent.
  • Upside: 55 paid drops at a $112 blend, matching the concept's 30-day target; this is a projection, not observed traction.
  • Stripe is the assumed processor at 2.9% + $0.30 per transaction, reflected in payment_fees_usd.
  • No ad spend in Conservative or Base; organic outreach only.
  • Upside includes a $300 test of sponsored local trade-group posts.
  • Operating costs cover Vercel, Supabase, Twilio, Resend, Google geocoding and a domain — under $5 per paid drop.
  • Refunds and chargebacks are near zero because the PDF is delivered instantly and is not recoverable; Upside carries one refund and one chargeback.
  • Every figure is a scenario projection, not verified revenue, customers or traction.

Conservative

6 customers
$690
collected revenue · avg payment $115
Refunds
$0
Chargebacks
$0
Payment fees
$22
Paid marketing
$0
Hackathon profit
$668
Operating costs
$40
Business profit
$628

Base case

22 customers
$2,530
collected revenue · avg payment $115
Refunds
$0
Chargebacks
$0
Payment fees
$80
Paid marketing
$0
Hackathon profit
$2,450
Operating costs
$110
Business profit
$2,340

Optimistic

55 customers
$6,160
collected revenue · avg payment $112
Refunds
$99
Chargebacks
$99
Payment fees
$195
Paid marketing
$300
Hackathon profit
$5,467
Operating costs
$240
Business profit
$5,227

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,178
Payment fees (3.9%)
$85
Paid marketing
$0
Hackathon profit
$2,093
Business profit
$1,983

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 built from the stated assumptions. These are projections, not verified revenue, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Pros buy one $99 drop as a novelty and never repeat, capping the business at a single transaction per customer.

Mitigation

Quote the three-street bundle at delivery of every drop and ask for the next street in the same message.

Validation experiment

Ask all first buyers for their next street and record bundle take rate over 14 days.

Kill criteria

If fewer than 10% of buyers purchase a second drop within 21 days, stop selling singles and rebuild the offer as a monthly route subscription.

Risk 2Cold outreach response rates from Google Business Profile contact details are far below the plan's assumption.

Mitigation

Send the finished sample before asking for money, and split-test the opener weekly.

Validation experiment

Send 50 personalized samples and measure reply rate by trade and by metro.

Kill criteria

If reply rate stays under 3% after 150 sends, abandon cold outreach and switch to copy-shop counter placement and trade-group inbound.

Risk 3QR scan volume is too low to feel like proof, making the tracking story unconvincing.

Mitigation

Enforce print-quality QR standards and add a printed incentive line on the hanger.

Validation experiment

Hand-deliver 30 hangers on one real street and count scans over 7 days.

Kill criteria

If scan rate is under 2% on a controlled drop, replace QR-only tracking with a text-to-shortcode reply and reprice the offer.

Risk 4Building free personalized samples at scale consumes more founder hours than the 30-day window allows.

Mitigation

Script the sample pipeline from a CSV row so a sample builds in one command.

Validation experiment

Time 10 sample builds end to end after automation.

Kill criteria

If a sample still takes over six minutes, cut the free-sample motion to 25 samples per week and charge $19 for extras.

Risk 5Cold texts to Google business numbers get reported as spam and shut the channel down.

Mitigation

Lead with email, text only published business lines, and honor every stop request instantly.

Validation experiment

Split 25 emails against 25 texts and count replies versus complaints.

Kill criteria

If any complaint is filed or reply rate on text is not at least double email, drop SMS outreach entirely.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and create Vercel and Supabase projects.
  • Scaffold the Next.js app and deploy it.
  • Write the schema: jobs, drops, doors, scans, purchases.

Output: Deployed app with a live database schema

Hours 3-4

  • Build the job intake form.
  • Wire photo upload to Supabase storage.
  • Geocode an address into 25-40 door records.

Output: Working intake form producing a door list

Hours 5-6

  • Build the 4-up React-PDF door hanger layout.
  • Generate a unique QR and short code per door.
  • Print one sheet and scan it with two phones.

Output: A physically scannable coded PDF

Hours 7-8

  • Ship the /d/[code] edge redirect with scan logging.
  • Build the public proof page and quote form.
  • Verify the scan appears in the database.

Output: End-to-end scan tracking

Hours 9-10

  • Create the $99 Stripe Payment Link and webhook unlock.
  • Start the 120-row prospect list from Google Maps.
  • Log the first 20 prospects with their job photo URLs.

Output: Live payment link plus a seeded prospect list

Complete report

Full 30-day launch report

Read the full generated report

SameStreet Drop — 30-Day Launch Report

Concept v1 · JEV score 60.9/100 (band C) · contest window Nov 16 – Dec 16, 2026. Every revenue number here is a projection built from stated assumptions. Nothing below is verified traction, and there are no customers, partners or sources to cite yet.

1. Product opportunity and positioning

SameStreet Drop sells one physical-adjacent artifact: a coded door-hanger drop for the street a pro just finished working on. The buyer is the owner-operator of a 1-3 person exterior trade — roofing, painting, pressure washing, gutters, fencing, window cleaning, landscaping — with 10-100 Google reviews and public job photos. The trigger is concrete and recurring: a job just wrapped on a residential street and 25-40 neighbours watched it happen.

That is the cheapest lead pool the pro will ever touch, and today it goes cold within a week. Activating the street means designing a flyer, guessing a discount, printing, walking the doors, and getting zero feedback. The alternatives fail differently: marketplace leads bill per click for strangers, and print shops sell blank hangers with no attribution. The claim is attribution — every door carries its own QR code and short code, so the pro learns which house scanned and when, which paper door hangers have never done.

Positioning stays deliberately narrow: not a CRM, not a website builder, not a lead marketplace, not a photo-to-quote SMS bot. One flat fee per street, one same-day deliverable, one measurable outcome. The pro prints at home or at a copy shop; nothing ships and nothing is stored.

JEV's two weakest criteria were monetization potential and market demand. The answer is not scope creep. It is a $249 three-street bundle that lifts order value, a repeat-street motion appended to every delivery, and pricing anchored against a single marketplace lead rather than against software. What the concept scores well on — speed to first revenue and solo build feasibility — is what a 30-day contest actually rewards, so the risk budget goes to outreach volume, not features.

Ceiling, stated honestly: at $99-$249 per street this is a fast first-dollar concept, not a $100K contender. The 30 days exist to prove the repeat loop works.

2. Smallest sellable MVP

Four build days: an intake form (1-3 photos, address, trade, offer line, price range), a PDF generator that lays out 25-40 uniquely coded hangers 4-up on letter sheets, a per-door QR redirect that logs the scan and forwards to a public proof page, that proof page with before/after photos and a quote form, Twilio SMS and Resend email alerts to the pro, a Stripe Payment Link that unlocks PDF download and the scan feed for 30 days, and a token-scoped dashboard of drops with scan counts.

Out of scope on purpose: print fulfillment, CRM, scheduling, invoicing, inbound SMS bots, AI quoting, website building, SEO, Google Business Profile sync, marketplaces, and team accounts. None of them are needed for the first dollar and all of them slow the build.

3. Technical implementation plan

Next.js 14 on Vercel, Supabase Postgres plus storage, Stripe Payment Links with a webhook, React-PDF for the layout, a Vercel Edge function at /d/[code] for redirect and scan logging, Twilio for SMS, Resend for email, Google Geocoding to expand an address into a door list. A server action writes the job and geocodes the address; a PDF route renders on demand from the door list; each scan writes a row that triggers the alert route; the Stripe webhook flips the drop to active and stamps the 30-day window.

The real technical risk is print quality, not architecture. Forty distinct QR codes on home-printer letter sheets can render unscannable, which silently destroys the entire tracking story. Generate at high error correction, enforce a minimum module size, and print and scan a real sheet with three phones before day 5.

4. Pricing and monetization

One Street Drop at $99 one-time covers 25-40 coded doors, the proof page, 30 days of SMS alerts and the quote inbox. Three Street Bundle at $249 covers up to 120 doors, 90 days of alerts and a combined dashboard. No subscription, no per-lead fee.

The growth path is the repeat street, not a new tier. Every delivery message asks for the next street the pro is working and quotes the bundle. That turns a one-time novelty into a route, and it is the only thing that makes the business worth more than a single transaction per customer.

5. First-customer acquisition

One channel: direct outreach to exterior-trade pros on Google Business Profile who posted a job photo in the last 14 days. The founder searches Google Maps for the target trades within 60 miles, filters to 10-100 reviews with a recent photo, and builds the finished drop from that pro's own photos and street before asking for anything. The email is three lines and carries the PDF: 32 doors, each with its own QR code, free. The $99 live version is offered only after the sample lands.

Follow-ups go out once at 72 hours with a single line. Every buyer is asked for the next street at delivery. Every non-buyer who replied is re-contacted on day 24. The channel is free, measured daily, and dies immediately if reply rate collapses.

6. 30-day execution roadmap

Days 1-5 are pure build, shipping to production daily and hitting a paid end-to-end drop by end of day 5. Day 6 builds the 120-prospect list; day 7 sends the first 25 samples; day 8 is the first-sale target. Days 9-14 fix what buyers hit, add the bundle, publish a landing page and compute real funnel math. Days 15-21 rebuild the list in a second metro, automate sample generation below four minutes each, push repeat purchases, and run a go/no-go on whether tracking holds. Days 22-28 push volume to 150+ cumulative samples, reactivate non-buyers, test $100 of sponsored trade-group posts and reconcile profit. Days 29-30 close outstanding links and document the repeat-purchase rate.

7. Revenue and profit scenarios

All three scenarios are projections, not verified revenue.

Conservative — 6 drops, $690 gross. No refunds, no chargebacks, roughly $22 in Stripe fees, no ad spend, $40 operating. Hackathon profit is about $668.

Base — 22 drops, $2,530 gross. No refunds, no chargebacks, about $80 in fees, no ad spend, $110 operating. Hackathon profit is about $2,450.

Upside — 55 drops, $6,160 gross. One $99 refund, one $99 chargeback, about $195 in fees, $300 in sponsored posts, $240 operating. Hackathon profit is about $5,467.

Even the upside is far below the $100K ceiling. The contest goal here is a credible first dollar and a proven repeat loop, not the top prize.

8. Main risks and validation experiments

One-and-done buyers. Test: ask every buyer for their next street and track bundle take rate over 14 days. Kill signal: under 10% repeat within 21 days — rebuild as a monthly route subscription.

Outreach response too low. Test: 50 personalized samples, reply rate by trade and metro. Kill signal: under 3% after 150 sends — move to copy-shop counters and trade-group inbound.

Scan volume too low to feel like proof. Test: hand-deliver 30 hangers on one live street, count scans over 7 days. Kill signal: under 2% — switch to text-to-shortcode replies and reprice.

Sample production eats the founder's hours. Test: time 10 automated builds. Kill signal: over six minutes each — cut free samples to 25 per week.

Cold texts flagged as spam. Test: split 25 emails against 25 texts. Kill signal: any complaint, or text reply rate under double email — drop SMS outreach.

9. First 24-hour action plan

Hours 1-2: domain, Vercel and Supabase projects, scaffold and deploy, write the schema. Hours 3-4: intake form with photo upload and address geocoding into a door list. Hours 5-6: the 4-up PDF with per-door QR codes, printed and scanned with two phones. Hours 7-8: the /d/[code] redirect, scan logging, proof page and quote form. Hours 9-10: the $99 Stripe Payment Link plus the first 20 logged prospects with their job photo URLs. By end of day one there is a deployed app, a scannable hanger and a payment link — everything else in the 30 days is repetition and volume.

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 →