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

Shortlist & Sign-off

Upload a client or employee list and get a budget-locked gift shortlist: three options per person with a one-line rationale, a per-person PDF card, and one order sheet a finance lead can approve in a single pass.

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.42/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Cold LinkedIn and email outreach to owners and ops leads at 5-50 person agencies, CPA practices and brokerages, opening with a finished five-name sample brief.
Who pays

Owner or operations lead at a 5-50 person professional-services firm in the US or Canada (marketing agency, CPA or bookkeeping practice, insurance brokerage, recruiting boutique) with no HR or procurement function.

Biggest execution risk

Monetization potential 5.0/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 10; 11 sales at $99 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
$99
Solo build
5 days
30d base revenue
$990
30d hackathon profit
$951
Section 1 of 8

Product opportunity and positioning

Target customer

Owner or operations lead at a 5-50 person professional-services firm in the US or Canada (marketing agency, CPA or bookkeeping practice, insurance brokerage, recruiting boutique) with no HR or procurement function.

Why now

The December list, the budget and the ship-by date already exist this week; the buyer needs the decision artifact, not a new store.

Problem

Picking something personal for 60 clients or staff means hours of browsing, duplicate gifts, flagged overspend and a last-minute fallback to generic gift cards.

Solution

Upload a CSV or paste rows, the product tags each recipient, ranks a top-three shortlist inside the per-head budget with a one-line rationale, then exports per-recipient PDF cards, a master order sheet CSV and a shareable three-option pick page.

Differentiation · ChatGPT gives text; this gives a budget guard, duplicate detection, price variance against the cap, PDF cards and an order sheet a finance lead can approve in one pass.

The buyer, the deadline and the artifact

A 5-50 person professional-services firm has three things every December: a list of 20-100 recipients, a per-head budget between $40 and $150, and a ship-by date that does not move. What it does not have is a person whose job is gifting. The owner or operations lead does it at night, in a spreadsheet, with a browser full of tabs. The result is predictable: duplicate gifts, one or two picks that blow the cap, a finance question about variance, and a final-hour retreat to generic gift cards that reads as impersonal to exactly the clients the firm is trying to keep.

The failure is not a shortage of products. It is a shortage of decision. Nobody needs another catalog; they need three defensible options per person, all inside the budget, with a sentence explaining why, and one sheet that a partner can sign without re-checking anything. That is a document, not a storefront.

Positioning. Shortlist & Sign-off sells the decision and the sign-off document. It never holds inventory, never ships, never takes a return. It competes with hours of browsing on one side and with gift cards on the other, and it wins on both because every recommendation arrives pre-priced, pre-justified and capped to the stated per-head budget. The buyer stops researching and starts ordering the same day.

Why this wedge and not the original. The insight worth keeping is that people want a small, well-chosen set plus the feeling someone thought about them. What made the original an e-commerce company, printed catalogs, inventory, fulfillment and a storefront competing with every other store, is exactly what a solo founder cannot operate in 30 days. This version keeps the curated shortlist and the recipient choice, and drops everything else: the buyer orders through their own vendor, and the software sells the decision.

The JEV read. This concept scored 6.42 weighted, 64.2 of 100, band C, confidence 0.746. The shape of that score matters more than the number. Speed to first revenue is the strongest criterion (normalized 8.4): the buyer has the list and the deadline already, so a finished sample is the pitch and there is no cold-start. Monetization potential is the weakest (4.98), which is why this plan opens at $99 to remove friction but deliberately builds two upgrade tiers live by day 13 and tests a second gifting occasion on day 19 rather than living off one December.

The honest constraint. Seasonality is the whole wedge and also the whole ceiling. Demand for December gifting collapses after mid-December, so every structural decision here favours closing fast in weeks 1-3 and treating days 19-30 as both a second-occasion probe and a January pipeline build, not as a growth phase.

Section 2 of 8

Smallest sellable MVP

A paid unlock that turns an uploaded list of up to 40 recipients into a budget-compliant top-three gift shortlist with rationale, per-recipient PDF cards and a downloadable order sheet CSV.

