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

Tonight Page

A hosted, auto-expiring deal page plus WhatsApp/Instagram post pack that lets an independent inn turn tonight's empty rooms into direct bookings from its own past guests, with zero OTA commission.

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.

Promising6.54/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Personalised cold email to independent innkeepers found on Google Maps, where every email links to a Tonight Page already built for that specific property.
Who pays

Owner or front-desk manager of an independent inn, B&B, guesthouse or boutique hotel with 5-40 rooms in the UK, US, Ireland, Australia or coastal India who handles last-minute inventory manually today.

Biggest execution risk

Monetization potential 5.1/10

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

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

0/10
Entry price
$99
Solo build
5 days
30d base revenue
$1,341
30d hackathon profit
$1,200
Section 1 of 8

Product opportunity and positioning

Target customer

Owner or front-desk manager of an independent inn, B&B, guesthouse or boutique hotel with 5-40 rooms in the UK, US, Ireland, Australia or coastal India who handles last-minute inventory manually today.

Why now

A solo founder can ship this in five days on managed services, and the buyer approves $99 without procurement because it costs less than the commission on one weekend booking.

Problem

Rooms unsold at 5pm are worth zero at midnight, and the only fast lever is discounting on Booking.com or Airbnb and still paying 15-18% commission.

Solution

The innkeeper fills a 6-field form; Tonight Page publishes a mobile page at /p/{slug}/tonight with rooms left, a countdown to local midnight and a step-down price ladder, and generates a ready-to-paste WhatsApp broadcast plus a 1080x1920 Story image.

Differentiation · OTAs own the guest and take 15-18%; a static Instagram post has no countdown, no price ladder and no expiry. Tonight Page is a branded, self-expiring page broadcast to an audience the inn already owns.

1. Product opportunity and positioning

Tonight Page sells to exactly one buyer: the owner or front-desk manager of an independent inn, B&B, guesthouse or small boutique hotel with 5-40 rooms. The problem is concrete and perishable. A handful of rooms are still unsold at 5pm, and at midnight that inventory is worth nothing. The two levers available today are both bad: discount on Booking.com or Airbnb and still hand over 15-18% commission, or post a blurry phone photo to an Instagram account nobody checks. Neither produces a branded, time-boxed offer sent to guests the inn already owns.

The product inverts the model of the marketplace it descends from. It does not aggregate hotels or acquire travellers. It sells one narrow instrument to the supplier, who supplies both the inventory and the audience. That removes the marketplace cold start, the commission reconciliation and the funding-dependent burn that killed the original business. Each night the innkeeper fills six fields, publishes a mobile page that expires at local midnight, and gets a WhatsApp broadcast plus a 1080x1920 Story image in the same click. Reservations still happen on WhatsApp or the phone, so Tonight Page never touches guest money and never needs a payment licence.

The competing alternative is not another SaaS tool. It is commission. At a mid-market nightly rate, $99 is less than the OTA cut on one weekend booking, so the buying decision is arithmetic rather than procurement. The JEV score of 65.4 (band B, confidence 0.75) matches that shape: speed to first revenue at 8.77 and solo build feasibility at 7.63 are the strong axes; market demand at 5.28 and monetization potential at 5.13 are the weak ones. Read plainly, the score says the founder will probably ship this and can probably close the first buyer quickly, but should not assume a durable category. The plan therefore optimises for reply rate and for the second and third sale, not for breadth, and it keeps the build small enough that every one of the thirty days after launch is spent selling.

Positioning line: your empty rooms tonight, sold from your own guest list, without the OTA cut. The founder never claims to bring demand. The founder brings a page and a broadcast format, and the inn brings the list. That division of labour is the whole wedge.

Section 2 of 8

Smallest sellable MVP

A Stripe-gated, six-field form that publishes one branded mobile page at /p/{slug}/tonight with a countdown to local midnight and a step-down price ladder, plus a WhatsApp broadcast text and a downloadable Story image generated from the same click.

Must-have features

  • Magic-link auth and a single property record per account
  • Six-field compiler: property name, room types, counts, base rate, floor rate, reserve contact
  • Hosted page at /p/{slug}/tonight with rooms-left counter and live countdown to local midnight
  • Perishable Price Ladder: 3-4 timestamped steps generated from base and floor rates
  • One-click WhatsApp broadcast text generator
  • Satori-rendered 1080x1920 Instagram Story PNG with rooms left, current price, link and expiry
  • Sold-out / pause toggle and automatic expiry at local midnight
  • Stripe Checkout with one-time plan gating (90 nights vs 12 months)
  • Founder-side demo-page generator from property name and town
  • Per-page view counter for follow-up emails

