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

ExhibitSmith Court Packets

ExhibitSmith turns a folder of case PDFs into a court-ready exhibit packet with Bates numbers, bookmarks, and a linked index in minutes.

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.30/10
MVP build (solo)
4 days
Launch price
$399
Sales to $1,000 revenue
3 customers
First paying customer
Cold email to litigation paralegals and office managers at 1-20 person US law firms sourced from public state bar directories.
Who pays

Litigation paralegal or solo attorney at a 1-20 person US law firm, triggered by a discovery production or trial prep deadline.

Biggest execution risk

Operational simplicity 4.7/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

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

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

0/18
Entry price
$399
Solo build
4 days
30d base revenue
$9,576
30d hackathon profit
$8,892
Section 1 of 8

Product opportunity and positioning

Target customer

Litigation paralegal or solo attorney at a 1-20 person US law firm, triggered by a discovery production or trial prep deadline.

Why now

The buying trigger is a filed date already on the firm calendar, the price sits under partner card-approval thresholds, and the output is deterministic so no legal review of AI text is required.

Problem

Assembling exhibits by hand in Acrobat causes misnumbered pages, broken bookmarks, missing index entries and last-minute rework before filing.

Solution

Upload PDFs, drag to order, set Bates prefix and start number, pick stamp position and bookmark depth, pay $399, and download one merged packet PDF plus a CSV manifest.

Differentiation · Acrobat ships the stamp and bookmark tools but not the workflow; ExhibitSmith is one form with a fixed output contract, and unlike AI editors it never rewrites document text.

1. Product opportunity and positioning

The buyer is a litigation paralegal or solo attorney at a 1-20 person US firm, working in the two weeks before a discovery production or a trial. The task is mechanical and unforgiving: merge 20-60 case PDFs, stamp sequential Bates numbers, bookmark every exhibit, and build an index whose page ranges match the printed numbers. They do it in Adobe Acrobat, and they redo it when a stamp lands sideways on a rotated page or a bookmark points one page off.

Acrobat ships the tools. It does not ship the workflow. That gap is the product.

ExhibitSmith is one form: upload the PDFs, drag them into order, set the Bates prefix and start number, choose stamp position and font size, pay $399, download a single packet PDF plus a CSV manifest. The output contract is fixed, so the paralegal knows exactly what comes back before running it.

The wedge is deliberately narrow. It does not rewrite document text, so there is no AI review step and no argument about altered content. It does not file anything and does not validate court rules. It performs the one deterministic job firms still assign to a person, at a price a partner approves on a card without procurement. The trigger, a filing date, is already on the firm calendar, so the first buyer can be emailed this week rather than nurtured for a quarter.

JEV scores this concept 6.3/10 in band C. Speed to first revenue (8.53 normalized) and solo build feasibility (7.78) are the strengths. Monetization (4.77) and operational simplicity (4.72) are the weaknesses, and this plan answers both: a $399 single charge with a repeat-packet path, and a stateless pipeline that deletes customer files after one hour.

Competitive reality: Acrobat, court-filing bundles and generic PDF utilities can all add sequence stamping. The defensible position is not the stamp, it is the packet contract: stamps plus bookmarks plus linked index plus CSV, produced in one pass with no post-fix. Every day the founder spends on repeat-packet speed and on trust statements is worth more than a new feature.

The market is unglamorous and reachable. Small litigation firms are listed in public state bar directories, publish staff emails on their own sites, and answer email from strangers when the message names their filing problem. No marketplace, no SEO ramp, no procurement cycle, no regulatory approval stands between the founder and the first $399.

Section 2 of 8

Smallest sellable MVP

A single web form that takes ordered PDFs plus Bates settings, charges $399 via Stripe Checkout, and returns one stamped, bookmarked, indexed packet PDF with a CSV manifest.

Must-have features

  • Multi-PDF upload with drag-to-order
  • Bates stamping: prefix, start number, position, font size
  • Auto-bookmark per source PDF from cleaned filename
  • Hyperlinked index page with page ranges
  • Merged packet download plus CSV manifest
  • Stripe Checkout one-time $399 with webhook unlock
  • 24-hour signed download links and 1-hour file deletion
  • Limits guard: 60 files, 2000 pages, 300 MB, encrypted PDF rejection