Must-have features

  • CSV upload and paste-in table with a column mapper for name, role or company, interests, per-head budget and avoid-list, plus manual row editing
  • Hand-curated catalog of roughly 150 tagged SKUs (name, category, price band, recipient-type fit, source URL) stored in Postgres and editable from one CSV
  • LLM ranking per recipient returning strict JSON: three options with price, fit score and one-line rationale
  • Deterministic post-filter that drops anything over the per-head budget or on the avoid-list
  • Budget guard on total spend plus duplicate detector flagging any gift appearing more than twice
  • Export bundle: one-page PDF card per recipient and a master order sheet CSV with quantity, unit price, line total and budget variance
  • Stripe Checkout unlock gate with five-recipient watermarked free preview and email receipt
  • Per-email and per-domain run caps to stop the free preview being farmed

Explicitly out of scope

  • No gift checkout, payment collection or fulfillment for the gifts themselves
  • No shipping addresses, tracking or delivery logistics
  • No vendor marketplace, affiliate placements or sponsored catalog entries
  • No subscription billing or team seats in the first 30 days
  • No mobile app and no account system beyond email plus a magic link
  • No gift-card issuance or e-gift delivery
  • No Shopify or accounting integrations in month one

Demo flow (what the buyer sees)

  1. Buyer opens the site and uploads a CSV of 40 names or pastes rows into the table.
  2. Column mapper guesses name, company/role, interests, budget and avoid-list; buyer corrects two columns.
  3. Ranker returns three priced options with a one-line rationale per recipient.
  4. Budget guard drops over-cap picks and the duplicate detector flags repeats.
  5. Buyer sees the first five PDF cards watermarked and clicks unlock.
  6. Stripe Checkout at $99 completes and the webhook releases the full export.
  7. Buyer downloads the PDF bundle and the order sheet CSV, and receives a shareable pick link per recipient.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase PostgresOpenAI or Anthropic JSON-mode API@react-pdf/rendererStripe Checkout plus webhookResend for receipts and share linksPapaParse for CSV ingestion

Architecture

A single Next.js app on Vercel holds both the buyer-facing pages and the API routes. Supabase stores runs, recipients, the catalog, picks and orders. Upload parses the CSV in the browser, posts normalised rows to an API route, which writes a run row and then fans out one LLM call per recipient with a strict JSON schema; a deterministic pass re-checks every returned option against budget and avoid-list before it is persisted. Exports are generated on request from stored data: the PDF bundle streams from @react-pdf/renderer, the order sheet is assembled server-side as CSV. Stripe Checkout on the preview page flips a paid flag through a webhook, which unlocks export routes and triggers the receipt email. Nothing needs a background worker; runs are synchronous with a retry on schema failure.

Build steps

  1. Scaffold Next.js on Vercel, create the Supabase project, commit the schema for runs, recipients, catalog, picks and orders.
  2. Load 150 hand-curated SKUs from a single CSV into the catalog table with price band and recipient-fit tags.
  3. Build the upload and column mapper with a manual row editor for broken rows.
  4. Implement the per-recipient LLM call with JSON schema validation and one retry on malformed output.
  5. Add the deterministic post-filter for budget and avoid-list, then the total-spend guard and duplicate detector.
  6. Log token usage and estimated cost per run to a column so margin is visible from the first sale.
  7. Render per-recipient PDF cards and assemble the order sheet CSV with line totals and variance.
  8. Add Stripe Checkout, the webhook unlock and the Resend receipt email.
  9. Add free-preview watermarking plus per-email and per-domain run caps.
  10. Build the public shareable pick page that records a single 'this one' choice back to the run.
  11. Load-test one 120-recipient run and record wall-clock time and API cost.

AI components

  • LLM call per recipient producing three ranked options with a one-line rationale in strict JSON
  • Tag inference from free-text interest fields so messy CSV rows still produce specific rationales
  • Optional swap suggestion text when a pick is filtered out for breaching the budget
Hardest technical risk: Catalog price drift: an SKU that changed price or was discontinued makes the order sheet wrong and breaks the core promise, so every SKU needs a manual re-check before each export batch and a visible 'verify price before ordering' line.
Section 3 of 8

Pricing and monetization

Starter Brief

Entry offer
$99 one-time

For Firm gifting up to 40 clients or employees this December

  • Top-three shortlist per recipient with rationale
  • Per-recipient one-page PDF cards
  • Master order sheet CSV with budget variance and duplicate flags
  • Shareable three-option pick pages

Full List Brief

$199 one-time

For Firm gifting 41 to 120 recipients, or running a client track and a staff track

  • Everything in Starter Brief up to 120 recipients
  • Two separate budget tracks
  • Swap suggestions where a pick breaches budget
  • Reorder of the same list at a lower price band

