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

Blockwright

A coach-side tool that turns a client's exported training log into a ready-to-send next-4-week progression block with exact sets, reps and weights, in under 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.03/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach to solo online coaches found through public Instagram/X profiles and coach directories that advertise custom programming.
Who pays

Solo online strength/physique coaches and independent personal trainers with 1-40 active clients who sell custom programming and receive client logs via CSV, screenshots or pasted notes.

Biggest execution risk

Market demand 4.6/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 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.2/10.

Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.

Your first 24 hours

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

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

Product opportunity and positioning

Target customer

Solo online strength/physique coaches and independent personal trainers with 1-40 active clients who sell custom programming and receive client logs via CSV, screenshots or pasted notes.

Why now

The buyer already has the raw log and already sells the output artifact, so the product only deletes a 30-60 minute arithmetic step and can be paid for by personal card immediately.

Problem

Every block cycle the coach must read 3-4 weeks of logged sets, judge progression or stalls, choose next loads, and reformat it into a client-ready plan by hand in a spreadsheet.

Solution

The coach uploads or pastes a client log; Blockwright parses and normalises lifts, computes e1RM trends and stall flags, applies a published progression ruleset, and emits a coach-reviewed 4-week table plus a 2-page branded PDF.

Differentiation · It is not a consumer workout app, logging app or video analyser. It is a back-office calculator and PDF assembler for the person already paid to program.

Blockwright opportunity and positioning

Blockwright is a coach-side back-office tool for solo online strength and physique coaches. The buyer already sells custom programming, already receives client logs as CSV exports or pasted notes, and already has a recurring trigger: a client's next 4-week block is due. Today that means opening a spreadsheet or rewriting a template from memory, reading 3-4 weeks of logged sets, judging whether each lift progressed or stalled, choosing the next load, and reformatting it into something a client will pay for. The work is repetitive, slow and inconsistent between clients.

The concept was scored by JEV at 60.3 total (C band, confidence 0.73). That score is a planning signal, not demand proof. Its strongest normalised criterion is speed to first revenue at 8.23; its weakest are market demand at 4.57, monetization at 4.78 and operational simplicity at 4.93. This launch plan is shaped by those gaps. It narrows the buyer to coaches with an active roster and a block due now, keeps the offer to a one-time $99 audit that can be bought from a personal card, and avoids regulated data, human operations and custom infrastructure.

The problem is not that coaches lack training knowledge. It is that the arithmetic and formatting step is high-friction and easy to get wrong under time pressure. A coach with 20 clients may rewrite the same progression logic 20 times a month with small copy-paste errors. Blockwright keeps the coach as author but replaces the arithmetic with a deterministic rule engine and the formatting with a client-ready PDF. The coach still reviews, edits notes and sends the document. That matters for trust and liability: the product is presented as a coach-reviewed calculator, not automated advice to the lifter.

The positioning is deliberately narrow. It is not a consumer workout planner, not an in-workout logger, not a video or bar-path analyser, and not a marketplace. The closest alternative is a spreadsheet plus a template, and the wedge is that Blockwright consumes the coach's existing export and returns an auditable 4-week table plus a branded PDF in under two minutes. The value is measured in minutes saved per client per block and in fewer formatting errors, not in new training science.

The first commercial proof is a free next-block audit on the coach's own log, delivered within 24 hours. If the coach sends that block to a real client after editing notes only, the paid offer becomes credible. If the coach does not trust the output enough to send it, the concept fails fast before more build time is spent.

Section 2 of 8

Smallest sellable MVP

A $99 Single Block Audit: upload one client CSV or paste raw notes, receive a parsed trend/stall report and a 2-page coach-reviewed 4-week progression PDF with sets, reps, loads and target RPE.

Must-have features

  • CSV importer for Hevy/Strong-style exports with column mapping
  • Canonical lift matcher with an alias table for common exercise names
  • Deterministic e1RM trend and stall detector
  • Published progression ruleset engine that outputs a 4-week table
  • Client-ready PDF with coach name/logo and editable coach notes
  • Stripe Checkout at $99 plus tokenised private result link and emailed PDF
  • Watermarked sample-report landing page built from a demo log

