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

BriefToBoard Compiler

Turns a signed client brief into an importable project board, a one-page scope memo, and a missing-inputs checklist for small web-design and branding agencies.

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.86/10
MVP build (solo)
5 days
Launch price
$39
Sales to $1,000 revenue
26 customers
First paying customer
Personalised direct messages on LinkedIn and X to independent web-design and branding agency owners with a publicly visible new-client kickoff or scope-creep post.
Who pays

Owner, founder, or account manager at a 2-15 person web-design or branding agency in the US, UK, Canada, or Australia, with a newly signed client and a kickoff inside 7 days.

Biggest execution risk

Operational simplicity 5.5/10

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

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

0/12
Entry price
$39
Solo build
5 days
30d base revenue
$1,788
30d hackathon profit
$1,733
Section 1 of 8

Product opportunity and positioning

Target customer

Owner, founder, or account manager at a 2-15 person web-design or branding agency in the US, UK, Canada, or Australia, with a newly signed client and a kickoff inside 7 days.

Why now

The trigger is a signature, so budget and a deadline already exist this week, and the output lands in a tool the agency already pays for, so there is no migration decision to stall.

Problem

After signature, the account manager retypes a long brief into tasks and milestones, losing 1-3 hours, starting kickoff against a half-empty board, and leaving out-of-scope work unrecorded so it becomes unbilled revision rounds.

Solution

The buyer pastes or uploads the brief, answers five scope questions, edits the generated tasks inline, then downloads a Client-Ready Project Pack: a CSV mapped to ClickUp, Asana, Trello or Taskade, a one-page scope memo with sign-off line, and a missing-inputs checklist with owners and due dates.

Differentiation · A generic AI chat gives prose, not a board-import schema, a locked phase taxonomy, and a client-facing scope memo with an out-of-scope list and sign-off block that protects the agency's margin.

1. Product opportunity and positioning

The buying moment is a signature, not a search query. An agency owner signs a client, books a kickoff for next week, and then sits down to convert a long prose brief into tasks, phases, due dates and dependencies inside ClickUp, Asana, Trello or Taskade. That conversion eats one to three hours, produces a board that is half-empty at kickoff, and — more expensively — leaves no written record of what the agency assumed or excluded. The revision round that follows is unbilled.

Every existing option is wrong for this moment. The board tool itself has no brief parser. A general AI chat produces a plausible-looking list but no import file, no consistent phase structure, and no client-facing scope artefact. Agencies do not want another workspace: they have already standardised on one, and asking a 6-person studio to migrate during a live project is a non-starter.

BriefToBoard Compiler is positioned as a compile step, not a platform. Input: the brief, plus five scope questions. Output: a portable Client-Ready Project Pack — a CSV mapped to the buyer's chosen board schema, a one-page scope memo listing in-scope work, assumptions, revision allowance and out-of-scope items with a sign-off line, and a missing-inputs checklist naming each absent asset, its owner and a due date. Nothing is stored in a new workspace, nothing is migrated, and there is no per-seat charge.

The narrow wedge is deliberate. This is not project management, not collaboration, not invoicing, not time tracking. It serves one job for one buyer type and then disappears until the next signature. That narrowness is what makes a 5-day solo build credible: the taxonomy is locked to eight web-project phases, so every pack is structurally identical and reviewable, and the CSV mapping problem is bounded to four known schemas.

Commercial logic follows from the trigger. The buyer already has an approved project budget and a deadline measured in days, so the urgency is real, not manufactured. The scope memo is the part a generic AI cannot reliably hand over — it is the margin-protection artefact — which is what justifies $149 for ten packs rather than a $9 utility. JEV scores this concept 68.6/100 (band B, confidence 0.73), with speed-to-first-revenue (8.0) and solo build feasibility (7.37) as its strongest criteria and monetization potential (5.66) as its weakest. The plan below treats monetization as the thing to test hardest and earliest, not the thing to assume.

Section 2 of 8

Smallest sellable MVP

A paid web flow that takes one pasted or uploaded brief, generates an editable task table from a locked eight-phase taxonomy, and returns three downloadable files: a board CSV for one chosen tool, a scope memo PDF, and a missing-inputs checklist.