Explicitly out of scope

  • No PMS, channel manager or OTA synchronisation
  • No traveller-facing search or marketplace
  • No processing of guest payments
  • No multi-property, teams or role permissions
  • No native mobile app
  • No competitor rate scraping or automatic dynamic pricing
  • No custom domain in the first build (Season Pass only, added day 18)

Demo flow (what the buyer sees)

  1. Innkeeper opens the Stripe payment link and pays $99
  2. Magic link issues access to the property dashboard
  3. Innkeeper fills the six fields for tonight
  4. Page publishes at /p/{slug}/tonight with countdown and price ladder
  5. Innkeeper copies the WhatsApp broadcast text and downloads the Story PNG
  6. Guest taps the reserve button; conversation continues on the inn's WhatsApp or phone
  7. Innkeeper toggles sold-out, or the page expires automatically at midnight
Build plan

Technical implementation plan

Stack

Next.js 15 App Router on VercelSupabase Postgres, Auth (magic link) and Row Level SecurityStripe Checkout and webhooksSatori via next/og for the 1080x1920 Story PNGResend for magic links and receiptsTailwind CSS and shadcn/uiVercel Cron for midnight expiry sweepOutscraper or manual Google Maps export for prospect data

Architecture

One Next.js app on Vercel serves both the authenticated dashboard and the public /p/{slug}/tonight pages. Supabase holds properties, room types, tonight inventory rows, ladder steps and page status, with RLS keyed on the authenticated owner id so a public page can only be read by slug. Stripe Checkout is created server-side; a webhook writes plan and expiry dates onto the property row, which is what gates publishing. The price ladder is computed at publish time from base and floor and stored as explicit steps, so the public page only compares the current clock against stored timestamps. A Vercel Cron job runs hourly and flips pages past local midnight to expired. Story images are generated on demand by a next/og route that accepts the page slug, so nothing is stored in a bucket.

Build steps

  1. Day 1: repo, Vercel project, Supabase project, Resend domain, Stripe test account
  2. Day 1: property and prospects tables plus the public address schema
  3. Day 2: magic-link auth, RLS policies, dashboard shell
  4. Day 2: six-field compiler form with validation and slug uniqueness
  5. Day 3: ladder engine that turns base and floor into 3-4 timestamped steps
  6. Day 3: public page render with rooms-left, countdown and reserve button
  7. Day 4: WhatsApp text generator and next/og Story route
  8. Day 4: view counter increment and sold-out toggle
  9. Day 5: Stripe Checkout, webhook plan gating, demo-page generator
  10. Day 5: end-to-end test purchase with a real card, then production deploy
  11. Day 6: legal pages, refund policy, onboarding Loom
  12. Day 18: custom domain support for Season Pass accounts

AI components

  • No model inference is used in the MVP. WhatsApp and Story copy are deterministic template slot-fills, so per-page delivery cost stays near zero and no API key can fail during a live sale.
  • Optional later: an LLM pass to rewrite the broadcast copy in the inn's tone, enabled per property and never on the critical publish path.
Hardest technical risk: Local-midnight expiry across UK, US, Ireland, Australia and India timezones. A page that expires at the wrong hour either kills a live offer or leaves a stale price on a sold-out night; store the property's IANA timezone and compute midnight server-side on every render rather than trusting a client clock.
Section 3 of 8

Pricing and monetization

Tonight Pass

Entry offer
$99 one-time

For Single-property innkeeper testing the tool for a season

  • 90 nights of Tonight Pages
  • WhatsApp broadcast and IG Story generator
  • Page-view counter
  • Custom slug

Season Pass

$249 one-time

For Inn or guesthouse that wants it as a standing front-desk tool

  • 12 months of Tonight Pages
  • Custom domain
  • Perishable Price Ladder automation
  • Priority email support

Model: Two one-time passes, no subscription, so the buyer can approve it without procurement and the founder collects cash inside the contest window.

First revenue offer: Tonight Page, 90 nights, $99 one-time, with the demo page already live at their own slug and the price held for 72 hours.

Expected ACV: $99

