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

Inbox Passport

Inbox Passport fingerprints a client domain's real email sending stack, generates the exact SPF, DKIM and DMARC records to paste, verifies them over 48 hours, and issues a timestamped white-label PDF certificate the agency can hand to its client.

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.70/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Manual, personalised cold outreach to 300 hand-built small-agency contacts, each message opening with that agency's own real DNS failure generated free by the product.
Who pays

Owner-operator or sole email marketer at a 1-10 person web design, Shopify or marketing agency in the US, UK, Canada or Australia, mid-onboarding of a client domain, mid-ESP migration, or reacting to a client complaint that mail lands in spam.

Biggest execution risk

Monetization potential 5.5/10

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 14; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.0/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

14 concrete actions. Tick them off as you go — nothing is saved or sent.

0/14
Entry price
$99
Solo build
5 days
30d base revenue
$1,386
30d hackathon profit
$1,317
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator or sole email marketer at a 1-10 person web design, Shopify or marketing agency in the US, UK, Canada or Australia, mid-onboarding of a client domain, mid-ESP migration, or reacting to a client complaint that mail lands in spam.

Why now

Agencies are onboarding and migrating client domains continuously and the free diagnosis tools stop short of producing anything a client will accept as proof of work.

Problem

Fixing SPF, DKIM and DMARC per ESP burns 1-3 unbilled hours, breaks silently on double SPF records or a wrong selector, and leaves the agency with no artifact proving the work was done correctly.

Solution

Enter a domain, get a live DNS report and stack fingerprint, receive a copy-paste record recipe with failure flags, watch a 5-minute re-check loop until all-green, then export a branded PDF certificate plus a read-only share link.

Differentiation · Free checkers diagnose; Inbox Passport delivers the stack-specific recipe plus a timestamped signed certificate the agency can rebill, and keeps re-verifying after the client touches DNS.

The gap is the artifact, not the diagnosis

An agency onboarding a client domain has a 90-minute job with no clean tool: work out which sending stack the site actually uses, publish the matching SPF include, find the DKIM selector the ESP picked, avoid the double-SPF mistake that silently voids both records, and then leave DMARC at p=none forever because nothing forces the upgrade. Free checkers (MXToolbox, Google Admin Toolbox, dmarcian, assorted DMARC testers) will show red and green. None of them produce a document the agency can forward to a client and invoice against.

That is the wedge. Inbox Passport reads the domain's live DNS over Cloudflare's DNS-over-HTTPS endpoint, probes around fourteen common DKIM selectors, and maps the observed SPF includes and CNAMEs to a recipe library covering roughly ten stacks: Google Workspace, Microsoft 365, Klaviyo, Mailchimp, Shopify Email, Mailjet, Brevo, HubSpot, SendGrid and Postmark. From that fingerprint it prints host, type, value and TTL rows the agency pastes directly into Cloudflare, GoDaddy or Namecheap, alongside explicit flags for multiple SPF records, over-limit DNS lookups, a dead selector, missing DMARC and p=none.

Then it does the part nobody else sells at this price: it re-checks every five minutes for 48 hours and, on all-green, mints a timestamped PDF certificate carrying the agency's logo, a per-record pass table, remaining warnings and a plain-English client summary behind a read-only share link. The certificate is the deliverable. The diagnosis is the lead magnet.

The buyer is the owner-operator of a 1-10 person web design, Shopify or marketing agency in the US, UK, Canada or Australia, triggered by a new client domain, an ESP migration, or a client complaint about invoices landing in Promotions. There is already a client budget line, so $99 needs no procurement, no DPA and no security review. Distribution is manual, personalised cold outreach to 300 hand-built agency contacts, each message opening with that agency's own real DNS failure generated free by the product.

JEV scores this concept 67.0/100 (band B), strongest on speed to first revenue and solo build feasibility, weakest on monetization depth and defensibility. The plan reflects that: ship in five days, sell the certificate at $99, and treat the $249/month Agency Desk as an experiment rather than a forecast. Delivery is DNS lookups plus one PDF render, so cost stays near zero and nothing here touches deliverability, lists or sending infrastructure.

