Score B · 6.57/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 16, 2026

ZonaCard

A shareable link that tells customers if you deliver to their neighborhood and sends the order straight to WhatsApp.

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.

Promising6.57/10
MVP build (solo)
3 days
Launch price
$39 · monthly
Sales to $1,000 revenue
26 customers
First paying customer
Instagram direct message to Brazil-based food businesses that mention delivery in their bio or captions but publish no zone or fee information.
Who pays

Owner-operated food businesses in Brazil or Mexico (home bakers, marmita/lunch delivery, small restaurants) with 1-5 employees that sell via WhatsApp and Instagram, deliver locally, and have no published zone or fee information.

Biggest execution risk

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 3 days; the plan targets a first sale on day 12; 26 sales at $39 clears $1,000 of collected revenue; strongest signal is solo build feasibility at 8.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.

0/15
Entry price
$39
Solo build
3 days
30d base revenue
$390
30d hackathon profit
$370
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operated food businesses in Brazil or Mexico (home bakers, marmita/lunch delivery, small restaurants) with 1-5 employees that sell via WhatsApp and Instagram, deliver locally, and have no published zone or fee information.

Why now

The buyer already sells on WhatsApp, already publishes a phone number, and can be reached by direct message today - no marketplace traffic, SEO ramp, ads budget or integration is required to prove value.

Problem

The owner re-types the same delivery answer dozens of times a day, answers inconsistently, and loses orders when customers stop replying before they learn the fee.

Solution

The owner adds neighborhoods and fees in a dashboard, gets a short link and QR code, and customers pick their neighborhood on a mobile page that shows fee and time and opens WhatsApp with a pre-filled order message.

Differentiation · A Google Business Profile or Instagram caption states delivery vaguely; ZonaCard answers the specific question, prices it, and routes a qualified order into the chat the owner already runs.

1. Product opportunity and positioning

ZonaCard converts the most repeated message in a small food business into a link. An owner-operated confeitaria, marmita kitchen or 1-5 person restaurant posts "fazemos entrega" on Instagram, then spends the day answering "voce entrega no meu bairro? quanto e?" in WhatsApp. Answers drift, replies lag, and some customers give up before ordering.

ZonaCard is not a marketplace and not a website builder. The owner enters neighborhoods and fees once; the product returns a short link, a QR code and a public mobile page. A customer picks a neighborhood, sees fee and estimated time, and taps "Pedir no WhatsApp", which opens a chat with a pre-filled message naming the neighborhood and the fee. The owner receives an order that is already qualified.

One-line position: the delivery-zone answer you send instead of typing it again.

JEV scored this concept 65.7/100 (band B). It is strongest on speed to first revenue (8.21/10) and solo build feasibility (8.89/10), weakest on market demand (4.38/10). That shape dictates the plan: do not spend 30 days polishing software. Ship a usable card by day 5 and spend the remaining 25 days proving owners will pay $39/month instead of living with a free workaround. Demand is the open question; everything else here is cheap to execute.

The buyer is reachable without a cold-start. They already publish a WhatsApp number on Instagram and already answer this question daily. The acquisition channel is a direct message containing a working sample card built from their own city's neighborhood names, so the reply is not "what is this" but "how much".

The wedge is deliberately narrow because breadth is what killed the directory model this concept descends from. A directory needs both sides to show up; a zone card needs one owner and one link. Value is proven inside the owner's existing WhatsApp audience on day one of use, with no platform traffic to bootstrap and no buyer-side accounts to create.

What ZonaCard refuses to become in these 30 days: no payments, no order management, no delivery tracking, no photo-to-catalog AI, no maps. Each of those adds surface area without adding a single reason for a baker to send $39 this week.

Section 2 of 8

Smallest sellable MVP

A magic-link dashboard where an owner enters business name, WhatsApp number, neighborhoods and fees, producing a public mobile card page plus a QR code, with a WhatsApp button that pre-fills neighborhood and fee.

Must-have features

  • Magic-link or email/password auth
  • Dashboard CRUD for neighborhoods, fees and estimated delivery time
  • Business name and WhatsApp number settings
  • Public mobile-first card page with neighborhood dropdown
  • WhatsApp click-to-chat URL with pre-filled message including neighborhood and fee
  • QR code generation for the card link
  • View and WhatsApp-click counters per account

