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

CallSheet Locker

CallSheet Locker turns one no-login availability link into a locked shoot date and a ready-to-send call sheet PDF for small podcast and video studios.

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.98/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Hand-built cold list of 150 small podcast and video studios from Google Maps and Instagram bios, contacted with a done-for-you free first shoot.
Who pays

Owner-producer of a 1-5 person podcast or video studio in the US, UK, Canada or Australia running 2-8 multi-person shoots a month, who personally schedules host, guest, freelancer and client after a shoot took 9-15 emails and two reschedules to get four people in one room.

Biggest execution risk

Market demand 3.8/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.2/10.

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

Your first 24 hours

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

0/10
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

Owner-producer of a 1-5 person podcast or video studio in the US, UK, Canada or Australia running 2-8 multi-person shoots a month, who personally schedules host, guest, freelancer and client after a shoot took 9-15 emails and two reschedules to get four people in one room.

Why now

A solo producer can buy at the export moment with one card entry, Stripe Checkout needs no procurement, and the deliverable is standard industry paperwork rather than a new habit to learn.

Problem

Multi-person shoot scheduling lives across email, SMS and WhatsApp, then the producer retypes the confirmed date into a Google Docs call sheet for every shoot; a reschedule silently breaks the call sheet, guests arrive at the wrong call time and freelancers get double-booked.

Solution

The producer creates a shoot with roles, a date window and per-role constraints, sends one tokenized link per participant, locks the winning slot, and gets a branded call sheet PDF plus .ics invites and confirmation emails for every role.

Differentiation · Polls and group texts answer when people are free; CallSheet Locker ends the thread with the artifact the shoot needs — locked date, per-role call times and a call sheet PDF — with no participant accounts.

CallSheet Locker — 30-Day Launch Report

1. Product opportunity and positioning

CallSheet Locker serves exactly one buyer: the owner-producer of a 1-5 person podcast or video studio in the US, UK, Canada or Australia who personally schedules 2-8 multi-person shoots a month. The trigger event is specific and expensive — a shoot that took 9-15 emails and two reschedules to get four people into one room, followed by the producer retyping the confirmed date into a Google Docs call sheet while a studio slot and a client relationship sit in the balance.

Existing tools stop at the poll. Doodle, When2Meet and group texts answer when people are free. None of them produce the artifact the shoot needs: a locked date, per-role call times, a contact block, notes and a call sheet PDF that host, guest, freelancer and client can all read without an account. CallSheet Locker is the last step of that thread, not a competing calendar. Participants receive one tokenized link and a tap grid on a phone; nobody installs anything or signs in.

The wedge is the paywall position. The gate sits on the PDF export — the exact second the producer has a confirmed date and needs the call sheet — so the purchase decision is one card entry at the moment of highest intent. The buyer is a single owner-operator, so there is no procurement, no security review and no seat negotiation. The deliverable is standard industry paperwork, which means zero education cost: a producer already knows what a call sheet is and already makes one badly every week.

This is not the original consumer social calendar. Participants get no calendar, no account and no app; the output is a professional document and a one-time workspace purchase rather than a free social product.

2. Smallest sellable MVP

One workflow, end to end: create a shoot with roles and a date window, send no-login availability links, see ranked overlapping slots with gaps named explicitly, lock a slot, pay $99, receive a branded call sheet PDF plus .ics files and confirmation emails. Everything else is out of scope for week one — no native apps, no two-way Google Calendar OAuth, no chat, no crew marketplace, no team permissions.

3. Technical implementation plan

Next.js on Vercel, Postgres via Supabase free tier, Stripe Checkout with a webhook license check, Resend for transactional email, @react-pdf/renderer for the call sheet, the ics package for invites, Tailwind for the interface. The architecture is deliberately thin: shoot and participant records in Postgres, availability stored as slot arrays, the overlap solver computed server-side rather than in the browser, PDF rendering on a serverless route, one webhook that flips a workspace from unpaid to licensed. Build order is schema, shoot builder, participant grid, solver, PDF, then payments and email last so the gate is never the blocker. The hardest technical risk is PDF layout fidelity — a plain-looking call sheet makes the product feel cheap — so the template gets built on day four, not day five, and is checked against a real studio call sheet.

