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

Figure Preflight

Automatically checks and repairs scientific manuscript figures against any journal's author guidelines, returning a submission-ready figure pack and compliance report for medical writers.

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.20/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct LinkedIn outreach to medical writers and publication managers at small medical communications agencies.
Who pays

Medical writers and publication managers at 5-50 person medical communications agencies who submit 10+ journal manuscripts per month.

Biggest execution risk

Solo build feasibility 5.0/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 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.5/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
$99
Solo build
5 days
30d base revenue
$2,280
30d hackathon profit
$2,067
Section 1 of 8

Product opportunity and positioning

Target customer

Medical writers and publication managers at 5-50 person medical communications agencies who submit 10+ journal manuscripts per month.

Why now

Structured-output LLM parsing makes author guidelines machine-readable at cents per job, and serverless image processing means one founder can deliver a paid order without a design team.

Problem

Journals reject or delay manuscripts for wrong DPI, RGB instead of CMYK, wrong column width, missing panel labels or bad file naming, and writers repair each figure by hand in Photoshop for every target journal.

Solution

Upload figures and the journal's guidelines; the app parses the guidelines into rules, runs each figure through a transform pipeline, and returns a ZIP of fixed files plus a PDF pass/fail compliance report.

Differentiation · General preflight tools validate PDF standards; Figure Preflight validates a named journal's author guidelines and rewrites the figure to match, then documents every fix.

1. Product opportunity and positioning

Figure rejection is a deadline problem, not a design problem. A medical writer at a 5-50 person medical communications agency ships ten or more manuscripts a month, and each one carries a journal-specific gauntlet: 300 vs 600 DPI, RGB vs CMYK, exact column width, embedded fonts, panel letters, file naming, TIFF vs EPS. The writer reads the author guidelines, opens every figure in Photoshop or Illustrator, repairs it by hand, then repeats the whole read-and-repair loop for the next journal. Hours per manuscript, every month, with a submission date attached.

Figure Preflight collapses that pass into one upload. The buyer is not a scientist creating a figure; it is the writer validating one before it leaves the agency. The wedge is deliberately narrow: no icon library, no editor, no collaboration layer. The deliverable is a ZIP of repaired figures plus a PDF compliance report listing each rule, its pass/fail state and the fix applied. That report is what the writer attaches to the submission record and what justifies the invoice to an account lead.

The positioning is the deterministic rule engine. The alternatives today are a checklist in a spreadsheet, a designer's hourly rate, or a general preflight tool that understands PDF/X but not the author guidelines of a specific journal. Figure Preflight competes on time-to-a-concrete-file and on the audit trail, not on visual creativity.

Why this is sellable inside a 30-day window: guideline parsing is now cheap and reliable enough with structured-output models, image transforms are a library call, and the entire pipeline runs serverless with no human in the loop. A solo founder can ship it in five days and deliver a $99 order at roughly cents of compute. The buyer is a professional spending agency money on a recurring, deadline-driven task, paying by card without procurement, and reachable directly on LinkedIn by role title. The first paying customer does not need SEO, a marketplace, an integration or a security review.

Scope discipline is the moat for the next 30 days: one workflow (upload, parse, repair, report), one output format (ZIP plus PDF), ten preloaded journals at launch growing to a requested-journal queue. Every feature that does not shorten the gap between "figures due Friday" and "figures accepted" is out of scope.

Section 2 of 8

Smallest sellable MVP

A paid web page where a writer uploads up to 10 figures, picks one of 10 preloaded journals or pastes guideline text, pays $99, and receives a fixed figure ZIP plus a PDF compliance report by email within 24 hours.

Must-have features

  • Figure upload for TIFF, PNG, PDF and PPTX with per-file size limits
  • Guideline intake by journal dropdown (10 preloaded) or pasted text
  • Rule extraction to a structured rule set with editable overrides
  • Transform pipeline: DPI resample, RGB to CMYK, resize to column width, pad/crop, panel labels, rename
  • Compliance report PDF with per-rule pass/fail and list of applied fixes
  • ZIP packaging and email delivery via a queued job
  • Stripe checkout with three tiers and instant access
  • Per-tier job quota and an admin screen to add journal rule packs

Explicitly out of scope

  • No figure creation or design editor
  • No collaboration, comments or reviewer workflow
  • No 3D, microscopy raw or vector reconstruction
  • No automated journal submission or portal login
  • No AI-generated illustrations
  • No team billing, SSO or procurement paperwork

