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

Vendor Memo

Turns a 10-minute requirements intake into a forwardable, 2-page vendor decision memo with a weighted comparison matrix and 24-month TCO for one software category.

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.19/10
MVP build (solo)
5 days
Launch price
$199
Sales to $1,000 revenue
6 customers
First paying customer
Direct community and LinkedIn outreach to people who posted a 'recommend a tool' question in the last 7 days.
Who pays

Operations manager, office manager, or controller at a 20-200 person company in the US, UK, or Canada who must recommend a tool in one category within 7 days.

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 10; 6 sales at $199 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
$199
Solo build
5 days
30d base revenue
$2,985
30d hackathon profit
$2,695
Section 1 of 8

Product opportunity and positioning

Target customer

Operations manager, office manager, or controller at a 20-200 person company in the US, UK, or Canada who must recommend a tool in one category within 7 days.

Why now

Buyers post 'what's the best [category] software for a 50-person company?' in public communities every day, and $199 sits under most approval thresholds, so no procurement cycle blocks the sale.

Problem

They burn 5-10 hours across review sites, Reddit and vendor pages, build a messy spreadsheet, then get their recommendation challenged because they missed seat minimums, implementation fees and auto-renewal terms.

Solution

A 12-question intake plus a curated vendor fact base produces a PDF memo: 3 shortlisted vendors, a weighted scoring matrix tied to the buyer's must-haves, a 24-month TCO table and 5 questions to ask each vendor, delivered by email and shareable link after payment.

Differentiation · G2, Capterra and GetApp sell vendor leads and endless reviews; Vendor Memo sells the buyer a signed-off decision artifact with TCO math, in one category, this week.

1. Product opportunity and positioning

Software selection is a research task with a deadline attached. A 20-200 person company rarely has a procurement team; the ops manager or controller is handed a category and a week. Their current process is browsing review marketplaces, skimming Reddit threads, opening six pricing pages, and assembling a spreadsheet that omits seat minimums, implementation fees and auto-renewal terms. The recommendation then gets challenged in a meeting because the analysis was never structured.

The review marketplaces (GetApp, G2, Capterra, Software Advice, TrustRadius) are monetized by vendors who pay for placement and leads. That model optimizes for breadth (45,000+ products) and for vendor surfaces, not for the single decision in front of one buyer. Nothing in that stack produces a forwardable artifact with a cost model attached.

Vendor Memo inverts this. It charges the buyer $199 and delivers one thing: a 2-page decision memo for one software category, built from a 12-question intake, a curated fact sheet per category, and a deterministic weighted scoring engine. Output: three shortlisted vendors, a weighted matrix tied to the buyer's own must-haves, a 24-month TCO table (seat tiers + implementation + renewal uplift), and five questions to ask each vendor. The buyer can forward it to a boss or partner and defend it.

Why this is sellable in 30 days: the customer is reachable one at a time, the deliverable is a file, and the price is under approval thresholds. There is no marketplace cold-start because we do not need vendors to participate; there is no SEO ramp because outreach is direct; there is no procurement cycle because $199 is a card charge. The wedge is deliberately narrow: twelve named categories, ten vendors each, manual curation, no reviews, no directory, no accounts.

Positioning sentence: for the one category you must decide this week, Vendor Memo gives you the memo your boss will accept, in ten minutes and $199, instead of five hours and a spreadsheet. JEV scored the concept 61.9/100 (band C, confidence 0.66), strongest on speed to first revenue (8.43) and solo build feasibility (7.58), weakest on market demand (4.88) and monetization (4.81). That score shapes this plan: the build is kept small, the first dollar is targeted for day 10, and demand is tested with outreach before the fact base is expanded past twelve categories.

Section 2 of 8

Smallest sellable MVP

A paid intake form for 12 categories that emails one PDF memo (3 vendors, weighted matrix, 24-month TCO, vendor questions) within minutes of Stripe payment.