Explicitly out of scope

  • No online payments or checkout
  • No map drawing or geocoding
  • No delivery tracking or driver assignment
  • No customer accounts or order history
  • No POS, ERP or Instagram API integrations
  • No AI or photo processing in v1
  • No custom domains or white-label

Demo flow (what the buyer sees)

  1. Founder opens dashboard and signs up with a magic link.
  2. Owner enters business name, WhatsApp number, five neighborhoods and their fees.
  3. System generates the public card URL and a QR code image.
  4. Customer opens the card on a phone and selects a neighborhood from the dropdown.
  5. Card shows fee and estimated time and reveals the order button.
  6. Customer taps the button; WhatsApp opens with a message naming the business, the neighborhood and the fee.
  7. Owner sees the order arrive and the view and click counters increment.
Build plan

Technical implementation plan

Stack

Next.js (App Router)Vercel hostingSupabase AuthSupabase Postgres with row-level securityTailwind CSSqrcode.reactStripe Checkout payment linksPlausible or a simple Postgres event counter

Architecture

A single Next.js app serves two surfaces: an authenticated dashboard at /app and a public card at /c/[slug]. Supabase stores accounts, zones and events with RLS so each owner reads only their rows. The public card is a server-rendered page that loads zones for the slug, renders a dropdown client-side, and builds a wa.me URL from the stored WhatsApp number plus a URL-encoded message. Views and clicks are inserted as rows in an events table; totals are read with a single aggregate query. Billing is a Stripe payment link, and a webhook flips the account to active.

Build steps

  1. Create Next.js repo, Supabase project and Vercel deployment.
  2. Define tables: accounts, zones, events, subscriptions; enable RLS.
  3. Build magic-link auth and a protected /app shell.
  4. Build zone CRUD: name, fee, estimated minutes, active toggle.
  5. Build the public card page with dropdown and fee/time display.
  6. Generate the wa.me deep link with URL-encoded pre-filled text.
  7. Add QR code rendering on the dashboard.
  8. Add view and click event inserts and a totals panel.
  9. Wire a Stripe payment link plus webhook to activate accounts.
  10. Build the marketing landing page with the $39 offer and one sample card.
  11. Test the card on three phones and two carriers before outreach.

AI components

  • None in v1. Fees and delivery times are owner-entered values; no LLM, vision model or inference cost is involved in delivering the product.
Hardest technical risk: WhatsApp deep links with pre-filled text can be truncated or stripped on some Android WebViews and in-app browsers; the message must stay short and degrade to a plain neighborhood-plus-business string if the platform drops the body.
Section 3 of 8

Pricing and monetization

ZonaCard Pro

Entry offer
$39 / month

For Owner-operated food businesses selling via WhatsApp

  • Public zone card link
  • QR code image
  • Unlimited neighborhoods and fees
  • WhatsApp pre-filled order message
  • View and click counters

ZonaCard Pro - 3-month prepay

$99 one-time

For Owners who ask for a discount after the first month of use

  • Everything in Pro
  • Three months of access
  • Priority setup of up to 20 neighborhoods

Model: Single monthly subscription at $39 per business, billed through a Stripe payment link, with a $19 first-month option used only as a closing concession.

First revenue offer: "I already built your ZonaCard with your city's neighborhoods - here is the link. First month is $19 instead of $39, cancel any time, you keep the QR code."

Expected ACV: $39

Upsell path: Start monthly at $39. At day 25-28, offer active users a 3-month prepay at $99 to pull cash forward, then add printed QR table stickers and a second card for a second location as later paid add-ons.

Target customers
25
Revenue model
$975
Costs
$60
Profit model
$915
Section 4 of 8

First-customer acquisition

Primary channel

Instagram direct message to Brazil-based food businesses that mention delivery in their bio or captions but publish no zone or fee information.

Where to find them

  • Instagram search: confeitaria + Sao Paulo, Belo Horizonte, Curitiba
  • Instagram search: bolo no pote and marmita fit + city name
  • Instagram search: doces artesanais and salgados + city name
  • Accounts with a wa.me link in bio and a post from the last 14 days
  • Accounts with 300-20,000 followers (owner still answers DMs personally)
  • Neighborhood "bazar" and "classificados" WhatsApp and Telegram groups

