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

Shortlist Press

Turns a recruiter's raw candidate resume PDF into a branded, contact-redacted one-page candidate profile with a shareable client link in under two minutes.

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.43/10
MVP build (solo)
4 days
Launch price
$79 · monthly
Sales to $1,000 revenue
13 customers
First paying customer
Direct LinkedIn DMs to independent recruiters who posted a live role in the last 7 days.
Who pays

Solo and 2-5 person contingency recruiting agencies and independent recruiters in the US/UK/Canada who submit 5-40 candidates per month to client hiring managers.

Biggest execution risk

Operational simplicity 4.5/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

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

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

0/11
Entry price
$79
Solo build
4 days
30d base revenue
$948
30d hackathon profit
$839
Section 1 of 8

Product opportunity and positioning

Target customer

Solo and 2-5 person contingency recruiting agencies and independent recruiters in the US/UK/Canada who submit 5-40 candidates per month to client hiring managers.

Why now

The trigger is a client waiting on a submission today, so the buyer decides in one conversation, pays $79 without procurement, and is directly reachable by LinkedIn DM.

Problem

Every submission needs the agency logo, colours, standard fields, and the candidate's contact details stripped out before it reaches the client; recruiters do this by hand in Word or Canva, which takes 20-45 minutes and still leaks emails and phone numbers.

Solution

The recruiter uploads a resume PDF, picks or saves an agency template (logo, two colours, footer), reviews the extracted fields on one screen, and gets a one-page Submission Sheet as PDF plus a hosted link with a short candidate code such as SP-4821.

Differentiation · It is not a resume builder, not an ATS, and not a job-description matcher; it produces one fixed client-facing artifact, the branded and contact-redacted submission sheet, from the resume the recruiter already has.

1. Product opportunity and positioning

The buyer is narrow and commercial: a solo or 2-5 person contingency recruiter in the US, UK or Canada who submits 5-40 candidates a month to client hiring managers. The trigger event is not "I should improve my workflow"; it is "the client asked for this candidate today." That trigger turns a formatting chore into revenue-blocking work, which is why a $79 monthly charge is approved in one message with no procurement cycle.

The painful task is exact. Every submission needs the agency logo, two brand colours, a standard footer, and the candidate's email, phone and personal links removed before it goes to the client. Recruiters currently rebuild that sheet by copy-pasting into a Word or Canva template. It costs 20-45 minutes per candidate, the formatting breaks, and the redaction occasionally fails, which is a client-relationship risk rather than an inconvenience.

Shortlist Press makes the submission sheet a by-product of dropping in the resume the recruiter already has. Upload a PDF, pick a saved agency template, correct anything the extractor got wrong on a single review screen, and export a one-page PDF plus a hosted link carrying a short candidate code (SP-4821). The deliverable is a single fixed artifact, which keeps the build a render pipeline rather than a platform.

Positioning: the fastest route from "client wants a submission" to a branded, anonymised one-pager. It is deliberately not a resume builder, not an ATS, not a LinkedIn integration and not a job-description matcher. Those are separate products with separate buyers.

JEV scored this concept 64.3/100 (band C, confidence 0.67). The strongest criterion is speed to first revenue at 8.54, which matches the design: a reachable business buyer with a same-day trigger. The weakest is operational simplicity at 4.49. The response is to keep the product stateless on managed services, use no human review step beyond the recruiter's own edit screen, and store nothing longer than needed to render and re-download a sheet. That constraint shapes every technical decision below.

2. Smallest sellable MVP

Six things, no more. A PDF upload that extracts text and rough layout into a fixed candidate schema (headline, roles, tenure, skills, summary). A redaction pass that removes emails, phone numbers and personal URLs and flags ambiguous strings for the recruiter. An agency template with a logo, two brand colours and a footer line, saved for reuse. An HTML-to-PDF render of a one-page Submission Sheet plus a hosted share link with a candidate code. Stripe checkout with a credit counter gating each render. A single-screen review UI where the recruiter fixes extracted fields before rendering.

