Score C · 5.87/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 15, 2026

ShelfPair Cross-Sell Maps

Turns a Shopify store's public catalog into a ready-to-import 'You May Also Like' and 'Frequently Bought Together' pair map for stores that have no order history for Shopify's native recommender to learn from.

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.

Speculative5.87/10
MVP build (solo)
5 days
Launch price
$199
Sales to $1,000 revenue
6 customers
First paying customer
Personalized preview links sent by direct DM or email, each containing a page built from the prospect's own public catalog.
Who pays

Founder-operator of a single-person Shopify DTC store with roughly 80-1,500 SKUs (fashion, home, beauty, hobby) in the US, UK, EU or India, who just launched a collection or opened a new store and sees empty recommendation blocks.

Biggest execution risk

Market demand 3.6/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; 6 sales at $199 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.4/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.

0/10
Entry price
$199
Solo build
5 days
30d base revenue
$2,290
30d hackathon profit
$2,194
Section 1 of 8

Product opportunity and positioning

Target customer

Founder-operator of a single-person Shopify DTC store with roughly 80-1,500 SKUs (fashion, home, beauty, hobby) in the US, UK, EU or India, who just launched a collection or opened a new store and sees empty recommendation blocks.

Why now

Shopify's behavioral recommender is a cold-start dead end for the long tail of new, single-founder stores, and those founders are reachable directly today with a preview built from their own catalog.

Problem

Native Shopify recommendations render blank on new catalogs, manual pairing of hundreds of SKUs is days of clicking, and bundle apps still require the merchant to decide which products go together.

Solution

Merchant submits a store URL; ShelfPair reads public products.json, tags each product from image and copy, scores candidate pairs under hard rules, and returns a CSV in Search & Discovery manual-recommendation format plus Frequently Bought Together trios.

Differentiation · A one-time file the merchant owns and imports in minutes, shown paired from their own catalog before payment, instead of a monthly storefront widget requiring install, trust and cancellation.

1. Product opportunity and positioning

A solo Shopify founder launches a collection, switches on You may also like in Search & Discovery, and the block renders nothing. Shopify's behavioral recommender needs order history the store does not have. The merchant already believes cross-sells lift AOV; what is missing is the pair data. At 80 to 1,500 SKUs, pairing by hand is days of clicking, and bundle apps still ask the merchant to decide which products go together.

ShelfPair sells the finished pair list. The merchant submits a store URL. ShelfPair reads the public products.json, tags every product from its image and copy, scores every candidate pair under hard rules, and returns a PairMap: a CSV in Search & Discovery manual-recommendation format plus a trio list for Frequently Bought Together, with same-variant, same-category and out-of-stock pairs removed.

The difference is the shape of the transaction, not the algorithm. Not a theme widget, not a monthly app the merchant must install, trust and cancel - a file the merchant owns, imported in minutes. The buyer can be shown their own catalog, already paired, before paying. No OAuth, no App Store review, no data history, no procurement cycle. JEV scores this concept 58.7 in band C, hardest on speed to first revenue (8.43) and softest on market demand (3.6): the plan must create demand store by store with personalized previews, and must not assume a self-serve funnel exists.

The wedge is deliberately narrow: one buyer, one trigger (empty recommendation slots on a new or thin catalog), one deliverable, one price. The category already tried to be a personalization platform and commoditized itself. ShelfPair sells the dataset, keeps the artifact simple, and lets the file be judged in a browser tab.

2. Smallest sellable MVP

Sellable on day 5: paste a store URL, get a free preview page at /s/{handle} with five unlocked pairs, pay $199 by Stripe Checkout, receive the full CSV plus an import walkthrough by email within minutes. Everything else - dashboard, theme extension, analytics, attribution - is noise in week one. The preview page is simultaneously the demo and the sales asset, because it is generated from the prospect's own catalog before they have spoken to the founder.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres and generated files, OpenAI text-embedding-3-small for catalog embeddings, gpt-4o-mini vision for attribute tagging, Stripe Checkout, Resend for delivery. Build order: catalog fetcher with pagination and failure handling, tagging and embedding pipeline with per-handle caching, pairing engine with hard rules, trio builder, CSV export in the exact Search & Discovery column format, preview page and checkout, delivery email, then the optional metafield push for the $349 tier.

