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

Chasseur Brief

Chasseur Brief turns raw property listing URLs into a branded, client-ready shortlist PDF in minutes for independent property hunters.

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.25/10
MVP build (solo)
5 days
Launch price
$149
Sales to $1,000 revenue
7 customers
First paying customer
LinkedIn outreach to French property hunters, in French.
Who pays

Independent property hunters (chasseurs immobiliers) in France, solo or 2-5 person firms, managing 5-20 active buyer clients, who compile weekly client reports by hand.

Biggest execution risk

Monetization potential 4.8/10

Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 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

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

0/16
Entry price
$149
Solo build
5 days
30d base revenue
$1,788
30d hackathon profit
$1,699
Section 1 of 8

Product opportunity and positioning

Target customer

Independent property hunters (chasseurs immobiliers) in France, solo or 2-5 person firms, managing 5-20 active buyer clients, who compile weekly client reports by hand.

Why now

LLM summarisation is cheap enough to run per listing and PDF rendering is a solved library problem, so one founder can ship the whole workflow in five days instead of a quarter.

Problem

Each week the hunter copies listing details, photos and notes into a document for every client, costing one to two hours per client and producing an unprofessional artifact.

Solution

A web app: create a client brief, capture listings with a bookmarklet or CSV, get a 0-100 match score per property, download a branded PDF shortlist with cover page, property cards and notes.

Differentiation · It is the report machine, not a CRM, not a portal feed, not a buyer marketplace. It outputs the one artifact a hunter already sends every week, in their own branding, from links they already have.

1. Product opportunity and positioning

Chasseur Brief is a web app for independent property hunters (chasseurs immobiliers) in France — solo operators and 2-5 person firms running 5-20 active buyer clients. The search side of their work is not where the hours disappear. The report is. Every week, for every client, they copy titles, prices, surface areas, photos and notes out of SeLoger, Bien'ici or PAP into a Word file, then email a PDF. At ten clients that is ten to twenty hours a week of unpaid production work, and it is the moment a hunter looks least like the professional their success fee implies.

Chasseur Brief collapses that into minutes. The hunter creates a client brief (budget, areas, property type, must-have keywords, deal-breakers), captures listings with a bookmarklet or a CSV upload, and the app scores each property 0-100 against the brief and renders a branded shortlist: cover page with the hunter's logo, property cards with photo, price, score badge and an editable notes block. The hunter downloads the PDF and sends it under their own name.

Positioning is deliberately narrow: it is the report machine, not a CRM, not a portal feed, not a buyer marketplace. The original business sold hunting to buyers; this sells the output of hunting to the hunters themselves.

JEV scored this exact concept 62.5/100 (band C, confidence 0.70). The strongest criterion is speed to first revenue at 8.4/10 — the product either produces a PDF worth sending or it does not, and a solo hunter decides alone on $149. The weakest is monetization at 4.82/10, because a single one-time charge has no expansion path. The plan answers that without changing the model: price against hours saved, make referrals the growth loop, and hold a higher price for the cohort after the contest rather than repricing mid-window.

The wedge is chosen for reachability, not for size. Hunters are identifiable by job title on LinkedIn, they already pay for tools, and they have a recurring weekly deadline that makes the pain concrete. One PDF demonstrates the value in under two minutes.

Section 2 of 8

Smallest sellable MVP

A paid web app where a hunter creates one client brief, captures three real listing URLs, scores them, and downloads a branded PDF shortlist with a cover page, property cards and notes.

Must-have features

  • Client brief form: budget, location, property type, must-have keywords, deal-breakers
  • Bookmarklet that captures title, price, address, size, rooms, description and image URL into the app
  • CSV upload mapped to the same listing schema
  • Rule-based 0-100 match score from budget, location, keywords and deal-breakers
  • Branded PDF: logo, cover page, property cards with image and score, editable notes
  • Stripe checkout at $149 one-time gating dashboard access
  • Dashboard listing clients and generated reports

