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

RateCon Rapid

Turns any broker load email into a signed-ready rate confirmation PDF in 30 seconds, with an automatic profit check for small trucking companies.

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.16/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Facebook groups for US owner-operators and small trucking companies, supported by direct DMs to members who post about booking loads.
Who pays

US owner-operator or small trucking company (1-10 trucks) that books loads by email and has no full TMS; the dispatcher answers broker offers within minutes.

Biggest execution risk

Monetization potential 4.6/10

Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 11 sales at $99 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

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

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

Product opportunity and positioning

Target customer

US owner-operator or small trucking company (1-10 trucks) that books loads by email and has no full TMS; the dispatcher answers broker offers within minutes.

Why now

Brokers still send load offers as unstructured email, and small carriers still reply with Word documents. Structured-output LLM extraction is now cheap and accurate enough to remove the retyping step for a $99 one-time charge with no procurement.

Problem

Retyping broker load details into a Word rate con template is slow and error-prone, and it hides deadhead miles and fuel cost, so carriers book unprofitable loads or lose the load to a faster reply.

Solution

Paste the broker email into a web form; the parser extracts every load field; the user reviews and edits; the app computes miles, fuel cost, net profit and a rate-per-mile flag, then generates a branded PDF rate confirmation with the load terms and a profit summary block.

Differentiation · Word templates and TMS rate con screens require manual data entry and never compute profit. RateCon Rapid does the extraction, the break-even math and the PDF in one pass, and it costs less than an hour of a dispatcher's time.

Product opportunity and positioning

RateCon Rapid is a document-automation tool for one artifact that small US trucking companies produce every single day: the rate confirmation PDF they send back to a broker after accepting a load. The buyer is an owner-operator or a 1-10 truck carrier who books freight through email and does not run a full TMS. That buyer already has the workflow. Nothing about their day changes except that the 10-15 minutes of retyping becomes 30 seconds, and the guesswork about whether the load actually pays disappears.

The inefficiency is specific and repeated. A broker emails a load offer with an origin, a destination, pickup and delivery windows, weight, commodity, equipment type, a reference number and a rate. The dispatcher copies those fields into a Word template, or a Google Doc, or a notes app, then exports a PDF, then replies. Three things go wrong: fields get transposed, the reply is slow enough that the broker gives the load to someone faster, and deadhead miles plus fuel cost are never counted, so a load that looks like $2.10 per mile turns out to be a loser after 90 empty miles and diesel.

RateCon Rapid compresses that into a single pass. The user pastes the raw email. A structured-output LLM call extracts every field into an editable form. The user corrects anything the model misread. The app pulls driving miles, applies the carrier's own MPG and fuel price, computes estimated fuel cost and net profit, compares the result to a target rate per mile the carrier sets once, and flags the load if it falls below. Then it renders a branded PDF rate confirmation carrying the user's logo, company block, all load terms and a compact profit summary, ready to email back.

Positioning is deliberately narrow. RateCon Rapid is not a TMS, not a load board, not a factoring product, not an accounting system. It does not scan email inboxes, it does not auto-send to brokers, and it does not market rates. It replaces one manual step with one faster, more accurate step and produces the same output the carrier already needs. That matters because the sale does not require changing behaviour: the buyer sees a video of their own messy email turning into a clean PDF and understands the product in under a minute.

Commercial logic follows from frequency and price. A rate con is created many times a week, so the tool gets used immediately, which reduces refund risk. At $99 one-time, the purchase sits comfortably under any approval threshold for a one-truck business and can be paid on a card in a Facebook group DM thread. The competitive alternative is free, which is the real obstacle, so the wedge has to be visibly faster and must catch at least one thing the template cannot: the profit flag.

The JEV score of 61.6 (band C) reflects exactly that tension. Speed to first revenue scores strongly (8.47 normalized) and solo build feasibility is high (7.61), while monetization potential is the weakest axis (4.62) because a single $99 charge has no repeat path unless the founder adds one. This plan treats that weakness as an execution problem: the 30 days are spent converting a fast, cheap, one-time tool into a paid installed base, then offering a renewal and a multi-truck tier after the first cohort has used the product. Every revenue figure below is a projection from stated assumptions, not observed traction.

Section 2 of 8

Smallest sellable MVP

A single-page web app where a carrier pastes a broker email, gets an editable extracted load form with a profit flag, and downloads a branded rate confirmation PDF after paying $99 by card.