4. Pricing and monetization

The core offer is Studio Year at $99 one-time: unlimited shoots for twelve months, no-login links, branded PDF export, ICS and emails. Agency Year at $249 adds five seats, client-branded templates and reusable crew defaults, and is treated as upside only. There is no free tier during the contest; the free thing is the founder's concierge setup of a studio's next shoot, which converts in the same email thread. Revenue grows through Agency Year upgrades from studios already running client work and through renewal in month thirteen, which is outside the 30-day window.

5. First-customer acquisition

One channel: a hand-built 150-row list of small podcast and video studios from Google Maps and Instagram bios across ten mid-size cities, contacted with a done-for-you offer. The message never leads with software. It leads with the outcome: send one link, get a locked date and a call sheet PDF in ten minutes, and the founder will do the next shoot free. The same offer goes into r/podcasting's weekly thread, one indie production Discord or Slack, and two studio-owner Facebook groups. Deliverability is guarded by sending small batches from a warmed domain, personalizing the first line with the studio name, and following up once at 48 hours with the generated call sheet attached as proof rather than a pitch.

6. 30-day execution roadmap

Week one is build and list. Days 1-5 ship the MVP to a live domain by the day-five deadline. Days 6-7 build the 150-row contact list and send the first 25 messages. Week two is proof: concierge three free call sheets, send 60 more messages, post in communities, and push the warmest threads to a Stripe link targeting the first sale on day 12. Week three scales the message that worked, publishes a redacted before-and-after call sheet as the case artifact, ships the reschedule flow to cut refunds, and lists the Agency Year tier. Week four is volume plus hygiene: two more outreach batches, a short landing page for the call sheet template search, explicit refund terms, delivery proof on every sale, and one upgrade push to existing buyers. Days 29-30 close open threads, reconcile every payment against TrustMRR, and cut any activity that produced no replies.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 Studio Year sales at $99, $297 gross, roughly $10 processing, no ad spend, $25 operating cost. Base: 10 sales, $990 gross, about $32 processing, $45 operating cost. Upside: 25 sales, $2,475 gross, one refund at $99, about $111 processing on a blended 4.5 percent rate, $150 of paid promotion, $90 operating cost. The contest ranks collected revenue minus refunds, chargebacks, processing fees and paid marketing; hosting, domains and AI or PDF delivery costs are not deducted for ranking but are tracked as operating cost so the business math stays honest. Every sale must clear its own delivery cost, and at $99 against roughly three dollars of marginal processing plus negligible infrastructure, it does.

8. Risks and validation experiments

Three risks drive the plan. First, free incumbents being judged good enough — tested by whether cold studios reply to a call-sheet-first message rather than a scheduling message. Second, cold email deliverability collapsing the funnel — tested by sending 25 messages on day seven and measuring replies before scaling to 150. Third, PDF quality failing to justify $99 — tested by hand-delivering three concierge call sheets and observing whether the producer forwards them to their own crew. A concept is killed or reshaped if 150 personalized messages produce fewer than four replies, or if twenty delivered free call sheets produce zero paid conversions.

9. First 24-hour action plan

Hours 1-2: create the Supabase project and migrate the shoot, role, participant, availability and order tables. Hours 3-5: scaffold Next.js with Tailwind, ship the landing page with the free-first-shoot offer, connect the domain. Hours 6-8: build the shoot creation form against real test data from one studio's last shoot. Hours 9-10: draft the two cold message variants and start the 150-row list in a spreadsheet. Hours 11-12: deploy to Vercel, run one end-to-end dry run, and send the first five messages.

Section 2 of 8

Smallest sellable MVP

A producer creates a shoot with roles and a date window, sends no-login availability links, locks the winning slot, pays $99 through Stripe Checkout, and receives a branded call sheet PDF with .ics invites and confirmation emails for every role.

