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

PitchBack

Paste any sponsorship pitch email and get a ready-to-send counter-offer with your rate card applied, for newsletter operators and small media brands.

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.41/10
MVP build (solo)
4 days
Launch price
$29 · monthly
Sales to $1,000 revenue
35 customers
First paying customer
Direct X/Twitter DMs to newsletter operators with 'sponsorships' in their bio.
Who pays

Solo newsletter operators and small media brands (1-10 people) who list sponsorships in their bio and receive several brand pitches per week.

Biggest execution risk

Market demand 4.8/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 9; 35 sales at $29 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.6/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

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

0/13
Entry price
$29
Solo build
4 days
30d base revenue
$396
30d hackathon profit
$347
Section 1 of 8

Product opportunity and positioning

Target customer

Solo newsletter operators and small media brands (1-10 people) who list sponsorships in their bio and receive several brand pitches per week.

Why now

The buyer is identifiable by a public bio keyword, the pain recurs weekly, and the deliverable is a single email they can send immediately, so no integration, procurement or trust cycle is required.

Problem

Each inbound pitch takes 15-30 minutes of checking rate card, inventory and deliverables before replying, so operators underprice or reply too slowly and lose the slot.

Solution

The operator saves a rate card once, pastes a pitch, and PitchBack extracts brand, budget, timeline and deliverables, applies floor and package rules, and returns a plain-text counter-offer email with a copy button.

Differentiation · A general AI assistant writes a confident reply with no prices because it has never seen the operator's floor price; PitchBack holds the rate card and always prices against it.

PitchBack — Opportunity and Positioning

Sponsorship inbound is the highest-value email a small publisher receives and the one they handle worst. A solo operator with 20,000 subscribers gets several brand pitches a week. Each one requires opening the rate card, checking whether that inventory slot is still free, deciding whether the offered budget clears the floor, and rewriting a reply from scratch. Fifteen to thirty minutes per email, done in the gaps between writing the issue. The failure mode is not silence — it is a reply that undersells, or a slow reply that loses the slot to a faster publisher.

The current workaround is a Google Doc rate card plus copy-paste plus mental arithmetic. The alternatives are CRMs built for outbound sales teams, or a general AI assistant that drafts a confident email with no prices in it because it has never seen the floor. PitchBack is deliberately narrow: not an inbox tool, not a CRM, no OAuth, no spreadsheet sync. The buyer pastes one pitch; the product returns one priced counter-offer.

JEV scored this concept 64.1/100 (band C), with high confidence. It is strongest exactly where a 30-day contest rewards strength — speed to first revenue (8.61 normalized) and solo build feasibility (7.77). It is weakest on market demand (4.82) and competitive defensibility (4.94). This plan does not pretend those weaknesses away; it routes around them. Demand risk is handled by selling a named output rather than a software category, and by making the first sample free and manual. Defensibility risk is handled by owning the operator's own data: their floor price, their packages, their blackout weeks. That rate card is not in any general assistant's context window, and rebuilding it elsewhere costs the buyer more than $29.

The wedge is one screen wide on purpose. Broad email AI is a commodity bundled into Gmail and Outlook; a priced counter-offer against a private rate card is not. Every additional feature — inbox sync, CRM pipeline, analytics — moves the product back toward the commodity and away from the one thing the buyer cannot get for free. Scope discipline is therefore the positioning, not a schedule compromise.

The commercial bet is simple: if one delivered counter-offer demonstrably raises a deal price by $200, a $29 monthly subscription pays for itself on the first reply. The 30 days exist to test that bet with real payments, not to build a platform.

Section 2 of 8

Smallest sellable MVP

A paid account where pasting one sponsorship pitch returns a priced, on-brand counter-offer email the operator can copy and send without editing.

Must-have features

  • Paste-in pitch textarea with submit
  • Rate card and package setup form stored per account
  • Extraction of brand, budget, timeline and deliverables into editable fields
  • Rule engine that counter-prices below-floor offers up to the nearest package
  • Plain-text counter-offer generation with copy button
  • Stripe Checkout for $29 Starter and $79 Pro monthly
  • Magic-link login via email
  • History list of past pitches and their offers