The hardest risk is not the model, it is the input: products.json is disabled or rate-limited on an unknown share of stores. The fetcher must degrade to a pasted CSV or product-URL list, and that fallback ships in week one, not week three. Tagging cost is controlled by caching per product handle so repeat previews are nearly free.

4. Pricing and monetization

Two one-time tiers: Full PairMap at $199 (top 8 pairs per product, trios, Search & Discovery CSV, walkthrough) and PairMap + Push at $349 (same plus metafield write through a merchant-supplied Admin API token and one re-run within 30 days). One-time pricing is correct because the artifact is a file and the trigger is an event; a subscription on a static file invites churn and refunds. Repeat revenue comes from re-runs after catalog changes and from new collections, not from a monthly fee.

5. First-customer acquisition

One channel: personalized preview links. Build a list of 300 single-founder Shopify stores from X, Instagram and TikTok launch posts, r/shopify threads and new-store announcements, generate each store's preview from its public catalog, then send three lines linking to their own URL. Follow up once at 72 hours with one swapped-in pair and a 48-hour code. Every buyer is asked for one referral store, which becomes the next preview. No paid ads in weeks one and two, because the message only works when it contains the recipient's own products.

6. 30-day execution roadmap

Days 1-5 build the sold artifact: fetcher, tagging, pairing, export, preview and checkout, with the MVP live on day 5. Days 6-10 instrument outreach: 60 stores on the sheet, 10 previews published, 50 messages sent, funnel counted from preview view to checkout. Day 11 is the first-sale target: follow-up round one with a discount code. Days 12-21 add the $349 tier, the CSV-upload fallback for blocked catalogs, the re-run button, a support video, and a public build thread with one store's before and after. Days 22-30 are volume and cleanup: 90 more previews, referral loop, second follow-ups, support FAQ, a proactive refund sweep, and reconciliation of every dollar in TrustMRR before December 16.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 buyers at $199, $597 collected, hackathon profit $572. Base: 10 buyers at a blended $229 (8 at $199, 2 at $349), $2,290 collected, hackathon profit $2,194 and business profit $2,134 after $60 of hosting, tooling and API cost. Upside: 25 buyers at the same blended $229, $5,725 collected, one $199 refund, $240 in processing fees, $150 of paid promotion, business profit $5,016. None reaches the $100K target. The wedge is worth running because it produces cash, a real buyer list and a repeat-purchase path, and because the engine that makes 25 maps can make 250.

8. Risks and validation experiments

Pair quality is the top risk: plausible but wrong pairs cause refunds inside a tight-knit founder community. Test it by having ten previewed founders grade five pairs each before scaling outreach; if more than 30 percent are marked wrong, the rules engine is broken and outreach pauses. Availability of products.json is second: run the fetcher against 100 candidate stores and record failures; if more than 40 percent are blocked and the CSV fallback does not convert, channel economics change. Third is the do-it-with-ChatGPT objection: split the first 100 messages between a file offer and an offer of the prompt itself, and treat a reply rate under 3 percent as a signal that the pitch, not the list, is wrong. Fourth, a refund wave: track bad-pair reports per store and refund proactively at day 29 rather than argue.

9. First 24-hour action plan

Connect Stripe to TrustMRR and deploy an empty Next.js app (hours 1-3). Get the products.json fetcher storing raw catalogs for three real stores (hours 4-7). Produce and hand-review candidate pairs for one store (hours 8-11). Build a 40-store prospect sheet with founder handles and SKU counts (hours 12-15). Ship a rough preview page and send five personalized links (hours 16-20). The day-one deliverable is not code, it is five messages containing five real catalogs.

Section 2 of 8

Smallest sellable MVP

A store-URL intake that generates a public 5-pair preview page, a Stripe Checkout for $199, and automatic email delivery of the full Search & Discovery CSV with an import walkthrough.

Must-have features

  • Public products.json fetcher with pagination to 1,000 SKUs
  • Vision plus text attribute tagging per product
  • Pairing engine with hard rules excluding same-variant, same-category, out-of-stock and off-price-band pairs
  • Top 8 pairs per product and Frequently Bought Together trios
  • CSV export in Search & Discovery manual-recommendation column format
  • Free preview page at /s/{handle} with 5 unlocked pairs
  • Stripe Checkout for $199 and $349
  • Email delivery of file plus 6-step import walkthrough