Must-have features

  • Shoot builder with title, location, date window and roles with required or optional flags
  • Per-role day constraints so a guest who can only do Tuesdays is respected by the solver
  • Tokenized no-login availability link per participant with a mobile-first tap grid
  • Overlap solver that ranks slots by required-role coverage and names the remaining gaps
  • Lock action that generates a branded call sheet PDF with per-role call times, contacts, notes and a shot list stub
  • Logo upload and default crew list stored per workspace
  • ICS file per participant plus Google Calendar add links
  • Confirmation email to every role via Resend with the PDF attached and a reschedule link
  • Stripe Checkout gate on PDF export with a webhook license check
  • Workspace dashboard listing past shoots and their locked dates

Explicitly out of scope

  • Native iOS or Android apps
  • Two-way Google or Outlook OAuth calendar sync
  • In-app chat, comments or crew payments
  • Crew marketplace or discovery directory
  • Automated timezone detection beyond a manual per-participant setting
  • Team permissions, SSO or enterprise admin
  • Free tier or trial accounts
  • Invoice or purchase-order billing

Demo flow (what the buyer sees)

  1. Producer signs in and creates a shoot titled Episode 41 with location, a 6-day date window and four roles.
  2. Producer marks host and camera op as required and adds a Tuesday-only constraint to the guest.
  3. System generates one tokenized link per participant; producer pastes them into an existing email thread.
  4. Each participant taps their free blocks on a phone grid; no account is created.
  5. Solver returns ranked overlapping slots with explicit gaps such as guest unavailable Thursday.
  6. Producer locks Thursday 14:00; Stripe Checkout opens on the PDF export.
  7. Payment clears; the branded call sheet PDF renders with per-role call times and the studio logo.
  8. Resend sends the PDF and .ics to all four roles with a reschedule link.
Build plan

Technical implementation plan

Stack

Next.js 14 on VercelPostgres via Supabase free tierStripe Checkout plus webhook license checkResend for transactional email@react-pdf/renderer for call sheet PDFics npm package for calendar filesTailwind CSSSupabase row-level security on token routes

Architecture

A single Next.js app serves the producer dashboard and the public tokenized participant routes. Postgres holds shoots, roles, participants, availability blocks and orders. Token routes are unauthenticated but scoped by a random 32-character token, and submissions write only to the matching participant row. The overlap solver runs server-side on demand, intersecting availability arrays against required roles and returning ranked slots. PDF rendering happens in a dedicated serverless route after the Stripe webhook marks the workspace licensed. Resend delivers the PDF and ICS attachments, and every generated file is stored against the shoot for resend.

Build steps

  1. Create Supabase project, migrate shoots, roles, participants, availability and orders tables with token indexes.
  2. Scaffold Next.js and Tailwind, deploy the landing page with the free-first-shoot offer to the live domain.
  3. Build the shoot creation form with role rows, required flags and per-role day constraints.
  4. Generate participant tokens and the public tap-grid route; persist submissions without accounts.
  5. Implement the overlap solver: intersect availability, rank by required-role coverage, list gaps by name.
  6. Build the call sheet PDF template with logo, per-role call times, contacts, notes and shot list stub.
  7. Add ICS generation and Google Calendar add links per participant.
  8. Wire Stripe Checkout on the export action and a webhook that flips the workspace to licensed.
  9. Add Resend confirmation emails with PDF and ICS attachments plus a reschedule link.
  10. Run three end-to-end dry runs on real studio data, then fix layout defects before any outreach.

AI components

  • No LLM in the core loop; the shot list stub is template text the producer edits
  • Optional: a single model call to summarize free-text notes into a shot list stub, capped and non-blocking
Hardest technical risk: PDF layout fidelity across four roles and variable note lengths; a plain or misaligned call sheet makes a $99 purchase feel cheap, so the template is built and reviewed on day four against a real studio document.
Section 3 of 8

Pricing and monetization

Studio Year

Entry offer
$99 one-time