Explicitly out of scope

  • No server-side scraping of portals
  • No CRM or pipeline management
  • No email sending or scheduling from the app
  • No mobile app
  • No multi-user teams or permissions
  • No market analytics or price indices

Demo flow (what the buyer sees)

  1. Hunter signs up and pays $149 via Stripe Checkout
  2. Hunter creates a client brief with budget, areas, keywords and deal-breakers
  3. Hunter drags the bookmarklet onto a listing page on SeLoger, Bien'ici or PAP and clicks it
  4. Capture panel shows the extracted fields for confirmation and editing
  5. Listing is saved and scored 0-100 against the brief
  6. Hunter repeats for two more listings, or uploads a CSV
  7. Hunter clicks Generate and downloads the branded PDF shortlist
Build plan

Technical implementation plan

Stack

Next.js 14 (React) on VercelTailwind CSSSupabase Postgres, auth and storage for logos and imagesStripe Checkout in live mode@react-pdf/rendererVanilla-JS bookmarklet posting to a single API routeOpenAI gpt-4o-mini for two-sentence description summaries

Architecture

The Next.js app on Vercel serves the dashboard and one capture endpoint. Supabase holds clients, listings, reports and logos, and enforces row-level access per user. The bookmarklet is a small script the hunter drags to their bookmarks bar; on click it extracts fields from the current page and POSTs them to the capture endpoint with the user's token. Scores are computed synchronously in the API route. PDF generation happens server-side with @react-pdf/renderer, streams back as a download and is stored in Supabase storage for re-download. Stripe Checkout creates a one-time $149 payment; a webhook flips the user record to paid and the dashboard gate reads that flag.

Build steps

  1. Create Next.js repo, Tailwind, deploy skeleton to Vercel
  2. Create Supabase project with auth, database and a logos bucket
  3. Create clients, listings and reports tables with row-level security
  4. Build client brief form and dashboard list
  5. Build /api/capture accepting the listing payload and validating it
  6. Write bookmarklet with JSON-LD, meta-tag and page-text extraction layers
  7. Add capture confirmation and edit panel before saving
  8. Implement rule-based scoring engine
  9. Build @react-pdf/renderer template: cover, cards, score badge, notes
  10. Add Stripe Checkout and webhook gate
  11. Run end-to-end with three real listing URLs and deploy to the production domain

AI components

  • OpenAI gpt-4o-mini generates a two-sentence plain-language summary of each listing description, cached per listing and capped per report
Hardest technical risk: The bookmarklet. French portals change markup and some render listings client-side, so a capture that silently returns empty fields destroys trust in one click.
Section 3 of 8

Pricing and monetization

Founding Hunter

Entry offer
$149 one-time

For Independent property hunters in France, solo or 2-5 person firms

  • Lifetime access
  • Unlimited client profiles and reports
  • Custom branding on PDFs (logo, accent colour)
  • Bookmarklet for listing capture plus CSV upload
  • Email support

Model: Single one-time $149 founding membership with lifetime access, no subscription.

First revenue offer: Founding Hunter at $149 one-time, lifetime access, offered to the first 20 hunters who reply on LinkedIn, with a sample PDF and a 90-second Loom sent before the payment link.

Expected ACV: $149

Upsell path: Referrals first: every buyer is asked for one named hunter. Revenue grows later by offering the next cohort a higher one-time price rather than repackaging mid-contest.

Target customers
20
Revenue model
$2,980
Costs
$103
Profit model
$2,877
Section 4 of 8

First-customer acquisition

Primary channel

LinkedIn outreach to French property hunters, in French.

Where to find them

  • LinkedIn search 'chasseur immobilier' filtered to Paris
  • LinkedIn search 'chasseur immobilier' filtered to Lyon and Bordeaux
  • LinkedIn search 'chasseur immobilier indépendant'
  • Hunters posting client-facing content or listing commentary on LinkedIn
  • Names referred by paying buyers
  • Comment threads under French real-estate posts where hunters are visibly active

