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

EventSheet

Turn your event schedule spreadsheet into a branded mobile app in minutes, no coding required.

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.41/10
MVP build (solo)
5 days
Launch price
$199
Sales to $1,000 revenue
6 customers
First paying customer
Direct LinkedIn outreach to organizers who publicly announced an upcoming event in the last 14 days.
Who pays

Event organizers at small to mid-sized organizations (10-500 attendees) running a conference, festival or meetup in the next 30-60 days who currently publish their schedule as a PDF or spreadsheet.

Biggest execution risk

Monetization potential 4.3/10

Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 9; 6 sales at $199 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.4/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
$199
Solo build
5 days
30d base revenue
$1,791
30d hackathon profit
$1,728
Section 1 of 8

Product opportunity and positioning

Target customer

Event organizers at small to mid-sized organizations (10-500 attendees) running a conference, festival or meetup in the next 30-60 days who currently publish their schedule as a PDF or spreadsheet.

Why now

Event announcements are public weeks before the app is needed, so a solo founder can find buyers who have a dated deadline and an existing event budget, and the deliverable is a single link that can be shipped in minutes.

Problem

Attendees expect a mobile schedule with speakers, favorites and last-minute updates, but building an app means hiring a developer or buying an event platform that takes weeks to configure and costs thousands.

Solution

The organizer uploads a schedule CSV or connects a Google Sheet, maps columns once, picks a theme and brand color, and EventSheet generates a hosted PWA on a subdomain with schedule, speaker bios, local favorites, push notifications and basic analytics.

Differentiation · Not a drag-and-drop builder and not a native app platform: templates are fixed, output is a PWA, and the purchase is one decision made by one organizer without procurement.

1. Product opportunity and positioning

Event organizers at small and mid-sized events already own the hardest asset: a finished schedule in a spreadsheet. What they lack is a mobile surface. Two weeks out, attendees ask "is there an app?", and the organizer has three bad answers: email a PDF, buy an event-app platform with a four-week onboarding, or find someone to build one.

EventSheet sells one artifact: a link. Upload the schedule CSV or point at a Google Sheet, map the columns once, pick a theme, and a branded Progressive Web App appears at yourevent.eventsheet.app with sessions, speakers, favorites and push notifications. Price: $199 one-time, delivered in minutes, hosted for three months.

The scored concept sits at 64.1/100 (JEV band C, confidence 0.72). The profile is honest about what this is. Speed to first revenue scores 8.43 and solo build feasibility 7.46, because a PWA generator is rendering code plus a Stripe link. Monetization potential scores 4.34, the harshest number, because $199 is charged once. This plan does not argue with that score. It prices an add-on at the moment of purchase ($99 custom domain) and builds a repeat path (next meetup, next year, multi-event organizer) instead of pretending the product is recurring software. The upside scenario is deliberately capped: 20 sales, not 50.

Differentiation is narrowness. EventSheet is not a builder, because templates are fixed. It is not a native app, because App Store review would blow the deadline. It is not a ticketing tool. The real competitor is a PDF attachment and a volunteer editing it by hand. Against that, a live link that re-syncs from the sheet is a clear, explainable win, and it is a decision one organizer can make alone in one message.

The acquisition logic follows from seasonality. Organizers announce events publicly weeks before they need an app, and those announcements are a dated lead list. That is why the channel is direct LinkedIn outreach, not SEO, ads or a marketplace. The founder is not building demand; he is intercepting an announcement that already happened.

The honest constraint is time. Thirty days, one person, no audience. The plan therefore spends four days building, two days assembling demos, and the remaining twenty-four days selling, with a hard gate: if the product cannot take a real card and generate a real subdomain by day 5, scope gets cut, not extended.

Section 2 of 8

Smallest sellable MVP

A Stripe-paid flow that accepts a schedule CSV, generates a themed PWA on a subdomain, and sends the buyer a shareable link within five minutes of purchase.

Must-have features

  • CSV and Google Sheet importer with column mapping for title, start, end, room, track, speaker name and bio
  • Four fixed themes with logo upload and brand color
  • Generated PWA pages: schedule by day, session detail, speaker list, local-storage favorites
  • Wildcard subdomain provisioning with SSL and an admin page to re-sync the sheet
  • OneSignal web push opt-in and a single broadcast composer
  • Stripe Checkout for $199 with webhook-triggered provisioning
  • Buyer dashboard: page views, favorites, push subscriber count
  • Refund promise: live within 24 hours of CSV upload or money back