Must-have features

  • Paste-broker-email textarea plus optional MPG, fuel price and target rate-per-mile settings
  • LLM structured-extraction that returns broker name, load ID, origin, destination, pickup/delivery windows, weight, commodity, rate, equipment type and reference numbers
  • Editable review form for every extracted field before PDF generation
  • Mileage lookup plus fuel cost, net profit and rate-per-mile flag against the carrier's target
  • React-PDF rate confirmation with uploaded logo, company block, all load terms and a profit summary box
  • Stripe checkout for a $99 one-time Founder's License that unlocks unlimited PDF generation for 12 months
  • Saved history list of previously generated rate confirmations per account

Explicitly out of scope

  • No TMS integration or load board scanning
  • No automated email sending to brokers
  • No driver mobile app or GPS tracking
  • No invoicing, accounting or factoring features
  • No multi-user seats or enterprise admin
  • No live market rate data or licensed load board feeds
  • No SMS or phone support promise

Demo flow (what the buyer sees)

  1. Founder opens the app and pastes a real, messy broker load email
  2. Parser returns a filled review form in a few seconds
  3. Founder edits one field to show correction is trivial
  4. Profit panel shows miles, fuel cost, net profit and a red rate-per-mile flag
  5. Click Generate PDF; branded rate confirmation downloads with load terms and profit summary
  6. Click Pay $99; Stripe checkout completes and the download unlocks permanently
Build plan

Technical implementation plan

Stack

Next.js (App Router) on VercelOpenAI gpt-4o-mini with JSON schema structured outputsGoogle Maps Distance Matrix API for driving milesReact-PDF (@react-pdf/renderer) for PDF generationStripe Checkout plus webhook for the $99 licenseSupabase Postgres with row-level security for accounts and saved rate consResend for transactional license emailsVercel Blob for uploaded logos

Architecture

A Next.js app on Vercel serves the form and the dashboard. The browser posts pasted email text to a server route that calls OpenAI with a strict JSON schema and returns a normalized load object. A second route takes origin and destination, calls Google Maps Distance Matrix, and returns miles; the profit calculator runs server-side from miles, rate, MPG and fuel price so the math is identical for every user. The user edits the load object in a review form, then a server route renders it to PDF with React-PDF and streams it back; the PDF and load object are saved to Supabase against the user record. Stripe Checkout handles the $99 payment and a webhook flips a license row to active, which gates PDF download and history. Supabase Auth handles email magic links.

Build steps

  1. Create Next.js repo on Vercel, set environment variables, deploy a hello-world page
  2. Define the load JSON schema and wire the OpenAI structured-output extraction route with two sample broker emails
  3. Build the paste form and the editable review form bound to the load object
  4. Add Google Maps Distance Matrix call plus the profit calculator and rate-per-mile flag logic
  5. Render the rate confirmation with React-PDF using a logo upload and a company settings block
  6. Add Supabase auth, license table, saved history list and dashboard
  7. Integrate Stripe Checkout, webhook license activation, and paywall gating on PDF download
  8. Test against 15 real broker email formats and add a fallback manual-entry path when extraction returns low confidence
  9. Add rate limiting, error logging and a free-trial allowance of 3 PDFs before payment

AI components

  • OpenAI gpt-4o-mini structured-output extraction of load fields from pasted broker email text
  • Optional confidence scoring per field to highlight fields the user should double-check
Hardest technical risk: Broker email formats vary wildly, so extraction confidence is the real failure mode; a misread rate or delivery window produces a wrong PDF and a refund. Mitigation is a mandatory human review step, per-field confidence highlighting, and a manual-entry fallback that never blocks a user.
Section 3 of 8

Pricing and monetization

Founder's License

Entry offer
$99 one-time

For Owner-operators and 1-10 truck carriers who build rate confirmations manually

  • Unlimited rate confirmation PDFs for 12 months
  • Logo upload and company branding block
  • Profit guard with fuel cost, net profit and rate-per-mile flag
  • Saved history of past rate confirmations

Fleet Renewal

$149 one-time

For Existing License holders renewing at month 12, or 3-10 truck carriers

  • Everything in Founder's License
  • Up to 5 company profiles
  • Priority parser fixes for broker formats they send in

Model: One-time $99 Founder's License covering unlimited rate confirmation PDFs for 12 months, sold by Stripe Checkout with no subscription.