Out of scope on purpose: job-description matching, resume rewriting, ATS or LinkedIn integration, candidate-side accounts, outbound email from the product, team seats and agency analytics. Each of these expands the surface without changing the artifact the client receives.

3. Technical implementation plan

Next.js on Vercel, Supabase for auth, storage and a credits table, unpdf or pdf.js for extraction, an LLM (OpenAI or Anthropic) to map extracted text into the candidate schema, Playwright/Chromium for HTML-to-PDF, and Stripe Checkout with webhooks. The pipeline is stateless: upload to storage, extract, redact, review, render, return a signed URL.

The hardest technical risk is multi-column and visually designed resume PDFs, where layout extraction degrades and the recruiter has to clean up more than they save. Mitigation: treat the LLM schema step as the primary parser with raw text as input, always show the review screen, and store the failure cases from the first ten real resumes as a regression set.

4. Pricing and monetization

Two monthly tiers. Founding Recruiter at $79/month: 30 Submission Sheets, one saved agency template, hosted share links with candidate codes, redaction pass. Small Agency at $199/month: unlimited sheets, three templates, custom subdomain on share links. Each render decrements a credit; credits reset monthly.

The week-one offer is the founding-recruiter link at $79/month, capped at the first 20 buyers. The upsell path is volume: a recruiter who hits the 30-sheet cap on the $79 tier moves to $199, and a second template is a natural trigger for a two-person agency.

5. First-customer acquisition

One channel: direct LinkedIn DMs to independent recruiters who posted a live role in the last seven days, backed by r/recruiting and independent-recruiter Slack and Facebook groups. Build a 60-name list on day one, then send roughly 25 DMs a day for 24 outreach days, about 600 total.

The offer is delivery-first, not a demo: "Send me one resume, I'll return your branded, contact-removed one-pager free today." The free sheet is produced through the same pipeline the product uses. Then one question closes or kills it: "Want the tool that made this, or shall I keep doing it for you?" A single follow-up goes out at 72 hours; nothing more.

6. 30-day execution roadmap

Days 1-4 build: repo, Stripe products, extraction, redaction, template editor, render, share link, review UI. Day 5 is the MVP deadline: ten real resumes through the pipeline, landing page live, 45-second Loom recorded. Days 6-14 are outreach plus manual free conversions, with the first paid subscription targeted for day 12. Days 15-21 add the $199 Agency tier, a build-in-public before/after post in three recruiter communities, and a mid-point review that swaps monthly pricing for a per-sheet pack if fewer than five buyers exist. Days 22-28 continue outreach, publish a redaction guarantee, collect three testimonial quotes, ship v1.1. Days 29-30 reconcile every payment inside the contest window and publish a build-in-public recap.

7. Revenue and profit scenarios (projections only)

Three modelled cases, all projections from stated assumptions, no verified customers. Conservative: 3 buyers at $79, $237 gross, no refunds, no chargebacks, roughly $8 in processing fees, no ad spend, $30 delivery cost; hackathon profit about $229. Base: 12 buyers at $79, $948 gross, one refund, $30 in fees, $85 delivery cost; hackathon profit about $839. Upside: 30 buyers blended at $99 (25 at $79, 5 at $199), $2,970 gross, two refunds, $95 in fees, $150 in sponsored posts, $190 delivery cost; hackathon profit about $2,567. Payment fees assume Stripe at roughly 3.2%. Operating cost assumes under $0.40 per rendered profile plus hosting.

8. Main risks and validation experiments

First, recruiters may see the sheet as low-value and keep using Word: test by delivering ten free sheets and counting how many ask for the tool. Second, extraction may fail on designed PDFs: test on ten real resumes and measure manual cleanup minutes; if the median exceeds five minutes, the value claim breaks. Third, a redaction miss would kill trust: run every sheet through a second independent regex check plus an LLM verifier, and kill the launch if any miss appears in the first 20 sheets. Fourth, cold-DM conversion may fall below 5%: if 150 DMs produce zero free-sheet requests by day 10, change the channel or the offer, not the product.

9. First 24-hour action plan