Explicitly out of scope

  • OCR or document review AI
  • E-filing or court integration
  • User accounts, teams or collaboration
  • Word/DOCX editing of any kind
  • Court-rule validation engine
  • LLM rewriting of document text
  • Phone support or a 24/7 SLA
  • Subscription billing

Demo flow (what the buyer sees)

  1. Open exhibitsmith.com and click Start a packet
  2. Drop 20 case PDFs and drag them into exhibit order
  3. Set prefix EX, start number 0001, bottom-right stamp, 10pt
  4. Choose bookmark depth of 1 and click Continue
  5. Pay $399 through Stripe Checkout
  6. Packet builds in under 90 seconds and download page appears
  7. Download packet.pdf, index.csv and manifest.csv; files auto-delete in one hour
Build plan

Technical implementation plan

Stack

Next.js 14 with TypeScriptTailwind CSSdnd-kit for drag-to-orderpdf-lib for merge, stamping, bookmarks and indexVercel Functions (Node runtime, 300s max duration)Cloudflare R2 with presigned uploadsStripe Checkout and webhookUpstash Redis for job state only, no document content

Architecture

The browser uploads PDFs straight to R2 using presigned URLs, so document bytes never sit in the app server. Only file keys, order and Bates settings go into a short-lived job record. Stripe Checkout is created before the build; the webhook flips the job to paid, which triggers a single Vercel Function that downloads the PDFs, merges them in order, computes stamp coordinates per page from MediaBox, CropBox and rotation, writes bookmarks, renders the index page with internal links, and streams one output PDF back to R2. The browser gets signed 24-hour download links. A scheduled job deletes all source and output objects after one hour.

Build steps

  1. Scaffold Next.js app, Tailwind and Vercel project on a staging URL
  2. Add R2 presigned upload with drag-to-order UI and job record
  3. Implement pdf-lib merge with continuous page numbering
  4. Compute per-page stamp position from MediaBox, CropBox and rotation
  5. Expose prefix, start number, position and font size in the settings form
  6. Generate outline bookmarks from cleaned filenames with depth control
  7. Render index page with exhibit name, page range and internal link destinations
  8. Emit CSV manifest and wire the output to a signed download link
  9. Add Stripe Checkout, webhook unlock and idempotent job execution
  10. Add limits guard, encrypted-PDF rejection and one-hour deletion cron
  11. Replay 10 real exhibit sets and fix coordinate defects

AI components

  • None required for v1; the pipeline is fully deterministic.
  • Optional and off by default: a small text-extraction step on the first page of each PDF to produce a human bookmark title instead of the filename.
Hardest technical risk: Stamp placement on rotated or cropped pages: if MediaBox origin, CropBox offset and page rotation are not applied per page, Bates numbers land outside the visible page and the packet is unusable.
Section 3 of 8

Pricing and monetization

Court Packet

Entry offer
$399 one-time

For Litigation paralegals and solo attorneys

  • One merged exhibit PDF
  • Sequential Bates numbering
  • Per-exhibit bookmarks
  • Hyperlinked index page
  • CSV manifest
  • 24-hour download, files deleted after one hour

Model: One-time $399 per court packet, paid by Stripe Checkout before the packet builds, with no subscription and no account required.

First revenue offer: Offer to assemble one exhibit packet free with no signup, quote the $399 price in the same email, then invoice the next packet.

Expected ACV: $399

Upsell path: Every buyer gets a reorder link that prefills the last Bates settings; repeat buyers can prepay a five-packet bundle at $1,595. Repeat packets and referrals, not new features, are the second revenue line.

Target customers
250
Revenue model
$99,750
Costs
$1,200
Profit model
$98,550
Section 4 of 8

First-customer acquisition

Primary channel

Cold email to litigation paralegals and office managers at 1-20 person US law firms sourced from public state bar directories.

Where to find them

  • State bar member directories filtered to litigation and small-firm practice areas
  • Firm websites with a staff or contact page listing paralegal emails
  • County bar association litigation section member lists
  • Public docket entries for firms filing exhibit-heavy motions
  • LinkedIn titles matching litigation paralegal at firms under 20 people
  • Paralegal association chapter forums and local LinkedIn groups