Section 2 of 8

Smallest sellable MVP

A public domain checker that fingerprints the sending stack, prints the exact copy-paste DNS rows with failure flags, runs a 48-hour verification loop, and unlocks a branded PDF certificate and share link on a $99 Stripe payment.

Must-have features

  • Domain intake plus live DNS check of SPF, DMARC, MX and PTR via Cloudflare DNS-over-HTTPS
  • DKIM sweep across ~14 common selectors with results shown per selector
  • Stack fingerprinter mapping SPF includes and CNAMEs to a 10-stack recipe library
  • Recipe generator emitting host, type, value, TTL rows per stack with explicit failure flags
  • 48-hour verification loop on a 5-minute cron with a public per-domain status page
  • Branded PDF certificate with logo upload, timestamp and per-record pass table
  • Stripe Payment Link unlock plus magic-link access and a read-only share token

Explicitly out of scope

  • Inbox placement or seed-list testing
  • Bulk sending, campaign builder or any ESP functionality
  • Email list validation or bounce cleaning
  • DMARC aggregate report (RUA) ingestion
  • Team seats, roles, SSO or a full client portal
  • Enterprise security review, DPA or procurement-ready tier

Demo flow (what the buyer sees)

  1. Visitor enters a client domain on the public checker
  2. Product shows live SPF, DKIM, DMARC, MX and PTR results
  3. Fingerprint panel names the detected sending stack with the evidence used
  4. Recipe panel lists exact DNS rows plus flags for every broken state
  5. Visitor pays $99 via Stripe Payment Link on that domain
  6. Cron re-checks every 5 minutes; on all-green the certificate PDF and share link unlock
Build plan

Technical implementation plan

Stack

Next.js 15 on Vercel (serverless routes plus cron)Cloudflare 1.1.1.1 DNS-over-HTTPS JSON API for all lookups (free)Supabase Postgres for domains, check history and share tokensSupabase Storage for generated certificate PDFsStripe Payment Links plus a webhook that flips a domain to paid@react-pdf/renderer for the certificateResend free tier for the two transactional emailsTailwind CSS for the report and status pages

Architecture

A single Next.js app serves the public checker, the paid results page and the share view. Every DNS read goes through one resolver wrapper that batches SPF, DMARC, MX, PTR and the DKIM selector sweep, normalises the answers, and writes a check row to Supabase. A pure function maps the normalised answers to a stack fingerprint and then to recipe rows from a static JSON library. Stripe Payment Links carry the domain id in metadata; the webhook sets paid_at on that domain. A Vercel cron hits an internal route every five minutes, re-resolves every paid domain younger than 48 hours, appends a check row, and on first all-green renders the certificate with @react-pdf/renderer into Supabase Storage and emails the link through Resend. Share tokens are opaque random ids scoped to one domain and one certificate version.

Build steps

  1. Scaffold Next.js, Supabase schema (domains, checks, certificates) and deploy an empty page to Vercel
  2. Write the Cloudflare DoH resolver wrapper with timeout, retry and answer normalisation
  3. Parse SPF includes, DMARC policy, MX and PTR into a pass/fail model
  4. Run the 14-selector DKIM sweep in parallel and store raw results
  5. Build the stack fingerprint map and the static recipe library JSON
  6. Render the recipe table with host, type, value, TTL plus failure flags
  7. Add Stripe Payment Link, webhook and magic-link access
  8. Add share tokens and the read-only share page
  9. Build the certificate PDF template with logo upload and timestamp
  10. Ship the 5-minute Vercel cron and the all-green email
  11. Run 20 known-good and 20 known-broken domains through the whole flow before launch

AI components

  • One LLM call drafts the plain-English client summary paragraph from the check table; a deterministic template is the fallback if the call fails or returns unusable text. No other model use.
