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

DepthCert

Upload a short stereo video and get a calibration and depth-accuracy certificate for your robot's vision rig in minutes.

One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.

Decide in 20 seconds

The facts that decide whether this is worth thirty days of yours.

Speculative5.24/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach to robotics engineers on LinkedIn plus a technical post on ROS Discourse, both offering a free sample report on their own rig.
Who pays

Robotics engineer at a 5-50 person manipulation or navigation startup who just integrated a new stereo camera and must validate it before a demo or deployment.

Biggest execution risk

Market demand 2.9/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 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

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
$958
Section 1 of 8

Product opportunity and positioning

Target customer

Robotics engineer at a 5-50 person manipulation or navigation startup who just integrated a new stereo camera and must validate it before a demo or deployment.

Why now

Depth tooling is mature enough that a serverless Python job produces a defensible measurement in minutes, and the deliverable is a file rather than an integration or a hardware purchase.

Problem

Stereo bring-up means days of one-off OpenCV calibration scripts, guessed error thresholds, and no standardized artifact to prove or compare rig accuracy.

Solution

Upload a 10-30 second stereo video; DepthCert runs stereo calibration, rectification checks and SGBM depth error at multiple distances, then returns a PDF certificate with parameters, heatmaps and a pass/fail table.

Differentiation · Free scripts are unversioned, undocumented and unshareable; DepthCert emits the same standardized pass/fail table every time, so two rigs can be compared and a result handed to a colleague or vendor.

1. Product opportunity and positioning

DepthCert sells a document, not a platform. The buyer is a robotics engineer at a 5-50 person manipulation or navigation startup who has just mounted a new stereo camera and has a demo or deployment on the calendar. That date is the trigger. Without it, engineers keep hacking OpenCV scripts on Friday afternoons and never pay for tooling.

The pain is measured in days, not dollars. A stereo bring-up means writing calibration code, guessing at acceptable error thresholds, and having nothing shareable to show a lead, a customer or a camera vendor when depth looks wrong. DepthCert converts a 10-30 second stereo video into a PDF certificate: intrinsics and extrinsics, a rectification check, depth error heatmaps at 0.5m, 1m and 2m, and a pass/fail table against common thresholds such as <2% depth error at 1m.

Why this is sellable now: a serverless Python job can produce a defensible measurement in under three minutes, and the output is a file. There is no API to adopt, no hardware to buy, no procurement cycle, and no data residency question beyond deleting the upload after processing.

JEV scored this concept 52.4 / 100 (band C, confidence 0.63). The weakest criteria are market demand (normalized 2.92) and monetization potential (4.07); the strongest is speed to first revenue (7.70). The thirty-day plan is shaped by that profile. Demand is addressed by narrowing hard to the pre-demo validation moment and naming it in every message. Monetization is addressed by keeping the first report cheap enough to be a card-swipe decision and adding a repeat path (Team Pack credits, re-certification after a lens or mount change, rig-to-rig comparison). Speed to revenue is spent immediately: outreach starts on day 7, before the product is polished.

Differentiation: free scripts exist and always will. They are unversioned, undocumented and not shareable. DepthCert wins by producing a standardized, comparable artifact - the same pass/fail table every time - so two rigs can be compared and a result can be forwarded to someone who was not in the room.

What this is not: not a live depth API, not a real-time streaming service, not a hardware product, not a replacement for a proper calibration lab. It is a fast, cheap, standardized sanity check with a paper trail. Every message should say that, because overclaiming accuracy is the fastest way to lose a robotics engineer's trust on the first reply.

Section 2 of 8

Smallest sellable MVP

A web page where a user uploads one stereo video plus baseline and focal length, pays $99 by card, and receives a PDF certificate with calibration parameters, depth error heatmaps and a pass/fail table within five minutes.

Must-have features

  • Video upload for MP4 or a zipped image pair sequence, capped at 200MB
  • Manual entry of baseline, focal length and image size, with checkerboard auto-detect when available
  • Stereo calibration and rectification check using OpenCV, with reprojection error reported
  • SGBM disparity to depth conversion with error measurement at 0.5m, 1m and 2m
  • Depth error heatmap images rendered per distance band
  • ReportLab PDF certificate with parameters, heatmaps and pass/fail table
  • Stripe Checkout for a single $99 report, unlocked by webhook
  • Email delivery of the PDF plus a stored copy on a minimal dashboard page