First revenue offer: Founder's License: $99 one-time, unlimited rate cons for 12 months, free for the first 10 carriers to try it — the $99 is collected from carrier 11 onward and from anyone who wants permanent history after the free trial.

Expected ACV: $99

Upsell path: Month 12 renewal at $149 and a fleet tier for multi-truck carriers; both are offered only after the first cohort has generated real rate cons in the product.

Target customers
25
Revenue model
$2,475
Costs
$100
Profit model
$2,375
Section 4 of 8

First-customer acquisition

Primary channel

Facebook groups for US owner-operators and small trucking companies, supported by direct DMs to members who post about booking loads.

Where to find them

  • Owner Operator Trucking Facebook groups
  • Trucking Business Owners Facebook groups
  • Small fleet / 1-5 truck carrier groups
  • Dispatch and load-booking discussion threads inside those groups
  • Public comments on trucking YouTube videos about rate cons and broker emails

Exact outreach motions

  • Join 5 groups and spend one day reading threads about rate cons, broker emails and slow replies; note exact wording carriers use
  • Post a 60-second screen recording of a messy broker email becoming a clean PDF with a red profit flag, with a comment offering free access to the first 10 carriers
  • DM 20 members who recently posted about booking loads, asking to run their own pasted load email through it live and sending the PDF back
  • Reply to every comment within an hour with a Stripe payment link and a 48-hour $99 price hold
  • Ask each free user for one sentence about time saved, then repost that sentence as social proof with permission and no invented names

Message template

Hey — saw you posting about booking loads off email. I built a tool that turns a broker's load email into a finished rate con PDF in about 30 seconds, and it flags the load if the rate per mile doesn't cover fuel. Want me to run one of your actual load emails through it and send you the PDF? No charge, no signup.
Week-one goal: 5 groups joined, 60-second demo posted in 3 groups, 20 DMs sent, 10 carriers running their own load email through the app.
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 1Infrastructure

Accounts and skeleton

  • Create Stripe account and connect it to TrustMRR before any customer exists
  • Deploy a Next.js hello-world to Vercel with Supabase project created
  • Join 5 owner-operator Facebook groups and read threads for phrasing

Deliverable: Live deploy, Stripe linked, 5 groups joined.

Day 2Extraction

Parser

  • Define the load JSON schema
  • Build the OpenAI structured-output route
  • Test against 6 real broker email formats collected from group threads

Deliverable: Parser returns correct load objects on 6 formats.

Day 3Review and profit

Form plus math

  • Build the paste form and editable review form
  • Add Google Maps Distance Matrix mileage lookup
  • Implement fuel cost, net profit and rate-per-mile flag against a saved target

Deliverable: End-to-end form showing a profit flag.

Day 4PDF

Rate confirmation output

  • Build the React-PDF rate confirmation with logo and company block
  • Add the profit summary box to the PDF
  • Render and visually check 5 PDFs against a real rate con layout

Deliverable: Downloadable branded rate confirmation PDF.

Day 5Sellable MVPMVP shipped

Auth, paywall, ship

  • Add Supabase auth, saved history and dashboard list
  • Wire Stripe Checkout and webhook license activation
  • Deploy the paid build and run one full purchase test with a real card

Deliverable: MVP live and purchaseable. mvp_deadline_day.

Day 6Hardening

Parser accuracy

  • Run 15 more broker email formats through the parser
  • Add low-confidence highlighting and a manual-entry fallback
  • Add a 3-PDF free trial allowance before payment

Deliverable: Parser stable across 20+ formats.

Day 7Asset

Demo video

  • Record a 60-second screen capture using a real messy broker email
  • Write the post copy and the free-first-10 offer
  • Prepare the DM list from group members who posted about rate cons

Deliverable: Demo video and post copy ready.

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

First posts

  • Post the demo video in 3 groups with the helpful comment
  • Reply to every comment within one hour
  • Log which groups respond and which remove the post

Deliverable: 3 posts live, first inbound replies.

Day 9Direct outreach

DMs

  • Send 20 personalized DMs offering to run their load email
  • Run each load email through the app and send back the PDF
  • Track replies in a simple sheet

Deliverable: 20 DMs sent, 10 PDFs delivered personally.

Day 10Conversion

Trials to paid

  • Follow up with every trial user within 24 hours with the Stripe link
  • Fix the top two extraction failures reported by users
  • Post the demo in 2 more groups