For Owner-producer of a 1-5 person podcast or video studio

  • Unlimited shoots for 12 months
  • No-login availability links per participant
  • Branded call sheet PDF export
  • ICS invites and confirmation emails

Agency Year

$249 one-time

For 3-10 person production company or freelancer collective running client shoots

  • 5 workspace seats
  • Client-branded call sheet templates
  • Reusable crew and role defaults
  • Unlimited shoots for 12 months

Model: One-time annual workspace license, paid at the call sheet export moment via Stripe Checkout.

First revenue offer: Send one link, get a locked shoot date and a branded call sheet PDF in ten minutes. I will run your next shoot free and put your logo on the call sheet. If it saves you the hour, Studio Year is $99 for twelve months.

Expected ACV: $99

Upsell path: Existing Studio Year buyers running client work upgrade to Agency Year at $249 for seats and client-branded templates; renewal lands in month thirteen outside the contest window.

Target customers
30
Revenue model
$2,970
Costs
$130
Profit model
$2,840
Section 4 of 8

First-customer acquisition

Primary channel

Hand-built cold list of 150 small podcast and video studios from Google Maps and Instagram bios, contacted with a done-for-you free first shoot.

Where to find them

  • Google Maps search for podcast studio across ten mid-size US, UK, Canada and Australia cities
  • Google Maps search for video production and recording studio in the same cities
  • Instagram bios of studio accounts that list a booking email
  • r/podcasting weekly thread
  • One indie production Discord or Slack
  • Two podcast studio owner Facebook groups
  • Existing studio booking pages that publish a contact email
  • Freelance camera operator accounts that tag the studios they shoot for

Exact outreach motions

  • Send 25 personalized cold emails per batch, first line naming the studio and one recent episode or client video.
  • Offer to run their next multi-person shoot free and deliver the call sheet PDF with their logo.
  • Follow up once at 48 hours with the generated call sheet attached as proof, no new pitch.
  • Post the same free-first-shoot offer in r/podcasting, one Discord and two Facebook groups.
  • After delivering a concierge call sheet, ask for the $99 Studio Year in the same thread with a Stripe link.
  • Ask every free user for a one-line quote about the reschedule or wrong-call-time problem they just avoided.

Message template

Hi Dana — saw Studio North's episode with the two-guest format. Getting four people into one room usually costs you a dozen emails and at least one reschedule, then the call sheet gets rebuilt in Docs the night before. I built CallSheet Locker: you send one link, everyone taps their free slots with no account, and you get a locked date plus a branded call sheet PDF with per-role call times. I will run your next shoot free and put Studio North's logo on the call sheet. Want me to set it up this week?
Week-one goal: 150-row list built with 40 verified emails, 25 personalized messages sent, at least 2 replies and one free shoot scheduled.
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

Schema and scaffold

  • Create Supabase project and migrate shoots, roles, participants, availability and orders tables.
  • Scaffold Next.js with Tailwind and deploy to Vercel on the live domain.
  • Ship the landing page with the free-first-shoot offer and one Stripe payment link.

Deliverable: Deployed skeleton with schema migrated and landing page live.

Day 2Build

Shoot builder

  • Build the shoot creation form with role rows and required flags.
  • Add per-role day constraints.
  • Test with one real studio's last shoot as data.

Deliverable: A shoot record created end to end in under three minutes.

Day 3Build

Participant links and grid

  • Create tokenized public route per participant.
  • Build the mobile-first tap grid and persist submissions without login.
  • Show per-participant response status in the producer view.

Deliverable: A link a stranger completes on a phone in twenty seconds.

Day 4Build

Solver and PDF

  • Implement the overlap solver ranking slots by required-role coverage.
  • List remaining gaps by role name.
  • Build the call sheet PDF template with logo and per-role call times.

Deliverable: A branded call sheet PDF generated from a locked slot.

Day 5BuildMVP shipped

Payments, email, launch

  • Gate PDF export behind Stripe Checkout and add the license webhook.
  • Send confirmation emails with PDF and ICS via Resend.
  • Run one full dry run and fix layout defects.

