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

Intake Proof

Intake Proof turns each garment intake into a signed, photo-pinned condition record PDF, so independent dry cleaners offering pickup and delivery can defend themselves when a customer later claims a stain, hole or tear.

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.29/10
MVP build (solo)
5 days
Launch price
$149
Sales to $1,000 revenue
7 customers
First paying customer
Direct walk-in and phone outreach to independent dry cleaners in one Paris arrondissement that list 'collecte et livraison' on Google Maps, with a live three-minute demo on the owner's own phone.
Who pays

Owner-manager of an independent dry cleaner or pressing with 1-3 shops and 2-12 staff that already advertises 'collecte et livraison' or is about to add it, in Paris, Lyon, Bordeaux, Lille, Nantes or Brussels.

Biggest execution risk

Market demand 4.5/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 11; 7 sales at $149 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

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

0/10
Entry price
$149
Solo build
5 days
30d base revenue
$4,392
30d hackathon profit
$4,067
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-manager of an independent dry cleaner or pressing with 1-3 shops and 2-12 staff that already advertises 'collecte et livraison' or is about to add it, in Paris, Lyon, Bordeaux, Lille, Nantes or Brussels.

Why now

Remote signing links and serverless PDF rendering are cheap enough that a solo founder can ship this in five days, and the buyer is one owner who can approve $149 during a single shop visit with no procurement.

Problem

When a garment leaves the shop on a delivery run, nobody records its condition at handover, so a later claim of an existing stain, tear or moth hole is settled by refund or free re-clean.

Solution

Staff photograph each garment at intake, tap a body-zone map to flag existing defects, and the customer signs on-screen or through an SMS/email link; the app produces one branded PDF per order with photos, defect map, timestamps, signature and order ID, exportable in one tap.

Differentiation · A paper ticket has no photos and no usable timestamps, a WhatsApp album has no signature and no order structure, and a full dry-cleaning POS is integration-heavy and not bought during a counter conversation.

JEV scores this concept 62.9/100 (band C) with speed-to-first-revenue as its strongest criterion (8.4 normalized) and market demand as its weakest (4.49). The plan is shaped by that: almost no money goes into demand creation, and almost all founder time goes into direct, same-day contact with a buyer who can approve a purchase alone.

The gap

Independent cleaners that advertise collecte et livraison have a structural blind spot. The garment leaves the counter on a van, and nobody has recorded what it looked like. Three days later a customer calls about a stain, a pulled seam or a moth hole. The shop has a paper ticket with a squiggle and a phone full of undated photos. The default outcome is a free re-clean or a refund — a recurring cash loss plus an argument with a regular customer.

Who buys

The buyer is the owner-manager of one to three shops with two to twelve staff, in Paris, Lyon, Bordeaux, Lille, Nantes or Brussels. They decide alone, they already feel the dispute moment, and they can pay $149 without a committee. The product is not sold to their customers, and it does not clean, route or deliver anything.

What it replaces

Intake Proof replaces the paper ticket with one signed, photo-pinned, timestamped PDF per order, produced in roughly 90 seconds at intake and exported in one tap when a dispute starts. Remote link signing is the differentiating detail: it still works when the garment already left the counter on the delivery van, which is precisely when a signature matters.

Why the wedge holds

Three properties make this sellable by one person in 30 days. First, the demo runs on the owner's own phone during a normal shop visit — no installation, no integration, no IT contact. Second, the value is legible in one sentence, because every owner has lost this argument. Third, price sits in the range a small business pays immediately, so the sales cycle is a conversation rather than a pipeline.

The honest weak point is demand certainty: the score says owners may see photo intake as slowing counter staff, and some will claim their signed paper ticket is already enough. The 30 days are therefore designed as a sequence of cheap disconfirming tests rather than a campaign — if 15 owner conversations do not surface repeated dispute losses, the concept is changed or dropped before more is spent on it.

Section 2 of 8

Smallest sellable MVP

