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

Rushes Inbox

A branded, no-login upload page that lets a video studio's clients push huge camera-card folders straight into the studio's own cloud bucket, resuming after drops and returning a checksum-backed arrival report.

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.29/10
MVP build (solo)
5 days
Launch price
$249
Sales to $1,000 revenue
5 customers
First paying customer
Direct outreach (DM or email) to small post houses found in public production-company directories and on their own Vimeo and Instagram pages.
Who pays

Owner or post-production supervisor at a 2-20 person video production or post house in the US, UK, Canada or Australia that receives client- or crew-shot footage every week.

Biggest execution risk

Operational simplicity 4.5/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

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; 5 sales at $249 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.1/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

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

0/11
Entry price
$249
Solo build
5 days
30d base revenue
$2,988
30d hackathon profit
$2,649
Section 1 of 8

Product opportunity and positioning

Target customer

Owner or post-production supervisor at a 2-20 person video production or post house in the US, UK, Canada or Australia that receives client- or crew-shot footage every week.

Why now

Studios already hold a cloud account and clients still send from laptops on consumer broadband, so the fix is one page and one report rather than a new transfer protocol or a storage subscription.

Problem

Receiving multi-hundred-GB camera-card folders is a recurring mess: browser uploaders stall or time out, share links expire mid-project, senders create duplicate folder trees, and nobody can prove which files landed intact.

Solution

The studio generates a permanent branded page in under two minutes; the client drags a whole card folder in, the browser uploads parallel chunks with presigned multipart URLs straight into the studio's own S3 or R2 bucket, resumes from a local manifest after a crash, hashes every file with SHA-256, and produces a shareable arrival report page plus PDF.

Differentiation · WeTransfer, Dropbox and raw bucket links expire, store footage on someone else's infrastructure and end with nothing provable; Rushes Inbox writes into the studio's own bucket and closes with a checksum-backed arrival report the studio can forward to the client.

Rushes Inbox - 30-Day Launch Report

Concept v1, scored 62.9/100 (band C) by JEV. Every financial figure in this report is a projection from stated assumptions, not verified revenue, customers or traction.

1. Product opportunity and positioning

The buyer. The owner or post-production supervisor at a 2-20 person video production house in the US, UK, Canada or Australia. This is the person who personally replies to the client's "where do I send the files?" message, this week, when a new project kicks off. They hold a company card and do not run procurement.

The pain, specifically. A client or a camera assistant turns up with a 300GB card dump. The studio sends a transfer link. Halfway through, the sender's laptop sleeps, the tab dies, or the link expires before the last folder goes up. The sender starts a second folder tree because they cannot tell what already landed. Nobody can prove which files arrived intact, so someone re-uploads overnight or ships a drive.

The product. One permanent branded page per studio, generated in under two minutes with the studio's logo, accent colour, project label and a short brief. The client opens it, drags a whole card folder in, and the browser uploads parallel chunks via presigned multipart URLs directly into the studio's own S3 or R2 bucket. A localStorage manifest keyed by file fingerprint resumes the send after a crash, sleep or bad Wi-Fi. Each file is hashed with SHA-256 in the browser. On completion both sides get an arrival report: file count, sizes, hashes, gaps and duplicates, as a shareable read-only link and a PDF.

Why it fits a 30-day solo window. The studio already owns the pain and already has (or can create) a cloud account. The output is one screen of product - a link and a report - not a platform. The first customer is reachable by a two-line DM with a live demo page attached, and the price is small enough to be approved on a card during a single call.

Why not the generic alternative. Free transfer tiers expire and hold the studio's footage somewhere the studio does not control. A raw bucket link proves nothing at the end and is unusable by a non-technical client. Rushes Inbox competes on the closing artifact rather than on a speed claim: a report the studio forwards to the client stating exactly what arrived, with hashes.

How this answers the JEV weaknesses. Monetization scored 4.6 and operational simplicity 4.51. Response: the price is anchored to a countable outcome (one avoided overnight re-upload costs more than the licence); the founder carries zero transfer infrastructure because footage never touches our servers, so there is no egress or storage exposure; and revenue expands by selling a second branded page to the same studio and by annual renewal at month 13, not by inventing new tiers before the first one sells.

