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

Ghostthread Invoice

Turns cold email threads into a one-page 'deal revival' brief with a ready-to-send follow-up, for solo agency owners chasing silent high-ticket proposals.

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.

Promising6.54/10
MVP build (solo)
4 days
Launch price
$19
Sales to $1,000 revenue
53 customers
First paying customer
Direct X and LinkedIn DMs to agency owners publicly posting about stalled proposals or being ghosted.
Who pays

Solo or 2-5 person creative/dev agency owner who personally sells $5k-$50k projects and has 5-30 silent proposals sitting in their sent folder.

Biggest execution risk

Monetization potential 4.6/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 4 days; the plan targets a first sale on day 9; 53 sales at $19 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 9.3/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

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

0/14
Entry price
$19
Solo build
4 days
30d base revenue
$990
30d hackathon profit
$951
Section 1 of 8

Product opportunity and positioning

Target customer

Solo or 2-5 person creative/dev agency owner who personally sells $5k-$50k projects and has 5-30 silent proposals sitting in their sent folder.

Why now

No OAuth, no inbox permission and no migration means checkout and delivery happen in one session, so a first paid brief is possible on day one of traffic.

Problem

High-ticket proposals go quiet and the owner never follows up, because re-reading an old thread and writing a non-needy nudge costs 30-60 minutes of emotional labour.

Solution

The owner pastes or forwards one cold thread; the tool extracts deal value, last-contact date and stated objections, then renders a one-page revival brief (HTML + PDF) and three tone variants of a short follow-up email, delivered to the buyer's inbox after Stripe checkout.

Differentiation · Generic AI writers produce a nudge from a thread snippet; Ghostthread produces a structured artifact — deal value, silence duration, objection map, why-it-stalled hypothesis, angle, and the draft — which is the thing the owner actually re-reads before sending.

1. Product opportunity and positioning

Ghostthread Invoice is a paid artifact, not a dashboard. A solo agency owner pastes one cold email thread, or forwards it, and within minutes receives a one-page "deal revival brief" plus a short follow-up email in three tones. That is the entire product.

The positioning is deliberately narrow: not an inbox assistant, not a CRM, not a sales-engagement suite. It competes against the owner's own avoidance behaviour. Re-reading an eight-month-old thread, remembering what was promised, and writing a nudge that does not sound needy takes 30-60 minutes of emotional labour. Owners skip it, and the proposal dies of inaction rather than rejection. Ghostthread charges $19 to make that task take four minutes.

The economics favour the buyer immediately: the deal on the thread is $5k-$50k, so any reply at all has an asymmetric payoff versus a $19 charge. There is no OAuth, no inbox permission, no data migration and no team rollout, which is why JEV scored speed_to_first_revenue at 9.26 and solo_build_feasibility at 7.89. The plan below is built to spend that advantage rather than a marketing budget.

The two known weaknesses are honest. Monetization potential scored 4.63: a $19 one-off is small, so the plan pushes the $99 Revival Pack as the default offer and adds a 10-brief bundle after validation. Competitive defensibility scored 5.14: the moat is not the model but the brief format, the speed of delivery, and the accumulated library of before/after examples the founder publishes.

Everything in this report is a projection or a plan. No customers, revenue, partnerships or market statistics are claimed.

2. Smallest sellable MVP

One page, one form, one output. The buyer pastes a thread or emails it to a forwarding address, pays $19 or $99, and gets a PDF brief plus a plain-text email draft by return mail. Six features ship: paste/forward intake, LLM extraction of deal value, last contact date and objections, HTML-to-PDF brief renderer, three-tone follow-up generator, Stripe Checkout with instant email delivery, and a history list keyed by buyer email.

Not built, deliberately: Gmail or Outlook OAuth, LinkedIn or news scraping, CRM sync, team seats, admin console, automated sending, subscriptions, mobile app.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres for threads and briefs, OpenAI for extraction and drafting, Stripe Checkout for payment, Resend for delivery, react-pdf for the PDF. A single webhook on payment success queues generation and emails the result. Extraction uses structured JSON output so the renderer never guesses; a validator blocks any claim not present in the thread text.