Demo flow (what the buyer sees)

  1. Writer signs up and pays $99 for a Single Manuscript Pack
  2. Writer uploads 6 figures and selects a target journal from the dropdown
  3. Parser converts the guidelines into a rule list shown for confirmation
  4. Pipeline resamples, color-converts, resizes, adds panel labels and renames each file
  5. Report generator writes a PDF with pass/fail per rule and the fix applied
  6. Writer receives an email with the fixed ZIP and the report PDF
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres and storageStripe Checkout and webhooksSharp for raster transformspdf-lib for report generationGhostscript or ImageMagick layer for CMYK conversionOpenAI API with structured outputs for guideline parsingResend for transactional email

Architecture

A Next.js app on Vercel handles auth, upload and Stripe checkout. Uploaded files go straight to Supabase storage under a job ID. The guideline text or a preloaded journal pack is parsed into a JSON rule set stored in Postgres. A serverless worker pulls the job, runs each file through Sharp and the CMYK step, writes outputs back to storage, generates the report PDF with pdf-lib, zips the results and emails a signed URL with Resend. Stripe webhooks gate job creation by tier quota. Everything is stateless; no always-on server, no per-customer infrastructure.

Build steps

  1. Scaffold Next.js app, Supabase schema (users, jobs, files, journals, rules) and deploy to Vercel on day 1
  2. Build upload UI with signed storage URLs and per-tier file limits
  3. Implement the Sharp transform chain and validate on five sample figures
  4. Add the guideline parser with a fixed JSON rule schema and cache preloaded journal packs
  5. Generate the compliance report PDF and ZIP, then deliver by email through a queued job
  6. Wire Stripe Checkout for the three tiers plus webhook-driven quota gating
  7. Load 10 journal rule packs and an admin screen for manual additions
  8. Run 20 dry runs, log failures, fix the top five, then flip to production keys

AI components

  • LLM with structured output converts pasted author-guideline text into the rule JSON schema
  • Fallback heuristic parser for guideline PDFs the model extracts poorly
Hardest technical risk: RGB to CMYK conversion plus DPI resampling can shift color and tone in ways a writer will not accept; the pipeline must flag any conversion it cannot prove safe rather than silently overwrite the file.
Section 3 of 8

Pricing and monetization

Single Manuscript Pack

Entry offer
$99 one-time

For Individual medical writer or researcher with one manuscript

  • Up to 10 figures
  • One target journal
  • Compliance report PDF
  • Auto-fixed figure files

Lab Pack

$299 one-time

For Small research lab or freelance writer with multiple submissions

  • 5 manuscripts
  • Up to 10 figures each
  • Compliance report PDFs
  • Auto-fixed figure files

Agency Monthly

$499 / month

For Medical communications agency submitting 10+ manuscripts per month

  • 20 manuscripts per month
  • Priority processing
  • Custom journal rule packs
  • Compliance reports and auto-fixed files

Model: Three prepaid tiers: two one-time manuscript packs and one monthly agency subscription, all bought by card with no procurement.

First revenue offer: Free preflight of one figure from a recent manuscript with a report and a 90-second Loom; if it holds up, $99 Single Manuscript Pack, or $499/month Agency plan at 50% off month one if signed within 7 days.

Expected ACV: $190

Upsell path: Single Manuscript Pack to Lab Pack for repeat submitters, then to Agency Monthly once a writer passes three manuscripts in a month; custom journal rule packs and extra manuscript blocks extend the monthly plan.

Target customers
200
Revenue model
$99,800
Costs
$600
Profit model
$99,200
Section 4 of 8

First-customer acquisition

Primary channel

Direct LinkedIn outreach to medical writers and publication managers at small medical communications agencies.

Where to find them

  • LinkedIn search: 'medical writer' filtered to agencies with 5-50 employees
  • LinkedIn search: 'publication manager' and 'publications lead' at healthcare communications firms
  • Freelance medical writer directories and personal portfolio sites
  • Medical writing and publication professionals groups on LinkedIn
  • Conference attendee lists and speaker rosters for medical writing events
  • Referral asks to every writer who receives a free preflight

Exact outreach motions

  • Send a 3-sentence LinkedIn connection note naming the journal-formatting pain, no pitch, no link
  • On acceptance, offer a free preflight of one figure from a recent manuscript with no signup
  • Deliver the free compliance report plus a 90-second Loom showing the before and after
  • Ask one question: which journal gave them the worst figure rejection last quarter
  • Offer the $99 pack with a 7-day window, or the $499 agency plan at 50% off month one
  • Follow up on day 3 with an anonymized time-saved example and ask for one referral