Explicitly out of scope

  • Native iOS/Android builds and app store submission
  • Drag-and-drop or custom page builder
  • Ticketing, payments or attendee registration
  • Integrations beyond CSV and Google Sheets
  • Multi-event management and team roles
  • Custom code injection or API access
  • 24/7 support or a support SLA

Demo flow (what the buyer sees)

  1. Organizer opens eventsheet.app and pays $199 via Stripe Checkout.
  2. Stripe webhook creates an event record and reserves a subdomain.
  3. Organizer uploads a CSV; the importer suggests column mappings for confirmation.
  4. Organizer picks a theme, uploads a logo and sets a brand color.
  5. Generator renders the static PWA and deploys it to eventname.eventsheet.app.
  6. Organizer receives the live link and a 20-second walkthrough email.
  7. Organizer shares the link; attendees install, favorite sessions and opt in to push.
  8. Organizer edits the sheet and clicks re-sync from the admin page.
Build plan

Technical implementation plan

Stack

Next.js 15 App Router on VercelVercel wildcard domain for *.eventsheet.appSupabase Postgres, Auth and StorageStripe Checkout and webhooksOneSignal web pushTailwind CSSOpenAI gpt-4o-mini for column mapping onlyResend for transactional email

Architecture

A single Next.js app serves the marketing page, checkout, buyer dashboard and every generated PWA. Subdomain requests are rewritten by middleware to a catch-all route that looks up the event by hostname, reads a stored JSON render schema from Supabase, and renders the attendee pages from that schema so no per-event build is needed. The importer parses CSV or Google Sheets, uses one LLM call to map unknown headers, and writes normalized sessions and speakers to Postgres plus a versioned schema row. Stripe webhooks mark an order paid and provision the event record and subdomain. OneSignal is configured per event via a subdomain-scoped service worker.

Build steps

  1. Create the repo, Supabase schema (events, sessions, speakers, orders, push_subs) and deploy an empty Next.js app to Vercel.
  2. Add wildcard domain and middleware rewriting so any subdomain resolves to a render route with a placeholder event.
  3. Build the CSV parser and a mapping screen that pre-fills detected columns with an LLM fallback.
  4. Build the render schema and four theme components for schedule, session, speaker and favorites pages.
  5. Add logo upload to Supabase Storage and brand color theming via CSS variables.
  6. Add the admin page with re-sync, session edit and preview link.
  7. Wire Stripe Checkout, price lookup, webhook signature check and order-to-provisioning.
  8. Add OneSignal opt-in and the broadcast composer for paid events.
  9. Add analytics counters for views, favorites and push subscribers.
  10. Add the refund-and-rebuild path: re-upload CSV replaces the schema atomically.
  11. Load-test with a synthetic 300-session schedule and verify the subdomain renders under two seconds.
  12. Write a buyer onboarding email and a one-page organizer help doc.

AI components

  • One gpt-4o-mini call per import to map unrecognized CSV headers to the canonical schema
  • Optional cleanup pass that normalizes speaker names and splits combined name/company fields
Hardest technical risk: Wildcard subdomain SSL plus correct hostname-to-event routing on Vercel; if that takes more than a day, fall back to a path-based URL (eventsheet.app/e/eventname) and ship the custom domain later.
Section 3 of 8

Pricing and monetization

Event App

Entry offer
$199 one-time

For Organizer of a single event under 500 attendees

  • PWA generation from CSV or Google Sheet
  • Hosted subdomain with SSL
  • Push notifications
  • Favorites and speaker pages
  • 3 months hosting
  • Basic analytics

Custom Domain Add-on

$99 one-time

For Organizer who wants the app on their own domain

  • Custom domain configuration
  • SSL certificate
  • 1 year domain registration
  • Same 3 months of hosting

Model: One-time $199 launch fee per event, with a $99 optional custom domain add-on at checkout, and a discounted $149 deadline offer used only on follow-ups.