Exact outreach motions

  • Build a 50-row sheet with profile URL, city and firm size before sending anything
  • Send 20 personalised connection requests per working day, roughly 215 across the window
  • On acceptance, send the Loom plus a sample PDF built on a fictional client
  • Offer the $149 founding price immediately to anyone replying with interest
  • 48-hour follow-up with a two-line reminder and the sample PDF
  • Ask every buyer for one named hunter introduction after their first generated report

Message template

Bonjour [Prénom], je vois que vous êtes chasseur immobilier à [ville]. J'ai créé un outil qui transforme vos liens d'annonces en un PDF client prêt à envoyer en 2 minutes. Je cherche 5 chasseurs pour tester cette semaine — ça vous intéresse ?
Week-one goal: MVP live by day 5, sales kit (Loom plus sample PDF) done by day 7, 40 connection requests sent by day 7.
Section 5 of 8

30-day execution roadmap

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

Mon 16 Nov: repo, hosting, Stripe live, TrustMRR

  • Create Next.js and Tailwind repo, deploy to Vercel.
  • Create Supabase project with email auth and a logos bucket.
  • Create the $149 one-time Stripe product in live mode.
  • Connect the Stripe account to TrustMRR before any charge.

Deliverable: Deployed skeleton with login and a live $149 checkout link.

Day 2Client brief

Data model and form

  • Create clients, listings and reports tables with row-level security.
  • Build the brief form: budget, location, type, keywords, deal-breakers.
  • Add the dashboard client list.

Deliverable: A hunter can create, edit and delete a client brief.

Day 3Capture

Bookmarklet and CSV

  • Build /api/capture for title, price, address, size, rooms, description and image URL.
  • Write the bookmarklet: JSON-LD first, meta tags second, page text third.
  • Add CSV upload mapped to the same schema.
  • Show a confirm-and-edit panel before saving.

Deliverable: Real listing URLs and CSVs land inside a client record.

Day 4Score and PDF

Scoring engine and template

  • Implement the 0-100 rule-based score from budget, location, keywords, deal-breakers.
  • Build the PDF template: cover, cards, score badge, notes block.
  • Add the cached OpenAI two-sentence summary.
  • Upload a logo and render it on the cover.

Deliverable: A branded shortlist PDF from a client with three listings.

Day 5MVP liveMVP shipped

Payment gate and end-to-end run

  • Gate dashboard access on a paid Stripe session.
  • Run one full pass with a fictional client and real links.
  • Fix layout breaks and deploy to the production domain.

Deliverable: MVP live at a public URL with one report generated end to end.

Day 6Hardening

Portal fixtures

  • Save HTML fixtures from SeLoger, Bien'ici and PAP for extraction tests.
  • Add fallback selectors and a clear edit-fields error path.
  • Time PDF generation against a 10-second budget.

Deliverable: Extraction test set plus a documented CSV fallback.

Day 7Sales kit

Proof assets

  • Record a 90-second Loom on a fictional client.
  • Export a sample PDF with a clearly fictional client name.
  • Write the landing page: promise, sample PDF, $149 offer.

Deliverable: Loom, sample PDF and live landing page with checkout.

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

50 hunters

  • Search LinkedIn for 'chasseur immobilier' in Paris, Lyon, Bordeaux, Nantes.
  • Collect 50 independent hunters with profile URL and city.
  • Filter for solo or 2-5 person firms.

Deliverable: A 50-row outreach sheet.

Day 9First wave

20 requests

  • Send 20 connection requests with the personalised French note.
  • Log the send date for each row.

Deliverable: 20 requests sent and logged.

Day 10Second wave and demos

40 requests, send the Loom

  • Send 20 more connection requests.
  • Send the Loom and sample PDF to everyone who accepted.
  • Reply to any question within two hours.

Deliverable: 40 requests sent; all acceptances have the demo.

Day 11Conversations

Qualify and offer

  • Send 15 more connection requests.
  • Offer the $149 founding price to anyone replying with interest.
  • Answer objections with the one-hour-per-client-per-week anchor.

Deliverable: First batch of Stripe links sent to warm leads.

Day 12First revenueFirst sale target