Exact outreach motions

  • Send a 60-word email offering to assemble one exhibit packet free, price stated in the same message
  • Follow up at 72 hours with a Stripe link and a 10% first-packet discount
  • Deliver the free packet within 24 hours and ask what almost stopped them
  • Email past buyers a reorder link when they mention the next filing date
  • Post the exhibit packet checklist in paralegal communities without pitching in the first reply

Message template

Subject: Can I assemble your next exhibit packet free?

Hi {first_name} - I build a tool that merges case PDFs and adds Bates numbers, bookmarks and a linked index in one pass. If you have an exhibit set going out this week, send me the PDFs and I will return the finished packet today, free, no signup. If it saves you the Acrobat afternoon, the next one is $399. Worth a try?
Week-one goal: Landing page live, MVP accepting payment, 100 verified firm contacts, 40 emails sent, first free packet 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 1Setup

Accounts and skeleton

  • Register exhibitsmith.com and point DNS at Vercel.
  • Create a Stripe account connected to TrustMRR.
  • Create the R2 bucket and Next.js repo with Tailwind.

Deliverable: Repo on a staging URL with Stripe test keys.

Day 2Upload

Multi-file intake

  • Build upload UI with drag-to-order using dnd-kit.
  • Presign R2 uploads and store order in a job record.
  • Enforce limits: 60 files, 2000 pages, 300 MB.

Deliverable: Working upload and reorder screen.

Day 3Stamping

Bates engine

  • Merge with pdf-lib and stamp sequential numbers.
  • Read page rotation and CropBox before placing text.
  • Expose prefix, start number, position and font size.

Deliverable: Merged, continuously stamped PDF download.

Day 4Structure

Bookmarks, index, manifest

  • Bookmark each source PDF by cleaned filename.
  • Generate the index page with page ranges and internal links.
  • Emit CSV manifest with exhibit, source file and page range.

Deliverable: Complete packet output matching the public sample.

Day 5PaymentMVP shipped

Ship the paid flow

  • Wire Stripe Checkout at $399 and a webhook that unlocks the job.
  • Issue 24-hour signed download links.
  • Add an error page with a manual rerun contact.

Deliverable: End-to-end paid packet; MVP live on day 5.

Day 6Hardening

Real-world PDFs

  • Run 10 real exhibit sets with mixed sizes, scans and rotated pages.
  • Fix every stamp misplacement found.
  • Reject encrypted PDFs with a clear message.

Deliverable: Test log with all defects closed.

Day 7Landing

Public site

  • Publish before-and-after sample packet and a 20-second recording.
  • Add FAQ covering retention and deletion.
  • Add Stripe Checkout and the pricing block.

Deliverable: Public site accepting payment.

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

200 firm contacts

  • Pull 200 small litigation firms from state bar directories.
  • Find paralegal or office manager emails on firm sites.
  • Log firm, contact, trigger type and source.

Deliverable: CSV of 200 verified contacts.

Day 9Outreach

First 40 emails

  • Send 40 free-packet offers from the warmed domain.
  • Track sends, opens and replies in one sheet.
  • Set a 72-hour follow-up reminder.

Deliverable: 40 sends logged.

Day 10Delivery

Free packet fulfilment

  • Send 50 more emails.
  • Run free packets for anyone who replies.
  • Ask each recipient what almost stopped them.

Deliverable: First five free packets delivered.

Day 11Follow-up

Convert and discount

  • Follow up the day-9 batch with a Stripe link and 10% discount.
  • Send 50 more emails.
  • Rewrite the subject line using reply language.

Deliverable: Follow-up sequence v2 live.

Day 12SaleFirst sale target

First paid packet

  • Close the first $399 packet.
  • Ask the buyer for two named referrals.
  • Record which message produced the sale.

Deliverable: First $399 collected.

Day 13Scale

Volume and lead magnet

  • Send 60 emails.
  • Expand the list to 400 contacts.
  • Publish a one-page exhibit packet checklist PDF.

Deliverable: List at 400 contacts, checklist live.