Hours 1-2: scaffold the Next.js repo, Supabase project and Stripe test products. Hours 3-5: extraction and redaction pipeline running on five sample resumes. Hours 6-8: build the 60-recruiter LinkedIn list with role and post date. Hours 9-11: HTML template plus Playwright PDF render. Hours 12-14: deploy a one-page landing site with one demo sheet and a Loom placeholder.

Section 2 of 8

Smallest sellable MVP

Upload a resume PDF, pick a saved agency template, review extracted fields on one screen, and download a branded, contact-redacted one-page Submission Sheet PDF plus a hosted share link with a candidate code.

Must-have features

  • PDF upload with text and rough layout extraction
  • LLM extraction into a fixed candidate schema (headline, roles, tenure, skills, summary)
  • Contact-redaction pass removing emails, phone numbers and personal URLs, with ambiguity flags
  • Saved agency template: logo, two brand colours, footer line
  • HTML-to-PDF render of a one-page Submission Sheet
  • Hosted share link with short candidate code (e.g. SP-4821)
  • Stripe Checkout with a credit counter gating each render
  • Single-screen review UI to edit extracted fields before rendering

Explicitly out of scope

  • Job-description matching or resume rewriting
  • ATS and LinkedIn integrations
  • Candidate-side accounts or job board
  • Outbound email sending from the product
  • Team seats, permissions or agency analytics
  • Custom subdomain (Agency tier only, added day 17)
  • Native mobile app

Demo flow (what the buyer sees)

  1. Recruiter signs in and uploads a candidate resume PDF
  2. Pipeline extracts text and maps it into the candidate schema
  3. Redaction pass strips emails, phones and personal links and flags uncertain strings
  4. Recruiter selects a saved agency template and corrects any field on the review screen
  5. Render produces a one-page Submission Sheet PDF and a hosted link with a candidate code
  6. One credit is deducted and the recruiter copies the link into the client email
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase (auth, storage, credits table)unpdf / pdf.js for PDF text and layout extractionOpenAI or Anthropic API for resume-to-schema extractionPlaywright/Chromium render service for HTML-to-PDFStripe Checkout and webhooks

Architecture

A single Next.js app on Vercel handles auth, upload and the review screen. Uploads land in Supabase storage; a serverless route extracts text, sends it to an LLM with a strict JSON schema for candidate fields, then runs a redaction pass (regex for emails, phones and URLs, plus an LLM verifier for ambiguous strings). The recruiter edits fields, the app renders a one-page HTML template with the saved logo and colours into PDF via Playwright, stores the PDF, and issues a signed hosted-link URL carrying the candidate code. Stripe webhooks increment a credits row; every render decrements it and blocks at zero. No long-lived state beyond the sheet itself.

Build steps

  1. Scaffold Next.js repo, Supabase project and env vars
  2. Create Stripe products at $79 and $199 plus checkout session route
  3. Build upload route and unpdf text extraction
  4. Write the schema-extraction prompt and validate JSON output on five sample resumes
  5. Implement redaction pass with regex plus LLM verifier and ambiguity flags
  6. Build template editor: logo upload, two colours, footer, saved per account
  7. Build the one-page HTML template and Playwright PDF render route
  8. Add hosted share link route with candidate code and signed URL
  9. Build the single-screen review UI wired to the extraction output
  10. Add credits table, Stripe webhook and render gating
  11. Deploy to Vercel and run ten real resumes end to end
  12. Add error toasts and a fallback manual-edit path for failed extractions

AI components

  • LLM resume-to-schema extraction with a strict JSON output schema
  • LLM verifier that reviews redacted text for residual personal identifiers
Hardest technical risk: Multi-column or heavily designed resume PDFs extract badly, forcing the recruiter to clean up more than the tool saves and destroying the value claim.
Section 3 of 8

Pricing and monetization

Founding Recruiter

Entry offer
$79 / month

For Solo recruiter doing 5-30 submissions a month

  • 30 branded Submission Sheets per month
  • One saved agency template
  • Hosted share links with candidate codes
  • Contact-redaction pass

Small Agency

$199 / month