Explicitly out of scope

  • Gmail or Outlook OAuth inbox sync
  • Google Sheets or live inventory connectors
  • Auto-send or sequence features
  • CRM pipeline and deal stages
  • Team seats and role permissions
  • Analytics dashboards
  • Mobile app
  • Self-serve free tier

Demo flow (what the buyer sees)

  1. Operator signs up with a magic link
  2. Fills rate card: packages, floor price, deliverables, unavailable weeks
  3. Pastes a real inbound pitch into the textarea
  4. Reviews extracted brand, budget range, timeline and deliverables
  5. Confirms and generates the counter-offer
  6. Copies the plain-text email and sends it from their own client
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase PostgresSupabase magic-link authResend for auth emailOpenAI API with structured JSON outputStripe Checkout and Billing PortalTailwind CSSVercel analytics

Architecture

A single Next.js app on Vercel serves the marketing page and an authenticated app shell. Supabase holds accounts, rate cards, pitches and generated offers, with row-level security scoped to the user. A server route takes pasted pitch text, calls OpenAI once for structured extraction into brand, budget range, budget confidence, timeline and deliverables, and returns JSON that renders as editable fields. On confirm, a deterministic rule function compares the extracted budget against the stored floor and package ladder and selects a branch: accept, counter up to the nearest package, downgrade to a smaller package, or decline. A second OpenAI call turns the chosen branch plus tone into a plain-text email. Stripe Checkout creates the subscription and a webhook flips an entitlement flag; generation is gated on that flag plus a usage counter.

Build steps

  1. Create Next.js repo, Vercel project and Supabase project; deploy an empty page to a real domain.
  2. Define Postgres tables: accounts, rate_cards, packages, pitches, extractions, offers, entitlements.
  3. Add magic-link auth with Supabase and Resend; protect app routes.
  4. Build the rate card form with package ladder, floor price, deliverables and blackout weeks.
  5. Implement the extraction route with a JSON schema response format and store the raw model output.
  6. Render extraction as editable fields with a confidence flag on budget.
  7. Write the pure rule function for accept, counter, downgrade and decline branches; unit test it against ten fixtures.
  8. Implement the drafting route that converts a chosen branch into a plain-text email with a copy button.
  9. Add Stripe Checkout for both tiers plus a webhook that sets entitlement, and add a usage counter.
  10. Add the history list, error states and a re-run button on failed extraction.
  11. Deploy, run ten real pitches end to end, and fix the two worst output failures.

AI components

  • Structured extraction of brand, budget range, budget confidence, timeline and deliverables from raw pitch text
  • Drafting of the plain-text counter-offer from the selected pricing branch and a tone setting
Hardest technical risk: Budget extraction on messy text: pitches bury numbers as ranges, hedges or vague bands, and a wrong budget produces a wrong price, which is the only error that permanently destroys trust.
Section 3 of 8

Pricing and monetization

Starter

Entry offer
$29 / month

For Solo newsletter operators

  • Unlimited counter-offer drafts
  • One rate card
  • Pitch and offer history
  • Copy-to-clipboard plain text

Pro

$79 / month

For Small media brands running multiple properties

  • Multiple rate cards
  • Priority generation queue
  • Export to .txt and .md
  • Everything in Starter

Model: Two monthly subscriptions billed through Stripe Checkout, no free tier, with a manually delivered free sample used as the trial.

First revenue offer: Send me your next real sponsorship pitch and your rate card; I will return a priced counter-offer within ten minutes, free, no signup. If it is useful, the link is $29 a month.

Expected ACV: $33

Upsell path: Upgrade Starter to Pro at $79 when a second rate card appears, then annual prepay at ten months' price, then a higher Starter floor if conversion holds above 30%.

Target customers
40
Revenue model
$1,160
Costs
$80
Profit model
$1,080
Section 4 of 8

First-customer acquisition

Primary channel

Direct X/Twitter DMs to newsletter operators with 'sponsorships' in their bio.

Where to find them

  • X bio search for 'newsletter' plus 'sponsorships'
  • X bio search for 'sponsorship' plus 'substack'
  • Operators who tweet about brand deals closing in the last 14 days
  • Newsletter directories cross-referenced with an X handle
  • Talent managers on LinkedIn who list three or more creator clients

