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

PassWindow

A pass-scheduling and link-budget report generator that turns a satellite operator's TLEs and ground station list into a printable weekly contact plan with predicted low-margin passes flagged.

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.70/10
MVP build (solo)
5 days
Launch price
$49 · monthly
Sales to $1,000 revenue
21 customers
First paying customer
Direct personalised outreach to named mission operations leads, each email carrying a contact plan generated from that mission's own public TLEs.
Who pays

Smallsat and CubeSat mission operations leads at 5 to 50 satellite operators and university ground stations, triggered by a new launch or an antenna addition.

Biggest execution risk

Market demand 2.7/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 9; 21 sales at $49 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

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

0/13
Entry price
$49
Solo build
5 days
30d base revenue
$980
30d hackathon profit
$944
Section 1 of 8

Product opportunity and positioning

Target customer

Smallsat and CubeSat mission operations leads at 5 to 50 satellite operators and university ground stations, triggered by a new launch or an antenna addition.

Why now

The buyer has a dated trigger event, a spreadsheet they already hate, and can pay for one generated document this week without any telemetry integration.

Problem

Ops teams compute pass windows, elevation masks and link margins by hand in spreadsheets every week, causing missed contacts and wasted antenna time.

Solution

Upload TLEs and station coordinates; PassWindow computes upcoming passes, flags low-margin ones against a simple link budget, and emails a weekly contact-plan PDF plus CSV.

Differentiation · It ships a schedulable artifact instead of a dashboard or an autopilot, and it needs only public TLEs plus two coordinates to do it.

Opportunity

A mission operations lead running 5 to 50 spacecraft already rebuilds a pass schedule every week. The loop is manual: pull the latest TLEs, paste them into a spreadsheet, compute windows for each station, apply an elevation mask, estimate whether the downlink closes, then hand a list to a scheduler. It costs hours, it breaks the week a new satellite or antenna appears, and it fails silently when a pass is too marginal to be worth the antenna time but nobody noticed.

PassWindow replaces that loop with one deliverable: a weekly contact plan as PDF and CSV, listing every upcoming pass with its elevation profile and a margin flag against a simple link budget. Marginal passes are marked so a scheduler can drop them early or buffer data instead of losing it.

Positioning

The original Constellation Space ambition, an autonomous operating system that reroutes satellite traffic, requires trust and a telemetry integration a solo founder cannot earn in 30 days. PassWindow asks for neither. It is read-only, it consumes public TLEs plus station coordinates, and it produces a document a scheduler uses on Monday morning. No live feed, no autonomy, no procurement.

Defensibility lives in the workflow rather than the model. Orbit propagation is commodity software. The value is the fixed input format, margin thresholds tuned for small ground stations, the recurring Monday delivery, and a flag that maps directly to an operational decision a scheduler already makes. A generic assistant handed the same TLE and station does not produce a plan that survives contact with a real antenna without doing this same engineering.

The trigger event is concrete and dated: a launch, a new antenna, a new spacecraft joining the constellation. That is the week the spreadsheet breaks and someone with budget authority wants it fixed. The buyer is named and reachable directly through mission websites, public CubeSat team rosters and LinkedIn operations titles. There is no marketplace cold start, no SEO ramp, no ad budget and no procurement cycle between the founder and the first sale.

Pricing stays inside the range a small team lead can approve without a purchase order: $49 per month for the recurring weekly plan, and $199 one-time for a multi-station contact plan when a team is adding a station. Both are delivered as an artifact, so the buyer can see exactly what they paid for.

Section 2 of 8

Smallest sellable MVP

A web form that accepts a TLE set plus one to five station coordinate sets, generates a seven-day pass plan PDF and CSV with low-margin passes flagged, and emails it on a weekly schedule behind a $49 per month Stripe subscription.

Must-have features

  • TLE ingestion by NORAD ID with a daily refresh
  • Ground station coordinates with a configurable elevation mask
  • Pass prediction returning AOS, LOS, max elevation and duration
  • Simple link-budget margin per pass with healthy, watch and marginal flags
  • Weekly contact-plan PDF plus CSV generated from one operator config
  • Stripe Checkout, license key gate and scheduled email delivery via Resend

Explicitly out of scope

  • No live telemetry ingestion
  • No autonomous rerouting or commanding
  • No real-time dashboard or countdown widgets
  • No RF hardware or radio driver integration
  • No multi-user roles or SSO
  • No mobile app

