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

Foldline Report

Paste a landing page URL and get a device-by-device Fold Map PDF that shows what visitors see before scrolling, with a ranked fix list for designers to ship.

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.23/10
MVP build (solo)
5 days
Launch price
$79
Sales to $1,000 revenue
13 customers
First paying customer
Direct LinkedIn and X DMs to agency owners who posted a client launch in the last 7 days, each with a free one-page Fold Map teaser of that public page.
Who pays

Owner or lead designer at a 1-10 person web design, Webflow or Shopify agency in the US, UK, Canada or Australia, triggered by a client asking why a newly launched landing page is not converting.

Biggest execution risk

Monetization potential 4.7/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; 13 sales at $79 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

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

0/12
Entry price
$79
Solo build
5 days
30d base revenue
$950
30d hackathon profit
$912
Section 1 of 8

Product opportunity and positioning

Target customer

Owner or lead designer at a 1-10 person web design, Webflow or Shopify agency in the US, UK, Canada or Australia, triggered by a client asking why a newly launched landing page is not converting.

Why now

Zero integration and zero traffic required: the buyer can run it on the next client page today and resell it as a paid audit line item, so no snippet, no data-collection consent and no trust cycle stands between payment and delivery.

Problem

After launch the designer must justify above-the-fold decisions by hand-capturing device screenshots, eyeballing the fold and writing a subjective fix list that clients push back on.

Solution

Pay $79 via Stripe Checkout, paste one URL, and receive a six-page PDF/HTML Fold Map: five viewport renders with numbered pins, a 15-check deterministic scorecard and a prioritized fix list with copy-paste CSS, headline and CTA snippets.

Differentiation · Heatmap and session-recording tools need installed code and visitor volume; a freshly launched or low-traffic page has neither. Foldline needs only a public URL and returns a client-ready artifact instead of a dashboard the agency still has to interpret.

1. Product opportunity and positioning

Foldline Report sells exactly one artifact: a Fold Map. A designer pastes a landing-page URL, pays, and receives a six-page PDF/HTML report that renders the page at five viewports (360, 390, 768, 1024, 1440), pins every meaningful element visible before the fold, scores the page against 15 deterministic checks, and ranks the fixes so a designer can ship them the same day.

The buyer is narrow and identifiable: the owner or lead designer of a 1-10 person web design, Webflow or Shopify agency in the US, UK, Canada or Australia. The trigger is a recurring, emotionally loaded moment. A page goes live, the client asks why it is not converting, and the designer has to defend above-the-fold decisions with something stronger than opinion. Today that defence costs two to three hours of manual screenshots plus a subjective write-up the client questions.

Three properties make this survivable for one person in 30 days. First, there is no integration: no JS snippet, no SDK, no analytics consent, no visitor volume. A page that launched yesterday with nine visitors can still be audited. Second, there is no trust cycle: the buyer does not have to believe a dashboard, they receive a document they can email straight to their client with their own logo on it. Third, the artifact is resellable: agencies already bill audits, so Foldline slots into an existing line item rather than creating a new budget conversation.

The honest weakness, and JEV flags it, is monetization potential. A $79 one-off is a thin charge. The launch plan answers this without inventing a subscription the founder cannot service: repeat-purchase packs. Five credits for $299 and ten for $499 with a logo swap turn one satisfied designer into four to six future reports, and give a reason to follow up after delivery that is not a discount.

Positioning against the incumbent category is deliberate. Foldline is not a heatmap, not a session recorder, not a click-tracking SDK and not a friction API for developers. Those products answer "what did visitors actually do?" Foldline answers "what does a visitor actually see before deciding to scroll?" and answers it for pages that have no traffic yet.

Non-goals are as important as goals here. No live visitor data, no continuous monitoring, no team accounts, no client portal, no A/B testing, no CMS or CRM integrations. Every one of those would add surface area and support load without adding a dollar of first-month revenue.

The market signal this plan actually relies on is not a statistic — it is a repeated job. Agencies produce post-launch audits. Foldline compresses the production of that audit from hours to minutes and makes it look like something the agency made, which is why the wedge can be sold in a DM rather than a procurement cycle.

Section 2 of 8

Smallest sellable MVP

