Client Funds Recon Pack
A solo-founder web tool that turns an EMI/BaaS account statement plus a company's internal ledger export into a reason-coded, audit-ready month-end reconciliation pack in minutes.
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.
The finance lead (Head of Finance, Finance Ops Manager or Controller) at a 10-100 person European fintech, marketplace or SaaS that holds client money at an EMI or BaaS provider.
Operational simplicity 5.8/10
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 6 sales at $199 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.0/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
The finance lead (Head of Finance, Finance Ops Manager or Controller) at a 10-100 person European fintech, marketplace or SaaS that holds client money at an EMI or BaaS provider.
Why now
Month-end close is dated and unavoidable, and companies that went live with an embedded account in autumn hit their first or second full close inside the contest window.
Problem
The provider statement and the internal ledger never agree exactly, and two to five days per close are lost explaining every residual by hand in Excel.
Solution
The buyer uploads a CAMT.053, MT940 or CSV statement plus a mapped ledger CSV and receives an XLSX pack with Summary, Matched, Unmatched-with-reason-codes and Variance-by-currency sheets, a CSV export and a sign-off PDF.
1. Product opportunity and positioning
Embedded finance created a new month-end chore. A company that embeds a client-funds account through an EMI or BaaS provider ends up holding money it does not own, moving it across SEPA, and reconciling two systems that were never designed to agree. The provider nets its fees out of the movement, applies its own value dates, occasionally converts currency, and posts refunds and chargebacks in a different period than the ledger does. The finance lead then opens two files in Excel, sorts by amount, and hunts.
The work is repetitive but not automatable with the tools that buyer already owns. Generic bookkeeping software assumes a normal bank account: one feed, one fee line, clean references. A BaaS statement has dozens of reference shapes and mixed fee treatment. So the buyer rebuilds the same fragile spreadsheet every month, and cannot hand an auditor a defensible explanation for the residual.
The wedge is the artifact, not a platform. Recon Pack returns a dated deliverable: a workbook with a Summary, a Matched sheet, an Unmatched sheet where every line carries one of roughly twelve fixed reason codes plus a suggested journal line, a variance-by-currency view, a CSV export and a one-page sign-off. The buyer judges it in sixty seconds by opening the Unmatched sheet and asking 'is that the reason?' Either the codes match what they spent two days finding, or they do not.
Positioning is deliberately narrow: European companies of 10-100 staff that hold or move client money through a banking-as-a-service or e-money provider. Not accountants in general, not corporates with treasury teams, not anyone reconciling a plain bank account. That narrowness is what makes the pitch credible in one cold message and what keeps delivery cost near zero, because the file formats are bounded.
Why this buyer and not a bigger one: the finance lead at a 30-person fintech can approve $199 on a card without procurement, without a security review, and without giving anyone API access. There is no sponsor bank, no licence, no KYC obligation on the founder, because the customer uploads their own files and receives their own output. The product never touches money and never connects to a bank.
JEV scored this concept 65.7/100 (band B), strongest on speed to first revenue and weakest on operational simplicity and market demand. Read that honestly: the build is feasible for one person in five days, the first sale is reachable by direct outreach, but demand has to be proven message by message rather than assumed. The 30 days are therefore organised around outreach volume and a sample artifact, not around feature depth.
Smallest sellable MVP
Upload page for two files (provider statement + ledger CSV), a saved column mapper, a deterministic matcher with fixed reason codes, and an emailed XLSX/CSV/PDF pack gated by a Stripe-issued licence key.
Must-have features
- Intake for CAMT.053 XML, MT940 and CSV statements plus an arbitrary ledger CSV with a saveable column mapper
- Canonical record normalizer: id, value date, amount, currency, direction, counterparty, normalized reference, fee flag
- Four-pass deterministic matcher: exact, date/amount tolerance window, reference-normalized, many-to-one fee or charge split
- Twelve fixed reason codes with a suggested journal line per unmatched item
- XLSX pack: Summary, Matched, Unmatched-with-reasons, Variance-by-currency
- CSV export and one-page sign-off PDF
- Stripe Checkout plus webhook-issued licence key, emailed pack link, 24-hour file auto-delete
Explicitly out of scope
- No bank, EMI or BaaS API connection and no PSD2/Open Banking access
- No journal posting into Xero, QuickBooks or an ERP
- No KYC/AML screening, regulatory reporting or safeguarding calculation
- No PDF statement parsing in the first 30 days
- No user roles, permissions or SSO
- No human-prepared reports, consulting or support SLA
Demo flow (what the buyer sees)
- Buyer pays $199 on Stripe Checkout and receives a licence key by email
- Buyer opens the upload page, enters the key and drops the provider statement and ledger CSV
- Buyer maps ledger columns once; the mapping is saved for the next close
- Worker normalizes both files and runs the four matching passes
- Unmatched items are tagged with reason codes and suggested journal lines
- Pack is generated, stored for 24 hours, and the download link is emailed
Technical implementation plan
Stack
Architecture
A Next.js app handles checkout redirects, licence validation and the upload UI. Uploads go straight to R2 with a signed URL, never through the app server. The webhook writes a licence row, and a queue row triggers a background worker that streams the statement and ledger from R2, normalizes both into one canonical record shape, runs the matching passes in memory, and writes the XLSX, CSV and PDF back to R2 under a 24-hour lifecycle rule. Rule profiles (tolerances, reference mappings, fee accounts) live in Postgres keyed by licence and entity so the second run skips mapping.
Build steps
- Create the Next.js repo, deploy to Vercel, add Supabase schema for licences, jobs, entities and rule profiles
- Wire R2 signed uploads and the 24-hour lifecycle rule
- Write three parsers (CAMT.053, MT940, CSV) against synthetic fixtures into one canonical record
- Build the ledger CSV column mapper with a saved mapping per entity
- Implement the four matching passes and unit-test them on fixtures with known answers
- Add the reason-code taxonomy and the suggested journal line template per code
- Generate the XLSX pack with four sheets, plus CSV export and the PDF sign-off
- Wire Stripe Checkout products, the webhook and licence-key issuance
- Add Resend delivery email with the 24-hour download link
- Harden: file size caps, malformed-XML handling, per-run timeout, error email to the buyer
- Deploy, run a full paid path in live mode with a real card and refund it
AI components
- An optional small LLM call to propose a column mapping when a buyer's ledger headers are unrecognisable, shown as an editable suggestion, never auto-applied
- No LLM is used inside the matching logic or in the generated reason codes; those stay deterministic and testable
Pricing and monetization
Single Close
Entry offerFor Finance lead closing one month for one entity, first time using the tool
- One reconciliation run on one entity
- XLSX pack: Summary, Matched, Unmatched with reason codes and suggested journal lines
- Variance by currency
- CSV export and one-page sign-off PDF
Monthly Close
For Companies with a recurring monthly close who want saved rules
- Unlimited runs per month for one entity
- Saved tolerance and reference-mapping profiles
- Month-over-month history
- Same pack output
Multi-Entity / Firm
For Outsourced-finance and bookkeeping firms running closes for several embedded-finance clients
- Up to five client entities
- Per-client rule profiles
- Branded sign-off sheet
- Same pack output
Model: One-time $199 per close, with a $149 monthly tier for recurring closes and a $399 monthly multi-entity tier for outsourced-finance firms.
First revenue offer: $199 Single Close through a Stripe link sent in the first cold message, with a redacted synthetic sample pack attached and money back if the pack flags nothing the buyer had not already found.
Expected ACV: $199
Upsell path: Single Close converts to $149/month after the second close, and bookkeeping firms move to $399/month for up to five client entities once they have run one close on the tool.
First-customer acquisition
Cold LinkedIn and email outreach to Heads of Finance and Finance Ops at European companies that mention IBAN accounts, client funds or payouts, led with a redacted synthetic sample pack.
Where to find them
- Company sites and docs pages that name an EMI or BaaS provider
- Job ads for Finance Ops, Controller or Head of Finance at 10-100 person fintechs
- Marketplace and SaaS payout or wallet help-centre pages
- LinkedIn search for 'Head of Finance' filtered to European fintech and marketplace companies
- Outsourced-finance and bookkeeping firms whose client pages list fintech or payments clients
Exact outreach motions
- Day 0 email: one paragraph naming the reconciliation pain, the $199 offer and a link to the redacted sample pack
- Day 0 LinkedIn connection note with the same angle in under 300 characters
- Day 3 email with a 40-second Loom walking one unmatched line from statement to reason code
- Day 8 email with the December pre-close dry-run angle for companies not yet closed
- Parallel track: 20 bookkeeping firms pitched the $399 multi-entity tier so they run client closes on it
Message template
Hi {first_name} — you moved client money through {provider} this month, so your statement and your ledger disagree on fees, value dates and period-cut refunds. I built a tool that takes both files and returns a reason-coded reconciliation pack (Unmatched sheet with suggested journal lines, variance by currency, sign-off page). Here is a redacted sample on synthetic data: {link}. $199 for one close, paid by card, no bank credentials, files deleted after 24 hours, money back if the pack flags nothing you had not already found. Want to run November through it?30-day execution roadmap
Week 1 · Build & validate · 7 days
Ship an empty deployed app with storage
- Create Next.js repo and deploy to Vercel
- Add Supabase tables for licences, jobs, entities, profiles
- Wire R2 signed uploads and 24-hour lifecycle
Deliverable: Live URL with a working signed upload endpoint
Three statement formats into one canonical record
- Write CAMT.053 XML parser
- Write MT940 and CSV parsers
- Build ledger CSV column mapper with saved mapping
Deliverable: Fixtures from all three formats produce canonical rows
Four passes plus reason codes
- Implement exact, tolerance and reference-normalized passes
- Implement many-to-one fee and charge split
- Attach reason code and suggested journal line
Deliverable: Unit tests pass on fixtures with known answers
The artifact the buyer pays for
- Generate XLSX with four sheets
- Add CSV export and PDF sign-off sheet
- Add variance-by-currency aggregation
Deliverable: Downloadable pack built from fixtures
Money in, pack out, no humans
- Create Stripe products and webhook licence issuance
- Add Resend delivery email with expiring link
- Run one live $199 card payment and refund it
Deliverable: End-to-end paid run on production
The thing cold messages carry
- Build a redacted sample pack on synthetic data
- Publish landing page with that sample and a live Stripe link
- Start the 200-row outreach list
Deliverable: Public sample link plus live checkout
First 40 messages
- Finish 200 rows with verified emails
- Send 40 first-touch emails with sample link
- Send 15 LinkedIn connection notes
Deliverable: 40 sends logged in the tracker
Week 2 · Launch & first sale · 7 days
Reach and reply rate
- Send 40 more first-touch emails
- Pitch 10 bookkeeping firms on the $399 tier
- Log replies and objections in one sheet
Deliverable: 80 cumulative sends, objection list
Video and follow-ups
- Record 40-second Loom on one unmatched line
- Send day-3 follow-up to the day-7 cohort
- Answer every reply within two hours
Deliverable: Loom link plus follow-ups sent
Assisted delivery
- Handle inbound sample requests personally
- Walk one prospect through the upload on a call
- Take payment before processing any real file
Deliverable: First paid job queued
Rewrite what is not replying
- Rewrite subject lines on non-opened sends
- Send 40 new first touches
- Publish one LinkedIn post with the sample pack
Deliverable: Second message variant live
Convert and deliver
- Close the first paying customer
- Deliver the pack and review the Unmatched sheet with them
- Log every reason code they disagree with
Deliverable: First revenue collected and pack accepted
Fix the codes buyers dispute
- Tune reason-code wording from day-12 feedback
- Add one provider CSV preset
- Send 30 more first touches
Deliverable: Updated taxonomy shipped
December pre-close angle
- Send day-8 angle to all non-responders
- Send 30 new first touches
- Pitch monthly tier to the first buyer
Deliverable: 140 cumulative sends
Week 3 · Repeat & systematize · 7 days
Providers buyers actually use
- Add CSV presets for the two most-named providers
- Harden malformed-XML error path
- Ship clearer upload error copy
Deliverable: Preset library of three formats
Multi-entity pitch
- Send 10 bookkeeping firm pitches with sample
- Offer a free first client close
- Send 40 first touches
Deliverable: 10 firm conversations opened
Cut false unmatched lines
- Improve reference normalization on failing samples
- Add tolerance defaults per currency
- Re-run all delivered packs mentally against changes
Deliverable: Lower unmatched count on same inputs
Auditor-facing credibility
- Add branded sign-off sheet for firm tier
- Tighten variance-by-currency labels
- Add run metadata and timestamp to Summary
Deliverable: v1.1 pack template
Volume and firm follow-ups
- Send 50 first touches
- Follow up 10 firms
- Post one before/after unmatched count
Deliverable: 190 cumulative sends
Decide what to change
- Compute reply, sample and paid rates per message variant
- Kill the worst performing variant
- Double down on best performing list segment
Deliverable: Funnel table with a decision
Catch up and clean
- Clear delivery backlog
- Fix the top reported defect
- Confirm all collected payments settled in Stripe
Deliverable: Zero open jobs
Week 4 · Scale what works · 7 days
Convert one-timers
- Offer monthly tier to every Single Close buyer
- Set up saved profiles for repeat buyers
- Send 40 first touches
Deliverable: First monthly subscription started
Prove the second run is faster
- Test saved tolerances and mappings on a repeat entity
- Fix mapping persistence bugs
- Document the two-minute second run
Deliverable: Repeat-run flow verified
Land one multi-entity account
- Run a free close for one firm client
- Send the $399 tier link
- Send 40 first touches
Deliverable: Firm tier proposal sent
Organic proof
- Publish a short write-up of a common reason-code pattern
- Send 40 first touches
- Reply to every open thread
Deliverable: One public artifact plus sends
Zero disputes
- Review every delivered pack for code errors
- Add a fallback reason code for unclassifiable items
- Email buyers a one-line summary of their variance
Deliverable: No open buyer complaints
Pre-close dry run
- Package a December pre-close dry-run offer
- Send it to all non-converted repliers
- Send 40 first touches
Deliverable: Dry-run offer live
Price and message decision
- Recalculate collected revenue minus refunds and fees
- Decide whether to hold $199 or test $249
- Decide January scope
Deliverable: Written pricing decision
Days 29-30 · Consolidate · 2 days
Convert warm threads
- Call every warm prospect once
- Send 40 last first touches
- Chase any unpaid Stripe invoices
Deliverable: All warm threads closed or closed out
Lock what worked
- Reconcile Stripe payouts against the pack deliveries
- Write the post-mortem with the real conversion rate
- Freeze scope for January
Deliverable: Post-mortem and January plan
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: 200 verified leads, 2% paid conversion, four Single Close sales, no ads.
- Base: 200-300 leads with three touches, 5-7% paid conversion, fourteen sales at the $199 Single Close price.
- Upside: 25% of base revenue arrives through firms and repeat buyers, so the effective ARPU rises to $207 with monthly and multi-entity tiers mixed in.
- Upside includes $150 of paid marketing (one sponsored newsletter placement); all other scenarios use organic outreach only, so ad_spend is 0.
- Payment fees assumed at roughly 3.1-3.5% effective: Stripe standard 2.9% + $0.30 on $149-$199 tickets, plus a small share of non-EEA cards.
- Operating costs cover Vercel, Supabase, R2, Resend and about $2 of compute per delivered pack; they are excluded from hackathon profit but deducted from business profit.
- Refunds are modelled as the money-back promise firing on one pack in the base case and two in the upside; chargebacks are modelled only in the upside.
- All figures are projections built from stated assumptions. They are not verified revenue, not existing customers and not traction.
Conservative
4 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $28
- Paid marketing
- $0
- Hackathon profit
- $768
- Operating costs
- $40
- Business profit
- $728
Base case
14 customers- Refunds
- $199
- Chargebacks
- $0
- Payment fees
- $98
- Paid marketing
- $0
- Hackathon profit
- $2,489
- Operating costs
- $95
- Business profit
- $2,394
Optimistic
26 customers- Refunds
- $398
- Chargebacks
- $199
- Payment fees
- $188
- Paid marketing
- $150
- Hackathon profit
- $4,447
- Operating costs
- $120
- Business profit
- $4,327
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,582
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
All scenarios are projections derived from the stated assumptions. They are not verified revenue, customers, traction or profit.
Main risks and validation experiments
Risk 1Finance teams refuse to upload client-fund statements to an unknown solo founder.
State 24-hour auto-delete, no bank credentials and no API access in the first message and on the upload page; show the R2 lifecycle rule in plain language.
Send 40 first touches with the privacy paragraph and count how many ask for the sample pack versus how many raise the trust objection.
If more than 60% of replies stall on data-handling concerns after 80 sends, pivot to an on-premise or self-hosted run where files never leave the buyer's machine.
Risk 2Cold outreach conversion lands well under 5%, so fourteen sales would need a list far larger than 200 rows.
Track reply, sample and paid rates per message variant daily; rewrite subject lines and segment by provider named on the company site.
A/B two subject lines across 40 sends each in week 2 and compare reply rate before scaling volume.
If reply rate stays below 4% after 120 sends across two variants, switch the primary channel to bookkeeping firms running closes for fintech clients.
Risk 3Messy or undocumented provider CSV formats make correct pairing hard without per-provider work.
Start with CAMT.053, MT940 and generic CSV; add a per-provider preset only after a real buyer hits it; ship a fallback unclassified reason code.
Ask three prospects to send a header-only sample of their provider CSV and test the parser against all three.
If more than half of interested prospects use formats outside CAMT.053, MT940 and CSV, the v1 scope is wrong and PDF parsing must be added before scaling outreach.
Risk 4Timing: by mid-December most targets have already closed November and have no urgent trigger.
Lead with the December pre-close dry run in the second touch and target companies whose first month with the provider was recent.
Offer a $199 dry run on November data to 30 non-responders on day 8 and count requests.
If almost no one has an open close in the window, reposition to an audit-readiness pack sold against a year-end review deadline.
Risk 5Wrong suggested journal lines damage trust with an auditor-facing buyer and trigger refunds.
Label every suggestion as advisory, keep the matching deterministic, and add a per-code explanation column in the Unmatched sheet.
Have the first two buyers mark each reason code correct or incorrect and measure the agreement rate.
If buyers mark more than 25% of codes as wrong on the first pack, ship a manual reason-code override before taking more sales.
Hour-by-hour: the first 24 hours
Hours 1-3
- Create the Next.js repo and deploy an empty app to Vercel
- Create Supabase tables for licences, jobs and entities
- Create the R2 bucket with a 24-hour lifecycle rule
Output: Live URL plus database and storage ready
Hours 4-7
- Build synthetic fixtures: one CAMT.053, one MT940, one provider CSV and a matching ledger CSV with deliberate fee and timing breaks
- Write the CAMT.053 parser and the ledger column mapper
Output: Fixture set plus two parsers reading into one record shape
Hours 8-10
- Implement exact and tolerance matching passes
- Define the twelve reason codes and their journal line templates
- Write the test asserting the fixture's known unmatched set
Output: Matcher with a passing test on known answers
Hours 11-14
- Create the three Stripe products in test mode
- Write the webhook that issues a licence key and queues a job
- Draft the first-touch email and the sample pack outline
Output: Test-mode checkout issuing a licence key, plus the outreach copy
Full 30-day launch report
Read the full generated report
Client Funds Recon Pack — 30-Day Launch Plan
1. Product opportunity and positioning
Embedded finance created a new month-end chore. A company that holds client money at an EMI or BaaS provider runs two systems that were never designed to agree: the provider's statement and its own ledger. The provider nets its fees out of movements, applies its own value dates, converts currency occasionally, and posts refunds and chargebacks in a different period. The finance lead then spends two to five days per close sorting two files by amount and hunting.
The buyer already owns bookkeeping software, but that software assumes a normal bank account: one feed, clean references, one fee line. A BaaS statement has dozens of reference shapes and mixed fee treatment, so the buyer rebuilds the same fragile spreadsheet every month and cannot defend the residual to an auditor.
The wedge is the artifact, not a platform. The product returns a dated deliverable: a workbook with Summary, Matched, Unmatched-with-reason-codes and Variance-by-currency sheets, a CSV export and a one-page sign-off. The buyer judges it in sixty seconds by opening the Unmatched sheet and checking whether the codes match what took them two days to find.
Positioning stays deliberately narrow: European companies of 10-100 staff that hold or move client money through an EMI or BaaS provider. Not accountants in general, not corporate treasury. That narrowness makes the pitch credible in one cold message and keeps delivery cost near zero, because the input formats are bounded.
The buyer can approve $199 on a card without procurement, a security review or an integration project. No bank credentials, no PSD2 licence, no KYC obligation on the founder: the customer uploads their own files and receives their own output. The product never touches money and never connects to a bank.
JEV scored this concept 65.7/100 (band B), strongest on speed to first revenue, weakest on operational simplicity and market demand. Read that honestly: the build is feasible solo in five days and the first sale is reachable by direct outreach, but demand must be proven message by message. The 30 days therefore optimise for outreach volume and a convincing sample artifact, not feature depth.
2. Smallest sellable MVP
One page, two file inputs, one pack out. The buyer pays, gets a licence key, drops a CAMT.053, MT940 or CSV statement plus a ledger CSV, maps the ledger columns once, and receives an XLSX, CSV and PDF by email within minutes. Behind it sits a deterministic four-pass matcher and a fixed set of twelve reason codes. Nothing else ships in the first five days: no dashboards, no charts, no integrations, no PDF parsing.
3. Technical implementation plan
Next.js on Vercel for the app; Supabase Postgres for licences, jobs, entities and rule profiles; Cloudflare R2 for uploads with a 24-hour auto-delete; a background function or Inngest worker for parsing and matching; SheetJS and PDFKit for output; Stripe Checkout plus webhooks; Resend for delivery.
Build order is fixtures first. Synthetic statement and ledger files with deliberate fee, timing and FX breaks are created before any parser, so every later step has a known correct answer. Then parsers, then the mapper, then the four matching passes, then the pack generator, then Stripe and licence gating, then the live paid run. The hardest technical risk is reference normalization: if provider reference strings cannot collapse to a comparable key, pass three fails and the Unmatched sheet fills with noise. AI is used in exactly one optional place, proposing a column mapping for unrecognisable ledger headers, shown as an editable suggestion. Matching and reason codes stay deterministic.
4. Pricing and monetization
Single Close at $199 one-time is the entry point and the only thing sold in week one. Monthly Close at $149 per month captures recurring closes with saved rule profiles. Multi-Entity at $399 per month serves outsourced-finance firms running several client closes. Expected first-purchase value is $199. The upsell path is mechanical: deliver the pack, then offer the monthly tier before the next close, and pitch firms the multi-entity tier after one free client close.
5. First-customer acquisition
One channel: cold LinkedIn and email to Heads of Finance and Finance Ops at European companies whose site, docs or job ads mention IBAN accounts, client funds, payouts or an EMI provider. Build 200 verified rows in two days. Every first touch carries a redacted sample pack built on synthetic data, never a customer file. Three touches over eight days: the sample, a 40-second Loom walking one unmatched line to its reason code, and a December pre-close dry-run angle. A parallel track of twenty bookkeeping firms is pitched the $399 tier. Week-one goal: 200 rows, 120 first touches, at least 10 replies and 3 sample requests.
6. 30-day execution roadmap
Days 1-5 are build: skeleton, parsers, matcher, pack output, paid path. Day 6 produces the sample pack, landing page and live Stripe link. Days 7-14 are outreach volume and the first paid delivery, targeting first sale on day 12. Days 15-21 cover provider presets, the firm channel, accuracy fixes and a funnel review that kills the worst message variant. Days 22-28 convert one-time buyers to monthly, land one firm account, and set the December dry-run offer. Days 29-30 close warm threads, reconcile Stripe payouts against deliveries, and freeze scope.
7. Revenue and profit scenarios
All three scenarios are projections from stated assumptions, not verified revenue.
Conservative: 4 customers at $199, $796 gross, no refunds or chargebacks, $28 fees, no ads, $40 operating cost. Base: 14 customers at $199, $2,786 gross, one $199 refund, $98 fees, no ads, $95 operating cost. Upside: 26 customers at a $207 blended ARPU, $5,382 gross, $398 refunds, $199 chargebacks, $188 fees, $150 of paid marketing, $120 operating cost.
Hackathon profit deducts refunds, chargebacks, fees and paid marketing only. Business profit also deducts operating costs. At base that is roughly $2,489 hackathon profit and $2,394 business profit. The gap between conservative and base is almost entirely outreach volume and message quality, not product scope.
8. Main risks and validation experiments
The trust barrier is the first risk: finance teams may refuse to upload client-fund data. Test it by sending 40 messages that state the 24-hour auto-delete and no-credentials design, and count trust objections separately from price objections. Below a 4% reply rate after 120 sends across two variants, the channel is wrong, not the message; switch to the bookkeeping-firm track.
Format coverage is the second risk. Ask three prospects for header-only CSV samples and test the parser against them. If more than half use formats outside CAMT.053, MT940 and CSV, v1 scope is wrong. The third risk is code accuracy: have the first two buyers mark each reason code correct or incorrect, and ship a manual override if more than 25% are wrong. Timing is the fourth: many targets will already have closed November, so the December dry-run offer must carry the second touch.
9. First 24-hour action plan
Hours 1-3: repo, Vercel deploy, Supabase schema, R2 bucket with lifecycle rule. Hours 4-7: synthetic fixtures with deliberate breaks, CAMT.053 parser and ledger mapper. Hours 8-10: exact and tolerance passes, the twelve reason codes, and a test asserting the fixture's known unmatched set. Hours 11-14: Stripe test products, webhook issuing a licence key, first-touch email and sample-pack outline. By hour 14 there is a deployed app, a passing matcher test and the outreach copy ready to send on day 7.
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 →Chase Ladder
Turns a freelancer or small agency's overdue invoice list into a dated, escalating chase schedule with ready-to-send email drafts and a calendar file they can run themselves.
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.
UsageGate Kit
UsageGate Kit turns an OpenAPI spec and Stripe account into a deployable Cloudflare Worker that issues API keys, enforces monthly quotas, blocks overages, and sends metered usage to Stripe.