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

LockDay Expiration Radar

A tool that turns a mortgage loan officer's messy pipeline export into a ranked rate-lock expiration radar and a Monday risk digest, so no loan silently expires.

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.41/10
MVP build (solo)
4 days
Launch price
$199
Sales to $1,000 revenue
6 customers
First paying customer
Direct outreach to loan officers in r/loanoriginators, mortgage-focused Facebook groups and LinkedIn, offering a free lock-risk check on their own pipeline export.
Who pays

Solo mortgage loan officers and broker-owners at 1–15 person US shops running 15–80 active loans on Encompass, Calyx, Byte or a spreadsheet, who recently ate a lock extension fee or nearly missed one.

Biggest execution risk

Monetization potential 5.0/10

Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.

Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 12; 6 sales at $199 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.6/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

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

0/15
Entry price
$199
Solo build
4 days
30d base revenue
$2,786
30d hackathon profit
$2,502
Section 1 of 8

Product opportunity and positioning

Target customer

Solo mortgage loan officers and broker-owners at 1–15 person US shops running 15–80 active loans on Encompass, Calyx, Byte or a spreadsheet, who recently ate a lock extension fee or nearly missed one.

Why now

A one-time $199 card purchase needs no procurement, the officer is the daily user, no borrower PII is required, and lock extensions are an immediate quantifiable loss rather than a vague efficiency gain.

Problem

Rate-lock expiration dates are scattered across the LOS, email and sticky notes; a missed expiration forces a costly extension or a repriced loan discovered days late.

Solution

The officer pastes a pipeline export, maps four columns (loan ID, lock date, lock days, lender), and LockDay applies US holidays and lender business-day conventions to output a ranked color-coded radar, a safe-to-close date with a 7-day buffer, per-loan Extension Decision Card PDFs and a scheduled Monday email digest.

Differentiation · Not an LOS replacement and not a rate-shopping tool: LOS alerts are per-file and unranked, while LockDay ranks only the loans needing action this week and pre-computes the extension cost in dollars.

The gap

A solo loan officer running 15–80 active loans tracks lock dates in three places at once: an LOS field, an inbox and a spreadsheet. LOS alerts fire per file, with no ranking and no dollar consequence attached, so they get dismissed. A missed rate-lock expiration becomes an extension fee or a repriced loan, usually discovered after the borrower has already been quoted a closing date. The loss is immediate and countable, which is what makes it sellable in a 30-day window.

Who pays

The buyer is the daily user: a solo mortgage loan officer or broker-owner at a 1–15 person US shop on Encompass, Calyx, Byte or a spreadsheet, who has recently paid an extension fee or nearly missed one. A $199 card charge needs no manager sign-off, no procurement cycle and no IT review. No borrower PII is required, so the trust barrier is a paste of four columns, not a data-processing agreement.

Why this wedge

LockDay is not an LOS replacement and not a rate-benchmarking or negotiation tool. It is a checkpoint between the LOS and the closing calendar. The officer maps loan ID, lock date, lock days and lender; LockDay applies US holidays and lender-specific calendar-versus-business-day conventions; the output is a ranked radar with green/amber/red states, a safe-to-close date with a 7-day buffer, a per-loan Extension Decision Card PDF using the officer's own per-day cost input, and a Monday email digest. A single officer can see their own pipeline ranked in under two minutes during a direct message conversation, which is the whole demo.

Scoring read

JEV scores this concept 64.1/100 (band C). The strengths are exactly the contest-relevant ones: speed to first revenue at 8.61/10 and solo build feasibility at 7.78/10. The weak criterion is monetization at 4.99/10, driven by a single low-value one-time charge. The plan does not redesign around that weakness; it adds a $399 five-seat Shop tier, a $50 referral credit and a twelve-month renewal path so revenue per buyer can move without changing the core workflow, the buyer or the channel.

Differentiation

Generic spreadsheet templates and native LOS reports show a date. LockDay shows a ranked decision: which loans need action this week, what the safe-to-close date is, and what waiting costs. The defensible asset is the editable lender convention library, built from corrections the officer makes, not from an integration nobody will grant in 30 days.

