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

SampleShip

Turns a sample spreadsheet into a CRO-ready shipment manifest, chain-of-custody PDF, and barcode label sheet in two 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.10/10
MVP build (solo)
4 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
LinkedIn direct message to Lab Operations Managers and Senior Research Associates at 10-50 person Series A biotech companies in the US.
Who pays

Lab Operations Manager or Senior Research Associate at a 10-50 person Series A biotech shipping samples to a CRO for the first time.

Biggest execution risk

Market demand 4.4/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

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; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.6/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
4 days
30d base revenue
$2,100
30d hackathon profit
$1,906
Section 1 of 8

Product opportunity and positioning

Target customer

Lab Operations Manager or Senior Research Associate at a 10-50 person Series A biotech shipping samples to a CRO for the first time.

Why now

The output is a document emailed to a third party, so it needs no LIMS integration, no IT review, and no procurement cycle; a lab ops manager can buy it with a card and use it the same afternoon.

Problem

Building shipment manifests, chain-of-custody forms, and barcode labels by hand across Excel, Word, and a barcode app, where a missing field or mismatched ID gets the shipment rejected by the CRO and delays the study by weeks.

Solution

Upload a CSV/XLSX, map columns, pass required-field validation, then download one PDF packet containing the manifest, a chain-of-custody form with signature blocks, and a printable Code128 label sheet, plus a CRO-compatible manifest CSV.

Differentiation · It is a single-output document tool, not an ELN or lab platform. Benchling-class systems require adoption across the lab; SampleShip only fixes the outbound CRO shipment artifact that already has a deadline attached.

1. Product opportunity and positioning

SampleShip does one job: it takes a sample spreadsheet and returns a shipment packet a CRO will accept, consisting of a manifest PDF, a chain-of-custody form with signature blocks, a printable Code128 label sheet, and a CRO-compatible CSV.

The buyer is the Lab Operations Manager or Senior Research Associate at a 10-50 person Series A biotech shipping samples to a CRO for the first time. The trigger event is concrete: a study start date is booked, the CRO emails the required manifest fields, and the lab ops person now has to reconstruct a packet from a spreadsheet, a Word template someone made years ago, and a barcode app. The failure mode is expensive and visible. A missing storage condition, a duplicated sample ID, or a label that will not scan at the CRO dock turns into a rejected shipment and weeks of delay.

That is the whole case for a $99-$499 one-time purchase. The buyer does not need a platform decision, a security review, or a procurement cycle. They need the packet to be correct before the courier arrives.

Why this is sellable in this 30-day window: there is no integration to sell against. No LIMS migration, no data migration, no admin console to learn. The buyer uploads a CSV, downloads a PDF, forwards it to the CRO, and the product has done its job within hours of purchase. Delivery cost is a PDF render and a barcode encode, which keeps operating cost near zero.

Differentiation matters here because the obvious comparison is wrong. SampleShip is not an ELN, not a notebook replacement, not an inventory system, and not a Benchling competitor. Benchling-class platforms solve sample tracking inside a system a lab has to adopt across teams. SampleShip solves the outbound artifact that leaves the building. A free spreadsheet template can approximate the manifest but cannot validate required fields, assign unique scannable barcodes, or produce signature blocks, and that gap is the paid wedge.

The honest read of the JEV score (6.1/10, band C) is that speed to first revenue and solo build feasibility are strong (8.6 and 7.8 normalized) while market demand and reachable customers are weak (4.4 and 5.5). Translation: the product will be easy to build and easy to deliver, and the risk is entirely in whether enough lab ops managers can be reached and whether they ship often enough to pay $299 or $499 rather than $99 once. The 30-day plan therefore spends 25 of its 30 days on distribution, not on features. The narrow wedge is deliberate: one artifact, one buyer, one channel, one price ladder.

Section 2 of 8

Smallest sellable MVP