A mobile web app where a cleaner photographs each garment, taps an existing-defect map, collects a signature, and exports one branded PDF per order — unlocked past three trial orders by a $149 Stripe licence.

Must-have features

  • Mobile web intake: create order, add garments, capture 1-3 phone-camera photos per garment
  • Tap-based defect map per garment type (shirt, trousers, dress, coat) plus free-text note
  • On-screen signature capture and a tokenised remote signing link with 72h expiry
  • Server-side PDF with shop logo, order ID, timestamps, photos, defect map and signature
  • Order history with search by customer name or order ID and one-tap PDF re-export
  • Shop settings: logo upload, shop name, address, default legal disclaimer text
  • Stripe Checkout licence key that unlocks unlimited PDF export after 3 trial orders
  • Resend transactional email for signing links and PDF delivery

Explicitly out of scope

  • Route planning, driver dispatch or delivery tracking
  • POS, accounting or dry-cleaning machine integrations
  • Native iOS or Android apps
  • Customer-facing marketing or booking site
  • Multi-language support beyond French and English
  • Automated dispute arbitration, insurance or claims handling

Demo flow (what the buyer sees)

  1. Owner opens the app on their own phone; founder creates a test order in 20 seconds
  2. Owner photographs a real garment on the counter and sees the photo pinned to the order
  3. Owner taps two defects on the body-zone map and adds a note
  4. Owner signs on-screen, or the founder sends a signing link to the owner's phone by SMS
  5. Founder taps Export and the branded PDF opens with photos, defect map, timestamps and signature
  6. Founder searches the order by customer name and re-exports the same PDF in one tap
  7. Founder shows the Stripe licence screen and the three-order trial counter
Build plan

Technical implementation plan

Stack

Next.js (App Router) mobile-first PWA on VercelSupabase Postgres for shops, orders, garments, defects, signaturesSupabase Storage (EU region) for compressed garment photosStripe Checkout for the one-time licence purchaseResend for signing-link and PDF emails@react-pdf/renderer in a Vercel serverless function for PDF outputUpstash Redis for signing-link token expiry and rate limiting

Architecture

A single Next.js app serves the mobile intake UI and the PDF export endpoint. Supabase holds relational rows for shops, orders, garments, defect flags and signature images, and object storage holds photos at roughly 300KB each. A licence row on the shop gates export after three orders; Stripe Checkout writes the licence through a webhook. Signing links are opaque tokens stored in Redis with a 72-hour TTL and resolved to a minimal sign-only page that needs no account. PDF generation runs in a stateless function that pulls rows and image URLs, composes the document, and streams it back or emails it via Resend.

Build steps

  1. Create Vercel project, Supabase project in EU region, and repo with PWA manifest
  2. Define schema: shops, licences, orders, garments, defects, signatures, audit timestamps
  3. Build intake flow: new order, add garment, client-side image compression to 300KB, upload to storage
  4. Build the defect map component for four garment types with tap targets and notes
  5. Build signature pad component storing a PNG to storage
  6. Build the PDF serverless endpoint rendering logo, order ID, timestamps, photos, defect map and signature
  7. Build order history with search by customer name or order ID and one-tap re-export
  8. Build shop settings for logo, name, address and default disclaimer text
  9. Add Stripe Checkout, webhook licence write and the three-order trial gate
  10. Add Resend emails for signing links and PDF attachments
  11. Add tokenised remote signing page with 72h expiry and rate limiting
  12. End-to-end test on three real Android and iPhone devices over mobile data

AI components

  • None in the critical path: intake, signing and PDF rendering are deterministic. No LLM or vision model is used in the MVP.
Hardest technical risk: Serverless PDF rendering with five to thirty phone photos can blow memory or time out on cold start; the mitigation is mandatory client-side compression, a three-photo-per-garment cap and a 1024MB function that streams images from storage rather than buffering base64.
Section 3 of 8

Pricing and monetization

Shop Licence

Entry offer
$149 one-time

For Owner of an independent cleaner with 1-3 shops

  • Unlimited orders and PDF exports for one shop
  • Remote signing links
  • Branded PDF with shop logo and disclaimer
  • Photo storage for 12 months
  • Email support