Demo flow (what the buyer sees)

  1. Operator signs up and enters a NORAD ID list or pastes TLEs
  2. Operator enters station latitude, longitude, altitude and elevation mask
  3. Operator confirms frequency, transmit power, antenna gain and required Eb/N0
  4. PassWindow computes seven days of passes and computes a margin per pass
  5. Passes below threshold are flagged marginal and highlighted in the plan
  6. PDF and CSV are generated, stored and emailed to the operator
Build plan

Technical implementation plan

Stack

Next.js with the App Router and TypeScriptSkyfield (Python) in a small worker for orbit propagationCelesTrak as the public TLE sourceSupabase Postgres and storage for configs and generated artifactsStripe Checkout for payment and license keysResend for scheduled email deliveryVercel hosting plus a scheduled cron job

Architecture

The Next.js app on Vercel stores operators, stations and TLE sets in Supabase. A Python worker running Skyfield fetches or accepts TLEs, propagates them, computes topocentric passes per station against its elevation mask, then scores each pass with a free-space path loss plus station G/T link budget and assigns a margin flag. The app renders the flagged pass list into a PDF and CSV, stores both in Supabase storage, and a weekly cron regenerates every active subscription and emails the artifacts through Resend. Stripe Checkout issues a license key that unlocks plan generation.

Build steps

  1. Deploy a Next.js skeleton to Vercel and create the Supabase schema for operators, stations, passes and plans
  2. Stand up the Skyfield worker and fetch TLEs from CelesTrak by NORAD ID
  3. Compute topocentric passes for a station with a configurable elevation mask
  4. Validate pass output against one known published pass time before shipping
  5. Implement the link-budget margin calculation and the healthy, watch, marginal classification
  6. Build the station setup form and persist configuration in Supabase
  7. Render the weekly contact-plan PDF and matching CSV
  8. Store artifacts in Supabase storage with signed URLs
  9. Wire Stripe Checkout and a license key gate around plan generation
  10. Add the Monday cron that regenerates and emails each active subscription
  11. Run one full path from signup to inbox and deploy version one
  12. Add a self-monitoring alert if a scheduled delivery fails

AI components

  • No model in the prediction or margin path; the maths is deterministic on purpose
  • An LLM parses unstructured station descriptions pasted from emails into coordinates and an elevation mask
  • An LLM drafts the per-customer cover note that accompanies each weekly plan
Hardest technical risk: Pass predictions drifting when the supplied TLE is more than a few days old, which destroys trust on the first sample plan.
Section 3 of 8

Pricing and monetization

Weekly Plan

Entry offer
$49 / month

For Small ops teams running 5 to 50 spacecraft

  • Weekly contact-plan PDF and CSV
  • Low-margin pass flags
  • Scheduled email delivery
  • Plan history for past weeks

Station Pack

$199 one-time

For Teams adding or commissioning a ground station

  • One-time multi-station contact plan
  • Link-budget report per station
  • Forty-eight hour turnaround

Model: A $49 per month recurring subscription for the weekly contact plan, plus a $199 one-time Station Pack when a team adds a ground station.

First revenue offer: A free contact plan for next week, generated from the mission's own public TLEs and its published station coordinates, delivered as PDF and CSV within 24 hours. Keep it coming every Monday for $49 per month.

Expected ACV: $49

Upsell path: Convert the subscription to a multi-station plan when a second antenna is added, and sell the $199 Station Pack at commissioning time; a team that buys both pays roughly $788 in year one.

Target customers
20
Revenue model
$980
Costs
$60
Profit model
$920
Section 4 of 8

First-customer acquisition

Primary channel

Direct personalised outreach to named mission operations leads, each email carrying a contact plan generated from that mission's own public TLEs.

Where to find them

  • University CubeSat team mission pages listing a ground station and an ops contact
  • Public NASA CubeSat Launch Initiative team rosters
  • LinkedIn titles containing mission operations, ground segment or spacecraft operations at smallsat startups
  • Ground-station-as-a-service startup team pages
  • Publicly announced upcoming launches with named operators
  • AMSAT chapter and amateur ground station operator pages
  • SmallSat conference speaker and attendee lists published as PDFs