Must-have features

  • Next.js intake form: 12 questions plus category picker for 12 narrow software categories
  • Curated JSON fact sheets: 10 vendors per category with seat minimums, implementation fees, contract terms, integration flags
  • Deterministic weighted scoring engine that ranks 10 vendors and returns the top 3
  • React-PDF memo generator: cover, shortlist rationale, weighted matrix, 24-month TCO table, 5 vendor questions, disclaimer
  • Stripe Checkout (TrustMRR-connected) gating memo generation; no memo before payment succeeds
  • Resend email with PDF attachment plus a read-only shareable link
  • Landing page with one redacted example memo and a single CTA
  • Repo-based JSON fact editor so vendor facts update without code changes

Explicitly out of scope

  • No reviews, ratings, or public vendor directory
  • No vendor marketplace, lead gen, or paid placement
  • No live scraping of vendor pricing
  • No user accounts, saved workspaces, or team collaboration
  • No enterprise RFP, security review, or procurement workflows
  • No renewal monitoring or alerts
  • No calls, demos, or human negotiation support

Demo flow (what the buyer sees)

  1. Buyer opens landing page, clicks 'Get your memo', sees the redacted example
  2. Buyer picks a category and answers 12 questions (seats, budget band, must-have integrations, contract length tolerance, implementation tolerance, compliance needs)
  3. Intake posts to the API; the scoring engine ranks the 10 curated vendors against weighted criteria
  4. Buyer pays $199 via Stripe Checkout
  5. Webhook fires; server renders the PDF, stores the order row, emails PDF via Resend and returns a shareable link
  6. Buyer forwards the PDF; founder sees the order in Supabase and follows up at day 3
Build plan

Technical implementation plan

Stack

Next.js 15 on VercelTailwind CSSSupabase Postgres (intake + orders)Stripe Checkout + webhookReact-PDFResendOpenAI API (optional narrative paragraph only)TrustMRR payment connectionGitHub repo for versioned JSON fact sheets

Architecture

Static Next.js landing and intake pages on Vercel call one serverless route that validates answers and runs a pure scoring function over versioned JSON fact sheets committed to the repo. Checkout happens on Stripe hosted pages so no card data touches the app. A Stripe webhook writes the order row to Supabase, renders the PDF in the same serverless invocation, stores it in Supabase Storage, and sends it via Resend. The shareable link is a signed Supabase Storage URL. Facts are plain JSON so the founder can fix a price without a deploy if needed, and every memo records the fact-sheet version used.

Build steps

  1. Scaffold Next.js + Tailwind on Vercel, connect GitHub, add env vars for Stripe, Supabase, Resend
  2. Define the fact-sheet JSON schema (vendor, seat_min, seat_tiers, implementation_fee, contract_term, renewal_uplift, integrations, pricing_url, last_verified)
  3. Curate 4 categories x 10 vendors, then 8 more on day 6-9
  4. Build the 12-question intake with category picker and client-side validation
  5. Implement the scoring engine as a pure function with weights from intake answers; unit-test against 3 hand-checked cases
  6. Build the React-PDF template: cover, shortlist, weighted matrix, 24-month TCO table, 5 vendor questions, disclaimer
  7. Wire Stripe Checkout and the webhook; gate rendering on payment_intent.succeeded
  8. Add Resend delivery and signed Storage link
  9. Ship landing page with redacted example memo and one CTA
  10. Add a Supabase orders view and a manual 'regenerate memo' admin route for support

AI components

  • Optional single OpenAI call producing a 120-word narrative rationale per shortlist, hard-bounded by the deterministic scores and disabled if the call fails
Hardest technical risk: Wrong or stale vendor facts (seat minimums, implementation fees) producing a memo a buyer can disprove, which triggers refunds and reputational damage in public communities.
Section 3 of 8

Pricing and monetization

Single Decision Memo

Entry offer
$199 one-time

For Ops manager, office manager, or controller at a 20-200 person company with a software decision due within 7 days

  • 12-question intake
  • 3-vendor shortlist
  • Weighted scoring matrix
  • 24-month TCO table
  • 5 vendor questions
  • PDF + shareable link

