PitchDeck Rewind
Turns a lost sales deck into a shareable 'what you missed' recap microsite for agency owners, sent as the follow-up that reopens stalled deals.
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.
Boutique agency and consultancy owners (2-20 staff) who have sent a $10k+ deck that has gone silent for 7 or more days, reachable directly through LinkedIn and founder communities.
Market demand 4.4/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 4 days; the plan targets a first sale on day 9; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.9/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
15 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Boutique agency and consultancy owners (2-20 staff) who have sent a $10k+ deck that has gone silent for 7 or more days, reachable directly through LinkedIn and founder communities.
Why now
AI text extraction is cheap and accurate enough on business decks, and founders are already sitting on dozens of sent decks, so the first output takes minutes rather than a build.
Problem
After a deck is sent, the deal goes quiet and the owner has no lightweight, non-pushy way to re-engage; re-sending the PDF reads as nagging and rebuilding the pitch costs an hour.
Solution
Upload the sent PDF or Docx, the tool extracts offer, price and next steps into structured fields, renders a one-page recap on a custom slug, emails or Slacks the owner on every view, and shows which link was reopened.
1. Product opportunity and positioning
Every agency owner has a folder of decks that were sent and never answered. The deal is not lost; it is silent. The owner knows the buyer is busy, knows that one more email risks looking needy, and knows that rewriting the pitch costs an hour they will not spend on a maybe.
PitchDeck Rewind sells the follow-up, not the pitch. The input is the deck that already went out. The output is a single page: what we offered, what it costs, what happens next, one button. The buyer skims it in sixty seconds. The seller gets a notification the moment it is opened, plus the number of views per link.
That reframes the purchase from a marketing expense to a pipeline recovery action. The buyer of the product is not shopping for a website; they are twelve days into silence on an $11,000 retainer and will pay a small amount for anything that plausibly restarts the conversation today.
The JEV score of 60.4 (band C, confidence 0.69) points to exactly one weakness worth designing around: market demand at 4.41 normalised, against speed to first revenue at 7.87 and solo build feasibility at 7.57. The concept is built fast and monetises quickly; the demand is not automatic. The fix is a tighter trigger, not a broader audience.
So the buyer is narrowed twice. First to agencies and consultancies with 2-20 staff, because they send custom decks and own the sales conversation personally. Second to a specific moment: a deck sent seven or more days ago, above roughly $10k, with no reply. That trigger is observable in public posts (founders describing ghosted proposals), and it converts an abstract tool into an immediate errand.
Competitive reality: the substitute is manual. A founder writes a follow-up email, records a Loom, or nudges with a CRM sequence. PitchDeck Rewind is not competing with Webflow or Canva on site building, and it is not a proposal builder. It competes with the twenty minutes of drafting an awkward follow-up, and it wins if the first recap takes under ten minutes and produces a view notification within a day.
The positioning sentence to use everywhere: your deck was not rejected, it was buried, so send the sixty-second version.
Smallest sellable MVP
A page where an owner uploads one PDF or Docx deck and receives a live recap microsite on a shareable slug, with view notifications, sold as a $99 five-recap pack through Stripe.
Must-have features
- PDF/Docx upload with text extraction
- LLM extraction of offer, price and next steps into structured fields
- Edit-before-publish form with three recap templates (consulting, creative, tech)
- One-page public recap at a custom slug with a single CTA button
- Per-link view count and reopen detection
- Email and Slack notification on first view and re-open
- Stripe checkout for the $99 Recap Pack with a five-recap credit balance
Explicitly out of scope
- Full website builder
- E-signature and in-recap payments
- CRM integrations
- Team seats and a multi-user analytics dashboard
- Custom domains (until the Monthly Closer tier ships in week 4)
- Automated prospecting lists
Demo flow (what the buyer sees)
- Owner signs up with email
- Uploads the sent deck PDF or Docx
- Reviews extracted offer, price and next steps in an edit form
- Picks a template and CTA label, publishes
- Copies the recap link and sends it to the buyer
- Opens the notification email when the buyer views the page
Technical implementation plan
Stack
Architecture
A Next.js app on Vercel serves the authenticated dashboard and the public /r/[slug] recap route. Uploads go to Supabase storage, text is extracted server-side, one OpenAI call returns structured JSON (offer, price, next steps, CTA candidates) into a Supabase table. The owner edits the JSON in a form, picks a template, and publishes; the recap route renders server-side from that row. A small view endpoint increments a counter per slug and per view session, and fires Resend plus Slack once on first view and again on a re-open after 12 hours. Stripe Checkout grants five recap credits via webhook on payment.
Build steps
- Provision Vercel, Supabase, Stripe, Resend and the domain; deploy a skeleton
- Build authenticated upload to Supabase storage with PDF/Docx text extraction
- Write the OpenAI extraction prompt with a strict JSON schema and a fallback for missing fields
- Build the edit-before-publish form and persist the recap row
- Build /r/[slug] server route with three template variants
- Add the view endpoint, per-slug counters and re-open detection
- Wire Resend emails and the Slack webhook for view notifications
- Add Stripe Checkout for the $99 pack, webhook credit granting and credit enforcement
- Load-test extraction on ten public decks and log failure modes
AI components
- OpenAI structured extraction of offer, price, next steps and a suggested CTA label from deck text
- Optional one-sentence summary generation for the recap hero
Pricing and monetization
Recap Pack
Entry offerFor Agency owner with a stalled $10k+ deal
- 5 recap microsites
- View and re-open tracking
- Email and Slack notifications
- Edit-before-publish
Monthly Closer
For Owners sending decks weekly
- Unlimited recaps
- Custom domain
- Priority support
Model: One-time Recap Pack plus an optional monthly subscription, both sold through Stripe Checkout with no free public tier.
First revenue offer: I converted the deck you posted about into a live 60-second recap page. Here is the link, it is yours free. If it reopens the deal, the next five cost $99.
Expected ACV: $99
Upsell path: After a pack is used, offer Monthly Closer at $49/mo for owners sending weekly; add custom domain and the retainer-renewal template as the reason to move up.
First-customer acquisition
Direct LinkedIn and founder-community outreach with a free pre-built recap of a deck the prospect already shared publicly.
Where to find them
- LinkedIn posts containing proposal, ghosted, no reply or lost deal
- LinkedIn search for agency owner and founder at 2-20 person agencies
- Founder Slack and Discord communities for agency and consultancy operators
- r/agency and r/consulting threads about follow-up and stalled proposals
- Twitter/X posts from consultants describing a dead deal
- Public case-study and deck links on agency websites
Exact outreach motions
- Send a mock recap link of the prospect's own public deck with one line of context
- Follow up at day 3 with view counts on the free recap
- Ask for the $99 pack only after the free recap has been opened
- Reply to public posts about silent deals with the recap of a similar deck
Message template
Saw your post about the proposal that went quiet. I rebuilt your deck as a 60-second recap page: [link]. It tracks who opens it, so you know if the buyer is still looking. It is yours free, no signup. If it restarts the thread, five more are $99.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Infrastructure and payments
- Deploy skeleton to Vercel with Supabase and domain.
- Create Stripe products for the $99 pack and $49 plan.
- Connect the Stripe account to TrustMRR before any sale.
Deliverable: Live skeleton app plus working checkout in test mode.
Extraction pipeline
- Upload to Supabase storage with PDF/Docx parsing.
- Write the OpenAI structured extraction prompt and schema.
- Run five public decks through and log failures.
Deliverable: Extraction endpoint returning clean JSON for four of five decks.
Recap rendering
- Build the edit-before-publish form.
- Build /r/[slug] with three templates.
- Add the single CTA button.
Deliverable: A recap page published from an uploaded deck.
Tracking and alerts
- Add the view endpoint and per-slug counters.
- Detect re-opens after 12 hours.
- Wire Resend email and Slack webhook alerts.
Deliverable: View notification delivered within 60 seconds of a page open.
Paid flow live
- Gate publishing behind pack credits.
- Handle Stripe webhook credit granting.
- Run one full paid test end to end.
Deliverable: MVP live and able to take a real $99 payment.
List and mock recaps
- Build a list of 60 agency owners with contact routes.
- Produce five mock recaps from public decks.
- Write the four-message outreach sequence.
Deliverable: 60-row outreach sheet and five live mock recap links.
First sends
- Send 20 first-touch messages with mock links.
- Log replies and objections in one sheet.
- Fix any broken mock recap immediately.
Deliverable: 20 sends out, reply sheet started.
Week 2 · Launch & first sale · 7 days
Volume and fixes
- Send 20 more first-touch messages.
- Patch extraction failures reported by prospects.
- Tighten recap copy on the top template.
Deliverable: 40 total sends and a fixed extraction prompt.
First paid pack
- Follow up on every opened free recap with the $99 offer.
- Share view counts as the reason to buy.
- Send the checkout link directly in DM.
Deliverable: First $99 Recap Pack payment collected.
Delivery automation
- Add the purchase confirmation email with a usage checklist.
- Add a two-minute walkthrough video on the dashboard.
- Remove manual steps from onboarding.
Deliverable: Automated post-purchase onboarding email.
Template quality
- Add a reply-to-reopen CTA variant.
- Add price presentation options.
- Test publish flow on mobile.
Deliverable: Templates v2 shipped.
Targeted segment
- Send 25 messages to owners posting about ghosted deals.
- Reply publicly with a recap example where appropriate.
- Track reply rate by message angle.
Deliverable: 65 cumulative sends with reply rate by angle.
Second tier
- Publish the Monthly Closer page at $49.
- Add a custom domain field placeholder.
- Offer the upgrade to every pack buyer.
Deliverable: Two-tier pricing page live.
Messaging decision
- Compute reply rate and conversion per angle.
- Kill the weakest message.
- Set week three targets from real numbers.
Deliverable: One-page memo on which angle converts.
Week 3 · Repeat & systematize · 7 days
Self-serve intake
- Add a self-serve upload form with manual approval.
- Cap free recaps at three per account.
- Instrument cost per recap.
Deliverable: Self-serve upload live with a cost log.
Public demos
- Publish three example recaps as demo links.
- Add a demo gallery page with copy.
- Add a CTA from gallery to checkout.
Deliverable: Public demo gallery live.
Community posts
- Post a lost-deck teardown in three founder communities.
- Link the demo gallery, not the pricing page.
- Answer every comment the same day.
Deliverable: Three posts and their traffic numbers.
Second wave
- Send 30 messages referencing the demo gallery.
- Re-message week-one non-repliers once.
- Log opens on every free recap.
Deliverable: 30 sends and reopen stats on free recaps.
Slack alerts
- Ship Slack app install for Monthly Closer users.
- Add per-workspace webhook storage.
- Test alert delivery latency.
Deliverable: Slack integration live.
Re-open alerts
- Add a distinct re-open notification email.
- Show view timeline on the owner dashboard.
- Add an unsubscribe path for emails.
Deliverable: Re-open alerts and per-recap timeline.
Numbers
- Reconcile Stripe payouts against TrustMRR.
- Handle any refund requests manually.
- Decide whether to keep or cut Monthly Closer.
Deliverable: Clean revenue ledger and tier decision.
Week 4 · Scale what works · 7 days
Custom domain
- Ship custom domain mapping for Monthly Closer.
- Add DNS instructions page.
- Test one live domain end to end.
Deliverable: Custom domain feature live.
Fourth template
- Build the retainer-renewal recap template.
- Add it to the publish picker.
- Update the gallery with one example.
Deliverable: Fourth template in production.
Repeat purchase
- Ask every prior buyer for a second pack.
- Send 30 new first-touch messages.
- Offer Monthly Closer to repeat pack buyers.
Deliverable: Repeat-purchase asks sent and reply log updated.
One guide
- Write a 600-word guide on the 60-second follow-up.
- Publish it on the site with a recap CTA.
- Share it as the outreach link for two days.
Deliverable: Guide published and used in outreach.
Extraction accuracy
- Collect every failed deck from the month.
- Add few-shot examples from failures.
- Re-run and log pass rate.
Deliverable: Extraction pass rate memo with new prompt version.
Retention emails
- Schedule day 1, 3 and 7 emails for Monthly Closer.
- Add a credit-balance reminder at two credits left.
- Add a win-back email for expired packs.
Deliverable: Three-email onboarding sequence live.
Testimonials
- Ask two paying users for a one-line quote with permission.
- Add quotes to the pricing page.
- Record a short case study of one reopened deal.
Deliverable: Two approved quotes live on site.
Days 29-30 · Consolidate · 2 days
Final push
- Send 25 messages and nudge all warm leads.
- Reconcile Stripe, refunds and fees for the month.
- Verify every sale ran through the connected account.
Deliverable: Reconciled month-end ledger.
Retrospective
- Freeze scope and publish a results page.
- Document the highest-converting message.
- Write the next 30-day plan from real reply rates.
Deliverable: Public results page and next-cycle 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
- All scenarios: Stripe processing assumed at 2.9% plus $0.30 per transaction, blended about 4% of gross (Conservative/Base/Upside).
- Base: 225 cumulative outreach sends at 15-20% reply and 25% close of conversations yields 10 pack buyers (Base).
- Conservative: slow replies and one refund-heavy cohort yield 3 buyers (Conservative).
- Upside: two community posts break out and one buyer upgrades, yielding 25 buyers including a small share of monthly plans (Upside).
- Blended ARPU held at $99 because monthly plans bill only once inside the 30-day window (all scenarios).
- Operating cost covers Vercel, Supabase, Resend, domain and OpenAI extraction at roughly $0.05-0.15 per recap (all scenarios).
- Ad spend is zero in Conservative and Base because the channel is organic outreach; Upside models $150 on one sponsored newsletter slot (Upside).
- Refunds are assumed zero unless a template misfires; only Upside carries a $50 refund line (Upside).
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $12
- Paid marketing
- $0
- Hackathon profit
- $285
- Operating costs
- $25
- Business profit
- $260
Base case
10 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $39
- Paid marketing
- $0
- Hackathon profit
- $951
- Operating costs
- $45
- Business profit
- $906
Optimistic
25 customers- Refunds
- $50
- Chargebacks
- $0
- Payment fees
- $97
- Paid marketing
- $150
- Hackathon profit
- $2,178
- Operating costs
- $90
- Business profit
- $2,088
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
- $906
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
Scenario models from stated assumptions, not verified revenue. No customers, traction or partnerships exist at the start; all figures are projections for planning only.
Main risks and validation experiments
Risk 1Cold outreach reply rate stays near zero, so no conversations start.
Lead with a finished recap of the prospect's own public deck instead of a pitch, and follow up once at day three with view data.
Send 40 messages in week one with mock links and count replies within 72 hours.
Fewer than 3 replies after 80 sends across two message angles means the channel is wrong and the segment must change.
Risk 2Extraction produces wrong prices or missing next steps on complex decks, making the recap look broken.
Strict JSON schema with optional fields, an edit-before-publish form, and a graceful template fallback that hides empty sections.
Run ten public decks through extraction and score field accuracy manually before day five.
Under 70% usable output after the edit form means the product needs a manual-first mode or a narrower deck format.
Risk 3Buyers treat the pack as a one-off and never repurchase or subscribe.
Ask for a second pack at day seven after first use, and gate custom domains and Slack alerts behind Monthly Closer.
Offer a second pack to the first five buyers and measure conversion.
Zero repeat purchases from five buyers means pricing must move to monthly only, or the wedge is a service not a product.
Risk 4Free recap abuse and runaway OpenAI and hosting cost erode margin.
Cap free recaps at three per account, manual approval on the free form, cache extraction output and log cost per recap.
Instrument delivery cost per recap from day fifteen and compare against the $99 price.
Cost above $10 per delivered pack after caching means the extraction model tier must drop or free intake must close.
Hour-by-hour: the first 24 hours
Hours 1-2
- Buy the domain and deploy the Next.js skeleton to Vercel.
- Create the Supabase project with storage and the recaps table.
- Create Stripe products for $99 and $49 and connect the account to TrustMRR.
Output: Live skeleton at a real domain and a working checkout in test mode.
Hours 3-5
- Add PDF/Docx upload and server-side text extraction.
- Write the OpenAI extraction prompt with a strict schema.
- Run three public decks and inspect the JSON.
Output: Extraction endpoint returning structured offer, price and next steps.
Hours 6-8
- Build the edit-before-publish form.
- Build /r/[slug] with the consulting template.
- Publish one live recap end to end.
Output: One shareable recap URL built from a real deck.
Hours 9-11
- Add the view counter and the Resend notification email.
- Convert two public decks into mock recaps.
- Build a 20-row outreach sheet with contact routes.
Output: Two mock recaps and a 20-row prospect list.
Hours 12-14
- Send 10 first-touch messages with mock links.
- Log sends and replies in one sheet.
- Note every objection verbatim.
Output: 10 sends out and a first objection log.
Full 30-day launch report
Read the full generated report
PitchDeck Rewind — 30-Day Launch Report
JEV scored this concept 60.4/100 (band C, confidence 0.69). The split inside that score is the whole plan: speed to first revenue normalises to 7.87 and solo build feasibility to 7.57, while market demand lags at 4.41. Build fast, sell fast, and narrow the buyer until demand stops being ambiguous.
1. Product opportunity and positioning
Every agency owner has a folder of decks that were sent and never answered. The deal is not lost, it is silent. The owner knows the buyer is busy, knows one more email risks looking needy, and knows rewriting the pitch costs an hour they will not spend on a maybe.
PitchDeck Rewind sells the follow-up, not the pitch. Input: the deck that already went out. Output: one page — what we offered, what it costs, what happens next, one button. The buyer skims it in sixty seconds. The seller gets an alert the moment it opens, plus a view count per link.
That reframes the purchase from marketing spend to pipeline recovery. The buyer is not shopping for a website; they are twelve days into silence on an $11,000 retainer and will pay a small amount for anything that plausibly restarts the thread today.
JEV's weak demand score is a targeting signal, not a verdict. The buyer is narrowed twice: agencies and consultancies of 2-20 staff, because they send custom decks and own the sale personally; and a specific moment — a deck sent seven or more days ago, above roughly $10k, with no reply. That moment is observable in public posts about ghosted proposals, which converts an abstract tool into an errand with a deadline.
The substitute is manual: a follow-up email, a Loom, a CRM nudge. PitchDeck Rewind competes with twenty minutes of drafting an awkward follow-up, and wins if the first recap takes under ten minutes and produces a view alert inside a day.
Use one sentence everywhere: your deck was not rejected, it was buried, so send the sixty-second version.
2. Smallest sellable MVP
Sellable means: upload a PDF, edit three fields, publish a slug, get an alert on open, pay $99. That is it. Three templates, one CTA, four recap credits per pack plus one for onboarding.
Out of scope for all 30 days: e-signature, payments inside the recap, CRM sync, team seats, analytics dashboards, a site builder. During week one the founder reviews extraction output before publishing; that is QA of software output, not a service business, and it ends at self-serve intake on day fifteen.
3. Technical implementation plan
Next.js on Vercel, Supabase for auth, Postgres and storage, pdf-parse and mammoth for text, one OpenAI structured-output call per deck, Stripe Checkout with a credit ledger, Resend for email and Slack webhooks for alerts.
The only call that matters: extraction into a strict JSON schema with optional fields. The publish form lets the owner correct a wrong price before the buyer ever sees it. The template hides empty sections instead of rendering blanks. Cache extraction per upload so a re-render costs nothing.
Hardest technical risk is designer-built decks with multi-column pricing pages. Mitigation is the fallback template plus few-shot examples harvested from real failures on day twenty-six. Cost control: three free recaps per account, manual approval on free intake, cost per recap logged from day fifteen.
4. Pricing and monetization
Recap Pack at $99 one-time for five recaps. Roughly one hour of an agency owner's billable time, spent against a $10k deal — an impulse purchase with an obvious comparison. Monthly Closer at $49/month for owners sending weekly, unlocked by custom domain and Slack alerts.
No public free tier. The free recap is a 1:1 gift in outreach, capped, so it never becomes a support queue. Blended ARPU stays near $99 inside 30 days because monthly plans bill once in the window.
Upsell path: second pack at day seven, upgrade to monthly when a buyer hits their third recap.
5. First-customer acquisition
One channel: direct LinkedIn and founder-community outreach, leading with a finished recap of the prospect's own public deck.
Targets: 40 sends in week one, 40 in week two, 55 in week three, 65 in week four, 25 in the final two days — about 225 total. At a 15-20% reply rate that is 34-45 conversations; at 25% close that is 9-11 buyers. That is the base scenario, and it is the number the whole month is engineered toward.
Every send has three parts: the recap link, one line of context, and the $99 offer only after the link is opened. Day-three follow-up uses view data as the reason to reply, never as pressure. Public posts about dead deals are answered with a similar recap example, not a pitch.
6. Detailed 30-day execution roadmap
Days 1-5 build and launch: infrastructure, extraction, recap rendering, tracking and the paid flow, with the MVP live on day five. Days 6-14 sell: list building, 65 sends, and the first $99 pack targeted for day nine. Days 15-21 make it repeatable: self-serve intake, public demo gallery, Slack alerts, re-open alerts, ledger reconciliation. Days 22-28 widen: custom domain, a retainer-renewal template, repeat-purchase asks, one guide, extraction accuracy work, onboarding emails, testimonials. Days 29-30 close: final sends, reconciliation, public results page and the next-cycle plan. Full day-level tasks and deliverables are in the roadmap object above.
7. Revenue and profit scenarios
All figures are projections from stated assumptions, not verified revenue. No customers exist today.
Conservative: 3 buyers, gross $297, fees about $12, no ad spend, operating cost about $25 — hackathon profit $285, business profit about $260.
Base: 10 buyers, gross $990, fees about $39, no ad spend, operating cost about $45 — hackathon profit $951, business profit about $906.
Upside: 25 buyers, gross $2,475, one $50 refund, fees about $97, $150 on a sponsored slot, operating cost about $90 — hackathon profit $2,178, business profit about $2,088.
Remember the two numbers: hosting and API cost do not reduce the hackathon figure but do reduce the business figure. Stripe fees, refunds and any ad spend reduce both.
8. Main risks and validation experiments
Silent outreach is the top risk. Test with 40 mock-link messages in week one; under 3 replies from 80 sends across two angles, change segment. Extraction quality is second: score ten public decks before day five; under 70% usable output, add a manual-first mode. Repeat purchase is third: ask the first five buyers for a second pack; zero repeats means pricing must move to monthly only. Cost creep is fourth: log cost per recap from day fifteen; above $10 per pack, drop the model tier or close free intake.
9. First 24-hour action plan
Hours 1-2: domain, Vercel skeleton, Supabase, Stripe products, TrustMRR connection. Hours 3-5: upload, extraction, prompt, three test decks. Hours 6-8: edit form and the first published recap. Hours 9-11: view counter, email alert, two mock recaps, 20-row prospect list. Hours 12-14: 10 sends and an objection log. At the end of day one the product is not finished, but a real recap link exists and ten agency owners have seen it.
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 →Hookframe
Hookframe turns an app icon, a few screenshots and one chosen mechanic into a single-file, MRAID-safe playable ad under 5MB that an indie mobile studio can upload to Meta or AppLovin the same day.
Pitch Rehearsal Scorecard
A voice rehearsal tool that turns a non-native founder's investor pitch into a scored, annotated audio scorecard they can fix before the real meeting.
Quote60 Trades
Talk through a job for 60 seconds and get a branded, line-item PDF quote you can text the customer before you leave the driveway.