Section 2 of 8

Smallest sellable MVP

A paste-four-columns tool that outputs a ranked lock-expiration radar, a per-loan extension-cost PDF and a Monday digest, sold for $199 one-time.

Must-have features

  • CSV/Excel paste with four-field column mapper (loan ID, lock date, lock days, lender)
  • Business-day lock calculator with US holiday list, calendar-vs-business-day presets and roll-forward rules
  • Ranked risk dashboard with green/amber/red states and a configurable 7-day safe-to-close buffer
  • Scheduled Monday email digest via Resend with at-risk loans and one-click links
  • Per-loan Extension Decision Card PDF with days left, safe-to-close date and cost estimate from the officer's per-day input
  • Stripe Checkout for $199 and $399 one-time, webhook-granted 12-month access, magic-link login
  • Editable lender convention library so the officer can correct a preset
  • Optional free no-login checker showing the top-10 ranked radar without digest or PDFs

Explicitly out of scope

  • No direct LOS/Encompass API integration
  • No SMS alerts
  • No borrower-facing portal or document upload
  • No rate benchmarking, Loan Estimate parsing or negotiation packets
  • No team permissions, audit logs or multi-office administration
  • No mobile app
  • No CRM, commission tracking or pipeline forecasting

Demo flow (what the buyer sees)

  1. Officer pastes or uploads a pipeline export
  2. Maps the four columns and confirms lender presets
  3. LockDay computes true expiration with holidays and roll-forward rules
  4. Radar renders loans sorted by days remaining with green/amber/red states
  5. Officer sets the safe-to-close buffer and per-day extension cost
  6. Officer downloads an Extension Decision Card PDF for the top at-risk loan
  7. Officer receives the same list as a Monday email digest
Build plan

Technical implementation plan

Stack

Next.js (App Router) on VercelNeon Postgres with Drizzle ORMMagic-link auth issued through ResendStripe Checkout plus webhooksreact-pdf for the Extension Decision CardPapaParse for client-side CSV parsingdate-fns-tz with a static US federal holiday listVercel Cron for the Monday digest

Architecture

The browser parses the export client-side with PapaParse so raw files need not persist; only mapped loan rows (ID, dates, lender, computed expiration) are written to Neon, keyed by the workspace email. A pure TypeScript calculator module converts lock date plus lock days into a true expiration date using a static holiday table and per-lender presets stored in Postgres. The radar page reads those rows and sorts by days remaining. A Vercel Cron job calls a digest route each Monday that renders the at-risk list and sends it through Resend. Stripe Checkout grants a 12-month access flag via webhook. The PDF is rendered on demand from the same row plus the officer's per-day cost input.

Build steps

  1. Create Neon database and Drizzle schema: workspaces, loans, lender_presets, purchases
  2. Write the pure calculator module with holiday list, calendar/business-day modes and roll-forward
  3. Add twelve fixture tests covering weekend, holiday, observed-holiday and roll-forward cases
  4. Build CSV paste box with PapaParse plus four-field column mapper and preview
  5. Build radar view sorted by days remaining with buffer setting and color states
  6. Add magic-link auth and persist mapped rows per workspace
  7. Integrate Stripe Checkout for $199 and $399 with webhook access grant
  8. Deploy to Vercel on a custom domain and run five real exports end to end
  9. Build Monday digest route, template and Vercel Cron schedule
  10. Render Extension Decision Card PDF with react-pdf and per-day cost input
  11. Publish free no-login checker page showing top-10 ranked loans
  12. Add editable lender preset library with change logging
  13. Add rate limiting, error logging and a support email alias

AI components

  • LLM used only as a fallback to normalize inconsistent lender names in pasted exports, mapped against a seeded preset list
  • LLM used to draft the one-line digest summary sentence; all date and cost math remains deterministic code