2. Smallest sellable MVP

Four things and no more: a studio record with an encrypted bucket credential that passes a one-object test write; a branded public upload page with a resumable parallel chunk uploader; SHA-256 hashing per file into a manifest; and an arrival report page plus PDF behind a Stripe-gated activation code. Anything that does not produce a demonstrable resume-after-crash or a forwardable report is cut. No media player, no review tool, no desktop client, no seat management.

3. Technical implementation plan

Next.js on Vercel serves three surfaces: the studio dashboard, the public upload page and the read-only report. Neon Postgres holds studios, transfers and per-file manifest rows. The browser does the heavy lifting - presigned multipart requests with 5-50MB adaptive parts and four parallel workers - so Vercel only issues signatures and writes rows. Credentials are encrypted at rest with libsodium and never returned to the client. Resend sends three transactional emails per transfer. Reports are rendered as HTML and exported to PDF into R2. The hardest part is CORS and IAM correctness on the customer's bucket, so the plan spends dedicated time on a copy-paste policy guide and on returning readable errors instead of silent stalls.

4. Pricing and monetization

One tier: Studio Licence, $249 one-time, covering one branded permanent upload page, unlimited transfers for 12 months, the arrival report and a done-for-you bucket connection. The first-revenue offer is "I set up your page and connect your bucket tonight, free for 14 days, then $249 once if you keep it." Expansion: a second project page at the same price when a studio wants separate pages per show, and renewal in month 13.

5. First-customer acquisition

One channel, run hard: direct outreach to studios found in public production-company directories and on their own Vimeo and Instagram pages. Each message carries a working demo upload page and a 60-second recording that shows a 200GB folder resuming after a deliberate tab crash and ending on the arrival report. Target roughly 300 sends across 30 days, two follow-ups at day 3 and day 7, and one introduction request per activated studio.

6. 30-day execution roadmap

Days 1-5 build and ship the MVP, with the bucket-connect path deliberately finished on day 2 because it is the riskiest step. Day 6 hardens CORS failures and records the demo. Days 7-14 run the first 60 sends, book setup calls, run the first live bucket connections and push for the first card payment by day 12. Days 15-21 expand the prospect list to 120 studios, keep sending, and ship polish that came out of real calls. Days 22-28 continue outreach to roughly 300 cumulative sends, run a community show-and-tell only after three studios are live, and chase pending activations. Days 29-30 close, wrap and document. Full day-by-day entries are in the structured roadmap.

7. Revenue and profit scenarios

All three cases are projections built from the assumption of a $249 one-time licence, Stripe at 2.9% + $0.30, zero paid marketing in the conservative and base cases, and near-zero delivery cost because footage never lands on our infrastructure. Conservative: 4 customers, $996 gross. Base: 12 customers, $2,988 gross. Upside: 22 customers, $5,478 gross, including a $200 test spend in post-production newsletters. Hosting, database, email and PDF storage run $40-$140 across the window. Contest ranking uses gross revenue minus refunds, chargebacks, processing fees and ad spend, so the operating costs shown here reduce business profit only. These are hypotheses, not results.

8. Risks and validation experiments

Three risks dominate. First, owners may treat a transfer link as a commodity; the test is whether a live resume demo converts a cold DM into a call within 72 hours. Second, bucket setup friction (IAM keys, CORS, multipart permissions) can eat founder hours; the test is time-to-green-test-write on the first five real studios, with a kill threshold of 30 minutes per studio before the flow is reworked. Third, credential handling is a security exposure; mitigation is scoped keys, encrypted storage, a documented revoke step and never storing object data. If fewer than 3 of the first 60 contacted studios agree to a free setup, the offer or the audience is wrong and the concept should be re-cut before more sends.

9. First 24 hours