Explicitly out of scope

  • No client-facing training app or in-workout logging
  • No video, bar-path or pose analysis
  • No wearable or HealthKit integrations
  • No subscription billing, team seats or coach marketplace
  • No exercise video library or nutrition planning
  • No automated advice delivery to the lifter

Demo flow (what the buyer sees)

  1. Coach opens the landing page and clicks Try a sample block
  2. Coach uploads a CSV or pastes raw log notes
  3. Blockwright maps columns and canonical lifts, then shows parsed sessions
  4. Engine computes e1RM trend, stall flags and a 4-week progression table
  5. Coach edits notes and confirms the block
  6. PDF is emailed and a private result link is shown; paid checkout unlocks a client-ready unwatermarked PDF
Build plan

Technical implementation plan

Stack

Next.js on VercelNeon Postgres for jobs and parsed logsStripe Checkout and webhookLLM API for messy-paste-to-structured-JSON parsing onlyDeterministic TypeScript rules engine for e1RM and progression mathreact-pdf or headless Chromium for PDF renderingResend for PDF email deliveryVercel Blob for temporary file storage with 7-day expiry

Architecture

The web app accepts a CSV or pasted text, stores a temporary job, and sends only messy unstructured text to an LLM for extraction into a strict JSON schema. All training math runs in deterministic TypeScript: canonical lift matching, e1RM calculation, stall detection, progression rules and deload flags. The rendered block is stored as JSON and turned into a PDF. Stripe webhook marks a job paid and releases the unwatermarked PDF plus a tokenised result link. No user accounts are required; access is by job token and email.

Build steps

  1. Create Next.js app, Postgres schema for jobs, parsed logs and blocks
  2. Build CSV upload with column-mapping screen and Hevy/Strong fixtures
  3. Add canonical lift alias table and unit tests for common exercise names
  4. Implement e1RM trend and stall detector with fixture-based tests
  5. Write progression ruleset as a versioned config and generate 4-week tables
  6. Render PDF template with coach notes, logo placement and watermark mode
  7. Add Stripe Checkout, webhook and tokenised paid result page
  8. Add Resend email delivery and 7-day Blob expiry
  9. Add LLM paste parser constrained to the same JSON schema with validation fallback
  10. Ship watermarked sample page and demo log for outreach

AI components

  • LLM used only to convert messy pasted notes into structured JSON; all progression arithmetic remains deterministic code
Hardest technical risk: Log-export format variance: a parser that silently mis-maps exercises or columns can produce a wrong block and a refund.
Section 3 of 8

Pricing and monetization

Single Block Audit

Entry offer
$99 one-time

For Solo coach running one client's next training block

  • Parsed log with trend and stall report
  • 4-week progression table PDF
  • Editable coach notes page
  • One revision within 7 days

Five-Block Pack

$349 one-time

For Coach with an active roster cycling several clients through a block

  • Five block audits
  • Saved lift alias mapping across blocks
  • Coach logo on all PDFs

Model: One-time per-block pricing, with a five-block pack for coaches cycling several clients through a block.

First revenue offer: Send me your own last 4 weeks of logged training and I will return your next 4-week block as a coach-reviewed PDF within 24 hours, free, no signup.

Expected ACV: $99

Upsell path: Convert single-block buyers into five-block packs, then repeat purchases as clients cycle into the next block; keep alias mappings to lower friction on repeat jobs.

Target customers
18
Revenue model
$1,782
Costs
$80
Profit model
$1,702
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to solo online coaches found through public Instagram/X profiles and coach directories that advertise custom programming.

Where to find them

  • Public Instagram bios mentioning 1:1 online coaching or custom programming
  • Public X/Twitter coach profiles with programming offers
  • Online coach directories and trainer listing pages
  • r/personaltraining and small online-coach Discord communities
  • Coaches already posting client progress or block reviews publicly

Exact outreach motions

  • Build a 60-coach list with name, handle, niche and one public programming signal
  • Send a short DM offering a free next-block audit on the coach's own log
  • Deliver the free PDF within 24 hours and ask if it is sendable after notes edits
  • Follow up on day 3 with one specific observation from their own log
  • Post an anonymised sample block in r/personaltraining and two coach Discords as a progression-math walkthrough, not an ad