Exact outreach motions

  • Send a 90-word email with the mission's own generated contact plan attached as PDF, no pitch in the first paragraph
  • Ask one question: whether the flagged marginal pass matches what their scheduler saw last week
  • Follow up once, plain text, three days later, with a single line describing the marginal-pass flag
  • Offer a free first week rather than a discount on the paid tier
  • Ask every recipient who replies for one named ops contact at another program
  • Quote $199 Station Pack to anyone who mentions a second or new antenna

Message template

Hi [name] - I built PassWindow and ran it on [mission]'s public TLEs against your [station] coordinates. Attached is next week's contact plan: every pass, elevation, and a link-budget margin per pass. Two passes are flagged marginal. Does that match what your scheduler saw last week? If it is useful, I will send it every Monday for $49/month. - [founder]
Week-one goal: 60 named contacts in the sheet, 20 personalised sample plans sent, at least 4 replies, and 1 paid subscription.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 930 days planned
Week 1 · Build & validate · 7 days
Day 1Foundation

Payment rails and a deployable shell

  • Register the domain and deploy a Next.js skeleton to Vercel.
  • Open Stripe and connect it to TrustMRR before any customer exists.
  • Create the Supabase schema for operators, stations, passes and plans.
  • Write the landing headline, sample-plan call to action and the $49 price.

Deliverable: Live landing page with working Stripe test checkout.

Day 2Orbit engine

Pass prediction that is provably correct

  • Stand up a Skyfield worker and fetch TLEs from CelesTrak by NORAD ID.
  • Compute topocentric passes for a station with a configurable elevation mask.
  • Unit-test output against one known published pass time.
  • Return JSON pass records with AOS, LOS, max elevation and duration.

Deliverable: CLI that prints a pass table for any NORAD ID and station.

Day 3Link budget

Margin flagging an ops lead will trust

  • Implement free-space path loss plus station G/T and downlink margin per pass.
  • Expose frequency, transmit power, antenna gain and required Eb/N0 as inputs.
  • Classify each pass as healthy, watch or marginal against a configurable threshold.
  • Add regression tests so the margin maths cannot silently drift.

Deliverable: Margin-flagged pass records stored per station.

Day 4Artifact

The PDF and CSV that get paid for

  • Render a one-page-per-week contact plan PDF with a fleet and station header.
  • Emit a matching CSV with identical rows and flags.
  • Build the station setup form and persist configuration to Supabase.
  • Store generated artifacts in Supabase storage behind signed URLs.

Deliverable: Real PDF and CSV produced from one operator configuration.

Day 5Paywall and deliveryMVP shipped

End-to-end MVP live

  • Add Stripe Checkout plus a license key that unlocks plan generation.
  • Send the finished plan by email through Resend.
  • Schedule a Monday cron that regenerates and delivers every active subscription.
  • Deploy version one and run one full pass from signup to inbox.

Deliverable: PassWindow version one live and self-serve.

Day 6Proof material

Samples that look like the buyer's own fleet

  • Pick 10 publicly listed CubeSat missions with published TLEs and station coordinates.
  • Generate a real contact plan for each using its own public TLE.
  • Record a 90-second Loom walking through one plan and the marginal flag.
  • Publish a sample plan as a public page.

Deliverable: 10 sample plans plus a public demo page.

Day 7List building

60 named contacts with a trigger event

  • Build a 60-row sheet with name, role, mission, station, trigger event and contact route.
  • Source from university CubeSat team pages, mission sites and LinkedIn ops titles.
  • Draft three message variants: launch-week, new-antenna, spreadsheet-replacement.
  • Verify each address reaches a human, not a shared info inbox.

Deliverable: 60-contact outreach sheet with three message variants.

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

20 personalised sample sends

  • Send 20 emails, each attaching that mission's own generated contact plan.
  • Log every send, open and reply in the sheet.
  • Post the sample plan in two space-operations communities.

Deliverable: 20 sends, each with the recipient's own plan attached.

Day 9First saleFirst sale target

Convert a reply into a paid subscription

  • Follow up every day-8 send that opened but did not reply.
  • Offer a 15-minute call or a direct Stripe link, whichever the lead prefers.
  • Close the first $49 per month subscription.

Deliverable: First paying customer and a Stripe receipt.

Day 10Second wave