Model: One-time $199 per decision memo, paid before the PDF is generated; no subscription in the first 30 days.

First revenue offer: I'll build your decision memo for [category] free this week if you'll tell me whether it was forwardable to your boss; if it holds up, the paid version is $199 for your next category.

Expected ACV: $199

Upsell path: Second category for the same buyer at $199, a colleague referral, then a $399 two-category bundle once repeat purchases appear; no subscription until buyer cadence is proven.

Target customers
80
Revenue model
$15,920
Costs
$500
Profit model
$15,420
Section 4 of 8

First-customer acquisition

Primary channel

Direct community and LinkedIn outreach to people who posted a 'recommend a tool' question in the last 7 days.

Where to find them

  • r/smallbusiness 'recommend software' threads from the last 7 days
  • r/ExperiencedFounders and r/sysadmin software selection threads
  • LinkedIn posts by ops managers, office managers and controllers asking for tool recommendations
  • r/Bookkeeping, r/humanresources, r/projectmanagement category-specific threads
  • LinkedIn Sales Navigator-free search: title 'Operations Manager' + company size 11-200 + post activity
  • Slack and Discord communities for SMB ops and finance operators (public channels only)

Exact outreach motions

  • Reply publicly with one useful specific fact (a seat minimum or implementation fee) then offer the free memo in the same reply
  • Two-sentence DM: what the memo contains, offer to run it free, no signup
  • Email or DM the finished memo within 24 hours and ask one question: was it forwardable?
  • Day-3 follow-up: what category are you buying next quarter?
  • Ask for one referral to a peer with a live decision
  • Publicly post the redacted memo as a reply so lurkers with the same question see the artifact

Message template

Saw your post about picking a [category] tool for a small team. I built a 10-minute intake that turns your requirements into a 2-page decision memo with a weighted comparison and 24-month TCO. Want me to run it for your category free this week? No signup.
Week-one goal: 60 outreach touches (30 public replies, 30 DMs), 10 replies, 5 free memos delivered, first paid $199 sale by day 10.
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, env vars, payment rails

  • Scaffold Next.js on Vercel and push to GitHub
  • Confirm Stripe + TrustMRR connection is live in test mode
  • Freeze the 12 category list

Deliverable: Deployed empty app with payment env vars set

Day 2Fact base

Schema + first categories

  • Write the fact-sheet JSON schema
  • Curate 4 categories x 10 vendors from public pricing pages
  • Record last_verified date per vendor

Deliverable: 4 validated JSON fact sheets

Day 3Core logic

Intake and scoring

  • Build 12-question intake with category picker
  • Implement weighted scoring as a pure function
  • Unit-test against 3 hand-checked cases

Deliverable: Working intake that returns a ranked top 3

Day 4Output

PDF, payment gate, email

  • Build React-PDF memo template with TCO table and disclaimer
  • Wire Stripe Checkout and webhook gating
  • Add Resend delivery and signed share link

Deliverable: Paid end-to-end memo delivery

Day 5MVP shipMVP shipped

Landing page and dry runs

  • Ship landing page with redacted example memo
  • Run 3 dry-run memos and fix layout defects
  • Declare MVP frozen

Deliverable: Live sellable product at vendor memo URL

Day 6Fact base 2

Expand coverage

  • Curate 4 more categories
  • Add implementation fee and renewal uplift fields where missing

Deliverable: 8 categories live

Day 7Launch

Outreach infrastructure

  • Set up outreach tracker with 60 target slots
  • Publish launch post in one SMB community
  • Draft the free-memo DM variant

Deliverable: Tracker populated, first 20 touches sent

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

Public replies

  • Reply to 30 recent 'recommend a tool' threads with one specific fact each
  • Log every reply and outcome

Deliverable: 30 public touches, target 5 replies

Day 9Outreach

DMs and free memos

  • Send 30 personalized LinkedIn DMs
  • Deliver up to 5 free memos within 24 hours