Deliverable: Live product with a working paid export path.

Day 6Acquisition

List building

  • Build a 150-row studio list across ten cities from Google Maps and Instagram.
  • Capture studio name, owner first name, email or handle and city.
  • Verify 40 emails and write two message variants.

Deliverable: 150-row sheet with 40 verified contacts.

Day 7Acquisition

First outreach

  • Send 25 personalized messages offering a free first shoot.
  • Post the offer in the r/podcasting weekly thread.
  • Prepare the Stripe payment link for same-thread closes.

Deliverable: 25 messages sent and the first replies logged.

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

Concierge delivery

  • Hand-schedule the next shoot for every studio that replied.
  • Deliver the call sheet PDF with their logo attached.
  • Ask for the $99 Studio Year in the same thread.

Deliverable: Three free call sheets delivered.

Day 9Acquisition

Outreach batch two

  • Send 30 more personalized messages.
  • Follow up on day-7 sends with the generated PDF attached.
  • Log reply rate by city and variant.

Deliverable: 55 cumulative contacts and five live conversations.

Day 10Acquisition

Community channels

  • Post the free-first-shoot offer in one Discord and two Facebook groups.
  • Reply to every comment within two hours.
  • Record which community produced replies.

Deliverable: Three community posts live with tracked responses.

Day 11Revenue

First sale push

  • Send the Stripe link to the three warmest threads.
  • Rewrite the opener to lead with the call sheet, not the poll.
  • Record every objection verbatim.

Deliverable: First paying customer or a written objection list.

Day 12RevenueFirst sale target

Close and fix

  • Convert the warmest thread to a $99 Studio Year.
  • Ship the single most-requested small change.
  • Publish a forty-second screen recording of the flow.

Deliverable: First sale recorded in TrustMRR and one objection fix shipped.

Day 13Acquisition

Outreach batch three

  • Send 30 more personalized messages.
  • Run 48-hour follow-ups on all prior batches.
  • Ask every free user for a one-line quote.

Deliverable: 85 cumulative contacts and two quotes in hand.

Day 14Review

Cut losing variants

  • Compute reply and close rate by city and message variant.
  • Kill the weaker variant and double the better one.
  • Add 50 more studios in the best-performing city.

Deliverable: Conversion table and 50 new qualified contacts.

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

Outreach batch four

  • Send 30 messages using only the winning variant.
  • Follow up with the redacted call sheet as proof.
  • Log every reply within the hour.

Deliverable: 30 sends under the winning variant.

Day 16Proof

Case artifact

  • Publish a redacted before-and-after call sheet page.
  • Link it in every follow-up.
  • Add a short testimonial block from collected quotes.

Deliverable: One public before-and-after proof page.

Day 17Acquisition

Referral seeding

  • Ask camera ops and editors which studios they shoot for.
  • Add those studios to the list.
  • Send 20 messages naming the shared contact.

Deliverable: 20 warm-adjacent contacts messaged.

Day 18Retention

Reschedule flow

  • Build a reschedule link that regenerates the call sheet and re-sends emails.
  • Add explicit refund terms to checkout and email receipts.
  • Test one simulated reschedule end to end.

Deliverable: Working reschedule path that reduces refund exposure.

Day 19Acquisition

Outreach batch five

  • Send 30 messages.
  • Re-post the free-first-shoot offer in the weekly thread.
  • Reply to every thread comment same day.

Deliverable: Cumulative contact top of funnel above 200.

Day 20Revenue

Agency tier

  • Add the $249 Agency Year checkout and seats copy.
  • Offer it only to buyers already running client shoots.
  • Track upgrade intent separately.

Deliverable: Agency Year page live with one eligible account targeted.

Day 21Review

Week three audit

  • Count sales, refunds and open threads.
  • Cut any channel with zero replies.
  • Reallocate the remaining days to the best channel.

Deliverable: Written channel decision for week four.

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

