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

VTC Profit Lens

VTC Profit Lens turns weekly Uber/Bolt/Heetch CSV exports into a one-page true-profit report for independent drivers, showing which platform and shifts actually pay after fuel and 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.

Speculative6.23/10
MVP build (solo)
5 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
French VTC Facebook groups.
Who pays

Independent VTC/ride-hailing drivers in France and Belgium who drive for 2+ platforms, earn €1,500–€4,000/month, and track earnings manually.

Biggest execution risk

Market demand 4.4/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

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

Product opportunity and positioning

Target customer

Independent VTC/ride-hailing drivers in France and Belgium who drive for 2+ platforms, earn €1,500–€4,000/month, and track earnings manually.

Why now

Weekly CSV downloads already exist for taxes; the first paid report can be delivered in 24 hours with no integration or procurement.

Problem

Drivers see gross earnings per app but not net profit after fuel, commission and wear, so they keep accepting low-margin rides.

Solution

Upload CSVs from Uber, Bolt, Heetch or FreeNow, enter fuel price and consumption, pay, and receive a PDF with profit per hour per platform, per shift, Phantom Profit Score and tax-deductible expense summary.

Differentiation · Unlike spreadsheets or gut feel, Profit Lens parses each platform file and calculates real hourly profit per shift, revealing phantom profit and the best platform mix.

Independent VTC drivers in France and Belgium already operate like small businesses: they pay commission, fuel, insurance, maintenance and vehicle wear, but most platforms show only gross earnings. A driver can finish a week with €900 gross on Uber and €600 on Bolt and still not know which platform produced €11/hour versus €17/hour net. That gap is the wedge. VTC Profit Lens sells a single, concrete output: a one-page PDF that converts existing weekly CSV exports into true hourly profit per platform and per shift, with a Phantom Profit Score and a tax-deductible expense summary. The buyer is not a fleet or an accountant; it is an independent driver who drives for two or more platforms, earns €1,500–€4,000/month and already downloads CSVs for taxes. The trigger is a weekly or monthly payout review, not a vague desire for analytics.

JEV scored this concept 62.3/100 (C band). Speed to first revenue is 8.49/10 and solo build feasibility is 7.63/10, which fits a 30-day hackathon. The weak criterion is market demand at 4.36/10, so this plan does not broaden into a platform. It narrows to drivers who can send a CSV today and see a paid report tomorrow. The differentiation is the calculation, not the dashboard: Profit Lens parses each platform file, applies fuel and wear assumptions, and ranks shifts by net profit per hour. A spreadsheet can do this manually; Profit Lens does it in minutes and turns the result into a shareable PDF. No API integration, no rider app, no marketplace and no accounting suite. The first sale can happen in a Facebook group with a sample report and a Stripe link, which is why the concept is sellable before it is scalable.

Section 2 of 8

Smallest sellable MVP

A paid CSV-to-PDF report: driver uploads two to three platform CSVs, enters fuel assumptions, pays $49, receives a branded PDF within minutes.

Must-have features

  • Landing page with sample report PDF and Stripe Checkout
  • CSV upload for Uber, Bolt, Heetch and FreeNow plus manual column mapping
  • Profit engine for commission, fuel, wear per km, per-hour and per-shift profit
  • Phantom Profit Score with top three recommendations
  • PDF generator via React-PDF
  • Resend email delivery with PDF attachment or download link
  • Stripe webhook writes order to Google Sheet
  • In-memory CSV processing with no CSV storage

Explicitly out of scope

  • No mobile app
  • No real-time ride-hailing API integrations
  • No tax filing or accounting
  • No fleet management or multi-user accounts
  • No bank connections
  • No automatic expense categorization beyond fuel and wear
  • No custom dashboard in v1; monthly plan is unlimited reports first

Demo flow (what the buyer sees)

  1. Driver lands on landing page and downloads sample PDF
  2. Driver uploads Uber, Bolt or Heetch CSV files
  3. Driver enters fuel price, consumption and wear per km
  4. System parses rows and calculates net profit per platform and shift
  5. Driver pays $49 through Stripe Checkout
  6. Driver receives PDF by email with Phantom Profit Score and recommendations
