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

Support SOP Forge

Support SOP Forge turns an export of your support conversations into a ready-to-use playbook of step-by-step SOPs for your top 20 recurring issues, complete with real customer phrasing and escalation rules.

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.31/10
MVP build (solo)
5 days
Launch price
$0
Sales to $1,000 revenue
not meaningful at this price
First paying customer
Direct outreach in support-leader communities to team leads who have publicly posted about hiring or onboarding support agents in the last 30 days.
Who pays

Support Team Lead or Head of CX at a 10-50 person e-commerce brand or SaaS company running Zendesk, Intercom, Gorgias or Freshdesk, who has just hired 2+ new agents (or is about to) and needs them productive within weeks. US, UK, Canada, Australia.

Biggest execution risk

Monetization potential 4.7/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 12; 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

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

0/15
Entry price
$0
Solo build
5 days
30d base revenue
$990
30d hackathon profit
$958
Section 1 of 8

Product opportunity and positioning

Target customer

Support Team Lead or Head of CX at a 10-50 person e-commerce brand or SaaS company running Zendesk, Intercom, Gorgias or Freshdesk, who has just hired 2+ new agents (or is about to) and needs them productive within weeks. US, UK, Canada, Australia.

Why now

LLM clustering makes the synthesis step cost $2-4 per playbook, so a $99 one-time price clears delivery cost, and CSV exports remove OAuth, integration review and cold-start data problems.

Problem

SOPs are tedious to write, so they get skipped or go stale; new agents ask senior agents the same 20 questions and resolution quality varies by who answers.

Solution

Upload a CSV of 200-2,000 tickets; the product clusters them by underlying issue, picks the top 20 by volume, drafts one SOP per cluster (definition, trigger phrases, resolution steps, escalation rule, macro) and delivers a branded PDF plus per-SOP markdown and macro blocks.

Differentiation · Not a dashboard, not a trend tracker, and not a PRD tool for product managers: it ships a finished artifact the team lead can hand to a new agent the same day, written in the customer's own words.

1. Product opportunity and positioning

Support SOP Forge takes a file the buyer already has written and makes it into a file they can hand to a new hire. The buyer is the Support Team Lead or Head of CX at a 10-50 person e-commerce brand or SaaS company on Zendesk, Intercom, Gorgias or Freshdesk who has just hired two or more agents. The painful moment is concrete and dated: a new hire starts Monday, twenty recurring issues exist, and nobody has written them down. The lead knows a playbook would fix the interruptions and the variance in resolution quality, but never finds a clean block of time to write one from scratch.

What is actually being sold

An artifact, not analytics. The lead uploads a CSV export of 200-2,000 recent tickets or chat transcripts. The product clusters tickets by underlying issue, ranks clusters by volume, and drafts one SOP per cluster: issue definition, the trigger phrases customers actually use, step-by-step resolution path, escalation rule, and a copy-paste macro. Output is a branded PDF playbook plus per-SOP markdown and macro blocks that paste straight into the help desk. There is no integration to approve, no data pipeline to maintain, and no dashboard to check.

Why this wedge rather than the original framing

The original category (mining support conversations for themes) produced insight for product and operations teams. Insight is a vitamin: someone still has to translate it into work. This concept keeps the raw material and the buyer universe but changes the deliverable to something the buyer is already obligated to produce. The trigger event is a hire, not a strategy review, and the proof of value is a document that exists at the end of the week.

Positioning against the alternatives

The realistic alternatives are: the team lead writes SOPs manually (a week they do not have), copies stale templates that do not match their products, or uses a help desk's built-in AI features that summarise tickets but do not produce a playbook. Support SOP Forge competes on specificity: the trigger phrases come from the buyer's own tickets, so a new agent recognises the language.

Honest read on the score

JEV scored this concept 63.1/100, band C, confidence 0.73. The strongest criterion is speed to first revenue (8.43 normalized): a CSV in, a payment link out, no procurement. The weakest is monetization potential (4.68), flagged as a single low-value one-time charge. This plan answers that weakness with a second, cheaper transaction: a $49 Playbook Refresh against a new export, tested inside the 30-day window rather than assumed. Competitive defensibility is thin (5.56); the moat is the artifact and the buyer-specific wording, not the model. Market demand (5.34) is unvalidated and is the first thing the outreach plan tries to falsify.

Section 2 of 8