First revenue offer: I built a working mobile version of [Event]'s schedule from your public programme. Here is the live link. It is $199 to put it on your own subdomain with push notifications and favorites, live within 24 hours of your CSV, or you get a full refund.

Expected ACV: $199

Upsell path: $99 custom domain at checkout, then a $299 three-event bundle offered to organizers who run recurring meetups, then a $149 renewal when the next event is announced.

Target customers
50
Revenue model
$9,950
Costs
$100
Profit model
$9,850
Section 4 of 8

First-customer acquisition

Primary channel

Direct LinkedIn outreach to organizers who publicly announced an upcoming event in the last 14 days.

Where to find them

  • LinkedIn posts containing 'registration is open', 'excited to announce' plus conference, summit, meetup or festival
  • LinkedIn event pages with a listed organizer and a date 3-8 weeks out
  • Event planner and community manager groups on LinkedIn and Facebook
  • Organizers of recurring monthly meetups listed on public meetup pages
  • Conference websites published with a public schedule page

Exact outreach motions

  • Send a first message with no link: name the event, name one session from their public schedule, ask if they want a mobile version.
  • Build the mockup before replying, then send the live subdomain link as the second message.
  • Offer a 10-minute screen-share to generate the app live from their own CSV.
  • Follow up after 48 hours with a $149 offer that expires in 48 hours.
  • Post the demo link in three event planner communities with a one-line description and no pitch.
  • Ask every buyer for one organizer referral in exchange for a $50 credit toward a second event.

Message template

Hi [Name] - I saw you're running [Event] in [Month]. I make a mobile schedule app from your existing spreadsheet: attendees get sessions, speakers, favorites and push updates from a link, no app store. Want me to build a free mockup from your public programme so you can see it with your own branding? Takes me about 10 minutes.
Week-one goal: 80 qualified organizers logged with event name, date, size and post URL; 50 personalized messages sent; 8 replies; 3 live 10-minute builds; 1 paid order.
Section 5 of 8

30-day execution roadmap

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

Shipable skeleton

  • Create repo, Supabase schema and Vercel project.
  • Add wildcard domain and subdomain rewrite to a placeholder event.
  • Connect Stripe test keys and TrustMRR payment account.

Deliverable: Deployed skeleton rendering a placeholder event at any subdomain.

Day 2Import

CSV to structured data

  • Build CSV parser and column mapping screen.
  • Add one LLM call for unrecognized headers.
  • Test against three real public conference schedules.

Deliverable: Importer that turns three different CSV formats into normalized sessions.

Day 3Render

Attendee-facing PWA

  • Build four theme components and CSS variable theming.
  • Add schedule, session detail, speaker list and local favorites.
  • Add logo upload to storage.

Deliverable: Static PWA output for a 60-session sample event.

Day 4Delivery

Provisioning and push

  • Wire subdomain provisioning on event creation.
  • Add admin page with re-sync and preview.
  • Add OneSignal opt-in and broadcast composer.

Deliverable: End-to-end generated app on a live subdomain with working push.

Day 5CommerceMVP shipped

First real card

  • Switch Stripe to live mode with checkout and webhook provisioning.
  • Buy the product with a real card and time the delivery.
  • Write refund policy page and onboarding email.

Deliverable: A real $199 purchase that provisions an app unattended. MVP deadline.

Day 6Proof assets

Demos that sell

  • Generate three demo apps from public event schedules.
  • Record a 40-second Loom showing CSV to live link.
  • Write a one-page buyer overview PDF.

Deliverable: Three demo links, one Loom, one overview page.

Day 7Pipeline

Lead list

  • Build an 80-row outreach sheet from LinkedIn and event pages.
  • Score each lead by event date within 60 days.
  • Prepare two message variants for testing.

Deliverable: 80 qualified leads with event date, size and post URL.

Week 2 · Launch & first sale · 7 days
Day 8Outreach

First 25 messages

  • Send 25 personalized first messages with no link.
  • Log every reply and objection in the sheet.
  • Pre-build mockups for the 5 warmest leads.

Deliverable: 25 sends, 5 mockups ready, objection log started.

Day 9OutreachFirst sale target

Volume and conversations

  • Send 25 more personalized messages.
  • Reply to all responders within 60 minutes.
  • Book the first three 10-minute build calls.