Hardest technical risk: DKIM selector discovery is guesswork: custom selectors produce false negatives, so a wrong certificate on a correctly configured domain erodes trust faster than any copy fix. Mitigation is a visible 'selector not found — enter it manually' path plus a disclaimer on the certificate.
Section 3 of 8

Pricing and monetization

Free Audit

Entry offer
$0 one-time

For Cold-outreach prospects and community readers

  • Live DNS pass/fail report
  • Read-only share link without certificate export

Single Domain Passport

$99 one-time

For Solo marketer or small agency fixing one client domain now

  • Live DNS authentication report
  • Stack-specific copy-paste record recipe
  • 48-hour verification loop with status page
  • Branded PDF certificate with agency logo
  • Read-only client share link

Agency Desk

$249 / month

For 1-10 person agency onboarding several client domains per month

  • Unlimited domain passports
  • White-label certificates
  • Monthly re-verification with drift alerts
  • Certificate re-issue after client DNS changes

Model: One-time $99 per domain for the recipe, 48-hour verification and branded certificate, with a free read-only audit as the lead magnet and a $249/month agency tier as the upsell experiment.

First revenue offer: Free read-only DNS report on the agency's own domain, sent unsolicited, closing with: $99 for the stack-specific recipe, 48-hour verification and a branded certificate you can hand to the client.

Expected ACV: $99

Upsell path: Every buyer and every responder is asked for one client domain they are onboarding this month and pitched Agency Desk at $249/month; annual prepay at $2,490 is offered for cash inside the window.

Target customers
30
Revenue model
$2,970
Costs
$170
Profit model
$2,800
Section 4 of 8

First-customer acquisition

Primary channel

Manual, personalised cold outreach to 300 hand-built small-agency contacts, each message opening with that agency's own real DNS failure generated free by the product.

Where to find them

  • Shopify Partner directory listings for small agencies
  • WordPress agency roundup posts and 'top agencies' listicles
  • Clutch profiles filtered to 1-10 person web design and marketing agencies
  • X and LinkedIn bios matching 'Shopify agency' or 'Klaviyo partner'
  • Agency Slack and Facebook communities where operators already discuss deliverability

Exact outreach motions

  • Run every agency's own domain through the free checker and keep only domains with at least one real failure
  • Send a three-sentence email opening with the specific failure found and a free read-only report link
  • 72-hour follow-up restating only the remaining failures
  • Day-7 follow-up with the certificate sample attached as a PDF
  • X and LinkedIn DMs to the same owners with the same opener, capped at 20 per day
  • Ask every responder for one client domain they are onboarding to pitch Agency Desk

Message template

Hi {first_name} — I ran {agency_domain} through a free email-authentication check and it has two SPF records while DMARC sits at p=none, which is the usual reason client mail starts landing in spam. Read-only report here: {share_link}. Fixing it is one paste. If you want the stack-specific record recipe plus a timestamped certificate you can hand the client, it's $99: {stripe_link}.
Week-one goal: 300 agency domains checked, 140 audited with share links, 100 personalised messages sent, at least 8 replies and 1 paying customer by day 14.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 1430 days planned
Week 1 · Build & validate · 7 days
Day 1Scaffold and DNS reader

Real DNS data rendering in public

  • Scaffold Next.js on Vercel with Supabase schema for domains and checks.
  • Wrap Cloudflare DoH JSON API in one resolver with timeout and retry.
  • Parse SPF, DMARC, MX and PTR into a pass/fail table.
  • Ship the public domain check page.

Deliverable: Live public DNS report page for any domain.

Day 2DKIM sweep and fingerprint

Identify the sending stack

  • Probe 14 common DKIM selectors in parallel.
  • Map SPF includes and CNAMEs to a 10-stack recipe library JSON.
  • Show the detected stack with the evidence used.
  • Log every probe for later tuning.

Deliverable: Fingerprinter that names the ESP for test domains.

Day 3Recipe and failure flags

Copy-paste output plus warnings

  • Emit host, type, value, TTL rows per detected stack.
  • Flag multiple SPF, over-limit lookups, missing DMARC, p=none and dead selectors.
  • Add opaque read-only share tokens.
  • Test against 20 known-good and 20 known-broken domains.