Smallest sellable MVP

CSV upload plus a top-20 clustered SOP playbook rendered as a branded PDF and markdown, gated behind a $99 Stripe checkout, with a free watermarked 3-SOP preview generated from the same export.

Must-have features

  • CSV upload with column mapping presets for Zendesk, Intercom, Gorgias and Freshdesk exports
  • LLM clustering pass grouping tickets by underlying issue, ranked by ticket volume
  • Top-20 cluster selection with visible ticket counts
  • Per-cluster SOP generator using a fixed template (definition, trigger phrases, resolution steps, escalation rule, macro)
  • Editable SOP card UI so the lead can fix a step before export
  • Watermarked 3-SOP preview to demonstrate quality
  • Stripe Checkout gating the full export until payment clears
  • PDF playbook assembler plus per-SOP markdown/macro download
  • Async job queue with progress email so no browser tab has to stay open

Explicitly out of scope

  • No live help desk integration or OAuth sync; CSV upload only
  • No ongoing dashboard, trend tracking or sentiment analytics
  • No agent-facing copilot or ticket-writing assistant
  • No multi-user seats, roles or SSO
  • No support chat, onboarding calls or 24/7 SLA
  • No languages other than English
  • No PRD generation or Linear/Jira export

Demo flow (what the buyer sees)

  1. Lead uploads a 500-ticket CSV export
  2. Maps columns via a preset for their help desk
  3. Job runs clustering, shows progress, emails on completion
  4. Product shows top 20 clusters ranked by volume with sample phrases
  5. Lead sees 3 SOPs free with a watermark on the PDF
  6. Lead pays $99 via Stripe Checkout
  7. Full PDF playbook and per-SOP markdown/macros unlock immediately
  8. Lead edits one SOP card and re-exports without re-running clustering
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres + storage for CSVs and PDFsOpenAI or Anthropic API for clustering and SOP draftingReact-PDF for playbook renderingStripe Checkout + webhooksResend for transactional emailUpstash QStash or a Supabase cron worker for the async job queue

Architecture

A single Next.js app on Vercel serves the upload UI and the results UI. Uploads land in Supabase storage and are parsed into a normalized tickets table (id, body, channel, created_at). A background worker pulls a job, batches ticket bodies to the LLM for issue clustering, stores clusters and membership counts, then generates one SOP per top-20 cluster into a sop table. The results page reads from those tables, lets the lead edit SOP fields, and triggers a React-PDF render stored back in Supabase. Stripe webhook flips an order row to paid, which unlocks the full render and the markdown download; unpaid sessions get the watermarked 3-SOP version only.

Build steps

  1. Scaffold Next.js + Supabase, deploy an empty shell to Vercel, add env vars
  2. Build CSV upload, column mapping presets for the four help desks, and ticket normalization
  3. Implement the clustering job: batch tickets, assign issue labels, merge near-duplicates, rank by volume
  4. Implement the SOP generator with a strict JSON template and validation on required fields
  5. Build the editable SOP card UI with save and re-render
  6. Add React-PDF playbook render and per-SOP markdown/macro export
  7. Add Stripe Checkout, webhook, order table and paywall logic with watermarked preview
  8. Add the async queue plus Resend progress and delivery emails
  9. Load-test with a 2,000-row export and cap token spend per job
  10. Add error paths: unparseable CSV, empty clusters, LLM timeout, re-run button

AI components

  • Issue clustering over batched ticket bodies
  • Cluster label and near-duplicate merge pass
  • SOP drafting (definition, steps, escalation rule) as structured JSON
  • Trigger-phrase extraction quoting real customer wording
  • Macro text generation constrained to the help desk's variable syntax
Hardest technical risk: Clustering quality on messy real exports: duplicate tickets, multi-issue tickets and mixed languages can produce 40 thin clusters or one giant bucket, which makes the playbook look generic and kills trust at the exact moment the lead decides to pay.
Section 3 of 8

Pricing and monetization

Sample

Entry offer
$0 one-time

For Team lead evaluating output quality

  • 3 SOPs generated from their own ticket export
  • Watermarked PDF preview

Full Playbook

$99 one-time

For Support team lead onboarding new agents

  • Top 20 SOPs from their tickets
  • Branded PDF playbook
  • Per-SOP markdown and macro blocks
  • One regeneration within 30 days of editing inputs

Playbook Refresh

$49 one-time