Season Pass

$349 one-time

For Firm or fractional ops consultant running gifting for several client companies

  • Up to five lists of 120 recipients each
  • Co-branded PDF cards with the buyer's logo
  • Priority regeneration when the list changes
  • Email support during December

Model: One-time payment per list, tiered by recipient count, with no subscription in the first 30 days.

First revenue offer: 'I built your December gift shortlist for five of your team - three options each, all under $75 with a rationale line. The full 40-recipient export, PDF cards and order sheet are $99, payable on the same page.'

Expected ACV: $99

Upsell path: Buyers whose list passes 40 names see an in-checkout upgrade to $199; existing buyers get an upgrade credit toward the two-track tier, and every buyer is asked for one peer-firm intro plus the January onboarding-kit offer.

Target customers
30
Revenue model
$2,970
Costs
$160
Profit model
$2,810
Section 4 of 8

First-customer acquisition

Primary channel

Cold LinkedIn and email outreach to owners and ops leads at 5-50 person agencies, CPA practices and brokerages, opening with a finished five-name sample brief.

Where to find them

  • LinkedIn search for 'agency owner' filtered to 2-50 employees, US and Canada
  • LinkedIn search for 'CPA firm partner' and 'managing partner accounting'
  • LinkedIn search for 'insurance brokerage principal'
  • State CPA society member directories that list firm websites
  • Public team pages and 'our clients' pages of small agencies
  • Local chamber of commerce member lists for mid-size metros
  • Recruiting boutique and bookkeeping practice owners active in operator communities

Exact outreach motions

  • Build a 300-row sheet with firm, contact name, public team-page names and a budget guess before sending anything.
  • Run the product on five public names at each of the first 40 firms and attach the finished PDF to the opening message.
  • Send with a subject naming a real person: 'Five gift options for your team (all under $75)'.
  • Follow up on day 3 with one line and the preview link; follow up on day 7 with the order-by deadline line, then archive.
  • Reply to every response within 30 minutes and offer to run their actual list live while they watch.
  • Ask every buyer for one named intro to a peer firm doing the same December gifting.
  • Post the before/after order sheet in two operator communities that allow promotional posts.

Message template

Hi [First name] - I built your December gift shortlist for five of your team. Three options each, all under $75, one line on why each fits. PDF is attached, nothing to install. If it's useful I can run the other 35 for $99 and send the PDF cards plus one order sheet your partner can sign in a single pass. Want the full list?
Week-one goal: 300 firms listed, 100 contacted with a finished five-name sample attached, and at least 8 replies logged.
Section 5 of 8

30-day execution roadmap

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

Repo, schema and payment plumbing

  • Scaffold Next.js on Vercel and connect the Supabase project.
  • Create tables for runs, recipients, catalog, picks and orders.
  • Round-trip a Stripe test checkout and webhook.

Deliverable: Deployed skeleton with a working test payment.

Day 2Catalog

150 tagged SKUs

  • Hand-enter 150 gift SKUs with price band, recipient-fit tags and source URL.
  • Ship a CSV importer so the catalog stays editable from one file.
  • Spot-check 20 SKUs against live vendor prices.

Deliverable: Seeded catalog of 150 tagged SKUs.

Day 3Ranking engine

Upload to shortlist end to end

  • Build CSV upload, column mapper and manual row editor.
  • Call the LLM in JSON mode for three options plus rationale per recipient.
  • Validate output against a schema and retry once on malformed JSON.

Deliverable: A full run producing a top-three shortlist.

Day 4Guardrails

Budget, duplicates, cost logging

  • Enforce per-head budget and total spend cap, dropping avoid-list hits.
  • Flag gifts repeating more than twice and suggest a lower price band swap.
  • Log token cost per run to a column.

Deliverable: Budget-compliant run with cost per run recorded.

Day 5Export and paywallMVP shipped

MVP goes live

  • Render per-recipient PDF cards with @react-pdf/renderer.
  • Generate the master order sheet CSV with line totals and variance.
  • Gate the full export behind Stripe Checkout and send the receipt via Resend.

Deliverable: Sellable MVP live: free preview plus $99 unlock.

Day 6Site and limits

Landing page plus abuse controls

  • Publish the landing page with a real anonymised sample brief.
  • Add per-email and per-domain run caps plus a privacy note with delete-on-request.
  • Ship the shareable pick page with a single-choice button.