Confirm the rules page, register the domain, deploy the Next.js skeleton and connect the payment account to TrustMRR. Provision Neon, define the studio/transfer/manifest schema and prove presigned multipart upload against a test R2 bucket from a browser script. Add fifteen studios with owner names and contact links to the prospect sheet, then write the two-line DM and the 14-day offer so outreach can start the moment the demo page is live.

Section 2 of 8

Smallest sellable MVP

A working branded upload page for one studio that resumes a crashed 200GB folder into that studio's own bucket and ends with a forwardable, hashed arrival report - sold behind a $249 Stripe gate.

Must-have features

  • Encrypted per-studio S3/R2 credential with a one-object test write on save
  • Branded public upload page with logo, accent colour, project label and brief
  • Parallel presigned multipart chunker with adaptive 5-50MB parts
  • localStorage resume manifest keyed by file name, size and last modified
  • Streaming SHA-256 per file written to a per-transfer manifest
  • Shareable arrival report page and PDF listing files, sizes, hashes, gaps and duplicates
  • Stripe Checkout with activation-code gate on the dashboard
  • Resend emails on first byte, 10-minute stall and completion

Explicitly out of scope

  • Media asset manager, player or review-and-approve tooling
  • Desktop sync client, CLI or Finder integration
  • Storing or proxying customer footage on our infrastructure
  • Team seats, SSO, audit logs or procurement paperwork
  • Public marketplace or studio directory
  • Multi-provider support beyond AWS S3 and Cloudflare R2 at launch

Demo flow (what the buyer sees)

  1. Founder opens the studio dashboard and pastes bucket name, region, key and secret
  2. Test write of a single object runs and returns green
  3. Studio record saves with logo, accent colour, project label and brief
  4. Founder opens the public page and drags a 200GB card folder in
  5. Upload runs in parallel chunks; founder kills the tab mid-send
  6. Reopening the page resumes only the missing parts
  7. SHA-256 hashes complete and the arrival report page renders
  8. Founder exports the PDF and forwards the share link
Build plan

Technical implementation plan

Stack

Next.js on VercelCloudflare R2 and AWS S3 presigned multipart APIsNeon PostgresBrowser WebCrypto SHA-256 plus a TypeScript chunk workerlibsodium for credential encryptionStripe CheckoutResendR2 for generated PDF reports

Architecture

Vercel hosts the dashboard, the public upload page and the read-only report route. Neon stores studios, transfers and one row per file. The browser asks our API for presigned part URLs and PUTs bytes directly to the studio's bucket, so no footage traverses our infrastructure. Credentials are encrypted with libsodium and never leave the server. Manifest rows are written as parts complete, and a localStorage record keyed by file fingerprint lets a reopened page resume. Reports are assembled from manifest rows and exported to PDF into R2.

Build steps

  1. Create Next.js app, Neon schema and Vercel deployment
  2. Build studio onboarding form with encrypted credentials and one-object test write
  3. Write S3 and R2 CORS and IAM policy guide with copy-paste JSON
  4. Render the public branded upload page from the studio record
  5. Implement presigned multipart chunker with parallel workers and adaptive part size
  6. Add localStorage resume manifest and reload recovery
  7. Stream SHA-256 per file during upload into the manifest
  8. Build arrival report page and PDF export
  9. Add Stripe Checkout plus activation-code gate
  10. Add Resend notifications for first byte, stall and completion
  11. Harden error surfaces for CORS, expired presigns and permission failures
  12. Load-test with a real 200GB folder and record the demo

AI components

  • No model inference in the core product; an optional LLM pass to summarise the arrival report into one plain-English sentence for the client email is deferred past day 30
Hardest technical risk: Customer bucket CORS and multipart permission misconfiguration that presents as a silent stall, making our product look broken during a live setup call.
Section 3 of 8

Pricing and monetization

Studio Licence

Entry offer
$249 one-time

For Owner or post supervisor at a 2-20 person production or post house

  • One branded permanent upload page with logo and brief
  • Unlimited transfers for 12 months
  • Resumable parallel browser uploads direct to the studio's own bucket
  • Checksum-backed arrival report page and PDF
  • Done-for-you bucket connection on a call