Explicitly out of scope

  • Live RTSP streaming or a real-time depth API
  • Multi-camera fusion or full 3D reconstruction
  • Custom model training or fine-tuning
  • Enterprise SSO, procurement or invoicing workflows
  • Hardware sales or camera manufacturing
  • Team collaboration beyond shared report links

Demo flow (what the buyer sees)

  1. Buyer opens the landing page and clicks Run a report
  2. Buyer pays $99 through Stripe Checkout
  3. Upload form accepts the stereo video plus baseline, focal length and image size
  4. Worker detects the checkerboard, calibrates, rectifies and computes disparity
  5. Depth error is computed at three distance bands and rendered as heatmaps
  6. PDF certificate is generated and emailed within five minutes
  7. Report appears on the buyer dashboard for download and sharing
Build plan

Technical implementation plan

Stack

Next.js on VercelFastAPI on RenderOpenCV headless (Python)NumPyReportLabPostgres via SupabaseCloudflare R2 or S3 for video and PDF storageStripe Checkout plus webhookResend for transactional email

Architecture

Next.js serves the marketing page, upload form and dashboard. FastAPI exposes three endpoints: create job, upload asset, fetch report. A Stripe webhook marks a job as paid before the worker touches it. Paid jobs are queued in a Postgres table and picked up by a single worker process on Render that runs OpenCV calibration, disparity and error computation, then renders the PDF with ReportLab and stores it in object storage. The original video is deleted twenty-four hours after processing. No always-on infrastructure beyond one small worker instance.

Build steps

  1. Scaffold Next.js and FastAPI repos, deploy skeletons to Vercel and Render
  2. Implement Stripe Checkout session creation and webhook that flips job status to paid
  3. Build upload endpoint with MP4 and zip handling, storing to object storage
  4. Write the OpenCV calibration module: checkerboard detection, calibrateStereo, rectification error
  5. Add SGBM disparity, reprojection to depth, and error computation against known geometry
  6. Render depth heatmaps as PNG and assemble the PDF certificate with ReportLab
  7. Build the dashboard list view and signed PDF download links
  8. Run three end-to-end tests with synthetic and real stereo sample videos and fix failure modes
  9. Add job timeout, retry and a clear failure email so broken uploads do not burn refunds

AI components

  • No LLM in the core pipeline; depth comes from OpenCV SGBM
  • Optional vision-model pass only if checkerboard autodetection fails, to locate corners in poor lighting
Hardest technical risk: User videos that do not contain a usable checkerboard or are badly out of sync. Mitigation: fall back to user-supplied intrinsics plus a self-consistency error check, and state clearly in the PDF which mode was used so the certificate never overstates confidence.
Section 3 of 8

Pricing and monetization

Single Report

Entry offer
$99 one-time

For Robotics engineer validating one camera rig before a demo

  • One stereo video upload
  • Calibration PDF certificate
  • Depth error heatmaps at three distances
  • Pass/fail summary table

Team Pack

$249 one-time

For Team comparing multiple rigs or iterating on mounts

  • Three report credits
  • Comparison dashboard across reports
  • Priority processing queue
  • Shareable report links

Model: One-time per-report purchase with a prepaid multi-report team pack; no subscription in the first 30 days.

First revenue offer: A free sample DepthCert report on their own stereo video, followed by a $99 full certificate if the sample looks useful.

Expected ACV: $99

Upsell path: Single Report buyers are offered a Team Pack when they mention a second rig; every certificate carries a $49 re-certification credit after a lens, mount or baseline change, which converts one-time buyers into repeat buyers.

Target customers
10
Revenue model
$990
Costs
$60
Profit model
$930
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to robotics engineers on LinkedIn plus a technical post on ROS Discourse, both offering a free sample report on their own rig.

Where to find them

  • LinkedIn search for perception engineer, robotics engineer and computer vision engineer at 5-50 person robotics companies
  • ROS Discourse camera and perception category threads about calibration
  • r/robotics and r/computervision posts about stereo depth problems
  • Public GitHub maintainers of ROS camera and stereo packages
  • University robotics lab pages with named PhD students and lab engineers
  • Cobot and warehouse automation integrator directories