Multi-Shop Licence

$349 one-time

For Owner running 2-4 locations

  • Unlimited orders across up to 4 shops
  • Per-shop branding and staff accounts
  • Consolidated order history CSV export
  • Photo storage for 24 months

Model: One-time licence per shop, paid by card through Stripe Checkout, with a three-order free trial before export unlocks.

First revenue offer: Three free intake orders created on the spot during the visit, then a $149 licence link by SMS within 48 hours with their own trial PDF attached.

Expected ACV: $174

Upsell path: Multi-Shop at $349 when the owner opens or reveals a second location, then paid add-ons for branded dispute-letter templates and extended photo retention; no subscription is introduced inside the 30 days.

Target customers
30
Revenue model
$4,470
Costs
$180
Profit model
$4,290
Section 4 of 8

First-customer acquisition

Primary channel

Direct walk-in and phone outreach to independent dry cleaners in one Paris arrondissement that list 'collecte et livraison' on Google Maps, with a live three-minute demo on the owner's own phone.

Where to find them

  • Google Maps listings for 'pressing' and 'teinturerie' in Paris 11e, 12e and 20e filtered for pickup and delivery mentions
  • Google Maps listings in Lyon 3e and 7e with a 'collecte et livraison' line in the description or reviews
  • Shopfronts with a delivery van parked outside or a 'livraison' sticker on the window
  • Local Facebook and WhatsApp groups for pressings and dry cleaners in Ile-de-France
  • Referrals from each paying shop to a neighbouring cleaner outside their catchment area

Exact outreach motions

  • Walk in at 10:00-11:30 when the counter is quiet and ask for the owner by role, not by name
  • Open with the question: 'How do you prove a stain was already there when a client disputes a delivery order?'
  • Ask how many disputes they had in the last six months and what each one cost them
  • Offer to run three free intake orders on their own phone right now with one garment from the rack
  • Send the licence link by SMS 48 hours later with their own trial PDF attached and a one-line price
  • Ask every paying shop for one introduction to a cleaner in a different arrondissement

Message template

Bonjour, je suis passé hier — voici le PDF que nous avons créé ensemble pour votre chemise (pièce jointe). C'est exactement ce que vous envoyez au client quand il conteste une tache. Licence unique 149 € pour la boutique, sans abonnement, et vos trois premières pièces sont déjà faites. Je peux repasser mardi à 10h ?
Week-one goal: 60 qualified cleaners listed across three Paris arrondissements and Lyon, 30 live owner conversations, 10 trials created on the owner's phone, and the app live with Stripe taking payment.
Section 5 of 8

30-day execution roadmap

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

Repo, deployment and data model

  • Create Vercel project and Supabase project in the EU region.
  • Write the Postgres schema for shops, licences, orders, garments, defects and signatures.
  • Ship an empty PWA shell with manifest and mobile viewport.

Deliverable: Deployed skeleton on a live URL with an empty database.

Day 2Intake

Order creation and photo capture

  • Build new-order and add-garment screens.
  • Add camera capture with client-side compression to 300KB.
  • Upload photos to Supabase Storage and render thumbnails.

Deliverable: A real order with three compressed garment photos stored and displayed.

Day 3Defects and signature

Body-zone map and signing pad

  • Build the defect map component for shirt, trousers, dress and coat.
  • Add tap targets with free-text notes per defect.
  • Build the canvas signature pad storing a PNG.

Deliverable: A garment record with two flagged defects and a captured signature.

Day 4PDF

Server-side document rendering

  • Build the PDF function with logo, order ID, timestamps, photos and defect map.
  • Embed the signature image and disclaimer text.
  • Stream the PDF back and email it via Resend.

Deliverable: One branded per-order PDF generated and emailed from a real order.

Day 5MVP freezeMVP shipped

History, settings and search

  • Build order history with search by customer name or order ID.
  • Add one-tap PDF re-export from history.
  • Ship the shop settings page with logo, name, address and disclaimer.