Must-have features

  • Brief intake via pasted text or PDF/DOCX upload with text extraction
  • LLM extraction into a structured brief object: deliverables, page count, stakeholders, dates, constraints
  • Locked eight-phase taxonomy (Discovery, Sitemap, Wireframes, Design rounds, Build, QA, Launch, Handoff)
  • Inline review table to rename, merge, delete and re-date tasks before export
  • CSV compiler with four mapping profiles: ClickUp, Asana, Trello, Taskade
  • One-page scope memo PDF with in-scope list, assumptions, revision allowance, out-of-scope items, sign-off block
  • Missing-inputs checklist engine flagging brand assets, copy, hosting/CMS access, legal pages, analytics
  • Stripe Checkout plus magic-link email returning the buyer to downloads for 7 days

Explicitly out of scope

  • No native OAuth or two-way sync with any board tool
  • No shared workspace, comments, or real-time team collaboration
  • No time tracking, invoicing, budget forecasting, or resource planning
  • No AI chat assistant or agent builder
  • No mobile app, no non-English output
  • No enterprise SSO, procurement paperwork, or invoice billing

Demo flow (what the buyer sees)

  1. Buyer lands on the page and clicks 'Compile a brief'
  2. Pastes brief text or uploads a PDF/DOCX
  3. Answers five scope questions: tool, kickoff date, revision rounds, deliverables out of scope, client sign-off owner
  4. Reviews and edits the generated task table inline
  5. Chooses a board profile and pays via Stripe Checkout
  6. Receives the magic link and downloads the CSV, scope memo PDF and checklist
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres plus magic-link authOpenAI or Anthropic API with structured JSON outputunpdf for PDF text extraction, mammoth for DOCXStripe Checkout and webhookResend for transactional emailVercel Blob for 24-hour brief file storageVercel Cron for retention cleanup

Architecture

A single Next.js app on Vercel. The intake page uploads a file to Vercel Blob or accepts pasted text, then one serverless route extracts text and calls the LLM with a strict JSON schema to produce a brief object. Deterministic code — not the model — expands that object into tasks against the locked taxonomy, offsets due dates from the kickoff date, and assigns dependencies. The buyer edits tasks in a client-side table held in Supabase. Export routes render the CSV per profile, the scope memo as printable HTML to PDF, and the checklist from a rules table. Stripe Checkout completes first, then a webhook writes the entitlement row and Resend sends the magic link.

Build steps

  1. Day 1: scaffold Next.js, Supabase schema (briefs, packs, tasks, entitlements), deploy landing page
  2. Day 2: intake route, PDF/DOCX text extraction, LLM structured-JSON extraction with schema validation and one retry
  3. Day 3: deterministic task generator on the locked taxonomy, plus the inline edit table
  4. Day 4: CSV compiler with four mapping profiles; scope memo and checklist renderers
  5. Day 5: Stripe Checkout, webhook, magic-link auth, download routes, end-to-end run on two real briefs

AI components

  • LLM extraction of deliverables, stakeholders, dates and constraints from raw brief text into a validated JSON object
  • LLM-suggested assumptions and out-of-scope candidates, always shown as editable suggestions, never auto-signed
  • Deterministic post-processing: phase assignment, date offsetting and dependency wiring are code, not model output
Hardest technical risk: Extraction quality on messy real briefs — scanned PDFs, nested tables, and deliverables buried in prose — producing a wrong task count on the free sample that destroys credibility before any payment.
Section 3 of 8

Pricing and monetization

Single Brief

Entry offer
$39 one-time

For Solo freelancers and two-person studios testing the output on one live project

  • One Client-Ready Project Pack
  • CSV export for one board tool
  • Scope memo PDF
  • Missing-inputs checklist

Agency Pack

$149 one-time

For 2-15 person agencies with several kickoffs per month

  • Ten Client-Ready Project Packs
  • All four CSV mapping profiles
  • Editable task review table
  • 7-day re-download history

Studio Monthly

$79 / month

For Agencies that want unlimited packs without counting credits

  • Unlimited packs
  • All export profiles
  • Saved scope-memo templates per client type
  • Email support within one business day

Model: One-time credit packs as the default, with an optional monthly unlimited tier offered only after a buyer has generated three or more packs.

First revenue offer: Convert one of your already-signed briefs into a Client-Ready Project Pack free within 24 hours — no signup, no call — then $149 for ten packs if it saved you an hour.

Expected ACV: $149