20 more personalised sends

  • Send 20 new personalised plans to the next sheet rows.
  • Ask each first-wave recipient for one referral name.
  • Fix any sample a recipient said looked wrong.

Deliverable: 20 more sends plus referral names collected.

Day 11Objection pass

Ship the top requested change

  • Triage replies into feature requests, accuracy doubts and price objections.
  • Ship the highest-frequency request that fits the wedge, capped at one day.
  • Update the sample page to answer the accuracy doubt directly.

Deliverable: One shipped fix and an updated proof page.

Day 12Follow-up

Turn opens into trials

  • Send a plain-text follow-up to every non-responder with one line of value.
  • Offer a free first week to anyone who replied but did not buy.
  • Target a second paying subscription.

Deliverable: Second customer or three active free trials.

Day 13Public proof

One post that carries the artifact

  • Publish a before-and-after: one spreadsheet row versus one PassWindow plan.
  • Share it in two operator communities without leading with the price.
  • Route every comment to a direct message.

Deliverable: One public post with inbound conversations logged.

Day 14Review

Numbers, not vibes

  • Tally sends, opens, replies, samples delivered, trials and paid.
  • Cut the worst-performing message variant and keep two.
  • Set the week-three target at three paying customers.

Deliverable: Week-two scorecard and a revised outreach script.

Week 3 · Repeat & systematize · 7 days
Day 15Station Pack

Sell the $199 one-time tier

  • Identify every prospect who mentioned a new or second antenna.
  • Send a multi-station offer with a sample two-station plan.
  • Close one Station Pack.

Deliverable: One $199 Station Pack sold or two in negotiation.

Day 16Self-serve

Remove the founder from onboarding

  • Make signup, station entry and first plan generation work without a call.
  • Add inline validation for coordinates and elevation mask.
  • Cut the time to first plan below two minutes.

Deliverable: Zero-touch signup that produces a plan.

Day 17Referrals

One paying customer into two

  • Ask every paying customer for one named ops contact.
  • Send the referral a plan generated from their own TLEs.
  • Track referral source on every new trial.

Deliverable: At least two warm referral sends.

Day 18Method page

Make the margin flag credible

  • Publish an explainer of the link-budget maths and its stated assumptions.
  • Let anyone check a station against published satellite parameters in one click.

Deliverable: Public methodology page linked from every plan.

Day 19Third wave

20 sends with the method page attached

  • Add 40 rows to the sheet from newly announced CubeSat launches.
  • Send 20 personalised plans with the method page attached.
  • Log replies into the same pipeline.

Deliverable: 20 sends with the methodology attached.

Day 20Retention

Make Monday delivery reliable

  • Verify the cron delivered on time to every active subscription.
  • Add a failure alert to the founder's own inbox.
  • Add plan history so customers can see past weeks.

Deliverable: Two consecutive on-time weekly deliveries.

Day 21Review

Decide where week four spends outreach

  • Compare revenue per outreach hour for $49 subscriptions versus $199 one-time sales.
  • Set the week-four pricing emphasis from that comparison.

Deliverable: Written pricing decision backed by numbers.

Week 4 · Scale what works · 7 days
Day 22Delivery proof

Show the flag changed a decision

  • Email each customer a one-line summary of last week's flagged marginal passes.
  • Ask whether the flag changed any scheduling decision.

Deliverable: Customer replies confirming or rejecting the flag's value.

Day 23Fourth wave

20 sends to launch-window teams

  • Target teams launching or commissioning within the next 60 days.
  • Send a commissioning-week plan tailored to their orbit and station.
  • Offer 48-hour turnaround on a paid Station Pack.

Deliverable: 20 commissioning-focused sends.

Day 24Multi-station

Price the second station

  • Set and publish the multi-station add-on price.
  • Offer the add-on to every customer with more than one station.

Deliverable: Add-on priced and at least one upgrade offered.

Day 25Trials

Convert or kill

  • Ask every open trial for a yes or no by a stated date.
  • Close silent trials and record the reason in the sheet.

Deliverable: Every trial resolved to paid or closed.

Day 26Testimonials

Only from real buyers

  • Ask two paying customers for a one-line quote with permission to publish.
  • Add any granted quote verbatim, or publish nothing.

Deliverable: Zero or more verified quotes on the landing page.

Day 27Fifth wave

Last cold cohort

  • Send 20 final personalised plans to untouched sheet rows.
  • Make one last attempt at every cold reply from weeks two and three.