Close

  • Follow up every warm lead with a two-line reminder and the sample PDF.
  • Ask the three warmest leads for payment today.
  • Onboard any buyer personally within the hour.

Deliverable: First paying customer (target) and a personal onboarding checklist.

Day 13Volume

Replies and referrals

  • Send 20 more connection requests.
  • Ask each buyer for one hunter they know.
  • Run the 48-hour follow-up on all unanswered threads.

Deliverable: A pipeline of open replies plus referral names.

Day 14Week review

Metrics

  • Measure requests sent, acceptance rate, replies and sales.
  • Rewrite the note if acceptance is under 30%.
  • Fix the top support issue reported by buyers.

Deliverable: Updated message and a one-page metrics sheet.

Week 3 · Repeat & systematize · 7 days
Day 15Second angle

Re-target non-responders

  • Message day-8 non-responders with a new angle: two minutes per client report.
  • Attach a screenshot of the PDF cover.

Deliverable: Second-touch sequence live for every non-responder.

Day 16Reliability

Bookmarklet fixes

  • Patch the selectors buyers reported broken.
  • Improve the manual-edit fallback copy.
  • Ship a short changelog note to buyers.

Deliverable: Extraction success rate improved on real user links.

Day 17Proof on LinkedIn

Public post

  • Publish one French LinkedIn post: before and after of a weekly client report.
  • Reply to comments with the sample PDF link.
  • Send 20 requests referencing the post.

Deliverable: One post live plus 20 attributed requests.

Day 18Cost check

Unit economics

  • Measure OpenAI cost per generated report.
  • Cap summaries per report and cache aggressively.
  • Confirm delivery cost per report stays under $0.05.

Deliverable: Documented cost per report.

Day 19Volume

30 requests

  • Send 30 connection requests.
  • Follow up every open thread.

Deliverable: 125+ cumulative requests sent.

Day 20Onboarding

Activation

  • Send each buyer a one-paragraph start guide.
  • Voice-note the two least active buyers.
  • Track first-report-generated per buyer.

Deliverable: Every paying buyer has generated at least one report.

Day 21Mid-point review

Decide the last nine days

  • Compare actual sales against the conservative scenario.
  • Decide: push volume, or fix activation first.
  • Update the outreach note with the best-performing line.

Deliverable: A written decision and a revised plan for days 22-30.

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

30 requests

  • Send 30 connection requests.
  • Ask two buyers for a written testimonial.

Deliverable: Testimonials captured from paying buyers, or none claimed at all.

Day 23Template value

Second PDF style

  • Ship a second cover and card style.
  • Let buyers choose an accent colour from their logo.

Deliverable: Two selectable PDF styles.

Day 24Referral loop

Ask with an asset

  • Send each buyer a forwardable one-pager about Chasseur Brief.
  • Ask for one introduction with no strings attached.

Deliverable: Forwardable one-pager distributed to every buyer.

Day 25Volume

30 requests

  • Send 30 connection requests.
  • Follow up every unanswered thread.

Deliverable: 185+ cumulative requests sent.

Day 26Performance

Speed and support

  • Reduce PDF generation below five seconds.
  • Write five canned answers to recurring questions.

Deliverable: Faster PDFs and a support macro sheet.

Day 27Deadline offer

Founding cohort closes 16 Dec

  • Message every warm lead that the founding price closes with the cohort.
  • State the exact date in the message.

Deliverable: Deadline message sent to every open lead.

Day 28Final volume

Last outreach

  • Send the final 30 connection requests.
  • Follow up twice on the warmest leads.

Deliverable: 215+ cumulative requests; list exhausted.

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

Last payments before cutoff

  • Voice-note every open lead.
  • Take payment before 16 Dec 13:00 UTC.
  • Stop selling when the window closes.

Deliverable: All closable deals closed inside the window.

Day 30Reconcile

Numbers and changelog

  • Reconcile Stripe payouts against TrustMRR.
  • Export revenue, refunds and fee inputs for the final profit figure.
  • Publish a short changelog and a thank-you to buyers.