Outreach batch six

  • Send 30 messages.
  • Follow up on all concierge deliveries.
  • Ask each buyer for a one-sentence referral name.

Deliverable: 30 sends plus three referral names.

Day 23Inbound

Template landing page

  • Publish a page explaining what a call sheet needs and offering the free first shoot.
  • Include the redacted PDF as a download.
  • Add a single email capture field.

Deliverable: One inbound page live with a working capture.

Day 24Risk

Refund and chargeback hygiene

  • Add clear delivery language to every receipt.
  • Keep a per-sale delivery log with PDF timestamps.
  • Respond to any complaint within 24 hours.

Deliverable: Delivery log and updated terms in place.

Day 25Volume

Outreach batch seven

  • Send 30 messages.
  • Follow up with agencies for the $249 tier only.
  • Log replies into a single pipeline sheet.

Deliverable: Pipeline sheet covering every contact.

Day 26Revenue

Upgrade push

  • Email every existing buyer about Agency Year.
  • Offer a client-branded template as the hook.
  • Set a 72-hour reply deadline.

Deliverable: Upgrade email sent to all buyers.

Day 27Review

Week four audit

  • Recalculate reply, close and refund rates.
  • Stop anything below the base-case pace.
  • Write the day-28 to day-30 close list.

Deliverable: Close list of every warm thread.

Day 28Volume

Final outreach push

  • Send the last 30 messages.
  • Note the price rises after the contest window.
  • Reply to all open threads the same day.

Deliverable: Final outbound batch sent.

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

Collect and reconcile

  • Work every warm thread to a paid decision.
  • Reconcile each payment and fee against TrustMRR.
  • Confirm no payment came from outside the window.

Deliverable: Reconciled payment ledger.

Day 30Close

Final tally and next month

  • Publish the honest numbers: sales, refunds, fees, net.
  • Write the three things that worked and three that did not.
  • Set the month-two plan around renewals and Agency Year.

Deliverable: Final report and a month-two operating 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

  • Conservative case assumes 3 Studio Year sales from 150 cold contacts plus community posts, at a 2 percent close on conversations.
  • Base case assumes 10 Studio Year sales, roughly a 6 percent reply rate and 25 percent conversion of concierge setups.
  • Upside case assumes 25 sales, one refund, one Agency Year upgrade folded into a blended $99 average revenue per customer.
  • Payment fees assume Stripe at 2.9 percent plus 30 cents domestic, blending to about 4.5 percent with international cards in the upside case.
  • Paid marketing spend is zero in conservative and base; upside includes $150 of sponsored newsletter or community placements.
  • Operating costs cover domain, Vercel, Supabase, Resend and PDF rendering, ranging from $25 to $90 at this volume.
  • All figures are projections from these assumptions and are not verified revenue, customers or traction.

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,475
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$111
Paid marketing
$150
Hackathon profit
$2,115
Operating costs
$90
Business profit
$2,025

Model your own numbers

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

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

Scenario models from stated assumptions, not verified revenue. All figures are projections; no customers, traction or revenue exist at launch.

Section 7 of 8

Main risks and validation experiments

Risk 1Studios judge Doodle, When2Meet or a Google Docs template as good enough and never reply.

Mitigation

Lead every message with the call sheet artifact and a free done-for-you first shoot, never with scheduling software.

Validation experiment

Send 25 personalized messages in day 7 and count replies within 96 hours.

Kill criteria

Fewer than four replies from 150 personalized messages, or zero acceptances of the free concierge shoot.

Risk 2Cold email deliverability collapses the top of funnel before any revenue lands.

Mitigation

Send in batches of 25 from a warmed domain, personalize the first line, and supplement with community posts and Instagram DMs.

Validation experiment

Track open and reply rate for batch one versus batch two and drop any subject line below a 20 percent open rate.

Kill criteria

Under 15 percent open rate on two consecutive batches with no reply from 50 sends.

Risk 3The generated call sheet PDF looks plain and buyers feel $99 is too much for a document.

Mitigation