Upsell path: Single Brief buyers who use their credit get a $149 Agency Pack upgrade offer; anyone generating a third pack is emailed the $79 Studio Monthly switch.

Target customers
36
Revenue model
$5,364
Costs
$95
Profit model
$5,269
Section 4 of 8

First-customer acquisition

Primary channel

Personalised direct messages on LinkedIn and X to independent web-design and branding agency owners with a publicly visible new-client kickoff or scope-creep post.

Where to find them

  • LinkedIn search: founder/owner/account manager at agencies with 2-15 employees in US, UK, CA, AU
  • X search for 'new client kickoff', 'signed', 'scope creep', 'revision rounds' posted in the last 30 days
  • Public agency directories and Clutch-style listings filtered to web design and branding
  • Indie Hackers and r/web_design threads where owners describe brief-to-board rebuilds
  • LinkedIn post commenters on project-management and scope-creep threads

Exact outreach motions

  • Three-line LinkedIn DM naming the agency and the exact pain: signed brief to usable board
  • X reply-then-DM to owners posting about a kickoff, offering the free conversion
  • Follow-up at 72 hours attaching the missing-inputs checklist generated from their own brief
  • Three build-in-public threads on X and Indie Hackers with an anonymised before/after pack
  • Day-20 email to anyone with 3+ packs offering the $79 monthly switch
  • Referral ask to paying buyers: one free pack per referred agency that buys

Message template

Hi {first_name} — saw {agency} just kicked off {client_type} work. Converting that signed brief into tasks is usually the 2-hour job nobody bills. Send me the brief and I'll return a ready-to-import board CSV, a one-page scope memo and a missing-inputs checklist within 24 hours, free, no signup. Worth a look?
Week-one goal: 300 verified agency contacts listed with a trigger note, 100 DMs sent, 8 free packs delivered, and at least 1 paid Agency Pack.
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

Repo, schema, taxonomy, landing page

  • Scaffold Next.js on Vercel with Supabase.
  • Write the eight-phase taxonomy spec as a versioned JSON file.
  • Deploy landing page with a sample-pack CTA.

Deliverable: Live landing page and committed taxonomy spec.

Day 2Foundation

Brief intake and extraction

  • Build paste and PDF/DOCX upload intake route.
  • Wire LLM extraction to a validated JSON schema.
  • Add one retry and a visible extraction-error state.

Deliverable: Brief in, structured brief object out, tested on three briefs.

Day 3Build

Task generation and inline review

  • Generate tasks, dates and dependencies deterministically from the taxonomy.
  • Build the editable review table with rename, merge, delete and re-date.
  • Persist pack state in Supabase.

Deliverable: Editable task table a buyer could review without help.

Day 4Build

Output artefacts

  • Write CSV compiler for ClickUp and Asana profiles.
  • Add Trello and Taskade profiles.
  • Render scope memo HTML-to-PDF and the checklist rules engine.

Deliverable: All three deliverables downloadable from one pack.

Day 5LaunchMVP shipped

Payments and end-to-end

  • Add Stripe Checkout, webhook and entitlement rows.
  • Add magic-link auth and 7-day download routes via Resend.
  • Run two real briefs end to end and time the result.

Deliverable: Paid product live; MVP deadline met.

Day 6Pipeline

List build and samples

  • Build 120-row agency contact list with trigger notes.
  • Finalise the three-line DM template.
  • Produce three sample packs to use as proof links.

Deliverable: 120-row sheet plus three shareable sample packs.

Day 7Pipeline

First send

  • Send 50 personalised DMs.
  • Set a 24-hour manual fulfilment fallback for any brief received.
  • Log every reply and objection in a single sheet.

Deliverable: 50 sends logged, first conversations open.

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

Volume and fulfilment speed

  • Send 50 more DMs from the list.
  • Deliver every free pack within 24 hours.
  • Log extraction failures for the day-13 fix batch.

Deliverable: 100 total sends; all free packs returned.

Day 9OutreachFirst sale target

First sale push

  • Follow up the day-6 batch with their own checklist as the hook.
  • Send the $149 offer line to anyone who opened but did not reply.
  • Record the first paid check if it lands.

Deliverable: First sale target day; funnel sheet updated.

Day 10Product

Post-purchase experience

  • Ship the post-purchase email with all three file links.
  • Add a one-line 'what to fix before your kickoff' note to the memo PDF.
  • Log every buyer objection verbatim.