Deliverable: Final numbers sheet and a post-launch changelog.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • All scenarios: price is $149 one-time; no subscription revenue is assumed.
  • All scenarios: payment processing assumed at 4.5-5.5% of collected revenue (Stripe plus USD/EUR conversion and international cards).
  • Conservative: LinkedIn response is slow and only 4 hunters buy; no paid marketing.
  • Base: 12 hunters buy, roughly consistent with 215 outreach messages and the demo-on-acceptance flow; no paid marketing.
  • Upside: 25 hunters buy with one refund; $120 of paid marketing is used only to boost the last week.
  • Operating costs cover Vercel, Supabase, domain and OpenAI delivery cost for the reports those customers generate.
  • Refunds and chargebacks are assumed near zero because the price is low and the buyer uses the product within minutes.

Conservative

4 customers
$596
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$27
Paid marketing
$0
Hackathon profit
$569
Operating costs
$30
Business profit
$539

Base case

12 customers
$1,788
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$89
Paid marketing
$0
Hackathon profit
$1,699
Operating costs
$55
Business profit
$1,644

Optimistic

25 customers
$3,725
collected revenue · avg payment $149
Refunds
$149
Chargebacks
$0
Payment fees
$194
Paid marketing
$120
Hackathon profit
$3,262
Operating costs
$95
Business profit
$3,167

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,788
Payment fees (3.9%)
$70
Paid marketing
$0
Hackathon profit
$1,718
Business profit
$1,663

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 exist yet and no payment has been collected.

Section 7 of 8

Main risks and validation experiments

Risk 1LinkedIn response rate is too low to produce a sale inside 30 days.

Mitigation

Two message angles, 215+ sequenced sends, and referral asks to every buyer.

Validation experiment

Send 20 requests on day 9 and measure acceptance and replies within 72 hours.

Kill criteria

If 200 requests and 30 demos produce zero payments by day 24, the channel or the concept is wrong and the plan stops spending on outreach.

Risk 2The bookmarklet breaks on portal markup changes and captures nothing.

Mitigation

Three extraction layers, a confirm-and-edit panel, and CSV upload as a permanent fallback.

Validation experiment

Run 20 real portal URLs through capture on day 6 and count usable title, price and image.

Kill criteria

Below 70% usable extraction across three layers: make CSV the default entry path and reposition as CSV to branded PDF.

Risk 3Hunters do not value the PDF and see the tool as another CRM they do not need.

Mitigation

Demo only the PDF output, never the dashboard, and lead with the hours-saved anchor.

Validation experiment

Track Loom-to-reply and demo-to-payment ratios from day 10 to day 20.

Kill criteria

30 demos delivering zero payments means the artifact is not the pain; stop building features and reposition before spending more days.

Risk 4Price is misjudged in either direction.

Mitigation

Offer $149 to the founding cohort and hold a higher one-time price for later cohorts; never reprice mid-window.

Validation experiment

Note objections verbatim and whether prospects pay without asking a question.

Kill criteria

Universal instant yes with no questions across the first 10 conversations means the price is too low and should rise for the next cohort.

Risk 5Portal terms of use or legal objection to listing extraction.

Mitigation

No server-side scraping; capture is user-initiated, one listing at a time, by the paying user.

Validation experiment

Ship bookmarklet-only capture and document the CSV path as the compliant default.

Kill criteria

If a portal formally objects, switch to CSV-only within a day rather than argue.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Next.js and Tailwind repo, deploy to Vercel.
  • Create Supabase project with auth and a logos bucket.
  • Create the $149 one-time Stripe product in live mode.
  • Connect Stripe to TrustMRR before any charge.

Output: Deployed skeleton, live $149 payment link, TrustMRR connected.

Hours 3-5

  • Create clients, listings and reports tables with row-level security.
  • Build the client brief form and dashboard list.
  • Ship login and session handling.

Output: A hunter can create, save and reopen a client brief.