The hardest risk is a confident misread — wrong deal value, wrong date, invented commitments — producing a brief that embarrasses the buyer. Mitigation: show every extracted field with its source quote, and let the buyer correct it before the draft regenerates.

4. Pricing and monetization

$19 Single Brief, $99 Revival Pack of five with priority turnaround. Both one-time. No subscription in the first 30 days. The pack is the offer pushed in every DM because it converts a $19 decision into a $99 decision and gives the buyer five chances to see value. After day 20, a $199 ten-brief bundle tests willingness to pre-buy. Payment via Stripe Checkout; assume 2.9% + $0.30 per transaction, roughly 4% blended.

5. First-customer acquisition

One channel: direct DMs on X and LinkedIn to agency owners who publicly post about stalled proposals or being ghosted. Search phrases include "proposal went cold", "client ghosted", "followed up twice nothing". The offer is always a free brief on one real thread first, delivered within an hour by a human, followed by the $99 pack ask. No ads. Week-one goal: 60 DMs, 8 threads received, 5 free briefs delivered, 1 paid pack by day 9.

6. 30-day execution roadmap

Days 1-4 build the MVP; day 5 is a hardening and dry-run day. Days 6-8 produce three public before/after teardowns and seed the DM list. Day 9 is the first-sale target. Days 10-21 are a daily loop: 20 DMs, free briefs, ask for the pack, publish one teardown every second day. Day 22 adds the $199 bundle and a one-click forward-to-brief address. Days 23-29 scale outreach and collect reply data as the marketing asset. Day 30 is accounting, TrustMRR reconciliation and shutdown of anything that costs money without converting.

7. Revenue and profit scenarios

Three projections only. Conservative: 3 packs at $99 = $297. Base: 10 packs = $990. Upside: 25 packs = $2,475, with $150 of paid promotion and $50 of refunds. Processing fees are modelled at about 4% of collected revenue. Operating cost stays between $25 and $90 across all three, since brief generation costs cents per run. None of these numbers is verified; they are hypotheses with stated inputs.

8. Main risks and validation experiments

DM replies may be near zero, so the first experiment is 30 DMs measured by threads received rather than money. Buyers may want inbox automation, so the free brief is the test: if owners ask for OAuth twice as often as they ask for a second brief, the wedge is wrong. Drafts may read generic, so every free brief ships with a one-line feedback request and we track the edit rate. Volume may stay far below $100k, which is expected and acceptable for a 30-day artifact business.

9. First 24-hour action plan

Hours 1-2: reserve domain, create Vercel and Supabase projects, set up Stripe test keys. Hours 3-5: schema for threads and briefs, intake form shipped. Hours 6-8: extraction prompt and JSON validator. Hours 9-12: renderer and PDF. Hours 13-16: Stripe Checkout, webhook, Resend delivery. Hours 17-20: run three real (founder-supplied) threads end to end and fix the worst output. Hours 21-24: build the DM target list of 40 agency owners and send the first 10 messages.

Section 2 of 8

Smallest sellable MVP

A Stripe checkout that accepts one pasted thread and emails back one PDF revival brief plus one follow-up draft within 10 minutes.

Must-have features

  • Paste-or-forward thread intake form
  • LLM extraction of deal value, last contact date, stakeholders and stated objections
  • One-page revival brief renderer (HTML plus PDF)
  • Follow-up email generator with three tone options
  • Stripe Checkout with instant email delivery via Resend
  • Buyer history list keyed by email

Explicitly out of scope

  • No Gmail or Outlook OAuth
  • No LinkedIn or news scraping
  • No CRM sync
  • No team seats or admin console
  • No automated sending of emails
  • No subscriptions or recurring billing
  • No mobile app

Demo flow (what the buyer sees)

  1. Buyer clicks a Stripe payment link
  2. Buyer pastes the cold thread into the post-payment intake form
  3. Server stores the thread and runs structured extraction
  4. Extracted fields with source quotes are shown for a 15-second confirm
  5. Brief renders as HTML and PDF
  6. Resend emails the PDF and three drafts
  7. Brief appears in the buyer's history list
Build plan

Technical implementation plan

Stack

Next.js (App Router) on VercelSupabase Postgres for threads and briefsOpenAI API for extraction and draftingStripe CheckoutResend for transactional emailreact-pdf on the Node runtime for the PDFVercel Cron for retry of failed deliveries