Deliverable: Clean purchase-to-download path with zero manual steps.

Day 11Distribution

Public proof

  • Publish X build-in-public thread with an anonymised before/after pack.
  • Post the same artefact to Indie Hackers.
  • Add the sample pack link to the DM template.

Deliverable: Two public posts with real output screenshots.

Day 12Outreach

Second wave

  • Send 50 DMs to the X-sourced segment.
  • Offer $39 Single Brief to non-repliers who engaged.
  • Reply to every comment on the thread within 2 hours.

Deliverable: 150 total sends; second segment opened.

Day 13Product

Fix the top failure

  • Fix the highest-frequency extraction failure from the log.
  • Add three missing-inputs rules from real briefs.
  • Re-run five past briefs and diff the output.

Deliverable: Measurably cleaner packs on the same inputs.

Day 14Review

Numbers and messaging

  • Compute reply rate, pack-to-paid rate and revenue to date.
  • Rewrite the DM subject line around the winning objection.
  • Decide whether $149 or $39 leads the next wave.

Deliverable: One-page decision memo on pricing and message.

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

Segment two list

  • Add 80 agencies from X kickoff and scope-creep posts.
  • Tag each with the exact post that triggered inclusion.
  • Deduplicate against the first 150.

Deliverable: 80 fresh, deduplicated contacts.

Day 16Outreach

Send

  • Send 40 personalised DMs from segment two.
  • Deliver free packs within 24 hours.
  • Log reply quality by segment.

Deliverable: 40 sends with segment tagging.

Day 17Distribution

Community post

  • Publish an Indie Hackers post on scope creep as a margin problem.
  • Run follow-up round two on all unanswered DMs.
  • Link the post in the DM signature.

Deliverable: One community post plus 60 follow-ups sent.

Day 18Product

Funnel instrumentation

  • Add event tracking to intake, edit, checkout and download.
  • Add saved scope-memo template scaffolding.
  • Check the funnel for the biggest drop-off.

Deliverable: Funnel dashboard showing where buyers stop.

Day 19Monetization

Monthly tier

  • Identify every buyer with three or more packs.
  • Email them the $79 Studio Monthly offer.
  • Draft the two-line comparison against buying packs.

Deliverable: Monthly-tier offer sent to qualified buyers.

Day 20Monetization

Recurring checkout

  • Ship Stripe subscription checkout for Studio Monthly.
  • Add unlimited-pack entitlement logic.
  • Confirm the one-time tiers stay live.

Deliverable: Three live tiers with correct entitlements.

Day 21Review

Segment performance

  • Add 100 contacts from directories and comment threads.
  • Compare conversion across the three segments.
  • Cut the worst segment from the next wave.

Deliverable: Segment scorecard and a trimmed target list.

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

Scale the winning segment

  • Send 50 DMs to the best-converting segment only.
  • Deliver packs within 24 hours.
  • Log time per pack to confirm unit economics.

Deliverable: 50 sends, all fulfilled, time-per-pack recorded.

Day 23Distribution

Case study

  • Ask one paying buyer for a one-paragraph testimonial.
  • Publish X thread two with that quote and a redacted pack.
  • Add the quote above the fold on the landing page.

Deliverable: One consented testimonial live on the site.

Day 24Product

Input robustness

  • Add DOCX parsing if not yet shipped.
  • Harden PDF extraction for scanned documents with a clear failure message.
  • Add error logging with brief-id correlation.

Deliverable: Fewer silent extraction failures.

Day 25Growth

Referral loop

  • Add a referral code to every receipt email.
  • Grant one free pack per referred agency that buys.
  • Measure referral attribution in Supabase.

Deliverable: Working referral loop with tracked codes.

Day 26Outreach

Third wave

  • Send 50 DMs with the testimonial as social proof.
  • Run follow-up round three on all opens.
  • Escalate high-response threads to a free call offer.

Deliverable: 50 sends with proof-backed messaging.

Day 27Positioning

Objection pages

  • Publish a page answering 'why not just use ChatGPT'.
  • Publish a page answering 'why CSV instead of native sync'.
  • Link both from the pricing section.

Deliverable: Two live objection pages.

Day 28Review

Double down

  • Recompute revenue, refunds and fees month to date.
  • Stop the lowest-yield outreach activity.
  • Allocate remaining days to the top two actions only.