A paid single-page tool that accepts a CSV or XLSX, maps columns, validates required shipment fields, and returns one downloadable PDF packet (manifest + chain-of-custody with signature blocks + Code128 label sheet) plus a CRO-compatible manifest CSV.

Must-have features

  • CSV/XLSX upload with drag-and-drop and sheet selection
  • Column mapping UI with saved mapping per project
  • Required-field validation with row-level error list (sample ID, volume, storage condition, container type, ship date)
  • Duplicate sample ID detection and blocking
  • Code128 barcode generation rendered into a printable label sheet PDF
  • Chain-of-custody PDF with shipment summary, storage conditions, and signature blocks
  • CRO-compatible manifest CSV export
  • Stripe Checkout with one-time payment and a tokenized download link
  • Regenerate packet from a stored project without re-uploading

Explicitly out of scope

  • No LIMS or ELN integration
  • No real-time shipment or courier tracking
  • No inventory database or freezer map
  • No multi-user roles, approvals, or audit trail
  • No 21 CFR Part 11 or regulatory validation claims
  • No custom per-CRO template builder in v1 (manual template matching only)
  • No mobile app

Demo flow (what the buyer sees)

  1. Buyer uploads a redacted sample spreadsheet
  2. SampleShip infers columns and shows a mapping screen
  3. Buyer confirms storage condition and ship date once for the shipment
  4. Validation flags missing or duplicated sample IDs with row numbers
  5. Buyer fixes the sheet and re-uploads, or edits inline
  6. SampleShip renders the packet: manifest, chain-of-custody, label sheet
  7. Buyer pays via Stripe Checkout and lands on a tokenized download page
  8. Buyer downloads the PDF packet and the CRO CSV and emails them to the CRO
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres for projects and packet recordsSupabase Storage for uploaded sheets and generated PDFsStripe Checkout and webhookpdf-lib for PDF compositionbwip-js for Code128 barcode renderingSheetJS (xlsx) for CSV/XLSX parsingResend for transactional email with download linksVercel Cron for expiry of unpaid uploads

Architecture

A single Next.js app on Vercel serves the upload wizard, the column mapper, and the tokenized download page. Uploads land in Supabase Storage and a job row is written to Postgres. Validation runs server-side on the parsed rows and returns a structured error list. On payment, the Stripe webhook flips the packet row to paid and Resend sends the download link. PDF generation is a serverless route that composes three documents with pdf-lib: the manifest table, the chain-of-custody page with signature blocks, and the label sheet where each cell is a bwip-js Code128 image. Generated files are cached in Supabase Storage so regeneration is a lookup, not a re-render.

Build steps

  1. Scaffold Next.js + Supabase, define tables: projects, uploads, packets, payments
  2. Build CSV/XLSX upload and SheetJS parse with header inference
  3. Build column mapping UI and persist mapping JSON per project
  4. Implement validation rules and row-level error rendering
  5. Generate manifest PDF with pdf-lib table layout
  6. Generate chain-of-custody PDF with shipment summary and signature blocks
  7. Generate label sheet with bwip-js Code128, fixed 3x10 grid on Letter
  8. Add CRO-compatible CSV export
  9. Wire Stripe Checkout, webhook, tokenized download route, Resend email
  10. Deploy to Vercel, run end-to-end test with three synthetic spreadsheets, set up error logging

AI components

  • Optional LLM call to infer and pre-fill column mappings from header names and two sample rows; falls back to manual mapping if confidence is low
Hardest technical risk: Label sheet print alignment: barcode density and margins must survive a standard label stock and a normal office printer, or the CRO scanner rejects the labels and the product's core promise fails.
Section 3 of 8

Pricing and monetization

Single Shipment

Entry offer
$99 one-time

For Lab ops manager with one urgent CRO shipment

  • 1 CRO-ready packet
  • Label sheet PDF
  • Chain-of-custody PDF
  • Manifest CSV

Lab Pack