Deliverable: Public site with caps, privacy note and pick pages.

Day 7Lead list

300 firms and 10 samples

  • Build the 300-row outreach sheet, 2-50 staff, US and Canada.
  • Capture firm, contact, public team names and a budget guess.
  • Run the product on the first 10 firms to create sample briefs.

Deliverable: 300-row sheet and 10 finished sample briefs.

Week 2 · Launch & first sale · 7 days
Day 8First send

40 outreach messages

  • Send 40 messages with the finished five-name PDF attached.
  • Log send time, opens and replies in the sheet.
  • Fix broken preview links flagged by early replies.

Deliverable: 40 contacted, 10 samples delivered.

Day 9Objection handling

Learn from replies

  • Reply to every response within 30 minutes.
  • Rewrite the preview waterline if quality objections appear.
  • Tag every objection as price, trust, AI-generic or timing.

Deliverable: Objection log and a revised preview.

Day 10Second batchFirst sale target

Push past 100 contacted

  • Send 60 more with a subject-line variant.
  • Build 10 more sample briefs for high-fit firms.
  • Ask two warm repliers for a $99 card payment directly.

Deliverable: 100 contacted and the first live checkout attempts.

Day 11Close

First revenue

  • Follow up day-3 non-responders with the order-by deadline line.
  • Offer a live run-on-your-list walkthrough to undecided repliers.
  • Ship any blocker that stopped a checkout.

Deliverable: First $99 payment collected through Stripe.

Day 12Delivery

Fast turnaround and referrals

  • Turn around every paid run within four hours.
  • Ask each buyer for one peer-firm intro.
  • Add catalog gaps named by buyers.

Deliverable: Delivered orders and referral asks sent.

Day 13Upgrade path

Add $199 and $349

  • Add two budget tracks and the 120-recipient tier to checkout.
  • Offer upgrades to buyers whose list exceeds 40 names.
  • Publish the Season Pass page for fractional ops consultants.

Deliverable: Three live checkout tiers.

Day 14Channel widening

New surface plus unit cost

  • Post the before/after order sheet in two operator communities.
  • Send 40 more outbound with a staff-gifting variant.
  • Measure LLM cost per recipient and target under $0.03.

Deliverable: Third batch sent and cost per recipient measured.

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

Social proof and objection FAQ

  • Ask two buyers for a one-line quote and permission to show an anonymised card.
  • Swap the landing sample for a buyer-approved one.
  • Add an FAQ that answers the free-ChatGPT comparison directly.

Deliverable: Landing page with proof and objection FAQ.

Day 16List completion

Reach 300 contacted

  • Send the remaining batch to reach 300 contacted.
  • Run the day-7 follow-up on all non-responders.
  • Archive dead leads with a reason code.

Deliverable: 300 contacted with follow-ups complete.

Day 17Referral engine

Peer introductions

  • Email every buyer asking for one named intro.
  • Draft a forwardable one-paragraph blurb buyers can send.
  • Track referral source on every sale.

Deliverable: Referral blurb and five intro asks out.

Day 18Fulfilment audit

Protect against refunds

  • Audit delivered order sheets against current vendor prices.
  • Fix or remove any SKU that drifted more than 10%.
  • Add a 'verify price before ordering' line to the order sheet.

Deliverable: Price-audited catalog and order sheet footer.

Day 19Second occasion

Test off-December demand

  • Pitch new-hire onboarding kits and client thank-yous to 20 existing contacts.
  • Write a variant preview for a 15-person onboarding cohort.
  • Record reply rate against the holiday pitch.

Deliverable: Second-occasion reply-rate data point.

Day 20Ops hardening

Reliability of paid runs

  • Add alerts for failed runs and failed webhooks.
  • Add a retry so a paid run never stalls.
  • Document the founder's manual fallback.

Deliverable: Alerting and retry in place.

Day 21Content surface

One organic pull asset

  • Publish a 'December client gift order sheet template' page.
  • Make the five-recipient sample form the page CTA.
  • Submit the page to the sitemap and one relevant newsletter.

Deliverable: One indexed lead-capture page.

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

Best-performing segment

  • Send 60 more to CPA practices and brokerages.
  • Pre-build 10 sample briefs for those firms.
  • Time sends to Tuesday morning.

Deliverable: 60 contacted in the best segment.

Day 23Price test