Deliverable: Recipe page with warnings and share link.

Day 4Payments and access

Free-to-paid unlock

  • Create the $99 Stripe Payment Link carrying the domain id.
  • Webhook flips the domain to paid and unlocks export.
  • Send magic-link access email via Resend.
  • Run a test-card purchase end to end.

Deliverable: Checkout that unlocks one domain.

Day 5Certificate and verify loopMVP shipped

Ship the deliverable

  • Render the PDF certificate with logo upload and timestamp.
  • Add the 5-minute Vercel cron for 48 hours.
  • Send the all-green email.
  • Deploy to the production domain.

Deliverable: End-to-end product live (MVP deadline).

Day 6Warm-up and list build

Sender reputation and first 50 accounts

  • Publish SPF, DKIM and DMARC on your own sending domain and warm it.
  • Hand-build 50 agencies from the Shopify Partner directory.
  • Run all 50 through the free checker and record failures.
  • Write the three-sentence outreach template.

Deliverable: 50-account list with per-domain failure notes.

Day 7Free audits at scale

Pipeline before pitching

  • Add 100 agencies from WordPress roundups and Clutch.
  • Generate free audit share links for all new domains.
  • Send the first 40 personalised messages.
  • Track replies in one sheet.

Deliverable: 140 audited domains, 40 messages sent.

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

Volume at low send rate

  • Send 60 more personalised messages.
  • Post one anonymised teardown in an agency Slack group.
  • Reply to every response within two hours.
  • Log objections verbatim.

Deliverable: 200 contacts, first live conversations.

Day 9Follow-up and copy fixes

Turn replies into checkouts

  • Send the 72-hour follow-up to day-7 non-responders.
  • Patch copy where objections repeat.
  • Add a plain 'what this does not fix' note above checkout.
  • Prepare the certificate sample PDF.

Deliverable: Revised checkout copy and follow-up wave sent.

Day 10Complete the 300

Full pipeline coverage

  • Add the remaining 100 agencies from X and LinkedIn bios.
  • Audit and queue their sends.
  • Publish free audit pages for all of them.
  • Draft teardown post one.

Deliverable: 300-account pipeline fully audited.

Day 11US holiday build day

No cold sends, fix the funnel

  • Pause cold email for the US holiday.
  • Watch three friendly founders use the free audit on a call.
  • Fix the top drop-off in the paid flow.
  • Add refund policy text to checkout.

Deliverable: Funnel fixes deployed without burning send reputation.

Day 12Light-touch day

Non-US sends only

  • Send 25 messages to UK, CA and AU agencies.
  • Post one teardown in a UK or AU agency community.
  • Clear all open reply threads.
  • Queue the full push list for day 13.

Deliverable: 25 sends and a queued push list.

Day 13Full push

Convert the failures-heavy accounts

  • Send 80 messages to accounts with two or more failures.
  • DM 20 owners on X and LinkedIn.
  • Offer a live 15-minute fix call for $99.
  • Track replies hourly.

Deliverable: 100 touches with replies in flight.

Day 14First sale and deliveryFirst sale target

Money and a delivery baseline

  • Close the first certificate sale.
  • Hand-deliver it and record time spent.
  • Ask for one sentence of feedback with permission to anonymise.
  • Pitch Agency Desk to the same buyer.

Deliverable: First verified revenue and a delivery timing baseline.

Week 3 · Repeat & systematize · 7 days
Day 15Second-niche wave

Shopify-only agencies

  • Send 100 messages to Shopify-only agencies.
  • Publish teardown post one.
  • Follow up all week-two non-responders.
  • Log which failure flag produces replies.

Deliverable: 100 new contacts and flag-level reply data.

Day 16Agency Desk build

Subscription tier

  • Add a multi-domain dashboard behind Agency Desk.
  • Wire the Stripe subscription.
  • Add monthly re-verification cron with drift email.
  • Ship the certificate re-issue button.