Day 14Review

Metrics pass

  • Compute reply rate, free-acceptance rate and paid conversion.
  • Cut the worst-performing subject line.
  • Decide whether to widen to solo attorneys.

Deliverable: Channel scorecard and decision note.

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

Eighty sends per day

  • Send 80 emails from a second warmed domain.
  • Add a trial-prep variant of the offer.
  • Answer every reply within 12 hours.

Deliverable: 80 sends with reply SLA met.

Day 16Repeat

One-click reorder

  • Add a reorder link that prefills last packet settings.
  • Email past buyers the reorder link.
  • Ask each for their next filing date.

Deliverable: Reorder flow live.

Day 17Friction

Saved presets

  • Persist Bates prefix and start number in the browser.
  • Add a page-count estimate before payment.
  • Ship the preset release.

Deliverable: Repeat packet takes under three minutes.

Day 18Proof

Testimonials

  • Collect two short written testimonials.
  • Add them to the landing page with firm size only.
  • Add a redacted sample packet.

Deliverable: Landing page carrying social proof.

Day 19Output

Index polish

  • Add index column options and a serif or sans choice.
  • Fix CSV column naming flagged by buyers.
  • Ship the release.

Deliverable: Index v2 shipped.

Day 20Wave two

Fresh firm segment

  • Send 100 emails to a new firm segment.
  • Expand the list to 700 contacts.
  • A/B test the free-versus-paid opening line.

Deliverable: 100 sends with A/B results logged.

Day 21Retention

Next packet

  • Email every buyer asking to prepay the next packet.
  • Offer the five-packet prepaid bundle at $1,595.
  • Record commitments.

Deliverable: Bundle offer sent to all buyers.

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

Trial-date segment

  • Send 100 emails to firms with trials inside 60 days.
  • Use the deadline-first subject line.
  • Expand the list to 1,000 contacts.

Deliverable: 100 sends to the deadline segment.

Day 23Support

Self-serve fixes

  • Publish a troubleshooting page for stamp and bookmark issues.
  • Add an in-app notice for encrypted or oversized PDFs.
  • Clear every open ticket.

Deliverable: Support under 15 minutes per packet.

Day 24Bundle

Prepaid packets

  • Ship the five-packet prepaid checkout at $1,595.
  • Add bundle terms to the FAQ.
  • Email the bundle to repliers who did not buy.

Deliverable: Bundle checkout live.

Day 25Community

Organic reach

  • Post the checklist in two paralegal LinkedIn groups and one chapter forum.
  • Answer questions without pitching in the first reply.
  • Log inbound leads.

Deliverable: Community posts live with inbound tracked.

Day 26Paid test

One sponsored slot

  • Buy one $150 paralegal newsletter sponsorship.
  • Use a dedicated landing URL with UTM tracking.
  • Set a five-day kill rule.

Deliverable: Sponsored slot live with tracked URL.

Day 27Polish

Guardrails

  • Add page-count and file-size estimation before checkout.
  • Warn when mixed page sizes need a stamp offset.
  • Ship the release.

Deliverable: Fewer failed packet builds.

Day 28Close

Final push

  • Send 150 emails to the remaining list.
  • Invoice anyone who asked for a packet and did not pay.
  • Offer the 10% discount one last time.

Deliverable: Final outreach complete.

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

Money check

  • Reconcile Stripe payouts against TrustMRR records.
  • Process refunds and log any chargebacks.
  • Confirm no payment predates launch.

Deliverable: Clean revenue ledger.

Day 30Wrap

Ship the results

  • Freeze features and capture final metrics.
  • Publish a results post comparing projection to actual.
  • Archive the outreach list and test logs.