Build plan

Technical implementation plan

Stack

Next.jsVercel serverless functionsStripe CheckoutReact-PDFResendPapa ParseRecharts server-side SVGGoogle Sheets APIUpstash Redis optional for idempotency

Architecture

Landing page and upload form run on Next.js. The upload route parses CSVs in memory, normalizes rows into a common trip table, runs the profit engine, renders a PDF, emails it through Resend and writes the order to Google Sheets after Stripe webhook confirmation. CSVs are discarded after PDF generation; only order metadata and anonymized aggregates are logged.

Build steps

  1. Create Next.js repo, deploy placeholder landing on Vercel
  2. Build synthetic CSV fixtures for Uber, Bolt and Heetch
  3. Implement Papa Parse mapping and manual column fallback
  4. Implement profit engine with commission, fuel and wear formulas
  5. Add per-platform and per-shift aggregation
  6. Generate PDF with React-PDF and sample charts
  7. Add Stripe Checkout and success page
  8. Wire Stripe webhook, Resend delivery and Google Sheet log
  9. Run three test purchases in Stripe test mode
  10. Deploy production MVP and publish sample PDF

AI components

  • No LLM in v1. The Phantom Profit Score and recommendations use deterministic rules; an LLM narrative can be added only after validation.
Hardest technical risk: CSV column names vary by country and platform and can break parsing; manual mapping fallback is mandatory before launch.
Section 3 of 8

Pricing and monetization

Single Shift Report

Entry offer
$49 one-time

For Independent drivers who want true profit for a specific week.

  • One PDF report covering one week of data from up to 3 platforms
  • Profit per hour per platform and per shift
  • Phantom Profit Score and recommendations

Monthly Driver

$19 / month

For Drivers who want ongoing tracking.

  • Unlimited reports per month
  • Dashboard with trends
  • Priority email support

Model: One-time $49 Single Shift Report with optional $19/month Monthly Driver for repeat reports.

First revenue offer: Post a free sample report in French VTC groups, then sell the $49 Single Shift Report to drivers who comment or DM; first 5 CSV sharers get a free anonymized sample, not a discount.

Expected ACV: $49

Upsell path: After first report, offer $19/month Monthly Driver for weekly reports and trend dashboard; annual prepay only if requested.

Target customers
25
Revenue model
$1,225
Costs
$75
Profit model
$1,150
Section 4 of 8

First-customer acquisition

Primary channel

French VTC Facebook groups.

Where to find them

  • Chauffeurs VTC France
  • VTC Entraide
  • VTC Belgique and Chauffeurs VTC Bruxelles groups
  • Uber & Bolt driver groups in France and Belgium
  • WhatsApp or Telegram driver groups joined through group admins

Exact outreach motions

  • Join 5 groups and ask admins for promotional permission before posting.
  • Publish before/after post with anonymized Uber vs Heetch sample and free sample offer.
  • DM every commenter within 2 hours with $49 checkout link.
  • Offer free sample to first 5 drivers who share anonymized CSV.
  • Follow up 10 sample requesters by day 13 with paid report link.

Message template

Salut, j'ai analysé mes exports Uber/Bolt et j'ai trouvé environ 3 €/h de bénéfice fantôme après carburant et commission. J'ai créé VTC Profit Lens: tu uploades tes CSV, tu reçois un PDF avec ton vrai profit/heure par plateforme. Échantillon gratuit pour les 5 premiers qui partagent un CSV anonymisé. Ça t'intéresse ?
Week-one goal: By day 7: 5 groups joined, 2 posts approved, 10 sample requests and 5 CSV uploads tested.
Section 5 of 8

30-day execution roadmap

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

Landing and sample

  • Buy domain and create Next.js repo.
  • Draft one-page landing copy with sample PDF CTA.
  • Build a sample PDF from synthetic CSVs.

Deliverable: Live landing page with sample PDF link.