Model: Single one-time studio licence per branded page, sold after a free 14-day done-for-you setup.

First revenue offer: I will set up your branded upload page and connect your own bucket tonight, free for 14 days. If a client send goes through cleanly, it is $249 once and you keep the page for 12 months.

Expected ACV: $249

Upsell path: A second branded page for a separate show at $249, referral introductions from activated studios, and renewal at month 13.

Target customers
12
Revenue model
$2,988
Costs
$75
Profit model
$2,913
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach (DM or email) to small post houses found in public production-company directories and on their own Vimeo and Instagram pages.

Where to find them

  • Public production-company directories filtered to 2-20 staff
  • Studio Instagram bios and contact links
  • Vimeo staff-picked and regional production showcases
  • Credits pages of recently released indie films and branded-content work
  • Local film commission member lists
  • Post-production Slack and Discord communities (read-only until three studios are live)

Exact outreach motions

  • Send a two-line DM with the demo upload page link and the 60-second resume recording attached
  • Offer the free 14-day done-for-you setup with a specific night named in the message
  • Follow up at day 3 with one line asking what their current send process is
  • Follow up at day 7 with the arrival report PDF from a real test transfer
  • Ask every activated studio for one peer introduction in exchange for a second project page free

Message template

Hi {name} - saw {studio} handles {type of work}. I built a branded upload page that drops client card folders straight into your own S3/R2 bucket, resumes if the sender's laptop dies, and emails a hashed arrival report. Here is a live one: {demo link}. Want me to set yours up tonight, free for 14 days?
Week-one goal: 40 studios listed with named contacts, 20 messages sent, 3 replies and 1 booked setup call.
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

Ship the skeleton and start the list

  • Register domain, create the Next.js repo, deploy to Vercel, provision Neon Postgres.
  • Create Stripe account and connect the payment account to TrustMRR before any customer exists.
  • Start the prospect sheet with 15 studios and named contacts.

Deliverable: Live empty app at the domain, connected payment account and a 15-row prospect sheet.

Day 2Bucket connection

Make the riskiest step work first

  • Build the credential form for bucket name, region, access key and secret with libsodium encryption.
  • Run a one-object test write on save and show a clear pass or fail.
  • Write the copy-paste CORS and IAM policy guide for S3 and R2.

Deliverable: A real bucket connects and returns a green test write.

Day 3Upload engine

Chunked parallel uploads

  • Render the branded public page from the studio record.
  • Implement presigned multipart uploads at 25MB parts with four parallel workers.
  • Record completed parts into the manifest table as they finish.

Deliverable: A 20GB folder lands in a real R2 bucket from the browser.

Day 4Resume and checksums

The deciding feature

  • Persist a localStorage manifest keyed by file fingerprint and resume only missing parts on reload.
  • Stream SHA-256 per file with WebCrypto during upload.
  • Kill the tab mid-send and confirm resume works.

Deliverable: A 200GB folder resumes after a deliberate crash with matching hashes.

Day 5Report, payment, emailMVP shipped

Complete the sellable loop

  • Build the arrival report page and PDF export with files, sizes, hashes, gaps and duplicates.
  • Wire Stripe Checkout and the activation-code gate on the dashboard.
  • Add Resend emails on first byte, 10-minute stall and completion.

Deliverable: End-to-end paid demo: page, upload, report, receipt.

Day 6Hardening and demo

Make failures readable

  • Surface CORS and permission errors as plain sentences instead of silent stalls.
  • Add a mobile and iPad warning banner before upload.
  • Record the 60-second screen recording ending on the arrival report.

Deliverable: Public demo page plus a 60-second video.

Day 7Outreach batch 1

First sends

  • Expand the prospect sheet to 40 studios with owner names and contact links.
  • Send 10 two-line messages with the recording and the free setup offer.

Deliverable: 40 prospects, 10 sends, first replies.

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

Convert replies to calls

  • Send 10 more messages.
  • Follow up the day-7 batch with one line about their current send process.
  • Book three setup calls.

