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

MoldPreflight

Upload a STEP or STL part and get an annotated, tool-ready preflight packet that flags draft, wall-thickness and undercut problems before a molder rejects the design.

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.

Speculative5.71/10
MVP build (solo)
6 days
Launch price
$0
Sales to $1,000 revenue
not meaningful at this price
First paying customer
Direct outreach to designers who publicly describe a molder rejection or a tooling round-trip, on r/industrialdesign, r/hardware and design Discords, offering one free preflight on the part they already sent.
Who pays

Freelance industrial designers and hardware founders at 2-30 person product companies who are about to send a plastic part to an injection molder.

Biggest execution risk

Market demand 4.0/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 6 days; the plan targets a first sale on day 12; strongest signal is speed to first revenue at 7.7/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

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

0/10
Entry price
$0
Solo build
6 days
30d base revenue
$1,788
30d hackathon profit
$1,567
Section 1 of 8

Product opportunity and positioning

Target customer

Freelance industrial designers and hardware founders at 2-30 person product companies who are about to send a plastic part to an injection molder.

Why now

Solo designers and small hardware teams already ship tooling on 1-3 week cycles and have no in-house DFM reviewer; the audit is a single file-in, artifact-out transaction they can buy on a card today.

Problem

The part looks fine in CAD, then the toolmaker replies 'no draft here, this wall is too thick, this undercut needs a slider' — costing a redesign cycle, a tooling change order or a launch delay.

Solution

Browser upload of a STEP/STL file runs a deterministic geometry audit along a chosen pull axis and returns a Tool-Ready Packet PDF: Ready/Fix-first verdict, heatmap screenshots, prioritized fix list with coordinates and millimetre values, plus a CSV of flagged faces.

Differentiation · Vendor-neutral and mold-agnostic: it is not a molder's free quoting tool, not a $50k simulation suite, and it produces a portable PDF you can forward to your molder or your client.

1. Product opportunity and positioning

The moment that creates the sale. A designer finishes a part, exports a STEP file, sends it to a molder, and waits. Three to seven days later the toolmaker comes back with a list: faces with zero draft, a wall that is 4.2 mm where the material wants 2.5 mm, an undercut that needs a slider and adds tooling cost. The designer now loses a week, possibly a change order, possibly a launch date. The buyer is not shopping for simulation software; they are standing inside a rejection email.

What MoldPreflight is. A browser uploader takes an STL or STEP file, asks for the pull axis and a material wall-thickness threshold, runs a deterministic geometry audit, and returns a Tool-Ready Packet: a Ready / Fix-first verdict, rendered heatmap screenshots of the flagged faces, a prioritized fix list with 3D coordinates and millimetre values, a CSV of flagged faces, and one re-run after edits. No solver, no plugin, no procurement. File in, artifact out.

Who pays. Freelance industrial designers and hardware founders at 2-30 person product companies. They buy personally with a card, usually within a day of a molder conversation, and they buy because the packet is something they can forward to a molder, a client, or a co-founder. The $149 Single Part Preflight is priced against one avoided round-trip, not against software seats.

Why this is defensible enough for a wedge. Large CAD vendors bundle DFM checks but require the file to live in their tool; molders offer free DFM but only to win a quote, which means the feedback is late, one-sided and not something a designer can take to a different vendor. MoldPreflight sits before the quote, is vendor-neutral, and outputs a portable document. That neutrality is the whole product.

Honest read of the scoring. JEV scored this concept 57.1/100 (band C, confidence 0.63). It is strong on speed to first revenue (7.67) and reachable customers (7.48), and weak on market demand (4.04) and monetization potential (4.77). The consequence is explicit: this is a cash-positive wedge expected to land in the low thousands of dollars in 30 days, not a $100K contender. The plan below is therefore built to (a) prove willingness to pay fast, (b) create a repeat-purchase path via the $349/month Studio tier so revenue is not a single one-off, and (c) keep operating cost near zero so every sale is profitable on delivery.