Exact outreach motions

  • Send 20-25 DMs per day from a warmed account, each naming the business and its city.
  • Attach a live sample card built with five real neighborhoods from that city before sending.
  • Follow up once after 48 hours with a single line and the link again.
  • Offer the $19 first month only after the prospect replies with interest.
  • Post a short Loom walkthrough link in the DM thread when the prospect asks how it works.
  • Ask each paying owner, at day 13, to share the card link in their WhatsApp status.

Message template

Oi! Vi que voces fazem entrega mas nao tem os bairros no perfil. Montei uma ZonaCard pra voces: [link] - o cliente escolhe o bairro, ve a taxa e o pedido ja cai no WhatsApp com o bairro escrito. Quer que eu deixe no ar com o nome de voces? Primeiro mes R$ com desconto.
Week-one goal: 100 DMs sent to qualified accounts, 10 sample cards delivered, 3 payment links issued.
Section 5 of 8

30-day execution roadmap

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

Repo, database and auth

  • Create Next.js repo, Supabase project and Vercel deploy.
  • Define accounts, zones, events and subscriptions tables with RLS.
  • Wire magic-link auth and the protected app shell.

Deliverable: Deployed skeleton with working sign-in.

Day 2Core data

Zone CRUD and business settings

  • Build zone create/edit/deactivate forms.
  • Add business name, WhatsApp number and slug settings.
  • Seed one test account with five real neighborhoods.

Deliverable: Working dashboard that saves zones.

Day 3Public artifact

The customer-facing card

  • Build /c/[slug] mobile page with neighborhood dropdown.
  • Show fee and estimated time on selection.
  • Generate wa.me link with neighbourhood and fee pre-filled.

Deliverable: Live card page that opens a pre-filled WhatsApp chat.

Day 4Shareability

QR code, counters and landing page

  • Add QR code rendering to the dashboard.
  • Record view and click events and show totals.
  • Publish landing page with the $39 offer and one demo card.

Deliverable: Shareable card, QR, counts and a public landing page.

Day 5Money pathMVP shipped

Checkout and MVP freeze

  • Create Stripe payment link and webhook to activate accounts.
  • Test end-to-end purchase with a real card.
  • Freeze MVP scope; no new features after today.

Deliverable: Paid, activating checkout; MVP frozen.

Day 6Ammunition

Sample cards and proof video

  • Build 10 sample cards for named real prospects.
  • Record a 30-second Loom showing card to WhatsApp order.
  • Write DM v1 and a 48-hour follow-up line.

Deliverable: 10 live sample links, one video, one message script.

Day 7First outreach

Send and track volume

  • Send 25 DMs with sample links attached.
  • Log every send, reply and objection in a sheet.
  • Reply to every response within two hours.

Deliverable: 25 DMs sent, response log started.

Week 2 · Launch & first sale · 7 days
Day 8Volume

Second wave and follow-ups

  • Send 25 new DMs.
  • Follow up on day-7 non-replies once.
  • Rewrite the opening line using the best reply so far.

Deliverable: 50 DMs total, follow-ups issued.

Day 9Concierge

Convert interest into a live card

  • Deliver 5 personalised sample cards to repliers.
  • Set each card up with their real name and WhatsApp number.
  • Ask each for a one-line reaction.

Deliverable: 5 owner-ready cards in the field.

Day 10Ask

Issue payment links

  • Send the $19 first-month offer to the warmest 10 prospects.
  • Post in 5 local bazar or classificados groups with a sample card.
  • Track opens and replies per message variant.

Deliverable: First payment links in the wild.

Day 11Push

More volume, faster replies

  • Send 25 new DMs.
  • Call the two warmest prospects on WhatsApp voice.
  • Fix any card bug reported by a prospect same day.

Deliverable: 75 DMs, two voice conversations.

Day 12First saleFirst sale target

Close the first paying account

  • Close at least one $39 or $19 payment.
  • Confirm activation and send the QR code.
  • Ask the buyer exactly what triggered the decision.

Deliverable: First verified payment from a real business.