Deliverable: MVP frozen; no new features until the first paid licence.

Day 6Money

Stripe and trial gate

  • Add Stripe Checkout for the $149 and $349 licences.
  • Write the licence webhook and enforce the three-order export gate.
  • Test a live $149 purchase end to end.

Deliverable: A working paid licence flow verified with a real transaction.

Day 7Remote signing

Link signing and consent

  • Build the tokenised signing page with a 72-hour expiry.
  • Add Resend SMS-style email delivery of the signing link.
  • Add French and English consent text about photographing garments and storing signatures.

Deliverable: A garment signed remotely from a phone that never touched the counter.

Week 2 · Launch & first sale · 7 days
Day 8List building

Sixty qualified cleaners

  • Build a spreadsheet of 60 cleaners in Paris 11e, 12e, 20e and Lyon 3e.
  • Flag every listing that mentions collecte et livraison.
  • Record address, owner role, opening hours and counter quiet window.

Deliverable: A 60-row outreach list with quiet-window times.

Day 9Launch

Landing page and first visits

  • Ship a one-screen landing page with a 60-second demo video and the licence button.
  • Walk into 10 cleaners in Paris 11e.
  • Log every objection verbatim in the spreadsheet.

Deliverable: Live sales page plus 10 owner conversations logged.

Day 10Outreach

Ten more contacts

  • Visit 6 cleaners and call 4 in Paris 12e.
  • Run the three-minute demo on any owner who will hold their phone.
  • Create a trial order on the spot for anyone who hesitates.

Deliverable: 10 contacts, at least 3 trials created.

Day 11First saleFirst sale target

Convert the warmest trial

  • Return to the three warmest trials at their quiet window.
  • Send the licence SMS with their own trial PDF attached.
  • Ask for payment on the spot via the Stripe link.

Deliverable: First paid licence collected inside the contest window.

Day 12Follow-up

48-hour SMS sequence

  • SMS every unpaid trial with their PDF and the $149 link.
  • Call back anyone who opened the link but did not pay.
  • Visit 8 new cleaners in Paris 20e.

Deliverable: Every trial contacted twice; at least one conversion from follow-up.

Day 13Onboarding

Make paying shops actually use it

  • Set up logo and disclaimer for each paying shop personally.
  • Run one live intake with their counter staff present.
  • Time the intake and record the median seconds per garment.

Deliverable: Each paying shop has produced at least one real customer PDF.

Day 14Review

Numbers and Lyon list

  • Count contacts, demos, trials, paid licences and objections.
  • Build a 40-row Lyon list from Google Maps.
  • Cut any feature work not tied to a paying shop.

Deliverable: Week-two scorecard and a Lyon outreach list.

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

Phone outreach

  • Call 12 Lyon cleaners between 10:00 and 12:00.
  • Book video demos for any owner who will not meet in person.
  • Log refusal reasons by category.

Deliverable: 12 Lyon calls and at least 2 booked demos.

Day 16Paris expansion

Arrondissements 4-6

  • Visit 10 cleaners in Paris 4e, 5e and 6e.
  • Lead with the dispute question and the median intake time from day 13.
  • Create trials only where the owner is present.

Deliverable: 10 visits and 2 new trials.

Day 17Referrals

Warm introductions

  • Ask every paying shop for one cleaner outside their catchment.
  • Send a one-line intro request the shop can forward.
  • Follow up on all forwarded introductions the same day.

Deliverable: At least 5 named introductions from paying shops.

Day 18Friction

Fix what real intakes expose

  • List the three slowest steps observed during live intakes.
  • Ship fixes for the worst step only.
  • Re-time intake on two devices.

Deliverable: Median intake time reduced and re-measured.

Day 19Upsell

Multi-shop tier

  • Ship the $349 Multi-Shop licence with per-shop branding.
  • Add CSV export of consolidated order history.
  • Offer the upgrade to any owner with two locations.

Deliverable: Multi-Shop tier live and offered to qualified owners.

