StampTrail Passport
Turns an event's booth or merchant list into a printable QR 'stamp passport', a live mobile web trail, and a per-stop engagement report, so organizers can prove sponsor foot traffic without an app or hardware.
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.
Event marketing manager or sponsorship lead at a 100-1,000 attendee B2B conference, trade show, or merchant association running a shop-local campaign, with an event in the next 30-90 days and a sponsor or board asking for foot-traffic proof.
Market demand 4.8/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 4 days; the plan targets a first sale on day 11; 6 sales at $199 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.2/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.
Product opportunity and positioning
Target customer
Event marketing manager or sponsorship lead at a 100-1,000 attendee B2B conference, trade show, or merchant association running a shop-local campaign, with an event in the next 30-90 days and a sponsor or board asking for foot-traffic proof.
Why now
One buyer controls every scan point, pays from an existing event budget, and needs the artifact before a fixed date, so a single conversation can close a $199 purchase this week.
Problem
Organizers sell booth and spot sponsorships but cannot hand a sponsor a countable per-stop visit report; paper stamp cards get lost and Google Forms cannot produce a passport experience.
Solution
The organizer uploads a CSV of stops, gets a QR poster PDF per stop, a mobile web passport attendees scan to collect stamps and unlock a prize, and a CSV/PDF report of unique scans, completions and time-of-day per stop.
1. Product opportunity and positioning
StampTrail Passport sells to exactly one person: the marketing manager, sponsorship lead, or merchant-association director who owns an event with 100-1,000 attendees and a fixed list of booths or shop stops. That person has usually already sold sponsorship packages against a promise of foot traffic, and now has to show something countable after the doors close. The realistic alternatives are paper stamp cards (lost, uncountable, no report), a Google Form per booth (no passport experience, messy per-booth data), or a custom app quote (weeks of lead time and thousands of dollars).
Why this buyer works for a solo founder in 30 days: the organizer controls every scan point, so there is no two-sided cold start. They already hold an event or sponsorship budget line, so a $199 one-time charge does not need procurement or legal review. And they have a hard date, which converts a nice-to-have into a deadline-driven purchase. No marketplace, no app store, no hardware, no integration with a venue system.
The product is deliberately narrower than the original location-social idea that inspired it. There is no friend graph, no public feed, no consumer sign-up funnel. The check-in mechanic is reused as a business instrument: the QR scan is the unit of proof, and the deliverable is a poster kit plus a report a sponsor can read. The economic buyer is the organizer, not the attendee.
JEV scored this concept 62.2/100 (band C, confidence 0.75). It is strongest where speed matters for a 30-day contest: speed to first revenue (8.18 normalized) and solo build feasibility (7.69). It is weakest on market demand (4.78) and monetization potential (4.98). This plan answers both directly. Demand risk is handled by narrowing the trigger to events inside a 30-90 day window and by leading every message with the sponsor report rather than the software. Monetization risk is handled by making the Season Pass ($449 for three trails in 90 days) a first-class offer from day 16, so a satisfied single-event buyer has a second reason to pay inside the same quarter.
The positioning sentence the founder should use everywhere: 'I turned your event floor plan into a QR stamp passport. Attendees scan at each booth, and you hand each sponsor a per-stop scan report. $199 for this event, live in an hour.' It names their asset, their output, their price and their setup time in one breath.
Smallest sellable MVP
Paid event workspace: CSV import of stops, generated QR poster PDF, live mobile passport with duplicate-blocked scans, and a downloadable per-stop report.
Must-have features
- CSV/Google Sheet import of stops with booth name, stop code and prize threshold
- QR code PNG plus print-ready A4/Letter poster PDF per stop
- Mobile web passport with stamp grid, progress bar and prize-unlock screen
- Scan endpoint recording stop and timestamp with one stamp per stop per attendee
- Organizer dashboard with live counts per stop and CSV/PDF report export
- Stripe Checkout paywall gating poster generation and the live trail
- Branding fields: logo upload, accent colour, prize text
Explicitly out of scope
- No native iOS or Android app
- No GPS or geofenced check-in, QR only
- No agency portal, white-label or reseller system
- No prize fulfilment, shipping or physical stamp cards
- No public trail directory or marketplace
- No CRM, email automation or attendee marketing suite
Demo flow (what the buyer sees)
- Organizer pays $199 via Stripe Checkout
- Organizer uploads a CSV of 25 booth names and stop codes
- System renders 25 QR posters into one print-ready PDF
- Organizer prints and places posters; attendees scan and collect stamps
- Dashboard shows unique scans per stop live during the event
- Organizer exports the per-stop CSV/PDF report and sends it to sponsors
Technical implementation plan
Stack
Architecture
A single Next.js app on Vercel serves three surfaces: the organizer dashboard (auth-gated), the public passport page at /t/[eventSlug] (no login), and the scan endpoint at /api/scan. Supabase Postgres holds events, stops, attendees, stamps and orders. Each poster QR encodes a signed per-stop URL; the passport stores a device token in local storage, and the scan endpoint rejects a second stamp for the same device and stop. Poster PDFs render server-side and stream directly to the browser. Stripe Checkout flips the order row to paid, which unlocks poster generation and the public trail; unpaid events stay in draft mode and cannot be scanned.
Build steps
- Create Next.js app, Supabase project and deploy a shell to Vercel
- Model events, stops, attendees, stamps, orders; add organizer magic-link login
- Build CSV import with per-row validation for booth name, stop code and prize threshold
- Generate signed QR payloads and render a batch poster PDF with logo and accent colour
- Ship the passport page: stamp grid, progress bar, prize unlock
- Ship the scan endpoint with device-token duplicate blocking and idempotent writes
- Wire Stripe Checkout and gate poster PDF plus live trail on paid status
- Build the dashboard: live per-stop counts, completions, time-of-day histogram
- Add CSV export then PDF report rendering from the same query
- Dry-run a full 25-stop event on a phone with throttled network before launch
AI components
- No LLM in the core flow; report narrative text is template-generated deterministically
Pricing and monetization
Single-Event Passport
Entry offerFor Event marketing manager or association director running one event or campaign
- One trail up to 25 stops
- QR poster PDF per stop
- Live mobile passport
- Per-stop CSV/PDF scan report
- 30-day hosting
Season Pass
For Agency or association running several events in a quarter
- Three trails within 90 days
- Custom branding per trail
- Prize-draw randomiser
- CSV and PDF report per event
Model: One-time per-event fee with a discounted multi-event Season Pass sold to the same buyer.
First revenue offer: $199 for this event: send me your booth list and I will have your QR stamp passport and sponsor report live within the hour.
Expected ACV: $199
Upsell path: Single-event buyers are offered the $449 Season Pass at the post-event report email, when the sponsor report has just proved useful; referrals to peer organizers are asked for in the same email.
First-customer acquisition
Personalized LinkedIn and email outreach to 75 named organizers and merchant-association directors, each receiving a pre-built demo trail using their own publicly listed booth or merchant names.
Where to find them
- Public event pages of small B2B conferences and trade shows with published exhibitor lists
- Chamber-of-commerce and merchant-association member directories
- Eventbrite and conference microsites with named organizer contacts
- LinkedIn titles: Sponsorship Manager, Event Marketing Manager, Executive Director
- Local shop-local campaign pages run by downtown associations
- Trade-show exhibitor manuals that list booth numbers
Exact outreach motions
- Send a demo link built from 3-5 of their real booth names, with the poster screenshot attached
- Lead with the sponsor proof angle: per-stop scan counts a sponsor can read
- Offer the $199 price and an hour of setup time in the first message
- Follow up once after three days with a mock per-stop report sample
- Ask every buyer for one peer organizer referral after their report is delivered
Message template
Hi [Name] - I turned [Event]'s exhibitor list into a QR stamp passport. Attendees scan at each booth, collect stamps, unlock a prize, and you get a per-stop scan report you can send each sponsor. Demo built from your booth list: [link]. $199 for this event, live in an hour. Want me to set it up?
30-day execution roadmap
Week 1 · Build & validate · 5 days
Lock scope, stand up the project
- Write the 7-feature MVP list and the do-not-build list.
- Buy the domain and create the Next.js repo.
- Deploy a shell to Vercel and create the Supabase project.
Deliverable: Live shell URL and scope doc.
Schema and organizer login
- Create tables for events, stops, attendees, stamps, orders.
- Add magic-link organizer auth.
- Seed one 8-stop test event.
Deliverable: Queryable test event in Postgres.
CSV in, QR codes out
- Build CSV import with per-row validation.
- Generate signed per-stop QR payloads and PNG downloads.
- Show validation errors inline.
Deliverable: 25 QR PNGs generated for a test event.
Print-ready output
- Build the A4/Letter poster template with logo and accent colour.
- Batch render all stops into one PDF.
- Print a test sheet at home and scan it.
Deliverable: Print-ready poster PDF per event.
Attendee side and dedupe
- Ship the mobile passport with stamp grid and progress bar.
- Build /api/scan with device-token duplicate blocking.
- Add the prize-unlock screen at threshold.
Deliverable: End-to-end scan working on a phone.
Week 2 · Launch & first sale · 7 days
Make it payable
- Wire Stripe Checkout at $199 and gate posters plus live trail.
- Add the $449 Season Pass product.
- Run a full dry run with a fake paid event and publish.
Deliverable: MVP live and taking payments.
Personalized proof for outreach
- Build 10 demo trails from publicly listed booth names.
- Capture poster, passport and sample report screenshots.
- Record one 90-second Loom.
Deliverable: 10 personalized demo packs.
First 35 touches
- Send 25 personalized emails to named organizers.
- Send 10 LinkedIn DMs to association directors.
- Log every send and reply in a sheet.
Deliverable: 35 touches out, tracker started.
Fill the pipeline
- Compile 50 events in the next 90 days and 25 merchant associations.
- Find a named contact for each.
- Build 10 more demo trails.
Deliverable: 75-row prospect list with contacts.
Second send, first follow-up
- Send batch 2 to 25 prospects.
- Follow up batch 1 with the sample per-stop report.
- Book calls only when asked.
Deliverable: 60 cumulative touches logged.
First collected payment
- Run reply calls and answer cost and setup objections.
- Send a Stripe payment link during the conversation.
- Push for a signed-up event this week.
Deliverable: First paid event or a dated commit.
Onboard the first buyer
- Upload their stops and branding, generate the kit.
- Email the print checklist and QR test steps.
- Keep onboarding under 30 minutes.
Deliverable: Live trail for the first customer.
Week 3 · Repeat & systematize · 8 days
The artifact sponsors read
- Finish per-stop CSV and PDF report with unique scans, completions, time-of-day.
- Add an event-level summary page.
- Test against the first live event.
Deliverable: Report export shipped.
More touches, first referral
- Send batch 3 to 25 prospects.
- Ask the first buyer for one peer referral.
- Post the build story on LinkedIn.
Deliverable: 25 new touches plus a referral ask.
Cut setup steps
- Review support messages and fix the top 3 issues.
- Add a scan-failure fallback page.
- Reduce the setup form to 5 fields.
Deliverable: Shorter setup flow.
Second purchase path
- Add the prize-draw randomiser and 3-trail allowance.
- Write a one-page $199 vs $449 comparison.
- Update checkout and email copy.
Deliverable: Season Pass sellable.
Shop-local campaigns
- Send 25 emails to merchant associations.
- Offer a two-week campaign trail instead of a single day.
- Build 5 association demo trails.
Deliverable: 25 association touches.
In-venue reliability
- Add 3 poster layouts and a table-tent size.
- Test QR scanning at 30cm and 1m from print.
- Document print settings for buyers.
Deliverable: Print kit v2.
Duplicate and offline handling
- Test two devices per attendee against the duplicate rule.
- Cache the passport page for weak Wi-Fi.
- Set up an uptime monitor on /api/scan.
Deliverable: Passport survives poor venue Wi-Fi.
Volume and public proof
- Send batch 4 to 25 prospects.
- Follow up every non-replier once.
- Publish an anonymised sample report as a public link.
Deliverable: Public sample report live.
Week 4 · Scale what works · 7 days
Deliver flawlessly
- Support any live customer event on one shared channel.
- Fix scan issues within the hour.
- Request a written quote if the buyer offers one.
Deliverable: Event completed and report delivered.
Self-serve demo
- Turn the completed event into an anonymised walkthrough.
- Add a demo trail anyone can scan.
- Update the landing page with the walkthrough.
Deliverable: Landing page with a live demo trail.
Volume plus second offer
- Send batch 5 to 25 prospects with the demo link.
- Re-offer warm replies the $449 Season Pass.
- Post in two event-planner communities.
Deliverable: 25 touches and 2 community posts.
Find the winning angle
- Offer 5 prospects a $199 pilot for a same-week event.
- Compare reply rate on sponsor-report angle vs print-materials angle.
- Keep only the winning angle.
Deliverable: Winning message angle documented.
Reduce refund risk
- Publish refund and event-cancellation policy pages.
- Add invoice fields and Stripe receipts.
- Schedule nightly database backups.
Deliverable: Policy pages and backups live.
Referral compounding
- Send batch 6 to 25 prospects.
- Ask every paying customer for one referral.
- Log all replies for the final push.
Deliverable: Referral requests sent to all buyers.
Close the loop on live events
- Generate and send reports for every completed event this week.
- Fix any data gaps found in those reports.
- Confirm each customer's 30-day hosting end date.
Deliverable: Reports delivered to every live customer.
Days 29-30 · Consolidate · 3 days
Convert warm pipeline
- Follow up every warm lead with a Dec 15 deadline offer.
- Call anyone who opened three or more times.
- Send payment links directly.
Deliverable: Final pipeline worked end to end.
Verified numbers
- Confirm all payments settled in the Stripe account connected to TrustMRR.
- Match each sale to a delivered event.
- Document any refunds.
Deliverable: Reconciled revenue log.
Decide what happens next
- Write what sold, what was ignored and setup time per event.
- Decide keep, iterate or stop for January.
- Publish the numbers as projections only.
Deliverable: Decision memo.
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 case: 3 paid events from 75 personalized touches; reply rate near 5%.
- Base case: 10 paid events, all at the $199 Single-Event Passport.
- Upside case: 24 paid events, 20 at $199 and 4 at the $449 Season Pass, blended ARPU $240.67.
- Stripe assumed at 2.9% + $0.30 per transaction; payment fees computed on that basis.
- No paid marketing in this window; ad_spend is $0 in every case because the channel is organic outreach.
- Free demo trails are built from publicly listed booth and merchant names; no customer, logo or revenue is claimed before a payment clears.
- Operating costs cover Vercel, Supabase, domain, Resend and poster PDF rendering only; founder time is not counted.
- Passport completion and scan volume affect perceived value but not price in this window.
- All figures are projections, not verified revenue or traction.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $18
- Paid marketing
- $0
- Hackathon profit
- $579
- Operating costs
- $25
- Business profit
- $554
Base case
10 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $61
- Paid marketing
- $0
- Hackathon profit
- $1,929
- Operating costs
- $45
- Business profit
- $1,884
Optimistic
24 customers- Refunds
- $199
- Chargebacks
- $0
- Payment fees
- $175
- Paid marketing
- $0
- Hackathon profit
- $5,402
- Operating costs
- $110
- Business profit
- $5,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.
All scenarios are projections built from the stated assumptions. They are not verified revenue, customers or traction.
Main risks and validation experiments
Risk 1Cold outreach reply rate under 5%, yielding fewer than three sales.
Build a real demo trail from each prospect's public booth list so the first message contains their own event, and follow up once with a sample report.
Send 50 personalized emails by day 10 and count replies within 72 hours.
If fewer than 2 replies come from the first 50 sends, rewrite the angle around sponsor reporting and re-test with 25 sends before building anything else.
Risk 2Nov 16 to Dec 16 sits between event seasons, pushing real event dates past the contest window.
Target holiday shop-local campaigns and January trade shows, and collect payment now for a trail that goes live later.
For 75 prospects, record whether a public event date falls before Feb 1.
If fewer than 10 of 75 prospects have an event before Feb 1, pivot all outreach to merchant associations running December holiday campaigns.
Risk 3Weak attendee identity produces duplicate stamps and undermines the per-stop report.
Device token in local storage plus server-side uniqueness per stop, with an organizer override for shared devices.
Run 20 scans from two phones against one stop on day 19 and count duplicates.
If duplicates exceed 10% of scans, add an optional one-field email gate before launch and re-test.
Risk 4Poor venue Wi-Fi causes scan failures and refund requests on event day.
Cache the passport page, keep scan payloads under 1KB, show a retry state that never loses the stamp.
Throttle the connection to slow 3G and run a 25-stop dry run before day 6 launch.
If scan failure rate exceeds 5% under throttle, add a numeric backup code printed under each QR.
Risk 5Organizers decide a paper card plus Google Forms is good enough and never pay.
Lead every message with the sponsor-facing report, since the report is the thing paper cannot produce.
In 10 reply conversations, ask directly what they currently hand sponsors after the event.
If 8 of 10 say their current proof is sufficient and none ask for the report, reposition toward associations with board reporting duties.
Risk 6Live-event support requests break the no-operations constraint.
Publish a print and scan FAQ, use five canned responses, and state a support window instead of promising 24/7.
Log every support message in the first two live events and count them per event.
If a single event generates more than five support threads, add an in-product self-test and a paid setup call.
Hour-by-hour: the first 24 hours
Hours 1-2
- Write the 7-feature MVP list and the do-not-build list.
- Register the domain and create the Next.js repo.
- Create the Supabase project and a Stripe account in test mode.
Output: Scope doc plus repo and cloud accounts.
Hours 3-5
- Model events, stops, attendees, stamps and orders.
- Deploy the shell app to Vercel.
- Seed one 8-stop test event.
Output: Deployed shell with a seeded test event.
Hours 6-8
- Build CSV import with row validation.
- Generate signed per-stop QR PNGs for the test event.
- Scan one QR on a phone and confirm the stamp is written.
Output: Working import-to-scan loop.
Hours 9-11
- Start the prospect list with 25 named event organizers.
- Record which have a public event date before Feb 1.
- Note booth or merchant names for demo trails.
Output: 25-row prospect list with contacts and dates.
Hours 12-14
- Build the first poster PDF template with logo and accent colour.
- Render all 8 test stops into one PDF.
- Print one page and scan it successfully.
Output: Print-ready poster PDF v1 plus a scannable printout.
Full 30-day launch report
Read the full generated report
StampTrail Passport - 30-Day Launch Report
1. Product opportunity and positioning
StampTrail Passport sells to one person: the marketing manager, sponsorship lead, or merchant-association director who owns an event with 100-1,000 attendees and a fixed list of booths or shop stops. That person has usually already sold sponsorship packages against a promise of foot traffic and now has to show something countable after the doors close. The realistic alternatives are paper stamp cards (lost, uncountable, no report), a Google Form per booth (no passport experience, messy per-booth data), or a custom app quote (weeks of lead time, thousands of dollars).
Why this buyer fits a solo founder in 30 days: the organizer controls every scan point, so there is no two-sided cold start. They hold an event or sponsorship budget line, so $199 does not need procurement or legal review. And they have a hard date, which turns a nice-to-have into a deadline-driven purchase. No marketplace, no app store, no hardware, no venue integration.
The product is deliberately narrower than the location-social idea that inspired it. There is no friend graph, no public feed, no consumer sign-up funnel. The check-in mechanic is reused as a business instrument: the QR scan is the unit of proof, and the deliverable is a poster kit plus a report a sponsor can read. The economic buyer is the organizer, not the attendee.
JEV scored this concept 62.2/100 (band C, confidence 0.75). It is strongest where a 30-day contest needs strength: speed to first revenue (8.18 normalized) and solo build feasibility (7.69). It is weakest on market demand (4.78) and monetization potential (4.98). This plan answers both. Demand risk is handled by narrowing the trigger to events inside a 30-90 day window and by leading every message with the sponsor report rather than the software. Monetization risk is handled by making the $449 Season Pass a first-class offer from day 16, so one satisfied buyer can pay twice inside the same quarter.
The sentence to use everywhere: 'I turned your event floor plan into a QR stamp passport. Attendees scan at each booth, and you hand each sponsor a per-stop scan report. $199 for this event, live in an hour.'
2. Smallest sellable MVP
Seven features, nothing else: CSV import of stops (booth name, stop code, prize threshold); a QR PNG plus a print-ready A4/Letter poster PDF per stop; a mobile web passport with stamp grid, progress bar and prize unlock; a scan endpoint that records stop and timestamp and blocks duplicates per attendee; an organizer dashboard with live per-stop counts and CSV/PDF export; Stripe Checkout that gates poster generation and the live trail; and branding fields for logo, accent colour and prize text.
Explicitly not built: native apps, GPS or geofencing, agency or white-label portal, prize fulfilment or shipping, a public trail directory, and any CRM or email automation. Each of those adds weeks without adding a first sale.
Demo flow: the organizer pays, uploads 25 booth names, downloads one poster PDF, prints it, attendees scan and collect stamps, the dashboard counts per stop live, and the organizer exports the sponsor report.
3. Technical implementation plan
One Next.js app on Vercel with Supabase Postgres, magic-link organizer auth, Stripe Checkout, the qrcode library, and @react-pdf/renderer. Three surfaces: the auth-gated dashboard, the public passport at /t/[slug], and /api/scan. Each poster QR encodes a signed per-stop URL. The passport keeps a device token in local storage; the scan endpoint rejects a second stamp for the same device and stop and writes idempotently. A paid order flips the event to live and unlocks poster rendering; unpaid events stay in draft and cannot be scanned.
Build order: shell and schema (days 1-2), import and QR (day 3), poster PDF (day 4), passport and scan endpoint (day 5), paywall and full dry run (day 6). The hardest risk is duplicate or lost stamps under weak venue Wi-Fi, because that corrupts the report the buyer paid for. Cache the passport page, keep scan payloads under 1KB, and add a numeric backup code under each QR if throttled testing shows more than 5% failures.
4. Pricing and monetization
Two one-time offers. Single-Event Passport at $199: one trail up to 25 stops, poster PDFs, live passport, per-stop report, 30-day hosting. Season Pass at $449: three trails within 90 days, per-trail branding, prize-draw randomiser, reports per event. No subscription, because a solo founder cannot promise recurring support and event buyers prefer a fixed line item. The Season Pass exists to create a second sale from the same relationship at the moment the first report proves useful.
5. First-customer acquisition
One channel: personalized LinkedIn and email outreach to 75 named organizers and association directors. Each receives a demo trail built from 3-5 of their own publicly listed booth or merchant names, plus a poster screenshot. Day 7 builds 10 demo packs, day 8 sends 25 emails and 10 DMs, day 9 fills the list to 75, day 10 sends batch 2 and follows up batch 1 with a sample report. Calls happen only when asked. Every buyer gets one referral ask after their report is delivered.
6. 30-day execution roadmap
Days 1-6 (Nov 16-21): build and launch the paid MVP. Days 7-14 (Nov 22-29): demo assets, three outreach batches, first sale target day 11, onboard the first buyer on day 12, ship the sponsor report on day 13. Days 15-21 (Nov 30-Dec 6): remove setup friction, launch Season Pass, switch to merchant associations, harden print and scan reliability, support the first live event. Days 22-28 (Dec 7-13): publish a self-serve demo trail, run batches 5 and 6, test message angles, harden policies and backups, push the close. Days 29-30 (Dec 14-15): reconcile payments against delivered events and write the keep/iterate/stop memo. Full day-by-day tasks are in the roadmap JSON.
7. Revenue and profit scenarios
All three are projections, not verified revenue or traction. Conservative: 3 customers at $199 = $597 gross, zero refunds and chargebacks, $18 payment fees, $0 ad spend, $25 operating cost, so $579 hackathon profit and $554 business profit. Base: 10 customers at $199 = $1,990 gross, $61 fees, $45 operating cost, so $1,929 hackathon profit and $1,884 business profit. Upside: 24 customers with a blended $240.67 ARPU (20 single, 4 Season Pass) = $5,776 gross, $199 refunds, $175 fees, $110 operating cost, so $5,402 hackathon profit and $5,292 business profit. Payment fees assume Stripe at 2.9% + $0.30 per transaction. Ad spend is zero in every case because the channel is organic outreach. Hosting and infrastructure are not deducted from hackathon profit by rule, but are deducted from business profit.
8. Main risks and validation experiments
Five tests, each cheap and dated. First, outreach reply rate: 50 sends by day 10, and if fewer than 2 replies arrive, rewrite the angle before building more. Second, event-season timing: check whether a public event date falls before Feb 1 for all 75 prospects; if fewer than 10 do, pivot to December shop-local campaigns run by associations. Third, duplicate stamps: 20 scans from two phones on day 19; above 10% duplicates means adding an optional email gate. Fourth, venue connectivity: throttle to slow 3G and run a 25-stop dry run before launch; above 5% failures means printing numeric backup codes. Fifth, the paper-card objection: ask 10 replying organizers what they currently hand sponsors; if 8 say it is sufficient, reposition to associations with board reporting duties. A sixth operational check: count support threads per live event, and above five per event add a paid setup call.
9. First 24-hour action plan
Hours 1-2: write the MVP and do-not-build lists, register the domain, create the repo, Supabase project and Stripe test account. Hours 3-5: model the five tables, deploy the shell, seed an 8-stop test event. Hours 6-8: CSV import plus signed QR generation, then scan one QR on a phone and confirm the stamp writes. Hours 9-11: build a 25-row prospect list with event dates and real booth names. Hours 12-14: render the first poster PDF with logo and accent colour, print one page, and scan it. By hour 14 the founder has a working import-to-scan loop, a printed QR, and a prospect list - the three things the next 29 days depend on.
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 →Unattributed 360
A link-based anonymous 360 collection tool that turns raw peer feedback into a client-ready, quote-safe PDF report for independent executive coaches.
Candor Digest
Candor Digest turns anonymous cohort questions into a moderated, shareable Q&A digest for cohort-based course creators.
Reaction Mint
Turns a community's mascot and inside jokes into a ready-to-install pack of Discord emoji, Twitch emotes and stickers, delivered as spec-perfect transparent PNG files within 24 hours, for community owners who cannot draw.