Upsell path: Day-7 follow-up converts Tonight Pass buyers to Season Pass at $249 with a custom domain. After the contest: annual renewal, a second property slug at $79, and a $39 holiday-preset pack for Christmas and New Year inventory gaps.

Target customers
105
Revenue model
$15,645
Costs
$600
Profit model
$15,045
Section 4 of 8

First-customer acquisition

Primary channel

Personalised cold email to independent innkeepers found on Google Maps, where every email links to a Tonight Page already built for that specific property.

Where to find them

  • Google Maps listings for independent inns and B&Bs in Cornwall and the Cotswolds, UK
  • Google Maps listings for coastal Maine and Vermont inns, US
  • Google Maps listings for West Cork and Connemara guesthouses, Ireland
  • Google Maps listings for Byron Bay and Margaret River, Australia
  • Independent-inn Facebook groups moderated in the UK and Ireland
  • Reddit host communities where small-property owners post inventory questions
  • Existing innkeeper directories and B&B association member lists with public emails

Exact outreach motions

  • Build a live demo page for the first 40 prospects before sending any email
  • Send a four-line email from a warmed domain, 20/day for the first two days then 80-100/day
  • Follow up on day 3 with the page's view count as the subject line
  • Follow up on day 7 with the $249 Season Pass and a custom domain
  • Post the same demo link in three innkeeper Facebook groups with a free-page angle
  • Call five non-responders per week on the number published on their Google Maps listing
  • Reply to every interested email within 60 minutes with a Stripe checkout link

Message template

Subject: Your empty rooms tonight

Hi {name} — I built you a page: tonight.page/p/{slug}/tonight. It shows tonight's unsold rooms, a price that steps down to your floor before midnight, and a WhatsApp message you can paste to past guests.

It is live now with sample numbers. $99 for 90 nights, no commission, no booking fees. The price holds until {date}.

Want me to load your real room types tonight? Reply with the count and I will do it in ten minutes.
Week-one goal: 600 prospects scraped, 40 live demo pages built, 200 personalised emails sent, and at least 6 replies.
Section 5 of 8

30-day execution roadmap

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

Accounts, repo, prospect list

  • Create the Next.js repo on Vercel and the Supabase project.
  • Buy the domain and verify it in Resend.
  • Scrape the first 300 inns with names, towns, phones and public emails.
  • Connect the Stripe account to TrustMRR in test mode.

Deliverable: Deployed hello page and a 300-row prospect sheet.

Day 2Data and auth

Schema, RLS, login

  • Create properties, room types, inventory and ladder tables.
  • Write RLS policies keyed on owner id.
  • Ship magic-link auth and the empty dashboard shell.

Deliverable: A user can log in and own a property record.

Day 3Core build

Compiler and public page

  • Build the six-field compiler form with slug uniqueness.
  • Implement the ladder engine producing 3-4 timestamped steps.
  • Render /p/{slug}/tonight with rooms-left and countdown.

Deliverable: A real Tonight Page renders from real inputs.

Day 4Distribution assets

WhatsApp copy and Story PNG

  • Build the WhatsApp broadcast text generator.
  • Build the next/og 1080x1920 Story route.
  • Add the view counter and sold-out toggle.

Deliverable: One click yields both share assets plus a live view count.

Day 5Monetisation and MVP shipMVP shipped

Stripe, gating, deploy

  • Wire Stripe Checkout and the plan-gating webhook.
  • Build the founder demo-page generator.
  • Test a real purchase end to end, then deploy to production.

Deliverable: MVP live in production with a verified test purchase.

Day 6Sales readiness

Demo pages and legal

  • Publish terms, privacy and refund policy pages.
  • Record a 4-minute onboarding Loom.
  • Generate 40 personalised demo pages for the top prospects.

Deliverable: 40 live demo links and an onboarding video.

Day 7First sends

Manual outreach

  • Send 20 emails one by one from the primary inbox.
  • Post the demo in two innkeeper Facebook groups.
  • Log every reply and objection in a sheet.

Deliverable: 20 sends, first reply data, objection list.

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

Email ramp

  • Send 60 personalised emails from the warmed domain.
  • Reply to all day-1 responses with a checkout link.

Deliverable: 80 cumulative sends.

Day 9Follow-up

Day-3 sequence

  • Send 80 emails to the next prospect batch.
  • Send the day-3 follow-up using the page view count.