$299 one-time

For Small lab shipping about five times in a month

  • 5 CRO-ready packets
  • Barcode label sheets
  • Manifest CSV exports
  • Priority email support

30-Day Unlimited

$499 one-time

For Series A biotech with recurring CRO shipments

  • Unlimited packets for 30 days
  • Priority email support
  • CRO CSV template matching
  • Regeneration of any prior packet

Model: Three one-time tiers sized to shipment frequency, with a path to a higher-value 30-day unlimited pass for labs shipping repeatedly.

First revenue offer: Send a free packet built from their redacted spreadsheet, then offer the $99 Single Shipment tier with a one-click Stripe link; quote $499 only if they mention recurring shipments.

Expected ACV: $175

Upsell path: Start every buyer at $99 to remove friction, then convert repeat shippers to the $299 Lab Pack at packet two and to $499 30-Day Unlimited once they have shipped three times in a month.

Target customers
100
Revenue model
$49,900
Costs
$1,500
Profit model
$48,400
Section 4 of 8

First-customer acquisition

Primary channel

LinkedIn direct message to Lab Operations Managers and Senior Research Associates at 10-50 person Series A biotech companies in the US.

Where to find them

  • LinkedIn Sales Navigator search: title contains 'Lab Operations' or 'Lab Manager', company size 11-50, industry Biotechnology, US
  • LinkedIn search for 'Senior Research Associate' at companies with 'Series A' in recent funding posts
  • People who posted on LinkedIn about shipping samples, CRO onboarding, or sample logistics in the last 90 days
  • Authors of public protocols and supplementary methods sections listing CRO sample transfer
  • Attendee lists and speaker pages for small biotech ops meetups
  • Referrals requested from every free-packet recipient

Exact outreach motions

  • Connection request with no pitch, then a two-sentence DM referencing their lab type
  • Free-packet offer: they send a redacted spreadsheet, you return a finished PDF within 12 hours
  • Day-3 follow-up with a one-page sample packet attached, no ask
  • Day-7 follow-up with the $99 checkout link and a one-line guarantee: regenerate free if the CRO rejects a field
  • Ask every free-packet recipient for one intro to another lab ops manager
  • Post a public before/after of a messy spreadsheet to packet on LinkedIn twice a week

Message template

Hi [Name] — I built a small tool that turns a sample spreadsheet into a CRO-ready packet: manifest, chain-of-custody with signature blocks, and printable barcode labels, in about two minutes. If you have a shipment coming up, send me a redacted copy of your sheet and I'll build the packet free so you can check it against your CRO's requirements. No call needed.
Week-one goal: 150 qualified LinkedIn profiles identified, 60 connection requests sent, 25 conversations opened, 8 redacted spreadsheets received, 8 free packets delivered.
Section 5 of 8

30-day execution roadmap

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

Data model and upload path

  • Scaffold Next.js on Vercel with Supabase project.
  • Create projects, uploads, packets, payments tables.
  • Build CSV/XLSX upload with SheetJS parsing and header inference.

Deliverable: A deployed page that accepts a spreadsheet and shows parsed rows.

Day 2Validation

Column mapping and required fields

  • Build column mapping UI with persisted mapping JSON.
  • Implement required-field and duplicate-ID validation with row numbers.
  • Render an error list the user can act on.

Deliverable: Validation screen that blocks bad sheets and explains why.

Day 3Documents

Manifest, chain-of-custody, labels

  • Compose manifest PDF with pdf-lib.
  • Add chain-of-custody page with storage conditions and signature blocks.
  • Render Code128 label sheet with bwip-js on a 3x10 Letter grid.
  • Add CRO-compatible manifest CSV export.

Deliverable: Full PDF packet and CSV generated from one upload.

Day 4Payments

Checkout and delivery

  • Wire Stripe Checkout for the three tiers.
  • Add webhook that marks packets paid and mints download tokens.
  • Send download email via Resend.
  • Build tokenized download page with regeneration.