Deliverable: 20 sends total and three booked calls.

Day 9First live onboarding

Prove setup on a real studio

  • Run the first setup call and connect a real customer bucket.
  • Record the exact steps that took longest.
  • Publish the self-serve connect-your-bucket guide.

Deliverable: One studio live on its own bucket.

Day 10Outreach volume

Message iteration

  • Send 10 more messages with the revised first line.
  • Rewrite the template based on the strongest reply so far.

Deliverable: 30 sends and a revised template.

Day 11Free setups

Put pages in front of clients

  • Run free 14-day setups for three warm studios.
  • Ask each to trigger one real client send this week.

Deliverable: Three studios live, each with a scheduled client send.

Day 12First closeFirst sale target

Convert the first licence

  • Ask the studio whose send succeeded to pay the $249 on the call.
  • Send the Checkout link while still on the call.
  • Activate the licence code on payment.

Deliverable: First paid Studio Licence.

Day 13Fix friction

Remove the top onboarding blocker

  • Fix the single most common setup failure seen on calls.
  • Update the CORS guide with the real error text seen.

Deliverable: Setup time under 20 minutes on a fresh studio.

Day 14Review and intros

Compound the wins

  • Ask every live studio for one peer introduction.
  • Review reply and conversion rates per message variant.

Deliverable: Two introductions and a ranked message list.

Week 3 · Repeat & systematize · 7 days
Day 15List expansion

Reach 120 studios

  • Expand the prospect sheet to 120 studios with named contacts.
  • Segment by city and by whether they run their own bucket.

Deliverable: 120-row prospect sheet.

Day 16Outreach

Volume with a proven message

  • Send 20 messages using the winning variant.
  • Log replies in the sheet same day.

Deliverable: 20 sends, reply rate logged.

Day 17Outreach and calls

Book the week's calls

  • Send 20 messages.
  • Run two setup calls.

Deliverable: Two more studios connected.

Day 18Product polish

Ship what calls demanded

  • Add studio logo and accent colour to the report PDF.
  • Improve duplicate detection messaging in the report.

Deliverable: Branded report PDF shipped.

Day 19Outreach

Keep the pipeline moving

  • Send 20 messages.
  • Follow up all day-15 and day-16 sends.

Deliverable: 20 sends and 40 follow-ups.

Day 20Outreach and referrals

Warm path only

  • Send 20 messages, half via introductions.
  • Ask live studios to forward the report link to their clients.

Deliverable: 20 sends and two forwarded reports.

Day 21Conversion audit

Find the leak

  • Compute reply, call and payment rates per channel slice.
  • Cut the worst-performing segment.

Deliverable: Funnel table with the next segment chosen.

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

Push toward 250 cumulative sends

  • Send 25 messages.
  • Add 40 new studios from a second directory source.

Deliverable: 25 sends and 160-row sheet.

Day 23Community proof

Show, do not tell

  • Post the resume recording as a plain show-and-tell in editor and post communities.
  • Reply to every comment with the demo link.

Deliverable: One community post live with tracked link.

Day 24Outreach

Keep sending

  • Send 25 messages.
  • Follow up all day-22 sends.

Deliverable: 25 sends and 25 follow-ups.

Day 25Onboarding day

Batch the setups

  • Run four setup calls in one block.
  • Fix any recurring CORS failure the same day.

Deliverable: Four studios connected.

Day 26Outreach

Final volume push

  • Send 25 messages to the newest segment.
  • Ask two live studios for a one-line testimonial.

Deliverable: Roughly 300 cumulative sends.

Day 27Payment chase

Collect what is owed

  • Resend Checkout links to every studio past day 12 of its free setup.
  • Confirm every payment landed inside the contest window.

Deliverable: All live studios invoiced or paid.

Day 28Funnel audit

Know the real numbers

  • Recompute profit with actual refunds and Stripe fees.
  • Identify which single message produced the most paid studios.

Deliverable: Working profit table reconciled to Stripe.

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

Last conversions

  • Call every warm studio still undecided.
  • Offer the free setup to any studio that replied but never scheduled.