Deliverable: Public results post published.

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

  • All figures are projections from stated assumptions, not verified revenue or existing customers.
  • Every scenario uses a flat $399 per-packet ARPU; prepaid bundle revenue is excluded.
  • Payment fees assume Stripe at 2.9% plus $0.30 per charge.
  • Conservative: 9 paid packets from roughly 1,450 targeted emails plus manual free-packet delivery.
  • Base: 24 paid packets including repeat packets from early buyers and two referrals.
  • Upside: 60 paid packets, helped by the $150 newsletter test and prepaid bundles.
  • Refunds: 0 conservative, 1 base, 2 upside.
  • Chargebacks: 0 conservative and base, 1 in upside.
  • Ad spend is $0 except the $150 sponsored newsletter test in the upside case.
  • Operating costs cover Vercel Pro, Cloudflare R2 storage and egress, domain, email tooling and job state.
  • Delivery cost per packet is estimated under $0.50, far below the $399 price.
  • Hackathon profit excludes hosting, domains, tooling and delivery cost; business profit deducts them.

Conservative

9 customers
$3,591
collected revenue · avg payment $399
Refunds
$0
Chargebacks
$0
Payment fees
$107
Paid marketing
$0
Hackathon profit
$3,484
Operating costs
$40
Business profit
$3,444

Base case

24 customers
$9,576
collected revenue · avg payment $399
Refunds
$399
Chargebacks
$0
Payment fees
$285
Paid marketing
$0
Hackathon profit
$8,892
Operating costs
$90
Business profit
$8,802

Optimistic

60 customers
$23,940
collected revenue · avg payment $399
Refunds
$798
Chargebacks
$399
Payment fees
$712
Paid marketing
$300
Hackathon profit
$21,731
Operating costs
$180
Business profit
$21,551

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$9,576
Payment fees (3.9%)
$373
Paid marketing
$0
Hackathon profit
$9,203
Business profit
$9,113

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 stated assumptions. They are not verified revenue, not existing customers and not a forecast of results.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold email deliverability and reply rates land far below plan.

Mitigation

Two warmed domains, plain-text 60-word emails, ramp from 40 to 150 sends per day, no attachments, reply-first offer.

Validation experiment

Send 80 emails across days 9 and 10 and count replies inside 72 hours.

Kill criteria

Fewer than 2 replies from 80 sends: switch to LinkedIn and paralegal association outreach before changing the product.

Risk 2Recipients accept a free packet but will not pay $399 for the next one.

Mitigation

Quote the price in the first email, invoice immediately after delivering the free packet, and ask what blocked them.

Validation experiment

Deliver 5 free packets, then request $399 for each follow-on packet within 7 days.

Kill criteria

Zero of five pay within 7 days: drop to $199 per packet or move to per-page pricing before scaling sends.

Risk 3Rotated, scanned or mixed-page-size PDFs produce misplaced stamps or broken bookmarks.

Mitigation

Per-page rotation and CropBox math, a 2,000-page cap, encrypted-PDF rejection, and a documented digital-native PDF limitation.

Validation experiment

Run 10 real exhibit sets pulled from public dockets and inspect output page by page.

Kill criteria

More than 3 of 10 sets still show visible stamp or bookmark defects after fixes: narrow the promise to digital-native PDFs and state it on the page.

Risk 4Firms refuse to upload case files to an unknown tool.

Mitigation

One-hour automatic deletion, no accounts, no retention statement, no training on customer files, and a manual delivery option for the free packet.

Validation experiment

Ask 10 recipients directly whether data retention is the blocking concern.

Kill criteria

Retention blocks more than half of interested firms: build a browser-only build mode before further outreach.

Risk 5The product is a one-off purchase with no repeat revenue.

Mitigation

Reorder links, saved Bates presets and the five-packet prepaid bundle at $1,595.

Validation experiment

Ask every buyer for their next filing date and track second packets inside 30 days.

Kill criteria

No buyer orders a second packet inside 30 days: keep acquisition-only unit economics and stop building retention features.

Risk 6Acrobat or a filing vendor bundles the same packet output.

Mitigation

Compete on the packet contract and turnaround speed, not on stamp features; keep the workflow to one form and one price.

Validation experiment

Ask 10 prospects what tool they used last time and whether they searched for an alternative.

Kill criteria

Prospects say a tool they already own does this well enough: reposition to conference-ready binders or move on.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register exhibitsmith.com and point DNS at Vercel.
  • Create the Stripe account connected to TrustMRR and copy test keys.
  • Create the Cloudflare R2 bucket.

Output: Domain live, Stripe test account, R2 bucket, empty deployed app.