For 2-5 person agency needing more volume and a second template

  • Unlimited Submission Sheets
  • Three saved templates
  • Custom subdomain on share links

Model: Monthly subscription with a per-render credit counter, plus a higher tier for agencies that need unlimited sheets and multiple templates.

First revenue offer: Founding-recruiter link at $79/month for the first 20 buyers, sent after delivering one free branded, contact-removed sheet from their own resume within 24 hours.

Expected ACV: $79

Upsell path: Recruiters who hit the 30-sheet cap or ask for a second template move to the $199 Small Agency tier; volume, not features, drives the upgrade.

Target customers
30
Revenue model
$2,370
Costs
$120
Profit model
$2,250
Section 4 of 8

First-customer acquisition

Primary channel

Direct LinkedIn DMs to independent recruiters who posted a live role in the last 7 days.

Where to find them

  • LinkedIn search for 'independent recruiter' and 'recruitment consultant' with posts in the last 7 days
  • LinkedIn posts saying 'I am hiring' or 'I am referring' from agency recruiters
  • r/recruiting and r/recruitingagency threads
  • Independent-recruiter Slack and Facebook groups
  • Recruiter communities where people post candidate-submission templates
  • Agency websites listing 1-5 consultants in the US, UK and Canada

Exact outreach motions

  • Send a 3-line DM referencing the specific role they posted and offering one free branded, contact-removed sheet within 24 hours
  • Deliver the free sheet through the pipeline the same day, then ask the closing question
  • Follow up once at 72 hours with the before/after pair attached
  • Post one before/after sheet pair in three recruiter communities as a build-in-public update
  • Ask every free-sheet recipient for the name of one other recruiter who submits weekly

Message template

Saw you posted the [role] search. Send me one candidate's resume PDF and I'll return your branded, contact-details-removed one-pager today, free, no signup. If it's useful, I'll show you the tool that made it.
Week-one goal: 60 recruiters listed, 90 DMs sent, 5 free Submission Sheets delivered, 5 replies.
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

Repo, billing products, target list

  • Scaffold Next.js repo and Supabase project.
  • Create Stripe products at $79 and $199.
  • Build a 60-recruiter LinkedIn list with role and post date.

Deliverable: Deployed skeleton repo plus a 60-name outreach list.

Day 2Extraction

PDF to candidate schema

  • Wire unpdf text extraction on upload.
  • Add LLM schema extraction with strict JSON output.
  • Add redaction pass with ambiguity flags.

Deliverable: Extraction and redaction working on five sample resumes.

Day 3Render

Template and PDF output

  • Build template editor: logo, two colours, footer.
  • Create the one-page HTML template and Playwright PDF route.
  • Add hosted share link with candidate code.

Deliverable: End-to-end render producing a PDF and a share link.

Day 4Billing and review

Credits and review screen

  • Add credits table and Stripe webhook gating renders.
  • Build the single-screen review UI.
  • Publish the landing page with one demo sheet.

Deliverable: MVP deployed with working checkout.

Day 5MVP deadlineMVP shipped

Real resumes, real output

  • Run ten real resumes through the pipeline and log failures.
  • Fix the two worst extraction breakages.
  • Record a 45-second Loom of one conversion.

Deliverable: Public v1 plus demo Loom.

Day 6Outreach wave 1

First 30 DMs

  • Send 30 LinkedIn DMs using the free-sheet offer.
  • Post the launch note in two recruiter communities.

Deliverable: 30 DMs sent and 2 community posts live.

Day 7Free conversions

Deliver manually, ask the closing question

  • Deliver 3 free Submission Sheets within 24 hours.
  • Ask each recipient the tool-or-service question.

Deliverable: 3 free sheets delivered and 3 replies logged.

Week 2 · Launch & first sale · 7 days
Day 8Outreach wave 2

Volume plus follow-up

  • Send 40 DMs to new names.
  • Follow up at 72 hours on the first wave.

Deliverable: 40 DMs and 20 follow-ups sent.

Day 9Conversion

Deliver more free sheets

  • Deliver 3 more free sheets same day.
  • Log every redaction flag raised by recruiters.