Deliverable: Agency Desk tier live at $249/month.

Day 17Proof assets

Make the page sell while you sleep

  • Turn the first delivery into an anonymised before/after.
  • Add the certificate sample to the landing page.
  • Write a pricing FAQ answering the free-tool objection.
  • Update meta description and share image.

Deliverable: Landing page with sample certificate and FAQ.

Day 18Volume day

400 cumulative contacts

  • Send 100 more personalised messages.
  • Post in two more agency communities.
  • Hold the two-hour reply SLA.
  • Book any call offered.

Deliverable: 400-plus cumulative contacts.

Day 19Calls

Close on screen share

  • Run booked calls with the live checker on screen.
  • Send a Stripe link during the call.
  • Capture the exact sentence that closes.
  • Update the template with it.

Deliverable: Call script v2 and closed deals.

Day 20Accuracy pass

Fix selector false negatives

  • Fix reported selector false negatives.
  • Add a manual custom-selector field.
  • Re-run 50 previously failing domains.
  • Update the recipe library.

Deliverable: Selector accuracy patch deployed.

Day 21Inbound setup

Stop relying only on outbound

  • Publish teardown post two.
  • Add an inbound free-audit form to the homepage.
  • Submit sitemap and check first impressions.
  • Add free-audit-to-paid CTA on every share page.

Deliverable: Inbound path live.

Week 4 · Scale what works · 7 days
Day 22Scale to 600

Double the pipeline

  • Add 200 more agencies.
  • Send 100 with failure-specific openers.
  • Follow up week-three non-responders.
  • Compute cost per sale at zero ad spend.

Deliverable: 600-account pipeline.

Day 23Agency Desk sell

Recurring revenue attempt

  • Pitch Agency Desk to every past buyer.
  • Offer annual prepay at $2,490.
  • Document onboarding in one page.
  • Add a usage guard for unlimited domains.

Deliverable: Subscription pitches sent to all buyers.

Day 24Certificate v2

Make the artifact more valuable

  • Add the client-facing summary paragraph.
  • Add certificate ID and a verify URL.
  • Test PDF rendering on mobile and print.
  • Re-issue all existing certificates.

Deliverable: Certificate v2 shipped.

Day 25Second channel test

Cheap inbound experiment

  • Post one teardown to a relevant subreddit within its self-promo rules.
  • Comment-only participation elsewhere.
  • Measure share links created from that traffic.
  • Keep or kill the channel after 48 hours.

Deliverable: One channel decision with data.

Day 26Retention and delivery

Protect the revenue already booked

  • Reply to every open customer thread same day.
  • Fix two reported friction points.
  • Add DNS-change re-check reminders on paid domains.
  • Ask two buyers for a referral agency.

Deliverable: Support SLA met and two referral asks made.

Day 27Drift alerts

Give Agency Desk a reason to exist

  • Build the monthly re-verification email.
  • Add a 'your client changed DNS' alert.
  • Test the flow on five paid domains.
  • Add an unsubscribe path.

Deliverable: Drift alerting live.

Day 28Pre-final push

Exhaust the list

  • Send 100 to remaining contacts.
  • Follow up all week-four non-responders.
  • Publish teardown post three.
  • Reconcile Stripe against the TrustMRR-connected account.

Deliverable: Outreach exhausted, books reconcile.

Days 29-30 · Consolidate · 2 days
Day 29Close the window

Convert open conversations

  • Send final 60 messages with a Dec 16 deadline angle.
  • Call every warm-but-unpaid lead once.
  • Process refunds same day.
  • Verify every certificate regenerates from stored data.

Deliverable: Final conversions booked.

Day 30Reconcile and report

Verified numbers

  • Export Stripe transactions and compute collected revenue minus refunds, fees and ad spend.
  • Write the public 30-day teardown.
  • Note the top three next builds.
  • Submit the verified revenue statement.

