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

Legacy Page Lifeline

Converts a business's broken or outdated web page into a modern, mobile-ready static page plus a plain-English fix report, delivered in 24 hours.

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.

Speculative5.82/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct reply outreach in local business Facebook groups and web-hosting support forums where owners post broken-site complaints.
Who pays

Owner or office manager of a 2-40 person local business (clinic, law office, trades, restaurant) with a visibly broken or outdated website, reached in local business Facebook groups and web-hosting support forums.

Biggest execution risk

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

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

0/18
Entry price
$99
Solo build
5 days
30d base revenue
$990
30d hackathon profit
$951
Section 1 of 8

Product opportunity and positioning

Target customer

Owner or office manager of a 2-40 person local business (clinic, law office, trades, restaurant) with a visibly broken or outdated website, reached in local business Facebook groups and web-hosting support forums.

Why now

Static page generation and managed LLM APIs make a full single-page rebuild cost under $6 in delivery cost, so a $99 one-time price clears delivery cost by a wide margin from order one.

Problem

Their site renders broken on phones, contact forms silently drop messages, and links are dead, but they have no technical staff and no budget for an agency rebuild.

Solution

The owner submits one URL and a goal checklist, pays $99 via Stripe, and within 24 hours receives a rebuilt responsive static page, a prioritized fix report and a downloadable HTML bundle by email.

Differentiation · A site builder requires the owner to do the work and a chatbot cannot crawl, rebuild and package a deployable bundle; this is one constrained input and one deployable artifact with a 24-hour turnaround.

1. Product opportunity and positioning

Legacy Page Lifeline sells one narrow outcome: a working, mobile-ready page plus a plain-English fix report, back in the customer's inbox within 24 hours of paying $99. The buyer is not "a business" — it is a specific person, usually the owner or office manager of a 2-40 person local business, who has just discovered their site renders as a squeezed, unclickable mess on a phone, or whose contact form quietly stopped delivering messages years ago. They have no developer, no CMS habit, and no appetite for a $4,000 agency rebuild or three weekends inside a site builder.

The wedge works because the input is constrained (one URL, a checkbox list of goals), the output is concrete (a downloadable HTML bundle plus a prioritized fix list), and the turnaround is a day. Nothing depends on a procurement cycle or a marketplace cold start: the founder replies in the same thread where the owner complained, with a free preview of their rebuilt page. The alternatives are either too generic (a $20/month site builder that still requires the owner to do the work) or too large (an agency quote). A general AI assistant is not a real substitute, because a chat window does not crawl the live page, does not produce a deployable bundle, and does not survive a copy-paste into a hosting panel.

JEV scored this concept 58.2/100 (band C), strongest on speed to first revenue (8.26) and solo build feasibility (7.46), weakest on monetization potential (3.87) and market demand (4.18). That shape is the operating instruction for the next 30 days: the build is not the risk, willingness to pay is. The plan therefore front-loads outreach and uses the free preview — the artifact that proves the fix — as the conversion device, rather than waiting for a website to sell itself.

Positioning discipline matters. This is not a rebuild service, not a hosting product, not a CMS and not a design retainer. Every sales message names one page, one price, one delivery window. The moment the offer drifts toward full multi-page rebuilds, custom design or ongoing editing, delivery cost and turnaround both break and the 24-hour promise becomes a liability.

Section 2 of 8

Smallest sellable MVP

A paid intake form where an owner submits one URL plus a goal checklist, and receives by email within 24 hours a rebuilt responsive static page, a prioritized fix report and a downloadable HTML bundle.

Must-have features

  • URL intake form with goal checklist (fix mobile layout, fix contact form, refresh outdated content)
  • Server-side crawl and content extraction of the submitted page
  • Responsive static page generator producing index.html and styles.css
  • Prioritized fix report generator with severity, cause and effort per issue
  • ZIP bundle builder and download link
  • Stripe Checkout for $99 Single Page Rescue and $249 Three Page Rescue
  • Resend delivery email containing the bundle link and fix report
  • Order state tracking with a hard page-size and page-count guard