Exact outreach motions

  • Build a 100-row sheet with handle, subscriber count, niche and contact route before sending anything.
  • Send 30 DMs offering a free counter-offer on their next real pitch, delivered in ten minutes.
  • Deliver every accepted pitch through the app within the same day and reply with the finished offer.
  • Send the Stripe link only after the buyer has seen the output, referencing their own pitch.
  • Follow up once on day 10 with a second sample counter-offer, never a second pitch of the product.

Message template

Hey {name} — you take sponsorships on {newsletter}, so your inbox is probably full of brand pitches. Send me your next one plus your rate card and I'll send back a priced counter-offer in 10 minutes, free, no signup. If it's not useful, ignore me.
Week-one goal: 30 DMs sent, at least 6 replies, 3 counter-offers delivered, 1 paid $29 subscription by day 9.
Section 5 of 8

30-day execution roadmap

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

Stand up the app and the data model

  • Create Next.js repo on Vercel and a Supabase project.
  • Model rate cards, packages, pitches, extractions and offers.
  • Register a domain and connect the TrustMRR-linked Stripe account.
  • Draft the extraction prompt with a strict JSON schema.

Deliverable: Empty app live at a real domain with Stripe connected.

Day 2Accounts

Auth and rate card capture

  • Ship magic-link signup with Supabase and Resend.
  • Build the rate card form with package ladder and floor price.
  • Store rate cards under row-level security.

Deliverable: A user can sign up and save a complete rate card.

Day 3Extraction

Turn a pitch into structured fields

  • Wire the extraction route with JSON response format.
  • Render brand, budget, timeline and deliverables as editable fields.
  • Flag low-confidence budgets and add a re-run button.

Deliverable: Pasted pitch becomes a correctable deal summary.

Day 4Pricing logic

Rule engine and drafting

  • Encode accept, counter, downgrade and decline branches against the floor.
  • Generate a plain-text counter-offer with a copy button.
  • Test the full flow against ten real pitches.

Deliverable: End-to-end counter-offer from paste to copy.

Day 5MVP deadlineMVP shipped

Paid, gated, deployed

  • Add Stripe Checkout for Starter $29 and Pro $79 monthly.
  • Gate generation behind entitlement plus a usage counter.
  • Ship the history list and run five fresh pitches live.

Deliverable: Paid PitchBack v1 live; MVP deadline met.

Day 6List building

100 named operators

  • Build a 100-row sheet from X bio searches.
  • Record subscriber count, niche and a contact route per row.
  • Write three DM variants and pick one.

Deliverable: 100-row outreach sheet ready to send.

Day 7Wave one

First 30 DMs

  • Send 30 DMs with the free counter-offer offer.
  • Reply to every response within two hours.
  • Log replies and objections in the sheet.

Deliverable: 30 DMs sent with a live reply log.

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

Deliver by hand

  • Turn every positive reply into a delivered counter-offer same day.
  • Run each pitch through the app and note every failure.
  • Fix the two worst output bugs tonight.

Deliverable: Three to six delivered counter-offers.

Day 9First saleFirst sale target

Convert delivered offers

  • Send the Stripe link to everyone who received a counter-offer.
  • Ask one buyer to pay today for unlimited drafts.
  • Post a short build-in-progress thread.

Deliverable: First paid $29 subscription collected.

Day 10Follow-up

Second touch and proof

  • Follow up once on day-7 DMs with a second sample offer.
  • Send 20 new DMs from the sheet.
  • Publish a sample-output page on the site.

Deliverable: 50 DMs total and a public sample page.

Day 11Quality

Make the draft editable-ready

  • Revise the drafting prompt using five real buyer edits.
  • Add a tone selector: firm, friendly, walk-away.
  • Add one line to every offer that justifies the price.

Deliverable: v1.1 with tone control and price rationale.

Day 12Wave two

Second segment

  • Send 25 DMs to podcast and newsletter hybrids.
  • Offer a 7-day trial to non-responders only.
  • Collect two written testimonials.

Deliverable: 75 DMs sent and two testimonials captured.

Day 13Trials

Convert or cut

  • Email each trial user one question: did the offer go out?
  • Convert anyone who sent it to a paid plan.
  • Expire trials inactive for five days.