Deliverable: Verified revenue statement and public teardown.

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

  • Conservative/Base/Upside: all scenarios sell the $99 Single Domain Passport only; Agency Desk revenue is excluded from every projection.
  • Conservative/Base/Upside: outreach is organic manual email and DM, so ad_spend is 0 except in the Upside case where $200 of sponsored community posts is assumed.
  • Conservative/Base/Upside: payment fees modelled at 5% of gross collected revenue (Stripe 2.9% plus $0.30 per charge, plus a buffer for non-US cards and currency conversion).
  • Conservative: 4 paid certificates from 300 contacts — low end of the reply-rate hypothesis with holiday drag.
  • Base: 14 paid certificates, consistent with an 8-12% reply rate and roughly 20% of responders paying.
  • Upside: 30 paid certificates matching the concept's own monetization math, one refund and one chargeback-free tail.
  • Operating costs cover Vercel, Supabase, domain, Resend and PDF rendering; DNS lookups are free. All figures are projections, not verified revenue.
  • Every sale must exceed its delivery cost: one $99 sale covers roughly $1-3 of marginal DNS and PDF cost.

Conservative

4 customers
$396
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$20
Paid marketing
$0
Hackathon profit
$376
Operating costs
$30
Business profit
$346

Base case

14 customers
$1,386
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$69
Paid marketing
$0
Hackathon profit
$1,317
Operating costs
$65
Business profit
$1,252

Optimistic

30 customers
$2,970
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$149
Paid marketing
$200
Hackathon profit
$2,522
Operating costs
$130
Business profit
$2,392

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,386
Payment fees (3.9%)
$54
Paid marketing
$0
Hackathon profit
$1,332
Business profit
$1,267

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

Scenario models from stated assumptions, not verified revenue. No customers, revenue or traction exist at launch; all figures are projections and the $100K target is not supported by this model.

Section 7 of 8

Main risks and validation experiments

Risk 1Prospects take the free audit, fix two records themselves and never pay.

Mitigation

Gate certificate export, the 48-hour verification loop and the share link behind payment; the free tier shows failures but no proof artifact.

Validation experiment

Track how many of the first 100 free-audit share links are opened more than twice without a purchase.

Kill criteria

If fewer than 1 in 25 audited prospects pays after 150 contacts, the artifact is not worth $99 and the offer needs rebuilding or repricing.

Risk 2DKIM selector guessing produces false negatives on correctly configured custom selectors, eroding trust.

Mitigation

Show 'selector not found — enter it manually' as a first-class path and state the limitation on the certificate.

Validation experiment

Run 40 known-good domains from public sources through the checker and count false negatives.

Kill criteria

If more than 15% of known-good domains are misreported, pause outreach until the selector path is fixed.

Risk 3Cold outreach from a brand-new domain lands in spam, killing the only channel.

Mitigation

Warm the sending domain for 48 hours, cap at 40-60 sends per day, and mirror the opener in LinkedIn and X DMs.

Validation experiment

Send 40 emails on day 7 and 20 DMs on day 12, then compare reply rates by channel.

Kill criteria

If combined reply rate stays under 3% after 150 sends, switch primary effort to DMs and community posting.

Risk 4A buyer still lands in Promotions for unrelated reasons and disputes the charge.

Mitigation

State 'verifies records, not inbox placement' above checkout and inside the certificate footer; refund on request without argument.

Validation experiment

Count how many of the first 20 buyers mention placement expectations before buying.

Kill criteria

If more than 2 of 20 buyers dispute on placement grounds, stop selling until the scope statement is rewritten.

Risk 5Free checkers commoditise the diagnosis and anchor the price at zero.

Mitigation

Never sell the report; sell the stack-specific recipe, the 48-hour proof and the client-ready certificate, and always lead with the free report as a gift.

Validation experiment

Offer the free report and the $99 artifact in the same message and measure which link gets clicked.

Kill criteria

If the free report link gets more than 5x the clicks of the paid link across 100 sends, reposition the paid offer around the certificate alone.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the production domain and connect it to Vercel.
  • Create the Supabase project and the domains, checks and certificates tables.
  • Write the Cloudflare DoH resolver wrapper.