Deliverable: 160 sends and first view-count follow-ups.

Day 10CloseFirst sale target

First paying customer

  • Send 80 emails and answer every reply within the hour.
  • Run a 10-minute onboarding call with the most engaged prospect.
  • Send the Stripe link in the same thread.

Deliverable: Target: first paid Tonight Pass.

Day 11Delivery

Onboard buyer one

  • Load the first customer's real room types and publish their page.
  • Send 100 emails to the next batch.
  • Ask the first buyer what nearly stopped them and record it.

Deliverable: One live paying customer page.

Day 12Scale outreach

Another region

  • Send 100 emails into Irish guesthouses.
  • Send the day-7 Season Pass follow-up to non-buyers.

Deliverable: 260 cumulative sends.

Day 13Proof

Objection handling

  • Rewrite the email opening around the top objection.
  • Send 100 emails with the new opening.

Deliverable: A/B opening line logged.

Day 14Review

Week two numbers

  • Compute open, reply and paid rates by region.
  • Cut the worst-performing region and send 100 emails elsewhere.

Deliverable: Channel scorecard and a pruned list.

Week 3 · Repeat & systematize · 7 days
Day 15Midpoint push

Season Pass

  • Send 100 emails and pitch Season Pass first to warmer replies.
  • Post the demo in two more host communities.

Deliverable: Second sale attempt in motion.

Day 16Volume

List expansion

  • Scrape 300 more inns in Australia and coastal India.
  • Send 100 emails.

Deliverable: 900 prospects total.

Day 17Conversion

Custom domain build

  • Ship custom domain support for Season Pass accounts.
  • Send 100 emails and announce the custom domain in follow-ups.

Deliverable: Season Pass parity shipped.

Day 18Volume

Reply handling

  • Send 100 emails.
  • Call five non-responders using their public Google Maps number.

Deliverable: Phone script tested on five calls.

Day 19Iterate

Holiday angle

  • Ship a holiday preset ladder for Christmas and New Year gaps.
  • Send 100 emails using the holiday angle.

Deliverable: Holiday preset live.

Day 20Volume

Host communities

  • Send 120 emails.
  • Run one free-page giveaway post in a host group.

Deliverable: Community post live with demo link.

Day 21Review

Week three numbers

  • Recompute reply and paid rates.
  • Kill the weakest subject line and send 120 emails with the winner.

Deliverable: Updated scorecard and subject-line decision.

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

New geography

  • Send 120 emails into US coastal Maine and Vermont.
  • Reply to every outstanding thread.

Deliverable: US segment opened.

Day 23Season Pass push

Upsell buyers

  • Offer existing Tonight Pass buyers the $249 upgrade with a custom domain.
  • Send 120 cold emails.

Deliverable: Upsell offer sent to the full buyer list.

Day 24Volume

Refund hygiene

  • Send 120 emails.
  • Confirm refund policy is visible at checkout and in the receipt.

Deliverable: Refund exposure documented.

Day 25Direct contact

Phone and DM

  • Call ten non-responders.
  • DM five inns that engaged on Instagram.
  • Send 120 emails.

Deliverable: Fifteen non-email touches logged.

Day 26Delivery quality

Retention of buyers

  • Check every paying page renders correctly on mobile.
  • Send 120 emails.

Deliverable: All live pages verified.

Day 27Urgency

Final offer window

  • Send 120 emails with the December 16 price deadline.
  • Follow up on all open threads.

Deliverable: Deadline campaign live.

Day 28Review

Week four numbers

  • Compute paid rate and cost per acquisition.
  • Send 120 emails with the best-performing segment messaging.

Deliverable: Unit economics check before the close.

Days 29-30 · Consolidate · 2 days
Day 29Last calls

Maximum volume

  • Send 150 emails.
  • Phone the five warmest unconverted prospects.

Deliverable: All warm leads contacted twice.

Day 30Close

Reconcile and stop

  • Send the final 100 emails before 13:00 UTC.
  • Reconcile Stripe payouts against TrustMRR.
  • Publish a profit summary with the projection disclaimer.

Deliverable: Final verified revenue count and a public summary.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.

Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).

The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.