Message template

Hi [Name] - I built a tool that checks manuscript figures against a target journal's author guidelines and auto-fixes DPI, CMYK, column width, panel labels and file naming. I'm running free preflights this week for medical writers. Can I run one figure from a recent manuscript and send you the compliance report? No signup needed.
Week-one goal: 300 verified LinkedIn profiles listed, 120 outreach messages sent, 12 replies, 5 free preflights delivered by day 7, and the first paid order closed by day 12.
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 1Build

Foundation

  • Scaffold Next.js app and deploy to Vercel.
  • Create Supabase tables for users, jobs, files, journals, rules.
  • Create three Stripe products in test mode.

Deliverable: Deployed skeleton with pricing page stub

Day 2Build

Image pipeline

  • Add upload UI with signed storage URLs.
  • Implement Sharp resample, resize and panel-label steps.
  • Add CMYK conversion with a safety flag.

Deliverable: Transforms working on 5 sample figures

Day 3Build

Rule engine

  • Define the rule JSON schema.
  • Write the structured-output guideline parser.
  • Hand-build 10 journal rule packs.

Deliverable: Rule JSON for 10 journals

Day 4Build

Output and delivery

  • Generate compliance report PDF with pdf-lib.
  • Zip outputs and send via Resend.
  • Add a queued job runner with retries.

Deliverable: End-to-end job with emailed ZIP and report

Day 5BuildMVP shipped

Paid launch

  • Wire Stripe checkout and webhook quota gating.
  • Add per-tier limits and job status page.
  • Deploy to production with real keys.

Deliverable: Live paid product (MVP deadline)

Day 6Harden

Reliability

  • Run 20 dry jobs on varied sample figures.
  • Log every failure and fix the top five.
  • Add fallback parsing for image-only guideline PDFs.

Deliverable: Pass-rate log with fixes shipped

Day 7Pre-launch

Proof assets

  • Record a 90-second Loom demo.
  • Publish landing page with the three tiers.
  • Run one real test purchase and refund it.

Deliverable: Demo assets and verified payment flow

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

List building

  • Build a 300-profile LinkedIn list of medical writers at small agencies.
  • Tag each lead by journal and manuscript volume.
  • Draft two message variants.

Deliverable: 300-lead spreadsheet with notes

Day 9Outreach

First sends

  • Send 40 personalized connection notes.
  • Post the offer in 3 medical writing LinkedIn groups.
  • Log every reply in the sheet.

Deliverable: 40 sends logged, first replies in

Day 10Outreach

Free preflights

  • Send 40 more messages.
  • Run free preflights for everyone who replied.
  • Send reports with a short Loom each.

Deliverable: 5 free compliance reports delivered

Day 11Outreach

Conversations

  • Send 40 more messages.
  • Follow up on all day-9 threads.
  • Send per-lead Looms to warm leads.

Deliverable: 8 live conversations

Day 12SellFirst sale target

First revenue

  • Send the $99 pack offer to every warm lead.
  • Remove friction: single-page checkout link.
  • Close and confirm payment in Stripe.

Deliverable: First verified payment

Day 13Deliver

Fulfilment quality

  • Deliver the paid job within 24 hours.
  • Ask for a one-line testimonial and a referral.
  • Log every manual touch needed.

Deliverable: Delivered ZIP, report and feedback note

Day 14Iterate

Fix what broke

  • Fix the top 3 issues from paid delivery.
  • Add 2 requested journal rule packs.
  • Update the landing page FAQ with real objections.

Deliverable: Changelog and 2 new journal packs

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

Referrals

  • Send 50 new LinkedIn messages.
  • Ask the first customer for 2 named referrals.
  • Post an anonymized before/after in one group.

Deliverable: 3 referrals identified

Day 16Outreach

Publication managers

  • Send 50 messages targeting publication managers.
  • Run free preflights for all repliers.
  • Test a subject line naming a specific journal.

Deliverable: 10 replies, 4 free reports

Day 17Sell

Pack upgrade

  • Pitch the $299 Lab Pack to multi-manuscript leads.
  • Offer a 5-manuscript bundle price for 7 days.
  • Close two pack sales.

Deliverable: 2 Lab Pack payments

Day 18Proof