Positioning statement. For designers about to send a plastic part to a molder, MoldPreflight is the preflight check that finds the draft, thickness and undercut problems first, so the molder conversation starts with a fix list instead of a rejection.

All revenue figures in this report are projections from stated assumptions. No customers, partnerships or revenue have been verified.

Section 2 of 8

Smallest sellable MVP

A browser upload of one STL or STEP file that returns a watermarked free preview (verdict plus counts) and, after a $149 Stripe payment, the full Tool-Ready Packet PDF with heatmap screenshots, a prioritized fix list with coordinates, and a flagged-face CSV.

Must-have features

  • Browser upload for STL/STEP up to 50MB with async job queue and email-on-completion
  • STL load plus STEP tessellation via OCP with unit and bounding-box sanity checks
  • Pull-axis draft audit with per-face angle, flags under 1 and 2 degrees, heatmap PNG render
  • Wall-thickness audit via ray casting with hotspot list in millimetres at a user-set threshold
  • Undercut detector listing trapped regions with face-area estimates and screenshots
  • Tool-Ready Packet PDF generator plus CSV of flagged faces with 3D coordinates
  • Stripe Checkout with a gated free preview showing verdict and counts before payment

Explicitly out of scope

  • No CFD, mold-flow, cooling or warp simulation
  • No automatic geometry repair or reshaping of the user's CAD file
  • No SolidWorks or Fusion plugin in the first 30 days
  • No tolerance stack-up, material selection or costing engine
  • No molder marketplace, quoting network or procurement flow
  • No 24/7 support promise; email support during founder hours only
  • No team accounts, SSO or invoicing

Demo flow (what the buyer sees)

  1. Designer opens the site and drags in a STEP or STL file
  2. Picks pull axis (+Z default) and a wall-thickness threshold for their material
  3. Job runs; preview page shows Ready / Fix-first verdict and counts of flagged draft, thickness and undercut regions
  4. Designer pays $149 via Stripe Checkout
  5. Full packet is generated: PDF with heatmap screenshots and prioritised fix list, plus flagged-face CSV
  6. Packet is emailed and downloadable for 30 days; one re-run is unlocked after they edit the part
Build plan

Technical implementation plan

Stack

Next.js on VercelPython FastAPI worker on Rendertrimesh + numpy for ray-cast wall thicknessOCP/cadquery for STEP tessellationthree.js for flagged-face viewerWeasyPrint for the PDF packetStripe CheckoutSupabase Postgres + Cloudflare R2

Architecture

Next.js frontend handles upload (presigned to R2), records a job row in Supabase, and shows a polling status page. A FastAPI worker on Render pulls queued jobs, tessellates STEP via OCP or loads STL directly with trimesh, runs three deterministic passes (draft angle per face vs pull axis, wall thickness by ray casting inward along face normals, undercut by occlusion test along the pull axis), renders heatmap PNGs from the flagged face sets, and writes results back to Postgres plus R2. The preview page reads only counts and verdict; the paid page unlocks the PDF and CSV generators. Stripe webhook flips the job to paid and triggers packet assembly.

Build steps

  1. Scaffold Next.js app, Supabase schema (jobs, parts, orders, packets) and R2 bucket with presigned upload
  2. Build uploader UI with axis selector, threshold input and job status polling
  3. Worker skeleton on Render: queue poller, job state machine, structured logging
  4. STL ingest with trimesh; unit and bounding-box sanity checks and a rejection path for broken files
  5. Draft audit: face normal vs pull axis, flag under 1 and 2 degrees, render heatmap PNG
  6. Wall-thickness audit: ray casting, hotspot clustering, millimetre values per hotspot
  7. Undercut detection: occlusion along pull axis, trapped-region grouping, area estimates
  8. three.js viewer that highlights flagged faces on the model
  9. WeasyPrint PDF template: verdict, screenshots, prioritized fix list, coordinates, CSV appendix
  10. CSV export of flagged faces with coordinates and face IDs
  11. Stripe Checkout plus webhook, free-preview gating, one re-run credit per order
  12. Deploy end to end and run three self-made test parts through the full paid flow