Hardest technical risk: Business-day correctness: observed-holiday shifts and calendar-versus-business-day lender conventions. One wrong red state on a live pipeline destroys trust, so the calculator is a pure tested module with fixtures and an explicit verify-with-your-lender line on every artifact.
Section 3 of 8

Pricing and monetization

Founding Solo

Entry offer
$199 one-time

For Single loan officer

  • 12 months of pipeline lock radar
  • Monday email digest
  • Unlimited pipelines and loans
  • Extension Decision Card PDFs
  • Editable lender convention library

Shop

$399 one-time

For Broker-owner with up to 5 loan officers

  • 12 months for up to 5 users
  • Shared lender convention library
  • Per-user Monday digests
  • Extension Decision Card PDFs

Model: Two one-time tiers covering 12 months of access, no subscription, single-officer entry price.

First revenue offer: I will run your current pipeline export through LockDay free and send back your ranked lock-risk radar plus a digest sample. If it flags loans you did not know were at risk, the founding plan is $199 for 12 months through this link.

Expected ACV: $199

Upsell path: Move single officers to the $399 Shop tier for five seats, credit $50 per forwarded digest that converts, and renew at $199 after twelve months.

Target customers
30
Revenue model
$5,970
Costs
$220
Profit model
$5,750
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to loan officers in r/loanoriginators, mortgage-focused Facebook groups and LinkedIn, offering a free lock-risk check on their own pipeline export.

Where to find them

  • r/loanoriginators posts and comments about lock expirations, extensions or pipeline management
  • Three to five mortgage loan officer Facebook groups (lock desk, sales tactics, broker-owner groups)
  • LinkedIn search: loan officer titles at 1–15 person brokerages in US metro areas
  • Broker-owner communities and mortgage Discord/Slack channels
  • Reply threads on posts asking 'is this lock extension fee normal'

Exact outreach motions

  • Open with the free checker link and no pitch: ask for their export, return a ranked radar
  • Post a redacted screenshot of a ranked radar in r/loanoriginators after reading the subreddit rules
  • Send 20 LinkedIn DMs per day: 'I built a free checker for missed lock dates — want me to run your export?'
  • Run a 10-minute screenshare, show the at-risk count, send their Monday digest sample
  • 48-hour follow-up containing the number of loans flagged and a one-line extension-cost estimate
  • Ask each buyer to forward the digest to one loan officer friend for a $50 account credit

Message template

Hey [Name] — quick one. Lock dates in your pipeline: do you track them in the LOS, a spreadsheet, or memory? I built a free checker that takes your export (loan ID, lock date, lock days, lender — no borrower names) and returns a ranked list of which locks expire first plus the extension cost. Want me to run yours? Takes two minutes and I will send the report back either way.
Week-one goal: 30 free pipeline audits run on real exports and the first paid customer by day 12.
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 1Lock math

Schema and calculator

  • Create Neon schema: workspaces, loans, lender_presets, purchases
  • Build pure calculator with 2027 US federal holiday list
  • Write twelve fixture tests for weekend, holiday and roll-forward cases

Deliverable: Passing calculator test suite

Day 2Intake

CSV paste and mapping

  • Build paste box with PapaParse and header detection
  • Ship four-field column mapper with preview table
  • Add no-borrower-PII notice next to the upload

Deliverable: Paste to mapped rows working end to end

Day 3Radar

Ranked risk view

  • Render loans sorted by days remaining with green/amber/red
  • Add configurable safe-to-close buffer defaulting to 7 days
  • Persist mapped rows to Neon per workspace

Deliverable: Working radar on a real export

Day 4Paywall

Stripe and login

  • Wire Stripe Checkout for $199 and $399 one-time
  • Handle webhook to grant 12-month access
  • Gate radar and PDFs; keep upload free

Deliverable: End-to-end paid signup

Day 5FreezeMVP shipped

Deploy MVP

  • Deploy to Vercel on the custom domain
  • Run five real pipeline exports through the full flow
  • Fix only blocking bugs from that pass

Deliverable: Live v1, feature-frozen