Explicitly out of scope

  • Storefront JavaScript widget or theme app extension
  • Real-time per-visitor personalization
  • Image generation or lifestyle composites
  • Klaviyo or Meta Ads integration
  • Shopify App Store listing or OAuth review
  • Analytics dashboard, revenue attribution or A/B testing

Demo flow (what the buyer sees)

  1. Prospect store URL is pasted or pulled from the outreach sheet
  2. Fetcher stores the catalog and tags every product
  3. Pairing engine scores pairs and builds trios
  4. Preview page publishes with 5 unlocked pairs
  5. Founder opens their own preview URL from a DM
  6. Merchant pays via Stripe Checkout
  7. CSV is generated, stored and emailed with the walkthrough
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres and storageOpenAI text-embedding-3-smallOpenAI gpt-4o-mini visionStripe CheckoutResendShopify public products.json endpointOptional Shopify Admin API metafield write

Architecture

A job queue fetches products.json per store, stores raw products in Supabase, tags each product once via vision and text models, and caches tags by product handle. Embeddings are computed per product and stored as vectors. The pairing engine runs similarity scoring plus hard rules in a single pass over candidates and writes pairs and trios to Postgres. The preview page reads the first five pairs from Postgres; Stripe Checkout flips the order to paid; a delivery worker renders the full CSV to storage and emails a signed link. The optional metafield push reuses the same pair rows and writes them through a merchant-supplied token with a dry-run view first.

Build steps

  1. Scaffold Next.js app, Supabase project and Stripe account, connect Stripe to TrustMRR
  2. Implement products.json fetcher with pagination, timeouts and failure logging
  3. Add tagging pipeline with per-handle cache and cost logging
  4. Add embedding generation and vector storage
  5. Implement pair scoring with hard-rule filters and price-band window
  6. Build trio builder from two strongest pairs sharing a hub product
  7. Implement CSV exporter matching Search & Discovery columns exactly
  8. Build /s/{handle} preview page with 5 unlocked pairs
  9. Wire Stripe Checkout for both tiers and a webhook that marks orders paid
  10. Build delivery worker: CSV to storage, Resend email with walkthrough
  11. Add bad-pair report link and refund handling note
  12. Add CSV or product-URL upload fallback for blocked catalogs
  13. Add re-run endpoint and catalog change detection
  14. Add metafield push with dry-run for the $349 tier

AI components

  • gpt-4o-mini vision tags each product image with category, color, material, use-case and style
  • text-embedding-3-small produces the vectors used for candidate pair similarity
  • Optional LLM pass condenses product copy into short attribute hints when images are weak
Hardest technical risk: Public products.json being disabled or rate-limited on a meaningful share of target stores, which breaks the preview-before-payment loop that the whole channel depends on.
Section 3 of 8

Pricing and monetization

Full PairMap

Entry offer
$199 one-time

For Single-founder store with 80-1,500 SKUs and empty recommendation slots

  • Top 8 You May Also Like pairs per product
  • Frequently Bought Together trios
  • Search & Discovery format CSV
  • Import walkthrough email

PairMap + Push

$349 one-time

For Merchant who does not want to import anything manually

  • Everything in Full PairMap
  • Metafield push via merchant-supplied Admin API token
  • One free re-run within 30 days

Model: Two one-time purchases - a $199 CSV pair map and a $349 pair map with a direct metafield push and one re-run.

First revenue offer: Generate the prospect's own 5-pair preview page and send it with: your recommendation blocks are empty because you have no order history yet - here are 5 pairs from your catalog, the full map is $199.

Expected ACV: $199

Upsell path: Upgrade Full PairMap buyers to the $349 push tier when they ask about importing, then sell paid re-runs after each catalog or collection change, and convert referral stores into new maps.

Target customers
50
Revenue model
$9,950
Costs
$150
Profit model
$9,800
Section 4 of 8

First-customer acquisition

Primary channel

Personalized preview links sent by direct DM or email, each containing a page built from the prospect's own public catalog.

Where to find them

  • X and Twitter posts announcing a new Shopify store or collection
  • Instagram and TikTok launch posts from founder-run DTC brands
  • r/shopify threads asking why You may also like shows nothing
  • Reddit r/ecommerce and r/Entrepreneur store-review requests
  • Shopify Community forum posts about Search & Discovery recommendations
  • Indie Hackers and founder Slack groups with Shopify store links
  • Buyers of Full PairMap naming one referral store each