Day 20New cities

Bordeaux and Lille

  • Call 12 cleaners in Bordeaux and Lille.
  • Use the recorded PDF as the opening attachment in every follow-up email.
  • Book any in-person visit for week four.

Deliverable: 12 calls and a shortlist of in-person visits.

Day 21Operations

Support and onboarding docs

  • Create a support inbox and a one-page onboarding checklist.
  • Add a self-serve FAQ covering compression, signing links and exports.
  • Review revenue and profit inputs against the scenarios.

Deliverable: Support loop documented; revenue checkpoint recorded.

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

Nantes and Brussels

  • Call 12 cleaners in Nantes and Brussels.
  • Offer a same-week trial with a 48-hour deadline.
  • Log which city produces the best answer rate.

Deliverable: 12 calls and a ranked city list by answer rate.

Day 23Sales assets

French demo and objection script

  • Record a French-language 90-second demo video.
  • Write a one-page objection script for price, staff time and paper tickets.
  • Put both on the landing page.

Deliverable: French demo video and objection script published.

Day 24Outreach

Twelve contacts and follow-ups

  • Visit 6 and call 6 cleaners across the best-performing city.
  • Run the full 48-hour SMS follow-up on every open trial.
  • Ask each trial owner for a decision date.

Deliverable: 12 contacts with explicit decision dates recorded.

Day 25Cost control

Storage and quota guard

  • Enforce a three-photo-per-garment cap at upload.
  • Add a storage dashboard per shop and a warning at 80% of quota.
  • Verify average PDF size stays under 3MB.

Deliverable: Storage guard live and cost per shop measured.

Day 26Close

Decision calls

  • Call every open trial and ask for a yes or no.
  • Send the Stripe link during the call, not after.
  • Record every no with its reason.

Deliverable: Every open trial closed as paid or lost.

Day 27Convert

Push the fence-sitters

  • Offer a time-boxed two-shop bundle at $249 to owners with two locations.
  • Re-contact every lost trial with one new proof PDF.
  • Confirm all payments landed in the TrustMRR-connected account.

Deliverable: Final conversions recorded and payments reconciled.

Day 28Review

Double down

  • Rank city and arrondissement by paid conversion.
  • Spend the day only on the best-performing segment.
  • Book in-person visits for days 29 and 30.

Deliverable: Concentration plan for the final two days.

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

Collections

  • Visit every shop that agreed but has not paid.
  • Call all unpaid trials one last time before 13:00 UTC.
  • Fix any last PDF or signing bug blocking a sale.

Deliverable: All pending payments collected or explicitly lost.

Day 30Close books

Verify and document

  • Export the Stripe revenue CSV and reconcile refunds and fees.
  • Confirm every transaction is recorded in the TrustMRR-connected account.
  • Write a one-page post-mortem on conversion, objections and intake time.

Deliverable: Verified profit number and a written post-mortem.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • Conservative: 8 licences from roughly 90 owner conversations, blended ARPU $174 (7 x $149 + 1 x $349).
  • Base: 24 licences from roughly 180 owner conversations, blended ARPU $183 (20 x $149 + 4 x $349), close to the concept's 30-licence target.
  • Upside: 32 licences driven by referrals, blended ARPU $186 (26 x $149 + 6 x $349).
  • Payment processing assumed at 4% of collected revenue via Stripe Checkout on EEA cards, including the one-time licence only.
  • No subscription revenue is modelled in the 30-day window; ARPU is a one-time blended licence value.
  • Paid marketing is near zero because the channel is walk-in and phone outreach; the upside line allows a small sponsored-post test.
  • Operating costs cover Vercel, Supabase (EU), Resend, Upstash and PDF compute for 12 months of compressed photo retention.
  • Refunds and chargebacks are modelled only in the base and upside lines, where volume makes them likely.
  • All figures are projections from stated assumptions, not verified revenue or existing customers.

Conservative