Deliverable: Trial-to-paid conversions recorded.

Day 14Week two review

Pick one winning message

  • Compute DM reply rate, delivery rate and paid rate.
  • Keep the best message and retire the others.
  • Set the week three customer number.

Deliverable: One winning message and a week three target.

Week 3 · Repeat & systematize · 7 days
Day 15Pro tier

Raise ARPU

  • Ship multiple rate cards behind Pro at $79.
  • Attempt upgrades on two multi-property users.
  • Add export to .txt and .md.

Deliverable: Pro tier live with two upgrade attempts made.

Day 16Second channel

One video test

  • Record a 60-second screen capture of a real pitch to counter-offer.
  • Share it in two operator communities with a UTM link.
  • Track clicks and signups from the video.

Deliverable: One demo video and first click data.

Day 17Onboarding

Cut time to first draft

  • Add a prefilled example rate card on first run.
  • Reduce signup to a single screen.
  • Get first generation under 30 seconds.

Deliverable: Signup to first draft under two minutes.

Day 18Wave three

Contextual outreach

  • DM 30 operators who posted about sponsorships this week.
  • Open with a reference to their specific post.
  • Book interested replies into 15-minute slots.

Deliverable: 30 contextual DMs sent.

Day 19Retention

Stop quiet churn

  • Add a weekly digest email of pitches and offers.
  • Email churned users a single question.
  • Fix the top churn reason found.

Deliverable: Digest live and churn reason identified.

Day 20Referral

Borrow the buyer's network

  • Add a shareable sample offer with rate card stripped.
  • Offer one free month per referred paying operator.
  • Announce the referral to existing customers.

Deliverable: Referral mechanism live and announced.

Day 21Week three review

Channel decision

  • Count paying customers and monthly recurring revenue.
  • Remove any feature with zero usage.
  • Decide between more DMs or doubling community posts.

Deliverable: Documented channel decision for week four.

Week 4 · Scale what works · 7 days
Day 22Pricing test

Find the ceiling

  • Test $39 Starter on half of new traffic.
  • Compare conversion against the $29 cohort.
  • Lock the winning price for new signups.

Deliverable: Pricing decision backed by cohort data.

Day 23Wave four

Managers

  • DM 30 talent managers who handle three or more creators.
  • Lead with the multiple rate cards angle.
  • Follow up once after three days.

Deliverable: 30 manager DMs logged with pipeline status.

Day 24Trust

Remove objections

  • Publish three anonymised before-and-after counter-offers.
  • Add a clear no-inbox-access statement to the homepage.
  • Publish a 7-day no-questions refund policy.

Deliverable: Trust page and refund policy live.

Day 25Speed

Latency

  • Cache rate card lookups per account.
  • Bring average generation under 12 seconds.
  • Add progress text during generation.

Deliverable: Faster generation shipped and measured.

Day 26Wave five

Recycle everything

  • DM 30 operators with a segment-specific claim.
  • Re-DM every non-opener from day 7.
  • Push every replier into a same-day demo.

Deliverable: 90 total DMs logged with full follow-up.

Day 27Annual plan

Cash today

  • Add an annual plan at ten months' price.
  • Offer it to every active subscriber.
  • Track acceptance rate.

Deliverable: Annual plan live and offered to all subscribers.

Day 28Support

Stay solo

  • Write a six-question FAQ.
  • Add an in-app feedback box.
  • Set a two-hour daily support window.

Deliverable: Self-serve support shipped.

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

Close warm leads

  • Send a last-call DM to every warm lead.
  • Offer a $19 first month to close today.
  • Post the final build thread with real numbers.

Deliverable: All warm leads contacted before the deadline.

Day 30Close

Reconcile and report

  • Reconcile Stripe revenue, refunds and fees.
  • Publish the results post using collected figures only.
  • Freeze scope and list week-one post-contest tasks.