Stripe Checkout for one $79 report credit, a URL intake form, an async render-and-score job, and an emailed PDF/HTML Fold Map with five pinned viewports and a ranked fix list.

Must-have features

  • Stripe Checkout with three one-time prices and a webhook that issues report credits
  • URL intake form plus a job status page with polling
  • Playwright render at five viewports (360, 390, 768, 1024, 1440) via Browserless
  • In-page DOM extractor for CTA bounds, fold offset, tap-target size, contrast, form field count and text density
  • 15-check weighted scoring engine with severity levels
  • Annotated screenshot compositor with numbered pins matched to a legend
  • HTML/PDF report builder with prioritized fixes and copy-paste CSS, headline and CTA snippets
  • LLM copy pass strictly constrained to extracted metrics and rule outputs
  • Resend delivery email with PDF attachment and HTML link
  • Logo and colour swap field for pack buyers

Explicitly out of scope

  • No live visitor heatmaps, click tracking or session recordings
  • No JS snippet, SDK or continuous monitoring
  • No A/B testing or experiment platform
  • No white-label client portal or team accounts
  • No CMS, CRM or analytics integrations
  • No subscription billing or usage metering
  • No multi-page crawl or sitewide audit

Demo flow (what the buyer sees)

  1. Buyer clicks a pricing tier and pays through Stripe Checkout
  2. Webhook writes a credit and renders the intake form
  3. Buyer pastes one public URL and optionally uploads a logo
  4. Job queues, Browserless renders five viewports, DOM extractor pulls metrics
  5. Rule engine scores 15 checks and ranks fixes by severity
  6. Sharp composites numbered pins onto each viewport render
  7. LLM writes headline and CTA suggestions constrained to the metrics
  8. PDF and HTML generated, stored, and emailed to the buyer
Build plan

Technical implementation plan

Stack

Next.js 15 on VercelSupabase Postgres and StorageBrowserless (Playwright render + DOM content endpoint)Sharp for screenshot compositingPlaywright Chromium print-to-PDFStripe Checkout and webhooksOpenAI API (gpt-4o-mini) for constrained copy suggestionsResend for delivery email

Architecture

A single Next.js app on Vercel serves the marketing page, intake form and status page. Stripe Checkout creates a payment; a signed webhook writes a credit row and, when the buyer submits a URL, a job row. A queued worker route claims pending jobs, calls Browserless to render five viewports and to return the post-render DOM, then runs the extractor and the 15-check rule engine in-process. Sharp composites numbered pins onto each screenshot using the extractor's element bounds. An LLM call receives only the metric JSON and rule failures, never the raw page, and returns headline and CTA suggestions that are slotted into a fixed template. Playwright prints the composed HTML to PDF, both artifacts land in Supabase Storage, and Resend emails the links. Credits, jobs and artifacts are the only state.

Build steps

  1. Create the Next.js repo, deploy to Vercel, wire env vars and a health endpoint
  2. Create Supabase tables for credits, jobs and artifacts plus a storage bucket
  3. Add Stripe Checkout sessions for single, 5-pack and 10-pack prices
  4. Add the Stripe webhook that issues credits and is idempotent on event id
  5. Build URL intake, validation and a polling status page
  6. Integrate Browserless: five viewport renders plus the rendered DOM
  7. Implement the DOM extractor and persist a metrics JSON per viewport
  8. Implement the 15-check weighted rule engine and severity ranking
  9. Composite numbered pins with Sharp and generate the report HTML
  10. Add the constrained LLM copy pass with a safe fallback template
  11. Print HTML to PDF and email both artifacts via Resend
  12. Add the logo and colour swap fields for pack buyers
  13. Harden with retries, timeouts, partial reports and a re-run credit rule

AI components

  • Constrained copy suggestions for headline and CTA alternatives, generated only from extracted metrics and failed checks
  • Plain-English one-sentence explanation per failed check, templated with a fixed schema
  • No freeform analysis, no page scraping into the model, no autonomous fixing
Hardest technical risk: Bot protection and bot-blocked pages: a paid URL that returns a challenge page instead of the real page produces a useless report and a refund request. Mitigate with a retry policy, a realistic user-agent, a detection check on response body, a visibly partial report, and an automatic free re-run credit.
Section 3 of 8