Deliverable: Written kill/keep list for the final sprint.

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

Final push

  • Send 60 DMs to the warmest uncontacted segment.
  • Email all free-pack recipients with a same-day offer.
  • Confirm every payout is TrustMRR-verified.

Deliverable: Maximum in-window collected revenue.

Day 30Close

Reconciliation and next 30 days

  • Reconcile revenue against Stripe and TrustMRR.
  • Process any refunds and record them.
  • Write the post-contest plan: keep, pivot price, or stop.

Deliverable: Closed books and a written go/no-go 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

  • Conservative: 300 DMs produce 3 paid Agency Packs at $149; messenger assumed to be 2.9% + $0.30 per Stripe transaction.
  • Base: 300 DMs plus follow-ups produce 12 paid Agency Packs at $149, consistent with the concept's 1-in-8 reply hypothesis and an 8% replier-to-paid rate.
  • Upside: 30 paid orders at a blended $160 average, mixing $149 packs with $79 monthly subscriptions.
  • Ad spend is zero in Conservative and Base because acquisition is organic DMs and posts; Upside includes $150 of paid promotion.
  • Operating costs cover Vercel, Supabase, domain, Resend, Vercel Blob and LLM/parsing cost at roughly $0.50 per pack plus fixed subscriptions.
  • Payment fees assumed at 2.9% + $0.30 (Stripe) for Conservative and Base, blended 4.0% for Upside where subscriptions and mixed ticket sizes apply.
  • Refunds are assumed zero until volume justifies them; Upside models one full refund.
  • No chargebacks are modelled in any scenario; this is an assumption, not a measurement.
  • All figures are projections derived from the stated assumptions and are not verified revenue, customers or traction.

Conservative

3 customers
$447
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$14
Paid marketing
$0
Hackathon profit
$433
Operating costs
$25
Business profit
$408

Base case

12 customers
$1,788
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$55
Paid marketing
$0
Hackathon profit
$1,733
Operating costs
$45
Business profit
$1,688

Optimistic

30 customers
$4,800
collected revenue · avg payment $160
Refunds
$149
Chargebacks
$0
Payment fees
$192
Paid marketing
$150
Hackathon profit
$4,309
Operating costs
$110
Business profit
$4,199

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$468
Payment fees (3.9%)
$18
Paid marketing
$0
Hackathon profit
$450
Business profit
$405

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

All scenarios are projections built from the listed assumptions. They are not verified revenue, existing customers, or measured conversion rates.

Section 7 of 8

Main risks and validation experiments

Risk 1LinkedIn or X restricts the sending account and outreach volume collapses below 300 contacts.

Mitigation

Spread sends across both platforms, keep per-day volume under platform limits, and hold a 100-contact email fallback list built from public agency sites.

Validation experiment

Send 20 DMs on day 7 and measure deliverability and reply rate before committing to 50 per day.

Kill criteria

If fewer than 1 in 20 delivers-and-reads after 100 sends, stop the channel and move to community posts and direct email.

Risk 2Buyers decide a general AI chat does the same job and refuse $149.

Mitigation

Lead every message with the scope memo and checklist, not the task list, and publish the 'why not just ChatGPT' page on day 27.

Validation experiment

Ask the first five repliers directly whether they would have used ChatGPT for this, and record the answer verbatim.

Kill criteria

If three or more of five repliers say ChatGPT is sufficient and none convert, drop to $39 Single Brief as the headline price.

Risk 3Extraction errors on the free sample destroy credibility before any payment.

Mitigation

Timebox every free pack, review task counts before sending, and ship an explicit 'this looked like a scanned PDF' failure state rather than a bad pack.

Validation experiment

Run ten real briefs through the pipeline and hand-score each output before sending any free sample.

Kill criteria

If fewer than 7 of 10 briefs need under five minutes of editing, extend the build and delay outreach rather than send defective samples.

Risk 4Agencies demand native ClickUp or Asana sync, which is out of scope and could stall conversion.

Mitigation

Answer with the CSV import path in one sentence, plus a screenshot of a successful import, and hold a sync waitlist instead of building it.

Validation experiment

Track how many repliers raise sync; capture the exact wording used.

Kill criteria

If more than half of qualified repliers make native sync a precondition, reposition around the scope memo only and raise price rather than build sync.