Deliverable: 20 sends and a cleared follow-up backlog.

Day 28Price test

Test willingness to pay

  • Quote the next five new prospects $69 per month instead of $49.
  • Record accept and decline rates per price point.

Deliverable: First pricing read from real quotes.

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

Maximum collected revenue inside the window

  • Offer a two-month prepay to every trial and stalled prospect.
  • Re-contact every replier with one concrete line of value.
  • Close whatever is closable before the deadline.

Deliverable: Final cohort of payments collected.

Day 30Reconcile and submit

Clean numbers and a defensible entry

  • Reconcile Stripe payouts against TrustMRR records.
  • Document refunds, chargebacks, fees and ad spend for the profit calculation.
  • Submit the hackathon entry and write a one-page post-mortem.

Deliverable: Submission sent with reconciled revenue.

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: all revenue is the $49 per month Weekly Plan, no Station Pack sells, and no paid marketing is used.
  • Base: 20 Weekly Plan subscriptions collected inside 30 days, matching the concept's target of 20 customers and roughly $980 gross, with no paid marketing.
  • Upside: 40 customers at a blended $60 ARPU from 37 subscriptions plus 3 Station Packs, with $150 of paid spend used to widen the last-week cohort.
  • Payment fees assume Stripe at roughly 2.9% plus $0.30 per transaction, plus a small allowance for non-US cards, giving 3.7% to 4.1% of gross.
  • Refunds are zero in Conservative and Base because the first week is free and the artifact is inspected before payment.
  • Operating costs cover Vercel, Supabase, Resend, a small Python worker and API delivery for the number of plans generated; they are not deducted from hackathon profit.
  • All figures are projections built from the stated assumptions, not verified revenue.

Conservative

5 customers
$245
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$10
Paid marketing
$0
Hackathon profit
$235
Operating costs
$35
Business profit
$200

Base case

20 customers
$980
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$36
Paid marketing
$0
Hackathon profit
$944
Operating costs
$60
Business profit
$884

Optimistic

40 customers
$2,400
collected revenue · avg payment $60
Refunds
$98
Chargebacks
$0
Payment fees
$96
Paid marketing
$150
Hackathon profit
$2,056
Operating costs
$150
Business profit
$1,906

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$980
Payment fees (3.9%)
$38
Paid marketing
$0
Hackathon profit
$942
Business profit
$882

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, existing customers or guarantees.

Section 7 of 8

Main risks and validation experiments

Risk 1Buyers already use free pass-prediction tools and will not pay for a document.

Mitigation

Sell the margin flag and the recurring Monday delivery, not the pass list, and always attach a plan generated from the buyer's own TLEs.

Validation experiment

Send 20 personalised plans in week two and count how many recipients ask to keep receiving them.

Kill criteria

Fewer than 2 of 40 recipients show any willingness to pay by day 14; switch to selling only the $199 one-time commissioning report.

Risk 2Outreach reply rates collapse because ops leads ignore cold email.

Mitigation

Never send a pitch without a real artifact attached, and keep the ask to one yes-or-no question.

Validation experiment

A/B two message variants across 20 sends each in week two and compare reply rate.

Kill criteria

Below a 5 percent reply rate after 60 personalised sends.

Risk 3Stale or wrong TLEs produce pass windows that miss, destroying trust on the first sample.

Mitigation

Refresh TLEs daily, stamp TLE age on every plan, and let operators paste their own TLEs.

Validation experiment

Ask two recipients to compare the generated plan against their live schedule and report any window that misses by more than a minute.

Kill criteria

Two buyers report material window errors that daily TLE refresh and manual paste do not fix.

Risk 4The addressable market of 5 to 50 satellite ops teams is too small to reach the base case.

Mitigation

Widen the top of funnel to university ground stations and add the one-time Station Pack so antenna additions create revenue without new logos.

Validation experiment

Track the ratio of university ground-station contacts to smallsat company contacts that convert in weeks two and three.

Kill criteria

Fewer than 20 qualified prospects identified after 120 sheet rows are researched.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and deploy a Next.js skeleton to Vercel.
  • Open Stripe and connect the payout account to TrustMRR before any customer exists.
  • Create the Supabase project and the four core tables.

Output: Live URL, connected payment account, empty database schema.