Message template

Hey [name] - you sell custom programming, so this may save you a block cycle. Send me your own last 4 weeks of logged training (CSV or pasted notes) and I will return your next 4-week block as a coach-reviewed PDF within 24 hours, free, no signup. If it is useful, I will show you the paid version for client logs.
Week-one goal: Contact 60 coaches, deliver at least 10 free next-block audits, and convert at least 2 to a $99 paid block by day 14.
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

Repo and data model

  • Create Next.js repo and deploy to Vercel.
  • Define jobs, parsed_logs and blocks schema in Neon.
  • Set up Stripe test keys and webhook endpoint.

Deliverable: Running app with schema and test checkout shell.

Day 2Import

CSV upload and mapping

  • Build upload UI and temporary Blob storage.
  • Add column-mapping screen for unknown headers.
  • Create Hevy and Strong fixture files.

Deliverable: CSV uploads normalise into JSON sessions.

Day 3Analysis

Lift matching and stall detection

  • Build canonical lift alias table.
  • Implement e1RM trend calculation.
  • Add stall rules and unit tests.

Deliverable: Tested detector that flags flat or declining lifts.

Day 4Engine

4-week progression output

  • Write versioned progression ruleset config.
  • Generate week, lift, sets, reps, load and target RPE table.
  • Add deload flag and snapshot tests.

Deliverable: Deterministic 4-week block table from a parsed log.

Day 5DeliveryMVP shipped

PDF, checkout and email

  • Build PDF template with notes and watermark mode.
  • Connect Stripe Checkout and webhook.
  • Send PDF by Resend with tokenised result link.

Deliverable: End-to-end $99 block job from upload to emailed PDF.

Day 6Proof

Sample landing page

  • Generate watermarked sample from demo log.
  • Write landing copy around the free audit offer.
  • Add Stripe checkout and sample CTA.

Deliverable: Public sample-report page and checkout.

Day 7Pipeline

Coach list

  • Collect 60 public coach profiles.
  • Record niche, handle and programming signal.
  • Segment by strength vs physique coaching.

Deliverable: 60-coach outreach spreadsheet.

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

First DM wave

  • Send 20 personalised DMs.
  • Track replies and free-audit requests.
  • Log objections in a shared sheet.

Deliverable: 20 coaches contacted.

Day 9Delivery

Free audits

  • Manually review 3 incoming logs.
  • Run parser and correct mappings.
  • Send 3 free next-block PDFs.

Deliverable: 3 free audits delivered.

Day 10Outreach

Second DM wave

  • Send 20 more DMs.
  • Join two coach Discords.
  • Draft Reddit walkthrough post.

Deliverable: 40 coaches contacted and community access.

Day 11Iteration

Follow-up and fixes

  • Follow up day-3 non-repliers.
  • Add revision flow for paid jobs.
  • Fix top parser mapping issue.

Deliverable: Follow-up sent and parser patch shipped.

Day 12RevenueFirst sale target

First paid conversion

  • Send paid offer to warm free-audit coaches.
  • Share Stripe link and sample report.
  • Monitor checkout and webhook.

Deliverable: First paid $99 block target.

Day 13Delivery

Paid job quality

  • Process first paid client log.
  • Review PDF and notes page.
  • Send PDF and ask for one feedback line.

Deliverable: Paid block delivered and reviewed.

Day 14Review

Week-two scorecard

  • Count contacts, replies, free audits and paid blocks.
  • Identify the biggest conversion blocker.
  • Plan week-three outreach volume.

Deliverable: Week-two metrics and blocker list.

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

Third DM wave and community post

  • Send 20 new coach DMs.
  • Publish Reddit walkthrough with redacted sample.
  • Answer comments with sample link.

Deliverable: 60 coaches contacted and one public thread live.

Day 16Product

Branded PDF polish

  • Add coach logo upload.
  • Improve notes page layout.
  • Add pack coupon field.