Deliverable: End-to-end paid flow working in Stripe test mode, then live mode.

Day 5MVP shipMVP shipped

Deploy and harden

  • Deploy to production domain and enable TrustMRR-connected Stripe account.
  • Run three synthetic spreadsheets end to end, including a bad one.
  • Print a label sheet on real label stock and scan every barcode.
  • Add error logging and a support email.

Deliverable: Live product accepting real payments. MVP deadline met.

Day 6Prospecting

Build the list

  • Build a 150-row LinkedIn list of Lab Operations Managers at 10-50 person US biotech companies.
  • Record company, title, recent post, and a personalization line per row.
  • Draft the two-message DM sequence and the free-packet offer.

Deliverable: 150-row prospect sheet with personalization notes.

Day 7Proof

Landing page and sample packet

  • Write landing page: one promise, the packet contents, three prices, no hype.
  • Generate a clearly labeled sample packet from synthetic data and embed it.
  • Add a free-packet request form that captures email and shipment frequency.

Deliverable: Public landing page with downloadable sample packet.

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

First 30 touches

  • Send 30 connection requests with no pitch.
  • Send the free-packet DM to anyone who accepts.
  • Post the launch announcement on LinkedIn with the sample packet image.

Deliverable: 30 prospects contacted, first inbound replies logged.

Day 9Outreach

Volume and replies

  • Send 25 more connection requests.
  • Reply to all inbound within two hours.
  • Request the first three redacted spreadsheets.

Deliverable: 55 prospects contacted, 3 spreadsheets requested.

Day 10Delivery

Free packets to build proof

  • Manually build and return every free packet within 12 hours.
  • Log every validation error the tool catches on real sheets.
  • Patch the top two validation gaps.

Deliverable: 3-8 free packets delivered and 2 fixes shipped.

Day 11Follow-up

Convert free-packet recipients

  • Send day-3 follow-ups with the sample packet attached.
  • Send the $99 checkout link to warm recipients.
  • Ask each recipient for one intro.

Deliverable: Checkout links sent to every free-packet recipient.

Day 12First revenueFirst sale target

Close the first sale

  • Offer a 48-hour $99 price to the two warmest prospects.
  • Personally walk one buyer through checkout on a screen share if needed.
  • Record exactly what objection was raised before payment.

Deliverable: First paying customer and a written objection log. first-sale target day.

Day 13Iterate

Remove the top objection

  • Ship the single change that killed the most deals.
  • Add a promise on the checkout page about free regeneration.
  • Update the sample packet to mirror the buyer's real CRO format.

Deliverable: Updated product and a revised checkout page.

Day 14Review

Week two numbers

  • Count contacted, replied, spreadsheets received, packets delivered, paid.
  • Kill the worst-performing message angle.
  • Write the week-three outreach target.

Deliverable: One-page funnel scorecard with conversion rates.

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

Double volume

  • Send 40 new connection requests using the winning angle.
  • Post a second LinkedIn before/after of a messy sheet to packet.
  • Follow up with every non-responder from week two once.

Deliverable: 40 new prospects and one public post live.

Day 16Upsell

Move $99 buyers up

  • Offer Lab Pack $299 to any buyer with more than one shipment booked.
  • Add CRO template matching as a manual service inside 30-Day Unlimited.
  • Ask the first buyer for a one-line testimonial about the packet.

Deliverable: At least one upsell offer sent; testimonial or refusal recorded.

Day 17Reach

Adjacent sources

  • Contact five people who posted about CRO onboarding or sample logistics.
  • Join two small biotech ops communities and answer logistics questions.
  • Request referrals from all delivered free packets.

Deliverable: 5 warm inbound conversations from non-outbound sources.

Day 18Delivery quality