Lift average order value

  • Test $129 on the Starter tier for new visitors.
  • Offer existing buyers an upgrade credit toward $199.
  • Compare conversion and refund rates across both prices.

Deliverable: Price test result and a chosen default.

Day 24Expansion

Convert buyers upward

  • Contact every Starter buyer whose list was near 40 names.
  • Pitch the two-track upgrade with a concrete example.
  • Log which upgrade argument converts.

Deliverable: Tracked upgrade pipeline.

Day 25Deadline campaign

Urgency on the full list

  • Send the order-by-date email to every non-buyer with a sample.
  • Add a countdown line to the landing hero.
  • State the final delivery date you can guarantee.

Deliverable: Urgency campaign sent to the full list.

Day 26Support window

Same-day turnaround

  • Hold a two-hour turnaround promise for paid runs.
  • Create a fixed reply template for messy-list questions.
  • Fix the top three recurring upload errors.

Deliverable: Documented turnaround and upload fixes.

Day 27Season close

Final conversions

  • Message every warm lead one last time.
  • Offer a same-day run for lists under 30 names.
  • Confirm vendor order-by dates with each buyer.

Deliverable: Final push completed.

Day 28Proof collection

Testimonials and intros

  • Ask every buyer for a quote and one intro.
  • Publish a results page with counts only, no invented metrics.
  • Resend the referral blurb to all buyers.

Deliverable: Public results page and referral asks sent.

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

Real margin per order

  • Export run and cost data and compute margin per order.
  • Write the January onboarding-kit offer.
  • Fix the single biggest delivery failure found.

Deliverable: Margin report and next-occasion offer.

Day 30Handoff

January pipeline and final tally

  • Email all buyers the January onboarding-kit offer.
  • Reconcile revenue, refunds, fees and ad spend for the contest.
  • Ship the most-requested catalog feature.

Deliverable: Final tally and January pipeline started.

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: 300 firms contacted, about 1 in 25 pays, no upgrade revenue.
  • Base: about 1 in 10 contacts replies and roughly 1 in 3 of repliers pays at the $99 entry tier, with upgrades left uncounted.
  • Upside: base conversion plus 5 upgrades to $199 and $349 tiers and a modest $150 in paid posts; ARPU is held at $99 so the upside number is deliberately understated.
  • Payment processing assumed at Stripe's 2.9% plus $0.30 per transaction, rounded to about 4% of collected revenue.
  • Refunds are held at zero in the conservative and base cases because the buyer sees five real cards before paying; the upside case assumes a 4% refund rate.
  • Operating costs cover Vercel, Supabase, domain and email plus LLM inference at $3 or less per 120-recipient run.
  • All figures are projections from stated assumptions, not verified revenue or existing customers.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$12
Paid marketing
$0
Hackathon profit
$285
Operating costs
$25
Business profit
$260

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$39
Paid marketing
$0
Hackathon profit
$951
Operating costs
$45
Business profit
$906

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$99
Paid marketing
$150
Hackathon profit
$2,127
Operating costs
$90
Business profit
$2,037

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$990
Payment fees (3.9%)
$39
Paid marketing
$0
Hackathon profit
$951
Business profit
$906

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.

These are projections built from stated assumptions, not verified revenue, customers or traction. Contest ranking uses hackathon profit (revenue minus refunds, chargebacks, payment fees and paid marketing); operating costs are shown separately.

Section 7 of 8

Main risks and validation experiments

Risk 1The buyer says ChatGPT can do this free and never converts.

Mitigation

Put the budget guard, duplicate flags and order sheet in the watermarked preview so the difference is visible before payment.

Validation experiment

Show the five-recipient preview to 10 contacts and ask directly whether they would pay $99 for the full export.

Kill criteria

Fewer than 1 in 10 sampled contacts says yes after seeing the real preview.

Risk 2Catalog price drift makes the order sheet wrong and triggers refunds.

Mitigation

Re-check 20 SKUs weekly, remove drift over 10%, and print a verify-price line on every order sheet.

Validation experiment

Audit all delivered order sheets on day 18 against live vendor prices and count mismatches.

Kill criteria

More than one refund traced to a wrong price in the same week.

Risk 3Seasonality collapses demand after mid-December.

Mitigation

Run the second-occasion test on day 19 and build a January onboarding-kit offer before the season ends.

Validation experiment

Send 20 second-occasion pitches and compare reply rate with the holiday pitch.