Hours 3-5

  • Build the Skyfield worker that fetches TLEs from CelesTrak by NORAD ID.
  • Compute topocentric passes for one station with a 10 degree elevation mask.
  • Check the output against one known published pass time and fix any offset.

Output: Verified pass table for at least three public satellites.

Hours 6-8

  • Implement the free-space path loss and link margin per pass.
  • Assign healthy, watch and marginal flags against a configurable threshold.
  • Render the pass list into a rough one-page PDF using the same data.

Output: First generated contact-plan PDF with at least one marginal pass flagged.

Hours 9-10

  • Pick 10 publicly listed CubeSat missions with published TLEs and station coordinates.
  • Draft the 90-word outreach email and the one-question ask.

Output: Target list of 10 missions plus a final outreach message.

Hours 11-12

  • Write the landing page headline, the $49 price and the free-sample call to action.
  • Publish the internal day-2 to day-5 build checklist so tomorrow starts with a task, not a decision.

Output: Landing copy committed and a written five-day build checklist.

Complete report

Full 30-day launch report

Read the full generated report

PassWindow — 30-Day Launch Report

1. Product opportunity and positioning

PassWindow sells an artifact, not a platform. A smallsat or CubeSat mission operations lead running 5 to 50 spacecraft and one to three ground stations rebuilds a pass schedule every week: pull TLEs, compute windows in a spreadsheet, apply elevation masks, guess whether the downlink closes, then hand a list to a scheduler. It takes hours, it breaks the week a new satellite or antenna appears, and it fails quietly when a pass sits too close to the margin and nobody notices.

PassWindow takes an operator's TLE set and station coordinates and returns a weekly contact plan: PDF plus CSV, every upcoming pass, its elevation profile, and a margin flag against a simple link budget. Marginal passes are marked so a scheduler can drop them early or buffer data instead of losing it.

The position is deliberately narrow. The original Constellation Space ambition, an autonomous operating system that reroutes satellite traffic, demands trust and a telemetry integration a solo founder cannot earn in 30 days. PassWindow asks for neither. It is read-only, it consumes public TLEs plus two coordinates, and it produces a document usable on Monday morning. The trigger event is concrete and dated: a launch, a new antenna, a new spacecraft joining a constellation. That is the week the spreadsheet breaks and someone with budget authority wants it fixed.

Defensibility sits in the workflow, not the model. Orbit propagation is commodity software. The value is the fixed input format, margin thresholds tuned for small ground stations, the recurring Monday delivery, and a flag that maps straight to an operational decision a scheduler already makes. The buyer is reachable by name through mission websites, public CubeSat team rosters and LinkedIn operations titles, with no procurement cycle and no marketplace cold start between the founder and the first sale.

2. Smallest sellable MVP

The MVP is one form and one document. An operator submits a NORAD ID list or pastes TLEs, enters one to five station coordinate sets with an elevation mask and a few link-budget parameters, and receives a seven-day contact plan as PDF and CSV with marginal passes flagged. Stripe Checkout unlocks generation, and a Monday cron regenerates and emails the plan for every active subscription.

Out of scope on purpose: live telemetry, autonomous rerouting, real-time dashboards, RF hardware, mobile apps and multi-user roles. Each one adds trust or integration cost without making the first document more sellable.

3. Technical implementation plan

Next.js on Vercel holds the app and the operator config in Supabase. A Python worker running Skyfield fetches TLEs from CelesTrak, propagates them, and computes topocentric passes per station against its elevation mask. Each pass is scored with free-space path loss, station G/T and required Eb/N0, then classified healthy, watch or marginal. The app renders the flagged list into a PDF and a matching CSV, stores both in Supabase storage, and emails them through Resend on a weekly cron.

No model sits in the prediction or margin path; the maths is deterministic on purpose because the buyer will check it. An LLM is used for two narrow jobs: parsing unstructured station descriptions pasted from email threads into coordinates and elevation masks, and drafting the short cover note that goes with each weekly plan.

The hardest technical risk is TLE staleness. A plan computed from a week-old element set can miss a window by enough to look wrong, and one wrong sample ends the conversation. Mitigation is daily TLE refresh, a stamped TLE age on every plan, and a manual paste field for operators who keep their own element sets.

4. Pricing and monetization