Make the packet CRO-proof

  • Collect the required-field list from three different CROs via buyers.
  • Add a per-CRO validation preset for the two most common formats.
  • Print and scan-test the label sheet again.

Deliverable: Two CRO presets live and verified print output.

Day 19Outreach

Second batch

  • Send 40 more connection requests.
  • Send free-packet DMs to all new accepts.
  • Follow up on every unpaid checkout link once.

Deliverable: 80 prospects contacted in week three.

Day 20Proof

Public case artifact

  • Publish a five-minute screen recording of sheet to packet.
  • Add it to the landing page and the DM follow-up.
  • Ask two buyers whether the CRO accepted the packet unchanged.

Deliverable: Demo video live; CRO acceptance answers recorded.

Day 21Review

Week three numbers

  • Update the funnel scorecard.
  • Compute revenue and cost to date against scenarios.
  • Decide whether to keep $99 as the entry price or raise it.

Deliverable: Mid-point decision memo with pricing verdict.

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

Highest-intent segment

  • Re-message every prospect who received a free packet but did not buy.
  • Offer the $499 30-Day Unlimited only to buyers with a second shipment.
  • Prioritize companies that mentioned a study start date in December.

Deliverable: Re-engagement pass sent to the full warm list.

Day 23Push

New volume

  • Send 40 fresh connection requests to a new title slice.
  • Post the third before/after on LinkedIn.
  • Reply to all inbound same day.

Deliverable: 40 new prospects, one post, zero unanswered replies.

Day 24Product

Reduce manual work

  • Automate CRO template matching for the two most requested formats.
  • Add one-click regeneration from the download page.
  • Reduce packet render time to under 15 seconds.

Deliverable: Faster packet generation and less manual per-order work.

Day 25Outreach

Referral engine

  • Ask every paying customer for one intro.
  • Send a short referral request to the free-packet list.
  • Follow up on all open checkout links a final time.

Deliverable: At least five referral asks sent with names.

Day 26Revenue

Close the backlog

  • Direct-message everyone with an abandoned checkout.
  • Offer a same-day packet build to remove the time objection.
  • Confirm every payment landed in the TrustMRR-connected Stripe account.

Deliverable: Backlog cleared and payment reconciliation done.

Day 27Proof

De-risk the offer

  • Publish the free-regeneration policy on the checkout page.
  • Add a one-page FAQ covering label stock, CRO formats, and file types.
  • Ask two buyers for a public one-liner.

Deliverable: FAQ and guarantee live; buyer quotes collected or declined.

Day 28Final outreach

Last volume push

  • Send 50 connection requests with the highest-performing angle.
  • Post a final LinkedIn call for December shipments.
  • Follow up with every warm lead one last time.

Deliverable: 50 new prospects and a final public post.

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

Close everything open

  • Call or message every open lead with a deadline-aware offer.
  • Push the $499 tier to anyone with a December study start.
  • Fix the last blocking support ticket.

Deliverable: All open leads contacted; no unresolved blockers.

Day 30Close

Final reconciliation

  • Reconcile Stripe payouts, refunds, and fees against the profit formula.
  • Confirm no customers or payments predate the launch window.
  • Write a one-page post-mortem: what converted, what did not, what ships next.

Deliverable: Reconciled profit figure and post-mortem.

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.
  • Blended ARPU is a mix of the $99 Single Shipment, $299 Lab Pack, and $499 30-Day Unlimited tiers; Conservative assumes mostly $99 sales, Upside assumes a higher share of $299+.
  • Payment processing is modeled at roughly 4.5% of collected revenue, assuming Stripe with a mix of domestic cards and one or two international cards plus fixed per-transaction fees.
  • ad_spend_usd is paid marketing only. Conservative and Base assume pure organic LinkedIn outreach, so $0. Upside assumes $250 of sponsored LinkedIn posts.
  • Refunds are modeled as one refunded packet in Base and one refunded Lab Pack in Upside, triggered by a CRO format the buyer could not use.
  • Chargebacks are $0 in all scenarios; buyers are identified individuals paying by card for a downloadable document.
  • operating_costs_usd covers Vercel, Supabase, Supabase Storage, Resend, domain, and any LLM calls for column inference; it scales with packet volume.
  • Hosting and delivery costs are excluded from hackathon profit by rule but included in business profit.
  • No customer, partnership, or revenue figure in this report is verified or existing.
  • The 30-day window is Mon 16 Nov 2026 13:00 UTC to Wed 16 Dec 2026 13:00 UTC; only payments inside it count.