Day 2Parser

CSV fixtures

  • Create synthetic Uber, Bolt and Heetch CSV fixtures.
  • Implement Papa Parse and column mapping fallback.

Deliverable: Parser normalizes fixtures into trips table.

Day 3Profit engine

Calculations

  • Implement commission, fuel, wear per km and per-hour aggregation.
  • Add Phantom Profit Score rule set.

Deliverable: Unit-tested profit engine with fixture outputs.

Day 4Checkout

PDF and Stripe

  • Build React-PDF report with platform and shift charts.
  • Add Stripe Checkout and success page.

Deliverable: End-to-end paid flow works in test mode.

Day 5LaunchMVP shipped

Production MVP

  • Wire Resend PDF delivery and Google Sheet order log.
  • Run 3 test purchases in Stripe test mode.
  • Deploy to production and publish sample report.

Deliverable: MVP live; $49 checkout works.

Day 6Access

Group entry

  • Request to join 5 French and Belgian VTC Facebook groups.
  • Read rules and ask admins for promo permission.

Deliverable: 5 memberships or pending requests; 2 admin conversations.

Day 7Copy

Outreach assets

  • Create before/after post with anonymized sample.
  • Write 3 DM variants for commenters.

Deliverable: Post copy and DM scripts ready.

Week 2 · Launch & first sale · 7 days
Day 8Soft launch

First posts

  • Publish first post in 2 groups with sample PDF.
  • Reply to every comment within 2 hours.

Deliverable: First post live; 10 sample requests.

Day 9First saleFirst sale target

DM and close

  • DM 10 commenters with $49 offer and sample.
  • Manually onboard first CSV uploads.

Deliverable: First paid $49 order target.

Day 10Fulfillment

Deliver and fix

  • Process paid reports within 24 hours and log issues.
  • Fix top parser bug from real CSV.

Deliverable: First PDF delivered; bug fix deployed.

Day 11Proof

Case study

  • Ask buyer to anonymize result as social proof.
  • Post short case in same groups if allowed.

Deliverable: One anonymized case study or testimonial.

Day 12Channel test

More groups

  • Post in 2 more groups and 1 Telegram group.
  • Offer free sample to 5 drivers.

Deliverable: 5 new sample requests; 3 DMs.

Day 13Conversion

Follow-up

  • Follow up all sample requests with $49 checkout link.
  • Track objections in sheet.

Deliverable: Objection list and checkout conversion count.

Day 14Review

Scorecard

  • Review visits, sample requests, paid orders and refunds.
  • Keep or change current message.

Deliverable: Week 2 scorecard.

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

Monthly plan

  • Add $19/month Stripe subscription for repeat reports.
  • Email first buyers with monthly option.

Deliverable: Subscription checkout live; 5 upsell emails.

Day 16Trust

Privacy

  • Add privacy note: CSVs processed in memory and deleted.
  • Add FAQ for GDPR and data handling.

Deliverable: Privacy and FAQ section live.

Day 17Referral

Buyer referrals

  • Add referral code for drivers who share report.
  • Ask 3 buyers to refer one driver.

Deliverable: Referral mechanic live; 3 asks sent.

Day 18Lead magnet

Calculator

  • Publish free phantom profit calculator on site.
  • Post calculator in groups.

Deliverable: Calculator live and shared.

Day 19Outreach

DMs

  • DM 20 drivers who engaged with posts.
  • Offer sample report.

Deliverable: 20 DMs sent; 5 replies.

Day 20Ops

Reliability

  • Automate PDF retry and error alert.
  • Add Stripe webhook idempotency.

Deliverable: Failure handling deployed.

Day 21Review

Best channel

  • Review paid orders and CAC by group.
  • Double down on best group.

Deliverable: Best-channel decision.

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

Best group

  • Publish 3 posts in best group with different angles.
  • Ask admin for pinned post.

Deliverable: 3 posts live; 1 pinned request.

Day 23Creators

Partnership-lite

  • Contact 3 VTC YouTube or TikTok creators for free report review.
  • No paid commitment.