Case study

  • Write an anonymized before/after case page.
  • Include time saved and rules fixed.
  • Add it to the outreach follow-up sequence.

Deliverable: Case study page live

Day 19Agency

Monthly pitch

  • Pitch the $499 Agency plan to 10 warm leads at 50% off month one.
  • Book 5 short demo calls.
  • Prepare a 20-manuscript quota walkthrough.

Deliverable: 5 demo calls booked

Day 20Agency

First subscription

  • Run the demo calls and quote the plan.
  • Send a checkout link immediately after each call.
  • Close one monthly subscription.

Deliverable: First recurring payment

Day 21Ops

Self-serve

  • Add a journal request form inside the app.
  • Enforce queue limits per tier.
  • Add a status page for in-flight jobs.

Deliverable: Request form and enforced limits live

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

Message testing

  • Send 60 messages with a second variant.
  • Compare reply rates across variants.
  • Keep the winning variant only.

Deliverable: Variant reply-rate table

Day 23Scale

Volume

  • Send 60 more messages.
  • Publish one community post on figure rejections.
  • Follow up on all unanswered threads.

Deliverable: 15 replies logged

Day 24Product

Trust

  • Add explicit warnings when CMYK conversion is uncertain.
  • Flag figures below target DPI instead of upscaling blindly.
  • Release v1.1.

Deliverable: v1.1 shipped with safety flags

Day 25Revenue

Upsell

  • Email Single Pack buyers the Lab Pack offer.
  • Add one-click top-up for extra manuscripts.
  • Close two upsells.

Deliverable: 2 upsell payments

Day 26Revenue

Agency trials

  • Send 60 messages to agency publication leads.
  • Follow up on every demo call from week 3.
  • Start 2 agency trials at 50% off.

Deliverable: 2 agency trials running

Day 27Ops

Support load

  • Review refunds and edge cases.
  • Write support macros for the 5 common objections.
  • Cap manual journal work to protect margin.

Deliverable: Support playbook

Day 28Proof

Referral loop

  • Publish a second case study.
  • Launch a referral link with one free preflight per referral.
  • Update the landing page hero with the case result.

Deliverable: Referral link live

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

Final closes

  • Send 80 messages with a deadline offer.
  • Convert trials to paid monthly plans.
  • Call every warm lead once.

Deliverable: 6 closes in 24 hours

Day 30Close

Reconciliation

  • Reconcile Stripe payouts against jobs delivered.
  • Confirm every payment landed inside the contest window.
  • Deliver any outstanding files same day.

Deliverable: Verified revenue total

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 case: only small one-time packs sell, no agency subscription closes.
  • Base case: mixed sales, mostly $99 packs, two $299 Lab Packs, one $499 monthly.
  • Upside case: four $499 monthly subscriptions plus a steady pack mix from referrals.
  • Payment fees assume Stripe at 2.9% plus $0.30, blended to roughly 5% on $99-$299 tickets.
  • Ad spend is $0 in all scenarios: the channel is organic LinkedIn outreach and referrals only.
  • Operating costs cover Vercel, Supabase, Resend, domain and OpenAI guideline-parsing calls at cents per job.
  • Hackathon profit excludes hosting, tooling and AI delivery costs; business profit subtracts them.
  • All figures are projections from stated assumptions, not verified revenue or existing customers.

Conservative

4 customers
$596
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$30
Paid marketing
$0
Hackathon profit
$566
Operating costs
$30
Business profit
$536

Base case

12 customers
$2,280
collected revenue · avg payment $190
Refunds
$99
Chargebacks
$0
Payment fees
$114
Paid marketing
$0
Hackathon profit
$2,067
Operating costs
$120
Business profit
$1,947

Optimistic

30 customers
$6,900
collected revenue · avg payment $230
Refunds
$149
Chargebacks
$0
Payment fees
$345
Paid marketing
$0
Hackathon profit
$6,406
Operating costs
$260
Business profit
$6,146

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,188
Payment fees (3.9%)
$46
Paid marketing
$0
Hackathon profit
$1,142
Business profit
$1,022

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. No customers, traction or partnerships exist yet.

Section 7 of 8

Main risks and validation experiments

Risk 1Journal guidelines are image-based PDFs or ambiguous prose, so parsed rules are wrong and figures get repaired incorrectly.

Mitigation

Show the parsed rule list for confirmation before processing, flag low-confidence rules, and ship 10 hand-verified journal packs as the default path.