Output: Deployed skeleton app with a working DNS resolver.

Hours 3-6

  • Parse SPF includes, DMARC policy, MX and PTR into a pass/fail model.
  • Build the public domain check page with the results table.

Output: Public checker returning real results for any domain.

Hours 7-10

  • Run the 14-selector DKIM sweep in parallel.
  • Write the 10-stack recipe library JSON.
  • Wire the fingerprint display.

Output: Fingerprinter naming the sending stack for test domains.

Hours 11-16

  • Render the recipe table with host, type, value, TTL and failure flags.
  • Add the share token and read-only share page.

Output: Shareable recipe page with warnings.

Hours 17-24

  • Create the $99 Stripe Payment Link and webhook.
  • Send the magic-link email through Resend.
  • Run the certificate PDF template.
  • Run one test-card purchase end to end.

Output: Payable, unlockable domain with a first-draft certificate.

Complete report

Full 30-day launch report

Read the full generated report

Inbox Passport — 30-Day Launch Report

Concept Inbox Passport v1 · JEV 67.0/100 (band B) · one solo founder · window 16 Nov – 16 Dec 2026 · 300 cold agency contacts · $99 one-time · first sale targeted day 14.

1. Product opportunity and positioning

The pain is 90 unbilled minutes per client domain. An agency onboarding a new Shopify or WordPress client has to work out which ESP the site actually sends through, publish the matching SPF include, guess the DKIM selector the ESP chose, and avoid the double-SPF mistake that voids both records. Free checkers confirm the mess but produce nothing the agency can put in front of a client, so the work stays invisible and gets redone on the next migration.

Inbox Passport sells the artifact, not the alarm. Input: one domain. Output: a stack-aware record recipe, a 48-hour verification loop, and a timestamped PDF certificate carrying the agency's logo plus a read-only share link it forwards to the client. The buyer is the owner-operator of a 1-10 person agency with an active domain migration or a client complaint, so the $99 sits inside an existing client budget line with no procurement and no security review.

Defensibility is deliberately thin. The recipe library, the 48-hour proof and post-handover re-issue are retention hooks, not a moat. The 30-day goal is 4 to 30 paid certificates and hard evidence that agencies pay for proof rather than diagnosis.

2. Smallest sellable MVP

Seven screens: public checker, results and recipe page, share page, checkout handoff, paid status page, certificate render, and a logo-upload field. The sellable unit is one domain that goes from red to green inside 48 hours and ends with a PDF. Anything that does not move a domain toward that PDF — placement testing, campaign tooling, list cleaning, RUA parsing — is out of scope and is stated as out of scope on the checkout page.

3. Technical implementation plan

Next.js on Vercel serves everything. One resolver wrapper hits Cloudflare's DNS-over-HTTPS JSON endpoint and batches SPF, DMARC, MX, PTR and the 14-selector DKIM sweep; results normalise into a single check row in Supabase. A pure function maps normalised answers to a stack fingerprint, then to rows from a static recipe library. Stripe Payment Links carry the domain id in metadata and a webhook stamps paid_at. A five-minute cron re-resolves every paid domain younger than 48 hours, and on first all-green it renders the certificate with @react-pdf/renderer into Supabase Storage and emails the link through Resend. The hardest technical risk is selector discovery: custom selectors produce false negatives, so the manual selector field and the certificate disclaimer are load-bearing, not cosmetic. One LLM call drafts the client summary paragraph; a fixed template is the fallback.

4. Pricing and monetization

Free Audit at $0 is the lead magnet and never includes export. Single Domain Passport at $99 one-time is the product: report, recipe, 48-hour verification, branded certificate and share link. Agency Desk at $249/month is the experiment: unlimited domains, white-label certificates, monthly re-verification with drift alerts and re-issue after client DNS changes. Annual prepay at $2,490 is offered for cash inside the window. No Agency Desk revenue appears in any projection; it is upside-only and every buyer and responder gets asked for one client domain to test it.