Explicitly out of scope

  • Multi-page site rebuilds beyond three pages
  • Hosting, DNS and domain management
  • CMS or ongoing editing
  • Custom design or brand work
  • Analytics, SEO campaigns, ad management
  • Live support or 24/7 chat
  • Accessibility certification

Demo flow (what the buyer sees)

  1. Owner opens the intake page and pastes one URL
  2. Owner ticks goals from a checklist and picks Single or Three Page Rescue
  3. Stripe Checkout collects $99 or $249
  4. Serverless job crawls the page and extracts text, images, metadata and contact details
  5. Generator produces the rebuilt responsive page and the prioritized fix report
  6. ZIP bundle is built, uploaded, and emailed with the fix report as the email body
  7. Owner downloads the bundle and hands it to their host or web person
Build plan

Technical implementation plan

Stack

Next.js on VercelVercel serverless functionsManaged LLM API (anthropic or openai)Stripe Checkout and webhooksResend transactional emailPostgres (Supabase free tier) for order stateCheerio plus a headless fetch for extractionS3-compatible object storage for ZIP bundles

Architecture

A Next.js app serves the marketing page, the intake form and a free-preview tool. Stripe Checkout handles payment; a webhook writes an order row to Postgres and enqueues a job. The job fetches the submitted URL, extracts content, calls the LLM with a fixed prompt and a strict output schema, renders the rebuilt page from a template, assembles the fix report, zips the bundle to object storage, and sends the delivery email. A polling or cron function retries failed jobs and marks anything past 20 hours for manual founder review.

Build steps

  1. Day 1: scaffold Next.js app, deploy to Vercel, buy domain, wire environment keys
  2. Day 2: build intake form, Stripe Checkout, webhook and order table
  3. Day 3: implement crawl and content extraction with size and timeout caps
  4. Day 4: implement page generator, fix report generator and deterministic HTML template
  5. Day 5: implement ZIP assembly, storage upload, delivery email and end-to-end test on three real broken sites
  6. Day 6: add retry logic, refund path, error states and cost guardrails
  7. Day 7: ship the free preview tool that rebuilds a page and returns a screenshot plus a three-line summary
  8. Day 20: patch the three most common delivery defects found in real orders

AI components

  • LLM call that rewrites extracted page copy into clean sections and headline hierarchy
  • LLM call that produces the prioritized fix report as strict JSON
  • LLM call that generates replacement alt text and short meta descriptions
Hardest technical risk: Image and asset handling: crawled pages reference assets that may 404, be huge, or be hotlinked, so the rebuilt page can look worse than the original unless the generator degrades gracefully to placeholders and text-only fallbacks.
Section 3 of 8

Pricing and monetization

Single Page Rescue

Entry offer
$99 one-time

For Small business owner with one broken page

  • One rebuilt responsive page
  • Prioritized fix report
  • Downloadable HTML bundle
  • 24-hour delivery

Three Page Rescue

$249 one-time

For Owner needing several key pages fixed

  • Three rebuilt responsive pages
  • Prioritized fix report
  • Downloadable HTML bundle
  • 48-hour delivery

Model: Flat one-time fee per rescue, paid before delivery, with an optional expedite add-on and a repeat-purchase path for additional pages.

First revenue offer: Reply to a broken-site post with a free rebuilt preview of their page and one line: I can send the full page files plus a fix list for $99 today, delivered inside 24 hours.

Expected ACV: $99

Upsell path: Offer the $249 Three Page Rescue at delivery, add a $49 six-hour expedite option, and sell a $49 per-page follow-on to any owner who already bought once.

Target customers
10
Revenue model
$990
Costs
$60
Profit model
$930
Section 4 of 8

First-customer acquisition

Primary channel

Direct reply outreach in local business Facebook groups and web-hosting support forums where owners post broken-site complaints.