Kill criteria

Zero replies from 20 second-occasion pitches by day 24.

Risk 4Sparse recipient data produces generic rationales, the exact failure the buyer fears.

Mitigation

Ask for two interests per row, flag thin rows in the UI and show a specific-edit prompt rather than a vague line.

Validation experiment

Run a 20-row list with only names and companies and rate each rationale for specificity.

Kill criteria

More than half the rationales on a names-only list are unusable.

Risk 5The free preview is farmed across email addresses to get the full list free.

Mitigation

Cap runs per email and per domain from day one and watermark every preview card.

Validation experiment

Review run logs on day 12 for repeated domains with no payment and adjust caps.

Kill criteria

Preview-to-paid ratio falls below 1 in 20 with evidence of multi-email farming.

Risk 6LinkedIn and email limits cap outbound volume below 300 contacts in week one.

Mitigation

Run email and LinkedIn in parallel and keep a 100-firm reserve list.

Validation experiment

Log actual sends per day in week one and project the 300-contact date.

Kill criteria

Projected 300-contact date slips past day 20.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the GitHub repo, scaffold Next.js, deploy an empty app to Vercel.
  • Create the Supabase project and write the schema SQL for runs, recipients, catalog, picks and orders.

Output: Live skeleton URL and committed schema file.

Hours 3-5

  • Assemble the first 60 SKUs in a single CSV with price band and recipient-fit tags.
  • Write the catalog importer and load the 60 rows into Postgres.

Output: Importable catalog CSV and 60 seeded rows.

Hours 6-9

  • Build the upload page and column mapper for name, company/role, interests, budget and avoid-list.
  • Wire one recipient through the LLM call and print the raw JSON response on screen.

Output: Working upload that returns a three-option shortlist for one row.

Hours 10-13

  • Extend the ranking call to every row in the run and persist picks.
  • Add the budget filter and duplicate detector as a deterministic post-step.

Output: A full 5-recipient run producing a compliant shortlist.

Hours 14-18

  • Add Stripe Checkout in test mode and the webhook that flips the paid flag.
  • Send the first outreach test message to yourself with a rendered PDF attached.

Output: Test payment loop and a real PDF sample in hand.

Complete report

Full 30-day launch report

Read the full generated report

Shortlist & Sign-off - 30-Day Launch Report

Concept version 1. JEV weighted score 6.42, 64.2 of 100, band C, confidence 0.746. The shape of that score drives this plan more than the number: speed to first revenue is the strongest criterion (normalized 8.4) because the buyer already owns the list, the budget and the deadline, while monetization potential is the weakest (4.98). This plan does not fix that by raising the entry price. It fixes it by shipping two upgrade tiers by day 13 and testing a second gifting occasion on day 19.

1. Product opportunity and positioning

A 5-50 person professional-services firm has three things every December: a list of 20-100 recipients, a per-head budget between $40 and $150, and a ship-by date that does not move. It has no HR function and no procurement cycle. The owner or ops lead does the gifting at night in a spreadsheet. The output is duplicates, one or two picks that breach the cap, a finance question about variance, and a final-hour fallback to gift cards that reads as impersonal to the clients the firm is trying to retain.

The shortage is not products, it is decisions. Nobody needs another catalog. They need three defensible options per person, all inside the budget, each with a sentence explaining why, plus one sheet a partner can sign without re-checking it. That is a document.

So the positioning is narrow on purpose: this is a decision artifact, not a store. No inventory, no shipping, no returns, no vendor marketplace. It beats hours of browsing on one side and beats generic gift cards on the other, because every recommendation arrives pre-priced, pre-justified and capped. The buyer stops researching the same day.

The mechanic worth borrowing from the original insight is the small, well-chosen set plus a real choice for the recipient. What made that business an e-commerce company - printed catalogs, inventory, fulfillment, a storefront competing with every other store - is exactly what one person cannot operate in 30 days. This version keeps the shortlist and the choice and drops the rest: the buyer orders through their own vendor.

The honest constraint is seasonality. December is the wedge and the ceiling. Every decision here favours closing fast in weeks one to three and treats the last ten days as a second-occasion probe and a January pipeline build.

2. Smallest sellable MVP

One paid unlock. Upload up to 40 recipients, get three priced options each with a rationale, download PDF cards and an order sheet. The five-recipient watermarked preview is the sales mechanism, not a free tier.