Stated assumptions

  • Base: 9 customers blended at $149 (6 Tonight Pass at $99 plus 3 Season Pass at $249 = $1,341); labelled Base.
  • Conservative: 3 Tonight Pass sales at $99, no upsell, from 600 sends; labelled Conservative.
  • Upside: 22 customers blended at $154 (14 at $99 plus 8 at $249 = $3,388) from roughly 2,500 sends; labelled Upside.
  • Payment fees assume Stripe at 2.9% + $0.30 per charge on collected revenue; stated for every scenario.
  • No paid ads in Conservative or Base; the Upside line assumes $150 of sponsored posts in host communities.
  • Operating costs cover Vercel, Supabase, Resend, the cold-email tool and domain amortisation; no model inference is used.
  • Refunds are modelled only where a Season Pass is large enough to matter, at roughly 2% of revenue.
  • All three scenarios are projections built from stated assumptions, not verified revenue or existing customers.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$12
Paid marketing
$0
Hackathon profit
$285
Operating costs
$35
Business profit
$250

Base case

9 customers
$1,341
collected revenue · avg payment $149
Refunds
$99
Chargebacks
$0
Payment fees
$42
Paid marketing
$0
Hackathon profit
$1,200
Operating costs
$70
Business profit
$1,130

Optimistic

22 customers
$3,388
collected revenue · avg payment $154
Refunds
$348
Chargebacks
$99
Payment fees
$105
Paid marketing
$150
Hackathon profit
$2,686
Operating costs
$140
Business profit
$2,546

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$891
Payment fees (3.9%)
$35
Paid marketing
$0
Hackathon profit
$856
Business profit
$786

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 derived from the stated assumptions. They are not verified revenue, not existing customers and not a forecast of results.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold-email deliverability collapses at 100/day from a new domain.

Mitigation

Warm the domain for 48 hours, send 20/day manually first, keep one link and no images, and split volume across two sending domains.

Validation experiment

Send 20 emails from the primary inbox on day 7 and measure replies before scaling.

Kill criteria

If 100 sends produce zero replies across two batches, stop email and move to phone plus community posts.

Risk 2Innkeepers see the page as duplicative of Booking.com's own last-minute deals.

Mitigation

Lead every email with the commission number and the fact that the guest lands in the inn's own WhatsApp, not an OTA inbox.

Validation experiment

A/B the opening line on 60 sends each: commission-first versus empty-rooms-first.

Kill criteria

If the commission angle loses to empty-rooms by more than 2x on replies, reposition around guest ownership.

Risk 3Many independent inns keep guest contacts only in a PMS or a paper book, so the broadcast step is impractical.

Mitigation

Add a fallback path: publish the page and use the Story image plus a link in the inn's Instagram bio and Google Business post.

Validation experiment

Ask the first ten repliers one question: where does your past-guest list live?

Kill criteria

If more than 6 of 10 have no usable list, rebuild the pitch around the Story image and Google Business post instead of WhatsApp.

Risk 4Demo pages built from public names and photos cause accuracy or permission complaints.

Mitigation

Use text-only demos with sample prices, label them clearly as a sample, and never publish a real photo or a real rate.

Validation experiment

Include a one-line sample disclaimer and track complaints across the first 200 sends.

Kill criteria

Any written complaint triggers removing photos entirely and adding an opt-out line to every email.

Risk 5Stripe KYC or an account hold blocks collection inside the window.

Mitigation

Complete identity verification on day 1, keep the first sale small, and have a second processor ready but unused.

Validation experiment

Run a real $1 self-purchase on day 5 and confirm the payout lands.

Kill criteria

If verification is incomplete by day 6, pause outreach and resolve it before any further sends.

Risk 6The price ladder gets set below the inn's own cost.

Mitigation

The form rejects a floor rate below a founder-set sanity threshold and warns when the last step is under 40% of base.

Validation experiment

Review every paying customer's floor rate in the first week.

Kill criteria

No kill; this is a guardrail that must ship with the MVP.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Vercel repo and deploy the Next.js starter.
  • Create the Supabase project and copy keys into the environment.

Output: A deployed hello page and a working local build.

Hours 3-4

  • Buy the domain and add DNS.
  • Verify the sending domain in Resend and send a test email.

Output: A verified sending domain with SPF and DKIM.

Hours 5-6

  • Create the Stripe account and complete identity verification.
  • Connect Stripe to TrustMRR and confirm test mode.

Output: A verified payment account ready to collect.

Hours 7-9

  • Scrape 120 inns in Cornwall and the Cotswolds.
  • Normalise name, town, phone, email and room count into one sheet.