Where to find them

  • Local business Facebook groups for three named metros
  • r/smallbusiness and r/webhosting threads about broken or outdated sites
  • WordPress.org support forum threads about broken themes
  • WebHostingTalk and low-end hosting community boards
  • Chamber of commerce member directories with visibly outdated sites
  • Google Maps listings in one vertical (dental, legal, trades) with non-mobile sites
  • Local trade association Facebook pages

Exact outreach motions

  • Send a free rebuilt preview screenshot plus a three-line fix summary in the same thread, no link
  • Follow up once after 48 hours with the specific defect found on their page
  • Post the free-preview offer in three local business groups per week
  • DM owners whose Maps listing shows a non-responsive site with a single-sentence defect callout
  • Ask every delivered customer for one referral to another owner in the same trade
  • Convert preview replies with a Stripe link that expires in 48 hours

Message template

Saw your post about the site looking broken on phones. I rebuilt your contact page as a test — screenshot attached, and the fix list is three items. If it is useful I can send the full page files plus the complete fix report for $99, delivered inside 24 hours. No subscription, no call needed.
Week-one goal: 100 qualified prospects logged with a named defect, 30 free previews sent, 8 replies, and the first paid order by day 12.
Section 5 of 8

30-day execution roadmap

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

Ship the skeleton

  • Create repo and deploy empty Next.js app to Vercel.
  • Buy domain and set up Resend plus Postgres.
  • Write the intake field list and goal checklist copy.

Deliverable: Live blank app on a real domain with keys wired.

Day 2Payments

Take money

  • Build intake form with URL and goal checklist.
  • Wire Stripe Checkout for $99 and $249 tiers.
  • Handle webhook and write order rows to Postgres.

Deliverable: A $99 test order that lands in the database.

Day 3Crawl

Reliable extraction

  • Implement fetch with 15s timeout and 5MB cap.
  • Extract text, headings, images, contact details.
  • Log extraction failures with a readable reason.

Deliverable: Extraction working on 5 varied real URLs.

Day 4Generation

Page and report

  • Write the page generator prompt with strict output schema.
  • Build the deterministic responsive HTML template.
  • Build the prioritized fix report renderer.

Deliverable: A rebuilt page and fix report for one real site.

Day 5DeliveryMVP shipped

End-to-end MVP

  • Assemble ZIP bundle and upload to object storage.
  • Send delivery email with bundle link and fix report.
  • Run three real orders start to finish.

Deliverable: MVP complete and sellable (day 5 deadline).

Day 6Hardening

Fail safely

  • Add retry, error states and a refund path.
  • Enforce page-size and page-count cost guards.
  • Add a 20-hour manual review alert.

Deliverable: Order pipeline that fails loudly, not silently.

Day 7Bait

Free preview tool

  • Ship a preview tool that rebuilds any URL free.
  • Return a screenshot plus a three-line fix summary.
  • Add an email capture field to the preview.

Deliverable: Public free-preview tool used in all outreach.

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

Build the list

  • Log 100 local businesses with visibly broken pages.
  • Record URL, owner contact and the specific defect.
  • Prioritise three verticals in three metros.

Deliverable: 100-row prospect sheet with named defects.

Day 9Outreach

Batch 1

  • Send 25 free previews to Facebook group posters.
  • Personalise each with the defect found.
  • Log reply and preview-open timestamps.

Deliverable: 25 personalised previews sent.

Day 10Outreach

Batch 2

  • Post in WordPress support and r/smallbusiness threads.
  • Send 25 previews from the prospect sheet.
  • Track which message angle gets replies.

Deliverable: 50 total outreach touches logged.

Day 11Follow-up

48-hour nudge

  • Follow up on batch 1 with the defect callout.
  • Publish the free-preview offer in three groups.
  • Answer every reply within two hours.

Deliverable: Follow-ups sent and all replies answered.

Day 12First saleFirst sale target

Close order one

  • Send Stripe link to the warmest reply.
  • Deliver the first order personally and fast.
  • Ask for a testimonial and a referral name.

Deliverable: First paid order collected (target day 12).

Day 13Conversion