Pricing and monetization

Single Client Report

Entry offer
$79 one-time

For Freelance designer or small agency owner with one client page to audit

  • One URL report
  • Five viewports
  • PDF and HTML artifact
  • 15-check scorecard
  • Prioritized fix list

Agency 5-Pack

$299 one-time

For Agency owner running audits across multiple clients

  • Five report credits
  • Logo swap
  • Priority queue
  • PDF and HTML artifacts

White-Label 10-Pack

$499 one-time

For Small agency reselling audits as a productized service

  • Ten report credits
  • Custom logo and colour
  • Priority queue
  • PDF and HTML artifacts

Model: One-time report credits sold per URL, with discounted multi-credit packs and a white-label option for resellers.

First revenue offer: A free one-page Fold Map teaser of the prospect's most recent public client page, with three pinned issues, plus: "Full client-ready PDF with all five viewports, the 15-check scorecard and the ranked fix list is $79 — five reports for $299 if you audit clients monthly."

Expected ACV: $79

Upsell path: Buyers move from a $79 single to a $299 five-pack after delivery, and high-volume agencies move from a five-pack to the $499 white-label ten-pack with their own logo and colour on the PDF.

Target customers
30
Revenue model
$2,370
Costs
$90
Profit model
$2,280
Section 4 of 8

First-customer acquisition

Primary channel

Direct LinkedIn and X DMs to agency owners who posted a client launch in the last 7 days, each with a free one-page Fold Map teaser of that public page.

Where to find them

  • Webflow Experts directory, filtered to 1-10 person studios
  • Shopify Partner directory listings with recent case studies
  • X posts containing "just launched" plus a Webflow or Shopify mention in the last 7 days
  • LinkedIn posts from agency owners announcing a client site go-live
  • Dribbble and Behance profiles of studio owners with recent landing-page shots
  • Public "site of the day" style community threads where agency owners post client work

Exact outreach motions

  • Run a free one-page teaser on the prospect's newest public client page and attach it as a PDF
  • DM with a one-line specific finding: mobile CTA sits below the fold at 390px, not a generic pitch
  • Send a 40-second Loom showing the full six-page PDF and the resale angle to any reply
  • Follow up after 48 hours with the 5-pack price and one line about billing it to the client
  • Ask every buyer for one named agency owner introduction in exchange for a free extra report

Message template

Hey [Name] — saw you launched [client site] this week. I ran a quick fold check on it: at 390px the primary CTA sits 210px below the fold and the hero headline wraps to four lines. Free one-pager attached with the three biggest issues. The full version is a six-page PDF — five viewports, a 15-check scorecard, ranked fixes with copy-paste CSS — $79, or $299 for five reports if you audit clients monthly. Want me to run it on [second page]?
Week-one goal: 50 qualified agency prospects listed, 20 free teaser PDFs produced, 20 DMs sent, at least 2 replies.
Section 5 of 8

30-day execution roadmap

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

Accounts and skeleton

  • Create the Next.js repo and deploy to Vercel.
  • Create the Supabase project with credits, jobs and artifacts tables.
  • Open Stripe, create the three one-time prices, connect TrustMRR.

Deliverable: Deployed skeleton URL with live Stripe price IDs.

Day 2Payments

Checkout to credit

  • Build the Stripe Checkout session route for all three tiers.
  • Add an idempotent webhook that writes a credit row.
  • Build URL intake and a polling status page.

Deliverable: Test-mode payment issues a credit end to end.

Day 3Rendering

Five-viewport capture

  • Integrate Browserless screenshot calls for five viewports.
  • Fetch the post-render DOM content for the same URL.
  • Add timeouts, retries and a block-detection check.

Deliverable: Five screenshots plus DOM stored per job.

Day 4Extraction

Metrics

  • Measure CTA bounds, fold offset and tap-target sizes.
  • Measure contrast, form field count and text density.
  • Persist a metrics JSON per viewport.

Deliverable: Metrics JSON validated on three test URLs.

Day 5Scoring

15-check engine

  • Implement the 15 checks with weights and severities.
  • Compute the 0-100 score and rank fixes.
  • Sanity-check outputs against two hand-reviewed pages.