Deliverable: 5 free memos delivered, feedback captured

Day 10First revenueFirst sale target

Convert to paid

  • Ask each free-memo recipient for the $199 paid memo on their next category
  • Fix top 3 memo complaints same day

Deliverable: First paid $199 sale target

Day 11Repair loop

Accuracy and trust

  • Re-verify 20 vendor records flagged by buyers
  • Add 'verified on' date stamp to every memo

Deliverable: Fact sheets current, stamp shipped

Day 12Proof

Case artifact

  • Publish one redacted memo as a public example
  • Ask two buyers for a one-line quote about forwardability

Deliverable: Public proof page section

Day 13Outreach

Second category wave

  • Target 3 new categories with live threads
  • Send 25 DMs to controllers and office managers

Deliverable: 25 touches, 3 new category entries

Day 14Review

Week 2 numbers

  • Tally reply rate, free memos, paid conversions
  • Kill the two worst-performing categories

Deliverable: Week 2 metrics note and category cut list

Week 3 · Repeat & systematize · 7 days
Day 15Fact base 3

Complete coverage

  • Curate final 4 categories
  • Add seat-tier breakpoints for the 3 most requested vendors

Deliverable: 12 categories live

Day 16Conversion

Paid page clarity

  • Add TCO example numbers to landing page
  • Add refund policy and disclaimer copy

Deliverable: Updated landing page

Day 17Outreach

Volume

  • 40 public replies and DMs combined
  • Follow up with all day-3 and day-7 contacts

Deliverable: 40 touches, follow-up log

Day 18Delivery

Turnaround

  • Measure median time from payment to email
  • Automate the manual regenerate path

Deliverable: Median delivery under 5 minutes

Day 19Expansion

Repeat purchase

  • Offer second-category memo to every past buyer
  • Ask each buyer for one referral

Deliverable: Repeat and referral offers sent

Day 20First sale checkpoint

Revenue review

  • Compare actual sales to base projection
  • Decide whether to add a $399 two-category bundle

Deliverable: Go/no-go note on bundle pricing

Day 21Outreach

LinkedIn push

  • Send 30 DMs to ops managers at 20-200 person companies
  • Post one public TCO breakdown thread

Deliverable: 30 DMs and one public thread

Week 4 · Scale what works · 9 days
Day 22Quality

Refund prevention

  • Audit all delivered memos for missing TCO lines
  • Contact any buyer whose memo needed a correction

Deliverable: Zero uncorrected memo errors

Day 23Outreach

Community depth

  • Answer 10 category questions with no pitch, then offer the memo
  • Log which categories get the most replies

Deliverable: Category demand ranking

Day 24Product

Small friction cuts

  • Add 'decision deadline' question to intake
  • Shorten intake to under 10 minutes on mobile

Deliverable: Faster intake shipped

Day 25Outreach

Follow-up wave

  • Follow up with every non-responder once
  • Deliver pending free memos

Deliverable: Follow-up sweep complete

Day 26Trust

Accuracy audit

  • Re-verify implementation fees for top 20 vendors
  • Update fact-sheet versions

Deliverable: Verified fact base snapshot

Day 27Revenue

Pipeline close

  • Ask every warm lead for a decision this week
  • Offer the paid memo with a delivery-time guarantee

Deliverable: Close list of 10 warm leads

Day 28Ops

Support load

  • Write a canned reply set for the five common questions
  • Confirm delivery runs without manual intervention

Deliverable: Support playbook and automated path

Day 29Final push

Maximum touches

  • 50 outreach touches in one day
  • Publish a second redacted example memo

Deliverable: 50 touches, second public example

Day 30Close

Books and next 30 days

  • Reconcile Stripe payouts, refunds and fees
  • Confirm every sale covers delivery cost
  • Write the next-30-day plan from reply-rate data