Day 6Digest

Monday email

  • Build digest template with at-risk list and per-loan links
  • Schedule Vercel Cron Monday 11:00 UTC via Resend
  • Add in-app digest preview

Deliverable: Scheduled digest sending a sample

Day 7PDF

Extension Decision Card

  • Render react-pdf card with days left, safe-to-close date, cost estimate
  • Add per-day cost input driving the estimate
  • Add verify-with-your-lender footnote

Deliverable: Downloadable per-loan decision card

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

Free no-login checker

  • Publish /check showing top-10 ranked radar free
  • Gate digest and PDFs behind purchase
  • Capture email for the digest sample

Deliverable: Public free lock-risk checker

Day 9Presets

Lender convention library

  • Seed calendar-day and business-day lender presets
  • Add editable preset per lender in workspace
  • Log every preset change for trust

Deliverable: Editable lender convention library

Day 10Prep

Proof assets

  • Capture redacted radar screenshot and 40-second demo GIF
  • Write r/loanoriginators post and read the subreddit rules
  • Build list of 20 mortgage Facebook groups and 3 mortgage Slack/Discord channels

Deliverable: Post copy, assets and channel list

Day 11Launch

Community posts

  • Post the free checker in r/loanoriginators and three Facebook groups
  • Reply to every comment within 30 minutes
  • DM commenters offering to run their export

Deliverable: First 10 free audits requested

Day 12SalesFirst sale target

Live audits

  • Run five 10-minute screenshares on real exports
  • Show at-risk count, send digest sample, drop the $199 link on screen
  • Log objections verbatim

Deliverable: First paying customer

Day 13Outreach

LinkedIn cadence

  • Send 20 DMs to loan officers at 1–15 person shops
  • Send 48-hour follow-ups with flagged-loan counts
  • Track reply, audit and sale rates in a sheet

Deliverable: 20 DMs per day cadence running

Day 14Friction

Fix objections

  • Ship the three most-cited blockers from days 12–13
  • Add a downloadable sample CSV per LOS
  • Sharpen the no-PII copy on upload

Deliverable: Friction fixes deployed

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

Outreach scale

  • Send 20 DMs and run 10 free audits
  • Post second redacted radar example in two groups
  • Follow up all day-12 to day-14 non-buyers

Deliverable: 60 cumulative DMs and 20 audits

Day 16Referral

Credit loop

  • Issue $50 credit links for forwarded digests that convert
  • Add in-app share button
  • Email buyers the referral ask

Deliverable: Referral loop live

Day 17Community

Second wave

  • Answer five lock-date questions in mortgage groups without selling
  • Post before/after redacted expiration example
  • Invite one moderator to try the free checker

Deliverable: Second wave posted

Day 18Digest proof

Email performance

  • Send real Monday digests to all trials
  • Measure open rate and click-through
  • Rewrite subject line around at-risk count

Deliverable: Digest engagement data

Day 19Shop tier

Broker-owners

  • Email five broker-owners the 5-seat offer
  • Run one multi-user screenshare
  • Add per-user digest to a live account

Deliverable: First Shop tier conversation

Day 20Proof

Case page

  • Publish one anonymized audit result with permission
  • Add buyer quotes collected to date
  • Link the case page from the checker

Deliverable: One live case study page

Day 21Review

Midpoint metrics

  • Reconcile Stripe revenue and refunds
  • Compute touch-to-sale conversion per channel
  • Cut the weakest channel and double the best

Deliverable: Midpoint metrics memo

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

Outreach push

  • Send 25 DMs and run 10 audits
  • Reactivate every trial with a new flagged-loan count
  • Ask two buyers for a one-line testimonial

Deliverable: 100 cumulative DMs

Day 23Seasonality

Extension-cost angle

  • Email non-buyers the December closing-calendar angle
  • Add holiday-hours warning banner in-app
  • Post the year-end lock reminder in two groups

Deliverable: Seasonal email sent to all trials

Day 24Trust