Conservative

4 customers
$596
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$27
Paid marketing
$0
Hackathon profit
$569
Operating costs
$45
Business profit
$524

Base case

12 customers
$2,100
collected revenue · avg payment $175
Refunds
$99
Chargebacks
$0
Payment fees
$95
Paid marketing
$0
Hackathon profit
$1,906
Operating costs
$90
Business profit
$1,816

Optimistic

30 customers
$6,600
collected revenue · avg payment $220
Refunds
$299
Chargebacks
$0
Payment fees
$297
Paid marketing
$250
Hackathon profit
$5,754
Operating costs
$180
Business profit
$5,574

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,052

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 stated assumptions. They are not verified revenue, existing customers, or real traction. Actual results depend on outreach conversion and CRO format acceptance.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold LinkedIn outreach converts below 1%, so even 12 sales is unreachable.

Mitigation

Lead with a free finished packet built from the buyer's own redacted sheet, so the first ask is not a purchase; track reply rate daily and switch the message angle the moment it drops below 10%.

Validation experiment

Send 30 connection requests and 30 free-packet DMs on days 8-9 and count replies and spreadsheets received by day 11.

Kill criteria

If fewer than 3 of 60 contacted prospects reply with a spreadsheet by day 14, stop scaling outreach and switch to referral-only from any warm contacts.

Risk 2CROs require manifest formats that vary by provider, so the generated packet gets rejected and refunds follow.

Mitigation

Ship two per-CRO validation presets by day 18 built from buyers' actual CRO requirement emails, and publish a free-regeneration promise on the checkout page.

Validation experiment

Ask every free-packet recipient to confirm their CRO accepted the packet unchanged, and collect the required-field list from three CROs.

Kill criteria

If two buyers report the packet was rejected for a field the tool could not represent, add the field within 48 hours or drop that CRO format from the pitch.

Risk 3Buyers see this as a one-time need and never pay $299 or $499, collapsing ARPU toward $99.

Mitigation

Price the entry tier at $99 to remove friction, then offer the Lab Pack only after a second shipment is mentioned; measure repeat purchase intent directly in the DM.

Validation experiment

Ask all free-packet recipients one question: how many CRO shipments are you sending in the next 30 days.

Kill criteria

If fewer than 20% of responders report two or more shipments in 30 days, retire the $499 tier and focus on volume of $99 and $299 sales.

Risk 4A free spreadsheet template or a barcode app undercuts the paid product.

Mitigation

Sell the validated packet and the signature-block form, not the barcode image; the differentiation is field validation and a single downloadable artifact.

Validation experiment

Include a line in the DM asking what they use today for manifests and labels, and tally the answers.

Kill criteria

If most prospects say their existing template is accepted by their CRO without edits, retreat to the $99 tier and a narrower per-CRO preset pitch.

Risk 5Solo delivery load: free packets built manually in week two consume build and sales time.

Mitigation

Automate the two most requested CRO formats by day 24 and cap free packets at eight per week during the contest.

Validation experiment

Log minutes spent per free packet for the first five packets.

Kill criteria

If a free packet takes more than 30 minutes after the fifth one, cut the free offer to a sample packet only.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Vercel project and Supabase instance.
  • Define projects, uploads, packets, payments tables.
  • Buy the domain and point it at Vercel.