Deliverable: Branded PDF option shipped.

Day 17Monetization

Pack offer

  • Create $349 five-block checkout.
  • Pitch pack to repeat free-audit coaches.
  • Add alias-memory note to pack copy.

Deliverable: Five-block pack live and offered.

Day 18Proof

Anonymised case sample

  • Build before/after sample from demo log.
  • Redact names and client details.
  • Publish sample page update.

Deliverable: Public redacted case sample.

Day 19Distribution

Community value post

  • Post progression-math teardown in two Discords.
  • Answer questions without hard selling.
  • Link only when asked.

Deliverable: Two community threads with sample link.

Day 20Pipeline

Follow-up all leads

  • Send 30 short follow-ups.
  • Ask warm leads for one client log.
  • Log who wants a paid block.

Deliverable: 10 active conversations.

Day 21Review

Reliability and policy

  • Add parser fallback path for unknown formats.
  • Publish refund and revision policy.
  • Review week-three metrics.

Deliverable: Risk log and policy page.

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

Fourth DM wave

  • Send 20 new coach DMs.
  • Work coach directories for 10 more leads.
  • Ask existing leads for referrals.

Deliverable: 80 coaches contacted.

Day 23Revenue

Paid conversion sprint

  • Send exact $99 offer to 15 warm leads.
  • Share one specific sample relevant to their niche.
  • Track objections by type.

Deliverable: 5 paid offers in market.

Day 24Delivery

Batch block production

  • Process up to 3 paid blocks.
  • Apply revisions within scope.
  • Ask for permission to use anonymised feedback.

Deliverable: 3 paid PDFs delivered.

Day 25Monetization

Pack upsell

  • Pitch five-block pack to single-block buyers.
  • Add logo setup to pack onboarding.
  • Record alias mappings for repeat jobs.

Deliverable: 2 pack offers sent.

Day 26Proof

Content asset

  • Publish redacted sample block and ruleset summary.
  • Explain stall detection in plain language.
  • Add CTA to free audit.

Deliverable: Public proof post live.

Day 27Outreach

Fifth DM wave

  • Send 20 new DMs.
  • Follow up all day-22 contacts.
  • Trim list to highest-signal coaches.

Deliverable: 100 coaches contacted.

Day 28Revenue

Close warm leads

  • Send sample to no-repliers once.
  • Answer refund and trust objections.
  • Push for 3 paid blocks.

Deliverable: 3 paid conversions target.

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

Accounting and reliability

  • Reconcile Stripe payments and fees.
  • Record refunds and operating costs.
  • Export job list and delivery status.

Deliverable: Clean ledger and delivery log.

Day 30Close

Final push and retro

  • Offer remaining warm leads a same-day block.
  • Deliver any open paid jobs.
  • Record final metrics and next-step decision.

Deliverable: Final 30-day scorecard and decision memo.

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 Single Block Audits at $99; Base: 10; Upside: 25. All are projections, not observed customers.
  • ARPU is modelled at $99 per block for all scenarios; five-block packs are an upside option but not required to hit the numbers.
  • Payment processing assumed at about 4% of gross revenue via Stripe Checkout; no separate platform fee.
  • Organic DM outreach is assumed to have $0 paid ad spend in all scenarios.
  • Operating costs cover Vercel, Neon, Resend, LLM parsing and domain; $25 conservative, $45 base, $90 upside.
  • Refunds are 0 in conservative and base; upside assumes one $99 refund.
  • Chargebacks are 0 in all scenarios.
  • No revenue, customers, partnerships or traction are claimed; all figures are hypotheses.

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
$40
Paid marketing
$0
Hackathon profit
$950
Operating costs
$45
Business profit
$905

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$99
Paid marketing
$0
Hackathon profit
$2,277
Operating costs
$90
Business profit
$2,187

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. Hackathon profit deducts refunds, chargebacks, payment fees and paid marketing; business profit also deducts operating costs.

Section 7 of 8

Main risks and validation experiments

Risk 1Log exports vary widely and a parser mishandles a format, producing a wrong block and refund.

Mitigation