AI components

  • No LLM in the geometry audit itself — checks are deterministic and must be reproducible
  • An LLM is used only to turn the raw flag list into the plain-English prioritized fix sentences in the PDF, with the numbers injected verbatim from the audit
Hardest technical risk: STEP tessellation of real-world files — imported STEP geometry frequently has non-manifold or self-intersecting faces that break ray casting and produce wrong flags, which turns directly into refunds.
Section 3 of 8

Pricing and monetization

Free Preview

Entry offer
$0 one-time

For Evaluators testing one file

  • Verdict page
  • Counts of flagged draft, thickness and undercut regions

Single Part Preflight

$149 one-time

For Designer or founder sending one part to a molder

  • Full Tool-Ready Packet PDF
  • Rendered flagged-face screenshots
  • Prioritized fix list with coordinates
  • CSV of flagged faces
  • One re-run after edits

Studio

$349 / month

For Small design studio running several parts per month

  • 10 preflights per month
  • Saved parts library
  • Pull-axis presets
  • CSV and PDF export for client handoff

Model: One-time $149 per part preflight with a free gated preview, plus a $349/month Studio plan for designers running several parts a month.

First revenue offer: $149 Single Part Preflight on the part they already sent to their molder, with the flagged faces from their own model referenced in the message and a 48-hour re-run guarantee.

Expected ACV: $149

Upsell path: Re-run credits and additional parts convert the one-time buyer into a repeat buyer; two or more parts a month are cheaper on Studio at $349/month, which creates the recurring line the concept currently lacks.

Target customers
12
Revenue model
$1,788
Costs
$55
Profit model
$1,733
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to designers who publicly describe a molder rejection or a tooling round-trip, on r/industrialdesign, r/hardware and design Discords, offering one free preflight on the part they already sent.

Where to find them

  • r/industrialdesign threads about DFM feedback, draft angles, undercuts
  • r/hardware and r/manufacturing posts about tooling change orders
  • Industrial design and 3D-printing Discord servers with a DFM or product channel
  • LinkedIn posts by industrial designers announcing a tooling kickoff or a molder quote
  • Freelance designer profiles listing injection-moulded consumer products in their portfolio
  • Public Kickstarter/Indiegogo hardware campaigns whose updates mention tooling

Exact outreach motions

  • Reply publicly in the thread with one specific, useful observation about the geometry problem, never a pitch
  • DM within an hour offering a free preflight on the actual file that got rejected
  • Deliver the free packet within 24 hours and ask one yes/no question: was the flagged issue real
  • Follow up on day 4 with a screenshot from their own model showing a flagged face
  • Follow up on day 9 with a second screenshot and the $149 offer plus the 48-hour re-run guarantee
  • Ask every paying buyer to forward the packet to their molder contact for a warmer introduction

Message template

Saw your post about the undercut feedback on the enclosure. I run a preflight check on STEP/STL parts before they go to a molder — draft, wall thickness, undercuts — and it returns a PDF you can forward. Send me the file you already sent and I'll run it free today and tell you what it flags. No signup needed.
Week-one goal: Log 300 qualified handles and threads, send 60 personalised outreach messages, deliver 8 free preflight packets, and book at least 3 explicit price conversations.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 6First sale target: day 1230 days planned
Week 1 · Build & validate · 7 days
Day 1Setup and recon

Ship the skeleton and start listening

  • Create repo, Supabase project, R2 bucket and deploy an empty Next.js app to Vercel.
  • Read r/industrialdesign, r/hardware and design Discords for DFM and undercut complaints; log the first 100 threads.

Deliverable: Live empty app plus a 100-row outreach log in a spreadsheet.

Day 2Uploader

File in

  • Build presigned upload to R2 with 50MB limit and job row creation.
  • Build the status page with polling and email-on-completion.

Deliverable: A real STL file uploads and moves through a job state machine.

Day 3Draft audit

First deterministic check

  • Load STL via trimesh with unit and bounding-box sanity warnings.
  • Compute per-face draft angle vs pull axis, flag under 1 and 2 degrees, render a heatmap PNG.