Deliverable: First Stripe payment links sent.

Day 11Close

Remove friction

  • Add a one-click sample load email on the homepage
  • Add an FAQ block answering price, refunds and logo upload
  • DM the 5 warmest trial users with a 48-hour price hold

Deliverable: Homepage friction removed, 5 price holds out.

Day 12RevenueFirst sale target

First sale target

  • Close the first paid Founder's License
  • Confirm the payment shows in the TrustMRR-connected Stripe account
  • Ask the buyer which broker format they see most

Deliverable: First verified sale. first_sale_target_day.

Day 13Iterate

Format coverage

  • Add parser handling for the format reported on day 12
  • Re-run the 20-format regression test
  • Update the demo video if the flow changed

Deliverable: One more broker format supported.

Day 14Review

Week 2 audit

  • Count posts, DMs, trials and paid conversions
  • Cut the channel step with the worst reply rate
  • Write the week 3 outreach list of 40 new names

Deliverable: Funnel numbers and a 40-name outreach list.

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

Second cohort

  • Send 25 DMs with a personalized PDF from their own emailed load
  • Post a before/after screenshot in 2 new groups
  • Reply to old threads where carriers complained about rate con typos

Deliverable: 25 DMs and 2 new group posts.

Day 16Proof

Time-saved evidence

  • Ask each paid user for one sentence on time saved
  • Add those sentences to the homepage with permission
  • Do not invent names, logos or numbers

Deliverable: Verified social proof section live.

Day 17Objection handling

Free-template objection

  • Write a short comparison of a Word template versus RateCon Rapid
  • Add a refund policy line to checkout
  • Answer the free-template question directly in every group thread

Deliverable: Comparison page or post live.

Day 18Referral

Word of mouth

  • Offer existing buyers a $25 credit for each carrier they refer who pays
  • Add a referral note to the license email
  • Follow up with buyers who went quiet

Deliverable: Referral offer live.

Day 19Retention signal

Usage

  • Count PDFs generated per paid user
  • Email the two lowest-usage users asking what blocked them
  • Fix the single most cited blocker

Deliverable: Usage table and one fix shipped.

Day 20Second channel test

YouTube comments

  • Find 10 trucking videos about rate cons and broker emails
  • Leave 10 specific, non-spammy comments mentioning the tool
  • DM 10 commenters who ask about it

Deliverable: 10 comments and 10 DMs from a second surface.

Day 21Review

Week 3 audit

  • Compare group posts versus DMs on cost per paid customer
  • Double down on the better surface
  • Set the week 4 target of 10 new paid licenses

Deliverable: Channel decision and week 4 target.

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

Paid push

  • Send 30 DMs to carriers from the day 14 list
  • Post the demo in 3 additional groups
  • Run 5 live PDFs over DM to close hesitators

Deliverable: 30 DMs and 3 group posts.

Day 23Renewal path

Second revenue line

  • Add the $149 Fleet Renewal tier to the pricing page
  • Email every buyer with the renewal and fleet option
  • Track interest without promising unbuilt features

Deliverable: Renewal tier live and announced.

Day 24Reliability

Support load

  • Add an error log dashboard for failed extractions
  • Add a self-serve retry button
  • Write a 5-line help page for the three most common failures

Deliverable: Failure handling shipped.

Day 25Proof depth

Case detail

  • Record a second 45-second video using a different broker format
  • Post it in the two groups that performed best
  • Ask buyers to comment publicly on their own purchase

Deliverable: Second demo video posted.

Day 26Conversion polish

Checkout

  • Shorten checkout to one screen
  • Add a clear 12-month license term in the button copy
  • Test the full purchase on mobile

Deliverable: Mobile checkout verified.

Day 27Pipeline

Late-month closes

  • DM every trial user who has not paid
  • Offer a 24-hour price hold on 5 warm leads
  • Log objections verbatim

Deliverable: All trial users contacted.

Day 28Review

Week 4 audit

  • Total paid licenses, refunds and fees
  • Recheck TrustMRR payment connection
  • Decide the final two-day push list

Deliverable: Verified totals for the month to date.

Days 29-30 · Consolidate · 2 days
Day 29Final push

Close window

  • DM 20 warmest leads with the final offer
  • Post the demo one last time in the best group
  • Fix any checkout or parser bug blocking a sale

Deliverable: Final outreach wave sent.