Holiday reference

  • Publish a short holiday and roll-forward explainer page
  • Link it from every PDF footer
  • Share it as a standalone reference in groups

Deliverable: Public calendar reference page

Day 25Close

Follow-up sprint

  • Call or DM every trial user directly
  • Offer founding price with a December 16 deadline
  • Log every reason for no

Deliverable: All trials contacted personally

Day 26Ops

Hardening

  • Add error logging and an alert on digest failures
  • Write a support macro and refund policy page
  • Test the paid flow on a second browser

Deliverable: Ops checklist complete

Day 27Shop push

Second broker attempt

  • Pitch three broker-owners the 5-seat plan
  • Offer a shared lender library walkthrough
  • Send a partial Shop invoice via Stripe link

Deliverable: One Shop tier sale or clear no

Day 28Last call

Deadline push

  • Email all trials the December 16 13:00 UTC cutoff
  • Post final community update
  • Confirm referral credits owed

Deliverable: Last-call campaign sent

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

Payments and reconciliation

  • Take remaining payments and confirm webhooks fired
  • Reconcile Stripe gross, fees and refunds
  • Export the customer list and renewal dates

Deliverable: Reconciled revenue ledger

Day 30Report

Publish results

  • Calculate hackathon profit and business profit
  • Publish the numbers and thank buyers publicly
  • Set the twelve-month renewal reminder

Deliverable: Public 30-day results post

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: 4 buyers, all Founding Solo at $199, reached from roughly 150 targeted touches.
  • Base: 14 buyers at $199, from roughly 600 touches, a 2.3% conversion that is a hypothesis, not a validated rate.
  • Upside: 24 buyers — 20 Founding Solo at $199 and 4 Shop at $399 — blended ARPU $232.
  • All tiers are one-time charges for 12 months of access; no recurring revenue is assumed inside the 30 days.
  • Payment fees assume Stripe at 2.9% plus $0.30 per transaction.
  • Ad spend is zero in every scenario; the primary channel is organic direct outreach and community posting.
  • Operating costs cover Vercel, Neon, Resend, domain and LLM/API usage to serve those customers, $35–$95 depending on volume.
  • One $199 refund is modeled in base and upside; conservative assumes none.
  • No chargebacks are modeled; a single $199 chargeback would reduce hackathon profit by that amount.
  • Every sale must exceed its delivery cost; nothing is priced below cost.

Conservative

4 customers
$796
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$24
Paid marketing
$0
Hackathon profit
$772
Operating costs
$35
Business profit
$737

Base case

14 customers
$2,786
collected revenue · avg payment $199
Refunds
$199
Chargebacks
$0
Payment fees
$85
Paid marketing
$0
Hackathon profit
$2,502
Operating costs
$60
Business profit
$2,442

Optimistic

24 customers
$5,568
collected revenue · avg payment $232
Refunds
$199
Chargebacks
$0
Payment fees
$169
Paid marketing
$0
Hackathon profit
$5,200
Operating costs
$95
Business profit
$5,105

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,786
Payment fees (3.9%)
$109
Paid marketing
$0
Hackathon profit
$2,677
Business profit
$2,617

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. No customers, traction or partnerships exist at launch.

Section 7 of 8

Main risks and validation experiments

Risk 1Loan officers believe their LOS already handles lock alerts, so the product feels redundant.

Mitigation

Position on ranked action plus dollar consequence plus lender business-day conventions, which LOS alerts do not produce.

Validation experiment

Ask ten loan officers in DMs how they track lock dates today and what their last extension cost.

Kill criteria

If eight of ten say LOS alerts are sufficient and nobody buys after 30 conversations, the wedge is wrong.

Risk 2Officers refuse to paste pipeline data into a new tool even with client-side parsing.

Mitigation

Parse in the browser, require only four columns, never request borrower names, add a delete-on-request line.

Validation experiment

Run five live screenshares and count how many actually paste their own export.

Kill criteria

If fewer than two of five paste a real export, the intake model must change before more outreach.