Deliverable: Heatmap PNG of flagged draft faces from a real part.

Day 4Thickness and undercuts

Complete the audit

  • Ray-cast wall thickness, cluster hotspots and report millimetres per hotspot.
  • Occlusion test along pull axis to group trapped regions with face-area estimates.

Deliverable: Verdict JSON listing draft, thickness and undercut counts.

Day 5Packet generator

The artifact

  • WeasyPrint template for the Tool-Ready Packet PDF with verdict, screenshots and fix list.
  • CSV export of flagged faces with coordinates and face IDs.

Deliverable: A complete PDF and CSV from a test part.

Day 6Payments and launchMVP shipped

MVP live

  • Wire Stripe Checkout and the webhook that unlocks the packet and one re-run.
  • Gate the free preview to verdict plus counts only; deploy to production domain.

Deliverable: Public site taking a real $149 payment end to end.

Day 7Self QA

Break it before customers do

  • Run three of your own test parts with a deliberately bad wall and a deliberate undercut.
  • Fix crashes on broken or non-manifold files; add a clean rejection message.

Deliverable: Three passing end-to-end runs and a graceful-failure path.

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

Volume

  • Expand the log to 300 handles across Reddit, Discords and LinkedIn design posts.
  • Send the first 30 personalised free-preflight offers.

Deliverable: 300-row log and 30 sent messages.

Day 9Free packets

Deliver value

  • Run and deliver free preflight packets for every file received.
  • Ask each recipient the yes/no question about whether the flag was real.

Deliverable: 5-8 delivered free packets with replies logged.

Day 10First price ask

Convert

  • Send the $149 offer to anyone who confirmed a flag was real.
  • Send 30 more outreach messages.

Deliverable: 3-5 explicit price conversations open.

Day 11Follow-up

Close

  • Follow up with a screenshot from each prospect's own model.
  • Fix any audit false positive reported by a free user.

Deliverable: At least one payment link clicked.

Day 12First saleFirst sale target

Money in

  • Close the first $149 Single Part Preflight and deliver the packet same day.
  • Log the exact objection that nearly blocked the sale.

Deliverable: First verified payment inside the contest window.

Day 13Packet polish

Referral-readiness

  • Improve PDF layout, verdict wording and fix-list ordering based on buyer feedback.
  • Add the buyer's molder-forward line and the founder email to the PDF footer.

Deliverable: Packet v2 shipped to all existing buyers.

Day 14Week two review

Double down

  • Rank outreach sources by reply and purchase rate; drop the worst one.
  • Send 40 messages to the top-performing source only.

Deliverable: Channel with the best reply rate identified.

Week 3 · Repeat & systematize · 7 days
Day 15Second-sale push

Repeat buyers

  • Offer every buyer a re-run on their edited part.
  • Pitch $349 Studio to anyone mentioning a second or third part.

Deliverable: At least one Studio conversation started.

Day 16STEP handling

Remove the biggest objection

  • Ship OCP tessellation for STEP uploads with a size and sanity guard.
  • Test on three user-provided STEP files.

Deliverable: STEP uploads working without manual rescue.

Day 17Studio tier

Recurring revenue

  • Ship saved parts library and pull-axis presets.
  • Wire the $349/month Stripe subscription with a 10-preflight monthly cap.

Deliverable: Studio plan purchasable.

Day 18Outreach wave two

Scale touches

  • Send 40 messages to design Discords and LinkedIn design posts.
  • Post one public, genuinely useful comment about draft-angle checking in two threads.

Deliverable: 40 new touches plus 2 public comments.

Day 19Support hardening

Keep load near zero

  • Write a one-page failed-upload troubleshooting note linked from the job page.
  • Add automatic refund-on-failure for jobs that error out.

Deliverable: Zero manual support for failed jobs.

Day 20Case artifacts

Proof without inventing it

  • Ask each buyer for permission to quote their one-line result anonymously.
  • Add an anonymised 'what the packet flags' example page using your own test parts only.

Deliverable: An example page built only from your own models.

Day 21Week three review