Risk 5Mid-November to mid-December is delivery-heavy and holiday-adjacent, slowing new tool purchases.

Mitigation

Lean on the 'free conversion in 24 hours' offer, which asks for no purchase decision, and push monthly upgrades to buyers already in the product.

Validation experiment

Compare reply and purchase rates in week 2 against week 4 to detect a seasonal drop.

Kill criteria

If paid conversion falls below 2% of repliers for two consecutive weeks, shift the offer to a discounted pack bundle inside the window.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the GitHub repo and Vercel project.
  • Provision Supabase and write the initial schema.

Output: Deployed empty app with a connected database.

Hours 3-5

  • Write the eight-phase taxonomy spec as JSON.
  • Define the structured brief extraction schema.
  • Commit both as versioned files.

Output: taxonomy.v1.json and brief-schema.v1.json.

Hours 6-8

  • Build the intake route for pasted text.
  • Call the LLM and validate the JSON response.
  • Render extracted deliverables on screen.

Output: Working paste-to-structured-brief demo.

Hours 9-10

  • Draft the landing page headline, offer and three-line DM.
  • Publish the page with a single call to action.

Output: Live landing page ready to receive a DM link.

Hours 11-12

  • Write the first 20 rows of the agency list with trigger notes.
  • Send the first five DMs as a deliverability test.

Output: 20-row contact sheet and five logged sends.

Complete report

Full 30-day launch report

Read the full generated report

BriefToBoard Compiler — 30-Day Plan

1. Product opportunity and positioning

The trigger is a signature. An agency owner signs a client, books a kickoff inside seven days, and then spends one to three hours retyping a prose brief into tasks, phases, dates and dependencies inside ClickUp, Asana, Trello or Taskade. The board is half-built at kickoff. Worse, nothing records what the agency assumed or excluded, so the first revision round arrives unbilled.

BriefToBoard Compiler sells a compile step, not a platform. The buyer pastes or uploads a brief, answers five scope questions, edits the generated task table, and downloads a Client-Ready Project Pack: a CSV mapped to their existing board schema, a one-page scope memo with in-scope work, assumptions, revision allowance, out-of-scope items and a sign-off line, and a missing-inputs checklist naming each absent asset, its owner and a due date.

The wedge is intentionally narrow. No workspace, no migration, no per-seat pricing, no native sync. That narrowness is what makes a five-day solo build credible: the taxonomy is locked to eight web-project phases, so every pack is structurally identical, and CSV mapping is bounded to four known schemas. JEV scores the concept 68.6/100 (band B). Speed to first revenue (8.0) and solo build feasibility (7.37) are strengths; monetization potential (5.66) is the weakest criterion, so this plan tests price early rather than assuming it.

2. Smallest sellable MVP

The MVP is one paid web flow: intake, extraction, an editable task table, and three downloads. Brief intake accepts pasted text or a PDF/DOCX upload. One LLM call returns a validated brief object. Deterministic code — not the model — expands that object across the locked taxonomy, offsets due dates from the kickoff date and assigns dependencies. The buyer renames, merges or deletes tasks inline, picks a board profile, pays, and receives a magic link to the CSV, the scope memo PDF and the checklist. Everything else — sync, collaboration, time tracking, chat, mobile — is out of scope until the contest ends.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres and magic-link auth, an OpenAI or Anthropic call with strict JSON schema output, unpdf and mammoth for text extraction, Stripe Checkout with a webhook, Resend for email, and Vercel Blob for 24-hour file retention. The build runs five days: scaffold and deploy; intake and extraction; task generation and inline review; CSV compiler plus memo and checklist renderers; then payments, auth, downloads and a full end-to-end run on two real briefs. The hard part is extraction quality on messy real documents. The mitigation is architectural: the model only extracts facts, and all phase, date and dependency logic is ordinary code that can be tested and diffed.

4. Pricing and monetization

Three tiers, all live by day 20. Single Brief at $39 one-time for a solo freelancer testing one live project. Agency Pack at $149 one-time for ten packs, all four CSV profiles and 7-day re-download history — this is the default offer. Studio Monthly at $79 per month for unlimited packs, offered only to buyers who have generated three or more packs, so the subscription never cannibalises the pack sale that funds it.

The first revenue offer is a free conversion: send one already-signed brief, receive the full pack within 24 hours, no signup and no call. The closing line is $149 for ten packs if it saved an hour. Upsell runs from Single Brief to Agency Pack to Studio Monthly.