Exact outreach motions

  • Generate the preview page first, then DM the founder the URL with one line about empty recommendation blocks
  • Email the founder address on the store's contact page when no social handle exists
  • Follow up at 72 hours with one swapped-in pair and a 48-hour $30-off code
  • Post a public before-and-after of one store's paired product page
  • Ask every buyer for one store name and generate that store's preview the same day

Message template

Hi {first_name} - your Shopify store's You may also like slots are empty because there is no order history for Shopify to learn from yet. I ran your {sku_count} products through ShelfPair and paired them: {preview_url} shows 5 of them. The full map is 8 pairs per product plus Frequently Bought Together trios, delivered as a Search & Discovery CSV you import in about 10 minutes - $199 one time. Want the full file?
Week-one goal: 60 stores on the prospect sheet, 10 preview pages published, 50 personalized messages sent, first reply booked.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 1130 days planned
Week 1 · Build & validate · 7 days
Day 1Foundation

Payment and deploy

  • Create Next.js repo and deploy to Vercel
  • Set up Supabase project with products and pairs tables
  • Connect Stripe to TrustMRR before any customer exists

Deliverable: Live skeleton on a custom domain with a working payment account

Day 2Catalog intake

Fetcher

  • Build products.json fetcher with pagination to 1,000 SKUs
  • Store title, price, tags, variants and image URLs
  • Log HTTP status and timeouts per store

Deliverable: Fetcher returning full catalogs for 3 real stores

Day 3Tagging

Attributes and vectors

  • Write vision prompt returning category, color, material, use-case, style
  • Batch embeddings with text-embedding-3-small
  • Cache tags per product handle to control cost

Deliverable: Tagged catalog with per-store API cost logged

Day 4Pairing

Scoring and rules

  • Score pairs with cosine similarity plus hard rules
  • Add price-band window plus same-variant and same-category exclusions
  • Build trios from two strongest pairs on a hub product

Deliverable: Top 8 pairs per product for one real catalog

Day 5Sell itMVP shipped

MVP live

  • Ship /s/{handle} preview with 5 unlocked pairs
  • Wire Stripe Checkout for $199 and $349
  • Send CSV and walkthrough via Resend on payment

Deliverable: MVP live: URL in, paid CSV out

Day 6Quality pass

Import correctness

  • Hand-review 200 pairs across 3 stores
  • Match Search & Discovery CSV columns exactly
  • Add a report-a-bad-pair link

Deliverable: Import-tested CSV on a real store

Day 7List building

Prospects

  • Collect 60 single-founder stores from X, Instagram and r/shopify
  • Record founder handle, store URL and SKU count
  • Generate and publish 10 previews

Deliverable: 60-store outreach sheet and 10 live preview URLs

Week 2 · Launch & first sale · 7 days
Day 8Outreach A

First 25 messages

  • Send 25 personalized DMs and emails with preview links
  • Ask one question: are your recommendation blocks empty?

Deliverable: 25 messages sent with reply tracking started

Day 9Outreach B

Second 25 messages

  • Send 25 more with a different subject line
  • Instrument preview view to checkout funnel

Deliverable: 50 total messages and a funnel counter

Day 10Feedback loop

Pair grading

  • Ask 10 non-buyers to grade 5 pairs each
  • Tune rules on the worst-graded pairs

Deliverable: Grading sheet with 50 rated pairs

Day 11First sale pushFirst sale target

Convert

  • Follow up round one at 72h with a swapped-in pair
  • Attach a 48-hour $30-off code on Full PairMap

Deliverable: First paying customer with file delivered in minutes

Day 12Public proof

Build thread

  • Post a build thread with one store's before and after
  • Ask the first buyer for one referral store

Deliverable: Public post live and one referral preview generated

Day 13Tier 2

Metafield push

  • Build metafield push using merchant-supplied Admin API token
  • Add dry-run view showing pairs before any write

Deliverable: PairMap + Push sellable at $349

Day 14Week 2 review

Decide

  • Compute preview to sale rate
  • Choose message angle from reply data

Deliverable: Written decision on pitch and list quality

Week 3 · Repeat & systematize · 7 days
Day 15Re-run

Repeat value

  • Add re-run button and catalog change detection
  • Email past buyers about the re-run option

Deliverable: Re-run working end to end

Day 16Outreach C

New stores

  • Add 60 new stores to the sheet
  • Generate and send 30 previews