Hours 3-5

  • Scaffold Next.js with Tailwind on a staging URL.
  • Build the upload screen with dnd-kit drag-to-order.
  • Wire presigned R2 uploads.

Output: Upload and reorder screen reachable on staging.

Hours 6-9

  • Implement pdf-lib merge with continuous page numbering.
  • Read MediaBox, CropBox and rotation per page before stamping.
  • Stamp prefix and start number bottom-right at 10pt.

Output: Stamped merged PDF produced from three test files.

Hours 10-12

  • Write outline bookmarks from cleaned filenames.
  • Render the index page with page ranges and internal links.
  • Emit the CSV manifest.

Output: Complete packet output from the sample set.

Hours 13-16

  • Wire Stripe Checkout at $399 and the unlock webhook.
  • Add signed 24-hour download links and the one-hour delete cron.
  • Run the paid flow end to end in test mode.

Output: Paid flow verified in test mode with a captured sample packet.

Hours 17-24

  • Draft landing copy and the FAQ retention statement.
  • Pull the first 100 firms from one state bar directory and collect contact emails.
  • Write and stage the first outreach email.

Output: Landing page draft, 100-contact list, first email ready to send on day 9.

Complete report

Full 30-day launch report

Read the full generated report

ExhibitSmith Court Packets: 30-Day Launch Report

Concept version 1. JEV weighted score 6.3/10, band C. One founder, 30 days, November 16 to December 15, 2026.

1. Product opportunity and positioning

The buyer is a litigation paralegal or solo attorney at a 1-20 person US firm, working the two weeks before a discovery production or a trial. Their task is mechanical and unforgiving: merge 20-60 case PDFs, stamp sequential Bates numbers, bookmark every exhibit, and build an index whose page ranges match the printed numbers. They do it in Adobe Acrobat, and they redo it when a stamp lands sideways on a rotated page or a bookmark points one page off.

Acrobat ships the tools. It does not ship the workflow. That gap is the product.

ExhibitSmith is one form: upload the PDFs, drag them into order, set the Bates prefix and start number, choose stamp position and font size, pay $399, download one packet PDF plus a CSV manifest. The output contract is fixed, so the paralegal knows what comes back before running it.

The wedge is deliberately narrow. It never rewrites document text, so there is no AI review step and no argument about altered content. It files nothing and validates no court rules. It performs the one deterministic job firms still hand to a person, at a price a partner approves on a card without procurement. The trigger, a filing date, is already on the firm calendar.

JEV gives this concept 6.3/10. Speed to first revenue (8.53 normalized) and solo build feasibility (7.78) are the strengths. Monetization (4.77) and operational simplicity (4.72) are the weaknesses. This plan answers both with a $399 single charge plus a repeat-packet path, and a stateless pipeline that deletes customer files after one hour.

2. Smallest sellable MVP

Five capabilities and nothing else: multi-PDF upload with drag-to-order; Bates stamping with configurable prefix, start number, position and font size; automatic bookmarks from cleaned filenames; a hyperlinked index page with page ranges; a merged download plus CSV manifest behind Stripe Checkout.

Out of scope on purpose: OCR, document review, e-filing, accounts, teams, DOCX editing, court-rule validation, and any model that touches document text. Each of those adds a review step or a compliance question that delays the first $399. The MVP is buildable and shippable by day 5.

3. Technical implementation plan

Next.js on Vercel, Tailwind, dnd-kit, pdf-lib, Cloudflare R2, Stripe Checkout, and Upstash Redis for job state only. The browser uploads PDFs directly to R2 through presigned URLs, so document bytes never transit the app server. Order and Bates settings live in a short-lived job record. Checkout is created before the build; the webhook flips the job to paid, which triggers one Vercel Function that merges, stamps, bookmarks, renders the index and streams the output back to R2. A cron deletes all objects after one hour.

The single hardest risk is stamp placement on rotated or cropped pages. If MediaBox origin, CropBox offset and page rotation are not applied per page, Bates numbers land outside the visible page and the packet is unusable. This gets tested on day 6 against ten real exhibit sets before volume outreach starts.

No AI is required in v1. The one optional model call, normalizing filenames into human bookmark titles, stays off by default so the pipeline remains deterministic.