8 customers
$1,392
collected revenue · avg payment $174
Refunds
$0
Chargebacks
$0
Payment fees
$56
Paid marketing
$0
Hackathon profit
$1,336
Operating costs
$40
Business profit
$1,296

Base case

24 customers
$4,392
collected revenue · avg payment $183
Refunds
$149
Chargebacks
$0
Payment fees
$176
Paid marketing
$0
Hackathon profit
$4,067
Operating costs
$90
Business profit
$3,977

Optimistic

32 customers
$5,952
collected revenue · avg payment $186
Refunds
$298
Chargebacks
$149
Payment fees
$238
Paid marketing
$150
Hackathon profit
$5,117
Operating costs
$140
Business profit
$4,977

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$3,576
Payment fees (3.9%)
$139
Paid marketing
$0
Hackathon profit
$3,437
Business profit
$3,347

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.

Scenario models from stated assumptions, not verified revenue. No customers, partnerships or traction are claimed.

Section 7 of 8

Main risks and validation experiments

Risk 1Owners believe photo intake will slow counter staff and refuse adoption.

Mitigation

Cap intake at 90 seconds by compressing images client-side, limiting to three photos per garment, and pre-selecting the garment type from the last order.

Validation experiment

Time five real intakes in two paying shops during week three and record median seconds per garment.

Kill criteria

If median intake exceeds three minutes after five shops, simplify the flow to a single photo plus signature before continuing outreach.

Risk 2Owners already use a signed paper ticket and do not feel the dispute cost.

Mitigation

Lead every conversation with the dispute question and quantify the loss in euros before showing any software.

Validation experiment

Ask fifteen owners how many condition disputes they had in the last six months and what each cost.

Kill criteria

If fewer than three of fifteen owners report a dispute in six months, stop outreach and re-scope the buyer or abandon the concept.

Risk 3Live demos do not convert into paid licences.

Mitigation

Create the trial on the owner's own phone during the visit and send the licence link within 48 hours with their own PDF attached.

Validation experiment

Track demos, trials and paid licences daily through day 14 and compute conversion per city.

Kill criteria

If zero licences are paid after twenty live demos by day 14, move to a $19 monthly price or stop the concept.

Risk 4Photo storage and PDF compute costs grow faster than revenue per shop.

Mitigation

Enforce a three-photo cap, compress to 300KB, set a 12-month retention policy and monitor average PDF size weekly.

Validation experiment

Measure cost per shop per month after the first five paying shops reach twenty orders each.

Kill criteria

If measured operating cost per shop exceeds 20% of the licence price, reprice or reduce retention.

Risk 5French data-protection expectations around photographing garments and storing signatures.

Mitigation

Add explicit consent text in French and English, keep Supabase in the EU region, and auto-delete photos at 12 months.

Validation experiment

Put the consent text in front of three owners and ask whether their staff would accept it at the counter.

Kill criteria

If owners object to the consent step in more than half of conversations, remove signature storage and keep photo-only records.

Risk 6One founder cannot sustain ten outreach contacts a day while building and supporting.

Mitigation

Batch outreach 10:00-12:30 and build or support 14:00-18:00, with no feature work after day 5 except blockers to a sale.

Validation experiment

Log actual contact counts daily and compare against a planned ten per day.

Kill criteria

If daily contacts fall below six for three consecutive days, cut to three cities and protect the outreach block.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and create the Vercel and Supabase projects in the EU region.
  • Initialise the Next.js repo with a PWA manifest and mobile viewport.

Output: A deployed skeleton URL and a live empty database.

Hours 3-5

  • Write the Postgres schema for shops, licences, orders, garments, defects and signatures.
  • Create the storage bucket and its access policies.

Output: Migrated schema and a working storage bucket.

Hours 6-9

  • Build the new-order and add-garment screens.
  • Add camera capture with client-side compression to 300KB and upload.

Output: A real order with three compressed garment photos visible on a phone.

Hours 10-12

  • Build a 40-row Paris cleaner list from Google Maps filtered for collecte et livraison.
  • Record quiet-window hours and street addresses for the first 10 visits.