Deliverable: 3 sheets delivered and a redaction issue list.

Day 10Warm pipeline

Founding link to warm names

  • Send the $79 founding link to all free-sheet recipients.
  • Send 40 DMs to new names.

Deliverable: 8 warm buyers and 40 new DMs.

Day 11Quality

Zero redaction misses

  • Manually audit every sheet rendered so far.
  • Patch any ambiguous redaction pattern found.

Deliverable: Audit log showing zero contact leaks.

Day 12First saleFirst sale target

Close paying recruiters

  • Send checkout links to all warm names with a same-day reason.
  • Take any call offered and close on the call.

Deliverable: First paid subscription collected through Stripe.

Day 13Onboarding

Make the first buyer successful

  • Save their logo, colours and footer as their template.
  • Ask for one sentence on time saved.

Deliverable: Live template for the first paying customer and one quote.

Day 14Review

Conversion math

  • Compute DM-to-reply and reply-to-paid rates.
  • Rewrite the DM opener around the best-performing angle.

Deliverable: Metrics sheet and revised DM script.

Week 3 · Repeat & systematize · 7 days
Day 15Agency outreach

2-5 person agencies

  • Send 60 DMs targeting multi-consultant agency accounts.
  • Add 20 new names to the list.

Deliverable: 60 DMs sent and list grown to 100.

Day 16Build in public

Second inbound trickle

  • Post one before/after sheet pair in three recruiter communities.
  • Reply to every comment with the free-sheet offer.

Deliverable: 3 posts live and comment replies logged.

Day 17Agency tier

Ship $199 plan

  • Enable unlimited sheets and three templates.
  • Add custom subdomain on share links.

Deliverable: Small Agency tier purchasable in Stripe.

Day 18Referrals

Ask for names

  • Follow up all free-sheet recipients asking for one recruiter referral.
  • Offer a free month of sheets for a referral that converts.

Deliverable: 10 referral asks sent and 3 names returned.

Day 19Extraction hardening

Multi-column resumes

  • Fix the most frequent extraction failure from real PDFs.
  • Add a manual-edit fallback for failed parses.

Deliverable: Extraction patch deployed.

Day 20Outreach wave 4

Hiring-post sniping

  • Send 60 DMs to recruiters who posted a role in the last 7 days.
  • Track reply rate by posting type.

Deliverable: 60 DMs and a reply-rate breakdown.

Day 21Mid-point decision

Pricing or offer change

  • Count paying customers and warm pipeline.
  • If under 5 paying, add a $9 three-sheet pack.

Deliverable: Decision memo with chosen pricing path.

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

Ship only if decided

  • Implement the per-sheet pack if the decision memo requires it.
  • Test the checkout copy on five warm names.

Deliverable: Alternative SKU live or explicitly rejected.

Day 23Outreach wave 5

Sustained volume

  • Send 60 DMs.
  • Post one build-in-public update in two communities.

Deliverable: 60 DMs and 2 posts.

Day 24Trust

Redaction guarantee

  • Publish a page stating the redaction check and what happens on a miss.
  • Add the guarantee line to the landing page.

Deliverable: Trust page live.

Day 25Social proof

Collect quotes

  • Ask three paying users for a one-line quote.
  • Add quotes to the landing page.

Deliverable: 3 quotes published.

Day 26Outreach wave 6

Referral-adjacent recruiters

  • Send 60 DMs to recruiters posting 'I am referring'.
  • Follow up all day-20 non-responders once.

Deliverable: 60 DMs and 30 follow-ups.

Day 27Polish

Speed and error handling

  • Reduce render time and add progress states.
  • Fix the top two support questions from real users.

Deliverable: v1.1 deployed.

Day 28Last call

Founding price deadline

  • Send a last-call founding price message to all warm names.
  • Send 50 new DMs.

Deliverable: Last-call message sent to every warm contact.

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

Convert trials before the window closes

  • Call or DM every trial user with a same-day close ask.
  • Confirm all payments landed in the connected Stripe account.

Deliverable: All payments confirmed inside the contest window.

Day 30Reconcile