Deliverable: 50 cumulative sends and 3 booked calls. First sale target.

Day 10Closing

Live builds

  • Run booked build calls and generate apps live.
  • Send $199 payment links immediately after each call.
  • Ask each caller for one organizer they know.

Deliverable: First paid order (target) and two referral names.

Day 11Follow-up

Recover non-responders

  • Send $149 48-hour offer to 25 non-responders.
  • Rebuild two mockups using logos from their sites.
  • Set up a simple payment-status tracker.

Deliverable: 25 follow-ups sent, 2 branded mockups delivered.

Day 12Communities

Organic second channel

  • Post the demo link in three event planner communities.
  • Answer every comment with a specific offer.
  • Measure referral traffic and replies.

Deliverable: Three live posts and a traffic baseline.

Day 13Product feedback

Fix what blocks purchase

  • Add the fifth theme and speaker photo support.
  • Fix the top three importer failures seen in calls.
  • Publish a changelog entry.

Deliverable: Deployed update with a short changelog.

Day 14Review

Kill or double

  • Compute reply rate and close rate per message variant.
  • Double down on the better variant and drop the other.
  • Refresh the lead sheet to 40 new warm leads.

Deliverable: Channel conversion numbers and a refreshed pipeline.

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

Reach 100 sends

  • Send 25 messages using the winning variant.
  • Target events happening in 2-4 weeks.
  • Book four calls for days 16-18.

Deliverable: 100 cumulative sends, 4 calls booked.

Day 16Monetization

Add-on revenue

  • Ship the $99 custom domain add-on end to end.
  • Add the add-on upsell to the post-purchase email.
  • Test the checkout flow once with a real card.

Deliverable: Working custom domain add-on purchase.

Day 17Proof

Social evidence

  • Ask two buyers for permission to show their app as an example.
  • Publish a short case note with the delivery time and outcome.
  • Add the examples to the outreach second message.

Deliverable: One permissioned example page.

Day 18Reliability

Push and mobile quirks

  • Test push opt-in on iOS Safari and Android Chrome.
  • Write a two-minute attendee install guide page.
  • Document known iOS push limits in the buyer email.

Deliverable: Tested push across platforms and a published install guide.

Day 19Repeat buyers

Recurring organizers

  • Message 15 recurring meetup organizers.
  • Offer the $299 three-event bundle.
  • Log which segment replies faster.

Deliverable: 15 bundle offers sent with segmented tracking.

Day 20Retention hook

Next event path

  • Add a renewal reminder field to the buyer dashboard.
  • Email existing buyers about the bundle.
  • Update pricing page with the bundle.

Deliverable: Bundle live on the site and offered to all buyers.

Day 21Review

Midpoint audit

  • Reconcile Stripe payouts against TrustMRR records.
  • Check refund window exposure on delivered apps.
  • Cut the weakest feature from the backlog.

Deliverable: Reconciled payment log and a pruned backlog.

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

Second cohort

  • Send 30 messages to newly announced events.
  • Rebuild the lead sheet with fresh posts only.
  • Book five calls.

Deliverable: 30 sends and 5 booked calls.

Day 23Funnel

Lower friction

  • Add a no-login CSV preview that renders a blurred schedule.
  • Add a one-field email capture before preview.
  • Wire preview leads into the follow-up list.

Deliverable: Live preview lead magnet capturing emails.

Day 24Visibility

Public launch post

  • Publish a build-and-launch post on LinkedIn and X with the demo link.
  • Reply to every comment the same day.
  • Send the post to 10 warm leads as a soft touch.

Deliverable: Two published launch posts and a comment log.

Day 25Conversion

Warm leads

  • Send 20 'your mockup is ready' messages.
  • Offer a 10-minute build to anyone who opens twice.
  • Close outstanding quotes.

Deliverable: 20 reactivation messages and closed quotes.

Day 26Buyer value

Analytics dashboard

  • Ship the buyer dashboard with views, favorites and subscribers.
  • Email all buyers a link to their numbers.
  • Use the numbers as a referral hook.

Deliverable: Buyer analytics live and announced to existing buyers.

Day 27Referrals

Second-order growth

  • Ask every buyer for one organizer referral.
  • Offer $50 credit per converted referral.
  • Track referrals in the order table.