Deliverable: Final revenue log and next-cycle plan

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 figures are projections from stated assumptions, not verified revenue or existing customers.
  • Price is $199 one-time per memo across every scenario (Concept).
  • Conservative: outreach reply rate near 5%, 4 paid memos, mostly warm community replies.
  • Base: reply rate near 10%, 15 paid memos, 12 categories live by day 15.
  • Upside: two public example memos get organically shared, 40 paid memos including repeats and referrals.
  • Payment processing assumed at Stripe 2.9% + $0.30 per transaction (about 3.0-3.2% of collected revenue).
  • No paid marketing in Conservative or Base; Upside assumes $250 of promoted posts and affiliate payouts.
  • Operating costs cover Vercel, Supabase, domain, Resend and OpenAI narrative calls; free tiers used until volume forces upgrades.
  • No customer is counted before cash is collected inside the contest window.
  • Every sale is priced above per-memo delivery cost, so no sale is loss-making.

Conservative

4 customers
$796
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$25
Paid marketing
$0
Hackathon profit
$771
Operating costs
$45
Business profit
$726

Base case

15 customers
$2,985
collected revenue · avg payment $199
Refunds
$199
Chargebacks
$0
Payment fees
$91
Paid marketing
$0
Hackathon profit
$2,695
Operating costs
$90
Business profit
$2,605

Optimistic

40 customers
$7,960
collected revenue · avg payment $199
Refunds
$398
Chargebacks
$199
Payment fees
$243
Paid marketing
$250
Hackathon profit
$6,870
Operating costs
$210
Business profit
$6,660

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,985
Payment fees (3.9%)
$116
Paid marketing
$0
Hackathon profit
$2,869
Business profit
$2,779

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 the stated assumptions. They are not verified revenue, existing customers, or traction, and they must be re-checked against actual Stripe data daily.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold outreach is ignored and the 12 categories have too few live 'recommend a tool' threads to sustain 30 days of touches.

Mitigation

Track reply rate per category daily and cut to the 4 categories with the most live threads by day 14.

Validation experiment

Send 30 public replies in 48 hours across two categories and count replies and profile visits.

Kill criteria

Fewer than 3 replies from 60 touches across two weeks means the channel is wrong, not the memo.

Risk 2Vendor pricing facts are wrong or stale, so a buyer disproves the TCO and refunds.

Mitigation

Stamp every memo with a verified-on date, store fact-sheet version per order, re-verify top 20 vendors weekly.

Validation experiment

Have 3 free-memo recipients check two vendor prices each against the vendor's own page.

Kill criteria

More than 2 factual errors across 10 delivered memos means curation must be narrowed before selling further.

Risk 3Buyers want live vendor quotes or a call, not a PDF, so $199 feels like a document rather than a decision.

Mitigation

Lead with the forwardable artifact and the 24-month TCO, and price against the 5-10 hours saved.

Validation experiment

Offer the free memo to 10 people and ask directly: would you have paid $199 for this, yes or no, and why.

Kill criteria

Fewer than 2 of 10 free-memo recipients say yes to $199 means the deliverable, not the price, is wrong.

Risk 4Free alternatives (G2, Capterra, Reddit) win because the buyer does not value a structured memo.

Mitigation

Sell time and defensibility, not information; show the TCO lines the free sites hide (seat minimums, implementation, renewal uplift).

Validation experiment

A/B two outreach messages: one on time saved, one on hidden fees caught, and compare reply rates over 40 sends.

Kill criteria

If neither message clears a 5% reply rate over 40 sends, re-scope the buyer before spending more build time.

Risk 5Stripe or TrustMRR verification delays cash collection or holds funds.

Mitigation

Complete verification before day 1, keep a second payout path ready, and record every order in Supabase as source of truth.

Validation experiment

Run one live $1 test charge and a refund on day 1 to confirm the full money path.

Kill criteria

If live payments are not working by day 3, pause outreach and resolve payments before any selling.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create GitHub repo, scaffold Next.js + Tailwind, deploy to Vercel
  • Print and freeze the 12-category list with a one-line definition each

Output: Live deployed skeleton and frozen category list committed to the repo