Column-mapping screen, alias table, validation warnings and manual review fallback for unknown headers.

Validation experiment

Run 10 public sample exports or 5 coach-provided anonymised logs through the parser and count manual repairs.

Kill criteria

If more than 30% of first 10 paid jobs need manual repair after mapping, narrow accepted formats before more outreach.

Risk 2Coaches may not trust the output enough to send it to a paying client.

Mitigation

Position as coach-reviewed calculator, include editable notes and publish the progression ruleset.

Validation experiment

Ask 5 free-audit coaches whether they would send the PDF after notes edits only.

Kill criteria

If none of 5 would send it, change the output to a draft with explicit coach decisions rather than a finished block.

Risk 3One-time purchases may not repeat, limiting month-two revenue.

Mitigation

Five-block pack, saved alias mappings and repeat-block reminders tied to client cycles.

Validation experiment

Offer the $349 pack to every single-block buyer and track interest.

Kill criteria

If fewer than 10% of buyers show pack or repeat interest after 10 sales, treat as a one-off service and re-scope.

Risk 4Cold DM conversion to solo coaches may be far below the model.

Mitigation

Use narrow lists, free next-block audit and one specific log observation in follow-up.

Validation experiment

Send 60 DMs and track reply, free-audit and paid conversion rates by segment.

Kill criteria

If fewer than 5% reply after 60 targeted DMs, change channel to community walkthroughs before building more.

Risk 5A coach can replicate the progression logic in a spreadsheet after seeing the PDF.

Mitigation

Compete on speed, branded PDF, alias memory and audit trail rather than secret math.

Validation experiment

Ask 5 buyers why they paid instead of rebuilding it.

Kill criteria

If buyers say they would rebuild and not repurchase, pivot to a higher-frequency workflow such as weekly load updates.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Next.js repo and deploy a blank Vercel app.
  • Define jobs, parsed_logs and blocks schema in Neon.
  • Create Stripe test product and webhook placeholder.

Output: Deployed skeleton with schema and test checkout.

Hours 2-5

  • Build CSV upload and column-mapping UI.
  • Add Hevy and Strong fixture files.
  • Normalise one fixture into JSON sessions.

Output: Working CSV import for two common formats.

Hours 5-8

  • Implement canonical lift alias table.
  • Add e1RM trend and stall detector.
  • Write unit tests for flat, rising and missing-load cases.

Output: Tested detector module.

Hours 8-10

  • Draft watermarked sample report copy.
  • Select a demo log and generate a rough PDF layout.
  • Write the free next-block audit message.

Output: Draft sample page and outreach message ready for day-two polish.

Complete report

Full 30-day launch report

Read the full generated report

Blockwright 30-day launch report

1. Product opportunity and positioning

Blockwright is a coach-side back-office tool. The buyer is a solo online strength or physique coach with 1-40 active clients who already sells custom programming and already receives client logs as CSV exports, screenshots or pasted notes. The trigger is concrete: a client's next 4-week block is due, and the coach would otherwise spend 30-60 minutes rebuilding progression math in a spreadsheet or template. Blockwright deletes that arithmetic and formatting step while keeping the coach as author and sender.

JEV scored this concept at 60.3 total, C band, confidence 0.73. That is a planning signal, not demand proof. Speed to first revenue is the strongest normalised criterion at 8.23; market demand at 4.57, monetization at 4.78 and operational simplicity at 4.93 are the weak points. The plan therefore narrows to coaches with an active roster and a block due now, prices at a personal-card-friendly $99, and avoids regulated data, human operations and custom infrastructure. The differentiation is not another consumer workout app. It is a calculator plus PDF assembler that consumes the coach's existing data and returns an auditable artifact.

2. Smallest sellable MVP

The smallest sellable product is a $99 Single Block Audit. A coach uploads one client CSV or pastes raw notes, maps any unknown columns, and receives a parsed trend/stall report plus a 2-page coach-reviewed 4-week progression PDF with sets, reps, loads and target RPE. The coach edits notes and sends it to the client. No accounts, no client app, no video analysis. The demo flow is: upload log, confirm mappings, view stall flags, review the 4-week table, edit notes, receive emailed PDF. The free version uses the same flow on a demo log and is watermarked.