Output: An outreach list ready for the morning of day 9.

Hours 13-14

  • Write the landing page copy and the dispute opening question.
  • Draft the French SMS follow-up template.

Output: Landing copy and outreach scripts ready to send.

Complete report

Full 30-day launch report

Read the full generated report

Intake Proof — 30-day launch report

1. Product opportunity and positioning

Independent dry cleaners that advertise collecte et livraison have a structural blind spot. The garment leaves the counter on a van and nobody has recorded what it looked like. Three days later a customer calls about a stain, a pulled seam or a moth hole. The shop has a paper ticket with a squiggle and a phone full of undated photos. The default outcome is a free re-clean or a refund: a recurring cash loss plus an argument with a regular customer.

Intake Proof sells to the owner who feels that loss, not to the customer. It replaces the paper ticket with one signed, photo-pinned, timestamped PDF per order, produced in about 90 seconds at intake and exported in one tap when a dispute starts. The wedge is deliberately narrow: one shop, one counter, one handover moment. Intake Proof does not schedule pickups, dispatch drivers or clean anything.

The alternatives are each broken in a specific way. A paper ticket carries no photos and no usable timestamps. A WhatsApp album carries no signature and no order structure. A full dry-cleaning POS is expensive and integration-heavy, and no owner buys one during a counter conversation. Intake Proof is mobile web, needs no installation, and can be demonstrated live on the owner's own phone in three minutes. Remote link signing is the differentiating detail: it still works when the garment already left the counter on the delivery van, which is exactly when a signature is most needed.

JEV scores this concept 62.9/100 (band C), with speed-to-first-revenue as the strongest criterion (8.4 normalized) and market demand as the weakest (4.49). The plan is shaped by that: almost no money goes into demand creation, and almost all founder time goes into direct, same-day contact with a buyer who decides alone.

2. Smallest sellable MVP

Seven things, no more: a mobile intake flow with phone-camera capture, a tap-based defect map for four garment types, an on-screen signature plus a tokenised remote signing link with 72-hour expiry, a branded server-rendered PDF, searchable order history with one-tap re-export, a shop settings page for logo and disclaimer, and a Stripe licence that unlocks export after three trial orders.

Explicitly excluded: route planning, driver dispatch, POS or accounting integrations, native apps, a customer booking site, languages beyond French and English, and any automated dispute arbitration. MVP freeze is day 5. After that, nothing ships unless it blocks a sale.

3. Technical implementation plan

Next.js App Router as a mobile-first PWA on Vercel. Supabase Postgres for shops, orders, garments, defects and signatures, with Cloudflare-free EU-region storage for compressed photos. Stripe Checkout writes the licence through a webhook. Resend delivers signing links and PDFs. @react-pdf/renderer runs in a stateless function. Upstash Redis holds signing tokens with a 72-hour TTL.

Build order: schema, intake and capture, defect map, signature pad, PDF endpoint, history and search, settings, Stripe gate, Resend, remote signing, then device testing on real Android and iPhone over mobile data.

The hardest technical risk is serverless PDF rendering with up to thirty phone photos: memory and cold-start timeouts. Mitigation is mandatory client-side compression to 300KB, a hard cap of three photos per garment, and a 1024MB function that streams images from storage instead of buffering base64. There is no model in the critical path; intake, signing and rendering are deterministic.

4. Pricing and monetization

Shop Licence at $149 one-time for one shop; Multi-Shop Licence at $349 one-time for up to four locations with per-shop branding and CSV export. Both are card payments through Stripe Checkout. Three free orders precede any charge, so the owner experiences the output before seeing a price.

The first revenue offer is concrete: three intake orders created on the spot during the visit, then a $149 licence link by SMS within 48 hours with the shop's own trial PDF attached. No subscription inside the 30 days, because "149 € une fois, sans abonnement" is a sentence an owner can approve without thinking about churn. ARPU blends the two tiers at roughly $174-$186 depending on how many owners reveal a second location.

5. First-customer acquisition