Architecture

A public marketing page and a Stripe Checkout link handle payment. The Stripe webhook creates a brief record in Supabase and kicks off generation in a serverless function: extract structured fields, validate each field against a verbatim quote from the thread, render the brief as HTML and PDF, generate three drafts, attach everything to a Resend email. A forwarded-thread alias maps inbound mail to a buyer by sender address. Nothing runs on a server the founder has to babysit.

Build steps

  1. Day 1: scaffold Next.js, Supabase schema (threads, briefs, buyers), deploy to Vercel
  2. Day 1: build the paste intake form and store raw thread text
  3. Day 2: write the extraction prompt with strict JSON schema and a quote-provenance validator
  4. Day 2: build the HTML brief renderer with fixed sections (deal snapshot, silence duration, objections, stall hypothesis, recommended angle)
  5. Day 3: add PDF rendering and the three-tone draft generator
  6. Day 3: wire Stripe Checkout, webhook, and Resend delivery with attachment
  7. Day 4: add buyer history list and the inbound forward-to-brief address
  8. Day 4: add error handling, retry on failed generation, and a fallback manual delivery path
  9. Day 5: dry-run on 5 real threads, tune prompts, harden output

AI components

  • Structured extraction of deal value, dates, stakeholders and objections from raw thread text
  • Stall-cause hypothesis generation grounded strictly in thread content
  • Three-tone follow-up email drafting (direct, warm, value-add)
  • Optional subject line variants
Hardest technical risk: The extraction step confidently misreading a quoted email chain — wrong deal value or wrong last-contact date — and producing a brief that damages the buyer's credibility with the prospect.
Section 3 of 8

Pricing and monetization

Single Brief

Entry offer
$19 one-time

For Owner testing the tool on one dead deal

  • One revival brief PDF
  • One follow-up email draft

Revival Pack

$99 one-time

For Owner with a backlog of 5-30 silent proposals

  • Five revival briefs
  • Five follow-up drafts with three tones each
  • Priority turnaround under 60 minutes

Model: One-time purchases: $19 for a single brief, $99 for a five-brief pack, with a $199 ten-brief bundle added after day 20 if the pack converts.

First revenue offer: Send me one real thread you've given up on. I'll send back the full revival brief and follow-up draft free, within an hour. If it's useful, $99 gets you five more.

Expected ACV: $99

Upsell path: Free brief converts to a $99 Revival Pack; pack buyers are offered a $199 ten-brief bundle from day 20 and repeat pack purchases as their pipeline refills. No subscription is introduced before validation.

Target customers
60
Revenue model
$5,940
Costs
$240
Profit model
$5,700
Section 4 of 8

First-customer acquisition

Primary channel

Direct X and LinkedIn DMs to agency owners publicly posting about stalled proposals or being ghosted.

Where to find them

  • X search: "proposal went cold", "client ghosted", "followed up twice" filtered to founder bios with agency keywords
  • LinkedIn posts by owners of 2-20 person creative, design, dev and branding agencies mentioning lost deals
  • Indie Hackers and r/agency threads about proposal follow-up
  • Founder's own network of agency owners met at meetups or in Slack communities
  • Reply threads under build-in-public posts about agency sales pipelines

Exact outreach motions

  • Send a free brief offer referencing their specific post, no pitch in the first line
  • Deliver the free brief within 60 minutes, manually reviewed before sending
  • Ask one question: did this get you closer to a reply?
  • Offer the $99 Revival Pack only after the free brief lands
  • Follow up once at 48 hours with a second free brief on another thread, then stop

Message template

Saw your post about the proposal going quiet. I built a small tool that turns a dead thread into a one-page revival brief plus a follow-up draft. Send me one thread you've given up on and I'll run it free and send the brief back within an hour. No signup, nothing to install.
Week-one goal: 60 DMs sent, 8 threads received, 5 free briefs delivered, and at least 1 paid Revival Pack ($99) collected 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 1Foundation

Scaffold and intake

  • Create Vercel and Supabase projects with threads, briefs and buyers tables.
  • Ship the paste intake form and store raw thread text.

Deliverable: Deployed intake page that persists a thread.

Day 2Extraction