Two tiers, both priced for a team lead who can approve without a purchase order. The Weekly Plan is $49 per month for the recurring PDF and CSV, the marginal-pass flags, scheduled delivery and plan history. The Station Pack is $199 one-time for a multi-station contact plan and per-station link-budget report, sold when a team is commissioning or adding an antenna.

A team that buys both spends roughly $788 in year one. The subscription is the engine and the Station Pack is the accelerator at the exact moment a team is spending money on hardware anyway. No discounts in the first two weeks; a free first week is the only concession, because it puts a real artifact in front of the buyer without training them to wait for a sale.

5. First-customer acquisition

The only channel is direct personalised outreach. Each email carries a contact plan generated from that mission's own public TLEs and published station coordinates, and asks exactly one question: does the flagged marginal pass match what the scheduler saw last week. That question converts because it can only be answered by someone who actually runs the station.

Targets come from university CubeSat team pages, public CubeSat launch program rosters, ground-station-as-a-service team pages, LinkedIn titles containing mission operations or ground segment, and newly announced launches. Every recipient is a named human, never a shared inbox. Replies route to a Stripe link or a fifteen-minute call, whichever the lead prefers, and every replier is asked for one named contact at another program.

6. 30-day execution roadmap

Days 1 to 5 are pure build with a live deployment every day: payment rails and schema, the orbit engine, the link budget, the PDF and CSV artifact, then the Stripe gate and the Monday cron. Version one ships on day 5.

Days 6 and 7 turn the product into proof: ten sample plans generated from real public missions, a public sample page, and a 60-contact sheet with three message variants. Days 8 to 14 are the first three outreach waves of 20 personalised sends each, followed by follow-ups, objection triage, one public before-and-after post, and a scorecard target of two paid customers.

Days 15 to 21 add the $199 Station Pack to antenna-adding teams, remove the founder from onboarding, harvest referrals, publish the link-budget methodology page, and verify two consecutive on-time deliveries. Days 22 to 28 focus on retention proof, a commissioning-window outreach wave, multi-station pricing, trial resolution, verified quotes only from real buyers, and a $69 price test on five new prospects.

Days 29 and 30 are a prepay push to close everything closable, then reconciliation of Stripe payouts against TrustMRR records and submission.

7. Revenue and profit scenarios

All three scenarios are projections from stated assumptions, not verified revenue or existing customers. Conservative assumes five Weekly Plan subscriptions and no paid marketing: $245 gross, $10 in payment fees, no refunds, $35 of operating cost. Base assumes 20 subscriptions at $49, matching the concept target: $980 gross, $36 in fees, zero refunds, $60 of operating cost. Upside assumes 40 customers at a blended $60 ARPU from 37 subscriptions plus 3 Station Packs, with $150 of paid spend widening the final cohort: $2,400 gross, $98 refunds, $96 in fees, $150 operating cost.

Hackathon profit is gross minus refunds, chargebacks, payment fees and ad spend. Hosting, domains and delivery cost are excluded from the ranking but included in business profit. Delivery stays well under the price of every sale, so no tier sells below cost.

8. Main risks and validation

The first risk is that free pass-prediction tools make a paid document feel redundant. The test is whether recipients of a personalised plan ask to keep receiving it; if fewer than two of forty do by day 14, the offer collapses to the $199 one-time commissioning report. The second is cold-email reply rate; two message variants run across 20 sends each, and a rate under 5 percent after 60 sends kills the channel. The third is accuracy: daily TLE refresh, a stamped TLE age, and a manual paste field, validated by asking recipients to compare the plan to their live schedule. The fourth is market size; the funnel is widened to university ground stations and the Station Pack, and if fewer than 20 qualified prospects exist after 120 researched rows, the wedge needs a different buyer.

9. First 24-hour action plan

Hours 1 to 2: domain, Vercel deployment, Stripe connected to TrustMRR, Supabase schema. Hours 3 to 5: Skyfield worker fetching CelesTrak TLEs and producing a pass table checked against one known pass. Hours 6 to 8: link-budget margin, healthy and marginal flags, first rough PDF. Hours 9 to 10: ten target missions and the 90-word outreach message. Hours 11 to 12: landing copy with the $49 price and the free-sample call to action, plus a written day-2-to-day-5 checklist. By hour 12 the founder has a deployed shell, a working prediction pipeline, a target list and a message — everything needed to build the sellable MVP in the next four days.

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 →