Exact outreach motions

  • LinkedIn DM batch of 15 per day offering a free sample certificate on their rig, no signup required
  • ROS Discourse post with a real sample PDF and an open invitation to send a video
  • Reply to existing calibration threads with a concrete measurement, not a pitch
  • Email three university lab engineers offering a free certificate for a student rig
  • Follow up every non-responder after four days with the sample report attached
  • Offer a $79 first-report price to the first ten responders as a launch concession

Message template

Hi [name] - saw you are working on perception at [company]. I built DepthCert: send a 30-second stereo video, get back a PDF with calibration params, depth error heatmaps at 0.5/1/2m and a pass/fail table. Happy to run your rig for free so you can see if the numbers are useful. Want me to?
Week-one goal: 40 named contacts identified and messaged, one ROS Discourse post live, and 5 free sample reports delivered on real customer videos.
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 1Foundation

Repo and deploy skeleton

  • Create Next.js and FastAPI repos and deploy both to Vercel and Render.
  • Wire Stripe test-mode Checkout and the webhook that flips job status.
  • Buy the domain and point it at Vercel.

Deliverable: Deployed skeleton with a working test-mode checkout.

Day 2Ingestion

Upload and decode

  • Build the upload endpoint for MP4 and zipped image sequences.
  • Decode frames with OpenCV and validate that both left and right streams exist.
  • Store uploads in object storage and delete after 24 hours.

Deliverable: A video can be uploaded and split into frame pairs.

Day 3Calibration

Stereo calibration core

  • Implement checkerboard detection and calibrateStereo.
  • Compute rectification error and reprojection error.
  • Add manual intrinsics fallback when detection fails.

Deliverable: Calibration parameters and error numbers for a test video.

Day 4Depth

Disparity and error metrics

  • Run SGBM disparity and convert to depth in metres.
  • Compute error at 0.5m, 1m and 2m bands.
  • Render three depth error heatmap PNGs.

Deliverable: Depth error heatmaps from a real stereo pair.

Day 5Report

PDF certificate and delivery

  • Assemble the certificate with ReportLab: parameters, heatmaps, pass/fail table.
  • Email the PDF via Resend and store it for the dashboard.
  • Add job timeout and a clear failure email path.

Deliverable: End-to-end paid job producing a PDF certificate.

Day 6Launch surfaceMVP shipped

Landing page and sample

  • Write the landing page: what the report proves, what it does not.
  • Publish one public sample certificate from a demo rig.
  • Run three full test purchases in live mode and refund them.

Deliverable: Live site with a public sample certificate.

Day 7Outreach prep

Lists and messages

  • Build a list of 40 robotics engineers with name, company and role.
  • Draft the LinkedIn DM and the ROS Discourse post.
  • Prepare the free-sample offer and a tracking sheet.

Deliverable: 40-contact list and two ready-to-send messages.

Week 2 · Launch & first sale · 7 days
Day 8First contact

Outreach batch one

  • Send 15 LinkedIn DMs offering a free sample report.
  • Publish the ROS Discourse post with the sample PDF.
  • Log every reply and objection in the tracker.

Deliverable: 15 DMs sent and one public forum post live.

Day 9First contact

Free sample delivery

  • Send 15 more DMs to a fresh segment.
  • Process the first two inbound videos through the pipeline.
  • Fix whatever breaks on real footage.

Deliverable: Two real sample reports delivered to prospects.

Day 10Follow-up

Follow-up and second post

  • Follow up all non-responders with the sample report attached.
  • Post a short technical write-up on rectification error in r/robotics.
  • Reply to two existing ROS calibration threads with a concrete measurement.

Deliverable: Second-wave outreach and one technical post.

Day 11Conversion

Free to paid handoff

  • Send each sample recipient a $99 checkout link.
  • Offer $79 to the first three who reply.
  • Track who opened the PDF versus who replied.

Deliverable: First paid checkout links out with a discount ladder.

Day 12RevenueFirst sale target