For Existing buyer with a fresh export 60+ days later

  • Re-clustered top 20 SOPs from a new export
  • Diff summary versus the previous playbook

Model: One-time $99 per playbook, with a free 3-SOP sample as the quality proof and a $49 refresh as the repeat purchase.

First revenue offer: Send me a CSV of 200 recent tickets; within 24 hours I'll send back 3 SOPs written from your own tickets, free, no call. If they are useful, the full top-20 playbook is $99 and takes you about ten minutes to request.

Expected ACV: $99

Upsell path: Every buyer is asked for a second export after 60 days at $49 with a diff summary; in the window, the refresh offer is pitched on day 25 to buyers whose export was older than two months.

Target customers
10
Revenue model
$990
Costs
$60
Profit model
$930
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach in support-leader communities to team leads who have publicly posted about hiring or onboarding support agents in the last 30 days.

Where to find them

  • Support Driven Slack channels (#hiring, #onboarding, #cx-leadership)
  • LinkedIn posts from Heads of CX and Support Managers announcing agent hires
  • r/CustomerSuccess and r/ecommerce threads about onboarding new agents
  • Gorgias and Zendesk community forums questions about macros and SOPs
  • Job boards: companies posting 2+ support agent roles in the last 30 days, then find the hiring manager on LinkedIn
  • Small e-commerce brand Slack groups and agency-run CX cohorts

Exact outreach motions

  • Send a 4-line DM to team leads who posted about hiring: offer 3 free SOPs from their own CSV, 24-hour turnaround, no call.
  • Comment publicly on the hiring post with one useful line, then DM the offer so the message is not cold.
  • Email the hiring manager at companies with 2+ open support roles, subject line naming their open role.
  • Post a redacted before/after SOP pair in Support Driven with a one-line offer to build one from a CSV.
  • Follow up once after 72 hours with the sample attached and a single-line note about the $99 full playbook.

Message template

Saw you're hiring support agents. If you export 200 recent tickets to CSV, I'll send back 3 SOPs written from your own tickets within 24 hours, free. No call, nothing to install. Want me to run it?
Week-one goal: 25 outreach messages sent to verified team leads who posted about agent hiring, with 3 free 3-SOP samples delivered.
Section 5 of 8

30-day execution roadmap

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

Deployable shell

  • Scaffold Next.js app with Supabase and Stripe test keys.
  • Create tickets, clusters, sops and orders tables.
  • Deploy empty shell to Vercel and confirm env vars.

Deliverable: Live URL with a working health check and schema migrated.

Day 2Ingest

CSV to normalized tickets

  • Build upload UI and Supabase storage write.
  • Add column mapping presets for Zendesk, Intercom, Gorgias, Freshdesk.
  • Normalize rows into the tickets table and show a parsed count.

Deliverable: A 500-row export parses into the tickets table in under 30 seconds.

Day 3Clustering

Issue groups ranked by volume

  • Batch ticket bodies to the LLM and assign issue labels.
  • Merge near-duplicate clusters and rank by ticket count.
  • Persist clusters and membership for the results page.

Deliverable: Top-20 cluster list with counts rendered for a real export.

Day 4SOP generation

Template-validated SOP drafts

  • Write the SOP prompt with a strict JSON contract.
  • Validate required fields and retry on malformed output.
  • Build editable SOP card UI with save.

Deliverable: 20 editable SOPs persisted and viewable in the app.

Day 5PaywallMVP shipped

PDF, preview and $99 checkout

  • Render a branded PDF of all 20 SOPs.
  • Add a watermarked 3-SOP preview for unpaid sessions.
  • Wire Stripe Checkout and the webhook to unlock full export.

Deliverable: MVP live: CSV in, paid PDF and markdown out. Deadline day.

Day 6Reliability

Async jobs and email

  • Move clustering and rendering to a background worker.
  • Send progress and delivery emails via Resend.
  • Add an error state and a re-run button.

Deliverable: A 2,000-row export completes without an open browser tab.

Day 7Quality pass

Prompt and template fixes

  • Run two unrelated exports end to end.
  • Rewrite prompts where SOP steps read generic.
  • Cap token spend per job and log cost.

Deliverable: Two playbooks the founder would personally hand to an agent.

Week 2 · Launch & first sale · 7 days
Day 8List building

100 qualified leads

  • Search LinkedIn for agent-hiring posts in the last 30 days.
  • Collect name, company, help desk and post link into a sheet.
  • Tag leads by help desk to test mapping quality.

Deliverable: 100-row outreach sheet with contact routes.

Day 9Outreach prep

Messages and sample workflow

  • Finalize the 4-line DM and the email variant.
  • Build an internal path to produce a 3-SOP sample fast.
  • Define the $99 Stripe payment link and refund policy page.

Deliverable: Send-ready messages, sample workflow and live payment link.

Day 10First contact

25 messages out

  • Send 25 DMs to leads who posted about hiring.
  • Post one useful comment on three public hiring posts.
  • Log send times for the 72-hour follow-up.

Deliverable: 25 messages sent, reply tracking live.

Day 11Sample delivery

Prove quality

  • Reply to every response within 6 hours.
  • Run first free samples through the pipeline manually.
  • Send each sample with one line on what to check.

Deliverable: First 3 free 3-SOP samples delivered.

Day 12First revenueFirst sale target

Convert samples to $99

  • Send the $99 link to every sample recipient.
  • Follow up on day-3 non-responders with the sample attached.
  • Remove friction: offer to take payment before export if asked.

Deliverable: First paid playbook. Target day.

Day 13Visibility

Public proof

  • Post a redacted before/after SOP pair in Support Driven.
  • Send 25 more DMs using the same template.
  • Record reply rate by source.

Deliverable: One public post live and 50 total messages sent.

Day 14Review

Reply-rate reality check

  • Tabulate replies, samples and paid conversions.
  • Fix the single most common objection in the message.
  • Send 25 more messages with the revised copy.

Deliverable: Week-2 funnel numbers with a revised message.

Week 3 · Repeat & systematize · 7 days
Day 15Quality loop

Clustering controls

  • Add manual cluster merge and split for the lead.
  • Re-rank clusters after a merge without a full re-run.
  • Re-issue one sample that had weak clusters.

Deliverable: Cluster merge/split shipped and one sample re-delivered.

Day 16Trust

Terms, refunds, payments

  • Publish terms, refund policy and a delivery-time statement.
  • Confirm Stripe account is connected to TrustMRR from day one.
  • Reconcile payout timing against the contest window.

Deliverable: Public policy pages and verified payment routing.

Day 17Price signal

Test $99 vs $79

  • Offer $79 to ten new leads and $99 to ten others.
  • Track acceptance, not just replies.
  • Keep the price that converts without a discount argument.

Deliverable: Price decision documented with counts.

Day 18Repeat path

$49 refresh

  • Build a refresh checkout that accepts a new export.
  • Generate a diff summary of changed SOPs.
  • Draft the refresh email for existing buyers.

Deliverable: Refresh product purchasable end to end.

Day 19Landing page

Public proof page

  • Publish a page with a redacted sample playbook.
  • Add the free-sample offer as the only CTA.
  • Link it in every community profile.

Deliverable: Public landing page with sample and one CTA.

Day 20Volume

Pipeline breadth

  • Send 25 more DMs to a fresh lead list.
  • Ask each buyer for a one-line quote with no logo use.
  • Log which help desk converts best.

Deliverable: 75 total messages sent, first quotes collected.

Day 21Decision point

Channel keep or kill

  • Compare reply rate against a 10% threshold.
  • Decide whether to keep, adjust or add a channel.
  • Document the decision and the evidence.

Deliverable: Written channel decision with funnel data.

Week 4 · Scale what works · 7 days
Day 22Second channel test

Reddit and LinkedIn comments

  • Post 20 helpful comments in r/CustomerSuccess and r/ecommerce.
  • DM only those who engage, with the sample offer.
  • Track replies separately from the Slack channel.

Deliverable: Second channel data set with 20 touches.

Day 23Unit economics

Cost per playbook

  • Measure LLM and render cost for three real playbooks.
  • Add caching for repeated clustering inputs.
  • Set a hard token cap per job.

Deliverable: Documented cost per playbook under $4.

Day 24Momentum

Second push

  • Send 25 DMs including the price test winner.
  • Offer a same-day turnaround slot to create urgency.
  • Re-open every unanswered thread once.

Deliverable: 100 total messages sent, 5+ samples delivered.

Day 25Expansion

Refresh offers

  • Email all buyers the $49 refresh with the diff example.
  • Target buyers whose export was older than 60 days.
  • Log refresh intent for month two.

Deliverable: Refresh offer sent to every existing buyer.

Day 26Lead magnet

Free SOP template post

  • Publish a generic SOP template as markdown in two communities.
  • Add one line pointing to the free sample offer.
  • Track inbound DMs from the post.

Deliverable: Template posted, inbound tracked.

Day 27Final push

Close the window

  • Send a deadline-framed DM to warm leads only.
  • Offer to run the export while they are on the call-free flow.
  • Prioritize leads with new hires starting this month.

Deliverable: All warm leads contacted with a dated close.

Day 28Delivery

Clear the queue

  • Deliver every outstanding playbook.
  • Review each PDF for broken macros or missing fields.
  • Confirm buyer receipt and ask for one-line feedback.

Deliverable: Zero outstanding deliverables.

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

Verified numbers

  • Reconcile Stripe gross, refunds, disputes and fees.
  • Confirm every transaction is recorded in TrustMRR.
  • Compute hackathon profit and business profit separately.

Deliverable: Reconciled ledger matching the contest definition.

Day 30Wrap and next month

What continues

  • Publish a short honest results post with no invented traction.
  • Decide month-two plan: refresh cadence, price, channel mix.
  • Set one metric to beat next month: sample-to-paid rate.

Deliverable: Results summary and month-two one-pager.

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: 10 team leads from roughly 100 direct outreach messages pay $99 within 30 days; projection, not validated traction.
  • Conservative: reply rates run well below plan and only 3 of 100 messages convert.
  • Upside: warm-list conversion plus a small paid sponsorship and refresh purchases yield 25 paid playbooks.
  • Payment fees assume Stripe at 2.9% + $0.30 per transaction (about 3.2% blended at a $99 price).
  • Operating costs cover Vercel, Supabase, Resend, the domain, and $2-4 of LLM plus rendering per playbook actually delivered.
  • Ad spend is zero in Conservative and Base because outreach is organic; Upside includes $150 for one paid community sponsorship.
  • Refunds are zero in Conservative and Base; Upside assumes one full $99 refund.
  • No chargebacks assumed in any scenario; a single chargeback would materially dent profit at this volume.
  • Refresh purchases at $49 are treated as upside only and are not required for the Base case.
  • All figures are projections built from these assumptions and are not verified revenue.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$10
Paid marketing
$0
Hackathon profit
$287
Operating costs
$25
Business profit
$262

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$32
Paid marketing
$0
Hackathon profit
$958
Operating costs
$45
Business profit
$913

Optimistic

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

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$490
Payment fees (3.9%)
$19
Paid marketing
$0
Hackathon profit
$471
Business profit
$426

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 derived from the stated assumptions, not verified revenue, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Outreach reply rates collapse below the 10% assumption, leaving revenue far under target.

Mitigation

Send in batches of 25 and rewrite the message every 25 sends based on the actual objection; keep the ask to a free sample with no call.

Validation experiment

Send 25 messages to team leads who posted about agent hiring in the last 30 days; count replies within 72 hours.

Kill criteria

Fewer than 3 replies from 50 messages, or zero sample requests, means the channel or the offer is wrong; switch to the help desk community forums before touching price.

Risk 2Clustering merges distinct issues or splits one issue into many, producing a playbook the lead does not trust.

Mitigation

Ship manual cluster merge and split, show ticket counts next to every cluster, and re-rank without a full re-run.

Validation experiment

Run three real exports from different help desks and have each lead mark how many of the top 20 clusters they would keep unchanged.

Kill criteria

Fewer than 12 of 20 clusters accepted unchanged across two different exports means the output needs a human rewrite and the $99 price is not defensible.

Risk 3CSV exports vary by help desk and break column mapping, creating manual founder work per customer.

Mitigation

Preset mappings for the four supported help desks, a manual mapping fallback, and a hard rejection message with an example header row.

Validation experiment

Collect exports from two Gorgias and two Zendesk users and time the mapping step for each.

Kill criteria

If more than 20 minutes of manual work is required per export, reduce to one help desk and re-scope the claim.

Risk 4The lead treats a playbook as a nice-to-have and defers the $99 past the 30-day window.

Mitigation

Anchor every message to the new hire's start date and offer same-day turnaround; the artifact only matters this week.

Validation experiment

Ask every sample recipient for their next agent start date and compare conversion for those hiring within 30 days versus not.

Kill criteria

If buyers with a start date inside 30 days still do not convert, the trigger is wrong and the buyer definition needs to narrow to e-commerce brands on Gorgias.

Risk 5Free-sample delivery consumes founder time and caps how many prospects can be served.

Mitigation

Samples run through the same pipeline rather than by hand, and the 3-SOP preview is generated automatically on upload.

Validation experiment

Time the delivery of 5 samples end to end and record minutes per sample.

Kill criteria

More than 30 minutes per sample means the sample must become fully self-serve or the volume plan is not executable solo.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Reserve the domain and create the repo.
  • Provision Supabase, Vercel and Stripe test keys.
  • Write the tickets, clusters, sops and orders schema.

Output: Deployed skeleton with schema migrated and env vars set.

Hours 3-6

  • Build the CSV upload UI and storage write.
  • Add the four help desk column mapping presets.
  • Normalize rows into the tickets table and display a parsed count.

Output: A real 500-row export parses correctly in the app.

Hours 7-10

  • Implement the clustering call with batching and label merging.
  • Rank clusters by volume and render the top-20 list.
  • Log token usage per run.

Output: Top-20 cluster view working on the same real export.

Hours 11-14

  • Write the SOP JSON prompt and validation.
  • Render the editable SOP cards.
  • Generate and inspect five SOPs for quality.

Output: Five SOPs that quote real customer phrasing from the export.

Hours 15-18

  • Draft the outreach message and the sample offer.
  • Build a 30-lead list from LinkedIn hiring posts.
  • Set up the payment link and refund policy page.

Output: 30-row lead sheet, message template and live Stripe link ready for day 2.

Complete report

Full 30-day launch report

Read the full generated report

Support SOP Forge — 30-Day Build and Revenue Report

A solo-founder plan for the $100K Hackathon by Ship or Die, running 16 Nov 2026 13:00 UTC to 16 Dec 2026 13:00 UTC. All revenue figures below are projections from stated assumptions, not verified traction.

1. Product opportunity and positioning

Support SOP Forge converts a ticket export into a finished 20-SOP playbook for a support team. The buyer is the Support Team Lead or Head of CX at a 10-50 person e-commerce brand or SaaS company on Zendesk, Intercom, Gorgias or Freshdesk who has just hired two or more agents. The painful moment is dated: a new hire starts Monday, twenty recurring issues exist, and nothing is written down. The lead knows a playbook fixes the interruptions and the inconsistency, but never has a clean block of time to write one.

The product sells an artifact, not analytics. Upload 200-2,000 tickets as CSV, get clusters ranked by volume, get one SOP per top cluster with the trigger phrases customers actually use, resolution steps, an escalation rule and a copy-paste macro. Output is a branded PDF plus markdown and macro blocks. No integration approval, no data pipeline, no dashboard.

JEV scored this concept 63.1/100 (band C, confidence 0.73). Speed to first revenue is the strength at 8.43 normalized. Monetization potential is the weak point at 4.68, flagged as a single low-value one-time charge. The plan addresses that with a $49 refresh against a new export, sold inside the window rather than assumed later. Defensibility is 5.56: the moat is the artifact and the buyer's own wording, not the model.

2. Smallest sellable MVP

The sellable unit is one upload and one PDF. Required: CSV upload with mapping presets for four help desks, an LLM clustering pass, a top-20 ranked cluster list, template-validated SOP drafting, an editable SOP card, a watermarked 3-SOP preview, Stripe Checkout gating the full export, the PDF render plus markdown download, and an async job with an email so nobody holds a browser tab open.

Explicitly excluded: live help desk OAuth, dashboards, trend tracking, sentiment analytics, agent copilot, seats, SSO, support chat, non-English, and any PRD or Linear/Jira export. Every exclusion protects the four-day build.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres and storage, an LLM API for clustering and drafting, React-PDF for the playbook, Stripe Checkout plus webhooks, Resend for email, and a cron or queue worker for jobs.

Flow: upload lands in storage, rows parse into a tickets table, a worker batches ticket bodies for issue labelling, near-duplicates merge, clusters rank by volume, and the top 20 are drafted into a sops table under a strict JSON contract. The results page reads that table and allows edits. A render writes the PDF back to storage. The Stripe webhook flips an order to paid, which unlocks the full render; unpaid sessions see only the watermarked 3 SOPs.

The hardest risk is clustering quality on messy exports: duplicates, multi-issue tickets and mixed languages produce 40 thin clusters or one giant bucket, which makes the playbook look generic at the exact moment payment is decided. Mitigation is manual merge/split plus visible ticket counts per cluster.

4. Pricing and monetization

Free: 3 SOPs from the buyer's own export, watermarked. Full Playbook: $99 one-time, 20 SOPs, PDF, markdown and macros, one regeneration within 30 days after editing inputs. Playbook Refresh: $49 one-time against a new export with a diff summary.

At $2-4 of LLM and rendering cost per playbook, $99 clears delivery cost by a wide margin, which satisfies the no-selling-below-cost rule. Expected ACV is $99; the refresh is the repeat path that answers the JEV monetization flag.

5. First-customer acquisition

One channel: direct outreach to team leads who publicly posted about hiring or onboarding support agents in the last 30 days. Sources are Support Driven Slack, LinkedIn hiring posts, r/CustomerSuccess, e-commerce CX groups, and job boards filtered to companies with two or more open support roles.

The ask is deliberately small: send a CSV of 200 tickets, receive 3 SOPs written from your own tickets in 24 hours, free, no call. Samples are produced through the same pipeline, not by hand, so founder time stays bounded. The paid offer follows only after the sample proves the trigger phrases are real. Week one target: 25 messages to verified leads, 3 samples delivered. First paid playbook targeted at day 12, with a single 72-hour follow-up.

6. 30-day execution roadmap

Days 1-5 build and ship the MVP (scaffold, ingest, clustering, SOP generation, paywall), with the deadline on day 5. Days 6-7 harden reliability and fix prompt quality on two real exports. Days 8-14 run the first outreach cycle: build 100 leads, send 50 messages, deliver samples, aim for the first $99 sale on day 12, publish one public before/after SOP example. Days 15-21 improve clustering controls, publish terms and refund policy, run a $99-versus-$79 price test, build the $49 refresh, and make a documented channel keep-or-kill call. Days 22-28 test a second channel, drive cost per playbook under $4, push to 100 messages, offer refresh to every buyer, post a free SOP template, and clear the delivery queue. Days 29-30 reconcile Stripe against the contest definition, confirm TrustMRR records every transaction, and set month-two metrics.

7. Revenue and profit scenarios

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

Conservative: 3 customers at $99 = $297 gross, no refunds, $10 payment fees, no ad spend, $25 operating costs. Hackathon profit $287; business profit $262.

Base: 10 customers at $99 = $990 gross, no refunds, $32 payment fees, no ad spend, $45 operating costs. Hackathon profit $958; business profit $913.

Upside: 25 customers at $99 = $2,475 gross, one $99 refund, $80 payment fees, $150 ad spend on one sponsorship, $90 operating costs. Hackathon profit $2,146; business profit $2,056.

Hosting, tooling and inference cost are not deducted from hackathon profit. Payment fees assume Stripe at 2.9% + $0.30. A single chargeback would materially dent any of these at this volume.

8. Risks and validation experiments

Outreach reply rate is the top risk. Test: 25 messages, count replies in 72 hours. Kill if fewer than 3 replies from 50 messages.

Clustering accuracy is second. Test: three real exports, have each lead mark how many of the top 20 clusters they would keep unchanged. Kill if fewer than 12 of 20 survive across two exports.

CSV variance is third. Test: time mapping for two Gorgias and two Zendesk exports. Kill if manual work exceeds 20 minutes per export; narrow to one help desk.

Deferred demand is fourth: buyers may treat a playbook as optional. Test whether conversion differs between leads with an agent starting inside 30 days and those without. If the trigger does not predict conversion, narrow the buyer to e-commerce brands on Gorgias.

Sample cost is fifth: time five sample deliveries. If more than 30 minutes each, the sample must go fully self-serve.

9. First 24 hours

Hours 1-2: repo, domain, Supabase, Vercel, Stripe test keys, schema. Hours 3-6: CSV upload and four mapping presets, verified on a real 500-row export. Hours 7-10: clustering, label merging, top-20 ranking with token logging. Hours 11-14: SOP prompt with validation and five inspected drafts. Hours 15-18: outreach message, a 30-lead list from hiring posts, payment link and refund policy page. End state: a working pipeline and a send-ready offer before day two.

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 →