Output: A 120-row prospect sheet with contact fields.

Hours 10-12

  • Write the four-line email and the day-3 follow-up.
  • Draft the page layout on paper so day 3 has no design decisions.

Output: Two email drafts and a page wireframe, ready for the day-3 build.

Complete report

Full 30-day launch report

Read the full generated report

Tonight Page — 30-Day Launch Report

1. Product opportunity and positioning

Tonight Page sells to exactly one buyer: the owner or front-desk manager of an independent inn, B&B, guesthouse or small boutique hotel with 5-40 rooms. The problem is concrete and perishable. A handful of rooms are still unsold at 5pm, and at midnight that inventory is worth nothing. The two levers available today are both bad: discount on Booking.com or Airbnb and still hand over 15-18% commission, or post a blurry phone photo to an Instagram account nobody checks. Neither produces a branded, time-boxed offer sent to guests the inn already owns.

The product inverts the model of the marketplace it descends from. It does not aggregate hotels or acquire travellers. It sells one narrow instrument to the supplier, who supplies both inventory and audience. That removes the marketplace cold start, the commission reconciliation and the funding-dependent burn that killed the original business. Each night the innkeeper fills six fields, publishes a mobile page that expires at local midnight, and gets a WhatsApp broadcast plus a 1080x1920 Story image in the same click. Reservations still happen on WhatsApp or the phone, so Tonight Page never touches guest money and never needs a payment licence.

The competing alternative is not another SaaS tool. It is commission. At a mid-market nightly rate, $99 is less than the OTA cut on one weekend booking, so the buying decision is arithmetic, not procurement. The JEV score of 65.4 (band B, confidence 0.75) matches that shape: speed to first revenue at 8.77 and solo build feasibility at 7.63 are the strong axes; market demand at 5.28 and monetization potential at 5.13 are the weak ones. Read plainly, the score says the founder can likely ship and likely close a first buyer, but should not assume a durable category. The plan therefore optimises for reply rate and for the second and third sale, not breadth, and keeps the build small enough that every day after launch is spent selling.

Positioning line: your empty rooms tonight, sold from your own guest list, without the OTA cut. The founder never claims to bring demand. He brings a page and a broadcast format; the inn brings the list.

2. Smallest sellable MVP

One chain, five days. A Stripe-gated six-field form publishes a page at /p/{slug}/tonight showing rooms left, a countdown to local midnight and a Perishable Price Ladder of three or four timestamped steps between base and floor rate. The same click produces a paste-ready WhatsApp broadcast and a 1080x1920 Story PNG. A sold-out toggle and an automatic midnight expiry close the night.

The MVP is sellable at this point because the buyer gets a live, branded page the same evening they pay, with no onboarding project and no data migration. Everything that would slow that down is out: no PMS sync, no channel manager, no traveller search, no guest payments, no multi-property accounts, no native app, no rate scraping.

3. Technical implementation plan

Next.js App Router on Vercel, Supabase Postgres with RLS, Stripe Checkout, Satori via next/og for stories, Resend for magic links, and a Vercel Cron sweep for expiry. The public page reads one property row by slug plus its stored ladder steps; nothing expensive runs on a guest's request. Stripe's webhook writes plan and expiry onto the property row, which is the only thing gating publish. Stories render on demand so no image storage is required.

The hardest technical risk is local-midnight expiry across five timezones. Store the property's IANA timezone and compute midnight server-side on every render. A page that expires at the wrong hour either kills a live offer or shows a stale price on a sold-out night, and either one destroys the buyer's trust on the first night they use it.

No model inference is used. Copy is deterministic template fill, so delivery cost per page is effectively zero and no API key can fail during a live sale.

4. Pricing and monetization

Two one-time passes: Tonight Pass at $99 for 90 nights, Season Pass at $249 for 12 months with a custom domain. One-time pricing is deliberate. It clears the buyer's procurement threshold, collects cash inside the contest window, and matches a seasonal purchase. Expected ACV is $99; the blended figure across scenarios reflects a minority of Season Pass sales.

The upsell path is short: day-7 follow-up to Season Pass, then a second property slug at $79 and a $39 holiday preset after the contest. No subscription is introduced in the first 30 days because recurring billing would add churn exposure before there is any retention evidence.

5. First-customer acquisition