Numbers and recap

  • Reconcile revenue, refunds and processing fees into one sheet.
  • Publish a build-in-public recap with what worked and what did not.

Deliverable: Profit reconciliation sheet and public recap post.

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 paying recruiters, all on the $79 Founding Recruiter tier, roughly 0.5% close on about 300 DMs.
  • Base: 12 paying recruiters at $79, roughly 2% close on about 600 DMs across 24 outreach days.
  • Upside: 30 buyers, 25 at $79 and 5 at $199, blended ARPU $99, driven by agency-tier conversions and referral traffic.
  • Payment processing assumed at Stripe rates, roughly 3.2% of collected revenue including fixed per-charge fees.
  • Operating cost assumes under $0.40 of LLM and compute per rendered profile plus Vercel, Supabase and domain costs.
  • Refunds modelled as one monthly charge in base and two in upside; chargebacks modelled at zero because billing is subscription-only and cancellable.
  • Ad spend is paid marketing only (sponsored recruiter-newsletter posts in upside); all organic DM outreach counts as zero.
  • Pricing, not volume, is the upside lever: the $199 tier is offered from day 17 onward.
  • All figures are projections from stated assumptions, not verified revenue, customers or traction.

Conservative

3 customers
$237
collected revenue · avg payment $79
Refunds
$0
Chargebacks
$0
Payment fees
$8
Paid marketing
$0
Hackathon profit
$229
Operating costs
$30
Business profit
$199

Base case

12 customers
$948
collected revenue · avg payment $79
Refunds
$79
Chargebacks
$0
Payment fees
$30
Paid marketing
$0
Hackathon profit
$839
Operating costs
$85
Business profit
$754

Optimistic

30 customers
$2,970
collected revenue · avg payment $99
Refunds
$158
Chargebacks
$0
Payment fees
$95
Paid marketing
$150
Hackathon profit
$2,567
Operating costs
$190
Business profit
$2,377

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$948
Payment fees (3.9%)
$37
Paid marketing
$0
Hackathon profit
$911
Business profit
$826

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

All scenarios are projections built from stated assumptions. They are not verified revenue, customers, traction or profit.

Section 7 of 8

Main risks and validation experiments

Risk 1Recruiters treat the submission sheet as low-value formatting and keep using Word.

Mitigation

Lead with the delivered artifact, not the software; measure whether they ask for the tool after seeing their own sheet.

Validation experiment

Deliver 10 free sheets this week and count how many ask to keep using the tool versus asking you to keep doing it.

Kill criteria

If fewer than 2 of 10 free-sheet recipients ask for the tool by day 14, reposition the offer or stop.

Risk 2Extraction fails on multi-column or designed resume PDFs, creating more cleanup than the recruiter saves.

Mitigation

Always show the review screen, keep a manual-edit fallback, and add failure cases to a regression set.

Validation experiment

Run 10 real resumes and time the manual cleanup for each; record the median minutes.

Kill criteria

If median cleanup exceeds 5 minutes per sheet, the time-saving claim collapses and the build must change before more outreach.

Risk 3A redaction miss leaks a candidate's email or phone to a client, destroying trust with a paying agency.

Mitigation

Run two independent checks (regex pass plus LLM verifier) and surface ambiguity flags instead of guessing.

Validation experiment

Audit the first 20 rendered sheets by hand for residual contact details before charging anyone.

Kill criteria

Any confirmed leak in the first 20 sheets halts paid rollout until the verifier is rewritten.

Risk 4Cold LinkedIn DM conversion falls far below the assumed 5%, leaving revenue under target.

Mitigation

Track reply rate daily, rewrite the opener weekly, and add agency accounts and referral asks as parallel sources.

Validation experiment

Send 150 DMs by day 10 and measure free-sheet requests and paid conversions separately.

Kill criteria

Zero free-sheet requests from 150 DMs by day 10 means the channel or offer changes, not the product.

Risk 5Recruiters buy for one role and churn, so monthly pricing converts worse than per-sheet pricing.

Mitigation

Hold a per-sheet pack in reserve and ship it on day 22 if the mid-point review shows fewer than 5 paying subscribers.