Must exist at launch: CSV and paste upload with a column mapper and manual row editing; a hand-curated catalog of about 150 SKUs; an LLM ranking call returning strict JSON; a deterministic filter that enforces the per-head budget and the avoid-list; a total-spend guard and a duplicate detector; per-recipient PDF cards plus a master order sheet CSV with line totals and variance; Stripe Checkout unlock with a Resend receipt; per-email and per-domain run caps.

Explicitly excluded: gift checkout or fulfillment, shipping addresses, a vendor marketplace, subscriptions, team seats, a mobile app, and any accounting integration. Every one of those adds operations to a 30-day solo build without adding a dollar of first-sale probability.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres, an LLM API in JSON mode, @react-pdf/renderer for cards, Stripe Checkout with a webhook, Resend for email, PapaParse for ingestion. No background worker: runs are synchronous with a single retry on schema failure.

The build order is schema, catalog, upload, ranking, guardrails, cost logging, exports, paywall, caps, pick pages. Cost logging on day 4 matters commercially, not just technically: it is the only way to know whether a 120-recipient run at $199 is profitable before ten of them have shipped.

The hardest technical risk is catalog price drift. An SKU that moved price or was discontinued makes the order sheet wrong, which breaks the one promise the buyer paid for. Mitigations: weekly re-check of a sample, removal of anything drifted more than ten percent, and a printed verify-price line on every order sheet.

4. Pricing and monetization

Three one-time tiers: Starter Brief $99 up to 40 recipients, Full List Brief $199 up to 120 recipients with two budget tracks, Season Pass $349 for five lists with co-branded cards. Entry price stays at $99 to keep the yes cheap on a task the buyer must complete anyway. The $199 and $349 tiers exist to answer the weak monetization score, and go live on day 13 rather than at launch so the MVP ships on day 5.

5. First-customer acquisition

One channel: cold LinkedIn and email to owners and ops leads, opened with a finished sample. Build a 300-row sheet with firm, contact, public team-page names and a budget guess. For the first 40 firms, run the product on five public names and attach the PDF to the first message. Follow up on day 3 and day 7, then archive. Reply within 30 minutes and offer to run their real list live. Ask every buyer for one named peer intro.

6. Thirty-day roadmap

Days 1-5 build. Days 6-7 prepare the site and the 300-row list. Days 8-11 send the first 100 messages and close the first payment, targeted for day 10. Days 12-17 deliver fast, ship the upgrade tiers, widen the channel and collect proof. Days 18-21 audit prices, run the second-occasion test, harden operations and publish one organic page. Days 22-28 run the best segment, test a $129 price, push upgrades, run the deadline campaign and close the season. Days 29-30 reconcile real margin and open a January pipeline. The three live checkpoints are: MVP on day 5, first payment by day 10, 300 contacted by day 16.

7. Revenue and profit scenarios

Conservative: 3 sales at $99, $297 collected, $12 in processing fees, $25 operating. Base: 10 sales, $990 collected, $39 fees, $45 operating. Upside: 25 sales, $2,475 collected, $99 refunds, $99 fees, $150 paid posts, $90 operating. ARPU is held at $99 in all three so upgrade revenue is uncounted upside. Contest ranking uses revenue minus refunds, chargebacks, fees and paid marketing; operating cost is shown separately as business profit. Every figure is a projection from stated assumptions, not verified revenue or existing customers.

8. Risks and validation experiments

Free-ChatGPT objection: show the guard, the duplicate flags and the order sheet inside the preview; kill if fewer than 1 in 10 sampled contacts says yes after seeing real output. Price drift: audit delivered order sheets on day 18; kill the affected SKUs on the first traced refund. Seasonality: 20 second-occasion pitches on day 19; kill that path on zero replies by day 24. Generic rationales on thin data: test a names-only list; kill the feature if half the rationales are unusable. Preview farming: review run logs on day 12 for unpaid repeat domains. Outbound limits: log daily sends and project the 300-contact date; act if it slips past day 20.

9. First 24 hours

Hours 1-2: repo, Vercel deploy, Supabase schema. Hours 3-5: first 60 catalog SKUs imported. Hours 6-9: upload plus one successful LLM shortlist. Hours 10-13: full run with budget filter and duplicate detector. Hours 14-18: Stripe test checkout and a real PDF sample. The day ends with a live skeleton, 60 SKUs, one working run and a PDF you can attach to an email.

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 →