Build the template on day four against a real studio call sheet and hand-deliver the first three with the studio logo.

Validation experiment

Deliver three concierge call sheets and ask directly whether the producer would forward it to a client.

Kill criteria

Zero paid conversions after twenty delivered free call sheets.

Risk 4One-time buyers churn and never return, capping the business at a single transaction per studio.

Mitigation

Frame the price explicitly as twelve months of unlimited shoots and offer Agency Year to buyers running client work.

Validation experiment

Ask every buyer in the delivery email how many shoots they expect in the next quarter.

Kill criteria

Fewer than one in five buyers reports three or more shoots a quarter.

Risk 5Studios expect two-way Google Calendar sync in week one and bounce.

Mitigation

Ship ICS files and Google Calendar add links on day five and state the limitation on the landing page.

Validation experiment

Log every objection verbatim and count how often calendar sync appears.

Kill criteria

Calendar sync named as the primary objection in more than half of lost conversations.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Supabase project.
  • Migrate shoots, roles, participants, availability and orders tables with token indexes.

Output: Live database schema with migrations applied.

Hours 3-5

  • Scaffold Next.js with Tailwind and deploy to Vercel.
  • Publish the landing page with the free-first-shoot offer and one Stripe payment link.

Output: Live domain serving the offer page.

Hours 6-8

  • Build the shoot creation form with roles and required flags.
  • Load one real studio shoot as test data.

Output: A shoot record created end to end.

Hours 9-10

  • Write the two cold message variants.
  • Start the 150-row studio list in a spreadsheet with name, owner, contact and city.

Output: Two message variants and the first 40 list rows.

Hours 11-12

  • Run one end-to-end dry run on the test shoot.
  • Send the first five personalized messages.

Output: Dry-run notes and five messages sent.

Complete report

Full 30-day launch report

Read the full generated report

CallSheet Locker — 30-Day Hackathon Launch Report

1. Product opportunity and positioning

CallSheet Locker serves exactly one buyer: the owner-producer of a 1-5 person podcast or video studio in the US, UK, Canada or Australia who personally schedules 2-8 multi-person shoots a month. The trigger event is specific and expensive — a shoot that took 9-15 emails and two reschedules to get four people into one room, followed by the producer retyping the confirmed date into a Google Docs call sheet while a studio slot and a client relationship sit in the balance.

Existing tools stop at the poll. Doodle, When2Meet and group texts answer when people are free. None of them produce the artifact the shoot needs: a locked date, per-role call times, a contact block, notes and a call sheet PDF that host, guest, freelancer and client can all read without an account. CallSheet Locker is the last step of that thread, not a competing calendar. Participants receive one tokenized link and a tap grid on a phone; nobody installs anything or signs in.

The wedge is the paywall position. The gate sits on the PDF export — the exact second the producer has a confirmed date and needs the call sheet — so the purchase is one card entry at the moment of highest intent. The buyer is a single owner-operator, so there is no procurement, no security review and no seat negotiation. The deliverable is standard industry paperwork, which means zero education cost: a producer already knows what a call sheet is and already makes one badly every week.

This is not the original consumer social calendar. Participants get no calendar, no account and no app; the output is a professional document and a one-time annual workspace purchase rather than a free social product.

2. Smallest sellable MVP

One workflow, end to end: create a shoot with roles and a date window, send no-login availability links, see ranked overlapping slots with gaps named explicitly, lock a slot, pay $99, receive a branded call sheet PDF plus .ics files and confirmation emails. Everything else is out of scope for week one — no native apps, no two-way Google Calendar OAuth, no chat, no crew marketplace, no team permissions, no free tier.

3. Technical implementation plan

Next.js on Vercel, Postgres via Supabase free tier, Stripe Checkout with a webhook license check, Resend for transactional email, @react-pdf/renderer for the call sheet, the ics package for invites, Tailwind for the interface. The architecture is deliberately thin: shoot and participant records in Postgres, availability stored as slot arrays, the overlap solver computed server-side, PDF rendering on a serverless route, one webhook that flips a workspace from unpaid to licensed. Build order is schema, shoot builder, participant grid, solver, PDF, then payments and email last so the gate is never the blocker. The hardest technical risk is PDF layout fidelity — a plain call sheet makes the product feel cheap — so the template is built on day four, not day five, and checked against a real studio document.