Hours 3-5

  • Write the fact-sheet JSON schema
  • Curate one full category (10 vendors) end to end as the reference sheet

Output: Schema file plus one complete validated fact sheet

Hours 6-8

  • Build the 12-question intake form with validation
  • Wire the scoring function signature and weight mapping

Output: Intake page that returns a ranked top 3 from the reference sheet

Hours 9-11

  • Run one live $1 Stripe test charge and refund to confirm the money path
  • Connect TrustMRR, confirm Supabase and Resend keys work

Output: Verified payment, database and email connections

Hours 12-14

  • Draft the redacted example memo layout on paper
  • Draft the outreach DM and the public-reply template

Output: Memo wireframe and two sendable message templates

Complete report

Full 30-day launch report

Read the full generated report

Vendor Memo — 30-Day Launch Report

1. Product opportunity and positioning

Software selection is a research task with a deadline bolted on. Companies between 20 and 200 people rarely staff procurement; an ops manager, office manager, or controller is handed a category and a week. They skim review marketplaces, open six pricing pages, and build a spreadsheet that forgets seat minimums, implementation fees, and renewal uplift. The recommendation then gets challenged in a meeting because the analysis was never structured.

Review marketplaces — GetApp, G2, Capterra, Software Advice, TrustRadius — monetize vendors paying for placement and leads. Their incentive is breadth and vendor surfaces, not one buyer's single decision. Nothing in that stack produces a forwardable artifact with a cost model attached.

Vendor Memo charges the buyer $199 and delivers exactly one thing: a 2-page decision memo for one software category, generated from a 12-question intake against a curated fact base. Output: three shortlisted vendors, a weighted matrix tied to the buyer's own must-haves, a 24-month TCO table, and five questions to ask each vendor. It is a file the buyer can forward and defend.

Why it can sell in 30 days: the buyer is reachable one at a time, the deliverable is a file, and $199 is under most approval thresholds. No marketplace cold-start, because vendors do not need to participate. No SEO ramp, because outreach is direct. No procurement, because it is a card charge. The wedge stays narrow: twelve named categories, ten vendors each, manual curation, no reviews, no directory, no accounts.

JEV scored this concept 61.9/100 (band C, confidence 0.66). Strongest on speed to first revenue (8.43) and solo build feasibility (7.58); weakest on market demand (4.88) and monetization (4.81). The plan below therefore compresses the build to five days and spends the remaining 25 days testing demand with outreach rather than expanding the fact base past twelve categories.

2. Smallest sellable MVP

The smallest sellable version is a paid intake that emails one PDF within minutes: twelve categories, ten curated vendors each, a deterministic scoring engine, an auto-renewal-aware TCO table, and a shareable link. Features that ship on day five: the intake form, the JSON fact sheets, the scoring engine, the React-PDF template, Stripe Checkout plus webhook gating, Resend delivery, and a landing page with one redacted example memo.

Not built, deliberately: reviews, ratings, a public directory, vendor lead gen, live scraping, accounts, saved workspaces, team collaboration, RFP workflows, renewal reminders, calls. Every one of those would add a support obligation a solo founder cannot carry in 30 days.

3. Technical implementation plan

Next.js 15 on Vercel with Tailwind; Supabase Postgres for intake and order rows; Stripe Checkout for payment; React-PDF for rendering; Resend for delivery; a versioned JSON fact base in the repo. One serverless route validates answers and runs a pure scoring function over the facts. Stripe's webhook writes the order, renders the PDF, stores it in Supabase Storage, and emails it — all inside one invocation, so the paid path has no queue to babysit. A signed Storage URL is the shareable link. Facts live in JSON with a last_verified field per vendor, and each memo records the fact-sheet version it used. An optional single OpenAI call writes a 120-word rationale, bounded by the deterministic scores and skipped entirely if it fails; the memo must render without it.

The real technical risk is not code, it is factual accuracy. A wrong implementation fee destroys the memo's credibility in public, so curation, versioning, and a visible verified-on date are product features, not admin chores.

4. Pricing and monetization