Deliverable: Reconciled results and a public 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/Base/Upside: ARPU is blended across Starter $29 and Pro $79, weighted heavily toward Starter.
  • Conservative: cold DMs convert slowly; 3 paying customers by day 30 with no paid spend.
  • Base: 12 paying customers, one refund, $33 blended ARPU after first-month discounts.
  • Upside: 26 paying customers, two refunds, $36 blended ARPU from a Pro-heavy mix and $120 of paid promotion.
  • Payment processing assumed at roughly 5% of collected revenue (Stripe 2.9% + $0.30 plus international card fees).
  • Operating cost covers domain, Vercel and Supabase paid tiers, Resend and OpenAI inference to serve those customers.
  • No chargebacks are projected; disputes for a $29 subscription are rare in the first 30 days.
  • All figures are projections, not verified revenue.

Conservative

3 customers
$87
collected revenue · avg payment $29
Refunds
$0
Chargebacks
$0
Payment fees
$4
Paid marketing
$0
Hackathon profit
$83
Operating costs
$25
Business profit
$58

Base case

12 customers
$396
collected revenue · avg payment $33
Refunds
$29
Chargebacks
$0
Payment fees
$20
Paid marketing
$0
Hackathon profit
$347
Operating costs
$45
Business profit
$302

Optimistic

26 customers
$936
collected revenue · avg payment $36
Refunds
$58
Chargebacks
$0
Payment fees
$47
Paid marketing
$120
Hackathon profit
$711
Operating costs
$90
Business profit
$621

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$348
Payment fees (3.9%)
$14
Paid marketing
$0
Hackathon profit
$334
Business profit
$289

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

Scenario models from stated assumptions, not verified revenue.

Section 7 of 8

Main risks and validation experiments

Risk 1Low DM reply rate on X with no existing audience.

Mitigation

Send two message variants, keep messages free-sample-first with no product mention, and reply within two hours.

Validation experiment

Send 30 DMs across two variants on day 7 and count replies by variant within 72 hours.

Kill criteria

Fewer than 3 replies from 30 DMs means the message or the channel is wrong; rewrite once, then switch to operator communities if the second wave also fails.

Risk 2Buyers keep using their own templates and never pay.

Mitigation

Send the Stripe link only after a delivered counter-offer, so the ask is anchored to real output rather than a promise.

Validation experiment

Track paid conversion across the first 20 delivered counter-offers.

Kill criteria

If fewer than 1 in 5 delivered counter-offers converts to a paid subscription, pivot to a pay-per-offer price rather than continuing to sell a monthly plan.

Risk 3Extraction errors on ambiguous budgets erode trust.

Mitigation

Show extracted fields as editable with a confidence flag, and route below-floor offers to a walk-away branch instead of a silent discount.

Validation experiment

Run 10 real pitches through extraction and count how many need the buyer to correct the budget field.

Kill criteria

If more than 4 of 10 need budget correction, stop outreach and rework the prompt and schema before sending wave two.

Risk 4Price ceiling is too low to produce meaningful profit in 30 days.

Mitigation

Test a $39 Starter and an annual prepay so ARPU can rise without new acquisition.

Validation experiment

Split new traffic 50/50 between $29 and $39 from day 22 and compare paid conversion.

Kill criteria

If $39 converts at less than half the rate of $29, keep $29 and accept that this concept is a small-revenue test, not a $100k contender.

Risk 5Churn after month one when the operator's pitch volume drops.

Mitigation

Add a weekly digest that shows offers sent and estimated value managed, so the subscription stays visible.

Validation experiment

Email every subscriber after 14 days asking whether they sent an offer in the last week.

Kill criteria

If more than half of paying users sent zero offers in a week, the wedge is too infrequent for a monthly subscription and pricing must move to per-offer credits.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js repo and Vercel project.
  • Create the Supabase project and domain.
  • Link the Stripe account to TrustMRR before any customer exists.

Output: Deployed empty app, a live domain, and a connected payment account.

Hours 3-4

  • Write the Postgres schema for accounts, rate cards, packages, pitches, extractions and offers.
  • Define the four extraction fields and the floor-price rule signature.

Output: Applied schema in Supabase and a written extraction contract.

Hours 5-7

  • Build the paste-in textarea and submit route.
  • Call OpenAI with a strict JSON schema for brand, budget, timeline and deliverables.
  • Store the raw response and render fields as editable.

Output: First working extraction on a real pitch saved to Postgres.

Hours 8-9

  • Test extraction on three messy real pitches.
  • Note the two worst failure cases in a running log.