Day 13Proof

Turn buyer into distribution

  • Ask the first buyer to post the card in WhatsApp status.
  • Add their own words to the landing page as a quote.
  • Draft a case walkthrough from their numbers.

Deliverable: One share request sent, one quote added.

Day 14Review

Fix the weak step in the funnel

  • Compute reply rate, offer rate and close rate.
  • Rewrite the DM around the strongest objection.
  • Set week-3 target of 30 DMs per day.

Deliverable: DM v2 and a funnel baseline.

Week 3 · Repeat & systematize · 7 days
Day 15Scale

Segment into lunch delivery

  • Send 30 DMs to marmita and lunch-delivery accounts.
  • Attach city-specific sample cards.
  • Log objections verbatim.

Deliverable: 130 DMs sent cumulatively.

Day 16Scale

Follow-ups and objections

  • Send 30 DMs.
  • Follow up on every 48-hour non-reply.
  • Answer the top objection with a one-line script.

Deliverable: 160 DMs, objection script.

Day 17Delivery

Onboard paying accounts properly

  • Configure every paying account with its real zones.
  • Test each live card on a phone.
  • Send each owner a ready-to-paste WhatsApp status text.

Deliverable: All paying accounts live and verified.

Day 18Scale

QR as a physical hook

  • Generate a printable QR sheet per paying account.
  • Send 30 DMs offering the QR plus link bundle.
  • Check counter data on active cards.

Deliverable: QR sheets delivered, 190 DMs.

Day 19Expand

Second city

  • Build sample cards for Belo Horizonte prospects.
  • Send 30 DMs in the new city.
  • Compare reply rate against the first city.

Deliverable: 220 DMs, second-city data.

Day 20Communities

Group distribution

  • Post a sample card in 5 WhatsApp or Telegram local groups.
  • Send 30 DMs.
  • Reply to inbound from groups the same day.

Deliverable: 250 DMs plus group distribution.

Day 21Review

Midpoint economics

  • Reconcile payments received against the processor dashboard.
  • Issue any refund immediately and note the reason.
  • Prune messaging that produced zero replies.

Deliverable: Updated revenue ledger and pruned scripts.

Week 4 · Scale what works · 7 days
Day 22Language

Open the Mexico path

  • Ship Spanish labels on the public card.
  • Build 5 Guadalajara and CDMX sample cards.
  • Draft the Spanish DM.

Deliverable: Spanish card live, 5 ES samples.

Day 23Language

Spanish outreach

  • Send 20 Spanish DMs with samples.
  • Compare reply rate to Portuguese.
  • Fix any locale display bug.

Deliverable: 20 ES DMs, locale comparison.

Day 24Scale

Combined volume

  • Send 30 DMs across both markets.
  • Follow up on all 48-hour non-replies.
  • Confirm every new payment activates correctly.

Deliverable: 300 DMs cumulatively.

Day 25Retention

Keep the paying cohort alive

  • Check which paying cards still receive clicks.
  • Message any owner with zero clicks to fix their zones.
  • Ask each paying owner what they would remove from the product.

Deliverable: Retention check on every account.

Day 26Cash forward

Prepay and referrals

  • Offer the $99 three-month prepay to active owners.
  • Ask every paying owner for one referral introduction.
  • Send 30 new DMs.

Deliverable: Prepay offers sent, referral asks logged.

Day 27Scale

Close the month strong

  • Send 30 DMs.
  • Re-activate all cold sample-card prospects.
  • Publish a short build-in-public post with a sample card.

Deliverable: 330 DMs, reactivation wave.

Day 28Reconcile

Payment hygiene

  • Match every payment to a business and a launch date.
  • Confirm the payment account is the one connected to TrustMRR.
  • Document fees actually charged.

Deliverable: Payment reconciliation complete.

Days 29-30 · Consolidate · 2 days
Day 29Final push

Maximum closes

  • Send 40 DMs to the highest-fit untouched accounts.
  • Call the five warmest prospects directly.
  • Close every verbal yes with a payment link today.

Deliverable: Final outreach wave sent and closed.

Day 30Close

Verify, refund, document

  • Verify every payment falls inside the contest window.
  • Process any refund and record the reason.
  • Publish the final profit ledger and a one-page learning summary.