Deliverable: Referral offer live and requested from all buyers.

Day 28Final push

Deadline urgency

  • Send 40 messages with the $149 48-hour offer.
  • Follow up every open conversation once.
  • Post a 'last week' reminder in the communities.

Deliverable: 40 sends plus a community reminder.

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

Collect before cutoff

  • Call or message every outstanding quote.
  • Ensure all payments settle before Dec 16 13:00 UTC.
  • Confirm every paid app is live to avoid refunds.

Deliverable: All open deals closed or explicitly lost.

Day 30Verify

Clean finish

  • Freeze features and stop deploys.
  • Export the Stripe revenue and refund report for TrustMRR.
  • Write a one-page post-mortem of what converted.

Deliverable: Verified revenue export and 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

  • Conservative: 3 one-time sales at $199 from roughly 120 outreach messages (about 2.5% close) - projection only.
  • Base: 9 sales at $199 average, no add-on attach - projection only.
  • Upside: 20 sales at a blended $214, assuming about 15% take the $99 custom domain add-on and a few $149 deadline discounts - projection only.
  • Payment fees assume Stripe at 2.9% plus $0.30 per charge, roughly 3.5% blended - projection only.
  • Refunds modeled at zero in conservative and base, one sale in upside; chargebacks near zero with default Stripe Radar rules.
  • No paid marketing in conservative or base; upside includes $120 of sponsored newsletter placement.
  • Operating costs cover Vercel Pro, domain, Supabase, OneSignal and Resend plus per-app LLM mapping calls, ranging from $25 to $120.
  • All figures are hypotheses, not verified revenue, customers or traction.

Conservative

3 customers
$597
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$21
Paid marketing
$0
Hackathon profit
$576
Operating costs
$25
Business profit
$551

Base case

9 customers
$1,791
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$63
Paid marketing
$0
Hackathon profit
$1,728
Operating costs
$55
Business profit
$1,673

Optimistic

20 customers
$4,280
collected revenue · avg payment $214
Refunds
$199
Chargebacks
$0
Payment fees
$150
Paid marketing
$120
Hackathon profit
$3,811
Operating costs
$120
Business profit
$3,691

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,791
Payment fees (3.9%)
$70
Paid marketing
$0
Hackathon profit
$1,721
Business profit
$1,666

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

All scenarios are projections built from stated assumptions, not verified revenue, existing customers or real traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Organizers reject a PWA as not a real app and insist on App Store listings.

Mitigation

Frame the product as an attendee web guide with install prompts and push, never as an app store app; mention the five-minute delivery first.

Validation experiment

Send 25 first messages and count how many raise 'app store' unprompted.

Kill criteria

If more than 40% of 20 replies say a store listing is required, reposition the offer around live updates and stop selling against native apps.

Risk 2LinkedIn outreach is throttled or read as spam, producing near-zero replies.

Mitigation

Cap at 25 messages per day, personalize the first line with a real session name, and send no link in the first message.

Validation experiment

A/B 25 messages with a link against 25 without, comparing reply rate.

Kill criteria

If reply rate stays under 5% after 100 sends, move the same message to email addresses published on event websites before changing price.

Risk 3CSV formats vary so widely that every order needs manual fixing, breaking the no-support promise.

Mitigation

Limit the schema to seven canonical columns, add an LLM mapping fallback, and expose an editable mapping screen so the buyer fixes it without the founder.

Validation experiment

Run ten real public schedules through the importer and count manual interventions per file.

Kill criteria

If more than 30% of files need founder intervention after the mapping screen ships, drop to a fixed template and accept only the standard layout.

Risk 4Zero paid orders by day 14, leaving too little time to reach any revenue before the December 16 cutoff.

Mitigation

Pre-sell at $149 with a 24-hour delivery guarantee from day 11 so cash arrives before the product is fully polished.

Validation experiment

Offer the $149 pre-sale to the 25 warmest leads on day 11 and track payment link clicks.

Kill criteria

If there are no paid orders by day 14, cut to one theme, lower the price to $99 and test willingness to pay with ten fresh leads.

Risk 5iOS push notifications fail or need home-screen installation, so the flagship feature disappoints buyers after payment.

Mitigation