Risk 3A business-day or holiday rule computes wrong and a loan is flagged incorrectly.

Mitigation

Pure tested calculator with twelve fixtures, editable lender presets, and a verify-with-your-lender line on every PDF and digest.

Validation experiment

Compare computed expirations against three officers' known-good manual dates.

Kill criteria

Any confirmed wrong red state on a live pipeline blocks further sales until fixed and re-tested.

Risk 4December pipeline volume and holiday schedules reduce urgency inside the contest window.

Mitigation

Lead with extension cost and year-end closing calendars; add holiday-hours warnings in-app.

Validation experiment

Compare week-1 and week-3 reply rates on the same message.

Kill criteria

If reply rate falls by half and no sale lands by day 20, shift outreach to broker-owners buying for teams.

Risk 5A one-time $199 price caps total revenue below a meaningful profit.

Mitigation

Add the $399 five-seat Shop tier, the $50 referral credit and a twelve-month renewal path.

Validation experiment

Present both tiers in the first ten demos and record which is chosen and why.

Kill criteria

If zero Shop interest after ten broker-owner conversations, drop the tier and push volume on Solo.

Risk 6Subreddit and Facebook group self-promotion rules block the primary channel.

Mitigation

Lead with the free checker, contribute answers without links, and ask moderators before posting.

Validation experiment

Post the free checker in one group and one subreddit and measure removal versus replies.

Kill criteria

If two of three communities remove the post, move the channel to LinkedIn DMs only.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-3

  • Create Neon schema for workspaces, loans, lender_presets
  • Write the pure lock calculator with US holiday list
  • Add twelve fixture tests

Output: Passing calculator test suite committed

Hours 3-6

  • Build CSV paste with PapaParse
  • Ship the four-field column mapper and preview

Output: Paste-to-mapped-rows working locally

Hours 6-9

  • Build the ranked radar with green/amber/red states
  • Add the configurable 7-day safe-to-close buffer

Output: Radar screenshot on a sample export

Hours 9-12

  • Wire Stripe Checkout for $199 and $399
  • Add magic-link login and access gating

Output: Working paid signup flow in test mode

Hours 12-16

  • Deploy to Vercel on the custom domain
  • Run three real exports through the flow
  • Capture a redacted radar screenshot

Output: Live URL plus the first outreach asset

Hours 16-24

  • Build a 50-name loan officer outreach list
  • Write the DM and the community post
  • Send the first 20 DMs

Output: 20 DMs sent and the first post queued

Complete report

Full 30-day launch report

Read the full generated report

LockDay Expiration Radar — 30-Day Launch Report

1. Product opportunity and positioning

Solo loan officers run 15–80 active loans across an LOS, an inbox and a spreadsheet. The rate-lock expiration date sits in a field nobody re-reads, and LOS alerts fire per file with no ranking and no dollar consequence attached. A missed lock becomes an extension fee or a repriced loan, usually discovered after the borrower already has a closing date. JEV scored this concept 64.1/100 (band C) with speed-to-first-revenue at 8.61/10 and solo build feasibility at 7.78/10 — the two criteria that decide a 30-day contest. The weak spot is monetization at 4.99/10; this plan answers it with a second $399 shop tier and a referral credit instead of redesigning the product.

LockDay is not an LOS replacement. It is a checkpoint: paste four columns — loan ID, lock date, lock days, lender — and get a ranked radar, a safe-to-close date with a 7-day buffer, per-loan extension cost and a Monday digest. The buyer is the daily user, no borrower PII is required, and there is nothing to procure. The wedge is narrow on purpose: no LOS integration, no rate benchmarking, no borrower portal.

2. Smallest sellable MVP

Four things must work for the $199 charge to be defensible: correct business-day math with US holidays and lender presets; a ranked radar with green/amber/red states and a configurable buffer; a per-loan Extension Decision Card PDF using the officer's own per-day cost input; and a scheduled Monday digest. CSV paste with a four-field mapper is the only intake. LOS APIs, SMS, team permissions and a mobile app stay out for 30 days.