Deliverable: Final payment batch collected.

Day 30Wrap

Handoff and next 30 days

  • Export the customer list, transfer manifests and renewal dates.
  • Write the next-30-day plan around the best-converting segment.

Deliverable: Close-out document and next-month plan.

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 three cases use the same single offer: $249 one-time Studio Licence after a free 14-day done-for-you setup.
  • Conservative: roughly 300 sends convert at about 1.3%, giving 4 paid studios.
  • Base: roughly 300 sends convert at about 4%, giving 12 paid studios, in line with the concept target.
  • Upside: 22 paid studios from the same sends plus referral introductions and one community post.
  • Payment processing assumed at Stripe 2.9% + $0.30 per transaction, about 3% effective at a $249 price.
  • Refund rate assumed under 10% because payment follows a free setup; conservative and base carry zero refunds, upside carries two.
  • No chargebacks modelled in any case; disputes are handled by refund before escalation.
  • Paid marketing is $0 in conservative and base; upside carries a $200 test spend in post-production newsletters.
  • Operating costs cover Vercel, Neon, Resend, domain, encryption tooling and PDF storage; these do not count against contest profit but do reduce business profit.
  • Delivery cost per customer stays near zero because footage goes from the client's browser to the studio's own bucket, never through our infrastructure.
  • No existing customers, revenue, partnerships or traction is claimed; every number here is a projection.

Conservative

4 customers
$996
collected revenue · avg payment $249
Refunds
$0
Chargebacks
$0
Payment fees
$30
Paid marketing
$0
Hackathon profit
$966
Operating costs
$40
Business profit
$926

Base case

12 customers
$2,988
collected revenue · avg payment $249
Refunds
$249
Chargebacks
$0
Payment fees
$90
Paid marketing
$0
Hackathon profit
$2,649
Operating costs
$75
Business profit
$2,574

Optimistic

22 customers
$5,478
collected revenue · avg payment $249
Refunds
$498
Chargebacks
$0
Payment fees
$165
Paid marketing
$200
Hackathon profit
$4,615
Operating costs
$140
Business profit
$4,475

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,988
Payment fees (3.9%)
$117
Paid marketing
$0
Hackathon profit
$2,871
Business profit
$2,796

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

All scenarios are projections derived from the stated assumptions. They are not verified revenue, customers or traction, and results may differ materially.

Section 7 of 8

Main risks and validation experiments

Risk 1Owners treat a transfer link as a commodity and refuse to pay $249 when free tiers exist.

Mitigation

Lead every message with the resume-after-crash recording and the arrival report, never with a speed claim; anchor the price to one avoided overnight re-upload.

Validation experiment

Send 20 messages in week one and count how many replies lead to a booked setup call within 72 hours.

Kill criteria

Fewer than 3 of the first 60 contacted studios accept a free setup - re-cut the offer or the audience before sending more.

Risk 2Bucket setup friction (IAM keys, CORS, multipart permissions) consumes founder hours and stalls onboarding.

Mitigation

Ship the copy-paste CORS and IAM guide on day 2, surface readable errors instead of silent stalls, and offer a done-for-you connection on a call.

Validation experiment

Time time-to-green-test-write on the first five real studios and log the exact failure text each one hits.

Kill criteria

Median setup time above 30 minutes after five studios - stop outreach and rebuild the connection flow as a guided wizard.

Risk 3Holding customer cloud credentials creates a security incident exposure a solo founder cannot insure against.

Mitigation

Require scoped write-only keys, encrypt with libsodium, never expose secrets to the browser, and document a one-step revoke procedure for the studio.

Validation experiment

Write the revoke procedure, have one studio rotate its key using it, and confirm uploads fail cleanly afterwards.

Kill criteria

Any evidence of a credential leak, or a studio unwilling to issue a scoped key - pause paid onboarding until the model changes.

Risk 4Senders on locked-down corporate laptops or iPads cannot run a large browser upload, weakening the demo.

Mitigation

Detect constrained environments, show a clear notice, and offer a folder-by-folder send path with the same resume behaviour.