Validation experiment

Parse 20 real author-guideline documents and score rule accuracy against a hand-written answer key.

Kill criteria

Fewer than 70% of rules correct without manual editing across those 20 documents.

Risk 2Medical writers do not trust automated fixes on scientific figures and keep repairing by hand.

Mitigation

Always return the original file alongside the fixed file, and warn instead of converting when CMYK output is uncertain.

Validation experiment

Send 10 writers a before/after pair for their own figure and ask whether they would submit the fixed version unchanged.

Kill criteria

Fewer than 3 of 10 say they would submit the fixed file.

Risk 3LinkedIn outreach is rate-limited or ignored, so fewer than five conversations start in week one.

Mitigation

Keep messages short and non-promotional, cap daily sends, and add community posts and referral asks as a parallel source.

Validation experiment

Send 100 connection notes over three days and track acceptance and reply rate by message variant.

Kill criteria

Under 10% acceptance after 100 sends with the best variant.

Risk 4Buyers treat a $99 pack as a one-off and never reach the $499 monthly plan, capping revenue.

Mitigation

Track manuscript volume in the free preflight call and route anyone above three per month straight to the agency pitch.

Validation experiment

Offer the agency plan to the first 10 free-preflight recipients and count how many take a discounted trial.

Kill criteria

Zero agency trials from 10 qualified offers.

Risk 5Figure auto-fixes could introduce scientific inaccuracies that damage a client relationship and trigger refunds.

Mitigation

Keep an immutable original, log every transform, and never silently upscale below-target resolution.

Validation experiment

Manually review 20 auto-fixed figures against originals before the first paid delivery.

Kill criteria

Any transform that alters content rather than format without a visible warning.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register domain and create Vercel and Supabase projects.
  • Scaffold the Next.js app and push the first deploy.
  • Create the Supabase schema for jobs, files, journals and rules.

Output: Live skeleton URL and database schema

Hours 3-5

  • Build the upload page with signed storage URLs.
  • Implement the Sharp DPI resample and resize steps.
  • Test on three sample figures from a public figure set you assemble yourself.

Output: Working upload plus transform on sample files

Hours 6-8

  • Define the rule JSON schema.
  • Write the structured-output guideline parser and run it on one public journal guideline.
  • Cache the parsed rules in Postgres.

Output: Parsed rule set for one journal

Hours 9-11

  • Generate a compliance report PDF with pdf-lib.
  • Zip the outputs and email them via Resend.
  • Connect the job runner end to end.

Output: First complete job: ZIP plus report in an inbox

Hours 12-14

  • Create the three Stripe products in test mode.
  • Wire checkout and webhook quota gating.
  • Publish the landing page with pricing and the free-preflight offer.

Output: Public landing page with working test checkout

Complete report

Full 30-day launch report

Read the full generated report

Figure Preflight - 30-Day Launch Report

Window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. This plan covers Days 1-30 (16 Nov - 15 Dec) and leaves 16 Dec as a collection buffer.

1. Product opportunity and positioning

A medical writer at a 5-50 person medical communications agency ships ten or more manuscripts a month. Every manuscript hits a journal-specific gauntlet: 300 vs 600 DPI, RGB vs CMYK, exact column width, embedded fonts, panel letters, file naming. The writer reads the author guidelines, repairs each figure by hand in Photoshop or Illustrator, and repeats the loop for the next journal. Hours per manuscript, every month, against a submission date.

Figure Preflight collapses that into one upload. The buyer is not a scientist creating a figure; it is the writer validating one. The wedge is narrow on purpose: no icon library, no editor, no collaboration. Output is a ZIP of repaired figures plus a PDF compliance report listing each rule, pass/fail and the fix applied. That report is the artifact the writer attaches to the submission and the reason an account lead approves the invoice.

The positioning is the deterministic rule engine. Alternatives are a spreadsheet checklist, a designer's hourly rate, or a general preflight tool that knows PDF/X but not the author guidelines of a named journal. Figure Preflight wins on time-to-a-concrete-file and on the audit trail, never on creativity.

2. Smallest sellable MVP