Hours 6-8

  • Build /api/capture with payload validation.
  • Write bookmarklet v1 with JSON-LD, meta and text extraction.
  • Add the confirm-and-edit panel.

Output: Three real listing URLs captured and stored in one client record.

Hours 9-11

  • Implement the 0-100 rule-based scorer.
  • Build the PDF template with cover, cards, score badge and notes.
  • Add the cached OpenAI summary.

Output: First branded shortlist PDF downloaded from real links.

Hours 12-14

  • Gate the dashboard on a paid Stripe session.
  • Run a full end-to-end dry run and fix layout breaks.
  • Deploy to the production domain and write the Loom script.

Output: Public URL, working payment gate, and the first demo recording.

Complete report

Full 30-day launch report

Read the full generated report

Chasseur Brief — 30-day launch report

1. Product opportunity and positioning

Chasseur Brief is a web app for independent property hunters (chasseurs immobiliers) in France — solo operators and 2-5 person firms running 5-20 active buyer clients. The search side of their work is not where the hours disappear. The report is. Every week, for every client, they copy titles, prices, surface areas, photos and notes out of SeLoger, Bien'ici or PAP into a Word file, then email a PDF. At ten clients that is ten to twenty hours a week of unpaid production work, and it is the moment a hunter looks least like the professional their success fee implies.

Chasseur Brief turns listing links into that PDF. The hunter creates a client brief (budget, areas, property type, must-have keywords, deal-breakers), captures listings with a bookmarklet or a CSV, and the app scores each property 0-100 against the brief and renders a branded shortlist: cover page with the hunter's logo, property cards with photo, price, score badge and an editable notes block.

Positioning is deliberately narrow: the report machine, not a CRM, not a portal feed, not a buyer marketplace. The original business sold hunting to buyers; this sells the output of hunting to the hunters.

JEV scored this exact concept 62.5/100 (band C, confidence 0.70). The strongest criterion is speed to first revenue at 8.4/10 — the product either produces a PDF worth sending or it does not, and a solo hunter decides alone on $149. The weakest is monetization at 4.82/10, because a single one-time charge has no expansion. The plan answers that without changing the model: price against hours saved, make referrals the growth loop, and hold a higher price for the cohort after the contest rather than repricing mid-window.

2. Smallest sellable MVP

Everything that is not on the path to one PDF is cut. Five capabilities ship on day 5: a client brief form; a bookmarklet plus CSV upload for capture; a rule-based scorer; a PDF template with logo, cards, scores and notes; a Stripe gate at $149.

Out of scope permanently: server-side scraping, CRM pipeline, email sending from the app, team seats, mobile app, analytics. Each doubles the build and none is why someone pays.

Ship test: create a fictional client, paste three real listing URLs, download the PDF, read it as the client. If it would not embarrass a hunter to send it, it is sellable.

3. Technical implementation plan

Stack: Next.js on Vercel, Supabase for Postgres, auth and logo storage, Stripe Checkout in live mode, @react-pdf/renderer for the document, a vanilla-JS bookmarklet posting to one API route, and OpenAI for a two-sentence description summary cached per listing.

Build order: schema, auth, capture endpoint, scorer, PDF, payment gate, deploy. The hardest technical risk is the bookmarklet. French portals change markup, some render client-side, and a capture that silently returns empty fields destroys trust in one click. Three extraction layers — JSON-LD, meta tags, then page-text heuristics — a confirm-and-edit panel before saving, and CSV upload as the permanent escape hatch. If the portal breaks, the hunter still ships a report.

Inference cost stays negligible: one short summary per listing, cached, capped per report. Target under $0.05 of delivery cost per generated report.

4. Pricing and monetization

One tier: Founding Hunter, $149 one-time, lifetime access, unlimited clients and reports, custom branding, bookmarklet, email support. No subscription. The reason is procedural, not strategic: a one-time charge removes procurement and card-on-file objections from a cold LinkedIn conversation, and it clears the contest rule that every sale must cover its delivery cost, by a wide margin.

The anchor in every message is time, not features: one to two hours per client, per week. A hunter billing a success fee does not need a spreadsheet to justify $149 against two hours saved.