Deliverable: Scorecard JSON for any submitted URL.

Day 6ReportMVP shipped

Artifact

  • Composite numbered pins with Sharp matched to a legend.
  • Build the HTML template and Playwright PDF export.
  • Add the constrained LLM copy pass and Resend delivery.

Deliverable: Full six-page PDF delivered by email for a real URL.

Day 7Go live

Launch and list

  • Flip Stripe to live mode and publish pricing plus a sample report.
  • Build a 50-prospect list from directories and launch posts.
  • Add a refund and re-run policy in plain language.

Deliverable: Live product and a 50-prospect list.

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

Free proof

  • Generate one-page teasers for 20 prospect pages.
  • Save each teaser as a named PDF.
  • Queue the DM copy per prospect.

Deliverable: 20 teaser PDFs ready to send.

Day 9OutreachFirst sale target

First DMs

  • Send 20 personalized DMs with teasers attached.
  • Log every reply and objection in a sheet.

Deliverable: 20 DMs sent, replies logged.

Day 10Packs

Higher ticket

  • Publish the 5-pack and 10-pack checkout links.
  • Add a credit-balance intake form.
  • Add the logo upload field.

Deliverable: Pack SKUs purchasable.

Day 11Proof asset

Demo

  • Record a 40-second Loom of a real Fold Map.
  • Embed the Loom and a sample PDF on the landing page.

Deliverable: Loom and sample live on site.

Day 12Outreach

Second batch

  • Send 20 more DMs to new prospects.
  • Follow up on batch one after 48 hours.

Deliverable: 40 prospects touched.

Day 13Delivery

Fulfilment

  • Deliver every paid report same day and log turnaround.
  • Add a delivery email that states the re-run policy.

Deliverable: Documented same-day delivery process.

Day 14Review

Fix message

  • Measure DM reply and teaser open rates.
  • Rewrite the message template using the best-performing line.
  • Ship a bot-block fallback with user-agent retry.

Deliverable: Revised template and fallback shipped.

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

Third batch

  • Send 30 DMs to a fresh prospect list.
  • Post a build-in-public thread on X about fold checks.
  • List 50 more prospects.

Deliverable: 70 prospects touched cumulatively.

Day 16Follow-up

Warm prospects

  • Send Loom follow-ups to 10 non-repliers.
  • Offer buyers a free re-run on a second page.

Deliverable: 10 Loom follow-ups delivered.

Day 17Referral

Loop

  • Add a referral ask to every delivery email.
  • Ask each buyer for one named agency introduction.

Deliverable: Referral ask live in the delivery flow.

Day 18Robustness

Render success

  • Batch-test 20 render-blocked URLs.
  • Add screenshot fallback and cap job retries.
  • Issue automatic re-run credits on hard failures.

Deliverable: Render success measured on a 20-URL test set.

Day 19Teasers

Scale proof

  • Script teaser generation into one command.
  • Produce 25 teasers and send 25 DMs.

Deliverable: 25 additional teasers and DMs.

Day 20Upsell

Packs

  • Email every single-report buyer the 5-pack offer.
  • Track pack conversion rate.

Deliverable: Upsell email sent and tracked.

Day 21Review

Cut losers

  • Compute replies, sales and profit to date.
  • Drop the weakest message variant.
  • Set the week-four sales target.

Deliverable: Written week-four plan with a target.

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

Fourth batch

  • Send 30 DMs to new prospects.
  • Follow up on the 5-pack upsell.
  • Collect one-line quotes from buyers.

Deliverable: 30 DMs and buyer quotes collected.

Day 23Content

Public proof

  • Publish an anonymized case page with before and after pins.
  • Post it in two communities that permit self-promotion.

Deliverable: Case page live and posted.

Day 24White-label

Top tier

  • Ship logo and colour swap in the PDF template.
  • Offer the 10-pack to two interested agencies.

Deliverable: White-label PDF template working.

Day 25Quality

Defects

  • Audit every delivered report for defects.
  • Fix the top two report bugs and re-issue broken PDFs.

Deliverable: Defect list closed.

Day 26Referral