Unit economics

  • Compute real cost per audit from worker minutes and storage.
  • Cut anything above $0.50 per audit.

Deliverable: Measured cost per audit under $0.50.

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

Pipeline

  • Send 50 messages across all logged threads not yet contacted.
  • Re-engage the 10 warmest free-packet recipients who never replied.

Deliverable: 50 touches and 10 re-engagements.

Day 23Molder side

Warm referrals

  • Ask buyers to forward the packet to their molder contact.
  • Offer the molder a free preflight on one incoming part to test the referral loop.

Deliverable: At least 2 molder-side conversations.

Day 24Conversion fixes

Checkout

  • A/B the preview page verdict wording against counts-only.
  • Add the 48-hour re-run guarantee to the checkout page.

Deliverable: One checkout change shipped.

Day 25Third wave

Volume

  • Send 50 messages to newly surfaced threads.
  • Follow up on every open price conversation with a screenshot.

Deliverable: 50 touches and all open threads followed up.

Day 26Second Studio push

Recurring

  • Offer existing buyers a Studio upgrade credit equal to their last one-time purchase.
  • Add Studio onboarding email with saved-part instructions.

Deliverable: Studio upgrade path live.

Day 27Reliability

Refund prevention

  • Add a pre-payment file sanity check that warns before checkout on suspicious geometry.
  • Re-run all delivered packets against the current build.

Deliverable: Pre-checkout validation shipped.

Day 28Week four review

Honest numbers

  • Recompute conservative, base and upside against actual paid orders.
  • Decide whether the volume or the Studio motion gets all remaining outreach time.

Deliverable: Updated projection sheet with real order counts.

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

Collect

  • Send a closing offer to every warm thread: preflight today, packet within 24 hours.
  • Deliver every outstanding packet.

Deliverable: All open conversations resolved to yes or no.

Day 30Wrap

Report

  • Reconcile Stripe against the contest window; confirm fees, refunds and chargebacks.
  • Write a one-page result summary and decide the next 30-day direction.

Deliverable: Reconciled revenue statement and go-forward decision.

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 the stated assumptions, not verified revenue.
  • Pricing assumed: $149 one-time Single Part Preflight; $349/month Studio used only in the upside case.
  • Payment processing assumed at Stripe's 2.9% + $0.30, rounded up to roughly 4% of collected revenue.
  • Primary channel is organic direct outreach, so ad_spend is $0 in Conservative and Base.
  • Conservative: 5 buyers from ~150 touches, roughly a 3% touch-to-purchase rate.
  • Base: 12 buyers from ~350 touches, consistent with the concept's stated 3-4% rate.
  • Upside: 22 buyers including 2 Studio subscriptions, arpu blent to $167.
  • Operating cost covers Vercel, Render worker minutes, R2 storage, Supabase and the small LLM call used to word the fix list — about $0.35-0.50 per audit.
  • Refund rate held near zero by the free preview showing the verdict before payment; one refund modelled in Base, two in Upside.
  • No chargebacks modelled beyond zero; card disputes on a $149 deliverable are rare and would be handled by refund.
  • Upside assumes one $100 sponsored design-newsletter placement is tested in week four.

Conservative

5 customers
$745
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$30
Paid marketing
$0
Hackathon profit
$715
Operating costs
$25
Business profit
$690

Base case

12 customers
$1,788
collected revenue · avg payment $149
Refunds
$149
Chargebacks
$0
Payment fees
$72
Paid marketing
$0
Hackathon profit
$1,567
Operating costs
$55
Business profit
$1,512

Optimistic

22 customers
$3,674
collected revenue · avg payment $167
Refunds
$298
Chargebacks
$0
Payment fees
$147
Paid marketing
$100
Hackathon profit
$3,129
Operating costs
$120
Business profit
$3,009

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$588
Payment fees (3.9%)
$23
Paid marketing
$0
Hackathon profit
$565
Business profit
$510

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 excludes hosting, tooling and AI/API delivery costs; business profit subtracts them.

Section 7 of 8

Main risks and validation experiments

