SwitchPack
SwitchPack turns a small business's mobile invoice into a ready-to-send cancellation and porting pack in under 2 minutes, so they can switch operators without paperwork headaches.
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 office manager of a French SME with 5–50 mobile lines who has already decided to leave their operator but is stuck on the cancellation and porting paperwork.
Market demand 3.5/10
Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 11; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.3/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 office manager of a French SME with 5–50 mobile lines who has already decided to leave their operator but is stuck on the cancellation and porting paperwork.
Why now
Switching is a decision already made; the only remaining blocker is paperwork, and OCR plus structured extraction can now turn an arbitrary invoice format into a filled template without any supplier integration.
Problem
Terminating a business mobile contract and porting numbers requires a specific letter, a porting mandate and correct timing; mistakes cause number loss, service gaps or extra fees, so the switch stalls for weeks.
Solution
The buyer uploads a PDF or photo of the invoice, reviews auto-extracted fields (operator, contract ID, end date, line numbers), and downloads a French PDF pack: termination letter, porting authorization and a dated switching timeline.
1. Product opportunity and positioning
SwitchPack is a paperwork product, not a comparison engine. The buyer is not shopping — they have already decided to leave their mobile operator. What stops them is a specific, boring, high-anxiety task: writing a termination letter that the incumbent will actually accept, filling a porting mandate with the right line numbers (RIO), and sequencing both so numbers do not go dark mid-week.
The wedge is deliberately narrow. Mobile only. French only. 5–50 lines. The output is a named artefact — a PDF switch pack — that the buyer forwards to their operator the same day. That specificity is the answer to the weakest JEV dimension, competitive defensibility (4.76): a generic AI assistant can draft a letter, but it will not extract a RIO list from a scanned invoice, keep the contract reference, and hand back a porting mandate with a deadline calendar attached.
The trigger event is what makes this sellable inside 30 days. The buyer is not a cold prospect waiting to be educated about savings; they are a business owner who has an outstanding quote from a new operator and a renewal date approaching. Willingness to pay for a $99 pack is anchored against the alternative: a broker who wants the commission, an internal hour of admin, or the cost of a botched port (lost numbers, duplicated billing).
JEV scored the concept at 55.5/100, band C, with high confidence. The profile is lopsided in a useful way: speed to first revenue 8.34 and solo build feasibility 7.59 are strong, while market demand 3.51 and monetization 4.19 are the constraints. The plan therefore optimises for the two things the score rewards — a live product on day 5 and a channel where the founder can talk to the buyer directly — and compensates for the two it penalises. Demand is de-risked by refusing to build anything until a sample pack has been shown to real SME owners in French groups and at least one pre-sale or explicit yes has been collected. Monetization is de-risked by pricing to a time-and-error outcome ($99 versus an hour of admin and a botched-port risk) and by opening a repeat/recurring path through telecom brokers on the $199 monthly tier.
Positioning line to repeat everywhere: "Your invoice in, your cancellation and porting pack out, in two minutes." No savings claims, no commission, no supplier deals — that keeps the product outside the regulated-advice question the JEV flagged as a risk, and keeps operating cost near zero.
Smallest sellable MVP
A single-page web app where a French SME uploads one mobile invoice, sees extracted fields it can correct, pays $99 by Stripe, and downloads a three-part French PDF pack.
Must-have features
- Drag-and-drop upload for PDF, JPG and PNG invoices
- Managed OCR (Google Cloud Vision) converting the file to text
- Structured extraction of operator name, contract ID, end date, line count and RIO numbers into editable fields
- Human review screen so the founder or buyer can correct any extracted field before generation
- Termination letter template in French, pre-filled with contract details
- Porting authorization mandate template in French with a line table
- Dated switching timeline PDF with the key deadlines counted from the contract end date
- Stripe Checkout one-time payment gating the download link
- Supabase storage of the uploaded file and generated pack with a signed download URL
Explicitly out of scope
- No tariff comparison or supplier database
- No automated submission to operators
- No energy, insurance or banking contracts
- No team accounts, roles or collaboration
- No subscription billing for SMEs in v1
- No mobile app — responsive web only
- No legal advice or compliance guarantee wording
Demo flow (what the buyer sees)
- Buyer lands on the French landing page and clicks "Créer mon pack".
- Buyer uploads the latest mobile invoice as PDF or photo.
- OCR runs, the extraction model returns a JSON field set in under 20 seconds.
- Buyer sees the extracted operator, contract reference, end date and line list and edits anything wrong.
- Buyer pays $99 through Stripe Checkout.
- A PDF pack is generated and the download link appears immediately, plus an email copy.
- Buyer sends the termination letter and porting mandate; the timeline tells them when to post which one.
Technical implementation plan
Stack
Architecture
Stateless Next.js app on Vercel. An upload hits a serverless route that pushes the file to Supabase Storage and creates a job row. A second route calls Cloud Vision for text, then the extraction model with a strict JSON schema to return operator, contract reference, end date and RIO lines. The review screen edits that JSON in the browser. On Stripe webhook confirmation the job is marked paid, PDFKit renders the three documents from French templates plus the edited JSON, the PDF is stored in Supabase Storage and a signed URL is emailed. No queue, no worker, no server to maintain.
Build steps
- Create the Next.js repo, deploy a hello-world to Vercel, create the Supabase project and jobs table.
- Build the upload route with size and MIME validation, storing files in a private bucket.
- Wire Cloud Vision OCR and log raw text to the job row for debugging.
- Define the extraction JSON schema and prompt; return validated fields, never free text.
- Build the review screen: editable fields, one row per line/RIO, visible confidence flags.
- Write the three French templates as typed data structures with placeholder tokens.
- Render the pack with PDFKit, store it, and expose a signed download URL.
- Add Stripe Checkout with the price fixed server-side, plus a webhook that flips the job to paid.
- Add Resend email delivery of the pack and a fallback download page by email lookup.
- Ship to production, then run the whole flow on 10 real invoices and fix the extraction prompt.
AI components
- Google Cloud Vision OCR for text from PDF and photo invoices
- LLM structured extraction from OCR text into operator, contract reference, end date, line list and RIO numbers
- Optional LLM pass that rewrites the operator address block into the correct French formal salutation format
Pricing and monetization
Single Switch Pack
Entry offerFor SME switching one mobile contract
- French termination letter
- Porting authorization mandate
- Dated switching timeline PDF
Multi-Service Pack
For SME switching mobile plus a second contract
- Two generated switch packs
- Priority email support
- Free regeneration if the operator rejects the letter
Agency/Broker Monthly
For Telecom brokers and agents handling several client switches
- Unlimited switch packs
- White-label header on the PDF
- Priority email support
Model: One-time $99 per switch pack, with a $199 two-service pack and a $199/month unlimited tier for telecom brokers and agents.
First revenue offer: "Send me your mobile invoice, I'll send back your complete résiliation + portage pack free as a sample; if it's usable, the next one is $99 — launch price for the first 20 businesses."
Expected ACV: $99
Upsell path: Single pack buyers with a second contract upgrade to the $199 two-pack; brokers who order a second client pack in the same month move to the $199/month unlimited tier.
First-customer acquisition
Direct posting and DM outreach in French entrepreneur Facebook groups and LinkedIn, using a redacted before/after switch pack as the proof asset.
Where to find them
- French SME owner Facebook groups (entrepreneur and dirigeants PME groups, 5 to start)
- LinkedIn: owners and office managers of French companies with 5–50 employees in services, BTP, transport and retail
- LinkedIn: French telecom brokers and agents who resell mobile fleets
- Local business networks: CCI-affiliated groups, franchise owner groups
- Existing contacts of the founder: any SME owner who has mentioned changing operators
Exact outreach motions
- Post a 60-second screen recording: invoice uploaded, PDF pack downloaded, no narration needed but French captions added.
- Post a redacted sample pack as a 3-page image carousel with the caption "voici ce que votre opérateur attend".
- Comment helpfully on every thread mentioning résiliation, portage or changement d'opérateur before posting anything promotional.
- DM each person who reacts or comments within 2 hours with a personalised offer to build their pack free.
- Follow up at 48 hours with the sample pack attached and one line asking which field would need to change to make it usable.
- DM 15 French telecom brokers per week pitching the $199 unlimited tier with a sample white-labelled pack.
Message template
Bonjour [Prénom], j'ai vu votre message sur [groupe]. Je construis un outil qui transforme votre dernière facture mobile en pack de résiliation prêt à envoyer : lettre de résiliation, mandat de portage avec vos numéros, et un calendrier des dates. Je vous le fais gratuitement pour votre contrat si ça vous intéresse — vous me dites juste si c'est utilisable. Répondez OUI et je vous envoie le lien d'upload.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Repo, deploy pipeline, data model
- Create the Next.js repo and deploy a hello-world page to Vercel.
- Create the Supabase project with a jobs table and a private storage bucket.
- Create the Stripe account, connect TrustMRR, and confirm payouts are enabled before any sale.
Deliverable: Live URL and an empty jobs table.
File intake and session tracking
- Build the upload route with PDF/JPG/PNG validation and a 10 MB cap.
- Store files in the private bucket and create a job row with a client-side session id.
- Add a status page that polls the job row.
Deliverable: Working upload that returns a job id.
OCR plus structured JSON
- Wire Google Cloud Vision and log raw OCR text per job.
- Define an extraction JSON schema: operator, contract ref, end date, lines, RIO numbers.
- Run 5 of your own invoices through and record failure modes.
Deliverable: Extraction returning validated JSON for a real invoice.
French templates and PDF rendering
- Write the termination letter template with the correct French formal register.
- Write the porting mandate with a line/RIO table and signature block.
- Write the dated timeline with deadlines computed from the contract end date.
- Render all three into one PDF with PDFKit.
Deliverable: A generated three-part PDF from static test data.
Review screen, payment, deploy
- Build the editable review screen with low-confidence fields flagged.
- Fix the Stripe price server-side at $99 and add the webhook that marks a job paid.
- Email the pack with Resend and add an email-based re-download page.
- Deploy to production and run one full end-to-end purchase with a real card and refund it.
Deliverable: Live product that takes $99 and returns a PDF pack.
Fix parsing on real formats
- Run 10 anonymised or own invoices through the full flow.
- Fix the three most common extraction failures in the prompt.
- Add a founder-side correction form so any job can be fixed in 3 minutes.
Deliverable: 8 of 10 invoices producing a usable pack with no correction.
Sample packs and demo video
- Generate 3 redacted sample packs across three different operators.
- Record a 60-second screen capture of invoice to PDF.
- Write the French landing copy: outcome, price, no-commission statement, disclaimer.
Deliverable: 3 sample PDFs, 1 video, landing copy ready.
Week 2 · Launch & first sale · 7 days
Landing page and pricing
- Ship the landing page with the video, sample pack preview and $99 checkout.
- Add FAQ answering: is this legal advice, is my invoice kept, what if the operator rejects it.
- Add the 20-business launch price counter.
Deliverable: Public landing page with working checkout.
Join groups, contribute only
- Join 5 French entrepreneur and SME Facebook groups.
- Answer 10 existing threads about résiliation or portage with useful, non-promotional detail.
- Identify 30 named SME owners from LinkedIn with 5–50 employees.
Deliverable: Group access and a 30-name prospect list.
Publish the demo in 2 groups
- Publish the demo video with French captions in 2 groups.
- Post the redacted sample pack carousel on LinkedIn.
- Reply to every comment within 2 hours.
Deliverable: 2 live posts and comment replies logged.
40 personalised DMs
- Send 40 DMs using the template with the prospect's context inserted.
- Offer a free pack to the 10 warmest replies.
- Track every send and reply in a simple sheet.
Deliverable: 40 DMs sent, reply rate recorded.
Deliver free packs fast
- Deliver every promised free pack within 4 hours of receiving the invoice.
- Ask each recipient one question: what would you pay to have this next time.
- Fix any extraction failure discovered during delivery.
Deliverable: 3+ free packs delivered, price feedback captured.
Convert free users to paid
- Send each free-pack recipient a $99 link with a one-line recap of what they got.
- Follow up at 48 hours with a reminder only.
- Log every objection verbatim.
Deliverable: Paid conversion attempts logged with objections.
Halfway checkpoint
- Count revenue, paid customers, free packs and reply rates.
- Rewrite the landing headline if reply rate is under 10%.
- Decide whether to push harder on SMEs or switch emphasis to brokers.
Deliverable: Written checkpoint with one decision.
Week 3 · Repeat & systematize · 6 days
Remove the upload objection
- Publish a plain French data page: files deleted after 30 days, no reuse, no resale.
- Add a "we regenerate free if the operator rejects it" guarantee to the offer.
- Add a sample pack preview directly on the landing page.
Deliverable: Trust page live and guarantee visible at checkout.
20 DMs per day
- Send 20 DMs with a sector-specific first line.
- Post the demo video in 2 new groups.
- Reply to all inbound within 2 hours.
Deliverable: 20 DMs and 2 group posts.
Repeat with variation
- Send 20 DMs using the strongest performing angle.
- Test a second message angle focused on the port date risk.
- Log which angle gets more replies.
Deliverable: A/B result on two DM angles.
Own the search question
- Publish a French LinkedIn article on how to terminate a business mobile contract correctly.
- Turn it into a 2-post Facebook thread.
- Add a lead capture for a free sample pack.
Deliverable: 1 article and 1 thread published.
Open the recurring tier
- Build a white-labelled sample pack with a broker's logo substituted.
- Send 15 broker DMs pitching the $199 monthly unlimited tier.
- Offer the first month at $99 for one broker only.
Deliverable: 15 broker conversations started.
Second touch
- Follow up with all broker conversations with the white-label sample.
- Add a broker billing option to Stripe for the monthly price.
- Book any calls offered.
Deliverable: Monthly tier purchasable end to end.
Week 4 · Scale what works · 7 days
Week three checkpoint
- Recompute revenue and compare against the base projection.
- Cut the channel with the worst reply-to-sale rate.
- Double the volume on the best channel.
Deliverable: Channel decision written down.
Turn buyers into a channel
- Email every paid buyer a referral code worth $20 off the second pack.
- Ask each paid buyer for one sentence of testimonial.
- Publish any testimonial received with permission.
Deliverable: Referral code live and testimonials collected.
Second contract
- Email every single-pack buyer the $199 two-pack offer.
- Add a one-click second upload from the confirmation email.
- Measure how many attach a second pack.
Deliverable: Upsell email sent and tracked.
Fresh groups
- Join 3 new French business groups.
- Post the demo video in each.
- Answer 10 threads before promoting anything.
Deliverable: 3 new groups and posts.
20 DMs per day
- Send 20 DMs to the highest-converting segment.
- Follow up with all cold leads from days 16–17.
- Reply to all inbound within 2 hours.
Deliverable: 20 DMs and 20 follow-ups sent.
One small ad test
- Run a $60 LinkedIn sponsored post targeted at French SME owners.
- Track clicks and checkout starts only.
- Kill it at 48 hours if cost per checkout start exceeds $15.
Deliverable: Ad test result with a keep or kill decision.
Delivery quality
- Audit all generated packs for template errors.
- Add bounds checks so a missing contract end date never renders a broken timeline.
- Document the 3-minute manual correction procedure.
Deliverable: Template audit completed, bug list closed.
Days 29-30 · Consolidate · 3 days
Last selling day
- Send the strongest DM and email angle to every unconverted lead.
- Post the demo one final time in the two best groups.
- Close any pending broker conversation on the monthly tier.
Deliverable: All pending opportunities contacted.
Verify money and fees
- Reconcile Stripe payouts against TrustMRR records.
- Confirm every pack delivered has a corresponding settled payment.
- Record refunds and chargebacks if any.
Deliverable: Reconciled revenue statement.
Write the record
- Write the 30-day retro: revenue, conversion by channel, top objections.
- Decide the single change for the next 30 days.
- Ship a changelog entry so the product is visibly alive.
Deliverable: Retro document and the next-30-day decision.
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 paying SMEs at $99 one-time, reachable inside the 30 days.
- Base: 10 paying customers, average order value $99 one-time.
- Upside: 22 paying customers with a mixed basket (mostly $99 packs, a few $199 two-packs and one $199 monthly broker), giving a blended ARPU of $118.
- Payment fees assumed at 5% blended (Stripe 2.9% + $0.30 on EU cards plus cross-border surcharge), applied to gross revenue.
- Ad spend is $0 in conservative and base because outreach is organic; upside includes $120 on one small LinkedIn sponsored test and one boosted group post.
- Operating costs cover Vercel, domain amortisation, Vision OCR pages and LLM extraction calls to serve the stated customers (inference cost to deliver, not rankable fees).
- No refunds or chargebacks assumed in conservative and base; upside assumes one refund on a $99 pack.
- All figures are projections built from stated assumptions, not verified revenue.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $15
- Paid marketing
- $0
- Hackathon profit
- $282
- Operating costs
- $30
- Business profit
- $252
Base case
10 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $49
- Paid marketing
- $0
- Hackathon profit
- $941
- Operating costs
- $60
- Business profit
- $881
Optimistic
22 customers- Refunds
- $99
- Chargebacks
- $0
- Payment fees
- $130
- Paid marketing
- $120
- Hackathon profit
- $2,247
- Operating costs
- $120
- Business profit
- $2,127
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $990
- Payment fees (3.9%)
- $39
- Paid marketing
- $0
- Hackathon profit
- $951
- Business profit
- $891
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 derived from stated assumptions, not verified revenue. No customers, traction or partnerships exist today.
Main risks and validation experiments
Risk 1SME owners refuse to upload a real invoice to an unknown solo founder, so the funnel dies at upload.
Add a plain French data page, delete files after 30 days, and let buyers send the invoice by email if they prefer.
Ask 10 warm group members a single question: would you upload your facture mobile here, or email it. Count the split before building anything else.
If fewer than 3 of 10 say they would upload or email a real invoice, the trust barrier is too high and the concept needs a lower-friction input.
Risk 2Extraction accuracy fails on varied invoice layouts, meaning every pack needs manual correction and delivery time collapses.
Always show extracted fields for a human check, flag low-confidence fields in red, and keep a 3-minute founder correction form.
Run 10 real invoices through the pipeline and count how many produce a usable pack with no correction.
If fewer than 6 of 10 invoices parse cleanly after two prompt iterations, stop and restrict the product to two named operators as a stated limitation.
Risk 3Generated termination letters are rejected by operators as non-compliant, so buyers demand refunds and the guarantee costs money.
Base every template on the operator's own published résiliation process, include the contract reference and RIO, and regenerate free on rejection.
Send one anonymised sample letter and mandate to two operators' customer service by email and ask whether the documents are acceptable.
If both operators say the letter would be rejected in its current form, redesign the template before selling another pack.
Risk 4Market demand is genuinely thin — this is a rare event for any single SME, so $99 one-time cannot sustain volume.
Open the $199 monthly broker tier early (day 19) so revenue can repeat without new SME acquisition.
Pitch 15 telecom brokers the white-label monthly tier in week three and count how many request a sample.
If revenue is below the conservative 3-customer scenario by day 21 and no broker has requested a sample, stop SME outreach and pivot all effort to brokers for the remaining days.
Risk 5Facebook groups ban the promotional posts, removing the only channel.
Lead with thread answers and DMs, never a link in the first post, and mirror everything on LinkedIn.
Post in 2 groups on day 10 and record whether the post survives 24 hours and how many comments it draws.
If both posts are removed within 24 hours, move the primary channel entirely to LinkedIn DM outreach.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create the Next.js repo, deploy hello-world to Vercel, create Supabase project and jobs table.
- Create Stripe account and start the TrustMRR connection so no sale can happen off-platform.
Output: Live URL, empty database, payment account in progress.
Hours 3-4
- Post in 3 French entrepreneur communities asking what blocks a mobile operator switch, without mentioning the product.
- DM 5 SME owners you already know and ask for their latest facture mobile to build a free sample.
Output: Reply thread started and at least 1 real invoice committed.
Hours 5-6
- Wire the upload route and Cloud Vision OCR.
- Run the one committed invoice through and print the raw OCR text.
Output: Raw OCR text from a real French mobile invoice.
Hours 7-8
- Draft the extraction JSON schema and the three French templates as plain text.
- Write the landing page headline, price and disclaimer.
Output: Schema file, three template drafts, landing copy.
Hours 9-10
- Send the 40-name prospect list first pass on LinkedIn with the message template.
- Log every send in the tracking sheet.
Output: First 15 DMs sent and a tracked prospect list.
Full 30-day launch report
Read the full generated report
SwitchPack — 30-Day Launch Report
JEV scored this concept 55.5/100 (band C, confidence 0.76). The profile is uneven in a useful way: speed to first revenue (8.34) and solo build feasibility (7.59) are strong; market demand (3.51) and monetization potential (4.19) are the binding constraints. Everything below is engineered around that shape — get to a sellable artefact fast, talk to buyers before building the second version, and open a repeating revenue path because a one-time $99 charge will not carry the month alone.
1. Product opportunity and positioning
SwitchPack sells the last mile of a decision that has already been made. A French SME owner with 5–50 lines has a quote from a new operator and a renewal date approaching. What stops them is not price comparison — it is a termination letter the incumbent will accept, a porting mandate with the correct line and RIO references, and the sequencing that prevents the numbers going dark. That is a two-hour admin task with a real downside if it is done wrong.
The product is deliberately narrow: mobile contracts only, French only, one named output. That narrowness is the direct answer to the weakest scored dimension, competitive defensibility (4.76). A general assistant can write a letter; it will not lift a RIO list off a scanned invoice, preserve the contract reference, and return a mandate plus a dated calendar. The constrained input (one invoice) and the constrained output (a three-document pack) are the moat available to a solo founder in 30 days.
Positioning must be repeated identically everywhere: invoice in, cancellation and porting pack out, in two minutes. No savings claims, no commission, no operator partnerships, no legal advice. That keeps the product outside the regulated-advice question and keeps delivery cost at the level of an OCR page and a model call.
2. Smallest sellable MVP
One page. Upload one invoice, see six extracted fields, correct anything wrong, pay $99, download a PDF containing a termination letter, a porting mandate and a dated timeline. Nothing else.
The human review step is not optional and is not a weakness. It is what makes an OCR product safe to sell before accuracy is perfect, and it converts a potential refund into a correction. The founder can also correct any job manually in three minutes, which is a legitimate way to serve the first twenty customers without a support team.
Explicitly excluded: comparisons, tariffs, supplier integrations, automated submission, energy or insurance contracts, accounts, mobile apps, and any compliance guarantee.
3. Technical implementation plan
Next.js on Vercel, Supabase for jobs and private file storage, Google Cloud Vision for OCR, a structured-output extraction call that returns a fixed JSON schema, PDFKit rendering three French templates, Stripe Checkout with a server-side fixed price, Resend for delivery. No queue, no worker, no server to patch.
The build order matters: upload and OCR first so real invoices can be tested on day three, templates on day four, review screen and payment on day five. Payment lands last because a working generator with a manual invoice is already enough to deliver a free sample pack in week one.
Hardest technical risk is extraction on poor scans. A wrong RIO produces a failed port, which is the one error the buyer will not forgive. Mitigation: never ship a pack without a human-confirmed line list, and colour-flag low-confidence fields rather than silently guessing.
4. Pricing and monetization
$99 one-time for a single switch pack, $199 for a two-service pack, $199 per month unlimited and white-labelled for telecom brokers and agents. The $99 is anchored against an hour of admin plus the cost of a botched port, not against free comparison sites.
This is launch pricing: $99 instead of $149 for the first twenty businesses. The broker tier exists specifically because the scored monetization weakness is real — a rare-event one-time purchase does not compound. Brokers switch clients repeatedly, so they convert the same product into recurring revenue with no extra acquisition cost.
5. First-customer acquisition
One channel: direct posting and DM outreach in French entrepreneur Facebook groups and LinkedIn, with a redacted before/after pack as the proof asset. No ads until day 26 at the earliest.
Sequence: contribute in threads before promoting, publish the demo video, offer a free pack to anyone who reacts, deliver it within four hours, then ask for $99 on the next one. Brokers get the white-labelled sample in week three. Week-one goal: five groups joined, two posts, forty personalised DMs, three free packs delivered, one paid pack.
6. 30-day execution roadmap
Days 1–5 build: repo and Stripe on day one, upload on day two, OCR and extraction on day three, French templates and PDF rendering on day four, review screen plus checkout plus deploy on day five. MVP is live on day five.
Days 6–14 sell and fix: parsing accuracy on real invoices, three redacted sample packs, landing page, group entry, first posts, forty DMs, free pack delivery, conversion attempt, and a written checkpoint on day fourteen.
Days 15–21 remove objections and open brokers: data and guarantee pages, DM volume at twenty per day, one French article, broker outreach and the monthly billing option, second checkpoint on day twenty-one.
Days 22–30 compound and close: referral codes, two-pack upsell, three new groups, a $60 ad test with a hard kill rule, template audit, final outreach push, Stripe-to-TrustMRR reconciliation on day twenty-nine, retro on day thirty.
First sale is targeted for day eleven — six days after the MVP exists, which is the realistic minimum for a cold first post plus DM follow-up.
7. Revenue and profit scenarios
All figures are projections from stated assumptions, not verified revenue.
Conservative: 3 customers at $99, $297 gross, $15 fees, no ad spend, $30 operating cost. Base: 10 customers at $99, $990 gross, $49 fees, no ad spend, $60 operating cost. Upside: 22 customers at a blended $118 ARPU, $2,596 gross, $99 refunds, $130 fees, $120 ad spend, $120 operating cost.
The gap between conservative and base is entirely a function of DM volume and reply rate, both of which are controllable inside the window. Hackathon profit ignores hosting and inference; business profit does not. Neither is large, which is exactly why the broker tier is opened in week three rather than month three.
8. Risks and validation experiments
The five real risks are covered in the structured section with a cheap test and a kill rule each: upload trust, parsing accuracy, letter rejection by operators, thin one-time demand, and group moderation. The two that can end the month are demand and parsing — both are tested before day twelve, so the founder still has eighteen days to change course.
9. First 24 hours
Ten hours in five blocks: ship the skeleton and start the payment connection, gather demand signal in communities, get one real invoice through OCR, draft the schema and templates, and send the first fifteen DMs. The output of day one is a live URL, one real OCR result and a warm pipeline — enough that day two is building, not deciding.
Every scenario above is a hypothesis. No customers, revenue or partnerships exist today; the plan exists to find out fast.
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 →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.
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.
LockDay Expiration Radar
A tool that turns a mortgage loan officer's messy pipeline export into a ranked rate-lock expiration radar and a Monday risk digest, so no loan silently expires.