Output: Deployed skeleton app with a reachable URL and a live database.

Hours 3-5

  • Build CSV/XLSX upload with SheetJS parsing.
  • Implement header inference and show parsed rows in a table.
  • Commit and deploy.

Output: Working upload and parse screen on production.

Hours 6-8

  • Build the column mapping UI and persist mapping per project.
  • Implement required-field and duplicate-ID validation with row-level errors.
  • Test with one deliberately broken spreadsheet.

Output: Validation screen that explains exactly what is wrong and where.

Hours 9-11

  • Compose the manifest PDF with pdf-lib.
  • Add the chain-of-custody page with storage conditions and signature blocks.
  • Render a Code128 label sheet with bwip-js.

Output: A downloadable PDF packet generated from the test spreadsheet.

Hours 12-14

  • Wire Stripe Checkout for the $99 tier only.
  • Add webhook and tokenized download link.
  • Create a 25-row LinkedIn prospect list to warm up for day 8.

Output: First payable flow in Stripe test mode and a starter prospect list.

Complete report

Full 30-day launch report

Read the full generated report

SampleShip — 30-Day Ship or Die Report

Product: SampleShip, concept version 1. JEV weighted score 6.1/10 (61/100, band C, confidence 0.75). Contest window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. Solo founder. No funding, no team, no existing customers.

1. Product opportunity and positioning

SampleShip does one job: it takes a sample spreadsheet and returns a shipment packet a CRO will accept — a manifest PDF, a chain-of-custody form with signature blocks, a printable Code128 label sheet, and a CRO-compatible CSV.

The buyer is the Lab Operations Manager or Senior Research Associate at a 10-50 person Series A biotech shipping samples to a CRO for the first time. The trigger is concrete: a study start date is booked, the CRO emails the required manifest fields, and the lab ops person reconstructs a packet from a spreadsheet, an old Word template, and a barcode app. The failure mode is a rejected shipment and weeks of delay. That is the case for a $99-$499 one-time purchase with no procurement cycle.

The JEV read is the plan's spine. Speed to first revenue (8.6 normalized) and solo build feasibility (7.8) are strong. Market demand (4.4) and reachable customers (5.5) are weak. So the build takes four days and the remaining twenty-six days go to distribution. That is not a slogan; it is why days 6-30 contain no new architecture and why day 22 exists purely for re-engagement.

Differentiation: SampleShip is not an ELN, not a notebook replacement, not an inventory system, and not a Benchling competitor. Benchling-class platforms require a lab to adopt a system. SampleShip fixes the outbound artifact that already leaves the building. A spreadsheet template approximates the manifest but cannot validate required fields, assign unique scannable barcodes, or produce signature blocks.

2. Smallest sellable MVP

The sellable unit is one paid packet. Upload a CSV or XLSX, map columns, pass validation, pay $99, download a PDF packet and a CRO CSV. The download page must be able to regenerate the packet without a re-upload, because that supports the free-regeneration promise that removes the buyer's biggest fear.

Out of scope by design: no LIMS integration, no courier tracking, no freezer mapping, no multi-user roles, no audit trail, no 21 CFR Part 11 claims, no custom CRO template builder, no mobile app. Every one of these would delay day 5 without improving day 12.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres and Storage, Stripe Checkout, pdf-lib, bwip-js, SheetJS, Resend. Uploads land in Supabase Storage, a packet row is written to Postgres, validation runs server-side and returns a row-level error list. The Stripe webhook marks the packet paid and Resend sends a tokenized download link. PDF generation composes three documents with pdf-lib; each label cell is a bwip-js Code128 image on a fixed 3x10 Letter grid.

The hardest risk is print alignment. Barcodes must survive standard label stock and an office printer, or the CRO scanner rejects the labels and the product's core promise dies. Day 5 explicitly includes printing and scanning a real label sheet. An optional LLM call only pre-fills column mappings from header names and two sample rows; if confidence is low, the user maps manually. Nothing else in the product depends on a model, which keeps delivery cost near zero.