4. Pricing and monetization

The core offer is Studio Year at $99 one-time: unlimited shoots for twelve months, no-login links, branded PDF export, ICS and emails. Agency Year at $249 adds five seats, client-branded templates and reusable crew defaults, and is treated as upside only. There is no free tier during the contest; the free thing is the founder's concierge setup of a studio's next shoot, which converts inside the same email thread. Revenue grows through Agency Year upgrades from studios already running client work. Renewal lands in month thirteen, outside the 30-day window, which is exactly why the price must read as a year of use rather than a one-off document.

5. First-customer acquisition

One channel: a hand-built 150-row list of small podcast and video studios from Google Maps and Instagram bios across ten mid-size cities, contacted with a done-for-you offer. The message never leads with software. It leads with the outcome: send one link, get a locked date and a call sheet PDF in ten minutes, and the founder will run the next shoot free. The same offer goes into the r/podcasting weekly thread, one indie production Discord or Slack, and two studio-owner Facebook groups. Deliverability is guarded by sending batches of 25 from a warmed domain, personalizing the first line with the studio name, and following up once at 48 hours with the generated call sheet attached as proof rather than a pitch.

6. 30-day execution roadmap

Week one is build and list. Days 1-5 ship the MVP to a live domain by the day-five deadline. Days 6-7 build the contact list and send the first 25 messages. Week two is proof: concierge three free call sheets, send 60 more messages, post in communities, and push the warmest threads to a Stripe link targeting the first sale on day 12. Week three scales the message that worked, publishes a redacted before-and-after call sheet as the case artifact, ships the reschedule flow to cut refund exposure, and lists the Agency Year tier. Week four is volume plus hygiene: two more outreach batches, a short landing page for call sheet searches, explicit refund terms, delivery proof on every sale, and one upgrade push to existing buyers. Days 29-30 close open threads, reconcile every payment against TrustMRR, and cut any activity that produced no replies.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 Studio Year sales at $99, $297 gross, about $10 processing, no ad spend, $25 operating cost. Base: 10 sales, $990 gross, about $32 processing, $45 operating cost. Upside: 25 sales, $2,475 gross, one refund at $99, about $111 processing on a blended 4.5 percent rate, $150 of paid promotion, $90 operating cost. The contest ranks collected revenue minus refunds, chargebacks, processing fees and paid marketing; hosting, domains and PDF delivery costs are not deducted for ranking but are tracked as operating cost so the business math stays honest. At $99 against roughly three dollars of marginal processing and negligible infrastructure, every sale clears its own delivery cost.

8. Risks and validation experiments

Three risks drive the plan. First, free incumbents being judged good enough — tested by whether cold studios reply to a call-sheet-first message rather than a scheduling message. Second, cold email deliverability collapsing the funnel — tested by sending 25 messages on day seven and measuring replies before scaling to 150. Third, PDF quality failing to justify $99 — tested by hand-delivering three concierge call sheets and observing whether the producer forwards them to their own crew. A fourth risk is that one-time buyers never return, tested by asking each buyer how many shoots they expect next quarter. The concept is killed or reshaped if 150 personalized messages produce fewer than four replies, or if twenty delivered free call sheets produce zero paid conversions.

9. First 24-hour action plan

Hours 1-2: create the Supabase project and migrate the shoot, role, participant, availability and order tables. Hours 3-5: scaffold Next.js with Tailwind, ship the landing page with the free-first-shoot offer, connect the domain. Hours 6-8: build the shoot creation form against test data from one studio's last shoot. Hours 9-10: write two cold message variants and start the 150-row list. Hours 11-12: deploy to Vercel, run one end-to-end dry run, and send the first five messages.

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 →