Validation experiment

Ask five live studios whether any client send failed for device or network reasons in the first two weeks.

Kill criteria

More than one third of real client sends fail for environment reasons - revisit whether a browser-only sender is viable.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Read the official rules page and confirm the contest window and profit definition.
  • Register the domain and create the Next.js repository.
  • Open the payment account and connect it to TrustMRR.

Output: Domain, repository and a connected payment account with zero customers.

Hours 3-5

  • Provision Neon Postgres and write the studios, transfers and file_manifest schema.
  • Deploy the skeleton to Vercel and confirm the public route resolves.

Output: Live URL plus a migrated database.

Hours 6-8

  • Create a test R2 bucket.
  • Run a browser script that presigned-multiparts a 2GB test file into it.

Output: Proof that the core upload path works end to end.

Hours 9-11

  • Build the prospect sheet with 15 studios, owner names and contact links.
  • Draft the two-line message and the 14-day free setup offer.

Output: 15-row prospect sheet and a ready-to-send message.

Hours 12-14

  • Write the CORS and IAM policy guide for S3 and R2.
  • Plan day 2's credential form and test-write check.

Output: Published setup guide and a day 2 build checklist.

Complete report

Full 30-day launch report

Read the full generated report

Rushes Inbox - 30-Day Launch Report

Concept v1, scored 62.9/100 (band C) by JEV. Every financial figure in this report is a projection from stated assumptions, not verified revenue, customers or traction.

1. Product opportunity and positioning

The buyer. The owner or post-production supervisor at a 2-20 person video production house in the US, UK, Canada or Australia. This is the person who personally replies to the client's "where do I send the files?" message, this week, when a new project kicks off. They hold a company card and do not run procurement.

The pain, specifically. A client or camera assistant turns up with a 300GB card dump. The studio sends a transfer link. Halfway through, the sender's laptop sleeps, the tab dies, or the link expires before the last folder goes up. The sender starts a second folder tree because they cannot tell what already landed. Nobody can prove which files arrived intact, so someone re-uploads overnight or ships a drive.

The product. One permanent branded page per studio, generated in under two minutes with the studio's logo, accent colour, project label and a short brief. The client opens it, drags a whole card folder in, and the browser uploads parallel chunks via presigned multipart URLs directly into the studio's own S3 or R2 bucket. A localStorage manifest keyed by file fingerprint resumes the send after a crash, sleep or bad Wi-Fi. Each file is hashed with SHA-256 in the browser. On completion both sides get an arrival report: file count, sizes, hashes, gaps and duplicates, as a shareable read-only link and a PDF.

Why it fits a 30-day solo window. The studio already owns the pain and already has (or can create) a cloud account. The output is one screen of product - a link and a report - not a platform. The first customer is reachable by a two-line DM with a live demo page attached, and the price is small enough to be approved on a card during a single call.

Why not the generic alternative. Free transfer tiers expire and hold the studio's footage somewhere the studio does not control. A raw bucket link proves nothing at the end and is unusable by a non-technical client. Rushes Inbox competes on the closing artifact rather than on a speed claim: a report the studio forwards to the client stating exactly what arrived, with hashes.

How this answers the JEV weaknesses. Monetization scored 4.6 and operational simplicity 4.51. Response: the price is anchored to a countable outcome (one avoided overnight re-upload costs more than the licence); the founder carries zero transfer infrastructure because footage never touches our servers, so there is no egress or storage exposure; and revenue expands by selling a second branded page to the same studio and by renewal at month 13, not by inventing new tiers before the first one sells.

2. Smallest sellable MVP

Four things and no more: a studio record with an encrypted bucket credential that passes a one-object test write; a branded public upload page with a resumable parallel chunk uploader; SHA-256 hashing per file into a manifest; and an arrival report page plus PDF behind a Stripe-gated activation code. Anything that does not produce a demonstrable resume-after-crash or a forwardable report is cut. No media player, no review tool, no desktop client, no seat management, no storage resale.

3. Technical implementation plan