Introductions

  • Email all buyers asking for a referral.
  • Offer a free report for each named introduction.

Deliverable: Referral emails sent to all buyers.

Day 27Outreach

Final push

  • Send 30 DMs.
  • Re-tease the 15 warmest non-buyers.

Deliverable: 30 DMs and 15 re-touches.

Day 28Review

Numbers

  • Reconcile Stripe payouts inside the hackathon window.
  • Log refunds, fees and net profit.
  • Confirm no unfulfilled credits remain.

Deliverable: Profit ledger for the window.

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

Fulfilment

  • Deliver all outstanding reports.
  • Verify every credit is consumed or refunded.

Deliverable: Zero open credits.

Day 30Wrap

Publish

  • Publish a public 30-day recap with real numbers.
  • Archive sample reports and remove ad-hoc discounts.

Deliverable: Recap post and final ledger.

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

  • Stripe is the payment provider; fees assumed at roughly 4% blended (2.9% + $0.30 per transaction).
  • Conservative: 3 single reports at $79, no packs sold, no paid marketing.
  • Base: 10 sales with a blended ARPU of $95 (mix of singles and one or two 5-packs).
  • Upside: 22 sales with a blended ARPU of $118, one $79 refund, and a $120 test of promoted posts on X.
  • Operating costs cover Vercel, Supabase, Browserless, OpenAI, Resend and domain; all under $120 across the window.
  • No chargebacks assumed in any scenario; refunds modeled only in the upside case.
  • All revenue is projected from outreach volume, not from existing customers or verified traction.
  • Each report costs under two minutes of compute and under $0.35 in API and render spend.

Conservative

3 customers
$237
collected revenue · avg payment $79
Refunds
$0
Chargebacks
$0
Payment fees
$10
Paid marketing
$0
Hackathon profit
$227
Operating costs
$25
Business profit
$202

Base case

10 customers
$950
collected revenue · avg payment $95
Refunds
$0
Chargebacks
$0
Payment fees
$38
Paid marketing
$0
Hackathon profit
$912
Operating costs
$60
Business profit
$852

Optimistic

22 customers
$2,596
collected revenue · avg payment $118
Refunds
$79
Chargebacks
$0
Payment fees
$104
Paid marketing
$120
Hackathon profit
$2,293
Operating costs
$110
Business profit
$2,183

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$790
Payment fees (3.9%)
$31
Paid marketing
$0
Hackathon profit
$759
Business profit
$699

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

All scenarios are projections built from the stated assumptions. They are not verified revenue, not existing customers and not a forecast of results.

Section 7 of 8

Main risks and validation experiments

Risk 1Bot protection blocks rendering, so a paid URL returns a challenge page instead of the real page.

Mitigation

Realistic user-agent, retry policy, response-body detection, visible partial report and an automatic free re-run credit.

Validation experiment

Run the renderer against 20 real agency client pages in week one and count failures.

Kill criteria

If more than 40% of paid URLs fail to render after the fallback ships, change the input model to uploaded screenshots.

Risk 2Cold DM reply rates are too low to reach the sales targets.

Mitigation

Teaser-first DMs with a specific pixel-level finding, 48-hour Loom follow-up, and a rewritten template every 20 sends.

Validation experiment

Send 20 DMs on day 9 and measure reply rate before scaling to 60.

Kill criteria

If fewer than 5% reply after 60 DMs, stop DM volume and switch to a paid community or Loom-first approach.

Risk 3Agencies distrust a static audit compared with real visitor heatmaps.

Mitigation

Position the Fold Map as a pre-launch and post-launch artifact billed to the client, and add an explicit re-run after fixes.

Validation experiment

Ask the first five repliers directly whether they would send this to a client this week.

Kill criteria

If three of the first five conversations demand live visitor data, reposition or stop.

Risk 4LLM fix suggestions come out generic or wrong and damage trust.

Mitigation

Constrain the model to extracted metrics and rule outputs, use fixed templates, and never let it invent measurements.

Validation experiment

Hand-review 10 generated fix lists for factual correctness before launch.

Kill criteria

If more than two of ten fix lists contain a wrong or invented claim, drop the LLM pass and ship template-only copy.

Risk 5One-off pricing kills repeat revenue and the buyer never returns.