Structured LLM extraction

  • Write the extraction prompt with a strict JSON schema.
  • Add a quote-provenance validator that rejects fields without a verbatim source.
  • Build the HTML brief renderer with five fixed sections.

Deliverable: Thread text in, structured brief JSON and HTML out.

Day 3Delivery

PDF, drafts, Stripe

  • Add react-pdf rendering and three-tone draft generation.
  • Wire Stripe Checkout and the success webhook.
  • Send the brief and drafts by Resend email with the PDF attached.

Deliverable: Paid end-to-end run delivering a brief by email.

Day 4Polish

History and forward alias

  • Add buyer history list keyed by email address.
  • Add the inbound forward-to-brief alias for buyers who prefer email.
  • Add retry handling for failed generation and a manual fallback.

Deliverable: Production-ready MVP with two intake paths.

Day 5HardeningMVP shipped

Dry runs on real threads

  • Run five real threads end to end and log extraction errors.
  • Tighten prompts until deal value and last-contact date are correct on all five.
  • Write the pricing page and the free-brief offer copy.

Deliverable: MVP declared done; quality baseline recorded.

Day 6Proof assets

Before/after teardowns

  • Publish teardown one on X with a redacted thread and the brief.
  • Publish the same teardown on LinkedIn.
  • Build a DM target list of 40 agency owners.

Deliverable: Two public teardowns and a 40-name list.

Day 7Outreach starts

First 20 DMs

  • Send 20 personalised DMs offering a free brief.
  • Log every send and reply in a sheet.
  • Deliver any free brief within 60 minutes of receiving a thread.

Deliverable: 20 DMs out, replies tracked.

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

Second DM wave

  • Send 20 more DMs.
  • Deliver every promised free brief manually reviewed.
  • Publish teardown two.

Deliverable: 40 cumulative DMs, 3+ free briefs delivered.

Day 9First revenueFirst sale target

Close the first pack

  • Ask every free-brief recipient for the $99 Revival Pack.
  • Remove any checkout friction found in the first sessions.
  • Record the first collected payment in TrustMRR.

Deliverable: First paid Revival Pack collected.

Day 10Iterate

Output quality

  • Review every draft the founder had to edit and fix the two worst prompt failures.
  • Add a 'why this stalled' hypothesis line to the brief.
  • Send 20 DMs.

Deliverable: Sharpened brief template, 60 cumulative DMs.

Day 11Loop

Free-brief throughput

  • Send 20 DMs.
  • Deliver 3 free briefs within the hour.
  • Ask each recipient for a one-line quote about the brief.

Deliverable: 3 free briefs, 2 quotes collected.

Day 12Proof

Publish results

  • Publish teardown three using an anonymised real thread and its brief.
  • Send 20 DMs.
  • Follow up once with day 6-7 non-responders.

Deliverable: Third teardown live, follow-up wave sent.

Day 13Packaging

Offer clarity

  • Rewrite the pricing page around five briefs and priority turnaround.
  • Add a sample brief PDF download to the site.
  • Send 20 DMs.

Deliverable: Converted pricing page with public sample.

Day 14Review

Week two audit

  • Compute DM-to-thread and thread-to-paid rates.
  • Kill the worst-performing DM opener and write a replacement.
  • Send 20 DMs with the new opener.

Deliverable: Funnel numbers and a revised opener.

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

Channel widening

  • Send 25 DMs plus 5 replies in agency community threads.
  • Deliver all free briefs within the hour.
  • Ask every buyer which single section of the brief was most useful.

Deliverable: 30 touches, section preference data.

Day 16Referral

Buyer-driven leads

  • Ask each paying buyer for one agency owner who has the same problem.
  • Send 25 DMs.
  • Publish teardown four.

Deliverable: Referral asks sent, teardown four live.

Day 17Loop

Throughput

  • Send 25 DMs.
  • Deliver 4 free briefs.
  • Fix any brief that took longer than 15 minutes to produce manually.

Deliverable: 4 briefs delivered, production time under 15 minutes.

Day 18Objections

Pricing pushback

  • Log every pricing objection verbatim.
  • Test a $99-to-$149 anchor in DM copy with 10 recipients.
  • Send 25 DMs.

Deliverable: Objection list and a price-anchor test running.

