ReplyLock
Replay-locks your AI chatbot's answers to a curated set for client demos and handoffs, so the same question always returns the same answer.
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.
Freelance and small-agency chatbot builders (1-10 people) shipping Voiceflow, Botpress or custom GPT assistants for SMB clients, in the 1-2 weeks before a client demo, UAT session or project handoff.
Monetization potential 4.6/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; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.5/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
11 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Freelance and small-agency chatbot builders (1-10 people) shipping Voiceflow, Botpress or custom GPT assistants for SMB clients, in the 1-2 weeks before a client demo, UAT session or project handoff.
Why now
Every freelancer shipping LLM bots now has a dated client demo, a card on file and no cheap way to freeze approved answers without stripping the live model out of the build.
Problem
In a client demo the same question returns a different answer than the one the client approved last week, which makes the bot look unreliable and triggers unpaid rework.
Solution
A CLI captures approved question/answer pairs with a fixed seed into lock.json, a hosted proxy serves those locked answers on match and falls back to the live model otherwise, and a dashboard shows which questions were not locked during the call.
Product opportunity and positioning
ReplyLock sells a fixed outcome to a person with a date on the calendar. A freelance chatbot builder has spent two weeks on a Voiceflow or Botpress assistant for an SMB client, the client approved a set of answers on a call, and the demo or handoff is next week. Run the same question again and the model answers differently. The bot looks broken, the client asks for changes, and the builder eats unpaid rework. Nobody sells that builder a cheap way to freeze the approved answers without ripping the live model out of the product.
The offer is a lock file plus a proxy. replylock capture calls the model with a fixed seed and records question, answer, seed and model version into lock.json, committed with the project. A hosted /v1/chat endpoint replaces the model URL in one line of config. Messages matching a locked question - exactly or by embedding similarity - return the locked answer immediately. Everything else passes through to the live model, unchanged. A dashboard lists the questions that fell through so the builder can add them after the call, and a one-page PDF lets the client sign off on what was approved.
JEV scored this concept 6.44 weighted, 64.4 overall, band C at 0.72 confidence. The profile matters more than the total: speed to first revenue 8.51 and solo build feasibility 7.59, against monetization potential 4.56. That is a product that can be sold this week and must earn its second dollar later. Month one is therefore a one-time $149 project purchase aimed at panic timing; a repeat path (90-day extension, second project) is designed on day 23 but deliberately excluded from the 30-day projection.
Positioning: Demo Mode for a client's chatbot, one URL swap. Differentiation is the deliverable, not the technique. This is not an observability platform, not a CI gate, not an inference API, and not a golden-snapshot regression suite for Series A platform teams. The buyer receives a file, a URL and a PDF, in the week they are most afraid of a bad call.
The wedge is narrow on purpose. The buyer already has a paying client and a demo date, the $149 is a project expense that needs no procurement, and the deliverable is small enough for one person to build and support. Wider versions - team seats, self-hosting, tracing, multi-agent orchestration - are explicitly refused, because each one adds a support burden the founder cannot carry alone.
One honest limit: if builders treat answer variance as harmless, this becomes a novelty. The outreach in the first week is designed to test that directly, by offering to freeze a demo for free and watching who says yes.
Smallest sellable MVP
A CLI that writes lock.json from approved Q&A pairs, a hosted proxy URL that serves those answers and falls back to the live model, and a Stripe link that issues the key automatically in under 60 seconds.
Must-have features
- `replylock capture` CLI reading a questions file plus a fixed seed and writing lock.json
- POST /v1/chat proxy with per-project key auth and locked-answer lookup
- Embedding similarity matching with a tunable threshold (default 0.86)
- Unmatched-question log with a one-click 'add to lock' action
- Stripe Checkout for $149 and $499 with webhook-issued keys and Resend email delivery
- One-page approved-answers PDF exported from lock.json
- 90-day key expiry tracked per project
Explicitly out of scope
- GitHub Action, PR gating or regression test runner
- Prompt tracing, cost analytics or observability dashboards
- Multi-agent orchestration or RAG pipeline features
- Self-hosted or SSO enterprise deployment
- Free tier, team seats or seat management
- Human-managed onboarding or a 24/7 support promise
Demo flow (what the buyer sees)
- Builder runs `replylock capture` with 20-30 approved questions and a seed
- CLI writes lock.json and prints the locked pair count
- Builder swaps the model base URL for their project proxy URL
- A locked question sent to the bot returns the exact approved answer
- A paraphrased question returns the locked answer via similarity match
- An unlocked question passes through to the live model and appears in the dashboard
- Builder clicks 'add to lock' and the answer is frozen from then on
- Builder downloads the approved-answers PDF for client sign-off
Technical implementation plan
Stack
Architecture
One Next.js app serves the marketing page, the dashboard and the /v1/chat proxy. On request the proxy reads the project key, pulls that project's lock set from a Redis cache (Postgres on miss), embeds the incoming message, and compares against stored question vectors. Above threshold it returns the locked answer; below it forwards to the buyer's configured provider and logs the unmatched question. Stripe webhooks write a project row, generate a key, set a 90-day expiry and trigger the Resend email. Nothing is provisioned by hand.
Build steps
- Create the Next.js repo, deploy to Vercel, provision Supabase and Upstash
- Build `replylock capture` with fixed seed, provider selection and lock.json schema
- Implement /v1/chat with key auth, exact-match normalization and Redis cache
- Add embedding generation and cosine similarity with a per-project threshold
- Build the minimal dashboard: locked pairs, unmatched questions, add-to-lock
- Create Stripe Checkout for both tiers and the webhook that issues keys
- Add the Resend delivery email and the quickstart page
- Export the approved-answers PDF from lock.json
- Load-test locked-answer latency and set an alerting threshold
AI components
- Model generation at capture time (OpenAI or Anthropic) with a fixed seed
- text-embedding-3-small for question similarity
- Live model fallback for messages not present in the lock set
Pricing and monetization
Project Lock
Entry offerFor Freelance chatbot builder about to demo or hand off one client project
- Up to 100 locked Q&A pairs
- Hosted Demo Mode proxy and project key for 90 days
- Similarity threshold tuning
- Unlocked-question dashboard
- Client sign-off PDF
Agency 5-Pack
For Small agency locking several client projects
- 5 project locks
- Shared dashboard across projects
- Same features as Project Lock
Model: One-time per-project purchase, priced as a project expense a freelancer can put on a client invoice.
First revenue offer: I will lock 20 of your chatbot's approved answers for free before your demo, send you the lock.json and the client PDF, and you only pay $149 if you want the hosted Demo Mode URL for the call.
Expected ACV: $149
Upsell path: Day 23 email to every buyer: $99 to lock a second project, and a $49 90-day extension when the original key expires. Neither is counted in the 30-day projection.
First-customer acquisition
Direct outreach in the Voiceflow and Botpress community forums and Discords, plus r/nocode, to builders posting about demos, UAT or client handoffs.
Where to find them
- Voiceflow community forum threads mentioning demo, launch or client feedback
- Botpress Discord #showcase and #help channels
- r/nocode and r/LangChain posts about inconsistent bot answers
- n8n community forum AI-agent threads
- Indie Hackers and small-agency Slack groups for no-code builders
- Freelancers on Upwork and Contra advertising Voiceflow or Botpress delivery
Exact outreach motions
- Reply to a public post about a demo problem with a specific, non-salesy diagnosis and an offer to freeze their answers free
- DM the poster offering to lock 20 answers for their project this week at no cost
- Deliver the lock.json and PDF within 24 hours of getting their question list
- Ask one question after delivery: is the demo date set, and do they want the hosted URL for $149
- Follow up once at 48 hours with a screenshot of which questions went unlocked in their session
- Post a public before/after lock.json diff in two communities as proof of work
- Pitch the 5-Pack to any agency running multiple bot retainers
Message template
Saw your post about the bot answering differently in front of a client. I can freeze 20 of your best answers into a lock file this week for free - same question, same answer, every time. No cost, no call needed unless you want one. Want me to do it for your project?
30-day execution roadmap
Week 1 · Build & validate · 7 days
Ship infra and payment rails before any customer exists
- Create Next.js repo on Vercel with a health route
- Provision Supabase Postgres and Upstash Redis
- Register domain and connect Resend
- Open Stripe and link the account to TrustMRR
Deliverable: Live deploy, empty database, Stripe connected to TrustMRR, zero customers
Produce a valid lock.json
- Build `replylock capture` reading a questions file plus a fixed seed
- Call OpenAI and Anthropic and store model version per pair
- Define the lock.json schema
- Run it against three sample bot question sets
Deliverable: lock.json v1 written by the CLI in under 30 seconds
Serve locked answers with a live fallback
- Implement POST /v1/chat with per-project key auth
- Add exact-match normalization and Redis cache
- Forward unmatched messages to the buyer's provider
- Log every unmatched question with a timestamp
Deliverable: Proxy returns locked answers or live fallback, with latency logged
Catch paraphrases and show what slipped
- Generate text-embedding-3-small vectors per locked question
- Add cosine similarity with default threshold 0.86
- Build the dashboard: locked pairs and unmatched questions
- Wire one-click add-to-lock that re-embeds the new pair
Deliverable: A paraphrased question hits the lock; dashboard lists unmatched questions
Sell without manual onboarding
- Create Stripe Checkout for $149 and $499
- Webhook issues key, proxy URL and 90-day expiry
- Resend email delivers the key and quickstart
- Run an end-to-end test with a test card
Deliverable: MVP complete: paid to working proxy in under 60 seconds
Give the buyer something to send the client
- Generate the approved-answers PDF from lock.json
- Write a 300-word quickstart with the one-line URL swap
- Measure p95 latency on locked hits
- Fix any locked hit slower than 500ms
Deliverable: PDF export live and a public quickstart page
First 15 real touches and one free lock
- Build a list of 40 builders from Voiceflow and Botpress communities
- Send 15 DMs offering a free demo lock
- Deliver one free lock with PDF to a live prospect
- Start a tracking sheet for touches, replies and free locks
Deliverable: 15 touches sent, 1 free lock delivered
Week 2 · Launch & first sale · 7 days
Volume and reply handling
- Send 25 more touches across r/nocode and n8n
- Reply to every public thread mentioning demo or UAT
- Deliver two more free locks
- Book the first 15-minute call
Deliverable: 40 cumulative touches, 3 free locks, 1 call booked
Publish one real artifact
- Write a short post on why bots answer differently in every demo
- Include a real before/after lock.json diff
- Post in two Discords and r/nocode
- Invite comments, not signups
Deliverable: Post published and the first inbound reply
Pitch the hosted proxy
- Ask what broke in their last demo
- Show their own bot running through the proxy
- Send the Stripe link within 10 minutes
- Record the objection word for word
Deliverable: First Stripe link sent to a warm prospect
Convert warm replies
- Follow up each free-lock recipient once with the unmatched-question screenshot
- Nudge every open checkout link at 48 hours
- Send 20 new touches
Deliverable: 3 open checkout links
Close the first $149
- Close one Project Lock, discounting to $99 for a case study if needed
- Confirm the payment lands in the TrustMRR-connected account
- Ask for two names to contact
- Log what actually closed it
Deliverable: First revenue collected inside the window
Turn the sale into evidence
- Write a 150-word case study using the buyer's own before/after
- Add it to the landing page and the DM template
- Send 25 touches referencing the case study
Deliverable: Case study live and 25 touches sent
Cut what did not work
- Tally touches, replies, free locks, calls and sales
- Kill the weakest channel and double the best
- Set a week-3 target of 3 sales
- Fix the single most common objection in the product or copy
Deliverable: Channel decision and week-3 targets written down
Week 3 · Repeat & systematize · 7 days
25 touches per day
- Send 25 touches to builders with recent handoff posts
- Pitch the 5-Pack to two agencies running client bots
- Deliver two free locks
Deliverable: 25 touches, 2 agency conversations, 1 sale
Sell the 5-Pack
- Add a shared multi-project dashboard view
- Draft the agency one-pager: 5 locks for the price of 3.3
- Send it to 10 small agencies
Deliverable: Agency page live and 10 agency touches sent
Ship a fix tied to a real refusal
- Categorize every 'no' received so far
- Ship the top fix: exact-match-only mode or a threshold control
- Update the quickstart and the DM copy
Deliverable: One shipped fix traceable to a real objection
Protect the demo itself
- Add uptime monitoring with alerting on the proxy
- Add fallback to a cached answer on provider timeout
- Publish a status page
Deliverable: Monitoring, fallback path and status page live
Sustain the pipeline
- Send 25 touches
- Reply to every unanswered thread
- Deliver two free locks
Deliverable: 25 touches and 2 free locks delivered
Public proof of work
- Host a 45-minute lock clinic in one Discord
- Lock a volunteer's bot live on the call
- Record it and cut a 60-second clip
Deliverable: Clinic held, clip posted, 2 warm leads
Forecast the finish
- Compare actual revenue and fees against the scenarios
- Decide whether the upside case needs a second offer
- Rebuild the day 22-30 plan around what worked
Deliverable: Updated forecast and a written closing plan
Week 4 · Scale what works · 7 days
Close open links
- Nudge every open checkout with one specific reason to buy now
- Offer a 48-hour $119 close to anyone stalled twice
- Send 25 new touches
Deliverable: 1-2 additional sales and a refreshed pipeline
Build the path past one purchase
- Email all buyers: $99 to lock a second project
- Draft the $49 90-day extension for expiring keys
- Measure open and reply rates
Deliverable: Repeat offer sent to every buyer
Fill the final week
- Send 25 touches prioritizing builders with demos this month
- Deliver two free locks
- Ask each free-lock recipient for a straight yes or no
Deliverable: 25 touches, 2 free locks, 2 direct answers
Compounding organic reach
- Publish a second post with the locked-hit latency benchmark
- Post the 60-second clinic clip in two more communities
- Put a sample lock.json on the landing page
Deliverable: Second post live and public sample file
Remove pre-sale friction
- Answer every pre-sale question within 2 hours
- Offer a free re-lock if the first lock misses
- Send 20 touches
Deliverable: Zero unanswered questions and 20 touches sent
Best-case push
- Pitch the 5-Pack to every agency conversation still open
- Offer a $149 plus $99 second-project bundle
- Send 25 touches
Deliverable: All agency conversations answered
Clean the books
- Reconcile Stripe payouts against TrustMRR records
- Document every refund and chargeback
- Confirm all revenue landed inside the window
Deliverable: Reconciled payment ledger
Days 29-30 · Consolidate · 2 days
Close before the wire
- Send a final 24-hour note to every open link
- Answer live questions in Discord
- Deliver any outstanding free locks
Deliverable: Final pipeline clear and every link answered
Final day before 13:00 UTC
- Collect final payments before 2026-12-16 13:00 UTC
- Freeze the ledger and screenshot verified profit
- Write a one-page retro on what sold and what did not
Deliverable: Closed books and submitted results
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: 3 buyers reached from free-lock samples and community replies; no paid marketing.
- Base: 12 buyers, roughly one every two days, with the $149 Project Lock dominating.
- Upside: 30 buyers with 2 of them on the $499 Agency 5-Pack, giving a blended ARPU of about $172.
- Payment fees assume Stripe at 2.9% + $0.30, rising to roughly 3.8% in the upside case for international cards and currency conversion.
- Refunds are modelled at one Project Lock in the upside case and zero in the other two; chargebacks are zero across all three.
- Ad spend is zero in conservative and base because the channel is organic outreach; upside assumes $150 for one sponsored community newsletter placement.
- Operating costs cover Vercel, Supabase, Upstash, domain and OpenAI/Anthropic generation plus embedding calls to serve those customers.
- All figures are projections from stated assumptions, not verified revenue or existing customers.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $14
- Paid marketing
- $0
- Hackathon profit
- $433
- Operating costs
- $25
- Business profit
- $408
Base case
12 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $58
- Paid marketing
- $0
- Hackathon profit
- $1,730
- Operating costs
- $60
- Business profit
- $1,670
Optimistic
30 customers- Refunds
- $149
- Chargebacks
- $0
- Payment fees
- $196
- Paid marketing
- $150
- Hackathon profit
- $4,665
- Operating costs
- $140
- Business profit
- $4,525
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $1,788
- Payment fees (3.9%)
- $70
- Paid marketing
- $0
- Hackathon profit
- $1,718
- Business profit
- $1,658
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. Hackathon profit excludes hosting, tooling and AI delivery costs; business profit subtracts them.
Main risks and validation experiments
Risk 1Builders treat model variance as harmless and will not pay to freeze it.
Lead with the free lock so the buyer sees their own inconsistent answers side by side before any price is mentioned.
Offer 10 free locks in week one and count how many ask for the hosted URL afterwards.
If fewer than 3 of 10 free-lock recipients want the paid proxy by day 14, reposition or stop.
Risk 2The hosted proxy adds latency or fails during the exact demo it protects.
Serve locked answers from Redis with no model call, add a cached-answer fallback on timeout, and publish a status page.
Run 200 locked-hit requests against the deployed proxy and record p95 latency and error rate before the first sale.
If locked hits cannot stay under 500ms p95 or the error rate exceeds 1%, do not sell the hosted URL.
Risk 3Paraphrase matching misses and the demo shows an unlocked answer at the worst moment.
Expose the similarity threshold per project, ship an exact-match-only mode, and log every unmatched question for post-call review.
Take 30 real client questions per free-lock project, rephrase each three ways, and measure hit rate.
If rephrase hit rate stays below 80% at a threshold that does not over-match, ship exact-match only and re-price.
Risk 4Voiceflow, Botpress or a platform ships a native demo mode and compresses the wedge.
Own the cross-provider and custom-GPT case, and be the artifact that travels with the project file rather than a platform setting.
Ask 10 prospects which platform they ship on and whether it already offers a frozen-answer mode.
If a platform already ships frozen answers for a majority of prospects, narrow to custom and multi-provider builds only.
Risk 5Community outreach is read as spam and the founder is banned from the main channel.
Always answer the public thread usefully first, never paste the same text twice, and ask permission before sending a DM.
Track reply and removal rates across the first 40 touches and stop any message that gets removed.
If two communities remove posts or issue warnings in week one, switch to direct email of public project authors only.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create GitHub repo and Next.js app, deploy to Vercel
- Register the domain and point it at the deployment
Output: A public URL returning a health response
Hours 3-5
- Provision Supabase tables for projects, keys, locks and session logs
- Provision Upstash Redis and connect both to the app env vars
Output: Live database schema and cache connection
Hours 6-9
- Build `replylock capture` with fixed seed and lock.json output
- Test it against one real bot question set of 20 pairs
Output: A committed lock.json generated by the CLI
Hours 10-13
- Open Stripe, create the $149 Checkout link, link the account to TrustMRR
- Draft the webhook that will issue keys
Output: Working checkout in test mode, zero customers, zero payments
Hours 14-24
- Build a list of 40 builders from Voiceflow, Botpress and r/nocode
- Send the first 8 free-lock offers using the message template
- Log every touch in the tracking sheet
Output: 40-name prospect list and 8 touches sent
Full 30-day launch report
Read the full generated report
ReplyLock - 30-Day Launch Report
Window: 2026-11-16 13:00 UTC to 2026-12-16 13:00 UTC. One founder. Every number below is a projection from stated assumptions, not verified revenue, customers or traction.
1. Product opportunity and positioning
A freelance chatbot builder has a date on the calendar. Two weeks of work sit in a Voiceflow or Botpress assistant, the client approved a set of answers on a call, and the demo or handoff is next week. Run the same question again and the model answers differently. The bot looks broken in front of the person paying for it, and the builder absorbs the rework.
ReplyLock sells the fix as an artifact, not an API. The capture CLI calls the model with a fixed seed and writes question, answer, seed and model version into lock.json, committed with the project. A hosted /v1/chat endpoint replaces the model URL in one line of config. Matched messages return the locked answer instantly; everything else passes through to the live model untouched. A dashboard lists the questions that fell through so the builder can freeze them after the call, and a one-page PDF lets the client sign off on what was approved.
JEV scored this 6.44 weighted and 64.4 overall, band C at 0.72 confidence. The shape of the score is the instruction: speed to first revenue 8.51 and solo build feasibility 7.59, against monetization potential 4.56. This is a product that can be sold this week and must earn a second dollar later. Month one is therefore a one-time $149 project purchase aimed at panic timing. The repeat path exists (day 23: a $99 second project, a $49 extension) but is excluded from the 30-day projection so the forecast does not depend on it.
Positioning is Demo Mode for a client's chatbot, one URL swap. Differentiation is the deliverable. This is not observability, not a CI gate, not a golden-snapshot regression suite for platform teams. The buyer gets a file, a URL and a PDF, in the week they are most afraid of a bad call.
2. Smallest sellable MVP
Six things ship: the capture CLI, the proxy, embedding-based matching with a threshold, the unmatched-question dashboard, Stripe checkout that issues a key automatically, and the sign-off PDF. Nothing else. If similarity matching slips, exact-match plus text normalization ships on day 4 with an honest note about what it covers. The product must be sellable on day 5, not perfect on day 12.
3. Technical implementation plan
One Next.js app on Vercel serves the landing page, the dashboard and the proxy. Supabase Postgres holds projects, keys, locks and unmatched-question logs. Upstash Redis caches each project's lock set and its embeddings so a locked answer is served without a model call. On request the proxy authenticates the project key, embeds the incoming message with text-embedding-3-small, compares against stored question vectors, and either returns the locked answer or forwards to the buyer's configured provider. Stripe webhooks create the project, generate the key, set a 90-day expiry and trigger a Resend email, so nobody is provisioned by hand.
The hardest technical risk is latency and availability at the worst possible moment. A proxy that is slower than the model, or that errors during the demo, is worse than the problem. The plan answers that with cache-first locked answers, a cached-answer fallback on provider timeout, an uptime monitor with alerting on day 18, and a documented p95 target of 500ms for locked hits before the first sale is attempted.
4. Pricing and monetization
Project Lock is $149 one-time for up to 100 locked pairs, a hosted proxy key for 90 days, threshold tuning, the dashboard and the PDF. Agency 5-Pack is $499 for five projects with a shared dashboard. Both are card purchases a freelancer bills to a client, with no procurement and no seat management.
JEV's monetization score of 4.56 is the known weak point. The answer inside the window is price discipline, not price cuts: hold $149, discount only to $99 in exchange for a named case study, and never discount the 5-Pack. The real fix is scheduled for day 23 - a $99 second-project offer to existing buyers and a $49 extension at expiry - but it is modelled as upside, never as base case.
5. First-customer acquisition
One channel: direct outreach where builders complain in public. Voiceflow community forum threads about demos and client feedback, Botpress Discord, r/nocode, the n8n community, and freelancers advertising Voiceflow or Botpress delivery on Upwork and Contra.
The motion is a free lock, not a pitch. Answer the public thread usefully, offer to freeze 20 approved answers at no cost, deliver lock.json and the PDF within 24 hours, then ask for $149 if they want the hosted URL for the call. One follow-up at 48 hours with a screenshot of which questions went unlocked. Target for week one: 40 touches, 3 free locks delivered, 1 booked call, 1 paid project. Nothing here costs money, which is why ad spend is zero in the conservative and base cases.
6. 30-day execution roadmap
Days 1-7 build and sell in the same week. Infrastructure and Stripe-on-TrustMRR land on day 1 before any customer exists. The CLI, proxy, matcher, dashboard, checkout and PDF are live by day 5. Days 6 and 7 add the sign-off artifact and the first 15 touches with one delivered free lock.
Days 8-14 convert. Twenty-five more touches on day 8, a public before/after post on day 9, the first sales call on day 10, follow-ups on day 11, first revenue targeted for day 12. Day 13 turns that sale into a case study and day 14 cuts the weakest channel.
Days 15-21 scale what worked. Daily 25-touch volume, the agency tier and its one-pager on day 16, one shipped fix tied to a real objection on day 17, reliability work on day 18, a live Discord lock clinic on day 20, and a midpoint forecast on day 21.
Days 22-30 close. Nudge open checkouts, send the repeat offer on day 23, keep touches running to day 27, reconcile the ledger on day 28, send a final 24-hour note on day 29, and collect everything before 13:00 UTC on day 30. Gates: MVP day 5, first sale day 12.
7. Revenue and profit scenarios
Projections only, built from the assumptions listed in the structured data.
| Scenario | Customers | ARPU | Gross | Refunds | Fees | Ad spend | Hackathon profit | Operating | Business profit |
|---|---|---|---|---|---|---|---|---|---|
| Conservative | 3 | $149 | $447 | $0 | $14 | $0 | $433 | $25 | $408 |
| Base | 12 | $149 | $1,788 | $0 | $58 | $0 | $1,730 | $60 | $1,670 |
| Upside | 30 | $172 | $5,160 | $149 | $196 | $150 | $4,665 | $140 | $4,525 |
Hackathon profit is what the contest ranks: gross minus refunds, chargebacks, processing fees and paid marketing. Hosting, domain, tooling and model/embedding spend are excluded there and subtracted only in business profit. Fees assume Stripe at 2.9% + $0.30, rising toward 3.8% in the upside case for international cards and currency conversion. The upside ARPU is blended because two of the 30 buyers are assumed on the $499 5-Pack. All three cases are hypotheses, not forecasts of verified income.
8. Main risks and validation experiments
Variance-as-harmless is the existential risk, tested by delivering 10 free locks and counting who asks for the hosted URL; fewer than 3 of 10 by day 14 means stop. Proxy latency and failure is tested with 200 locked-hit requests and a 500ms p95 gate. Paraphrase misses are tested by rephrasing 30 real client questions three ways and requiring an 80% hit rate at a threshold that does not over-match. Platform commoditisation is tested by asking 10 prospects whether their platform already freezes answers. Channel risk is tested by tracking reply and removal rates across the first 40 touches and stopping any message that gets removed.
9. First 24 hours
Hours 1-2: repo, Next.js app, Vercel deploy, domain. Hours 3-5: Supabase schema and Redis. Hours 6-9: capture CLI writing a real 20-pair lock.json. Hours 10-13: Stripe checkout plus TrustMRR connection, zero customers and zero payments at this point. Hours 14-24: 40-name prospect list and the first 8 free-lock offers sent.
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 →Repo Second Opinion
A paid, plain-English code risk report for non-technical founders who paid an agency or freelancer to build their app and now need to know if the code is safe to keep building on.
MissedCall Quote Card
Turns a missed call plus a customer photo into a ready-to-send SMS quote card for solo home-service pros.
TrustPacket
TrustPacket turns a 12-question intake into the exact DPA, subprocessor list, security overview, and hosted trust page an enterprise buyer asks for — exported as one send-ready ZIP in under 10 minutes.