Mitigation

5-pack and 10-pack credits, a re-run credit after fixes, and a referral ask in every delivery email.

Validation experiment

Offer the 5-pack to the first three single buyers and record uptake.

Kill criteria

If zero of the first ten buyers take a multi-pack, keep the single price only and stop building pack features.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-3

  • Verify the Stripe account is live and TrustMRR is connected before any customer exists.
  • Create the $79, $299 and $499 one-time prices.
  • Deploy the Next.js skeleton to Vercel with env vars.

Output: Live Stripe prices and a deployed app shell.

Hours 3-7

  • Create Supabase tables for credits, jobs and artifacts.
  • Add a storage bucket for screenshots and PDFs.
  • Build a polling status endpoint.

Output: Working data schema and status endpoint.

Hours 7-12

  • Wire Browserless and render one test URL at five viewports.
  • Confirm screenshot dimensions and file sizes.

Output: Five viewport screenshots stored for one URL.

Hours 12-18

  • Build the DOM extractor and pull metrics for the same URL.
  • Record CTA bounds, fold offset, tap targets, contrast, form fields and text density.

Output: A metrics JSON for the test page.

Hours 18-24

  • Draft the 15-check rule engine and score the test page.
  • Write the DM template and list the first 10 agency prospects.

Output: A first score JSON plus a message template and prospect list.

Complete report

Full 30-day launch report

Read the full generated report

Foldline Report — 30-Day Launch Report

Product: Foldline Report v1 — a landing page URL in, a client-ready Fold Map PDF out. Window: 16 Nov 2026 13:00 UTC to 16 Dec 2026 13:00 UTC. One founder, no team, no funding, no brand. JEV score: 62.3/100, band C. Strongest criterion is speed to first revenue; weakest is monetization potential, which this plan addresses with repeat-purchase packs rather than a subscription.

1. Product opportunity and positioning

Foldline Report sells one artifact: a Fold Map. A designer pastes a landing-page URL, pays, and receives a six-page PDF/HTML report that renders the page at five viewports (360, 390, 768, 1024, 1440), pins every meaningful element visible before the fold, scores the page against 15 deterministic checks, and ranks the fixes so they can be shipped the same day.

The buyer is narrow and identifiable: the owner or lead designer of a 1-10 person web design, Webflow or Shopify agency in the US, UK, Canada or Australia. The trigger is a recurring, emotionally loaded moment. A page goes live, the client asks why it is not converting, and the designer must defend above-the-fold decisions with something stronger than opinion. Today that defence costs two to three hours of manual screenshots plus a subjective write-up the client questions.

Three properties make this survivable for one person in 30 days. There is no integration: no snippet, no SDK, no visitor volume, so a page that launched yesterday with nine visitors can still be audited. There is no trust cycle: the buyer does not have to believe a dashboard, they receive a document they can email to their client. And the artifact is resellable: agencies already bill audits, so Foldline slots into an existing line item rather than creating a new budget conversation.

The weakness JEV flags is real. A $79 one-off is a thin charge. The answer is not a subscription the founder cannot service, but repeat-purchase packs: five credits for $299 and ten for $499 with a logo swap, which create four to six future reports from one satisfied designer and give a legitimate reason to follow up after delivery.

Positioning against the incumbent category is deliberate. Foldline is not a heatmap, not a session recorder, not a click-tracking SDK and not a developer friction API. Those answer "what did visitors actually do?" Foldline answers "what does a visitor see before deciding to scroll?" for pages that have no traffic yet.

2. Smallest sellable MVP

Stripe Checkout for one $79 credit, a URL intake form, an async render-and-score job, and an emailed PDF with five pinned viewports and a ranked fix list. The 15-check engine runs on extracted metrics, not on model judgement, so the same URL produces the same score twice.

Out of scope on purpose: no snippet, no visitor heatmaps, no session recordings, no A/B testing, no client portal, no team accounts, no CMS or CRM integrations, no multi-page crawl. Each would add support load without adding first-month revenue.

3. Technical implementation plan