One page: upload up to 10 figures, pick one of 10 preloaded journals or paste guideline text, pay $99, receive a fixed ZIP and a PDF report by email. Nothing else ships on day 5. The compliance report is the product surface; the figure transforms are the reason it exists.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres and storage, Stripe Checkout with webhooks for quota gating, Sharp for raster transforms, pdf-lib for the report, Resend for delivery, and an LLM with structured outputs to convert guideline text into the rule schema. The job runner is stateless: pull job, transform files, write outputs, build report, zip, email a signed URL. Ten hand-verified journal packs ship at launch so the first customer never depends on parsing quality. The hardest technical risk is CMYK conversion and DPI resampling changing tone; the pipeline must flag uncertain conversions rather than overwrite silently.

4. Pricing and monetization

Three card-first tiers: Single Manuscript Pack $99 one-time (10 figures, one journal), Lab Pack $299 one-time (5 manuscripts), Agency Monthly $499 (20 manuscripts per month, priority processing, custom journal packs). Expected average order value at launch is about $190. The path is pack, then Lab Pack, then monthly once a writer passes three manuscripts in a month.

5. First-customer acquisition

One channel: LinkedIn outreach to medical writers and publication managers at small medical communications agencies. Build a 300-profile list, send short non-promotional notes, and convert replies with a free preflight of one real figure plus a 90-second Loom. The free report is the sales call. Week one target: 300 leads listed, 120 messages sent, 12 replies, 5 free preflights delivered.

6. 30-day execution roadmap

Days 1-5, build: scaffold, image pipeline, rule engine, report and delivery, then Stripe and production deploy. MVP is live on day 5.

Days 6-7, harden and prepare: twenty dry jobs, fix the top five failures, record the demo, publish the landing page, run and refund a real test purchase.

Days 8-14, first revenue: build the list, send 40 messages a day, run free preflights, close the first paid pack on day 12, deliver within 24 hours, then fix whatever the paid job exposed.

Days 15-21, expand ticket size: referrals, publication-manager targeting, $299 Lab Pack pushes, an anonymized case page, and the first $499 agency subscription by day 20.

Days 22-30, compound and close: message-variant testing, 60-message days, v1.1 with explicit safety flags on CMYK and resolution, upsells to pack buyers, agency trials started, a referral link, a final deadline push, and full Stripe reconciliation on day 30.

7. Revenue and profit scenarios (projections only)

These are models, not results. There are no customers today.

  • Conservative: 4 customers at $149 average, $596 gross, $0 refunds, $30 payment fees, $0 ad spend, $30 operating cost. Hackathon profit $566; business profit $536.
  • Base: 12 customers at $190 average, $2,280 gross, $99 refunds, $114 fees, $0 ad spend, $120 operating cost. Hackathon profit $2,067; business profit $1,947.
  • Upside: 30 customers at $230 average, $6,900 gross, $149 refunds, $345 fees, $0 ad spend, $260 operating cost. Hackathon profit $6,406; business profit $6,146.

Fees assume Stripe at 2.9% plus $0.30, blended to roughly 5% on small tickets. Ad spend is zero because the channel is organic. Operating cost covers Vercel, Supabase, Resend, the domain and guideline-parsing calls. The contest ranks hackathon profit, which excludes hosting and delivery costs; business profit subtracts them. The 200-customer figure in the original concept is not used here as a forecast.

8. Main risks and validation experiments

Parsing accuracy. Test 20 real guideline documents against a hand-written key. Kill the auto-parse path if under 70% of rules are correct without manual editing; fall back to hand-built packs.

Trust in auto-fixes. Send 10 writers a before/after pair for their own figure and ask if they would submit the fixed file unchanged. Fewer than 3 yes answers means repositioning to a check-only report.

Outreach deliverability. Send 100 connection notes over three days and measure acceptance and reply rate by variant. Under 10% acceptance means switching to community posts and referral asks.

Ticket-size ceiling. Offer the agency plan to the first 10 free-preflight recipients. Zero trials from 10 qualified offers means the monthly tier needs redesign before day 30.

9. First 24-hour action plan

  • Hours 1-2: domain, Vercel, Supabase, schema, first deploy.
  • Hours 3-5: upload page and the Sharp resample/resize chain working on sample figures.
  • Hours 6-8: rule schema plus the structured-output parser on one public guideline.
  • Hours 9-11: report PDF, ZIP, Resend delivery, first complete job.
  • Hours 12-14: three Stripe products in test mode, webhook gating, landing page published with the free-preflight offer.

At the end of day one the founder has a public page, a working job, and a payment path in test mode. Days 2-5 turn that into the paid product.

All revenue and profit figures in this report are projections derived from stated assumptions. No customers, revenue, partnerships or sources are claimed.

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 →