Day 19Content

Search-shaped posts

  • Publish a teardown titled around the exact phrase agency owners search.
  • Send 25 DMs.
  • Follow up with day 12 non-responders once.

Deliverable: Search-shaped post live, follow-ups sent.

Day 20Expansion

Ten-brief bundle

  • Add the $199 ten-brief bundle to the pricing page.
  • Offer it to existing pack buyers first.
  • Send 25 DMs.

Deliverable: Bundle live, offer sent to buyers.

Day 21Review

Week three audit

  • Compare Single Brief vs Revival Pack share of revenue.
  • Cut any task that produced zero threads.
  • Send 25 DMs.

Deliverable: Revenue mix report and pruned task list.

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

Forward-to-brief address

  • Promote the forward-to-brief email address as the zero-friction path.
  • Add an instant confirmation email with expected delivery time.
  • Send 25 DMs.

Deliverable: Forward path promoted, confirmation live.

Day 23Proof

Reply data

  • Ask all past buyers whether any prospect replied, and log yes/no.
  • Publish an aggregate reply-rate post with no invented numbers.
  • Send 25 DMs.

Deliverable: Reply data table and an honest aggregate post.

Day 24Loop

Throughput

  • Send 30 DMs.
  • Deliver 5 free briefs.
  • Templatise the founder's manual review checklist.

Deliverable: 30 touches, review checklist documented.

Day 25Conversion

Checkout cleanup

  • A/B the checkout button copy between two variants.
  • Add a one-line refund promise on the pricing page.
  • Send 30 DMs.

Deliverable: Checkout test live, refund promise published.

Day 26Reactivation

Dormant leads

  • Re-DM every person who received a free brief but did not buy.
  • Offer a $19 single brief as the low-friction entry.
  • Send 30 new DMs.

Deliverable: Reactivation wave sent.

Day 27Content

Final public teardown

  • Publish teardown five with the strongest real example.
  • Send 30 DMs.
  • Pin the best-performing post on X.

Deliverable: Teardown five live and pinned.

Day 28Close

Last conversion push

  • Offer the pack to every warm contact with a 48-hour expiry.
  • Send 30 DMs.
  • Check Stripe payouts and refunds match records.

Deliverable: Final conversion wave, payments reconciled.

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

Buyer experience

  • Deliver any outstanding briefs within the hour.
  • Answer every open question with a template reply.
  • Fix the single most-reported output complaint.

Deliverable: Zero outstanding deliveries, one fix shipped.

Day 30Settle

Accounting and decision

  • Reconcile gross revenue, refunds, fees and ad spend in TrustMRR.
  • Write a one-page post-mortem on what converted.
  • Decide the day-31 offer based on the pack-vs-single revenue mix.

Deliverable: Verified profit figure and a written go-forward decision.

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

  • Base case: 10 Revival Packs at $99 within 30 days (Base).
  • Conservative: 3 paid briefs or packs total, blended at $99 (Conservative).
  • Upside: 25 sales at $99 average, including some $199 bundle purchases (Upside).
  • Payment processing assumed at Stripe 2.9% + $0.30, modelled as ~4% blended on collected revenue.
  • No paid marketing in Conservative or Base; $150 of sponsored posts or paid promotion only in Upside.
  • Refunds modelled at 0 in Conservative and Base because delivery is fast and manual; ~2% of revenue in Upside.
  • Chargebacks modelled at 0 in all scenarios; delivery evidence is retained in Supabase.
  • Operating cost covers Vercel, Supabase, Resend and OpenAI delivery at roughly $0.10-$0.50 per brief plus fixed tooling.
  • DM outreach is organic and costs $0 in ad spend by definition.

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
$50
Chargebacks
$0
Payment fees
$97
Paid marketing
$150
Hackathon profit
$2,178
Operating costs
$90
Business profit
$2,088

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$190
Payment fees (3.9%)
$7
Paid marketing
$0
Hackathon profit
$183
Business profit
$138

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. All figures are projections with no existing customers, traction or partnerships implied.

Section 7 of 8

Main risks and validation experiments

Risk 1DM outreach is ignored or flagged as spam, producing zero threads.

Mitigation