Preview to paid

  • Send expiring Stripe links to all preview replies.
  • Add a reply-with-FIX call to action in every message.
  • Log preview-to-paid conversion rate.

Deliverable: Conversion rate measured for the week.

Day 14Review

Read the numbers

  • Compute reply rate, preview rate, paid rate.
  • Cut the worst-performing message angle.
  • Rewrite the top-performing one.

Deliverable: One winning message template locked in.

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

Publish evidence

  • Publish three anonymised before-and-after pages.
  • Add the 24-hour delivery promise to the site.
  • Link case pages from every outreach message.

Deliverable: Three live case pages on the site.

Day 16Niche

One vertical

  • Pick one vertical, such as dental clinics.
  • Write a niche-specific first line for outreach.
  • Send 25 previews to that vertical only.

Deliverable: 25 niche-targeted previews sent.

Day 17Upsell

Raise order value

  • Add the $249 Three Page Rescue offer to delivery emails.
  • Add a $49 six-hour expedite option.
  • Track attach rate on every delivery.

Deliverable: Upsell live and measured.

Day 18Outreach

Batch 3

  • Send 40 new previews from the prospect sheet.
  • Test two different opening lines.
  • Log replies by line variant.

Deliverable: 40 previews sent with a clean A/B split.

Day 19Guarantee

Remove risk

  • Offer a refund if delivery misses 24 hours.
  • State the guarantee in every message.
  • Track refund requests raised.

Deliverable: Guarantee live on site and in outreach.

Day 20Quality

Fix defects

  • List the three most common delivery defects.
  • Patch asset fallback, form handling and missing content.
  • Add a pre-send QA checklist.

Deliverable: Defect rate reduced on the next five orders.

Day 21Decision

Double or kill

  • Compare channels by paid conversions, not replies.
  • Double the winning channel for week four.
  • Drop the weakest channel entirely.

Deliverable: Written channel decision with numbers.

Week 4 · Scale what works · 7 days
Day 22Self-serve

Buy without talking

  • Ship a public order page with Stripe Checkout.
  • Add a two-minute sample bundle download.
  • Link the order page in every forum signature.

Deliverable: Anyone can buy without a conversation.

Day 23Volume

Batch 4

  • Send 50 previews to the winning vertical.
  • Automate preview generation for each prospect.
  • Keep manual personalisation to one sentence.

Deliverable: 50 previews sent at lower time per prospect.

Day 24Content

Forum-safe post

  • Write why-your-site-looks-broken-on-phones post.
  • Include the free-preview call to action.
  • Post it in three groups that allow it.

Deliverable: One post live in three communities.

Day 25Referral

Borrow trust

  • Offer $30 credit per referred owner.
  • Ask all delivered customers for one name.
  • Track referrals in the order table.

Deliverable: Referral loop live with tracked codes.

Day 26Volume

Batch 5

  • Send 50 previews with the case pages attached.
  • Re-message every previous no-reply once.
  • Log all outcomes in the sheet.

Deliverable: 100 late-week touches sent.

Day 27Operations

Hold 24 hours

  • Automate the delivery QA checklist.
  • Add failure alerts to the email channel.
  • Confirm median turnaround time.

Deliverable: Median delivery time documented.

Day 28Checkpoint

Revenue review

  • Tally orders, refunds, fees and ad spend.
  • Pick the final-week push angle.
  • Set a closing offer with a real deadline.

Deliverable: Final-week plan with a revenue target.

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

Convert the warm

  • Send the closing offer to every warm lead.
  • Follow up every preview sent but not bought.
  • Deliver all open orders before the window ends.

Deliverable: Every warm lead contacted once more.

Day 30Submit

Lock the result

  • Clear remaining orders and refund any failures.
  • Screenshot Stripe payouts and reconcile fees.
  • Submit the hackathon report before 13:00 UTC.