First sale

  • Close the warmest lead with a live screen share of their certificate.
  • Fix any report wording that scared them off.
  • Record the exact objection that nearly blocked the sale.

Deliverable: First paying customer and a recorded objection log.

Day 13Quality

Accuracy on real rigs

  • Compare certificate output against two buyers' manual calibration numbers.
  • Tighten the pass/fail thresholds to match published robotics conventions.
  • Add a mode banner to the PDF stating detection mode used.

Deliverable: Certificate wording revised after two real comparisons.

Day 14Review

Funnel audit

  • Count contacts, replies, samples and sales; compute each conversion rate.
  • Cut the message angle with the worst reply rate.
  • Write next week targets from the real numbers.

Deliverable: Funnel table with week-two targets set.

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

Batch three

  • Send 20 DMs to a new segment: cobot integrators.
  • Email three university lab engineers with the free-sample offer.
  • Log reply rate by segment.

Deliverable: 20 new contacts and segment reply-rate data.

Day 16Monetization

Team Pack launch

  • Ship the $249 Team Pack with three credits.
  • Add a comparison view listing two or more reports side by side.
  • Email existing single buyers about the pack.

Deliverable: Team Pack live and purchasable.

Day 17Sales

Live demos

  • Run three 15-minute screen-shares on prospects' own videos.
  • Ask each demo what threshold their team actually uses.
  • Capture verbatim language for the landing page.

Deliverable: Three demos completed and objection language collected.

Day 18Product

Known-target accuracy

  • Add a mode that measures error against a known-size target.
  • Show measured-versus-expected distance table in the PDF.
  • Document the mode difference in one help page.

Deliverable: Known-target mode shipped with a help page.

Day 19Distribution

Public proof

  • Post a results comparison on ROS Discourse.
  • Publish the certificate gallery page with anonymised samples.
  • Add an email capture for the sample report.

Deliverable: Public gallery page and one results post.

Day 20Revenue

Second paid cohort

  • Send checkout links to everyone who received a free sample.
  • Ask each buyer for permission to quote them anonymously.
  • Handle any refund request same day.

Deliverable: Two or more additional paid reports.

Day 21Review

Pricing signal

  • Compare conversion at $99 versus the $79 launch price.
  • Test a $149 price on the next five prospects to read resistance.
  • Decide the price to hold for week four.

Deliverable: Pricing decision with the evidence behind it.

Week 4 · Scale what works · 9 days
Day 22Scale outreach

Batch four

  • Send 20 DMs targeting teams with named SLAM or grasping projects.
  • Re-contact every warm lead who went quiet.
  • Ask two buyers for one referral each.

Deliverable: 20 new contacts plus referral asks sent.

Day 23Product

Repeat purchase path

  • Ship the $49 re-certification credit for existing reports.
  • Add a one-click re-run on a stored report.
  • Email prior buyers about the credit.

Deliverable: Re-certification credit live in the dashboard.

Day 24Proof

Case artifact

  • Publish one anonymised before-and-after rig report.
  • Add the strongest buyer sentence to the landing page.
  • Refresh the sample certificate with the improved template.

Deliverable: One case page published.

Day 25Conversion

Deadline push

  • Email all non-responders with the December 16 cutoff.
  • Offer the Team Pack at $199 for 48 hours.
  • Post the deadline in the ROS Discourse thread.

Deliverable: Deadline campaign sent to the full list.

Day 26Operations

Throughput

  • Cut processing time below three minutes per report.
  • Add an automatic refund if a job fails twice.
  • Automate the PDF delivery email.

Deliverable: Sub-three-minute median processing time.

Day 27Expansion

Second rig

  • Ask every buyer whether they have a second rig.
  • Send Team Pack offers to multi-rig accounts.
  • Log expansion revenue separately.

Deliverable: Expansion offers sent to all buyers.

Day 28Conversion

Final outreach

  • Send a final 20 DMs.
  • Post a last-call message on every channel used.
  • Close outstanding checkout links.

Deliverable: Final outreach wave completed.

Day 29Books

Reconciliation

  • Reconcile Stripe receipts against the TrustMRR payment account.
  • Confirm no chargebacks or unresolved refunds.
  • Export the revenue ledger with timestamps inside the window.