Next.js on Vercel serves the marketing page, intake and status page. Stripe Checkout writes a credit through an idempotent webhook; submitting a URL creates a job. A worker route claims pending jobs, calls Browserless to render five viewports and return the post-render DOM, then runs the extractor and rule engine in-process. Sharp composites numbered pins using the extractor's element bounds. The LLM receives only metric JSON and failed checks, never the raw page, and fills a fixed template. Playwright prints the composed HTML to PDF; both artifacts land in Supabase Storage and go out via Resend.

The hardest technical risk is bot-blocked URLs producing a useless paid report. Mitigation is a realistic user-agent, retries, response-body detection, a visibly partial report, and an automatic re-run credit. A scripted teaser generator on day 19 turns prospect pages into free one-pagers in a single command.

4. Pricing and monetization

Three one-time SKUs: $79 single report, $299 five-pack, $499 white-label ten-pack. Stripe is the processor, assumed near 4% blended. The first offer sent this week pairs a free one-page teaser with a clear $79 ask and the $299 pack as the second step. Upsell path runs single to five-pack after delivery, five-pack to ten-pack when an agency wants its own logo and colour on the PDF.

5. First-customer acquisition

One channel: LinkedIn and X DMs to agency owners who posted a client launch in the last seven days, each accompanied by a free teaser of that public page. Prospects come from the Webflow Experts and Shopify Partner directories, recent "just launched" posts, and studio profiles on Dribbble and Behance. The DM names a specific measured finding, not a category pitch. Week-one goal: 50 prospects listed, 20 teasers produced, 20 DMs sent, at least two replies.

6. 30-day execution roadmap

Week 1 (days 1-7): accounts, checkout webhook, five-viewport rendering, DOM extraction, the 15-check engine, PDF compositing, live launch and the first 50-prospect list. MVP is live on day 6; outreach starts day 8.

Week 2 (days 8-14): 20 teasers, 20 DMs, pack SKUs and logo upload, a 40-second Loom proof asset, 20 more DMs, same-day delivery discipline, and a message rewrite based on measured reply rates plus a bot-block fallback.

Week 3 (days 15-21): outreach volume to 70 cumulative prospects, Loom follow-ups to non-repliers, referral asks in every delivery email, a 20-URL render robustness test, scripted teaser generation, and a 5-pack upsell to every single buyer.

Week 4 (days 22-28): 30 more DMs, an anonymized public case page, the white-label template, a full defect audit, referral emails, and a Stripe reconciliation of the window.

Days 29-30: close all outstanding credits, publish a public recap with real numbers, archive samples, end ad-hoc discounts.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue or existing customers.

ScenarioCustomersARPUGrossRefundsFeesAd spendOperating
Conservative3$79$237$0$10$0$25
Base10$95$950$0$38$0$60
Upside22$118$2,596$79$104$120$110

Hackathon profit excludes operating costs: $227, $912 and $2,293 respectively. Business profit after hosting, tooling and delivery spend is $202, $852 and $2,183. The conservative case is what three teaser-driven sales look like; the upside requires roughly 600 DMs, two pack buyers and one $120 promoted-post test.

8. Main risks and validation experiments

Bot-blocked renders. Test 20 real agency pages in week one. If more than 40% fail after the fallback, switch to an uploaded-screenshot input model.

Low DM reply rate. Measure after 20 sends, then after 60. If replies stay under 5%, abandon DM volume for a community or Loom-first approach.

Static-audit credibility. Ask the first five repliers whether they would send the PDF to a client this week. If three demand live visitor data, the positioning is wrong.

LLM copy quality. Hand-review 10 fix lists before launch. More than two wrong or invented claims means shipping template-only copy.

One-off pricing. Offer the 5-pack to the first three single buyers. Zero uptake across ten buyers means cutting pack work and keeping the $79 product.

9. First 24 hours

Hours 1-3: verify Stripe live mode and TrustMRR, create the three prices, deploy the app shell. Hours 3-7: Supabase schema, storage bucket, status endpoint. Hours 7-12: Browserless render of one test URL at five viewports. Hours 12-18: DOM extractor metrics for that URL. Hours 18-24: first draft of the 15-check engine, a scored test page, the DM template and the first 10 prospects. By hour 24 the founder should hold a render, a metric JSON, a score and a sendable message — everything except payments proven end to end.

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 →