One channel: walk-in and phone outreach to cleaners in one Paris arrondissement that list collecte et livraison on Google Maps, with a live demo on the owner's own phone.

The list is built from Google Maps for Paris 11e, 12e and 20e plus Lyon 3e, filtered on pickup-and-delivery language. Ten contacts a day, at the counter quiet window between 10:00 and 11:30. The opening line is a question, not a pitch: "How do you prove a stain was already there when a client disputes a delivery order?" Then: how many disputes in six months, and what did each cost? Only after that does the phone come out. Trials are created on the spot. Every unpaid trial gets an SMS at 48 hours carrying their own PDF and the licence link. Every paying shop is asked for one introduction to a cleaner outside their catchment area.

6. 30-day execution roadmap

Week 1 (days 1-7), build. Days 1-5 take the product from empty repo to frozen MVP: schema, intake and capture, defect map and signature, PDF rendering, history and settings. Day 6 wires Stripe and the three-order gate and verifies a live $149 transaction. Day 7 ships remote signing with 72-hour expiry plus French and English consent text for photographing garments and storing signatures.

Week 2 (days 8-14), launch and sell. Day 8 builds the 60-row list with quiet-window times. Day 9 ships the landing page with a 60-second demo video and starts ten visits. Days 10-13 run ten contacts a day, create trials on the owner's phone, follow up at 48 hours and onboard paying shops personally, timing real intakes. First paid licence is targeted for day 11. Day 14 is the scorecard.

Week 3 (days 15-21), expand and fix. Lyon by phone, Paris 4e-6e in person, referrals from every paying shop, one friction fix driven by observed intake times, and the $349 Multi-Shop tier with CSV export. Bordeaux and Lille calls close the week.

Week 4 (days 22-28), close. Nantes and Brussels calls, a French demo video and objection script, decision calls on every open trial, storage quota guard, and a concentration shift onto the best-converting city.

Days 29-30, collect and verify. Visit every shop that agreed but has not paid, call all unpaid trials before 13:00 UTC, reconcile the Stripe export, confirm every transaction sits in the TrustMRR-connected account, and write the post-mortem.

7. Revenue and profit scenarios

All three scenarios are projections built from the assumptions listed alongside them. No customers, revenue or traction exist today.

Conservative: 8 licences, blended ARPU $174, gross $1,392, with 4% Stripe fees of $56 and $40 of operating cost. Base: 24 licences, ARPU $183, gross $4,392, one $149 refund, $176 fees, $90 operating cost. Upside: 32 licences driven by referrals, ARPU $186, gross $5,952, $298 refunds, $149 chargeback, $238 fees, $150 of paid marketing, $140 operating cost.

Because hosting and AI/API delivery costs are excluded from the contest ranking but not from the business, the gap between hackathon profit and business profit is small here: roughly $40 to $140 across the three cases. That is the point of the stack choice.

8. Main risks and validation

The first risk is speed at the counter. Owners fear photo intake slows staff. The test is timing five real intakes in two paying shops; if the median exceeds three minutes, simplify to one photo plus signature before continuing.

The second is that the pain is not real. Fifteen owners are asked how many disputes they had in six months and what each cost. If fewer than three report any, outreach stops and the concept is re-scoped or dropped.

The third is conversion. If twenty live demos by day 14 produce zero paid licences, the offer moves to a $19 monthly price or the concept stops. Storage economics and French data-protection expectations are the two secondary risks, tested by measuring cost per shop after five shops reach twenty orders, and by putting the consent copy in front of three owners during week one.

9. First 24 hours

Hours 1-2: domain, Vercel and Supabase in the EU region, Next.js repo with PWA manifest. Hours 3-5: schema, storage bucket, access policies. Hours 6-9: intake screens, camera capture, client-side compression, upload. Hours 10-12: a 40-row Paris cleaner list with quiet windows and addresses. Hours 13-14: landing copy, the dispute opening question, and the French SMS template. By the end of day one there is a deployed skeleton holding one real order with three photos, and a list to walk on day nine.

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 →