After the window the lever is price, not packaging: the next cohort is offered at a higher one-time price, and every buyer is asked for one named referral. No ad spend is assumed in the conservative or base case.

5. First-customer acquisition

One channel: LinkedIn, in French. Build a 50-row list of independent hunters in Paris, Lyon, Bordeaux and Nantes, filtered to solo or small firms. Send 20 personalised connection requests per working day, roughly 215 over the window. On acceptance, send a 90-second Loom and a sample PDF built on a fictional client. Offer $149 to anyone who replies with interest. Follow up at 48 hours. Ask every buyer for one introduction.

Opening note: Bonjour [Prénom], je vois que vous êtes chasseur immobilier à [ville]. J'ai créé un outil qui transforme vos liens d'annonces en un PDF client prêt à envoyer en 2 minutes. Je cherche 5 chasseurs pour tester cette semaine — ça vous intéresse ?

Week-one goal: MVP live by day 5, sales kit done by day 7, 40 requests sent. First payment targeted day 12.

6. Detailed 30-day roadmap

Week 1 (days 1-5): ship the MVP and the payment gate; day 5 is the hard deadline. Days 6-7: harden on real portal fixtures and produce the sales kit.

Week 2 (days 8-14): list building, then outreach in two waves of 20, demos on acceptance, first sale target day 12, referrals requested from day 13, metrics reviewed day 14.

Week 3 (days 15-21): second-touch sequence to non-responders, bookmarklet fixes from real user reports, one public LinkedIn post, unit-cost check, activation of buyers who have not generated a report, mid-point decision on day 21.

Week 4 (days 22-28): volume outreach to 215+ cumulative, second PDF style, referral one-pager, performance fixes, deadline messaging that the founding cohort closes 16 December.

Days 29-30: close every open lead before 13:00 UTC on 16 December, reconcile Stripe against TrustMRR, publish the changelog. Full day-by-day tasks sit in the roadmap table above.

7. Revenue and profit scenarios (projections only)

Three projections at $149, with processing assumed at 4.5-5.5% (Stripe plus USD/EUR conversion and international cards):

  • Conservative: 4 customers, $596 collected, $27 fees, $30 operating. Hackathon profit $569; business profit $539.
  • Base: 12 customers, $1,788 collected, $89 fees, $55 operating. Hackathon profit $1,699; business profit $1,644.
  • Upside: 25 customers, $3,725 collected, one $149 refund, $194 fees, $120 paid marketing, $95 operating. Hackathon profit $3,262; business profit $3,167.

The honest reading: this is a $1,600-$3,200 contest entry, not a $100k one, unless the referral loop compounds after day 20. That is the variable to watch, not the price.

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

8. Main risks and validation experiments

LinkedIn response rate. Test 20 requests on day 9 and measure acceptance within 72 hours; if 100 requests produce fewer than five replies, rewrite the note before touching the product.

Bookmarklet breakage. Test 20 real portal URLs on day 6; if fewer than 70% yield usable title, price and image across three extraction layers, make CSV the default entry path and market the product as CSV to branded PDF.

Perceived value of the artifact. If 30 demos produce zero payments, the report is not the pain and the concept needs repositioning, not more outreach.

Price. Offer $149 to the first cohort and a higher one-time price to the next; if every prospect says yes without a question, the price is too low.

Portal terms and legal exposure. No server-side scraping; capture is user-initiated and per-listing. If a portal objects, go CSV-only within a day.

9. First 24-hour action plan

Hours 1-2: repo, deployment, Supabase, Stripe live product at $149, TrustMRR connected before any charge. Output: live payment link.

Hours 3-5: schema, auth, client brief form. Output: a brief you can save and reopen.

Hours 6-8: capture API and bookmarklet v1. Output: three real URLs stored.

Hours 9-11: scorer and PDF template. Output: one branded PDF.

Hours 12-14: end-to-end dry run, production deploy, Loom script written. Output: public URL and the first demo recording.

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 →