Deliverable: Verified revenue ledger exported.

Day 30Submission

Close and report

  • Confirm every payment landed before 13:00 UTC December 16.
  • Write the final results summary with real numbers only.
  • Submit the entry and archive all certificates and ledgers.

Deliverable: Submission complete with an auditable ledger.

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

  • Projections only, not verified revenue or existing customers.
  • Conservative: 3 single reports at $99, organic outreach only, no ad spend.
  • Base: 10 reports at $99 blended, matching the concept target of 10 customers in 30 days.
  • Upside: 25 purchases at a $105 blended ARPU as some buyers take the $249 Team Pack.
  • Payment fees assume Stripe at 2.9% plus $0.30 per transaction, roughly 3-4% of collected revenue.
  • Ad spend is zero in Conservative and Base because the channel is organic outreach; Upside assumes $150 of paid boosts to forum and newsletter placements.
  • Operating costs cover Render worker hours, object storage, Vercel, domain and email, non-zero because each report runs real OpenCV compute.
  • Refunds assume 0 in Conservative and Base; Upside assumes one $50 partial refund on a failed job.
  • Chargebacks assume 0 in all scenarios given the low price point and card-swipe buyer.
  • Hosting, domains, software and AI/API delivery costs are excluded from hackathon profit by contest rules but are included in business profit.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$10
Paid marketing
$0
Hackathon profit
$287
Operating costs
$25
Business profit
$262

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$32
Paid marketing
$0
Hackathon profit
$958
Operating costs
$45
Business profit
$913

Optimistic

25 customers
$2,625
collected revenue · avg payment $105
Refunds
$50
Chargebacks
$0
Payment fees
$84
Paid marketing
$150
Hackathon profit
$2,341
Operating costs
$90
Business profit
$2,251

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.

All three scenarios are projections built from stated assumptions. They are not verified revenue, not existing customers, and not a forecast of results.

Section 7 of 8

Main risks and validation experiments

Risk 1The calibration and depth numbers are not accurate enough for an engineer to trust or forward.

Mitigation

Report reprojection and rectification error alongside depth error, state the detection mode used, and never claim lab-grade accuracy.

Validation experiment

Ask two prospects to send their own manual calibration numbers and diff them against the certificate on day 13.

Kill criteria

If certificate depth error differs from a buyer's manual measurement by more than 25% on two independent rigs, stop selling and rebuild the metric.

Risk 2Engineers do the task themselves with free OpenCV scripts and never pay.

Mitigation

Sell the artifact and the time saved, not the algorithm: the PDF is the product, and it exists for sharing and comparison.

Validation experiment

Offer a free sample to 20 engineers and count how many then ask a follow-up question about their rig.

Kill criteria

If 20 free samples produce zero follow-up questions and zero checkout clicks, the willingness to pay is not there.

Risk 3Outreach volume is too low to reach 10 buyers as a solo founder with no network.

Mitigation

Fixed daily quota of 15 to 20 messages across LinkedIn, ROS Discourse and email, tracked in one sheet.

Validation experiment

Track reply rate by segment across batches one and two and cut the worst segment on day 14.

Kill criteria

If 60 contacts produce fewer than 6 replies by day 14, switch the primary channel before spending more days on it.

Risk 4Uploads fail or process slowly, generating refunds and support load.

Mitigation

Hard cap upload size, validate streams on arrival, auto-refund after two failed attempts, and keep the manual-intrinsics fallback path.

Validation experiment

Run five deliberately awkward videos through the pipeline on day 13 and count failures.

Kill criteria

If more than 30% of real uploads fail, pause outreach until the pipeline is stable.

Risk 5A single $99 transaction leaves too little revenue to matter in a 30-day window.

Mitigation

Push the $249 Team Pack from day 16 and the $49 re-certification credit from day 23.

Validation experiment

Price test $149 on five prospects between days 21 and 22 and record resistance.

Kill criteria

If no buyer upgrades to a Team Pack or re-cert by day 26, the repeat path is unproven and should be dropped rather than forced.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-3

  • Buy the domain and create the Next.js and FastAPI repositories.
  • Deploy both skeletons to Vercel and Render.