Deliverable: Submission filed with reconciled numbers.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • All scenarios are projections from stated assumptions, not verified revenue.
  • Conservative, Base and Upside each assume the $99 Single Page Rescue is the volume tier.
  • Upside ARPU of $109 reflects roughly one in eight orders taking the $249 tier or a $49 expedite add-on.
  • Payment fees are modelled at roughly 4 percent of gross revenue, close to Stripe 2.9 percent plus 30 cents per transaction.
  • Ad spend is zero in Conservative and Base because the primary channel is organic forum and group outreach.
  • Upside assumes 150 dollars of paid boosts in local business groups to extend reach in week four.
  • Operating costs cover Vercel, domain, Postgres, object storage and LLM plus crawl delivery cost at roughly 2 to 5 dollars per order.
  • Every price point clears per-order delivery cost, so no order is sold below cost.

Conservative

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

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$39
Paid marketing
$0
Hackathon profit
$951
Operating costs
$45
Business profit
$906

Optimistic

25 customers
$2,725
collected revenue · avg payment $109
Refunds
$99
Chargebacks
$0
Payment fees
$136
Paid marketing
$150
Hackathon profit
$2,340
Operating costs
$120
Business profit
$2,220

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$990
Payment fees (3.9%)
$39
Paid marketing
$0
Hackathon profit
$951
Business profit
$906

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 figures are scenario projections built from the stated assumptions. They are not verified revenue, not traction, and not a forecast of results.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold forum and group outreach gets ignored, so no conversation ever starts.

Mitigation

Lead with the free rebuilt preview of their own page instead of a pitch, and cap each message at three sentences.

Validation experiment

Send 25 personalised previews in two days and measure reply rate against a 10 percent threshold.

Kill criteria

Fewer than 3 replies from 50 previews across two batches means the channel or the message is wrong; switch to one named vertical and rewrite the opener.

Risk 2The rebuilt page misses owner intent, so the output feels wrong and triggers refund requests.

Mitigation

Make the goal checklist mandatory, keep original copy and structure, and never invent services or prices.

Validation experiment

Deliver five orders and ask one question: what is missing or wrong. Count corrections per order.

Kill criteria

If more than one in three orders needs a manual rewrite, the generator prompt or the intake is broken and must change before more selling.

Risk 3Large or asset-heavy pages blow up LLM and crawl cost per order.

Mitigation

Enforce a 5MB fetch cap, a page-count cap per tier, image placeholders on failure, and a cost log per order.

Validation experiment

Track measured cost per delivered order for the first ten orders against a 6 dollar ceiling.

Kill criteria

Any order whose measured delivery cost exceeds 25 percent of its price gets a hard size limit added the same day.

Risk 4Willingness to pay is lower than assumed because owners see this as a favour, not a purchase.

Mitigation

Anchor against an agency quote in one line, and offer the $249 tier so the $99 option looks like the entry point.

Validation experiment

Present two price points to two matched outreach batches and compare paid conversion.

Kill criteria

If preview-to-paid conversion stays under 5 percent after 60 previews, reposition the offer around a named outcome such as restoring a broken contact form.

Risk 5Delivery slips past 24 hours and the core promise breaks.

Mitigation

Automate the pipeline, alert at the 20-hour mark, and keep a manual fallback path the founder can run in 30 minutes.

Validation experiment

Time five consecutive deliveries end to end and record the median.

Kill criteria

If median turnaround exceeds 18 hours, cut the Three Page tier until the pipeline is faster.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the repo and deploy an empty Next.js app to Vercel.
  • Buy the domain and point it at the deployment.
  • Open Stripe, Resend and the LLM API accounts and store keys.

Output: Live blank deployment on a real domain with all accounts open.

Hours 3-5

  • Write the intake form with URL field and goal checklist.
  • Write the marketing page headline and the three-line offer.
  • Define the $99 and $249 tier copy.

Output: Intake and sales page copy committed to the repo.

Hours 6-9

  • Wire Stripe Checkout and the webhook handler.
  • Create the orders table in Postgres.
  • Run one test purchase and confirm the row lands.

Output: Working test payment writing an order row.