Day 30Close and wrap

Verification

  • Confirm every payment is inside the contest window
  • Reconcile refunds and fees against Stripe
  • Write the post-mortem with real numbers only

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

  • Conservative: 3 paid licenses, mostly from DMs, no ad spend, near-zero refunds, Stripe fees at 3.9% plus fixed component on a $99 charge.
  • Base: 10 paid licenses from 5 groups and roughly 60 DMs, no ad spend, Stripe fees at about 3.9%.
  • Upside: 25 paid licenses matching the concept target, one $150 test of a paid sponsored post in a trucking group, Stripe fees near 3.9%, two refunds.
  • Payment processing assumed to be Stripe Checkout at roughly 3.9% effective on a $99 single charge, rounded to whole dollars.
  • Ad spend is paid marketing only; all organic Facebook group posting and DM outreach is $0.
  • Operating costs cover Vercel, Supabase, OpenAI extraction, Google Maps Distance Matrix calls, Resend and the domain; hosting and API costs are not deducted from hackathon profit.
  • All figures are projections from these assumptions, not observed revenue, customers or traction.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$12
Paid marketing
$0
Hackathon profit
$285
Operating costs
$25
Business profit
$260

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$39
Paid marketing
$0
Hackathon profit
$951
Operating costs
$45
Business profit
$906

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$50
Chargebacks
$0
Payment fees
$97
Paid marketing
$150
Hackathon profit
$2,178
Operating costs
$90
Business profit
$2,088

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$990
Payment fees (3.9%)
$39
Paid marketing
$0
Hackathon profit
$951
Business profit
$906

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. Nothing here represents existing customers, collected payments or real traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Facebook group admins remove promotional posts before any carrier sees them.

Mitigation

Lead with a useful before/after comment and only post where group rules allow vendor posts; keep DM outreach as the primary path.

Validation experiment

Post the demo in 3 groups on day 8 and count removals versus replies within 24 hours.

Kill criteria

If 3 of 3 groups remove the post and DMs yield fewer than 5 replies from 20 sends, change channel before day 12.

Risk 2Carriers see a free Word template as good enough and never pay $99.

Mitigation

Lead every message with the profit flag and the rate-per-mile warning, which no template produces.

Validation experiment

Ask 10 carriers in DMs what they currently use and whether a profit flag would change their reply; record verbatim answers.

Kill criteria

If fewer than 2 of 10 carriers say the profit check matters, reposition the offer around speed alone or add a differentiator before spending more outreach.

Risk 3AI extraction misreads the rate or delivery window and produces a wrong PDF, causing refunds.

Mitigation

Mandatory review form, low-confidence field highlighting, and a manual-entry fallback.

Validation experiment

Run 20 real broker email formats through the parser and count fields needing correction per email.

Kill criteria

If more than 3 fields per email need correction on average, add template training or restrict supported formats before charging.

Risk 4Google Maps and OpenAI costs rise faster than the $99 price covers.

Mitigation

Cache mileage per origin-destination pair and cap free trial generations at 3.

Validation experiment

Measure cost per generated PDF across the first 100 generations.

Kill criteria

If cost per PDF exceeds $1.50, cut mileage lookups to cached pairs only or raise the price.

Risk 5The single $99 charge has no repeat path, so revenue stops after the first cohort.

Mitigation

Ship the $149 Fleet Renewal tier and a referral credit inside the same 30 days.

Validation experiment

Offer the renewal tier to every buyer on day 23 and count expressed interest.

Kill criteria

If zero buyers express renewal interest by day 28, plan a different recurring product rather than pushing this one.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Stripe account and connect it to TrustMRR
  • Confirm no payments or customers exist before launch

Output: Payment rail live and contest-compliant.

Hours 3-5

  • Create the Next.js repo, Supabase project and Vercel deploy
  • Set environment variables for OpenAI, Google Maps and Stripe

Output: Deployed skeleton with all keys wired.

Hours 6-9

  • Write the load JSON schema
  • Build the OpenAI extraction route and test with 2 real broker emails

Output: Working parser on 2 real formats.

Hours 10-12

  • Join 5 owner-operator Facebook groups
  • Save 20 recent threads about rate cons and booking delays

Output: Channel access plus a phrasing bank.

Complete report

Full 30-day launch report

Read the full generated report

RateCon Rapid — 30-Day Launch Report