3. Technical implementation plan

Next.js on Vercel, Neon Postgres with Drizzle, magic-link auth through Resend, Stripe Checkout with webhooks, react-pdf for the card, PapaParse for client-side CSV, date-fns-tz plus a static US holiday list, and Vercel Cron for the Monday send. Parsing happens in the browser, so raw exports never have to persist; only mapped loan rows land in Postgres. Build order is schema, calculator with fixtures, mapper, radar, paywall, deploy, digest, PDF, free checker, lender presets.

The hardest risk is the calendar layer: observed-holiday shifts and calendar-versus-business-day lender conventions, where one wrong red state destroys trust. Mitigation is a pure, tested module with twelve real-world fixtures and an explicit verify-with-your-lender line on every artifact. An LLM is used only for lender-name normalization fallback and one digest summary sentence — never for date math.

4. Pricing and monetization

Founding Solo is $199 one-time for 12 months, single officer, unlimited pipelines and loans. Shop is $399 one-time for up to five officers with a shared lender library and per-user digests. One-time beats monthly here because a lock expires before a subscription renews, and a card charge needs no approval. The first-revenue offer is a free audit of the officer's own export, then the founding link while their at-risk count is on screen. Growth after sale one: a $50 credit per forwarded digest that converts, the Shop tier for owners, and renewal at $199 in twelve months.

5. First-customer acquisition

One channel: direct outreach to loan officers in r/loanoriginators, mortgage Facebook groups and LinkedIn, offering to run their own pipeline export. Daily cadence is 20 LinkedIn DMs plus 10 free audits. The message angle never changes — free lock-risk check on the real export, no login, no borrower data. Week one goal: 30 free audits run and the first paid customer by day 12. Referrals replace ads entirely; ad spend stays at zero.

6. Detailed 30-day roadmap

Days 1–5 build and freeze the MVP: calculator with fixtures, CSV mapper, radar, Stripe. Days 6–9 add the Monday digest, the Extension Decision Card PDF, the free no-login checker and the editable lender library. Days 10–14 launch publicly, run live screenshare audits and close the first sales. Days 15–21 scale outreach to 20 DMs a day, ship the referral credit, publish one anonymized case page and open the Shop conversation. Days 22–28 run the second community wave, push the December 16 deadline and attempt a second Shop sale. Days 29–30 reconcile Stripe, close outstanding payments and publish the final profit figure.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 4 buyers at $199, $796 gross, $24 fees, $35 operating. Base: 14 buyers at $199, $2,786 gross, one $199 refund, $85 fees, $60 operating. Upside: 24 buyers — 20 Solo at $199 and 4 Shop at $399 — $5,568 gross, $199 refunds, $169 fees, $95 operating. Hackathon profit is gross minus refunds, chargebacks and payment fees. Business profit also subtracts operating cost. Payment fees assume Stripe at 2.9% plus $0.30. No paid marketing is planned, so ad spend is zero in every scenario.

8. Main risks and validation experiments

First: officers say their LOS already alerts on locks. Test with ten DMs asking how they track lock dates today; if eight say LOS alerts are enough and nobody buys after 30 conversations, the wedge is wrong. Second: data trust. Browser-side parsing, four columns, no borrower names — kill signal is five live screenshares where fewer than two will paste. Third: December seasonality compresses urgency; compare week-1 and week-3 reply rates and pivot to broker-owners if replies halve. Fourth: the $199 one-time price caps revenue, handled by the Shop tier and referral credit. Fifth: a calendar rule error would be fatal, so a confirmed wrong red state blocks further sales until re-tested.

9. First 24-hour action plan

Hours 1–3: schema, holiday list, twelve fixture tests. Hours 3–6: calculator plus CSV mapper. Hours 6–9: radar UI with buffer setting. Hours 9–12: Stripe checkout and magic link. Hours 12–16: deploy, run three real exports, capture a redacted screenshot. Hours 16–24: build a 50-name outreach list, send the first 20 DMs, queue the community post.

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 →