PortalProof Handoff Kit
A Chrome extension that records a browser data-entry task once and exports a self-contained, replayable handoff kit so a small ops team can rerun it without the founder.
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.
Owner or ops lead at a 5-50 person bookkeeping, freight-brokerage or insurance-agency office whose staff re-type the same data into non-API web portals.
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 5 days; the plan targets a first sale on day 10; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.2/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
10 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Owner or ops lead at a 5-50 person bookkeeping, freight-brokerage or insurance-agency office whose staff re-type the same data into non-API web portals.
Why now
The buyer already pays a person to do the re-typing, so the budget exists this week and needs no procurement, no IT project and no integration with the portal.
Problem
Staff burn hours re-typing identical records into legacy portals, and when someone leaves the task knowledge leaves with them.
Solution
The user records one portal task; the extension captures fields and steps, then exports a signed JSON kit plus a one-page runbook that the buyer's staff replays in-browser with a confirm prompt per field.
PortalProof Handoff Kit: opportunity and positioning
Small bookkeeping, freight-brokerage and insurance offices run on portals that were never built to integrate: carrier booking screens, government filing forms, insurer claim pages. Staff re-type the same record into those screens several times a day. The cost hides inside payroll and nobody measures it. When the person who knows the click sequence leaves, the office loses the capability as well as the hours.
PortalProof Handoff Kit sells the handoff rather than the automation. The buyer is the owner or ops lead of a 5-50 person office. They already pay a person to do the re-typing, so the budget exists today and no procurement cycle stands in the way. The deliverable is a Chrome extension that records one portal task and exports two files: a signed JSON kit and a one-page printable runbook. Their staff replays the kit in the browser, confirming each field as it fills.
Against the realistic alternatives: a screen-recording SOP shows what happened but cannot be executed; a written checklist is re-interpreted differently by every new hire; an enterprise RPA seat is priced and implemented for companies far larger than this buyer. PortalProof's output is a runnable artifact the buyer tests in ten minutes on their own machine. Field matching by label and ARIA hints, with a selector fallback, keeps the kit usable when the portal restyles.
The wedge is deliberately narrow. JEV scores this concept 59.7/100 (band C, confidence 0.62). Speed to first revenue is the strongest dimension at 8.22; market demand (4.78) and monetization potential (4.59) are the weak ones. The plan is shaped by that shape: demand gets validated by direct-message replies rather than forecasts, delivery stays concierge for the first ten buyers, and the price is a one-time fee small enough to approve without a meeting. The monetization weakness is answered by an Office Pack upgrade and paid re-records when a portal changes, not by bolting on a subscription the buyer did not ask for.
The one-sentence pitch the whole launch runs on: record your worst portal task once, get a replayable kit and a one-page runbook in 48 hours for $149, refund if it does not replay on your machine.
Smallest sellable MVP
One recorded portal task exported as a JSON kit plus a PDF runbook, replayable in the buyer's browser under a license key issued by Stripe.
Must-have features
- Chrome extension recorder capturing clicks, keystrokes and field labels
- Field-intent tagger storing label text and ARIA hints instead of raw CSS selectors
- Kit exporter producing a portable JSON file
- Printable one-page runbook PDF generated with jsPDF
- Replay runner executing a kit in the active tab with a per-step confirm prompt
- License key check gating kit export and replay via Cloudflare Worker
- Stripe Checkout page issuing license keys by webhook
Explicitly out of scope
- No cloud dashboard or team accounts
- No scheduled or headless automation
- No marketplace of shared kits
- No LLM-based self-healing locator at replay time
- No support SLA or onboarding calls
- No CRM or billing portal beyond Stripe
Demo flow (what the buyer sees)
- Founder joins a 15-minute screen share with the buyer
- Buyer demonstrates the portal task once
- Extension records steps, field labels and keystrokes
- Exporter writes the kit JSON and the runbook PDF
- Stripe payment completes and the webhook emails a license key
- Buyer opens the runbook, hits Run, and confirms each field
- Kit is replayed twice by the buyer before the founder leaves the call
Technical implementation plan
Stack
Architecture
A content script captures events in the active tab and writes a draft session to IndexedDB. The service worker owns export, license validation and PDF generation. Export and replay both call a Cloudflare Worker that checks the license key against KV. Stripe Checkout creates the order; a webhook mints the key and emails it. The landing page sits on Cloudflare Pages and links straight to both checkout prices.
Build steps
- Scaffold the MV3 extension repo with content script, popup and service worker
- Create the two one-time Stripe prices and connect the account to TrustMRR
- Implement click and keystroke capture with label and ARIA extraction
- Define the versioned kit JSON schema and the field-intent tagger
- Build the export path writing kit JSON to disk
- Build the replay runner with per-step confirm and abort
- Add the Cloudflare Worker license check and gate export and replay
- Add the Stripe webhook that issues and emails the key
- Generate the runbook PDF from the kit JSON
- Dogfood on three sandbox portals and ship v0.2 with label-similarity scoring
AI components
- A single LLM pass at export time drafts runbook prose from captured step labels, under $0.02 per kit; nothing model-based runs at replay time and the kit works if that step is skipped
Pricing and monetization
Single Kit
Entry offerFor Owner of one small ops office
- One recorded portal task kit
- Printable runbook
- 30-day replay license
Office Pack
For Ops lead with several recurring tasks
- Up to four task kits
- Runbook set
- 90-day replay license
Model: One-time purchase per kit with a larger multi-kit pack; no subscription inside the 30-day window.
First revenue offer: I will record your worst portal task and hand you a replayable kit plus a one-page runbook for $149, delivered within 48 hours. If it does not replay cleanly on your machine, refund.
Expected ACV: $149
Upsell path: Offer the Office Pack on the recording call when the buyer names a second and third task, then sell paid re-records when a portal changes, which lifts blended ARPU toward $190.
First-customer acquisition
Direct messages to people who publicly describe repetitive portal data entry in niche communities.
Where to find them
- r/Bookkeeping threads about repetitive client portal entry
- r/FreightBrokers posts about carrier and load-board re-typing
- Small-business Facebook groups for bookkeepers and freight agents
- Upwork job posts for data entry and virtual assistant work
- LinkedIn ops leads at 5-50 person bookkeeping and insurance agencies
Exact outreach motions
- Send 30 messages naming the exact portal the poster mentioned and offer a flat $149 recorded kit
- Send 30 more the next day and one follow-up after five days on non-replies
- Book a 15-minute screen share to see the portal before quoting
- Send the Stripe link immediately after the call and promise 48-hour delivery
- Ask every buyer for one named referral and offer $50 off their next kit
Message template
Saw your post about re-typing [portal] records. I built a Chrome extension that records the task once and gives your staff a replayable kit plus a one-page runbook: $149, delivered in 48 hours, refund if it does not replay on your machine. Want me to record yours?
30-day execution roadmap
Week 1 · Build & validate · 7 days
Infrastructure and payments
- Create the Chrome MV3 repo with content script, popup and service worker.
- Create Stripe one-time prices at $149 and $399.
- Connect the Stripe account to TrustMRR before any payment.
- Deploy a holding page on Cloudflare Pages.
Deliverable: Repo scaffold, two live checkout links, holding page live.
Event capture
- Capture click and keystroke events in the active tab.
- Store each step with element label, ARIA role and nearby text.
- Persist draft sessions in IndexedDB.
- Test capture on two real portals.
Deliverable: Recorder that saves a working draft session.
Schema and intent tagger
- Define kit JSON schema with steps, field intents, value sources and version.
- Build the field-intent tagger writing labels instead of CSS selectors.
- Add a manual step-ordering panel.
- Export a draft kit to file.
Deliverable: Versioned kit schema and working exporter.
Execution in the browser
- Execute kit steps with a confirm prompt per field.
- Match fields by label and ARIA first, selector second.
- Add pause, resume and abort controls.
- Log a replay result summary.
Deliverable: Replay runner filling fields in the active tab.
MVP completion
- Deploy a Cloudflare Worker validating license keys and kit versions.
- Gate export and replay behind the key.
- Generate the one-page PDF runbook with jsPDF.
- Wire the Stripe webhook to issue and email the key.
Deliverable: MVP: a paid kit can be exported, keyed and replayed.
Fix the worst breakage
- Record three tasks on public sandbox portals.
- Fix the top five replay failures.
- Record a 60-second demo video.
- Publish the pricing page.
Deliverable: Demo video and live pricing page.
Build the 60-name pipeline
- Collect 60 posters describing repetitive portal entry.
- Log name, portal, office size and thread link.
- Draft two pitch variants for testing.
- Set up a plain spreadsheet CRM.
Deliverable: 60-name target list with portal notes.
Week 2 · Launch & first sale · 7 days
First 30 messages
- Send 30 DMs using the two-line pitch.
- Offer a paid kit build for their worst portal.
- Log replies and portal names.
- Book the first 15-minute screen share.
Deliverable: 30 messages sent, reply log started.
Second 30 messages and first call
- Send 30 more DMs.
- Follow up once on non-replies from day 8.
- Run the booked screen share and capture the portal.
- Send a Stripe checkout link after the call.
Deliverable: 60 total DMs sent, checkout links out.
Collect the first payment
- Close the first Single Kit at $149.
- Record the buyer's task live on a screen share.
- Deliver kit plus runbook within 48 hours.
- Ask for one named referral.
Deliverable: First collected payment and delivered kit.
Inbound leads
- Post a short question asking which portal wastes people's day in three communities.
- Reply publicly with a demo clip.
- Collect 20 new portal names.
- Send 10 DMs from those threads.
Deliverable: 20 new leads and 10 DMs from community threads.
Reliability
- Rebuild any kit that failed first replay.
- Add label-similarity scoring to field matching.
- Ship extension v0.2.
- Update the runbook template.
Deliverable: v0.2 with stronger field matching.
Credibility on the page
- Write one anonymized before-and-after timing note per delivered kit.
- Add a short FAQ covering portal terms of service.
- Update the landing page with the replay demo.
- Add an explicit refund policy line.
Deliverable: Landing page with proof and refund policy.
Turn buyers into leads
- Email every buyer asking for one referral name.
- Offer $50 off their next kit for a paid referral.
- Send 10 DMs from new portal names.
- Review week-two conversion numbers.
Deliverable: Referral requests sent, pipeline reviewed.
Week 3 · Repeat & systematize · 7 days
Segment testing
- Send 40 DMs to new posters.
- Separate bookkeeping from freight messaging angles.
- Test the $399 Office Pack angle on multi-task offices.
- Log which angle earns replies.
Deliverable: 40 more DMs plus angle comparison data.
Fulfilment speed
- Deliver all paid kits within 24 hours.
- Template the three most common portals.
- Cut build time per kit under 45 minutes.
- Tighten runbook wording.
Deliverable: Delivery time under 45 minutes per kit.
Raise order value
- Offer the Office Pack to every Single Kit buyer.
- Record a second task for one buyer as an upsell.
- Send the Stripe upgrade link.
- Log upgrade conversion.
Deliverable: First Office Pack upgrade attempt live.
Sharpen the pitch
- Collect the top three objections from replies.
- Write one paragraph answering each.
- Add them to the DM follow-up.
- Re-message 15 cold leads with the new answer.
Deliverable: Objection script and 15 re-messages.
Show the artifact
- Record a 90-second replay on a real portal layout.
- Show the runbook page beside the replay.
- Post it in three communities.
- Attach it to the first DM message.
Deliverable: Demo v2 published and linked from outreach.
Kill or double down
- Count collected payments, refunds and delivered kits.
- Kill any channel with zero replies.
- Double down on the best-converting community.
- Set the day-21 target.
Deliverable: Written mid-point review with decisions.
Second-degree buyers
- Ask all buyers for a named referral again.
- Offer a free re-record for any portal change.
- Send 25 DMs to referral-adjacent offices.
- Update the CRM.
Deliverable: Referral-sourced conversations started.
Week 4 · Scale what works · 7 days
Capped marketing experiment
- Spend a small capped amount on one community sponsorship or promoted post.
- Track clicks through to Stripe checkout.
- Compare cost per checkout against organic.
- Cancel if no sale within 72 hours.
Deliverable: Ad spend test result, strictly capped.
Operational throughput
- Batch-record four kits for Office Pack buyers.
- Standardize the runbook cover page.
- Stamp kit version on every exported file.
- Ship extension v0.3 with bug fixes.
Deliverable: v0.3 shipped and a batch delivery run completed.
Improve the page
- Rewrite the hero to name the portal and the hours saved.
- Add a two-tier price comparison.
- Add a three-step how-it-works block.
- Test checkout link placement.
Deliverable: Revised landing page live.
Last cold wave
- Send 40 final DMs with a deadline line.
- Re-contact every warm lead who did not buy.
- Offer a same-week delivery guarantee.
- Log every reply.
Deliverable: 40 final DMs sent and logged.
Deliver everything paid
- Deliver all outstanding paid kits.
- Confirm every buyer received the runbook and key.
- Request a one-line testimonial from each buyer.
- Resolve any license issues.
Deliverable: All paid kits delivered and confirmed.
Protect collected revenue
- Replay-test every delivered kit once more.
- Send a short replay checklist to each buyer.
- Offer a free re-record if anything fails.
- Log any refund request.
Deliverable: Zero unresolved replay failures.
Social proof
- Publish collected testimonials with written permission.
- Add them to the landing page and the DM pitch.
- Update the demo video description.
- Refresh the community posts.
Deliverable: Testimonials live on the page and in outreach.
Days 29-30 · Consolidate · 2 days
Window-end revenue
- Send a final 24-hour offer to warm leads.
- Deliver anything paid before the window closes.
- Reconcile Stripe against TrustMRR.
- Confirm no chargebacks are pending.
Deliverable: Reconciled payment record.
Numbers and decision
- Log final collected revenue, refunds and fees.
- Write down the three best-performing message angles.
- Decide whether the next 30 days continue one-time or add a repeat purchase.
- Archive all kits and runbooks.
Deliverable: Final numbers and post-window decision note.
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 Single Kits at $149, all sourced from direct messages, zero paid marketing.
- Base: 10 Single Kits at $149, matching the concept target of 10 customers in 30 days.
- Upside: 22 kits with an 18 Single Kit / 4 Office Pack mix, blended ARPU $190.
- Payment processing assumed at Stripe 2.9% + $0.30 per transaction on collected revenue.
- Refunds modeled at zero in Conservative and Base; one $149 refund modeled in Upside.
- Chargebacks modeled at zero in all scenarios; Stripe Radar defaults stay on.
- Operating costs cover domain, Cloudflare Workers paid tier and email delivery; no runtime inference cost.
- LLM runbook drafting cost is under $0.02 per kit and folded into operating costs.
- Buyers install a Chrome extension without IT approval in the target office size.
- All figures are projections built from stated assumptions, not verified revenue.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $14
- Paid marketing
- $0
- Hackathon profit
- $433
- Operating costs
- $25
- Business profit
- $408
Base case
10 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $46
- Paid marketing
- $0
- Hackathon profit
- $1,444
- Operating costs
- $55
- Business profit
- $1,389
Optimistic
22 customers- Refunds
- $149
- Chargebacks
- $0
- Payment fees
- $130
- Paid marketing
- $150
- Hackathon profit
- $3,751
- Operating costs
- $140
- Business profit
- $3,611
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $1,490
- Payment fees (3.9%)
- $58
- Paid marketing
- $0
- Hackathon profit
- $1,432
- Business profit
- $1,377
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.
Main risks and validation experiments
Risk 1Portal terms of service restrict automated replay on carrier and government screens.
Per-step human confirm keeps a person in the loop; the runbook states the buyer's responsibility for portal terms.
Read the terms of three target portals before sending any DM and record which ones forbid replay.
If all three target portals forbid replay outright, narrow to portals that permit assisted entry.
Risk 2Label-based matching still breaks on dynamic or iframe-heavy portals.
Label-similarity scoring plus a manual override panel that saves the correction into the kit.
Record and replay one kit, wait seven days, replay again and count field failures.
More than half of kits fail first replay after v0.2 ships.
Risk 3Buyers expect a hosted service and reject a file-based kit.
Lead with the 48-hour delivery and the refund line; show the runbook next to the replay in the demo.
Split the first 30 DMs between the kit framing and a done-for-you framing and count replies.
Fewer than 6 replies from 60 messages by day 14.
Risk 4Cold direct-message reply rate is too low to reach 10 customers.
Community posting and buyer referrals run as a second and third channel from day 11.
Track replies per 30 messages and compare communities after day 14.
Zero screen shares booked by day 12.
Risk 5Refund requests when a kit fails on the buyer's machine.
Replay-test every kit before delivery and re-record free within 14 days if a portal changes.
Replay every delivered kit once more on day 27 and log failures.
Refund rate above 25% of delivered kits.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create the Chrome MV3 repo with content script, popup and service worker.
- Deploy a holding page to Cloudflare Pages.
Output: Repo scaffold and a live holding page.
Hours 3-5
- Open Stripe and create the $149 and $399 one-time prices.
- Connect the Stripe account to TrustMRR before any payment is taken.
Output: Two live checkout links on a TrustMRR-connected account.
Hours 6-9
- Implement click and keystroke capture in the content script.
- Persist draft sessions with field labels in IndexedDB.
Output: Recorder that saves a draft session.
Hours 10-12
- Collect 20 posters from r/Bookkeeping and r/FreightBrokers.
- Log the specific portal each one named.
Output: 20-name target list with portal notes.
Hours 13-16
- Define the versioned kit JSON schema.
- Export the first draft kit file.
Output: Kit schema plus one example kit file.
Full 30-day launch report
Read the full generated report
PortalProof Handoff Kit: 30-Day Launch Report
1. Product opportunity and positioning
Small bookkeeping, freight-brokerage and insurance offices run on portals that were never built to integrate: carrier booking screens, government filing forms, insurer claim pages. Staff re-type the same record into those screens several times a day. The cost hides inside payroll and nobody measures it. When the person who knows the click sequence leaves, the office loses the capability as well as the hours.
PortalProof Handoff Kit sells the handoff rather than the automation. The buyer is the owner or ops lead of a 5-50 person office. They already pay a person to do the re-typing, so the budget exists today and no procurement cycle stands in the way. The deliverable is a Chrome extension that records one portal task and exports two files: a signed JSON kit and a one-page printable runbook. Their staff replays the kit in the browser, confirming each field as it fills.
Against the realistic alternatives: a screen-recording SOP shows what happened but cannot be executed; a written checklist is re-interpreted differently by every new hire; an enterprise RPA seat is priced and implemented for companies far larger than this buyer. PortalProof's output is a runnable artifact the buyer tests in ten minutes on their own machine. Field matching by label and ARIA hints, with a selector fallback, keeps the kit usable when the portal restyles.
The wedge is deliberately narrow. JEV scores this concept 59.7/100 (band C, confidence 0.62). Speed to first revenue is the strongest dimension at 8.22; market demand (4.78) and monetization potential (4.59) are the weak ones. The plan is shaped by that shape: demand gets validated by direct-message replies rather than forecasts, delivery stays concierge for the first ten buyers, and the price is a one-time fee small enough to approve without a meeting. The monetization weakness is answered by an Office Pack upgrade and paid re-records when a portal changes, not by bolting on a subscription the buyer did not ask for.
2. Smallest sellable MVP
The MVP is one recorded task, exported and replayed. The extension captures clicks, keystrokes and field labels in the active tab; the field-intent tagger stores label text and ARIA hints instead of raw CSS selectors; the exporter writes a portable JSON kit plus a printable PDF runbook; the replay runner executes the kit with a confirm prompt per step; a license key, issued by Stripe webhook through a Cloudflare Worker, gates export and replay.
Not built: cloud dashboard, team accounts, scheduled or headless runs, a kit marketplace, LLM self-healing locators, support SLAs, onboarding calls. Recording is founder-assisted for the first ten buyers: the buyer shares their screen, the founder records, the kit ships within 48 hours.
3. Technical implementation plan
Chrome Manifest V3 extension in vanilla JavaScript, state in IndexedDB, no framework. The content script captures events; the background service worker owns export, license check and PDF generation. Cloudflare Workers plus KV validate license keys and kit versions. Stripe Checkout handles both one-time prices and a webhook issues the keys. jsPDF renders the runbook from the kit JSON. The landing page sits on Cloudflare Pages.
Build order: repo scaffold and Stripe prices; event capture; kit schema and intent tagger; replay runner; license gate and runbook; dogfood on three sandbox portals; ship v0.2 with label-similarity scoring after the first replay failures.
Hardest risk: field matching on portals that render labels dynamically or use iframes. Mitigation is a manual override panel where the buyer re-picks a field once and the choice is saved back into the kit. No model runs at replay time; a single LLM pass at export writes the runbook prose from captured step labels, costs under $0.02 per kit, and the kit still works if that step is skipped.
4. Pricing and monetization
Single Kit at $149 one-time: one recorded portal task, printable runbook, 30-day replay license. Office Pack at $399 one-time: up to four kits, a runbook set, 90-day license. Both are one-time charges on Stripe, no subscription inside the window.
The first-revenue offer is a flat $149 with delivery inside 48 hours and a refund if the kit does not replay cleanly. Expected first-order value is $149. Upsell path: Office Pack upgrade for buyers who name a second and third task during the recording call, then paid re-records when a portal changes. Roughly one in four buyers is expected to name multiple tasks, lifting blended ARPU toward $190.
5. First-customer acquisition
One channel: direct messages to people who publicly describe repetitive portal entry. Sources are r/Bookkeeping, r/FreightBrokers, small-business Facebook groups for bookkeepers and freight agents, Upwork data-entry job posts, and LinkedIn ops leads at 5-50 person agencies.
Sequence: build a 60-name list on day 7, send 30 messages on day 8 and 30 on day 9 with one follow-up, book a 15-minute screen share, send a Stripe link after the call, deliver within 48 hours, ask for one referral. Every message names the portal the poster mentioned.
Template in short: saw your post about re-typing [portal] records, I built an extension that records the task once and gives your staff a replayable kit plus a one-page runbook, $149 delivered in 48 hours, refund if it does not replay on your machine. Week-one goal: 60 messages sent, at least 6 replies, 2 screen shares booked.
6. 30-day execution roadmap
Days 1-5 build the MVP: extension scaffold and Stripe prices, recorder, kit schema, replay runner, license gate and runbook export. Day 5 is the MVP deadline.
Days 6-7 dogfood and list-building: three sandbox recordings, a 60-second demo, a 60-name target list.
Days 8-14 first revenue: 60 DMs, screen shares, the first $149 sale targeted for day 10, concierge delivery, v0.2 with label-similarity matching, proof assets and the first referral asks.
Days 15-21 second wave: 40 more DMs split by segment, Office Pack upgrades, objection scripts, demo v2, and a mid-point review that kills any channel with zero replies.
Days 22-28 scale and conversion: a capped paid test on one community sponsorship, batch delivery, a landing page rewrite, 40 final DMs, testimonial collection, and refund prevention by replay-testing every delivered kit.
Days 29-30 close: final 24-hour offer to warm leads, delivery of everything paid, Stripe-to-TrustMRR reconciliation, and a written decision on what continues after the window.
7. Revenue and profit scenarios
Projections only, derived from the stated assumptions. Conservative: 3 Single Kits, $447 gross, $14 processing, $25 operating. Base: 10 kits, $1,490 gross, $46 processing, $55 operating. Upside: 22 kits at blended $190 ARPU, $4,180 gross, one $149 refund, $130 processing, $150 paid marketing, $140 operating.
Hackathon profit, which is what the contest ranks, excludes hosting and delivery cost; business profit subtracts it. The base case therefore ranks at about $1,444 and nets about $1,389 after operating cost. No customers, revenue or traction exist today; these are hypotheses, not results.
8. Main risks and validation experiments
Portal terms of service: many carrier and government portals restrict automated replay. Mitigation is a per-step human confirm so a person is always in the loop, plus a runbook line naming the buyer's responsibility. Test: read the terms of three target portals before messaging.
Field matching breaks on dynamic portals. Mitigation is label-similarity plus a manual override saved into the kit. Test: record and replay one kit, wait a week, replay again. Kill criterion: more than half of kits fail first replay after v0.2.
Buyers want hosted software, not a file. Test: split the first 30 DMs between the kit framing and a done-for-you framing and count replies. Kill criterion: fewer than 6 replies from 60 messages by day 14.
Low reply rates from cold DMs. Mitigation is community posting and referrals as backup. Kill criterion: zero screen shares booked by day 12.
Refund requests after failed first replay. Mitigation is replay-testing every kit before delivery and a free re-record inside 14 days. Kill criterion: refund rate above 25% of delivered kits.
9. First 24-hour action plan
Hours 1-2: create the Chrome MV3 repo and deploy a holding page. Output: repo and live URL.
Hours 3-5: open Stripe, create the $149 and $399 one-time prices, connect the account to TrustMRR. Output: two live checkout links.
Hours 6-9: build event capture in the content script and persist drafts in IndexedDB. Output: a recorder saving a draft session.
Hours 10-12: collect the first 20 target names from r/Bookkeeping and r/FreightBrokers with the portal each person named. Output: a target list.
Hours 13-16: define the kit JSON schema and export a first draft kit. Output: schema plus an example kit file.
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 →Bridge Brief
Turns a founder's own LinkedIn connections export into a ranked warm-intro map against a specific target list, with a ready-to-send ask for every path.
Zéro Écart
A fixed-price catch-up service for French small businesses that are months behind on bookkeeping: upload a bank export plus a pile of receipts, and receive a finished, importable accounting journal, renamed receipts, and an itemised list of exactly what could not be matched.
CleanFeed Statement Converter
CleanFeed turns any bank or credit-card statement PDF into a validated, import-ready CSV for QuickBooks Online or Xero in under two minutes, and refuses to hand over the file until the debits and credits reconcile to the statement total.