Risk 1Designers just ask their molder for DFM feedback for free instead of paying $149.

Mitigation

Position the packet as pre-quote and vendor-neutral, and emphasise that it is forwardable to a different molder or to a client, which a molder's own feedback is not.

Validation experiment

Offer 10 free packets this week and ask each recipient whether their molder had already flagged the same issues; count how many say no.

Kill criteria

If 7 of 10 say the molder already covers it, the free-alternative objection wins — reposition to studios who switch molders, or stop.

Risk 2Broken STEP geometry produces wrong flags, which converts directly into refunds and lost trust.

Mitigation

Pre-checkout sanity validation, a clean rejection path, automatic refund on job failure, and manual review of the first 10 paid STEP files before the packet is released.

Validation experiment

Run 10 user-supplied STEP files through the pipeline without manual repair and record how many complete cleanly.

Kill criteria

If fewer than 6 of 10 STEP files complete without manual intervention, restrict the product to STL only and say so on the page.

Risk 3Rule-based checks cannot judge design intent, so false positives erode trust in the verdict.

Mitigation

Phrase flags as questions with millimetre values rather than errors, show the pull-axis assumption on every screenshot, and let the buyer request one re-run at a different axis.

Validation experiment

Track every buyer dispute of a flag in week two and three; count false-positive claims per packet.

Kill criteria

If more than 25% of packets draw a legitimate false-positive dispute, the audit logic needs rework before further selling.

Risk 4Projected profit lands in the low thousands, far below the $100K prize, so the founder loses motivation mid-run.

Mitigation

Treat this explicitly as a cash-positive wedge test with a Studio recurring path; judge the 30 days on validated willingness to pay, not on prize rank.

Validation experiment

Compare week two versus week three revenue per 100 outreach touches to see whether the channel is compounding.

Kill criteria

If revenue per 100 touches falls week over week, the outreach channel is exhausted at this audience size.

Risk 5Solo support load grows with each edge-case upload and eats the outreach time that produces sales.

Mitigation

No 24/7 promise, email-only support during founder hours, a troubleshooting page, and automatic refund on failed jobs.

Validation experiment

Log minutes spent per delivered packet for the first 10 packets.

Kill criteria

If support exceeds 30 minutes per order, cut the surface area (STL only, single axis) before taking more orders.

Risk 6Studio recurring revenue never materialises, leaving only one-time $149 charges.

Mitigation

Pitch Studio at the moment a buyer mentions a second part, with an upgrade credit equal to their last one-time purchase.

Validation experiment

Ask every buyer how many parts they expect to send in the next 90 days and record the number.

Kill criteria

If no buyer reports two or more parts per month, drop the Studio tier from the page rather than carry dead pricing.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create repo, Supabase project and R2 bucket.
  • Deploy an empty Next.js app to Vercel on the production domain.

Output: Live URL and provisioned infrastructure.

Hours 3-5

  • Build presigned upload to R2 with a 50MB cap.
  • Create the jobs table and a status page that polls job state.

Output: A real STL file uploads and shows a job status.

Hours 6-8

  • Stand up the FastAPI worker on Render with a queue poller.
  • Load STL via trimesh and compute per-face draft angle against a pull axis.

Output: Verdict JSON with a real draft-flag count.

Hours 9-11

  • Render a heatmap PNG of flagged draft faces.
  • Log the first 50 outreach threads from r/industrialdesign and r/hardware.

Output: First heatmap image and a 50-row outreach log.

Hours 12-14

  • Draft the outreach message and the free-preflight offer.
  • Send the first 5 personalised messages to designers describing a molder rejection.

Output: 5 messages sent and logged with thread URLs.

Complete report

Full 30-day launch report

Read the full generated report

MoldPreflight — 30-Day Launch Report

1. Product opportunity and positioning

The sale is triggered by a specific event: a designer sends a STEP file to a molder and gets back a rejection list. Draft angles under a degree, a 4 mm wall where the material wants 2.5 mm, an undercut that needs a slider. Each round-trip costs a week, sometimes a change order, sometimes a launch date.