Deliverable: Final verified ledger and written summary.

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

  • All figures are projections, not verified revenue or existing customers.
  • Monthly price is $39; blended ARPU of $39 assumes the $19 first-month concession is applied only to a minority of accounts.
  • Conservative assumes 3 paying businesses in 30 days, base 10, upside 25.
  • Payment fees modeled at roughly 5% of collected revenue (Stripe Checkout in BRL plus currency conversion to USD).
  • Conservative and Base assume zero refunds and zero chargebacks in the first 30 days.
  • Upside assumes one $39 refund out of 25 customers and no chargebacks.
  • ad_spend_usd is paid marketing only; all Instagram DM outreach is organic and costs $0.
  • Operating costs cover Vercel, domain and email tooling; Supabase free tier and no inference cost because v1 has no AI component.
  • Hackathon profit excludes hosting and tooling; business profit subtracts them.
  • No customers or payments exist before the launch window opens.

Conservative

3 customers
$117
collected revenue · avg payment $39
Refunds
$0
Chargebacks
$0
Payment fees
$6
Paid marketing
$0
Hackathon profit
$111
Operating costs
$28
Business profit
$83

Base case

10 customers
$390
collected revenue · avg payment $39
Refunds
$0
Chargebacks
$0
Payment fees
$20
Paid marketing
$0
Hackathon profit
$370
Operating costs
$35
Business profit
$335

Optimistic

25 customers
$975
collected revenue · avg payment $39
Refunds
$39
Chargebacks
$0
Payment fees
$49
Paid marketing
$50
Hackathon profit
$837
Operating costs
$60
Business profit
$777

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$390
Payment fees (3.9%)
$15
Paid marketing
$0
Hackathon profit
$375
Business profit
$340

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

All scenarios are projections derived from stated assumptions. They are not verified revenue, existing customers or real traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Instagram DM reply rate is too low because messages land in requests or read as spam.

Mitigation

Warm the account for 3 days before outreach, cap at 25 DMs per day, personalise every first line with the business name and city, and lead with a live sample link rather than a pitch.

Validation experiment

Send three opener variants to 10 qualified accounts each over two days and record reply rate per variant.

Kill criteria

If fewer than 5% of 60 personalised DMs reply, stop Instagram DMs and move to the WhatsApp-group plus walk-in concierge path.

Risk 2Owners do not consider the delivery-zone question painful enough to pay $39, because a free Google Business Profile or Instagram caption feels sufficient.

Mitigation

Ask the question directly before pitching, quoting the number of times per day they answer it, and price against the lost orders rather than the software.

Validation experiment

Ask 10 owners what they actually do today when a customer asks about delivery, and count how many describe it as routine pain versus no problem.

Kill criteria

If 7 of 10 owners say the question is not a problem, reposition the same build to the pre-filled WhatsApp order message and re-test with a different promise.

Risk 3Price resistance at $39 for businesses that treat $39 as a meaningful monthly cost.

Mitigation

Keep the $19 first month as the closing concession and offer the $99 three-month prepay only after a month of use.

Validation experiment

Split the next 40 offers: 20 at $39 first month, 20 at $19 first month, and compare close rate.

Kill criteria

If $39 produces zero closes in 20 offers while $19 closes three or more, restructure to a $19 base tier and keep $39 for multi-card accounts.

Risk 4WhatsApp pre-filled order text is truncated or stripped in some in-app browsers, so the owner receives an unqualified message.

Mitigation

Keep the pre-filled body under 120 characters, encode it server-side, and test on iOS Safari, Android Chrome and the Instagram in-app browser.

Validation experiment

Open the card and complete an order on five devices and two mobile carriers, recording whether neighborhood and fee survive.

Kill criteria

If the body is lost on two or more mainstream devices, fall back to a two-step flow that copies the message to clipboard and shows it on screen.

Risk 5The account holder who pays is not the person answering WhatsApp, so the card never gets shared.

Mitigation

Send a ready-to-paste WhatsApp status text and a printable QR at onboarding so the share takes one action.

Validation experiment

Check click counters for every paying account within 72 hours of activation.

Kill criteria