Deliverable: 30 new personalized messages sent

Day 17Communities

Answer in public

  • Answer 5 r/shopify threads about empty recommendations
  • Post the import walkthrough in 2 founder groups

Deliverable: Community answers with preview tool linked

Day 18Quality tuning

Rules v2

  • Re-tune price and color matching on 5 real catalogs
  • Remove any pair class with the highest error rate

Deliverable: Rules v2 scoring better on the grading sheet

Day 19Video

Reduce support

  • Record a 2-minute Search & Discovery import walkthrough
  • Embed the video in the delivery email

Deliverable: Support video live and email updated

Day 20Checkout polish

Proof on page

  • Show SKU count and pair count on the preview page
  • Add a 3-question FAQ under the pay button

Deliverable: Preview page with pair-count proof and FAQ

Day 21Week 3 review

Books

  • Reconcile Stripe against TrustMRR
  • List every refund and bad-pair report

Deliverable: Revenue and refund ledger

Week 4 · Scale what works · 6 days
Day 22Outreach D

International

  • Target 60 UK, EU and India stores for time-zone coverage
  • Send 30 previews with a local pricing note

Deliverable: 30 international messages sent

Day 23Fallback

Blocked catalogs

  • Ship CSV or product-URL upload for blocked catalogs
  • Count how many prospects needed the fallback

Deliverable: Fallback path live and measured

Day 24Automation

Delivery

  • Cron the delivery email and 30-day re-run reminder
  • Log every failed delivery for retry

Deliverable: Delivery no longer manual

Day 25Referral loop

Compounding

  • Ask all buyers for one store name
  • Generate and send that store's preview the same day

Deliverable: Referral previews sent within 24 hours

Day 26Support

Self-serve

  • Answer the top 3 repeated questions in the FAQ
  • Add a re-download link for lost files

Deliverable: Self-serve answers covering most tickets

Day 27Final outreach

Close the list

  • Send 30 final previews to untouched stores
  • Follow up every warm reply

Deliverable: Outreach closed at roughly 300 stores

Days 29-30 · Consolidate · 3 days
Day 28Chase

Pending money

  • Email everyone who viewed but did not check out
  • Confirm all money landed in TrustMRR

Deliverable: Every pending checkout contacted

Day 29Cleanup

Refunds

  • Proactively refund any buyer with an unusable map
  • Confirm no chargebacks are pending

Deliverable: Refund sweep done and books clean

Day 30Close

Decide next step

  • Publish a short results post with real numbers only
  • Decide the post-hackathon re-run offer

Deliverable: Final results report and a written next-step decision

Section 6 of 8

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

  • Base and Upside use a blended ARPU of $229, implying 8 buyers at $199 and 2 at $349 per 10 buyers; Conservative assumes $199 only.
  • Payment fees modeled at roughly 4.2% of collected revenue (Stripe 2.9% + $0.30 plus international card surcharge).
  • Ad spend is $0 in Conservative and Base because the channel is organic personalized DMs and email; Upside includes $150 of paid promotion.
  • Conservative: 3 buyers from about 120 previews (2.5% close). Base: 10 from about 300 (3.3%). Upside: 25 from about 600 (4.2%). These close rates are hypotheses, not measured.
  • Operating costs cover Vercel, Supabase, Resend and OpenAI vision and embedding calls; they scale with previews generated for non-buyers too, not only with buyers.
  • Only Upside models a refund, one $199 map, because pair quality at volume is unproven.
  • No scenario in this wedge reaches the $100K target in 30 days; the goal is a repeatable loop and a repeat-purchase path.
  • All figures are projections derived from stated assumptions and must not be read as verified revenue or traction.

Conservative

3 customers
$597
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$25
Paid marketing
$0
Hackathon profit
$572
Operating costs
$25
Business profit
$547

Base case

10 customers
$2,290
collected revenue · avg payment $229
Refunds
$0
Chargebacks
$0
Payment fees
$96
Paid marketing
$0
Hackathon profit
$2,194
Operating costs
$60
Business profit
$2,134

Optimistic

25 customers
$5,725
collected revenue · avg payment $229
Refunds
$199
Chargebacks
$0
Payment fees
$240
Paid marketing
$150
Hackathon profit
$5,136
Operating costs
$120
Business profit
$5,016

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,990
Payment fees (3.9%)
$78
Paid marketing
$0
Hackathon profit
$1,912
Business profit
$1,852

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.