Personalise the first line to the specific post, cap at 30 DMs per day, and always lead with a free brief rather than a pitch.

Validation experiment

Send 30 DMs over 3 days and measure threads received, not revenue.

Kill criteria

Fewer than 3 threads received from 90 DMs means the channel is wrong and the plan must move to community threads and direct email.

Risk 2Buyers expect inbox automation and treat the paste step as a dealbreaker.

Mitigation

Make the free brief the proof, add the forward-to-brief alias so no form is needed, and price at $19 so the test is cheap.

Validation experiment

Count how many free-brief recipients ask for Gmail connection versus ask for a second brief.

Kill criteria

If OAuth requests outnumber second-brief requests 2:1 across 10 deliveries, the wedge is wrong and the concept must be re-scoped or abandoned.

Risk 3LLM drafts feel generic and the buyer does not send them.

Mitigation

Force every draft to reference a specific detail and date from the thread, and manually review the first 10 free briefs before sending.

Validation experiment

Track the edit rate — how much of each draft the founder or buyer rewrites before sending.

Kill criteria

If more than 60% of draft text is rewritten across 10 briefs, the generation logic needs rebuilding before any more outreach.

Risk 4Volume stays far below $100k and the entry is not competitive in absolute revenue terms.

Mitigation

Optimise verified profit rather than revenue: near-zero ad spend, sub-$0.50 delivery cost, no support promises.

Validation experiment

Compare profit per DM against revenue per DM each week.

Kill criteria

If paid conversion stays under 1% of free briefs delivered after 20 deliveries, move to pre-paid packs sold before delivery.

Risk 5Stripe review or payout holds delay the first collectable payment.

Mitigation

Create the Stripe account on day 1 with accurate business details, and keep the first offers small so review risk is low.

Validation experiment

Process a $1 test charge and a $19 live charge on day 4.

Kill criteria

If payments are still unavailable on day 7, switch to an alternate processor before any outreach spend.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Buy the domain and point it at Vercel.
  • Create Supabase, Stripe and Resend accounts and store keys in Vercel env vars.

Output: Live project skeleton with all accounts open.

Hours 3-5

  • Create the threads, briefs and buyers tables.
  • Ship the paste intake form on a public URL.

Output: Working intake page that stores a thread.

Hours 6-9

  • Write the extraction prompt and strict JSON schema.
  • Build the quote-provenance validator that rejects unsupported fields.

Output: Extraction pipeline returning validated structured fields.

Hours 10-13

  • Build the five-section brief renderer.
  • Add PDF output via react-pdf.

Output: A complete brief as HTML and PDF from one pasted thread.

Hours 14-17

  • Wire Stripe Checkout and the success webhook.
  • Send the brief and three drafts by Resend with the PDF attached.

Output: Paid end-to-end delivery path.

Hours 18-20

  • Run three founder-supplied threads through the full pipeline.
  • Fix the two worst output failures.

Output: Quality baseline on three real threads.

Hours 21-24

  • Build a 40-name DM target list from X and LinkedIn search.
  • Send the first 10 personalised DMs offering a free brief.

Output: 10 DMs out, 40-name pipeline loaded.

Complete report

Full 30-day launch report

Read the full generated report

Ghostthread Invoice — 30-Day Public Report

1. Product opportunity and positioning

Ghostthread Invoice is a paid artifact, not a dashboard. A solo agency owner pastes or forwards one cold email thread and, within minutes, receives a one-page deal revival brief plus a short follow-up email in three tones. That is the whole product.

The positioning is deliberately narrow: not an inbox assistant, not a CRM, not a sales-engagement suite. It competes against the owner's avoidance behaviour. Re-reading an eight-month-old thread, remembering what was promised, and writing a nudge that does not sound needy takes 30-60 minutes of emotional labour. Owners skip it, and the proposal dies of inaction rather than rejection. Ghostthread charges $19 to make that task take four minutes.

The economics favour the buyer immediately: the deal on the thread is $5k-$50k, so any reply at all has an asymmetric payoff versus $19. No OAuth, no inbox permission, no migration, no team rollout — which is why JEV scored speed_to_first_revenue at 9.26 and solo_build_feasibility at 7.89. This plan spends that advantage instead of a marketing budget.