Deliverable: 3 creator emails sent.

Day 24Polish

PDF and parser

  • Improve PDF design and recommendations.
  • Add FreeNow mapping support.

Deliverable: Updated PDF and FreeNow parser.

Day 25Sales

Unpaid checkouts

  • Follow up all unpaid checkouts.
  • Offer monthly plan to repeat users.

Deliverable: 10 follow-ups sent.

Day 26Proof

Case study

  • Turn best buyer result into anonymized PDF case.
  • Post case in 3 groups.

Deliverable: Case study published.

Day 27Referral push

Campaign

  • Email buyers with referral code.
  • Post referral offer in groups.

Deliverable: Referral campaign live.

Day 28Profit review

Stripe reconciliation

  • Calculate hackathon profit from Stripe.
  • Refund unhappy buyer fast if needed.

Deliverable: Profit dashboard and refund log.

Days 29-30 · Consolidate · 2 days
Day 29Final push

Last call

  • Post last-call $49 offer in top 3 groups.
  • DM warm leads.

Deliverable: Final campaign live.

Day 30Close

Reconcile and deliver

  • Reconcile Stripe, TrustMRR and Google Sheet.
  • Deliver any pending reports.
  • Write 30-day recap.

Deliverable: Final verified order list and recap.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • Conservative: 3 paid $49 Single Shift Reports from organic Facebook and Telegram posts; no ads.
  • Base: 10 paid $49 reports, 40% from group posts and 60% from DMs and free samples.
  • Upside: 25 paid $49 reports with optional $100 paid boost; monthly upsell not modeled.
  • Stripe fees assumed at 2.9% + $0.30 per transaction.
  • No refunds in Conservative and Base; Upside includes one $49 refund.
  • Operating costs cover Vercel, domain, Resend, Google Sheets and PDF rendering; no founder salary.
  • Hosting, domains, software and delivery costs are excluded from hackathon profit by contest rules.
  • All figures are projections, not verified revenue or existing customers.

Conservative

3 customers
$147
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$5
Paid marketing
$0
Hackathon profit
$142
Operating costs
$25
Business profit
$117

Base case

10 customers
$490
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$17
Paid marketing
$0
Hackathon profit
$473
Operating costs
$45
Business profit
$428

Optimistic

25 customers
$1,225
collected revenue · avg payment $49
Refunds
$49
Chargebacks
$0
Payment fees
$43
Paid marketing
$100
Hackathon profit
$1,033
Operating costs
$90
Business profit
$943

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$490
Payment fees (3.9%)
$19
Paid marketing
$0
Hackathon profit
$471
Business profit
$426

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.

Projection only: derived from stated assumptions, not verified revenue, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Market demand is the weak JEV criterion at 4.36/10, so drivers may not pay for reports.

Mitigation

Narrow to drivers who already export CSVs for taxes and lead with a sample report, not a dashboard.

Validation experiment

DM 20 drivers asking whether they already export CSVs; count how many have a file ready.

Kill criteria

Fewer than 3 of 20 have a CSV and no one pays after 30 qualified DMs.

Risk 2CSV formats vary and may break parsing for real drivers.

Mitigation

Build manual column mapping and fixture tests before launch.

Validation experiment

Process 10 volunteer CSVs within 48 hours and track failure rate.

Kill criteria

3 of first 10 real CSVs fail after manual mapping; pause outreach and rebuild parser.

Risk 3Drivers may not trust a new tool with financial data.

Mitigation

Process CSVs in memory, delete after PDF, publish a plain-language privacy page.

Validation experiment

Add privacy note and measure sample-request conversion before and after.

Kill criteria

Most sample requesters refuse to upload after reading the privacy explanation.

Risk 4Facebook groups may ban promotional posts.

Mitigation

Ask admins first, use value-first posts and build Telegram/WhatsApp backup.

Validation experiment

Request promo permission in five groups by day 6.

Kill criteria

Four of five groups ban and no alternative channel yields 50 visits.

Risk 5Free sample to paid conversion may be too low.