MoldPreflight sits before that email. A browser upload takes an STL or STEP file, a pull axis and a wall-thickness threshold, runs a deterministic geometry audit, and returns a Tool-Ready Packet: Ready / Fix-first verdict, heatmap screenshots of flagged faces, a prioritized fix list with coordinates and millimetre values, a CSV of flagged faces, and one re-run after edits.

The buyer is a freelance industrial designer or a hardware founder at a 2-30 person product company. They pay personally with a card, usually within a day of a molder conversation, and they buy the artifact, not a seat. The differentiator is neutrality: a molder's free DFM exists to win a quote, and CAD-vendor checks require the file to live in that vendor's tool. MoldPreflight's PDF can be forwarded to a different molder or to a client, which is the whole point.

JEV scored this 57.1/100, band C, on 0.63 confidence. Speed to first revenue (7.67) and reachable customers (7.48) carry it; market demand (4.04) and monetization potential (4.77) are the weak axes. Read that honestly: this is a cash-positive wedge expected in the low thousands over 30 days, not a $100K contender. The plan compensates by pushing for a repeat-purchase path (Studio at $349/month) and by keeping delivery cost under $0.50 per audit so every sale is profitable.

All numbers in this report are projections. No customers, revenue or partnerships are verified.

2. Smallest sellable MVP

One upload, one audit, one PDF. The MVP is: drag in an STL or STEP file, pick a pull axis and a wall threshold, see a free watermarked preview with the verdict and the counts of flagged draft, thickness and undercut regions, pay $149, and receive the full Tool-Ready Packet PDF and flagged-face CSV by email and download.

Must be present for the first sale: upload with async job queue, STL load and STEP tessellation, draft audit with heatmap render, ray-cast wall thickness with millimetre hotspots, undercut occlusion test, PDF generator, CSV export, Stripe Checkout, and the free-preview gate.

Not built in the first 30 days: no mold-flow or warp simulation, no automatic geometry repair, no CAD plugin, no tolerance stack-up or costing, no molder marketplace, no 24/7 support, no team accounts. Every one of those is a reason to delay the first sale and none is a reason a buyer hands over $149.

3. Technical implementation plan

Next.js on Vercel handles upload and status. Files go to Cloudflare R2 via presigned URLs; job rows live in Supabase Postgres. A Python FastAPI worker on Render polls the queue, tessellates STEP through OCP or loads STL with trimesh, then runs three deterministic passes: per-face draft angle against the pull axis (flag under 1° and 2°), wall thickness by ray casting inward along face normals with hotspot clustering in millimetres, and undercut detection by occlusion testing along the pull axis with trapped-region grouping.

Heatmap PNGs are rendered from the flagged face sets. WeasyPrint assembles the PDF; the CSV carries face IDs and 3D coordinates. Stripe Checkout with a webhook flips the job to paid and unlocks packet generation plus one re-run credit. three.js gives a flagged-face viewer on the paid page.

There is no LLM in the geometry math — the checks must be reproducible. An LLM is used only to word the prioritized fix sentences, with every number injected verbatim from the audit output.

The hardest risk is STEP tessellation. Imported STEP files routinely contain non-manifold or self-intersecting faces that break ray casting and produce wrong flags. Mitigation: pre-checkout sanity validation, a clean rejection path, automatic refund on job failure, and manual review of the first ten paid STEP files.

4. Pricing and monetization

Free Preview at $0 shows the verdict and counts only — enough to prove the audit found something, not enough to hand to a molder. Single Part Preflight is $149 one-time and includes the PDF, screenshots, prioritized fix list with coordinates, the CSV and one re-run after edits. Studio is $349/month for ten preflights, a saved parts library, pull-axis presets and client-ready exports.

The $149 is priced against one avoided round-trip, not against software. The first revenue offer this week is that $149 preflight on the file the prospect already sent their molder, with the flagged faces from their own model named in the message and a 48-hour re-run guarantee.

Upsell: every buyer is offered a re-run on their edited part, then Studio when they mention a second or third part, with an upgrade credit equal to their last one-time purchase.