5. First-customer acquisition

One channel: manual, personalised cold outreach. Build 300 agencies by hand from the Shopify Partner directory, WordPress roundups, Clutch, and X/LinkedIn bios — no purchased lists. Run every agency's own domain through the free checker and keep only domains with at least one real failure. The opener is three sentences: the specific failure found, a free read-only report link, and the $99 artifact. Follow up at 72 hours and day 7 with the remaining failures only. Keep send volume at 40-60 per day on a warmed domain and mirror the opener in 20 DMs per day. Every week publish one anonymised authentication teardown in two agency communities to build a passive trickle.

6. Detailed 30-day execution roadmap

Days 1-5 build: resolver and public checker, DKIM sweep and fingerprint, recipe generator with failure flags, Stripe unlock and magic link, certificate plus cron. Day 5 is the MVP deadline. Days 6-7 warm the sending domain and audit the first 140 agencies. Day 8 starts outreach at 60 sends. Days 9-10 finish the 300-contact list and ship follow-ups. Day 11 is a US holiday: no cold sends, funnel fixes only. Day 12 sends to non-US agencies. Day 13 is the full push to accounts with two or more failures. Day 14 targets the first paid certificate and a delivery timing baseline. Days 15-21 add the Shopify-only niche, ship Agency Desk, publish two teardowns, fix selector accuracy and open an inbound path. Days 22-28 scale to 600 contacts, pitch subscriptions to every buyer, ship certificate v2 with a verify URL, run one subreddit channel test with a keep/kill decision, add drift alerts, and exhaust the list. Days 29-30 convert warm leads with a deadline angle, process refunds same day, reconcile Stripe against the TrustMRR-connected account and publish the teardown.

7. Revenue and profit scenarios

Three projections, inputs only. Conservative: 4 certificates at $99 = $396 gross, $0 refunds, $0 chargebacks, $20 payment fees, $0 ad spend, $30 operating cost. Base: 14 at $99 = $1,386 gross, $69 fees, $0 ad spend, $65 operating cost. Upside: 30 at $99 = $2,970 gross, $99 refund, $149 fees, $200 ad spend, $130 operating cost. Payment fees are modelled at 5% of gross to cover Stripe's 2.9% plus $0.30 and a non-US card buffer. Hackathon profit is gross minus refunds, chargebacks, fees and ad spend; business profit further subtracts operating cost. Every sale clears its marginal delivery cost of roughly $1-3.

These are projections from stated assumptions, not verified revenue. No customer, payment or traction exists at launch. Reaching $100,000 would need roughly 1,010 certificates at $99, which this plan does not project and does not claim.

8. Main risks and validation experiments

Free-audit freeloading is the biggest risk: prospects fix the two records themselves. Test by tracking repeat opens of share links without purchase; if fewer than 1 in 25 audited prospects pays after 150 contacts, rebuild the offer. Selector false negatives come second: run 40 known-good domains and pause outreach if more than 15% are misreported. Channel death from spam traps is third: compare 40 cold emails against 20 DMs and switch primary effort if reply rate stays under 3% after 150 sends. Placement disputes are fourth: state scope above checkout and refund without argument; stop and rewrite the scope statement if 2 of the first 20 buyers dispute on placement. Commoditisation is fifth: measure whether the free-report link outclicks the paid link by more than 5x across 100 sends, and reposition around the certificate alone if it does.

9. First 24-hour action plan

Hours 1-2: domain, Supabase schema, DoH resolver wrapper. Hours 3-6: SPF, DMARC, MX and PTR parsing plus the public checker page. Hours 7-10: 14-selector DKIM sweep, recipe library JSON, fingerprint display. Hours 11-16: recipe table with failure flags, share token, read-only share page. Hours 17-24: Stripe Payment Link and webhook, magic-link email, first certificate PDF template, one test-card purchase end to end. By hour 24 the founder has a payable product that produces a real certificate for a real domain — which is the only asset the day-6 outreach can honestly point at.

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 →