Output: A failure log that drives day 3 prompt work.

Hours 10-12

  • Draft the DM message with two variants.
  • Start the 100-operator sheet from X bio searches.
  • Collect the first 25 qualified names.

Output: Two DM variants and 25 named prospects.

Complete report

Full 30-day launch report

Read the full generated report

PitchBack — 30-Day Launch Report

1. Product opportunity and positioning

Sponsorship inbound is the highest-value email a small publisher receives and the one they handle worst. A solo operator with 20,000 subscribers gets several brand pitches a week. Each one requires opening the rate card, checking whether that inventory slot is still free, deciding whether the offered budget clears the floor, and rewriting a reply from scratch. Fifteen to thirty minutes per email, done in the gaps between writing the issue. The failure mode is not silence — it is a reply that undersells, or a slow reply that loses the slot to a faster publisher.

The current workaround is a Google Doc plus copy-paste plus mental arithmetic. The alternatives are CRMs built for outbound sales teams, or a general AI assistant that drafts a confident email with no prices in it because it has never seen the floor. PitchBack is deliberately narrow: not an inbox tool, not a CRM, no OAuth, no spreadsheet sync. The buyer pastes one pitch; the product returns one priced counter-offer.

JEV scored this concept 64.1/100 (band C), confidence 0.76. It is strongest where a 30-day contest rewards strength — speed to first revenue (8.61 normalized) and solo build feasibility (7.77). It is weakest on market demand (4.82) and competitive defensibility (4.94). This plan does not pretend those weaknesses away. Demand risk is handled by selling a named output rather than a software category, with the first sample delivered free and by hand. Defensibility risk is handled by owning the buyer's own data: their floor price, their packages, their blackout weeks. That rate card is not in any general assistant's context window, and rebuilding it elsewhere costs the buyer more than $29.

The wedge is one screen wide on purpose. Broad email AI is now a commodity bundled into Gmail and Outlook; a priced counter-offer against a private rate card is not. Every added feature — inbox sync, CRM pipeline, analytics — moves the product back toward the commodity and away from the one thing the buyer cannot get free. Scope discipline is the positioning, not a schedule compromise.

The commercial bet: if one delivered counter-offer raises a deal price by $200, a $29 monthly plan pays for itself on the first reply. The 30 days exist to test that bet with real payments, not to build a platform.

2. Smallest sellable MVP

The sellable unit is a single counter-offer email the buyer can send without editing. Everything that does not produce that email is cut.

Shipped by day 5: paste-in pitch box, one rate card form (packages, floor price, deliverables, unavailable weeks), extraction into brand, budget, timeline and deliverables shown as editable fields, a rule that counter-prices below-floor offers up to the nearest package, a plain-text counter-offer with a copy button, Stripe Checkout, and a history list.

Not built: inbox sync, spreadsheet connectors, auto-send, CRM pipeline, team seats, analytics, mobile app.

The editable extraction fields matter more than they look. They convert a wrong guess into a correction, and a correction costs the buyer two seconds instead of a lost deal.

3. Technical implementation plan

Next.js on Vercel, Supabase for magic-link auth and Postgres, OpenAI structured JSON output for extraction, a second prompt for drafting, Stripe Checkout for subscriptions, Resend for magic links. Four build days, one hardening day.

Order: repo and data model on day 1; auth and rate card form on day 2; extraction and editable fields on day 3; rule engine, drafting and copy button on day 4; Stripe gating, usage counter and deploy on day 5.

The hardest technical problem is budget extraction. Pitches bury numbers — 'somewhere in the low four figures', 'two to three k depending on format' — and a wrong budget produces a wrong price, which is the only error that permanently destroys trust. Mitigation: the model returns a budget range plus a confidence flag, both visible and editable, and offers below the floor always render the walk-away or downgrade branch rather than a silent discount. Store every pasted pitch and every buyer edit; those edits are the signal for prompt revision on days 8 and 11.

4. Pricing and monetization

Starter at $29/month: unlimited drafts, one rate card, history. Pro at $79/month: multiple rate cards, priority generation, text export. Monthly, card up front, cancel anytime.