Mitigation

Ask for the sale directly after delivering sample and track objections.

Validation experiment

Offer $49 checkout to 10 sample requesters and record responses.

Kill criteria

0 paid from 20 sample requesters by day 14; change offer or price.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Buy domain, create Next.js repo and deploy placeholder landing.
  • Add sample PDF CTA.

Output: Live URL and repo.

Hours 3-5

  • Create synthetic Uber, Bolt and Heetch CSV fixtures.
  • Implement parser skeleton with column mapping.

Output: Parser test fixtures.

Hours 6-8

  • Implement profit engine formulas.
  • Generate first sample PDF.

Output: Sample PDF file.

Hours 9-10

  • Add Stripe Checkout test mode.
  • Add Resend delivery stub.

Output: Test checkout flow.

Hours 11-12

  • Draft French group post and 3 DM variants.
  • Request to join 5 VTC groups.

Output: Outreach copy and 5 join requests.

Complete report

Full 30-day launch report

Read the full generated report

VTC Profit Lens — 30-Day Launch Report

This plan is for one solo founder selling one product: a paid CSV-to-PDF report for independent VTC drivers. All revenue figures below are projections built from stated assumptions; they are not verified revenue, customers or traction.

1. Product opportunity and positioning

Independent VTC drivers in France and Belgium already export weekly CSV files from Uber, Bolt, Heetch and FreeNow for taxes. Those files contain trips, gross earnings, commissions and times, but not the number the driver needs: net profit per hour after fuel and vehicle wear. VTC Profit Lens sells that number as a PDF. The buyer is an independent driver on two or more platforms earning €1,500–€4,000/month who tracks earnings manually. The trigger is a weekly payout review. JEV scored the concept 62.3/100 (C band), with speed to first revenue at 8.49/10 and solo build feasibility at 7.63/10; market demand is the weak criterion at 4.36/10. The plan therefore narrows to drivers who can send a CSV today and see a paid report tomorrow. Differentiation is calculation: Profit Lens parses each platform file, applies fuel and wear assumptions, and ranks shifts by net profit per hour. It is not a dashboard, not a tax filer and not a ride-hailing app.

2. Smallest sellable MVP

The smallest sellable MVP is a paid report, not a SaaS platform. A driver lands on a one-page site, downloads a sample PDF, uploads two or three platform CSVs, enters fuel price, consumption and wear per km, pays $49 through Stripe Checkout, and receives a PDF by email within minutes. The PDF shows profit per hour per platform, profit per shift, a Phantom Profit Score, three recommended actions and a tax-deductible expense summary. Must-have: landing page with sample PDF, CSV upload with manual column mapping, profit engine, PDF generator, Stripe checkout, Resend delivery and a Google Sheet order log. Out of scope: mobile app, real-time APIs, bank connections, tax filing, fleet management and user accounts in v1.

3. Technical implementation plan

Stack: Next.js on Vercel, Stripe Checkout, React-PDF, Resend, Papa Parse, Recharts server-side SVG and Google Sheets API. Architecture: the upload route receives files, parses them in memory, normalizes rows into a common trip table, runs the profit engine, renders a PDF, emails it through Resend and writes the order to Google Sheets after the Stripe webhook confirms payment. CSVs are not stored; only order metadata and anonymized aggregate metrics are logged. Build order: fixtures, parser, profit engine, PDF, checkout, email, deploy. The hardest technical risk is CSV variance: column names differ by country and platform. Manual column mapping is mandatory before launch. No LLM is required in v1; the Phantom Profit Score is a deterministic formula so output is reproducible and cheap.

4. Pricing and monetization

Pricing is two tiers. Single Shift Report is $49 one-time for one week of data from up to three platforms, including profit per hour per platform and shift, Phantom Profit Score and recommendations. Monthly Driver is $19/month for unlimited reports, a trend dashboard and priority email support. The first revenue offer is the $49 report, supported by a free sample PDF for the first five drivers who share anonymized CSVs. Do not discount before the first ten sales; the sample is the trust builder. After a paid report, upsell the $19/month plan to drivers who want weekly tracking. Expected ACV for the hackathon is $49 because the first sale is a one-time report.