Contest window: Monday November 16, 2026 13:00 UTC to Wednesday December 16, 2026 13:00 UTC. Solo founder. All revenue figures below are projections from stated assumptions, not verified revenue, customers or traction.

1. Product opportunity and positioning

Small US trucking companies produce one document constantly: the rate confirmation PDF they send back to a broker after accepting a load. The buyer here is a 1-10 truck carrier with no TMS, booking freight by email, rebuilding that PDF from scratch several times a week in Word or a Google Doc.

The cost of that manual step is threefold. Fields get transposed between the email and the template. The reply is slow enough that the broker gives the load to a faster carrier. And deadhead miles plus diesel are never counted, so a load quoted at $2.10 per mile can lose money after 90 empty miles.

RateCon Rapid compresses the whole step into one pass: paste the broker email, let a structured-output model extract every field, correct anything misread in an editable form, get miles, fuel cost, net profit and a rate-per-mile flag against your own target, then download a branded PDF carrying your logo, company block, all load terms and a profit summary.

Positioning stays deliberately narrow. RateCon Rapid is not a TMS, load board, factoring tool or accounting system. It does not scan inboxes, auto-send to brokers or serve market rates. It replaces one manual step with a faster, more accurate version of the same output, which means the buyer does not have to change behaviour to get value.

The JEV score of 61.6 (band C) matches this reality. Speed to first revenue is the strongest axis at 8.47 normalized and solo build feasibility is 7.61, while monetization potential is the weakest at 4.62 because a single $99 charge has no repeat path. This plan treats that as an execution problem: build in five days, sell for twenty-five, then open a renewal and fleet tier after the first cohort has used the product.

2. Smallest sellable MVP

The sellable unit is one page: a paste box, an editable review form with a profit flag, a PDF download, and a $99 Stripe paywall. Seven features ship: paste input with saved MPG, fuel price and target rate per mile; structured extraction of broker name, load ID, origin, destination, pickup and delivery windows, weight, commodity, rate, equipment type and reference numbers; an editable review form; mileage plus fuel cost, net profit and rate-per-mile flag; a React-PDF rate confirmation with logo and profit summary; Stripe Checkout for a 12-month Founder's License; and a saved history list.

Out of scope on purpose: no TMS integration, no load board scanning, no automated email to brokers, no driver app or GPS, no invoicing or factoring, no multi-user seats, no live market rates, no support promise.

The demo is the sale. Paste a genuinely messy broker email, watch the form fill in, change one field to show correction is trivial, point at a red rate-per-mile flag, generate the PDF, then hit the paywall.

3. Technical implementation plan

Next.js on Vercel serves the app. The browser posts pasted email text to a server route that calls OpenAI gpt-4o-mini with a strict JSON schema and returns a normalized load object. A second route resolves miles through Google Maps Distance Matrix; caching origin-destination pairs keeps that cost near zero. The profit calculation runs server-side so every user gets identical math from miles, rate, MPG and fuel price. The review form edits the load object, a server route renders it through React-PDF and streams the file back, and both the load and the PDF are stored in Supabase against the user. Stripe Checkout takes the $99 and a webhook flips a license row to active, which gates downloads and history.

Build order: skeleton and deploy, schema and extraction route, paste and review forms, mileage and profit logic, PDF rendering, auth and history, Stripe and paywall, then regression testing across twenty broker formats.

The hardest risk is format variance. A misread rate or delivery window produces a wrong PDF and a refund, so the review step is mandatory, low-confidence fields are highlighted, and manual entry is always available as a fallback.

4. Pricing and monetization

One product, one price: a $99 one-time Founder's License covering unlimited rate confirmations for twelve months, sold through Stripe Checkout with no subscription and no sales call. That price sits under any approval threshold for a one-truck business and still covers delivery cost by a wide margin.

The first-revenue offer is specific: the first 10 carriers use it free, and the $99 is collected from carrier 11 onward and from any trial user who wants permanent history after the free allowance of three PDFs.

After the first cohort, revenue grows two ways. A $149 Fleet Renewal at month twelve, and a fleet tier for 3-10 truck carriers needing multiple company profiles. Both are offered only after buyers have generated real rate cons, so the pitch rests on usage rather than promises.

5. First-customer acquisition

The primary channel is Facebook groups for US owner-operators and small trucking companies, backed by direct DMs to members who post about booking loads.