4. Pricing and monetization

One price: $399 per court packet, paid by Stripe Checkout before the build, no subscription, no account. The price sits under partner card-approval thresholds and above any delivery cost, which stays under $0.50 per packet. The first-revenue offer is a free packet plus the $399 price stated in the same email. After purchase, every buyer gets a reorder link that prefills the last Bates settings, and serious repeat buyers can prepay five packets for $1,595. Repeat packets and referrals are the second revenue line; the plan does not depend on a subscription that a small firm will not sign in 30 days.

5. First-customer acquisition

Cold email is the only acquisition channel. The founder builds a list from public state bar directories and firm staff pages, targeting litigation paralegals and office managers at 1-20 person firms. The message is 60 words, offers to assemble one exhibit packet free with no signup, and quotes the $399 price in the same breath. Replies get a packet within 24 hours, then a follow-up at 72 hours with a Stripe link and a 10% first-packet discount. Volume ramps from 40 sends on day 9 to 150 on day 28, roughly 1,450 targeted emails, with no paid marketing until the single $150 newsletter test on day 26.

6. 30-day execution roadmap

Week 1 (days 1-7) is build and ship: accounts, upload, Bates engine, bookmarks and index, Stripe, then hardening on ten real PDF sets, then a public landing page. Day 5 is the MVP deadline.

Week 2 (days 8-14) is the first outreach wave: 200 contacts, 40 to 60 sends per day, manual free-packet delivery, follow-ups, and the first paid packet targeted for day 12. Day 14 is a metrics pass that cuts the worst subject line.

Week 3 (days 15-21) is volume and repeatability: 80 to 100 sends per day, saved presets, reorder links, two testimonials, and the five-packet bundle offer to every existing buyer.

Week 4 (days 22-28) is the deadline segment, self-serve support, community posts, one sponsored newsletter test at $150, output guardrails, and a final 150-email push.

Days 29-30 are reconciliation and wrap: reconcile Stripe against TrustMRR, log refunds and chargebacks, confirm no payment predates launch, freeze features and publish a results post.

7. Revenue and profit scenarios

All three cases are projections from the assumptions listed in the report data. They are not verified revenue and not existing customers.

Conservative assumes 9 paid packets from about 1,450 emails: $3,591 gross, $107 in payment fees, no refunds, no ads, $40 operating cost. Base assumes 24 packets including repeats and two referrals: $9,576 gross, one $399 refund, $285 in payment fees, $90 operating cost. Upside assumes 60 packets helped by the newsletter test and bundles: $23,940 gross, two refunds, one chargeback, $712 in payment fees, $300 of ad spend, $180 operating cost.

The point of the model is the spread. Even the conservative case clears hackathon profit after fees because delivery cost is under $0.50 per packet. The base case is the number to plan against.

8. Risks and validation experiments

Deliverability and reply rate: test 80 emails over two days and require at least 2 replies before scaling.

Willingness to pay: deliver five free packets and ask for $399 within seven days; if none convert, reprice before sending more email.

Format edge cases: ten real exhibit sets from public dockets; if more than three still fail after fixes, narrow the promise to digital-native PDFs.

Trust and data handling: one-hour deletion and a no-retention statement, validated by asking ten recipients whether retention is the blocker.

Repeat purchase: track second packets inside 30 days; if none, keep acquisition-only economics and stop building retention features.

Bundling by incumbents: ask ten prospects what they used last time; if an owned tool already does the job, reposition rather than add features.

9. First 24-hour action plan

Hours 1-2: domain, Stripe connected to TrustMRR, R2 bucket. Hours 3-5: Next.js scaffold and the drag-to-order upload screen. Hours 6-9: pdf-lib merge and per-page stamp math with rotation handling. Hours 10-12: bookmarks, index page and CSV manifest. Hours 13-16: Stripe Checkout, unlock webhook, signed links, one-hour delete cron, tested end to end. Hours 17-24: landing copy, FAQ retention statement, 100 contacts from a state bar directory, and the first outreach email staged to send on day 9.

Every figure in this report is a projection. The only number that will matter on December 15 is what Stripe actually collected.

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 →