Personalised cold email where every message links to a Tonight Page already built for that property. The founder scrapes independent inns from Google Maps across Cornwall and the Cotswolds, coastal Maine and Vermont, West Cork and Connemara, then Byron Bay and Margaret River, plus association lists with public emails. Roughly 600 records go in first, expanding to about 900 by day 16.

The sequence: 20 manual sends on day 7 from the primary inbox, then 60-120/day from a warmed domain, day-3 follow-up whose subject is the page's real view count, day-7 follow-up pitching Season Pass. Every reply is answered within the hour with a Stripe link and a 10-minute onboarding call or Loom. Community posts in innkeeper Facebook groups and host subreddits run in parallel from day 7, and five non-responders a week get a phone call on the number published on their listing. Week-one goal: 600 prospects, 40 demo pages, 200 sends, six replies.

6. 30-day execution roadmap

Week 1 (days 1-5, Mon 16 to Fri 20 November) is build only. Days 1-2 handle accounts, schema, RLS and magic-link auth. Day 3 ships the compiler and the public page. Day 4 ships the WhatsApp text and the Story PNG plus view counting. Day 5 wires Stripe, the demo generator and production deploy, with a real card test against a live build. MVP deadline is day 5.

Week 1 weekend (days 6-7) is sales readiness: legal pages, a four-minute Loom, 40 personalised demo pages, then the first 20 manual sends. First-sale target is day 10.

Week 2 (days 8-14) ramps to 80-100 sends per day, adds the day-3 view-count follow-up and the day-7 Season Pass follow-up, and onboards the first buyer with real room types. Week 3 (days 15-21) expands the list to 900, ships custom domain support for Season Pass, adds a holiday preset ladder, and prunes the weakest region. Week 4 (days 22-28) opens the US segment, upsells existing buyers to $249, starts phone calls and Instagram DMs, and runs a December 16 deadline campaign. Days 29-30 are last-call volume: 150 sends, then 100 more before 13:00 UTC on Wednesday 16 December, followed by reconciliation and a public summary. The day-by-day table with tasks and deliverables sits above this report.

7. Revenue and profit scenarios

All three are projections from stated assumptions, not verified revenue and not existing customers.

Conservative: 3 Tonight Pass sales at $99, gross $297, zero refunds, zero chargebacks, $12 processing fees, no ads, $35 operating cost. Base: 9 customers blended at $149 (six at $99, three at $249), gross $1,341, one $99 refund, $42 processing fees, no ads, $70 operating cost. Upside: 22 customers blended at $154 (fourteen at $99, eight at $249), gross $3,388, $348 refunds, a $99 chargeback, $105 processing fees, $150 of sponsored posts, $140 operating cost.

Two different profit numbers matter and they must not be mixed. Hackathon profit deducts refunds, chargebacks, processing fees and paid marketing, but not hosting, domains, tooling or delivery cost. In the Base case that is $1,341 minus $99, minus $42, which leaves $1,200. Business profit then subtracts the $70 operating cost, leaving $1,130. The gap between hackathon profit and business profit is small here only because the product carries no inference cost; that is a deliberate design choice, not an accident.

8. Main risks and validation experiments

Deliverability is risk one. Warm the domain, send 20 manually first, one link, no images. Kill email if 100 sends produce zero replies across two batches. Risk two is the duplicate-of-Booking.com objection; the mitigation is to lead with the commission number and the fact that the guest stays in the inn's own inbox. Run a 60-send A/B on the opening line and reposition if the commission angle loses badly.

Risk three is that most independent inns have no usable past-guest list, which breaks the broadcast premise. Ask the first ten repliers where their list lives; if six or more have nothing usable, pivot the pitch to the Story image plus a Google Business post. Risk four is permission or accuracy complaints about demo pages built from public data: text-only demos, sample prices, a visible sample disclaimer, and an immediate photo removal if anyone objects. Risk five is a Stripe verification delay; complete KYC on day 1 and confirm a payout lands by day 5.

9. First 24-hour action plan

Hours 1-2: deploy the Next.js starter to Vercel and create the Supabase project. Hours 3-4: buy the domain, verify the sending domain in Resend, send one test email. Hours 5-6: create the Stripe account, complete identity verification, connect it to TrustMRR. Hours 7-9: scrape 120 Cornwall and Cotswolds inns into a normalised sheet. Hours 10-12: write the four-line email and the day-3 follow-up, and wireframe the page so day 3 contains no design decisions.

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 →