5. First-customer acquisition

One channel: personalised DMs on LinkedIn and X to agency owners with a visible new-client kickoff or scope-creep post. Targets come from LinkedIn owner searches at 2-15 person agencies in the US, UK, Canada and Australia, X keyword searches, public agency directories, and Indie Hackers threads. Every contact is recorded with the specific post that triggered inclusion.

The message is three lines: name the agency, name the pain, offer the free conversion. Follow up once at 72 hours with the missing-inputs checklist built from their own brief. Three build-in-public threads carry anonymised before-and-after packs. Week-one goal: 300 contacts listed, 100 DMs sent, 8 free packs delivered, at least one paid Agency Pack.

6. 30-day execution roadmap

Days 1-5 build and launch. Day 1 scaffolds the app and writes the taxonomy spec. Day 2 ships intake and extraction. Day 3 ships task generation and the edit table. Day 4 ships the CSV compiler and both document renderers. Day 5 adds Stripe, magic-link auth and downloads — MVP live and sellable.

Days 6-14 are the first outreach wave. Build a 120-row list, finalise the DM, produce three sample packs, send 50 DMs on day 7 and 50 more on day 8, follow up on day 9 as the first-sale target, then ship the post-purchase email, publish a build-in-public thread, send a third wave, fix the top extraction failure, and review reply and paid rates on day 14.

Days 15-21 widen the pipe and add recurring revenue. Segment two adds 80 X-sourced agencies; 40 DMs go out on day 16; an Indie Hackers post ships on day 17; funnel tracking lands on day 18; the Studio Monthly offer goes to 3+ pack buyers on day 19 and checkout ships on day 20; day 21 scores segments and adds 100 more contacts.

Days 22-28 scale the winner. Fifty DMs to the best segment, a consented testimonial, DOCX and scanned-PDF hardening, a referral code per receipt, a proof-backed third wave, two objection pages ('why not ChatGPT', 'why CSV'), then a written kill/keep list. Days 29-30 are the final push: 60 DMs, an offer to every free-pack recipient, payout verification against TrustMRR, reconciliation, refunds, and a go/no-go decision for the following month.

7. Revenue and profit scenarios

All three scenarios are projections from stated assumptions, not verified revenue. Conservative: 3 Agency Packs at $149, $447 gross, $14 in Stripe fees, $25 operating cost. Base: 12 packs, $1,788 gross, $55 fees, $45 operating. Upside: 30 orders at a $160 blended average, $4,800 gross, $149 refunds, $192 fees, $150 ad spend, $110 operating.

Hackathon profit counts revenue minus refunds, chargebacks, payment fees and paid ad spend — hosting and AI delivery costs are not deducted there, but business profit is. In Conservative and Base, hackathon and business profit differ only by $25 and $45 respectively; operating cost never threatens the margin because a pack costs roughly $0.50 in model and parsing spend against a $39 to $149 price.

8. Main risks and validation experiments

First, channel restriction. If LinkedIn or X throttles sends, volume dies. Test with 20 sends on day 7; if fewer than 1 in 20 is read after 100 sends, move to email and community posts.

Second, 'ChatGPT could do this'. Lead with the scope memo, not the task list, and ask the first five repliers directly. If three of five say a chat is sufficient and nobody converts, make $39 the headline price.

Third, extraction errors on free samples. Hand-score ten real briefs before sending anything; if fewer than seven need under five minutes of editing, delay outreach rather than ship a bad sample.

Fourth, demands for native sync. Answer with CSV in one sentence plus an import screenshot, and keep a waitlist. If more than half of qualified repliers make sync a precondition, reposition around the memo only.

Fifth, a holiday-adjacent December. Compare week-2 and week-4 conversion; if paid conversion stays under 2% of repliers for two weeks, switch to a discounted bundle inside the window.

9. First 24-hour action plan

Hours 1-2: repo, Vercel project, Supabase schema. Hours 3-5: taxonomy spec and extraction schema committed as versioned files. Hours 6-8: paste-to-structured-brief working on screen. Hours 9-10: landing page live with a single call to action. Hours 11-12: twenty contact rows with trigger notes and five test DMs sent. The day-one artefact is a live page, a validated extraction demo, and proof that the sending account works.

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 →