Test on iOS Safari and Android Chrome before day 18, publish an install guide, and state the limit in the buyer email.

Validation experiment

Send one broadcast to a test device on each platform and measure delivery.

Kill criteria

If iOS delivery cannot be demonstrated reliably, remove push from the headline offer and lead with favorites and live schedule updates.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register eventsheet.app and create the Vercel project.
  • Create the Supabase project and write the events, sessions, speakers, orders and push_subs tables.
  • Connect the payment account to TrustMRR before any charge exists.

Output: Domain, deployed empty app and schema.

Hours 3-5

  • Add wildcard domain and the middleware rewrite.
  • Render a hardcoded placeholder event on any subdomain.
  • Verify SSL on a test subdomain.

Output: Working subdomain routing proof.

Hours 6-8

  • Write the CSV parser for the seven canonical columns.
  • Build the mapping screen with auto-detection.
  • Import one real public conference schedule.

Output: Importer producing normalized session rows.

Hours 9-12

  • Build the schedule and session detail views with Tailwind.
  • Add local-storage favorites.
  • Deploy and open the result on a phone.

Output: A viewable attendee schedule page on a live subdomain.

Hours 13-16

  • List the first 20 target organizers with event dates and post URLs.
  • Draft the two message variants.
  • Write the refund and delivery promise copy.

Output: 20-row lead sheet, two messages, one promise statement.

Complete report

Full 30-day launch report

Read the full generated report

1. Product opportunity and positioning

Event organizers at small and mid-sized events already own the hardest asset: a finished schedule in a spreadsheet. What they lack is a mobile surface. Two weeks out, attendees ask whether there is an app, and the organizer has three bad answers: email a PDF, buy an event platform with a four-week onboarding, or find someone to build one.

EventSheet sells one artifact: a link. Upload the schedule CSV or point at a Google Sheet, map the columns once, pick a theme, and a branded Progressive Web App appears at yourevent.eventsheet.app with sessions, speakers, favorites and push notifications. Price: $199 one-time, delivered in minutes, hosted for three months.

The scored concept sits at 64.1/100, JEV band C, confidence 0.72. The profile is honest about what this is. Speed to first revenue scores 8.43 and solo build feasibility 7.46, because a PWA generator is rendering code plus a Stripe link. Monetization potential scores 4.34, the harshest number, because $199 is charged once. This plan does not argue with that score. It prices an add-on at the moment of purchase and builds a repeat path across events instead of pretending the product is recurring software. The upside case is deliberately capped at 20 sales.

Differentiation is narrowness. EventSheet is not a builder, because templates are fixed. It is not a native app, because store review would blow the deadline. The real competitor is a PDF attachment and a volunteer editing it by hand. Against that, a link that re-syncs from the sheet is a clear, explainable win, and one organizer can approve it alone in one message.

The acquisition logic follows from seasonality. Organizers announce events publicly weeks before they need an app, so the lead list is dated and public. That is why the channel is direct LinkedIn outreach rather than SEO, ads or a marketplace: the founder intercepts an announcement that already happened.

2. Smallest sellable MVP

The sellable unit is not a platform, it is a transaction: pay $199, upload a spreadsheet, receive a live link. Everything in the build serves that one loop. Seven canonical columns, four fixed themes, favorites stored in the browser, one push composer, a subdomain, and a buyer dashboard showing views, favorites and subscribers. The admin page lets the organizer re-sync the sheet after an edit, which is the single most requested feature in event software and the cheapest to build.

The refund promise is part of the MVP, not a policy afterthought: live within 24 hours of receiving the CSV or the money comes back. It converts the buyer's only real risk, the deadline, into the founder's risk, and it costs nothing when the generator works.

Explicitly excluded: native builds, store submission, drag-and-drop editing, ticketing, registration, custom code and 24/7 support. Each of those either adds weeks of work or adds an obligation a solo founder cannot meet during a 30-day sprint.

3. Technical implementation plan

One Next.js application on Vercel does everything: marketing page, Stripe checkout, buyer dashboard and every generated app. A middleware rewrite sends any subdomain request to a catch-all route that looks up the event by hostname, reads a stored JSON render schema from Supabase, and renders attendee pages from that schema. No per-event build pipeline, no container per customer, no deploy step on purchase.