One product, one price: $199 one-time per decision memo, paid before generation. No subscription in the first 30 days. Revenue grows through the same buyer: a second category, a colleague referral, then possibly a two-category bundle if repeat purchases show up by day 20. The price is defensible against five to ten hours of research and against the hidden fees the memo surfaces.

5. First-customer acquisition

One channel: direct outreach to people who asked a 'recommend a tool' question in the last seven days. Sources are SMB and category subreddits, LinkedIn posts from ops managers and controllers at 20-200 person companies, and public SMB ops Slack and Discord channels. The play is: reply publicly with one specific useful fact (a seat minimum, an implementation fee), then offer to run the memo free in the same breath. Deliver within 24 hours and ask a single question — was this forwardable? Then ask for the $199 paid memo on their next category, and for one referral. Week-one goal: 60 touches, 10 replies, 5 free memos, first paid sale by day 10.

6. 30-day execution roadmap

Days 1-5 build and ship: repo and payment rails, fact-sheet schema with four categories, intake plus scoring engine, PDF with TCO table and payment gating, landing page with a redacted example. Day 5 is the MVP deadline and the product is frozen.

Days 6-14 sell: expand to eight categories, build the outreach tracker, send 30 public replies and 30 DMs, deliver five free memos inside 24 hours, convert to the first $199 sale by day 10, then re-verify flagged vendor facts and publish one redacted memo as public proof. Day 14 is a hard review: cut the two worst-performing categories.

Days 15-21 scale what worked: twelve categories live, clearer landing page with TCO numbers and a refund policy, 40 touches, median payment-to-email time under five minutes, repeat and referral offers to every past buyer, and a go/no-go on a $399 bundle.

Days 22-30 protect and close: audit every delivered memo for missing TCO lines, answer community questions without pitching, shorten the intake, re-verify the top 20 vendors, push all warm leads to a decision, write the support playbook, run 50 touches on day 29, and reconcile Stripe payouts, refunds, and fees on day 30 against the delivery cost of every sale.

7. Revenue and profit scenarios

All numbers are projections, not verified revenue, and carry no claim of customers or traction.

Conservative: 4 memos at $199 = $796 gross, no refunds, no chargebacks, about $25 in Stripe fees (2.9% + $0.30), no ad spend, $45 operating cost. Contest profit is the gross minus refunds, chargebacks, fees, and ads; business profit additionally subtracts operating cost.

Base: 15 memos at $199 = $2,985 gross, one refund at $199, $91 in payment fees, no ad spend, $90 operating cost.

Upside: 40 memos at $199 = $7,960 gross, $398 refunds, $199 chargebacks, $243 in payment fees, $250 in promoted posts and affiliate payouts, $210 operating cost.

Every scenario prices each memo well above delivery cost (a few cents of compute plus email), so no sale is loss-making.

8. Risks and validation experiments

Outreach silence: send 30 public replies in 48 hours and count replies; fewer than 3 replies from 60 touches over two weeks means the channel is wrong. Factual error: have three free-memo recipients check two vendor prices each; more than two errors across ten memos means narrow curation before selling more. Wrong deliverable: ask ten free-memo recipients directly whether they would have paid $199; fewer than two yes answers means the artifact, not the price, is wrong. Free-alternative pressure: A/B the time-saved message against the hidden-fees message over 40 sends. Payment failure: run one live $1 charge and refund on day 1; if live payments are not working by day 3, stop outreach and fix money first.

9. First 24-hour action plan

Hours 1-2: scaffold and deploy the Next.js skeleton, freeze the twelve-category list. Hours 3-5: write the fact-sheet schema and curate one complete ten-vendor category as the reference sheet. Hours 6-8: build the intake form and the scoring function so it returns a ranked top three from the reference sheet. Hours 9-11: run one live $1 Stripe charge and refund, confirm TrustMRR, Supabase, and Resend work end to end. Hours 12-14: wireframe the memo layout and write the DM and public-reply templates so outreach can start on day 7 without drafting time.

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 →