Output: Live skeleton URLs and a repo with CI-ready structure.

Hours 3-6

  • Create the Stripe account and product for the $99 Single Report.
  • Wire Checkout session creation and a webhook that sets job status to paid.

Output: A test-mode checkout that marks a database row as paid.

Hours 6-10

  • Build the upload endpoint for MP4 files.
  • Decode left and right frames with OpenCV and confirm sync.

Output: One uploaded video decoded into frame pairs.

Hours 10-14

  • Implement checkerboard detection and calibrateStereo.
  • Print reprojection and rectification error for the test video.

Output: Calibration numbers from a real stereo clip.

Hours 14-18

  • Run SGBM disparity, convert to depth, compute error at three distances.
  • Render the first heatmap PNG.

Output: A depth error heatmap image from real footage.

Hours 18-24

  • Assemble a rough PDF with ReportLab and email it to yourself.
  • Write the 40-contact outreach list skeleton and the DM draft.

Output: First end-to-end PDF certificate and a draft outreach list.

Complete report

Full 30-day launch report

Read the full generated report

1. Product opportunity and positioning

DepthCert sells a document, not a platform. The buyer is a robotics engineer at a 5-50 person manipulation or navigation startup who has just mounted a new stereo camera and has a demo or deployment on the calendar. That date is the trigger. Without it, engineers keep hacking OpenCV scripts on Friday afternoons and never pay for tooling.

The pain is measured in days, not dollars. A stereo bring-up means writing calibration code, guessing at acceptable error thresholds, and having nothing shareable to show a lead, a customer or a camera vendor when depth looks wrong. DepthCert converts a 10-30 second stereo video into a PDF certificate: intrinsics and extrinsics, a rectification check, depth error heatmaps at 0.5m, 1m and 2m, and a pass/fail table against thresholds such as <2% depth error at 1m.

Why now: a serverless Python job can produce a defensible measurement in under three minutes, and the output is a file. No API to adopt, no hardware to buy, no procurement cycle.

JEV scored the concept 52.4 / 100 (band C). The weakest criteria are market demand (2.92) and monetization (4.07); the strongest is speed to first revenue (7.70). This plan is shaped by that profile. Demand is addressed by narrowing to the pre-demo validation moment and naming it in every message. Monetization is addressed by keeping the first report cheap enough to be a card-swipe decision and adding a repeat path: Team Pack credits, re-certification after a lens or mount change, rig-to-rig comparison. Speed to revenue is spent immediately - outreach starts on day 8, not after polish.

Differentiation: free scripts exist and always will. They are unversioned, undocumented and unshareable. DepthCert wins by producing a standardized, comparable artifact, so two rigs can be compared and a result can be forwarded to someone who was not in the room.

This is not a live depth API, a real-time streaming service, or a calibration lab. It is a fast standardized sanity check with a paper trail, and every message must say so - overclaiming accuracy loses a robotics engineer on the first reply.

2. Smallest sellable MVP

One page, one upload, one payment, one PDF. The user pays $99, uploads a stereo video with baseline and focal length, and receives a certificate in under five minutes. Six features ship: upload, calibration with reprojection error, rectification check, SGBM depth with error at three distances, heatmaps, and a pass/fail table inside a PDF.

Explicitly excluded: live RTSP, multi-camera fusion, model training, SSO, hardware. Everything that turns a five-day build into a thirty-day build is out.

3. Technical implementation plan

Next.js on Vercel serves marketing, upload and dashboard. FastAPI on Render exposes create-job, upload and fetch-report. A Stripe webhook flips a job to paid before the worker touches it. A single Render worker polls a Postgres queue, runs OpenCV calibration and SGBM, renders heatmaps with NumPy and PNG output, then assembles the PDF with ReportLab into object storage. Uploads are deleted after 24 hours.

The hardest risk is user video that has no usable checkerboard or is badly synced. The fallback is manual intrinsics plus a self-consistency error check, and the PDF states which mode was used so it never overstates confidence. Build order runs day 1 to day 6, with the first full end-to-end paid job landing on day 5.

4. Pricing and monetization