There is no self-serve free tier. Free users paste once and leave, and the product's whole value is a repeated weekly action. The free sample is manual instead: the founder runs one real pitch through the app and sends back the counter-offer. That costs ten minutes and converts far better than a trial nobody activates.

Base-case blended ARPU is $33, reflecting a mostly-Starter mix with a minority upgrading to Pro once they run a second property. Revenue grows by upgrading on the second rate card, by annual prepay at ten months' price, and by raising the Starter floor if conversion holds above 30%.

5. First-customer acquisition

One channel: X/Twitter DMs to operators who put 'sponsorships' in their bio. That keyword is the entire targeting strategy — it is self-declared, current, and implies they already receive pitches.

Build a 100-row sheet on day 6 with handle, subscriber count, niche and contact route. Send 30 DMs on day 7. The message does not pitch software. It offers to convert their next real pitch into a counter-offer within ten minutes, free, no signup.

Week-one goal: 30 DMs sent, at least 6 replies, 3+ counter-offers delivered, 1 payment by day 9. Fewer than 3 replies from 30 DMs means the message is wrong, not the product, and the message changes before more DMs go out.

6. 30-day execution roadmap

Days 1-5 build and ship the paid MVP. Days 6-7 build the list and send wave one. Days 8-9 deliver counter-offers by hand and collect the first payment. Days 10-14 run a quality pass, waves two and three, trial conversions, then a week-two review that picks one winning message. Days 15-21 ship the Pro tier, test one video channel, compress onboarding, add a retention digest, launch a referral loop, then a week-three review that decides between DMs and community posts. Days 22-28 run a pricing test, waves four and five, publish a trust page, cut latency, add an annual plan and self-serve docs. Days 29-30 do last-call outreach, then reconcile and publish.

The sequencing matters: revenue collection starts on day 9, so the remaining three weeks are conversion and quality work rather than construction. Every day has one deliverable, and no deliverable is a document.

7. Revenue and profit scenarios

All three scenarios are projections from stated assumptions, not verified revenue.

Conservative: 3 customers at $29 blended ARPU, $87 gross, no refunds, about $4 in processing fees, no ad spend, $25 operating cost.

Base: 12 customers at $33 blended ARPU, $396 gross, one $29 refund, about $20 in processing fees, no ad spend, $45 operating cost.

Upside: 26 customers at $36 blended ARPU, $936 gross, two refunds totalling $58, about $47 in processing fees, $120 of paid promotion, $90 operating cost.

Contest ranking uses hackathon profit: gross minus refunds, chargebacks, processing fees and paid marketing. Hosting, domain and inference cost are excluded from that figure but included in business profit, which also subtracts operating cost. On the base case that is roughly $347 hackathon profit and roughly $302 business profit before the founder's time.

None of these figures approaches $100,000. This concept is a real revenue test at small scale, not a $100k contender, and pretending otherwise would corrupt every decision downstream — especially the day-22 pricing test and the decision to keep sending DMs.

8. Risks and validation experiments

DM reply rate is the largest unknown. Test: 30 DMs across two message variants on day 7, replies counted at 72 hours. If fewer than 3 of 30 reply, rewrite once, then move to operator communities.

Willingness to pay versus free templates. Test: send the Stripe link only after a delivered counter-offer and track conversion across the first 20 deliveries. Below 1 in 5, switch from subscription to pay-per-offer.

Extraction accuracy. Test: 10 real pitches, count how many need the buyer to correct the budget field. Above 4 of 10, stop outreach and rework the prompt.

Price ceiling against the contest. Test: $39 Starter on half of new traffic from day 22. If it converts at less than half the $29 rate, keep $29 and accept the smaller number honestly.

9. First 24-hour action plan

Hours 1-2: repo, Supabase project, domain, Stripe account linked to TrustMRR before any customer exists. Hours 3-4: Postgres schema for accounts, rate cards, packages, pitches, extractions and offers, plus a written extraction contract. Hours 5-7: paste-in form and the first OpenAI extraction call returning strict JSON, rendered as editable fields. Hours 8-9: run three messy real pitches and log the two worst failures. Hours 10-12: draft two DM variants and collect the first 25 qualified operator names.

Output by hour 12: a deployed skeleton, one working extraction saved to the database, a failure log, and a partially built outreach sheet.

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 →