Validation experiment

Ask every free-sheet recipient whether they would pay per sheet or monthly, and record verbatim answers.

Kill criteria

If 7 of 10 warm names prefer per-sheet and fewer than 5 monthly buyers exist by day 21, switch the primary SKU.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js repo and Supabase project.
  • Create Stripe products at $79 and $199 in test mode.

Output: Deployed skeleton and configured billing products.

Hours 3-5

  • Wire PDF upload and unpdf text extraction.
  • Add the LLM schema-extraction prompt with a strict JSON schema.
  • Add the regex redaction pass.

Output: Extraction and redaction running on five sample resumes.

Hours 6-8

  • Build a 60-name LinkedIn list of independent recruiters with a live role posted in the last 7 days.
  • Capture role, company and post date per name.

Output: 60-row outreach spreadsheet ready to send.

Hours 9-11

  • Build the one-page HTML submission template with logo and two colours.
  • Add the Playwright PDF render route.

Output: First branded PDF rendered from a real resume.

Hours 12-14

  • Deploy a one-page landing site with one demo sheet and the founding price.
  • Draft the DM opener and the closing question.

Output: Public landing page plus outreach script ready for day 2.

Complete report

Full 30-day launch report

Read the full generated report

Shortlist Press — 30-Day Launch Report

1. Product opportunity and positioning

The buyer is narrow and commercial: a solo or 2-5 person contingency recruiter in the US, UK or Canada who submits 5-40 candidates a month to client hiring managers. The trigger is not "I should improve my workflow"; it is "the client asked for this candidate today." That turns a formatting chore into revenue-blocking work, which is why a $79 monthly charge gets approved in one message with no procurement cycle.

The task is exact. Every submission needs the agency logo, two brand colours, a standard footer, and the candidate's email, phone and personal links removed before it reaches the client. Recruiters currently rebuild that sheet by copy-pasting into Word or Canva: 20-45 minutes per candidate, broken formatting, and the occasional redaction miss that is a client-relationship risk rather than an annoyance.

Shortlist Press makes the submission sheet a by-product of dropping in the resume the recruiter already has. Upload a PDF, pick a saved agency template, correct anything the extractor got wrong on one review screen, and export a one-page PDF plus a hosted link carrying a short candidate code such as SP-4821. One fixed artifact, not a platform.

Positioning: the fastest route from "client wants a submission" to a branded, anonymised one-pager. Deliberately not a resume builder, not an ATS, not a LinkedIn integration, not a job-description matcher.

JEV scored this concept 64.3/100 (band C, confidence 0.67). Speed to first revenue is the strongest criterion at 8.54, which matches the design: a reachable business buyer with a same-day trigger. Operational simplicity is the weakest at 4.49. The answer is to stay stateless on managed services, add no human review step beyond the recruiter's own edit screen, and store nothing beyond what is needed to render and re-download a sheet.

2. Smallest sellable MVP

Six things: PDF upload extracting into a fixed candidate schema; a redaction pass removing emails, phones and personal URLs with ambiguity flags; a saved agency template of logo, two colours and footer; an HTML-to-PDF render of a one-page Submission Sheet plus a hosted link with a candidate code; Stripe checkout with a credit counter gating each render; and a single-screen review UI for correcting extracted fields.

Out of scope on purpose: job-description matching, resume rewriting, ATS or LinkedIn integrations, candidate-side accounts, outbound email, team seats and analytics. Each expands the surface without changing the artifact the client receives.

3. Technical implementation plan

Next.js on Vercel, Supabase for auth, storage and a credits table, unpdf for extraction, an LLM for schema mapping, Playwright/Chromium for PDF rendering, and Stripe Checkout with webhooks. Upload goes to storage; a serverless route extracts text, an LLM maps it to the candidate schema, regex plus an LLM verifier handles redaction, the recruiter edits fields, and the render route returns a PDF and a signed share URL. Every render decrements a credit and blocks at zero.