The two weaknesses JEV flagged are handled honestly. Monetization potential scored 4.63: a $19 one-off is small, so the $99 Revival Pack of five is the default offer in every conversation and a $199 ten-brief bundle is tested from day 20. Competitive defensibility scored 5.14: the moat is the brief format, delivery speed, and the published library of before/after examples.

No customers, revenue, partnerships or market statistics are claimed anywhere in this document.

2. Smallest sellable MVP

One form, one output, one payment link. Six features ship: paste-or-forward intake, LLM extraction of deal value, last-contact date, stakeholders and stated objections, a one-page HTML-to-PDF brief, a three-tone follow-up generator, Stripe Checkout with instant email delivery, and a buyer history list.

Explicitly not built: Gmail or Outlook OAuth, LinkedIn or news scraping, CRM sync, team seats, admin console, automated sending, subscriptions.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres, OpenAI for extraction and drafting, Stripe Checkout, Resend, react-pdf. The Stripe webhook creates a brief record and triggers generation: extract structured fields, validate each field against a verbatim quote from the thread, render HTML and PDF, generate three drafts, email everything. A forwarded-thread alias maps inbound mail to a buyer by sender address.

The hardest risk is a confident misread — wrong deal value, wrong date, invented commitment — producing a brief that embarrasses the buyer. Mitigation: every extracted field is shown with its source quote and the buyer can correct it before regeneration.

4. Pricing and monetization

$19 Single Brief; $99 Revival Pack of five with priority turnaround. Both one-time. The pack is pushed in every DM because it turns a $19 decision into a $99 decision and gives the buyer five chances to see value. Processing is modelled at roughly 4% blended (Stripe 2.9% + $0.30). Delivery cost per brief is cents, so operating cost stays between $25 and $90 across all scenarios.

5. First-customer acquisition

One channel: direct DMs on X and LinkedIn to agency owners who publicly post about stalled proposals or being ghosted. Search phrases: "proposal went cold", "client ghosted", "followed up twice nothing". The sequence is always free brief first, delivered by a human within an hour, then the $99 ask. Week-one goal: 60 DMs, 8 threads received, 5 free briefs delivered, 1 paid pack by day 9.

6. 30-day execution roadmap

Days 1-4 build; day 5 is dry-run hardening on five real threads. Days 6-8 publish three redacted teardowns and build the DM list. Day 9 is the first-sale target. Days 10-21 run a daily loop of 20-25 DMs, free briefs delivered within the hour, one teardown every second day, and a weekly funnel audit. Days 22-28 add the forward-to-brief alias promotion, the $199 bundle, and reactivation of every non-buyer who received a free brief. Days 29-30 settle: deliver outstanding briefs, reconcile Stripe and TrustMRR, write the post-mortem.

7. Revenue and profit scenarios

Three projections, no claim of verified revenue. Conservative: 3 sales at $99 = $297, no ad spend. Base: 10 sales at $99 = $990, no ad spend. Upside: 25 sales at $99 average = $2,475, with $150 of paid promotion and $50 refunds. Processing fees sit near 4% of collected revenue. Hackathon profit is gross revenue minus refunds, chargebacks, processing fees and ad spend; business profit additionally subtracts the $25-$90 of hosting and AI delivery cost.

8. Main risks and validation experiments

DM replies may be near zero: test with 30 DMs measured by threads received, and abandon the channel below 3 threads per 90 DMs. Buyers may demand inbox automation: count Gmail-connection requests against second-brief requests across 10 deliveries. Drafts may read generic: track the edit rate and rebuild generation if more than 60% of draft text is rewritten. Volume may stay far below $100k: optimise profit per DM, not revenue. Stripe review may hold funds: run a live $19 charge on day 4 and switch processors if payments are still blocked on day 7.

9. First 24-hour action plan

Hours 1-2: domain, Vercel, Supabase, Stripe and Resend accounts. Hours 3-5: schema and public intake form. Hours 6-9: extraction prompt plus quote-provenance validator. Hours 10-13: five-section renderer and PDF. Hours 14-17: Stripe Checkout, webhook, Resend delivery. Hours 18-20: run three real threads end to end and fix the worst failures. Hours 21-24: build a 40-name DM list and send the first 10 free-brief offers.

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 →