Next.js on Vercel serves three surfaces: the studio dashboard, the public upload page and the read-only report. Neon Postgres holds studios, transfers and per-file manifest rows. The browser does the heavy lifting - presigned multipart requests with 5-50MB adaptive parts and four parallel workers - so Vercel only issues signatures and writes rows. Credentials are encrypted at rest with libsodium and never returned to the client. Resend sends three transactional emails per transfer. Reports render as HTML and export to PDF into R2. The hardest part is CORS and IAM correctness on the customer's bucket, so the plan spends dedicated time on a copy-paste policy guide and on returning readable errors instead of silent stalls.

4. Pricing and monetization

One tier: Studio Licence, $249 one-time, covering one branded permanent upload page, unlimited transfers for 12 months, the arrival report and a done-for-you bucket connection. The first-revenue offer is "I set up your page and connect your bucket tonight, free for 14 days, then $249 once if you keep it." Expansion comes from a second project page at the same price when a studio wants separate pages per show, from referral introductions, and from renewal in month 13. No recurring tier exists at launch because the buyer is not yet trained to accept one, and a subscription fails the 30-day cash test.

5. First-customer acquisition

One channel, run hard: direct outreach to studios found in public production-company directories and on their own Vimeo and Instagram pages. Each message carries a working demo upload page and a 60-second recording that shows a 200GB folder resuming after a deliberate tab crash and ending on the arrival report. The plan targets roughly 300 sends across 30 days, two follow-ups at day 3 and day 7, and one introduction request per activated studio. No ads, no SEO, no partnerships, no marketplace cold start.

6. 30-day execution roadmap

Days 1-5 build and ship the MVP, with the bucket-connect path deliberately finished on day 2 because it is the riskiest step. Day 6 hardens CORS failures and records the demo. Days 7-14 run the first 60 sends, book setup calls, run the first live bucket connections and push for the first card payment by day 12. Days 15-21 expand the prospect list to 120 studios, keep sending daily, and ship polish that came out of real calls. Days 22-28 continue outreach toward roughly 300 cumulative sends, run a community show-and-tell only after three studios are live, and chase pending activations. Days 29-30 close, reconcile the profit numbers against Stripe, and document the next month.

7. Revenue and profit scenarios

All three cases are projections built from the assumption of a $249 one-time licence, Stripe at 2.9% + $0.30, zero paid marketing in the conservative and base cases, and near-zero delivery cost because footage never lands on our infrastructure. Conservative: 4 customers, $996 gross. Base: 12 customers, $2,988 gross. Upside: 22 customers, $5,478 gross, including a $200 test spend in post-production newsletters. Hosting, database, email and PDF storage run $40-$140 across the window. Contest ranking uses gross revenue minus refunds, chargebacks, processing fees and ad spend, so the operating costs shown here reduce business profit only. These are hypotheses, not results, and they must be re-checked against Stripe on day 28.

8. Risks and validation experiments

Three risks dominate. First, owners may treat a transfer link as a commodity; the test is whether a live resume demo converts a cold DM into a booked setup within 72 hours, with a kill threshold of fewer than 3 of the first 60 studios accepting a free setup. Second, bucket setup friction can eat founder hours; the test is median time-to-green-test-write on the first five real studios, and above 30 minutes the connection flow gets rebuilt before more outreach. Third, credential handling is a security exposure; mitigation is scoped keys, encrypted storage, a documented revoke step and never storing object data, validated by having one studio rotate its key using our procedure. A fourth watch item is device constraints: if more than a third of real client sends fail for environment reasons, revisit whether a browser-only sender is viable.

9. First 24 hours

Confirm the rules page, register the domain, deploy the Next.js skeleton and connect the payment account to TrustMRR. Provision Neon, define the studio, transfer and file_manifest schema, then prove presigned multipart upload against a test R2 bucket from a browser script before writing any product surface. Add fifteen studios with owner names and contact links to the prospect sheet, write the two-line DM and the 14-day offer, and publish the CORS and IAM guide so day 2 starts with the riskiest integration, not with copywriting.

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 →