3. Technical implementation plan

Use Next.js on Vercel, Neon Postgres for jobs and parsed logs, Stripe Checkout with a webhook, Resend for email, Vercel Blob with 7-day expiry, and react-pdf or headless Chromium for PDF rendering. An LLM is used only to turn messy pasted notes into strict JSON; all training math is deterministic TypeScript. Build order: repo and schema, CSV import with column mapping, canonical lift alias table, e1RM and stall detector, versioned progression ruleset, PDF renderer, Stripe checkout and tokenised result page, email delivery, paste parser fallback, watermarked sample page. The hardest risk is format variance: a parser that silently mis-maps a lift or column can produce a wrong block and a refund. Validation warnings and a manual review path are part of the MVP.

4. Pricing and monetization

Pricing is one-time per block: $99 for a Single Block Audit with parsed log, 4-week PDF, editable notes and one revision within 7 days. A $349 Five-Block Pack adds five audits, saved lift alias mapping and coach logo on all PDFs. There is no subscription in the 30-day scope. The first revenue offer is a free next-block audit on the coach's own log, delivered within 24 hours, followed by the paid version for client logs. The upsell path is pack conversion and repeat blocks as clients cycle.

5. First-customer acquisition

The primary channel is direct outreach to solo online coaches found through public Instagram/X profiles and coach directories advertising custom programming. Build a 60-coach list, send a short DM offering a free next-block audit on their own log, deliver within 24 hours, and follow up on day 3 with one specific observation from their log. Post an anonymised sample block in r/personaltraining and two coach Discords as a progression-math walkthrough, not an ad. Week-one goal: contact 60 coaches, deliver at least 10 free audits, and convert at least 2 paid blocks by day 14.

6. 30-day execution roadmap

Days 1-5 build the MVP: schema, CSV import, lift matching, stall detection, progression engine, PDF, Stripe and email. Day 6 ships the watermarked sample page. Day 7 builds the coach list. Days 8-14 run the first two DM waves, deliver free audits, fix the top parser issue and target the first paid block on day 12. Days 15-21 add branded PDFs, launch the five-block pack, publish redacted samples and follow up all leads. Days 22-28 run two more outreach waves, push paid conversions, batch-deliver paid blocks, pitch packs and close warm leads. Days 29-30 reconcile Stripe, record operating costs, deliver open jobs and write the final scorecard.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 blocks at $99 = $297 gross, $12 payment fees, $0 refunds, $0 chargebacks, $0 ad spend, $25 operating costs. Base: 10 blocks = $990 gross, $40 fees, $45 operating costs. Upside: 25 blocks = $2,475 gross, one $99 refund, $99 fees, $90 operating costs. Hackathon profit deducts refunds, chargebacks, payment fees and paid marketing; business profit also deducts operating costs. No customers, partnerships or traction are claimed.

8. Risks and validation experiments

First, format variance: test 10 public or anonymised exports and count manual repairs; if over 30% need repair after mapping, narrow accepted formats. Second, trust: ask 5 free-audit coaches if they would send the PDF after notes edits only; if none would, change the output to a draft with explicit coach decisions. Third, one-time revenue: offer the $349 pack to every buyer; if under 10% show pack or repeat interest after 10 sales, re-scope. Fourth, cold DM conversion: send 60 targeted DMs; if under 5% reply, change to community walkthroughs. Fifth, replication: ask buyers why they paid instead of rebuilding; if they would rebuild and not repurchase, move to a higher-frequency workflow.

9. First 24-hour action plan

Hours 1-2: create the repo, deploy a blank Vercel app, define the Neon schema and create a Stripe test product with webhook placeholder. Output: deployed skeleton with schema. Hours 2-5: build CSV upload, column mapping and two fixture imports. Output: working importer. Hours 5-8: add lift alias table, e1RM trend and stall detector with unit tests. Output: tested detector. Hours 8-10: draft the watermarked sample page, generate a rough PDF layout and write the free-audit outreach message. Output: sample page draft and outreach copy ready for day two.

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 →