5. First-customer acquisition

Primary channel: French VTC Facebook groups. Join 'Chauffeurs VTC France', 'VTC Entraide', Belgian VTC driver groups and Uber/Bolt driver groups. Ask admins for promotional permission before posting. Publish a before/after post with an anonymized sample: 'I analyzed my Uber vs Heetch earnings and found I was losing €3/hour on Uber.' Offer a free sample report to the first five drivers who share a CSV. DM every commenter within two hours with the $49 checkout link and a one-line explanation. Week-one goal: five groups joined, two posts approved, ten sample requests and five CSV uploads tested. First paid sale target is day 9, after the MVP is live on day 5.

6. Detailed 30-day execution roadmap

Roadmap in five blocks. Days 1–5: build. Day 1 landing and sample PDF; day 2 parser and fixtures; day 3 profit engine; day 4 PDF and Stripe; day 5 email, order log and production deploy. Days 6–7: group access and outreach copy. Days 8–14: soft launch, first sale, fulfillment, proof and second-channel tests. Days 15–21: monthly upsell, privacy page, referral, free calculator and follow-up. Days 22–28: scale posts in the best group, creator outreach, PDF polish, case study and profit review. Days 29–30: final push, reconcile Stripe with TrustMRR and deliver pending reports. The only hard deadlines are MVP live by day 5 and first sale by day 9. If day 9 passes with no sale, do not add features; run 20 more DMs and ask for the CSV blocker.

7. Revenue and profit scenarios

Scenarios are projections. Conservative: 3 customers × $49 = $147 gross; refunds $0; chargebacks $0; payment fees $5; ad spend $0; operating costs $25. Base: 10 × $49 = $490; fees $17; ad spend $0; operating costs $45. Upside: 25 × $49 = $1,225; one refund $49; chargebacks $0; fees $43; ad spend $100; operating costs $90. Payment fees assume Stripe at 2.9% + $0.30 per transaction. Hackathon profit = gross revenue − refunds − chargebacks − payment fees − ad spend. Business profit = hackathon profit − operating costs. Hosting, domain, software and delivery costs are excluded from hackathon profit by the contest rules. The conservative case is 3 drivers from organic posts; base is 10 drivers from groups plus DMs; upside assumes 25 drivers and one optional paid boost. No scenario assumes existing customers, partnerships or verified revenue.

8. Main risks and validation experiments

Risk 1: market demand is the weak JEV criterion. Test: DM 20 drivers asking whether they already export CSVs; kill or reposition if fewer than 3 have a CSV and no one pays after 30 qualified DMs. Risk 2: CSV formats break parsing. Mitigation: manual mapping fallback and fixture tests. Test: process 10 volunteer CSVs within 48 hours; pause outreach if 3 of 10 fail after mapping. Risk 3: trust and GDPR. Mitigation: in-memory processing, delete files after PDF, privacy page. Test: add privacy note and measure sample-request conversion; kill if most requesters refuse to upload after reading it. Risk 4: Facebook groups ban promotion. Mitigation: ask admins, post value-first, build Telegram/WhatsApp backup. Test: request permission in five groups by day 6; if four ban and no alternative yields 50 visits, change channel. Risk 5: free-to-paid conversion is low. Test: offer $49 checkout to 10 sample requesters; if 0 pay from 20 sample requesters by day 14, change offer or price.

9. First 24-hour action plan

Hours 1–2: buy domain, create Next.js repo, deploy placeholder landing with sample PDF CTA. Hours 3–5: create synthetic Uber, Bolt and Heetch CSV fixtures and parser skeleton. Hours 6–8: implement profit engine formulas and generate first sample PDF. Hours 9–10: add Stripe Checkout test mode and Resend delivery stub. Hours 11–12: draft French group post, three DM variants and request to join five groups. Output by end of day: live URL, sample PDF, test checkout, outreach copy and five join requests.

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 →