Section 7 of 8

Main risks and validation experiments

Risk 1Generated pairs look plausible but wrong to a domain expert, producing refunds and reputational damage in small merchant communities.

Mitigation

Hard rules plus a report-a-bad-pair link on every delivery, and a proactive refund sweep on day 29.

Validation experiment

Ask 10 previewed founders to grade 5 pairs each before scaling outreach past 100 messages.

Kill criteria

If more than 30 percent of 50 graded pairs are marked wrong across 10 stores, pause outreach and rebuild the rules engine.

Risk 2Public products.json is disabled or rate-limited on enough stores to break the preview loop.

Mitigation

Ship a CSV or product-URL upload fallback in week three and count how often it is needed.

Validation experiment

Run the fetcher against 100 candidate store URLs and record the failure rate by store platform and size.

Kill criteria

If more than 40 percent of stores fail and the fallback converts under 2 percent, change the acquisition channel.

Risk 3Merchants reply that they can do this with ChatGPT in an hour, collapsing willingness to pay.

Mitigation

Lead with the finished file and the import walkthrough, not the prompt, and show pair count and SKU count on the preview page.

Validation experiment

Split the first 100 messages between a file offer and a prompt offer and compare reply rates.

Kill criteria

If reply rate stays under 3 percent after 200 messages and no buyer completes checkout, reposition or stop.

Risk 4Cold DM and email deliverability caps how many previews are actually seen.

Mitigation

Use the store contact address and the founder's public handle, and keep messages to three lines with no attachments.

Validation experiment

Track preview page views against messages sent each day for the first five sending days.

Kill criteria

If preview views stay under 10 percent of messages sent after 150 sends, change the delivery path to community posts.

Risk 5A refund wave inside a tight-knit founder community stalls the only acquisition channel.

Mitigation

Refund without argument, keep the refund rate visible in the ledger, and never sell a map rated badly by the merchant.

Validation experiment

Reconcile refunds against bad-pair reports weekly and compare which pair classes drove them.

Kill criteria

If refunds exceed 20 percent of collected revenue at any point, stop selling until pair quality is fixed.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-3

  • Create Stripe account and connect it to TrustMRR
  • Deploy an empty Next.js app to Vercel on a bought domain

Output: Live payment account with no customers plus a deployed skeleton

Hours 4-7

  • Write products.json fetcher with pagination
  • Run it against 3 real candidate stores and store the raw output

Output: Raw catalogs stored for 3 stores with HTTP status logged

Hours 8-11

  • Draft the vision tagging prompt and run it on one catalog
  • Hand-review 20 candidate pairs for obvious errors

Output: A short list of what the rules engine must exclude

Hours 12-15

  • Build a 40-store prospect sheet
  • Record founder handle, store URL, SKU count and reachability

Output: 40-row prospect sheet ready for preview generation

Hours 16-20

  • Ship a rough /s/{handle} preview page for one store
  • Send 5 personalized DMs or emails containing that URL

Output: 5 messages sent with live preview links, reply tracking started

Complete report

Full 30-day launch report

Read the full generated report

1. Product opportunity and positioning

A solo Shopify founder launches a collection, switches on You may also like in Search & Discovery, and the block renders nothing. Shopify's behavioral recommender needs order history the store does not have. The merchant already believes cross-sells lift AOV; what is missing is the pair data. At 80 to 1,500 SKUs, pairing by hand is days of clicking, and bundle apps still ask the merchant to decide which products go together.

ShelfPair sells the finished pair list. The merchant submits a store URL. ShelfPair reads the public products.json, tags every product from its image and copy, scores every candidate pair under hard rules, and returns a PairMap: a CSV in Search & Discovery manual-recommendation format plus a trio list for Frequently Bought Together, with same-variant, same-category and out-of-stock pairs removed.

The difference is the shape of the transaction, not the algorithm. Not a theme widget, not a monthly app the merchant must install, trust and cancel - a file the merchant owns, imported in minutes. The buyer can be shown their own catalog, already paired, before paying. No OAuth, no App Store review, no data history, no procurement cycle. JEV scores this concept 58.7 in band C, hardest on speed to first revenue (8.43) and softest on market demand (3.6): the plan must create demand store by store with personalized previews, and must not assume a self-serve funnel exists.

2. Smallest sellable MVP