If more than half of paying accounts show zero WhatsApp clicks after 7 days, the product is being bought but not used and onboarding must change before more outreach.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Re-read the hackathon rules page and note the exact revenue window.
  • Buy the domain and create Vercel and Supabase projects.
  • Create the payment account connected to TrustMRR.

Output: Live domain, deployed hello-world, payment account ready.

Hours 3-6

  • Create accounts, zones, events and subscriptions tables with RLS.
  • Build magic-link auth and the protected app shell.
  • Ship zone CRUD with fee and estimated-time fields.

Output: Working dashboard that saves zones for one test account.

Hours 7-9

  • Build the public /c/[slug] card with neighborhood dropdown.
  • Generate the wa.me link with neighborhood and fee pre-filled.
  • Test the flow on one iPhone and one Android device.

Output: A working card link that opens a pre-filled WhatsApp chat.

Hours 10-12

  • Build five real sample cards using named prospects' business names and city neighborhoods.
  • Render QR codes for each sample.
  • Write DM v1 and a 48-hour follow-up line.

Output: Five live sample cards, five QR images, one message script.

Hours 13-16

  • Build a list of 40 qualified Instagram accounts with a WhatsApp link and no zone info.
  • Send the first 10 DMs with their matching sample links.
  • Start the response tracking sheet.

Output: 40-account prospect list, 10 DMs sent, tracking sheet live.

Complete report

Full 30-day launch report

Read the full generated report

ZonaCard — 30-Day Launch Report

1. Product opportunity and positioning

ZonaCard converts the most repeated message in a small food business into a link. An owner-operated confeitaria, marmita kitchen or 1-5 person restaurant posts "fazemos entrega" on Instagram, then spends the day answering "voce entrega no meu bairro? quanto e?" in WhatsApp. Answers drift, replies lag, and some customers give up before ordering.

ZonaCard is not a marketplace and not a website builder. The owner enters neighborhoods and fees once; the product returns a short link, a QR code and a public mobile page. A customer picks a neighborhood, sees fee and estimated time, and taps "Pedir no WhatsApp", which opens a chat with a pre-filled message naming the neighborhood and the fee. The owner receives an order that is already qualified.

JEV scored this concept 65.7/100 (band B), strongest on speed to first revenue (8.21/10) and solo build feasibility (8.89/10), weakest on market demand (4.38/10). That shape dictates the plan: do not spend 30 days polishing software. Ship a usable card by day 5 and spend the remaining 25 days proving owners will pay $39/month instead of living with a free workaround.

The buyer is reachable without a cold-start. They already publish a WhatsApp number and already answer this question daily. The channel is a direct message containing a working sample card built from their own city's neighborhoods, so the reply is not "what is this" but "how much".

Narrowness is deliberate. A directory needs both sides to show up; a zone card needs one owner and one link. Value is proven inside the owner's existing WhatsApp audience on day one of use, with no platform traffic to bootstrap and no buyer-side accounts.

2. Smallest sellable MVP

The sellable unit is one live card link plus a QR code, generated by a dashboard the owner controls. Seven things must work: sign-in, zone and fee CRUD, business name and WhatsApp number settings, a public mobile card with a dropdown, a pre-filled WhatsApp deep link, a QR image, and view/click counters. Everything else is excluded: no payments, no maps, no tracking, no catalog, no AI, no integrations, no custom domains. Build time is four days; the freeze lands on day 5 so outreach starts with a real product, not a promise.

3. Technical implementation plan

A single Next.js app on Vercel serves an authenticated dashboard and a public server-rendered card. Supabase handles auth and Postgres with row-level security so each owner reads only their own zones and events. The card loads zones for its slug, renders a dropdown client-side, and builds a wa.me URL from the stored number and a URL-encoded message. Views and clicks are inserted as rows and aggregated on read. Stripe payment links take the money and a webhook flips an account active.

The hardest part is not the stack; it is the WhatsApp deep link. Pre-filled bodies get truncated or dropped in some in-app browsers. Keep the message under 120 characters, encode server-side, and test iOS Safari, Android Chrome and the Instagram browser before sending a single DM. There is no AI component: every fee and delivery time is entered by the owner, so delivery cost per customer stays near zero.