Hours 10-14

  • Implement the crawl and extraction step with timeout and size caps.
  • Draft the page generator prompt and the fix report schema.
  • Test extraction on three real broken URLs.

Output: Extraction output saved for three real sites.

Hours 15-19

  • Build the responsive HTML template.
  • Generate one rebuilt page and one fix report by hand-run script.
  • Compare against the original page on a phone viewport.

Output: One real rebuilt page plus fix report as proof of output quality.

Hours 20-24

  • Log 30 prospects from two Facebook groups and one forum.
  • Draft the outreach message and the free-preview pitch.
  • Schedule the first 10 previews for the next morning.

Output: 30-row prospect sheet and 10 previews queued for day two.

Complete report

Full 30-day launch report

Read the full generated report

Legacy Page Lifeline — 30-Day Launch Report

1. Product opportunity and positioning

Legacy Page Lifeline sells one narrow outcome: a working, mobile-ready page plus a plain-English fix report, in the customer's inbox within 24 hours of paying $99. The buyer is not "a business" — it is a specific person, usually the owner or office manager of a 2-40 person local business, who just discovered their site renders as a squeezed, unclickable mess on a phone, or whose contact form stopped delivering messages years ago. They have no developer, no CMS habit, and no appetite for a $4,000 agency rebuild or three weekends inside a site builder.

The wedge holds because the input is constrained (one URL, a goal checklist), the output is concrete (a downloadable bundle plus a prioritized fix list), and the turnaround is a day. Nothing depends on a procurement cycle or marketplace cold start: the founder replies in the same thread where the owner complained, attaching a free rebuilt preview. Alternatives are either too generic (a site builder that still makes the owner do the work) or too large (an agency quote). A general AI assistant is not a substitute, because a chat window does not crawl the live page, does not produce a deployable bundle, and does not survive a copy-paste into a hosting panel.

JEV scored this concept 58.2 out of 100, band C, strongest on speed to first revenue (8.26) and solo build feasibility (7.46), weakest on monetization potential (3.87) and market demand (4.18). That shape is the operating instruction: the build is not the risk, willingness to pay is. The plan therefore front-loads outreach and makes the free preview the conversion device rather than waiting for a website to sell itself.

Positioning discipline matters. This is not a rebuild service, not hosting, not a CMS and not a design retainer. Every message names one page, one price, one delivery window. The moment the offer drifts toward multi-page rebuilds or custom design, delivery cost and turnaround both break and the 24-hour promise becomes a liability.

2. Smallest sellable MVP

Five days of build, no more. The MVP is a URL box, a goal checklist, a Stripe button, and an automated pipeline that returns a ZIP containing a rebuilt responsive page, a stylesheet and a fix report, delivered by email. Three working real orders is the bar for calling it sellable, not a polished dashboard.

Anything that does not change whether a stranger can pay $99 and receive a usable page is out: no accounts, no editing UI, no hosting, no analytics, no support portal. Delivery runs through one transactional email and one download link, with the founder as the manual fallback when a job fails.

3. Technical implementation plan

Next.js on Vercel, serverless functions for the job, Postgres for order state, Stripe Checkout plus webhooks for money, Resend for delivery, an S3-compatible bucket for the ZIP, and one managed LLM API for rewriting copy and producing the fix report as strict JSON.

The critical design choice is a deterministic HTML template fed by LLM output, never raw model-generated HTML. That keeps output consistent, cheap and repairable. The crawl gets a 15-second timeout and a 5MB cap so one heavy page cannot blow the delivery budget. Every order logs measured cost.

The hardest technical risk is asset handling. Crawled images 404, are enormous, or are hotlinked, so a rebuilt page can look worse than the original. Mitigation is graceful degradation: placeholders, alt text from the model, and a text-first layout that reads well with zero images.

4. Pricing and monetization

Two one-time tiers: $99 Single Page Rescue and $249 Three Page Rescue. Payment is taken before work starts through Stripe Checkout, which removes invoicing and chasing. A $49 six-hour expedite add-on lifts order value without a new product.