The importer parses CSV or Google Sheets, maps known headers, and makes exactly one LLM call to interpret unknown ones. The mapping screen is editable, so a wrong guess costs the buyer ten seconds rather than a support ticket. Stripe webhooks flip an order to paid and provision the event and subdomain. OneSignal handles push with a subdomain-scoped service worker. Resend sends the onboarding link.

The hardest technical risk is wildcard subdomain SSL and hostname routing on Vercel. If that is not working by the end of day one, the fallback is path-based URLs, and the custom domain add-on ships later. Everything else is rendering code with well-known failure modes.

4. Pricing and monetization

$199 one-time for the event app, $99 for a custom domain, $149 as a deadline discount used only on follow-ups. The custom domain add-on exists because it is the one upsell a conference organizer genuinely wants and it lifts blended revenue without adding delivery work.

This is not subscription pricing and should not be sold as such. The repeat path is the next event: recurring meetup organizers get a $299 three-event bundle, and single-event buyers get a renewal email when their next announcement appears. With a JEV monetization score of 4.34, the right move is to maximize revenue per closed deal, not to invent retention claims.

5. First-customer acquisition

The channel is LinkedIn outreach to organizers who announced an event in the last 14 days. The sequence is fixed: a first message with no link that names a real session from their public programme, a second message carrying a pre-built mockup on a live subdomain, an offer to build live on a 10-minute screen share, and a $149 48-hour follow-up.

Targets: 120 messages over three weeks, roughly 15% reply rate, three to five live builds, and two to three closed sales on the conservative line. Supporting activity is posting the demo link in three event planner communities and asking every buyer for one referral in exchange for a $50 credit. There is no paid acquisition in the base case.

6. Thirty-day execution roadmap

Days 1-5 are build and commerce, ending with a real card purchase that provisions an app unattended. Days 6-7 produce three demo apps and a Loom. Days 8-14 are the first 50 outreach messages, the first live builds and the first closed deal, targeted for day 9. Days 15-21 add the custom domain add-on, permissioned examples, push reliability testing and the three-event bundle. Days 22-28 push a second and third outreach cohort, ship a lead-capture preview, add buyer analytics and run referrals. Days 29-30 freeze the product, close open quotes and export a clean revenue report before the December 16 13:00 UTC cutoff.

The gate is day 5. If a purchase cannot provision an app by then, scope is cut, not the date. The second gate is day 14: no paid order means repricing to $99 and testing with ten fresh leads.

7. Revenue and profit scenarios

Conservative: 3 sales at $199, $597 gross. Base: 9 sales at $199, $1,791 gross. Upside: 20 sales at a blended $214 including add-ons, $4,280 gross. Fees assume about 3.5% blended with Stripe. Ad spend is zero in both lower cases and $120 in the upside case.

Two numbers matter and they are different. Hackathon profit is collected revenue minus refunds, chargebacks, processing fees and paid marketing, and that is the number the contest ranks. Business profit subtracts hosting and delivery costs as well, which stay between $25 and $120 because the stack is serverless and the only inference cost is one mapping call per import.

Every figure here is a projection built from the stated assumptions. It is not verified revenue and it does not describe existing customers.

8. Main risks and validation experiments

The five risks worth testing this month are: buyers rejecting a PWA as not a real app, LinkedIn throttling outreach, CSV variance forcing manual work, zero sales by day 14, and iOS push failing after payment. Each has a cheap test in week two and an explicit kill rule. The two that would actually end the plan are the sales risk and the CSV risk, so both are tested before day 14 and both have a fallback that keeps the product sellable at a lower price.

9. First 24-hour action plan

The first 24 hours produce artifacts, not intentions. Hours 1-2: domain, Vercel project, Supabase schema and the TrustMRR payment connection, before any charge exists. Hours 3-5: wildcard routing rendering a placeholder event on a live subdomain with valid SSL. Hours 6-8: a CSV importer that normalizes a real public conference schedule. Hours 9-12: schedule and session views with favorites, opened on a phone. Hours 13-16: a 20-row lead sheet with event dates, two outreach message variants and the written delivery-and-refund promise.

By the end of day one the founder should be able to show a stranger a link that looks like a real event app, which is the only asset needed to start the outreach clock on day eight.

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 →