4. Pricing and monetization

Three one-time tiers: Single Shipment $99, Lab Pack $299 (five packets), 30-Day Unlimited $499. The entry tier is deliberately low because the first sale matters more than the first margin. The $499 tier only survives if the validation experiments show repeat shippers; day 21 is the decision point.

Expected ARPU in the base projection is $175, a blend weighted toward $99 with some $299 sales. Nothing above $499 is offered inside the window: a self-serve PDF does not justify a subscription motion.

5. First-customer acquisition

One channel only: LinkedIn direct message to Lab Operations Managers and Senior Research Associates at 10-50 person US biotech companies. The mechanics are worked on day 6 (150-row list), day 8 (first 30 touches), and day 14 (kill the worst angle). The template is short and offers a free finished packet built from the buyer's own redacted spreadsheet. That converts the first ask from a purchase into a proof.

Week one goal: 150 profiles identified, 60 connection requests, 25 conversations, 8 redacted spreadsheets received, 8 free packets delivered. Those eight packets are the actual sales asset; the landing page is secondary.

6. 30-day execution roadmap

Days 1-5: build and ship. Day 1 upload, day 2 validation, day 3 documents, day 4 payments, day 5 deployment and a real print-and-scan test. MVP deadline day 5.

Days 6-14: list, landing page, first 55 outreach touches, free packets delivered within 12 hours, day-3 follow-ups, first paid sale targeted for day 12. Day 13 ships only the change that killed the most deals. Day 14 produces a funnel scorecard.

Days 15-21: volume doubles, upsell offers go to repeat shippers, two CRO validation presets ship on day 18, a demo video publishes on day 20, and day 21 is a pricing decision memo.

Days 22-30: re-engagement of every warm lead, 40 new touches, referral asks to every buyer, automation of the two most requested CRO formats, backlog closing, and a day-30 reconciliation against the profit formula. The reconcilation includes an explicit check that no customer or payment predates the launch window.

7. Revenue and profit scenarios (projections only)

These are projections from stated assumptions, not verified revenue, existing customers, or real traction.

Conservative: 4 customers, $149 ARPU, $596 gross revenue, $27 payment fees, no refunds, no ad spend, $45 operating cost.

Base: 12 customers, $175 ARPU, $2,100 gross revenue, $99 refunds, $95 payment fees, no ad spend, $90 operating cost.

Upside: 30 customers, $220 ARPU, $6,600 gross revenue, $299 refunds, $297 payment fees, $250 paid marketing, $180 operating cost.

Hackathon profit is gross revenue minus refunds, chargebacks, payment fees, and ad spend. Hosting and delivery costs are not deducted for ranking but do reduce business profit. The base projection is deliberately far below the concept's original 100-customer math; cold LinkedIn conversion makes 100 unrealistic in 30 days.

8. Main risks and validation experiments

Five risks are tracked, each with a cheap test and a kill criterion. Conversion below 1%: tested by 60 touches before day 14, killed if fewer than 3 prospects send a spreadsheet. CRO format variance: tested by asking every recipient whether their CRO accepted the packet unchanged, killed per-format if two rejections occur on a field the tool cannot represent. One-time-need risk: tested by asking shipment frequency, killed by retiring the $499 tier if fewer than 20% ship twice in a month. Free template substitution: tested by asking what they use today. Solo delivery load: tested by logging minutes per free packet, capped at eight per week.

9. First 24-hour action plan

Hours 1-2: Vercel, Supabase, domain, schema. Hours 3-5: upload and parse. Hours 6-8: mapping and validation. Hours 9-11: manifest, chain-of-custody, label sheet PDF. Hours 12-14: Stripe checkout, tokenized download, 25-row prospect list. By hour 14 there is a payable product and the start of the list that determines whether day 12 happens at all.

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 →