Single Report at $99 one-time; Team Pack at $249 for three credits plus a comparison dashboard and priority queue. No subscription in the first 30 days - subscriptions require trust the product has not earned yet. The first revenue offer is a free sample on the prospect's own rig, then $99 for the full certificate, with $79 for the first ten responders as a launch concession.

Upsell path: single buyers with a second rig get the Team Pack; every certificate carries a $49 re-certification credit after a mount, lens or baseline change. Repeat purchase is the answer to JEV's monetization weakness, so it ships on day 16 and day 23 rather than being deferred.

5. First-customer acquisition

The channel is direct outreach plus one public technical post. Forty named contacts in week one from LinkedIn searches for perception and robotics engineers at small robotics companies, plus ROS Discourse calibration threads, r/robotics and public ROS package maintainers. Each message offers a free sample certificate on their own video - no signup, no demo call required.

Week-one goal: 40 contacts messaged, one ROS Discourse post live with a real sample PDF, and five free sample reports delivered on real customer footage. Every reply and objection is logged; the worst-performing message angle is cut after batch one. No paid ads until the organic message is proven.

6. Detailed 30-day execution roadmap

Days 1-6: build. Day 1 deploys the skeleton with test-mode Stripe. Day 2 handles upload and decode. Day 3 does calibration. Day 4 does disparity and error heatmaps. Day 5 assembles the PDF and delivers it by email. Day 6 ships the landing page with a public sample certificate.

Days 7-14: outreach and first sale. Day 7 builds the 40-contact list. Days 8-9 send 30 DMs and deliver two real sample reports. Day 10 follows up and posts technically. Day 11 sends checkout links with the discount ladder. Day 12 targets the first paying customer through a live screen share. Day 13 validates accuracy against two buyers' manual numbers. Day 14 audits the funnel and cuts the weakest angle.

Days 15-21: conversion and repeat path. Day 15 sends 20 more DMs into cobot integrators. Day 16 ships the Team Pack and comparison view. Day 17 runs three screen-share demos. Day 18 adds known-target accuracy mode. Day 19 publishes a results post and gallery. Day 20 closes the second paid cohort. Day 21 runs a price read at $149.

Days 22-30: scale and close. Day 22 sends 20 final-segment DMs and asks for referrals. Day 23 ships the $49 re-certification credit. Day 24 publishes an anonymised case. Day 25 runs the deadline push. Day 26 cuts processing below three minutes. Day 27 works second-rig expansion. Day 28 does the final outreach wave. Day 29 reconciles Stripe against TrustMRR. Day 30 confirms every payment landed before 13:00 UTC on December 16 and submits.

7. Revenue and profit scenarios

Projections only. Conservative: 3 customers at $99, $297 gross, no refunds, no chargebacks, $10 fees, no ad spend, $25 operating cost. Base: 10 customers at $99, $990 gross, $32 fees, $45 operating cost. Upside: 25 purchases at a $105 blended ARPU, $2,625 gross, one $50 refund, $84 fees, $150 ad spend, $90 operating cost. Hackathon profit ranks gross revenue minus refunds, chargebacks, fees and ad spend; business profit further subtracts hosting, domains and delivery compute. These are hypotheses, not results.

8. Main risks and validation experiments

Accuracy: if certificate depth error differs from a buyer's manual measurement by more than 25% on two rigs, stop selling and rebuild the metric. Willingness to pay: if 20 free samples yield zero follow-up questions and zero checkout clicks, demand is not there. Reach: if 60 contacts produce fewer than 6 replies by day 14, switch the primary channel. Reliability: if more than 30% of real uploads fail, pause outreach until the pipeline is stable. Deal size: if no buyer upgrades to a Team Pack or re-cert by day 26, drop the repeat path rather than force it.

9. First 24-hour action plan

Hours 1-3: buy the domain, create both repos, deploy skeletons. Hours 3-6: Stripe product and webhook that marks a job paid. Hours 6-10: upload endpoint and frame decode. Hours 10-14: checkerboard detection and calibrateStereo, printing reprojection error. Hours 14-18: SGBM, depth conversion, first heatmap PNG. Hours 18-24: rough PDF via ReportLab emailed to yourself, plus the outreach list skeleton and DM draft. By hour 24 there is a working certificate and a draft message, which is enough to start selling on day 7.

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 →