Week-one motion: join five groups and read threads for exact phrasing, post a 60-second screen recording of a messy broker email becoming a clean PDF with a red profit flag, then DM twenty members offering to run their own load email through it and send the PDF back free. Every comment gets an answer within an hour.

Message angle that works: "Want me to run one of your actual load emails through it and send you the PDF? No charge, no signup." The reply is the demo, and the demo is the offer.

Week-one goal: 5 groups joined, demo posted in 3 groups, 20 DMs sent, 10 carriers running their own load email through the app.

No paying customers, partnerships or endorsements exist at the start. Every claim in outreach is about what the tool does, never about who uses it.

6. 30-day execution roadmap

Days 1-5 build. Day 1: Stripe connected to TrustMRR, Vercel and Supabase live, five groups joined. Day 2: schema and extraction route tested on six real formats. Day 3: paste form, review form, mileage and profit flag. Day 4: React-PDF rate confirmation with logo and profit block. Day 5: auth, history, Stripe paywall, first full purchase test. The MVP is sellable on day 5.

Days 6-7 harden and prepare: regression test twenty formats, add low-confidence highlighting and manual fallback, record the 60-second demo.

Days 8-14 sell: post in three groups on day 8, twenty personalized DMs on day 9, follow-ups and two more groups on day 10, homepage and FAQ friction removed on day 11, first sale target on day 12, format fix on day 13, funnel audit on day 14.

Days 15-21 expand: 25 more DMs, verified social proof from paying users only, a free-template objection page, a $25 referral credit, usage audit on paid accounts, a YouTube comment test, and a channel decision on day 21.

Days 22-28 push volume and open the second revenue line: 30 DMs, $149 renewal tier announced, error logging and retry, second demo video, shorter mobile checkout, and full contact of every unpaid trial user.

Days 29-30 close: final outreach wave, last group post, then reconcile every payment against the contest window and write the post-mortem with real numbers only.

7. Revenue and profit scenarios

All three scenarios are projections built from the stated assumptions. They are not verified revenue, existing customers or evidence of demand.

Prices are $99 one-time. Payment processing is modelled as Stripe Checkout at roughly 3.9% effective on a single $99 charge. Organic outreach costs nothing; ad spend is zero in two scenarios and $150 in the upside.

Conservative — 3 customers, $297 gross. $0 refunds, $0 chargebacks, $12 payment fees, $0 ad spend, $25 operating costs. Hackathon profit $285; business profit $260.

Base — 10 customers, $990 gross. $0 refunds, $0 chargebacks, $39 payment fees, $0 ad spend, $45 operating costs. Hackathon profit $951; business profit $906.

Upside — 25 customers, $2,475 gross. $50 refunds, $0 chargebacks, $97 payment fees, $150 ad spend, $90 operating costs. Hackathon profit $2,178; business profit $2,088.

The gap between conservative and upside is almost entirely distribution volume, not price or product. That is why days 8-28 are outreach days, not build days.

8. Main risks and validation experiments

Group admins remove promotional posts. Test by posting in three groups on day 8 and counting removals versus replies within 24 hours. If all three remove it and 20 DMs yield fewer than 5 replies, change channel before day 12.

Free Word templates are good enough. Test by asking ten carriers what they use and whether a profit flag would change their reply. If fewer than two of ten care about the profit check, reposition the offer before spending more outreach.

Extraction errors create wrong PDFs and refunds. Test twenty real broker formats and count corrections per email. If more than three fields need fixing on average, restrict supported formats or add template training before charging.

Delivery costs outrun the price. Measure cost per generated PDF across the first hundred generations. Above $1.50 per PDF, cache mileage pairs only or raise the price.

One-time pricing has no repeat path. Offer the $149 renewal to every buyer on day 23 and count interest. Zero interest by day 28 means a different recurring product is needed, not more of this one.

9. First 24-hour action plan

Hours 1-2: create the Stripe account and connect it to TrustMRR, confirming no payments or customers exist before launch. Output: a compliant payment rail.

Hours 3-5: create the Next.js repo, Supabase project and Vercel deploy; set keys for OpenAI, Google Maps and Stripe. Output: deployed skeleton.

Hours 6-9: write the load JSON schema, build the extraction route, test on two real broker emails. Output: working parser.

Hours 10-12: join five owner-operator Facebook groups and save twenty recent threads about rate cons and booking delays. Output: channel access and a phrasing bank for day 8 posts.

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 →