Catalog Bridge
A Chrome extension that turns a supplier's product pages into a Shopify-ready import CSV, captured inside the buyer's own logged-in browser session.
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-operator of a 1-5 person Shopify or WooCommerce store who has just signed a new supplier or is migrating a catalog of 50-500 SKUs, with no developer on staff.
Monetization potential 4.9/10
Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.8/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
18 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Owner-operator of a 1-5 person Shopify or WooCommerce store who has just signed a new supplier or is migrating a catalog of 50-500 SKUs, with no developer on staff.
Why now
The buyer is mid-migration with a deadline and an owed spreadsheet, the question is asked weekly in r/shopify and r/ecommerce, and Manifest V3 plus a merchant-of-record checkout let one person ship and sell in under a week.
Problem
Copy-pasting titles, prices, variants and image URLs from a supplier site into an import sheet takes 2-5 days per catalog and still produces rows that fail Shopify's importer.
Solution
The user picks fields once with a visual picker; the extension saves that mapping as a per-domain recipe, pages through the listing in the user's own session, and emits a Shopify-spec CSV with a row-level validation report.
Catalog Bridge — 30-Day Solo Founder Report
JEV score 63.6/100 (band C, confidence 0.64). Contest window Nov 16 – Dec 16, 2026, 13:00 UTC. One founder, no funding, no paid acquisition. Every revenue figure is a projection built from stated assumptions, not verified revenue.
1. Product opportunity and positioning
Catalog Bridge sells a file, not a platform. The buyer owns a one-to-five-person Shopify or WooCommerce store and has just signed a supplier or is migrating 50-500 SKUs. They already owe someone a spreadsheet on a deadline, and producing it means two to five days of copy-pasting titles, prices, variants and image URLs — work that still yields rows Shopify's importer rejects.
That is the wedge. The buyer is not shopping for automation software; they are trying to hit a launch date. A free first-catalog conversion costs the founder twenty minutes and proves the output before any trust cycle starts.
The position is deliberately narrow: one fixed artifact (a validated Shopify-spec CSV plus a row-level validation report) and one reusable per-domain recipe. General browser-automation tools — the category the original Axiom.ai defined — ask a non-technical buyer to build and maintain a bot per supplier site. That is a platform purchase on a deadline. Catalog Bridge asks for one picker pass and remembers it.
JEV scored 63.6/100. Strongest signals: speed to first revenue (7.79 normalized) and solo build feasibility (7.04). Weakest: monetization potential (4.9), with the hint to tie price to a measurable outcome and add a repeat path. The plan answers that directly: price anchors to days of labor saved, and Pro exists so a buyer with several suppliers or a quarterly re-sync pays more than once.
Why now is distribution, not technology. 'How do I import my supplier's catalog?' is asked in r/shopify and r/ecommerce most weeks, by people who can be answered today and sold to without ads, an SEO ramp, a partnership or procurement.
2. Smallest sellable MVP
The sellable unit: open a supplier listing, click the fields once, get back a CSV Shopify accepts on first import plus a report of the rows that would have broken. Everything else is deferrable.
In v1: MV3 extension, click-to-pick selector overlay, per-domain recipe in chrome.storage.local, pagination loop with a max-page guard, a fixed field-to-Shopify-column mapping (title, price, SKU, variant, image URL, body), Papa Parse CSV output, a validator flagging missing price, duplicate SKU and malformed variants, Lemon Squeezy license activation, and a docs page with a 90-second walkthrough.
Not in v1: a general bot builder, hosted or scheduled scraping, WooCommerce/Etsy/Amazon export, image downloading, team accounts, shared recipe library. Each is a platform promise this product refuses.
Demo flow: install, open a supplier catalog, click New recipe, click title → price → SKU → variant → image on one product, advance one page to confirm the loop, press Capture. The extension walks the listing in the buyer's own logged-in session, validates rows in the popup, and downloads supplier-catalog.csv plus validation-report.txt.
3. Technical implementation plan
Stack: Chrome Manifest V3, vanilla JS bundled with esbuild, Papa Parse, chrome.storage.local, Lemon Squeezy License API, Cloudflare Pages, chrome.downloads.
Plain-language architecture: the content script draws the picker overlay and returns CSS selectors for clicked elements. The service worker owns the loop — it re-injects the collector per page, reads rows, finds the next control, and stops on a repeated URL, a missing control or the page cap. The popup holds the mapping table, runs validation and writes the CSV. License state is checked once per session against Lemon Squeezy and cached; a lapsed key degrades to a 20-row export instead of a hard failure.
Build order: MV3 skeleton and message bus, picker overlay, recipe persistence by hostname, single-page collection, pagination with stop conditions, mapping table, CSV write and validator, license activation, landing page and walkthrough.
The hardest technical risk is pagination on supplier sites using infinite scroll, hashed class names, or a next-link that changes shape per page. Mitigation: let the user click the next control during recipe creation rather than guessing it, and ship a capture-current-page-only fallback so a failed loop still produces a partial file rather than nothing.
AI is optional and cost-capped: one serverless call may suggest which Shopify column an ambiguous field label maps to, on user request only. Validation and CSV generation stay deterministic.
4. Pricing and monetization
Two one-time tiers. Starter $149: one catalog up to 300 SKUs, one saved recipe, CSV export, validation report. Pro $349: five catalogs up to 1,500 SKUs, unlimited recipes, a re-run diff of changed prices and new SKUs, and setup email support. One-time pricing matches a project-shaped purchase and removes the subscription objection on day one; the repeat path is additional catalogs, the re-run diff and a repeat-run pass, not a monthly charge.
The first offer is free and is the whole acquisition engine: send three supplier URLs, receive a Shopify-ready CSV within 24 hours plus the rows a manual sheet would have broken. The license is offered only after the file lands and its SKU count and capture time are quoted back.
Expected first-purchase value is $149, with a $349 upside when a buyer names a second supplier in the same conversation. Revenue grows through Pro upgrades, a repeat-run pass for quarterly re-syncs, and referrals.
5. First-customer acquisition
One channel: replying to existing threads where store owners ask how to import a supplier catalog. No ads, no SEO ramp, no partnerships.
Places: r/shopify, r/ecommerce, r/dropship, Shopify Community forums, the WooCommerce support forum, two or three small ecommerce Discords, and public posts announcing a new supplier.
Actions: search each community weekly on 'import supplier catalog', 'CSV import', 'new supplier', 'migrating products'; reply with a genuine short answer plus the free-three-URLs offer; deliver within 24 hours; send the $149 Starter offer with SKU count and time saved attached; follow up once after five days with the validation report.
Message: 'Saw your post about the new supplier. Two to five days of copy-paste is normal and Shopify still rejects half the rows. Send me up to three supplier URLs — I'll send back a Shopify-ready CSV and the validation report within 24 hours, free. If it's useful, the extension that produced it is $149 and you run the rest yourself.'
Week-one goal: extension live and taking payment, 30 threads answered, 10 free catalogs delivered, first paid license attempted.
6. 30-day execution roadmap
Week 1 (days 1-5 build, 6-7 launch): extension to sellable v1 by day 5 with license activation live, landing page and docs published, 40-thread outreach sheet built with subreddit rules noted, 10 replies live on day 7.
Week 2 (days 8-14): deliver every free CSV within 24 hours, convert to $149, fix the top supplier-site failure, publish refund policy and a sample validation report, follow up all recipients; first sale targeted day 12; re-run diff shipped by day 13.
Week 3 (days 15-21): add a second and third channel, publish three starter recipes, pitch Pro at $349, instrument capture time per delivery, ask each buyer for one referral.
Week 4 (days 22-28): cut refund surface with a pre-purchase sample CSV, publish one indexable how-to page, 15 touches per day, add a $79 repeat-run pass, publish redacted before/after proof above the fold.
Days 29-30: final 20-thread push, reconcile every payment in TrustMRR, write the post-mortem.
7. Revenue and profit scenarios
Projections only. Conservative: 4 licenses at $149 ARPU ≈ $596 gross. Base: 14 licenses at $189 blended ARPU ≈ $2,646 gross. Upside: 30 licenses at $199 blended ARPU ≈ $5,970 gross. Fees assume Lemon Squeezy merchant-of-record at 5% + $0.50 per transaction, about 5.5% effective. No paid marketing in any scenario except upside. Hackathon profit deducts refunds, chargebacks, processing fees and paid spend; business profit additionally deducts hosting, domain and tooling. Operating costs are low because the extension runs in the buyer's browser and there is no scraping fleet.
8. Risks and validation experiments
Recipe breakage on login walls and client-side rendering: mitigate with the manual next-button picker and page-only fallback; validate by attempting three real supplier catalogs in the first 48 hours; kill the recipe approach for a domain if it fails on two of three.
Shopify variant edge cases producing rejected rows and refunds: mitigate with a validator plus a pre-purchase sample file; validate by importing one generated CSV into a real dev store before selling.
Subreddit self-promotion rules removing offers: mitigate by answering first and offering in-thread only where rules allow; validate by checking each subreddit's rule page before posting.
Supplier terms prohibiting automated capture: mitigate by capturing only in the buyer's own authenticated session and never storing supplier content server-side; validate by reading ToS on the three most common supplier domains.
Conversion below 25% on free conversions: validate after 10 deliveries; if under 10%, change the offer to a paid $49 single-catalog conversion before abandoning the wedge.
9. First 24 hours
Hours 1-2: repo, MV3 skeleton, extension loads unpacked; Lemon Squeezy account and two draft products. Hours 3-5: click-to-pick overlay returning selectors. Hours 6-8: recipe persistence and replay. Hours 9-12: single-page collection plus first real CSV from a public supplier catalog. Hours 13-16: 20-thread outreach sheet with rules noted. Hours 17-20: landing hero, docs stub and the free-three-URLs message written.
Smallest sellable MVP
A Chrome extension that captures one supplier catalog into a Shopify-accepted CSV with a validation report, gated by a Lemon Squeezy license key.
Must-have features
- Chrome MV3 extension with a click-to-pick field selector
- Per-domain recipe saved in chrome.storage.local and re-runnable
- Pagination loop with next-control picker, repeat-URL stop and page cap
- Mapper from picked fields to Shopify CSV columns (title, price, SKU, variant, image URL, body)
- Papa Parse CSV generation triggered by chrome.downloads
- Validator flagging missing price, duplicate SKU and malformed variant rows
- Lemon Squeezy license activation with a degraded 20-row trial mode
- Docs page with a 90-second capture walkthrough
- Capture-current-page-only fallback when pagination fails
Explicitly out of scope
- General-purpose bot builder or visual workflow canvas
- Hosted or scheduled cloud scraping
- WooCommerce, Etsy or Amazon export
- Image downloading or re-hosting
- Team accounts, roles or shared recipe library
- Metafield and collection mapping
- Automatic supplier-side login handling
Demo flow (what the buyer sees)
- Install the extension and open a supplier catalog listing page
- Click New recipe and click title, price, SKU, variant and image on one product
- Advance one page to confirm the next-control detection
- Press Capture; the extension walks the listing in the buyer's own session
- The popup validates rows and downloads supplier-catalog.csv plus validation-report.txt
- Buyer imports the CSV into Shopify and sees zero rejected rows
Technical implementation plan
Stack
Architecture
The content script draws the picker overlay and returns CSS selectors for clicked elements. The service worker owns the capture loop: it re-injects the collector on each page, extracts rows, finds the next control the user picked, and stops on a repeated URL, a missing control or a page cap. The popup holds the field-to-Shopify-column mapping table, runs deterministic validation and writes the CSV through chrome.downloads. Recipes are stored per hostname in chrome.storage.local. License state is checked once per session against the Lemon Squeezy API and cached; an invalid key allows a 20-row export so the buyer can still see the output.
Build steps
- Scaffold the MV3 extension with popup, content script and service worker; wire the message bus
- Build the click-to-pick overlay and serialize selectors for each picked field
- Persist and reload a recipe keyed by hostname in chrome.storage.local
- Collect rows from a single listing page into a structured array
- Add pagination: user-picked next control, repeat-URL detection, max-page guard
- Implement the mapping table from picked fields to Shopify CSV columns
- Generate the CSV with Papa Parse and download it via chrome.downloads
- Implement the validator and render a row-level validation report
- Add Lemon Squeezy license activation with a cached session check and trial cap
- Publish landing page, docs and the 90-second walkthrough to Cloudflare Pages
AI components
- Optional only: one serverless LLM call that suggests which Shopify column an ambiguous field label maps to, invoked on explicit user request and never used in validation or CSV generation
Pricing and monetization
Starter
Entry offerFor Single-store owner onboarding one supplier catalog
- 1 catalog up to 300 SKUs
- 1 saved supplier recipe
- Shopify-spec CSV export
- Row-level validation report
Pro
For Store owner running several suppliers or re-syncing catalogs quarterly
- 5 catalogs up to 1,500 SKUs
- Unlimited saved recipes
- Re-run diff showing changed prices and new SKUs
- Email support for setup
Model: One-time per-catalog licenses with a saved recipe, sold in two tiers, plus a low-priced repeat-run pass for quarterly re-syncs.
First revenue offer: Send me up to three supplier URLs; I return a Shopify-ready CSV plus the validation report within 24 hours, free — then $149 to run the rest of the catalog yourself.
Expected ACV: $189
Upsell path: Upgrade to Pro at $349 when the buyer names a second supplier in the same thread; sell a $79 repeat-run pass when the same catalog is re-synced next quarter; ask every buyer for one named referral.
First-customer acquisition
Replying to existing 'how do I import my supplier's catalog' threads in r/shopify and r/ecommerce with a free first-catalog conversion.
Where to find them
- r/shopify threads mentioning supplier, catalog import or CSV errors
- r/ecommerce and r/dropship migration threads
- Shopify Community forum 'Importing products' section
- WooCommerce support forum product-import threads
- Two or three small ecommerce Discords with a help channel
- Public posts announcing a newly signed supplier
Exact outreach motions
- Search each community weekly for 'import supplier catalog', 'CSV import', 'new supplier', 'migrating products'
- Reply with a real answer about Shopify's CSV requirements first, then the free-three-URLs offer only where rules permit
- Deliver the CSV within 24 hours and reply with SKU count, capture time and the rows that would have failed
- Send the $149 Starter offer referencing the delivered file, not a generic pitch
- Follow up once after five days with the validation report attached
- Post one build-in-public note showing the before/after row count where self-promotion is allowed
Message template
Saw your post about the new supplier. Two to five days of copy-paste is normal and Shopify still rejects half the rows. Send me up to three supplier URLs — I'll send back a Shopify-ready CSV and the validation report within 24 hours, free. If it's useful, the extension that produced it is $149 and you run the rest yourself.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Extension skeleton
- Scaffold MV3 extension with popup, content script and service worker.
- Wire the content-to-popup message bus.
- Stub the license check to allow local development.
Deliverable: Extension loads unpacked and reads the active tab DOM.
Click-to-pick and recipe persistence
- Build the click-to-pick overlay returning CSS selectors.
- Save recipe JSON keyed by hostname in chrome.storage.local.
- Add a re-run button that re-applies the saved recipe.
Deliverable: Recipe saved on one visit and re-applied on the next.
Pagination and row collection
- Implement user-picked next control with repeat-URL stop and max-page guard.
- Collect and normalize rows across pages into memory.
- Handle variant rows from a size or colour matrix page.
Deliverable: Multi-page capture of a real 50-SKU listing in one pass.
The sellable artifact
- Generate the Shopify-spec CSV with Papa Parse.
- Flag missing price, duplicate SKU and malformed variant rows.
- Run three public supplier catalogs end to end.
Deliverable: Valid CSV plus row-level validation report from three sites.
Payments and store listing
- Create Lemon Squeezy Starter $149 and Pro $349 products with license activation.
- Publish landing page, docs and 90-second walkthrough on Cloudflare Pages.
- Submit the extension to the Chrome Web Store.
Deliverable: MVP accepting payments with a working license gate.
Threads and message
- Write the free-three-URLs reply and the delivery email.
- Collect 40 target threads from r/shopify and r/ecommerce.
- Record each subreddit's self-promotion rule in the sheet.
Deliverable: Outreach sheet with 40 threads and rules notes.
First public replies
- Reply to 10 threads with the free conversion offer.
- Post one build-in-public note where rules allow.
- Set up a single support inbox alias.
Deliverable: 10 replies live and one build note posted.
Week 2 · Launch & first sale · 7 days
First conversions
- Convert the first three supplier URLs received.
- Return each CSV within 24 hours with SKU count and time saved.
- Log every supplier-site blocker encountered.
Deliverable: Three free CSVs delivered with metrics attached.
Starter offer
- Send the $149 Starter offer to every free-CSV recipient.
- Reply to 10 more threads.
- Ask one recipient for a one-line permission quote.
Deliverable: Offers sent and 20 threads touched.
Top failure
- Fix the most common supplier-site failure (login wall or lazy load).
- Ship a patch release to the store.
- Deliver four more free CSVs.
Deliverable: Updated extension and seven free CSVs delivered.
Refund surface
- Publish a refund policy and a sample validation report page.
- Add a one-click license activation screen.
- Reply to 10 more threads.
Deliverable: Trust pages live and 30 threads touched.
Close the first license
- Follow up every free-CSV recipient once.
- Offer a 20-minute screen-share capture to the two warmest leads.
- Post a demo GIF in the build thread.
Deliverable: First paid license expected.
Pro features
- Build the re-run diff of changed prices and new SKUs.
- Demo the diff to existing users.
- Reply to 10 more threads.
Deliverable: Working re-run diff view.
Funnel maths
- Count replies, free CSVs, licenses and conversion rate.
- Drop the message angle that produced zero replies.
- Queue week-three threads.
Deliverable: Funnel spreadsheet with week-two numbers.
Week 3 · Repeat & systematize · 7 days
Beyond two subreddits
- Answer questions on the Shopify Community and WooCommerce forums with the same offer.
- Find 5 ecommerce Discords with active help channels.
- Log which source produced each reply.
Deliverable: Two additional channels active and tracked.
Lower first-run friction
- Ship three starter recipes for common supplier platforms.
- Document them on the docs page.
- Reference them in relevant replies.
Deliverable: Three published starter recipes.
Raise order value
- Pitch Pro at $349 to any buyer naming two or more suppliers.
- Add unlimited-recipe handling to the license check.
- Reply to 12 threads.
Deliverable: First Pro offer sent.
Quantify the outcome
- Instrument capture time and row count in the extension.
- Attach the numbers to every delivery email.
- Reply to 12 threads.
Deliverable: Per-delivery time-saved stat generated automatically.
Variant and stock rows
- Handle variant pricing and out-of-stock rows correctly.
- Add a manual column override in the picker.
- Ship v0.4 to the store.
Deliverable: v0.4 with column override support.
Second-degree buyers
- Ask every paying buyer for one store-owner referral.
- Add a $25 credit note to each delivery email.
- Reply to 12 threads.
Deliverable: Referral ask sent to all buyers.
Cut what fails
- Tally revenue, refunds and conversion by channel.
- Stop the work that produced no replies.
- Plan days 22-30.
Deliverable: Week-three scorecard with per-channel conversion.
Week 4 · Scale what works · 7 days
Pre-purchase proof
- Add a sample-CSV step to the landing page before checkout.
- Publish a one-business-day support turnaround.
- Audit any refund request within 12 hours.
Deliverable: Lower refund surface with sample-first checkout.
One indexable page
- Write a supplier-catalog-import how-to on the docs site.
- Link it in replies instead of repeating text.
- Add a clear title and description.
Deliverable: One indexable how-to page published.
Touches per day
- Reply to 15 threads across both subreddits.
- DM five store owners who posted catalogs publicly.
- Keep every free CSV inside 24 hours.
Deliverable: 15 new touches and 5 direct messages.
Non-subscription repeat revenue
- Add a $79 repeat-run pass for quarterly re-syncs.
- Upgrade any Starter buyer running two catalogs to Pro.
- Publish the new price line.
Deliverable: Repeat-run pass live and pitched.
Public evidence
- Publish a redacted before/after CSV with its validation report.
- Place it above the fold on the landing page.
- Reply to 15 threads.
Deliverable: Public proof section live.
Repeat signal
- Email every buyer a free re-run for one new supplier this month.
- Track replies as a repeat-purchase signal.
- Reply to 15 threads.
Deliverable: Buyer list emailed with a tracked reply rate.
Verified numbers
- Recount revenue, refunds, chargebacks and processing fees.
- Choose the final December 16 push channel.
- List the three remaining blockers.
Deliverable: Verified numbers sheet ready for reconciliation.
Days 29-30 · Consolidate · 2 days
Maximum touches
- Reply to 20 threads with the free conversion offer.
- Follow up every warm lead exactly once.
- Publish a final build-in-public thread.
Deliverable: 20 touches and a final public post.
Reconcile and write up
- Send final invoices ahead of the December 16 13:00 UTC cutoff.
- Reconcile every payment in the TrustMRR-connected account.
- Write the post-mortem and the next-30-day plan.
Deliverable: Reconciled close and written post-mortem.
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: 4 licenses sold, all Starter at $149, no paid marketing.
- Base: 14 licenses at a $189 blended ARPU (roughly 80% Starter, 20% Pro).
- Upside: 30 licenses at a $199 blended ARPU (roughly 75% Starter, 25% Pro) after 20% of revenue-equivalent paid spend on sponsored posts.
- Payment processing assumes Lemon Squeezy merchant-of-record at 5% + $0.50 per transaction, about 5.5% effective at these price points.
- No paid marketing in the conservative and base scenarios; organic subreddit outreach is $0.
- Operating costs cover Cloudflare Pages, domain, email alias and the optional field-suggestion API only; there is no scraping fleet or human operations.
- Refunds assume one Starter unit in the base case and two in the upside case.
- All figures are projections from stated assumptions, not verified revenue or existing customers.
Conservative
4 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $33
- Paid marketing
- $0
- Hackathon profit
- $563
- Operating costs
- $40
- Business profit
- $523
Base case
14 customers- Refunds
- $149
- Chargebacks
- $0
- Payment fees
- $146
- Paid marketing
- $0
- Hackathon profit
- $2,351
- Operating costs
- $120
- Business profit
- $2,231
Optimistic
30 customers- Refunds
- $298
- Chargebacks
- $0
- Payment fees
- $328
- Paid marketing
- $200
- Hackathon profit
- $5,144
- Operating costs
- $250
- Business profit
- $4,894
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $2,086
- Payment fees (3.9%)
- $81
- Paid marketing
- $0
- Hackathon profit
- $2,005
- Business profit
- $1,885
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. Nothing here represents existing customers, traction or collected money.
Main risks and validation experiments
Risk 1Supplier sites behind a login wall or heavy client-side rendering break the recipe and truncate the capture.
Let the user click the next control during recipe creation and ship a capture-current-page-only fallback so a partial file is always produced.
Attempt three real supplier catalogs within 48 hours and record time-to-recipe and truncation rate per domain.
If two of the first five supplier domains cannot be captured, narrow the pitch to platforms that work and re-test before spending more days.
Risk 2Shopify variant and metafield edge cases produce rows the importer rejects, triggering refunds and chargebacks.
Validator plus a pre-purchase sample CSV generated from the buyer's own URL before they pay.
Import one generated CSV into a real Shopify development store and count rejected rows before the first sale.
If more than 5% of rows are rejected on two independent catalogs after fixes, stop selling until the mapper is corrected.
Risk 3Subreddit self-promotion rules remove the free-conversion offer posts and cut the only acquisition channel.
Answer the technical question first and offer the conversion only in threads where rules permit; keep a second and third channel live by day 15.
Read each subreddit's rules page before posting and log removals per community over the first 10 replies.
If more than half of replies are removed for promotion, move the offer to the Shopify and WooCommerce forums and DMs only.
Risk 4Free conversions do not convert to paid licenses at the assumed 25%.
Deliver the file with SKU count and capture time attached, then send the $149 offer against that measured outcome.
Measure paid conversion across the first 10 free conversions before changing price or product.
If conversion is under 10% after 10 deliveries, test a $49 paid single-catalog conversion before abandoning the wedge.
Risk 5Supplier terms of service may prohibit automated capture even inside the buyer's own session.
Capture runs entirely in the buyer's authenticated browser, nothing is stored server-side, and the docs state the buyer is responsible for supplier terms.
Read the terms of the three most common supplier domains named in outreach threads and log the language.
If major suppliers explicitly prohibit any automated collection, add a manual per-page confirm step or change the target supplier category.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create the repo and MV3 skeleton with popup, content script and service worker.
- Load the extension unpacked and confirm it reads the active tab.
- Open Lemon Squeezy and create Starter $149 and Pro $349 draft products.
Output: Working unpacked extension plus two draft products.
Hours 3-5
- Build the click-to-pick overlay that returns CSS selectors.
- Test the picker on two public supplier catalogs.
- Log selector quality per site.
Output: Functioning field picker with two test captures.
Hours 6-8
- Persist recipe JSON keyed by hostname in chrome.storage.local.
- Add the re-run button that re-applies the recipe.
- Verify round-trip on a reloaded page.
Output: Recipe save and replay working end to end.
Hours 9-12
- Collect rows from one listing page and map them to Shopify columns.
- Generate the first CSV with Papa Parse and download it.
- Eyeball the output against Shopify's documented column names.
Output: First real catalog CSV generated from a public supplier site.
Hours 13-16
- Build a 20-thread outreach sheet from r/shopify and r/ecommerce.
- Record each subreddit's self-promotion rule next to the thread.
- Draft the free-three-URLs reply and the delivery email.
Output: Outreach sheet with 20 threads, rules notes and two message drafts.
Hours 17-20
- Write the landing page hero and a docs stub.
- Publish both to Cloudflare Pages.
- Queue the Chrome Web Store submission details.
Output: Live landing page and docs stub ready for day-two traffic.
Full 30-day launch report
Read the full generated report
Catalog Bridge — 30-Day Solo Founder Report
JEV score 63.6/100 (band C, confidence 0.64). Contest window Nov 16 – Dec 16, 2026, 13:00 UTC. One founder, no funding, no paid acquisition. Every revenue figure is a projection built from stated assumptions, not verified revenue.
1. Product opportunity and positioning
Catalog Bridge sells a file, not a platform. The buyer owns a one-to-five-person Shopify or WooCommerce store and has just signed a supplier or is migrating 50-500 SKUs. They already owe someone a spreadsheet on a deadline, and producing it means two to five days of copy-pasting titles, prices, variants and image URLs — work that still yields rows Shopify's importer rejects.
That is the wedge. The buyer is not shopping for automation software; they are trying to hit a launch date. A free first-catalog conversion costs the founder twenty minutes and proves the output before any trust cycle starts.
The position is deliberately narrow: one fixed artifact (a validated Shopify-spec CSV plus a row-level validation report) and one reusable per-domain recipe. General browser-automation tools — the category the original Axiom.ai defined — ask a non-technical buyer to build and maintain a bot per supplier site. That is a platform purchase on a deadline. Catalog Bridge asks for one picker pass and remembers it.
JEV scored 63.6/100. Strongest signals: speed to first revenue (7.79 normalized) and solo build feasibility (7.04). Weakest: monetization potential (4.9), with the hint to tie price to a measurable outcome and add a repeat path. The plan answers that directly: price anchors to days of labor saved, and Pro exists so a buyer with several suppliers or a quarterly re-sync pays more than once.
Why now is distribution, not technology. 'How do I import my supplier's catalog?' is asked in r/shopify and r/ecommerce most weeks, by people who can be answered today and sold to without ads, an SEO ramp, a partnership or procurement.
2. Smallest sellable MVP
The sellable unit: open a supplier listing, click the fields once, get back a CSV Shopify accepts on first import plus a report of the rows that would have broken. Everything else is deferrable.
In v1: MV3 extension, click-to-pick selector overlay, per-domain recipe in chrome.storage.local, pagination loop with a max-page guard, a fixed field-to-Shopify-column mapping (title, price, SKU, variant, image URL, body), Papa Parse CSV output, a validator flagging missing price, duplicate SKU and malformed variants, Lemon Squeezy license activation, and a docs page with a 90-second walkthrough.
Not in v1: a general bot builder, hosted or scheduled scraping, WooCommerce/Etsy/Amazon export, image downloading, team accounts, shared recipe library. Each is a platform promise this product refuses.
Demo flow: install, open a supplier catalog, click New recipe, click title -> price -> SKU -> variant -> image on one product, advance one page to confirm the loop, press Capture. The extension walks the listing in the buyer's own logged-in session, validates rows in the popup, and downloads supplier-catalog.csv plus validation-report.txt.
3. Technical implementation plan
Stack: Chrome Manifest V3, vanilla JS bundled with esbuild, Papa Parse, chrome.storage.local, Lemon Squeezy License API, Cloudflare Pages, chrome.downloads.
Plain-language architecture: the content script draws the picker overlay and returns CSS selectors for clicked elements. The service worker owns the loop — it re-injects the collector per page, reads rows, finds the next control, and stops on a repeated URL, a missing control or the page cap. The popup holds the mapping table, runs validation and writes the CSV. License state is checked once per session against Lemon Squeezy and cached; a lapsed key degrades to a 20-row export instead of a hard failure.
Build order: MV3 skeleton and message bus, picker overlay, recipe persistence by hostname, single-page collection, pagination with stop conditions, mapping table, CSV write and validator, license activation, landing page and walkthrough.
The hardest technical risk is pagination on supplier sites using infinite scroll, hashed class names, or a next-link that changes shape per page. Mitigation: let the user click the next control during recipe creation rather than guessing it, and ship a capture-current-page-only fallback so a failed loop still produces a partial file rather than nothing.
AI is optional and cost-capped: one serverless call may suggest which Shopify column an ambiguous field label maps to, on user request only. Validation and CSV generation stay deterministic.
4. Pricing and monetization
Two one-time tiers. Starter $149: one catalog up to 300 SKUs, one saved recipe, CSV export, validation report. Pro $349: five catalogs up to 1,500 SKUs, unlimited recipes, a re-run diff of changed prices and new SKUs, and setup email support. One-time pricing matches a project-shaped purchase and removes the subscription objection on day one; the repeat path is additional catalogs, the re-run diff and a repeat-run pass, not a monthly charge.
The first offer is free and is the whole acquisition engine: send three supplier URLs, receive a Shopify-ready CSV within 24 hours plus the rows a manual sheet would have broken. The license is offered only after the file lands, with SKU count and capture time quoted back.
Expected first-purchase value is $149, with a $349 upside when a buyer names a second supplier in the same conversation. Revenue grows through Pro upgrades, a repeat-run pass for quarterly re-syncs, and referrals.
5. First-customer acquisition
One channel: replying to existing threads where store owners ask how to import a supplier catalog. No ads, no SEO ramp, no partnerships.
Places: r/shopify, r/ecommerce, r/dropship, Shopify Community forums, the WooCommerce support forum, two or three small ecommerce Discords, and public posts announcing a new supplier.
Actions: search each community weekly on 'import supplier catalog', 'CSV import', 'new supplier', 'migrating products'; reply with a genuine short answer plus the free-three-URLs offer; deliver within 24 hours; send the $149 Starter offer with SKU count and time saved attached; follow up once after five days with the validation report.
Message: 'Saw your post about the new supplier. Two to five days of copy-paste is normal and Shopify still rejects half the rows. Send me up to three supplier URLs — I'll send back a Shopify-ready CSV and the validation report within 24 hours, free. If it's useful, the extension that produced it is $149 and you run the rest yourself.'
Week-one goal: extension live and taking payment, 30 threads answered, 10 free catalogs delivered, first paid license attempted.
6. 30-day execution roadmap
Week 1 (days 1-5 build, 6-7 launch): extension to sellable v1 by day 5 with license activation live, landing page and docs published, 40-thread outreach sheet built with subreddit rules noted, 10 replies live on day 7.
Week 2 (days 8-14): deliver every free CSV within 24 hours, convert to $149, fix the top supplier-site failure, publish refund policy and a sample validation report, follow up all recipients; first sale targeted day 12; re-run diff shipped by day 13.
Week 3 (days 15-21): add a second and third channel, publish three starter recipes, pitch Pro at $349, instrument capture time per delivery, ask each buyer for one referral.
Week 4 (days 22-28): cut refund surface with a pre-purchase sample CSV, publish one indexable how-to page, 15 touches per day, add a $79 repeat-run pass, publish redacted before/after proof above the fold.
Days 29-30: final 20-thread push, reconcile every payment in the TrustMRR-connected account, write the post-mortem.
7. Revenue and profit scenarios
Projections only. Conservative: 4 licenses at $149 ARPU, about $596 gross. Base: 14 licenses at a $189 blended ARPU, about $2,646 gross. Upside: 30 licenses at a $199 blended ARPU, about $5,970 gross. Fees assume Lemon Squeezy merchant-of-record at 5% + $0.50 per transaction, roughly 5.5% effective. No paid marketing in the conservative or base cases; $200 of sponsored posts in the upside. Hackathon profit deducts refunds, chargebacks, processing fees and paid spend; business profit additionally deducts hosting, domain and tooling. Operating costs stay low because capture runs in the buyer's browser and there is no scraping fleet.
8. Risks and validation experiments
Recipe breakage on login walls and client-side rendering: mitigate with the user-picked next control and page-only fallback; validate on three real supplier catalogs in the first 48 hours; narrow the pitch if two of five domains fail.
Shopify variant edge cases producing rejected rows and refunds: mitigate with the validator plus a pre-purchase sample file; validate by importing one generated CSV into a development store before selling.
Subreddit self-promotion rules removing offers: mitigate by answering first and keeping two more channels live by day 15; validate by logging removals across the first 10 replies.
Supplier terms prohibiting automated capture: mitigate by capturing only in the buyer's authenticated session with nothing stored server-side; validate by reading the terms of the three most common supplier domains.
Conversion below 25%: validate after 10 free deliveries; if under 10%, test a $49 paid single-catalog conversion before abandoning the wedge.
9. First 24 hours
Hours 1-2: repo, MV3 skeleton loading unpacked, Lemon Squeezy products drafted. Hours 3-5: click-to-pick overlay returning selectors. Hours 6-8: recipe persistence and replay. Hours 9-12: single-page collection and the first real CSV from a public supplier catalog. Hours 13-16: 20-thread outreach sheet with rules noted and the free-three-URLs message drafted. Hours 17-20: landing hero and docs stub live on Cloudflare Pages.
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 →VendorQ Pack
Turns a company's past completed security questionnaires plus its SOC 2 and policy documents into a filled-in, source-cited answer spreadsheet for the new vendor security questionnaire that is currently blocking a deal.
ReviewReady Packet
Generates a reviewer-ready Meta App Review submission bundle — per-permission justifications, screencast script, test-account steps and deauth code — for solo devs and small agencies stuck at 'rejected'.
Chargeback Brief
Chargeback Brief turns a Stripe or Shopify Payments dispute into a bank-ready evidence packet — cover letter, delivery timeline and exhibit index — in under ten minutes for Shopify stores that currently lose disputes by missing the response deadline.