Sellable on day 5: paste a store URL, get a free preview page at /s/{handle} with five unlocked pairs, pay $199 by Stripe Checkout, receive the full CSV plus an import walkthrough by email within minutes. Everything else - dashboard, theme extension, analytics, attribution - is noise in week one. The preview page is simultaneously the demo and the sales asset, because it is generated from the prospect's own catalog before they have spoken to the founder.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres and generated files, OpenAI text-embedding-3-small for embeddings, gpt-4o-mini vision for tagging, Stripe Checkout, Resend for delivery. Build order: catalog fetcher with pagination and failure handling, tagging with per-handle caching, pair scoring with hard rules, trio builder, CSV export in the exact Search & Discovery columns, preview page, checkout webhook, delivery worker, then the metafield push for the $349 tier.

The hardest risk is not the model, it is the input: products.json is disabled or rate-limited on an unknown share of stores. The fetcher degrades to a pasted CSV or product-URL list, and that fallback ships in week one. Tagging cost is controlled by caching per product handle so repeat previews are nearly free.

4. Pricing and monetization

Two one-time tiers: Full PairMap at $199 (top 8 pairs per product, trios, Search & Discovery CSV, walkthrough) and PairMap + Push at $349 (same plus metafield write through a merchant-supplied Admin API token and one re-run within 30 days). One-time is correct because the artifact is a file and the trigger is an event; a subscription on a static file invites churn and refunds. Repeat revenue comes from re-runs after catalog changes and from new collections, not from a monthly fee.

5. First-customer acquisition

One channel: personalized preview links. Build a list of 300 single-founder Shopify stores from X, Instagram and TikTok launch posts, r/shopify threads and new-store announcements, generate each store's preview from its public catalog, then send three lines linking to their own URL. Follow up once at 72 hours with one swapped-in pair and a 48-hour code. Every buyer is asked for one referral store, which becomes the next preview. No paid ads in weeks one and two, because the message only works when it contains the recipient's own products.

6. 30-day execution roadmap

Days 1-5 build the sold artifact: fetcher, tagging, pairing, export, preview and checkout, with the MVP live on day 5. Days 6-10 instrument outreach: 60 stores on the sheet, 10 previews published, 50 messages sent, funnel counted from preview view to checkout. Day 11 is the first-sale target: follow-up round one with a discount code. Days 12-21 add the $349 tier, the CSV-upload fallback, the re-run button, a support video and a public build thread with one store's before and after. Days 22-30 are volume and cleanup: 90 more previews, referral loop, second follow-ups, support FAQ, a proactive refund sweep, and reconciliation of every dollar in TrustMRR before December 16.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 buyers at $199, $597 collected, hackathon profit $572. Base: 10 buyers at a blended $229 (8 at $199, 2 at $349), $2,290 collected, hackathon profit $2,194 and business profit $2,134 after $60 of hosting, tooling and API cost. Upside: 25 buyers at the same blended $229, $5,725 collected, one $199 refund, $240 in processing fees, $150 of paid promotion, business profit $5,016. None reaches the $100K target. The wedge is worth running because it produces cash, a real buyer list and a repeat-purchase path, and because the engine that makes 25 maps can make 250.

8. Risks and validation experiments

The top risk is pair quality: plausible but wrong pairs cause refunds inside a tight-knit founder community. Test it by having ten previewed founders grade five pairs each before scaling outreach; if more than 30 percent are wrong across ten stores, outreach pauses. Availability of products.json is second: run the fetcher against 100 candidate stores and record failures; if more than 40 percent are blocked and CSV fallback does not convert, channel economics change. Third is the do-it-with-ChatGPT objection: split the first 100 messages between a file offer and a prompt offer, and treat a reply rate under 3 percent after 200 sends as a signal that the pitch is wrong. Fourth, deliverability: track preview views against messages sent. Fifth, a refund wave: track bad-pair reports weekly and refund proactively on day 29 instead of arguing.

9. First 24-hour action plan

Connect Stripe to TrustMRR and deploy an empty Next.js app (hours 1-3). Get the products.json fetcher storing raw catalogs for three real stores (hours 4-7). Produce and hand-review candidate pairs for one store (hours 8-11). Build a 40-store prospect sheet with founder handles and SKU counts (hours 12-15). Ship a rough preview page and send five personalized links (hours 16-20). The day-one deliverable is not code, it is five messages containing five real catalogs.

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 →