At roughly 2 to 5 dollars of delivery cost per order, every sale clears its own cost with wide margin, which is a hard requirement of the contest and also the reason the price can stay impulse-friendly. The repeat path matters more than the first sale: an owner with a broken homepage usually has a broken services and contact page too, and the $249 tier exists to capture that in the same conversation rather than a second campaign.

5. First-customer acquisition

The only channel is direct reply outreach where owners already complain: local business Facebook groups, web-hosting and WordPress support forums, and Maps listings with visibly non-responsive sites. Generic advertising is a poor fit because the trigger is a specific defect the founder can name.

The mechanic is the free preview. Build the rebuilt page, screenshot it, and send it in-thread with a three-line explanation of what was broken. Only then mention the $99 deliverable. Follow up exactly once after 48 hours. Every preview reply gets a Stripe link that expires in 48 hours.

Week-one target: 100 prospects logged with a named defect, 30 previews sent, 8 replies, first paid order by day 12. If replies stay under 10 percent across two batches, the message changes before the volume changes.

6. 30-day execution roadmap

Days 1-5 build and ship the pipeline, with MVP live on day 5. Day 6 hardens failure paths and day 7 ships the free preview tool that every outreach message depends on.

Days 8-14 are the first real selling block: a 100-row prospect sheet, two outreach batches of 25, a 48-hour follow-up, and the first paid order targeted for day 12. Day 14 is a numbers review that cuts the weakest message angle.

Days 15-21 add proof and focus. Three anonymised before-and-after case pages go live, one vertical gets a dedicated opener, upsells appear in delivery emails, and a delivery-time guarantee removes buyer risk. Day 21 decides which channel gets doubled.

Days 22-28 push volume and self-serve: a public order page, two 50-preview batches, one forum-safe content post, a referral credit, and an operations pass to hold the 24-hour promise. Day 29 is a closing offer to every warm lead. Day 30 clears open orders, reconciles fees against Stripe payouts, and files the submission before 13:00 UTC.

7. Revenue and profit scenarios

Three projections, all labelled as hypotheses. Conservative: 3 customers at $99, 297 dollars gross, 12 dollars of fees, 25 dollars of operating cost. Base: 10 customers at $99, 990 dollars gross, 39 dollars of fees, 45 dollars of operating cost, zero paid marketing because the channel is organic. Upside: 25 customers at a 109 dollar blended ARPU, 2,725 dollars gross, one refund, 136 dollars of fees, 150 dollars of group boosts, 120 dollars of operating cost.

Contest ranking uses hackathon profit, which subtracts refunds, chargebacks, payment fees and paid marketing from collected revenue but not hosting or delivery cost. Business profit subtracts operating cost on top. Both are derived from these inputs. None of these figures describe existing customers or real revenue; they are planning targets.

8. Main risks and validation experiments

Five risks carry weight. Cold outreach being ignored is tested by a 25-preview batch against a 10 percent reply floor. Output missing owner intent is tested by delivering five orders and counting corrections. Cost blowout on heavy pages is tested by logging measured delivery cost on the first ten orders against a 6 dollar ceiling. Weak willingness to pay is tested by presenting two price points to matched batches. Delivery slipping past 24 hours is tested by timing five consecutive jobs against an 18-hour median bar.

Each risk has a kill criterion written down before the test runs, so the decision is mechanical rather than emotional at the end of a bad week.

9. First 24-hour action plan

Hours 1-2: deploy the skeleton on a real domain and open Stripe, Resend and the LLM account. Hours 3-5: write the intake form, sales copy and tier definitions. Hours 6-9: wire Checkout and the webhook and confirm one test order writes a row. Hours 10-14: build crawl and extraction with caps and test on three real URLs. Hours 15-19: generate one real rebuilt page plus fix report and check it on a phone viewport. Hours 20-24: log 30 prospects and queue the first 10 previews for the next morning. The day ends with a working payment path, one proof artifact, and a prospect list — everything day two needs to start selling.

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 →