4. Pricing and monetization

One plan at $39 per month per business, billed through a Stripe payment link. A $19 first month exists only as a closing concession, never as an advertised tier, so the published price anchors at $39. After a month of use, active owners can be offered a $99 three-month prepay to pull cash forward. Later add-ons are printed QR table stickers and a second card for a second location.

At $39, a paying customer covers the entire monthly hosting bill several times over. That is the point: this product should be profitable at three customers, not at three hundred.

5. First-customer acquisition

The only channel is Instagram DM to Brazil-based food businesses that mention delivery but publish no zone or fee information. Search confeitaria, bolo no pote, marmita and salgados plus a city name; filter for accounts with a wa.me link in bio and a post in the last two weeks. Build the sample card first, then send the message naming the business and its city with the link attached. Follow up once after 48 hours. Only after a reply does the $19 first month appear.

Week one target: 100 DMs, 10 sample cards delivered, 3 payment links issued. Days 15 to 30 push to 30 DMs per day, add a second Brazilian city, then open a Spanish path into Guadalajara and CDMX on day 22. Local bazar and classificados WhatsApp groups provide a second, lower-volume surface.

6. Thirty-day execution roadmap

Week 1 is build plus first send: days 1-4 deliver the dashboard, the public card and the QR, day 5 freezes scope behind a working checkout, and days 6-7 produce ten real sample cards and the first 25 DMs.

Week 2 converts. Days 8-11 add volume and voice calls, day 12 is the first-sale target, day 13 asks the buyer to share the card in their WhatsApp status, and day 14 recalculates reply, offer and close rates to rewrite the message.

Week 3 scales to 30 DMs per day, splits out lunch-delivery accounts, onboards paying accounts properly with real zones, and starts a second city. Day 21 reconciles payments against the processor and prunes any messaging that produced zero replies.

Week 4 opens Spanish, pushes combined volume to roughly 330 DMs, runs a retention check on every paying card, and offers the $99 prepay plus referral asks. Days 29-30 send a final wave of 40 high-fit DMs, verify every payment sits inside the contest window, process any refund, and publish the verified ledger.

7. Revenue and profit scenarios

All three scenarios are projections from stated assumptions, not verified revenue.

Conservative: 3 customers at $39 ARPU, $117 gross, $6 processing, no refunds, no ads, $28 operating cost. Base: 10 customers, $390 gross, $20 processing, $35 operating cost. Upside: 25 customers, $975 gross, one $39 refund, $49 processing, $50 paid marketing, $60 operating cost.

Two different numbers matter. Hackathon profit subtracts refunds, chargebacks, processing fees and paid marketing only. Business profit additionally subtracts hosting, domain and tooling. Even the conservative case clears hackathon costs; the base case is the realistic target given a 300-DM outreach volume and a 3-4% close rate on cold DMs.

8. Main risks and validation experiments

Reply rate is the first risk. Warm the account, cap at 25 DMs per day, personalise every opener, and test three variants on 10 accounts each. If fewer than 5% of 60 DMs reply, abandon Instagram and move to WhatsApp-group distribution and in-person concierge.

Demand is the second. Ask 10 owners what they do today when asked about delivery and classify the answer as pain or non-pain. If 7 of 10 say it is not a problem, keep the build and change the promise to the pre-filled order message.

Price is the third. Split 40 offers between $39 and $19 first month. If $39 produces zero closes while $19 closes three, restructure the tiers rather than discounting forever.

Technical risk sits in the WhatsApp deep link. Test five devices before outreach, and if the body is lost on two mainstream devices, ship a copy-to-clipboard fallback that shows the message on screen.

9. First 24-hour action plan

Hours 1-2: read the rules, buy the domain, create Vercel and Supabase projects, open the payment account connected to TrustMRR. Hours 3-6: tables, auth, zone CRUD. Hours 7-9: public card and WhatsApp deep link, tested on two devices. Hours 10-12: five real sample cards, QR images, DM script. Hours 13-16: a 40-account prospect list and the first 10 personalised DMs sent with their matching sample links.

By the end of day one the founder should have a deployed product, five live cards bearing real business names, and ten conversations in flight. Everything after that is repetition and refinement.

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 →