The hardest technical risk is multi-column or heavily designed resume PDFs, where extraction degrades and the recruiter cleans up more than the tool saves. Mitigation: treat the LLM schema step as the primary parser, always show the review screen, keep a manual-edit fallback, and turn the first ten real resumes into a regression set.

4. Pricing and monetization

Two monthly tiers. Founding Recruiter at $79: 30 Submission Sheets, one saved template, hosted share links with candidate codes, redaction pass. Small Agency at $199: unlimited sheets, three templates, custom subdomain on share links. Credits reset monthly and gate each render.

The week-one offer is the founding link at $79/month, capped at the first 20 buyers, sent only after a free sheet has been delivered. Upsell is volume-driven: hitting the 30-sheet cap or asking for a second template moves a buyer to $199.

5. First-customer acquisition

One channel: LinkedIn DMs to independent recruiters who posted a live role in the last seven days, backed by r/recruiting and independent-recruiter Slack and Facebook groups. Day one builds a 60-name list; roughly 25 DMs a day across 24 outreach days gives about 600 sends.

The offer is delivery-first: "Send me one resume, I'll return your branded, contact-removed one-pager free today." The free sheet is made by the same pipeline the product uses. The close is one question: "Want the tool that made this, or shall I keep doing it for you?" One follow-up at 72 hours, then stop.

6. 30-day execution roadmap

Days 1-4 build the pipeline, billing and review screen. Day 5 is the MVP deadline: ten real resumes through the system, landing page live, 45-second Loom recorded. Days 6-14 are outreach plus manual free conversions, with the first paid subscription targeted for day 12 and onboarding of that first account on day 13. Days 15-21 ship the $199 Agency tier, publish a before/after pair in three recruiter communities, harden extraction, and hold a mid-point review that swaps monthly pricing for a $9 three-sheet pack if fewer than five buyers exist. Days 22-28 continue outreach at 60 DMs per wave, publish a redaction guarantee, collect three quotes, and ship v1.1. Days 29-30 close every open trial and reconcile revenue, refunds and fees.

7. Revenue and profit scenarios (projections only)

Three modelled cases, all projections from stated assumptions, with no verified customers.

Conservative: 3 buyers at $79, $237 gross, no refunds, no chargebacks, about $8 in processing fees, no ad spend, $30 delivery cost; hackathon profit lands near $229.

Base: 12 buyers at $79, $948 gross, one refund, about $30 in fees, $85 delivery cost; hackathon profit near $839.

Upside: 30 buyers blended at $99 (25 at $79, 5 at $199), $2,970 gross, two refunds, about $95 in fees, $150 in sponsored recruiter-newsletter posts, $190 delivery cost; hackathon profit near $2,567.

Processing assumes Stripe at roughly 3.2%. Delivery assumes under $0.40 of LLM and compute per rendered profile plus hosting. None of these numbers are verified; they exist to show which lever (buyers or price tier) moves the outcome most.

8. Main risks and validation experiments

Low perceived value: recruiters may keep using Word. Test by delivering ten free sheets and counting how many ask for the tool; fewer than two by day 14 means reposition or stop.

Extraction failure on designed PDFs: time manual cleanup across ten real resumes; a median above five minutes breaks the saving and the build must change first.

Redaction miss: any leaked contact detail is trust-killing. Run regex plus an LLM verifier, hand-audit the first 20 sheets, and halt paid rollout on any confirmed miss.

Cold-DM conversion below 5%: send 150 DMs by day 10; zero free-sheet requests means the channel or offer changes, not the product.

Churn after a single role: hold a $9 three-sheet pack in reserve and ship it on day 22 if fewer than five monthly buyers exist, and record verbatim per-sheet-versus-monthly preferences from warm names.

9. First 24-hour action plan

Hours 1-2: repo, Supabase project, Stripe products at $79 and $199. Hours 3-5: upload, extraction, LLM schema mapping and regex redaction on five sample resumes. Hours 6-8: the 60-name recruiter list with role, company and post date. Hours 9-11: one-page HTML template with logo and two colours plus the Playwright PDF render. Hours 12-14: landing page with one demo sheet, founding price, and the DM script ready to send on day 2.

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 →