5. First-customer acquisition

One channel: direct outreach to designers who publicly describe a molder rejection or a tooling round-trip, on r/industrialdesign, r/hardware and design Discords.

Log threads where someone mentions DFM feedback, draft angles, undercuts or a tooling change order. Reply publicly with one specific, useful observation about the geometry problem — never a pitch. Then DM offering a free preflight on the actual rejected file. Deliver within 24 hours and ask one question: was the flagged issue real? Follow up on day 4 and day 9 with a new screenshot from their own model, then present the $149 offer.

Week-one goal: 300 logged handles and threads, 60 personalised messages, 8 free packets delivered, 3 explicit price conversations.

6. 30-day execution roadmap

Days 1-6: build. Skeleton and recon (day 1), uploader and job queue (2), draft audit and heatmap (3), thickness and undercuts (4), PDF and CSV packet (5), Stripe and public launch (6). MVP deadline is day 6.

Days 7-14: first revenue. Self-QA on deliberately bad test parts (7), 300-row outreach log and first 30 messages (8), free packets delivered (9), first price asks (10), screenshot follow-ups (11), first $149 sale (12), packet v2 (13), channel ranking (14). First sale target is day 12.

Days 15-21: repeat and recur. Re-run offers and Studio conversations (15), STEP tessellation (16), Studio tier with saved parts library (17), second outreach wave (18), refund-on-failure and troubleshooting page (19), anonymised example page from your own test parts only (20), measured cost per audit under $0.50 (21).

Days 22-30: scale and close. 50 touches (22), molder-side referral asks (23), checkout A/B and guarantee (24), third wave plus follow-ups (25), Studio upgrade path (26), pre-checkout validation (27), honest re-projection against real orders (28), closing offer to every warm thread (29), Stripe reconciliation for the contest window and a go-forward decision (30).

7. Revenue and profit scenarios

Projections only, from stated assumptions.

Conservative: 5 customers at $149 = $745 gross, $0 refunds, $0 chargebacks, $30 payment fees (Stripe, ~4%), $0 ad spend, $25 operating cost.

Base: 12 customers at $149 = $1,788 gross, $149 refunds, $0 chargebacks, $72 payment fees, $0 ad spend, $55 operating cost.

Upside: 22 customers at a blended $167 = $3,674 gross, $298 refunds, $0 chargebacks, $147 payment fees, $100 ad spend (one sponsored newsletter test), $120 operating cost.

Hackathon profit excludes hosting and AI delivery; business profit subtracts operating cost. The base case lands near $1.5K hackathon profit — enough to prove willingness to pay, nowhere near the prize. Say that out loud rather than pretend otherwise.

8. Main risks and validation experiments

The biggest risk is that the free alternative wins: designers ask their molder instead of paying. Test it by delivering 10 free packets and asking whether the molder had already flagged the same issues. If 7 of 10 say yes, reposition to studios that switch molders or stop.

Second, broken STEP geometry produces wrong flags and refunds. Test 10 user-supplied STEP files through the pipeline unassisted; below 6 clean completions, ship STL only.

Third, false positives erode trust. Track disputed flags per packet; above 25% dispute rate, rework the logic before selling more.

Fourth, support load eats outreach time. Log minutes per delivered packet; above 30 minutes per order, cut surface area.

Fifth, Studio never materialises. Ask every buyer how many parts they expect in 90 days; if nobody reports two a month, remove the tier from the page.

9. First 24-hour action plan

Hours 1-2: provision repo, Supabase, R2, deploy an empty Next.js app to the production domain.

Hours 3-5: presigned upload with a 50MB cap, jobs table, polling status page.

Hours 6-8: FastAPI worker on Render, trimesh STL load, per-face draft angle against a pull axis.

Hours 9-11: render the first heatmap PNG; log 50 outreach threads.

Hours 12-14: draft the outreach message and free-preflight offer; send the first 5 personalised messages to designers describing a molder rejection.

Everything in this report is a projection built on stated assumptions. Verified revenue begins only when a real Stripe payment lands inside the contest window.

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 →