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

PitchSheet

PitchSheet turns your Google Sheet into a live, shareable proposal with auto-updating pricing and view analytics, so freelancers and agencies never send stale numbers again.

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.

Speculative6.42/10
MVP build (solo)
4 days
Launch price
$149
Sales to $1,000 revenue
7 customers
First paying customer
Direct, personalized LinkedIn DMs to freelance consultants and small agency owners, backed by two community posts.
Who pays

Independent consultants, freelance designers/developers and 1-10 person agencies in the US, UK, Canada and Australia who send 5-20 proposals a month and just had to regenerate one because pricing changed.

Biggest execution risk

Monetization potential 4.9/10

Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.

Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 12; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.1/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
$149
Solo build
4 days
30d base revenue
$1,488
30d hackathon profit
$1,414
Section 1 of 8

Product opportunity and positioning

Target customer

Independent consultants, freelance designers/developers and 1-10 person agencies in the US, UK, Canada and Australia who send 5-20 proposals a month and just had to regenerate one because pricing changed.

Why now

Low-code OAuth, serverless hosting and managed email make a live-document wedge buildable by one person in four days, and the buyer can approve $149 on a card in the same conversation.

Problem

Proposals are built in Google Docs or Canva, exported to PDF and emailed, so every price change forces a manual rebuild and resend, and the sender never learns whether the prospect opened the file.

Solution

Pick a template, connect a Google Sheet, map its pricing rows, and publish a unique mobile-friendly proposal URL whose pricing table reads live from that sheet; views and per-section time are logged and emailed via Resend.

Differentiation · Generic document builders produce a frozen artifact; PitchSheet keeps the pricing table bound to a spreadsheet so a single row edit propagates to every link already in a prospect's inbox, plus open analytics.

PitchSheet sells one outcome: a proposal link that is never out of date. Freelance consultants, independent designers and developers, and 1-10 person agencies send 5-20 proposals a month. They assemble them in Google Docs or Canva, export a PDF, email it, and rebuild the whole thing whenever a rate or scope line moves. They also learn nothing afterwards: no open signal, no idea which section the prospect read before going quiet.

The wedge is deliberately narrow. The original BUNKR insight still holds - static, exported documents rot the moment the underlying numbers change - but a general presentation platform has no urgent buyer. PitchSheet applies that insight to one artifact where staleness costs real money, the priced proposal, and to one buyer who can approve $149 on a card inside a single conversation. The differentiator is not templates or design. It is the Google Sheet as source of truth plus open tracking: edit a row, every shared link reflects it; a prospect opens the link, the founder gets an email with time on each section.

The JEV score of 64.2 (band C) reads true: speed to first revenue and solo build feasibility are the strong axes, monetization potential is the weak one. This plan answers that weakness three ways. First, the $299 Agency tier is pushed from day 8 rather than left as a footnote, because a 1-10 person shop has five seats to justify. Second, every message ties the price to one recovered deal rather than to document features. Third, a recurring plan is introduced for new buyers after the contest window, while founding members keep lifetime access - so the one-time launch offer stays exactly as scored, and the business does not end at day 30.

Section 2 of 8

Smallest sellable MVP

A founder-side dashboard that connects one Google Sheet, publishes one template-based proposal to a public URL with live pricing, and emails the owner on every view.

Must-have features

  • Template builder with intro, scope, pricing and terms blocks plus block reordering
  • Google Sheets OAuth connect, tab picker and column mapping to the pricing table
  • Publish to a unique public proposal URL that renders pricing live from the sheet
  • View logging with per-section dwell time
  • Resend email notification on first view and on repeat visits
  • Stripe Checkout for $149 and $299 one-time prices with webhook-driven account creation
  • Dashboard listing proposals with view counts, last-opened time and duplicate action

Explicitly out of scope

  • E-signature and contract management
  • CRM or pipeline tracking
  • Custom domains and white-labeling
  • Team roles beyond basic seat sharing
  • AI writing or content generation
  • Integrations other than Google Sheets
  • Prospect-facing comment threads

Demo flow (what the buyer sees)

  1. Founder signs up, pays $149 via Stripe Checkout, account is created by webhook
  2. Founder clicks Connect sheet and authorizes Google Sheets read access
  3. Founder picks a spreadsheet and tab, maps item, description, qty and unit price columns
  4. Founder picks a template, edits intro/scope/terms copy, orders blocks and publishes
  5. Public URL goes live with a pricing table rendering from the sheet
  6. Founder edits one price row in Google Sheets and the public table changes within a minute
  7. A test visitor opens the URL; founder receives a Resend email with device and per-section time
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres, Auth and Row Level SecurityGoogle Sheets API v4 via Google Cloud OAuth (sheets.readonly)Stripe Checkout plus webhooksResend transactional emailTailwind CSSVercel Cron for periodic sheet revalidation

Architecture

A Next.js app on Vercel does all rendering; Supabase holds users, proposals, sheet mappings, view events and section timings. Public proposal pages are server-rendered from cached sheet data stored in a proposals_cache row, refreshed on publish, on a 15-minute cron and on an owner-triggered refresh, so a prospect visit never blocks on a Google API call. OAuth tokens are stored encrypted per user and refreshed server-side. Stripe Checkout collects the one-time payment and the webhook writes the entitlement row that unlocks the dashboard. The public page posts view and dwell beacons to a lightweight endpoint that inserts into view_events and triggers one Resend email per prospect session.

Build steps

  1. Provision Vercel, Supabase and domain; scaffold Next.js with Tailwind and auth
  2. Create Stripe prices for $149 and $299, build Checkout session and webhook entitlement writer
  3. Register Google Cloud OAuth client with sheets.readonly and build the connect + token refresh flow
  4. Build sheet picker, tab picker and column mapping UI, storing the mapping JSON
  5. Build the template editor with ordered blocks persisted as JSON
  6. Build the public proposal route: resolve slug, read cache row, render blocks and pricing table
  7. Add cache refresh on publish, on cron and on manual refresh
  8. Add view and dwell beacons, view_events table and the Resend notification
  9. Build the dashboard: proposal list, per-section analytics, duplicate action
  10. Load test 50 concurrent public page views and a mid-session price edit

AI components

  • None in delivery; no LLM inference is used, which keeps marginal cost near zero
Hardest technical risk: Google OAuth verification and token refresh: an unverified app triggers an interstitial and refresh tokens can silently expire, breaking the live sync that is the entire product promise.
Section 3 of 8

Pricing and monetization

Founding Member

Entry offer
$149 one-time

For Solo freelancers and consultants sending proposals weekly

  • Unlimited live proposal links
  • Google Sheets pricing sync
  • View notifications and per-section analytics
  • Lifetime access
  • 30-day money-back guarantee

Agency

$299 one-time

For Agencies of up to 5 people

  • Everything in Founding Member
  • 5 team seats
  • Shared templates
  • Priority email support

Model: Two one-time lifetime tiers sold through Stripe Checkout during the 30-day window, with an Agency upgrade path.

First revenue offer: Founding member deal: $149 lifetime (normally $299), 30-day money-back, includes a free setup call where I connect your pricing sheet live on the call.

Expected ACV: $186

Upsell path: Founding members upgrade to Agency for a $150 delta when they add a second seat; after the contest window new buyers move to a recurring plan while founding members keep lifetime access.

Target customers
20
Revenue model
$2,980
Costs
$150
Profit model
$2,830
Section 4 of 8

First-customer acquisition

Primary channel

Direct, personalized LinkedIn DMs to freelance consultants and small agency owners, backed by two community posts.

Where to find them

  • LinkedIn search: 'freelance consultant', 'agency owner', 'independent consultant' filtered to US/UK/Canada/Australia and 1-10 employees
  • LinkedIn profiles listing 'proposal' or 'RFP' in the headline or recent posts
  • r/freelance and r/consulting posters who describe pricing or proposal problems
  • Indie Hackers product and milestone threads from solo consultants
  • MicroConf Connect and two freelance Slack/Discord communities
  • Bookkeeping and design-retainer freelancers who send monthly recurring proposals

Exact outreach motions

  • Send 20 personalized DMs daily with a first line referencing the prospect's actual service and one sentence on the stale-pricing problem
  • Follow up with non-responders after 3 days using a 45-second Loom showing a price edit propagating to a live link
  • Post a build-in-public thread on Indie Hackers on launch day with the Loom and the founding offer
  • Post a no-hard-sell r/freelance write-up of the stale-PDF problem and link the demo proposal in a comment
  • On demo calls, run the demo on the founder's own live proposal and send the Stripe link in-call, never later
  • Ask every buyer for one named referral in the welcome email

Message template

Hi {first_name} - saw you run {service} for clients. Quick question: when your rates change, do you rebuild and resend every proposal PDF? I built PitchSheet: it turns your Google Sheet into one live proposal link, so the pricing updates everywhere at once and you get an email when a prospect opens it. Founding deal is $149 lifetime (normally $299) with a 30-day money-back. Want a 2-minute demo?
Week-one goal: 100 prospects collected, 70 personalized DMs sent, 2 community posts live, first Stripe payment link sent.
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

Accounts, checkout and landing page

  • Create Next.js repo on Vercel and Supabase project; buy the pitchsheet domain.
  • Create Stripe $149 and $299 one-time prices, Checkout session and webhook entitlement writer.
  • Ship a landing page with the founding offer, guarantee and FAQ.
  • Confirm the Stripe account is the TrustMRR-connected account and take zero payments.

Deliverable: Live landing page plus working test-mode checkout

Day 2Sheets sync

Google OAuth and pricing table

  • Register Google Cloud OAuth client with sheets.readonly and submit the consent screen.
  • Build connect-sheet, tab picker and column mapping UI.
  • Persist the mapping JSON and fetch rows into a cache table.
  • Render a pricing table from the mapped rows on a private preview URL.

Deliverable: Sheet-driven pricing table rendering from real data

Day 3Proposal builder

Template, blocks and public route

  • Build the editor with intro, scope, pricing and terms blocks plus reordering.
  • Store proposal JSON in Supabase with a public slug.
  • Build the public route that renders blocks and the live pricing table.
  • Style the public page for mobile and print.

Deliverable: One real proposal published at a public URL

Day 4Analytics and email

Views, dwell time and notifications

  • Add view and dwell beacons writing to view_events.
  • Send the Resend view notification with device and per-section time.
  • Build the dashboard: proposal list, view counts, last-opened, duplicate action.
  • Add manual sheet refresh plus a 15-minute cron.

Deliverable: End-to-end product with notifications and dashboard

Day 5ShipMVP shipped

MVP deadline and live launch

  • Test with three of your own sheets, including a price edit mid-view.
  • Record a 90-second Loom of a price edit propagating to a live link.
  • Clear test data, publish the demo proposal, switch Stripe to live.
  • Post the launch thread on Indie Hackers.

Deliverable: PitchSheet publicly launched and accepting real payments

Day 6Prospecting

Build the list and start DMs

  • Build a 100-row prospect sheet: name, role, company size, LinkedIn URL, proposal evidence.
  • Search LinkedIn with the target filters and fill the sheet.
  • Send 20 personalized DMs using the offer message.
  • Log every send and reply in the same sheet.

Deliverable: 100 qualified prospects, 20 DMs sent

Day 7Outreach

Volume and community seeding

  • Send 25 more DMs, segmenting agency owners separately.
  • Post the build-in-public thread with the Loom.
  • Reply to every comment within 30 minutes.

Deliverable: 45 DMs sent, one community post live

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

Book calls and send payment links

  • Follow up with day-6 non-responders using the Loom link.
  • Book 3 demo calls and run them on your own live proposal.
  • Send the Stripe link inside the call, never after.
  • Start pitching the $299 Agency tier to shops with visible staff.

Deliverable: 3 demos booked, first payment link sent

Day 9Agency segment

Higher-ticket outreach

  • Send 30 DMs to agency owners quoting the $299 tier.
  • Post the stale-PDF write-up on r/freelance without a hard sell.
  • Answer all replies within 2 hours.

Deliverable: 30 agency DMs, one Reddit post live

Day 10Trust

Guarantee and onboarding speed

  • Add the 30-day money-back guarantee to every message and the landing page.
  • Onboard any buyer within 10 minutes of payment.
  • Ship the top friction fix reported in demos.

Deliverable: Onboarding checklist plus one shipped fix

Day 11Channels

Second and third channel seeding

  • Join MicroConf Connect and two freelance communities; answer 5 threads value-first.
  • Send 25 DMs and 10 follow-ups.
  • Ask every demo no-show for a one-line reason.

Deliverable: Two channels seeded, 35 touches sent

Day 12First saleFirst sale target

Close the first paying customer

  • Close at least one $149 founding-member sale through Stripe Checkout.
  • Send a 5-line welcome email that gets their first proposal live.
  • Ask for one named referral in the same email.

Deliverable: First verified payment collected

Day 13Activation

Time to first live link

  • Add a sample template so a new buyer publishes in under 5 minutes.
  • Send 30 DMs and 15 follow-ups.
  • Record a 3-minute build of a real customer proposal with permission.

Deliverable: Faster activation and 45 new touches

Day 14Review

Message performance

  • Tabulate DMs sent, reply rate, demo rate and close rate per angle.
  • Cut the weakest angle and keep the best.
  • Request a written testimonial from any buyer.

Deliverable: Message performance table with the winning angle

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

Cadence at 40 DMs per day

  • Run 40 DMs per day with the winning angle and two saved variants.
  • Add an Agency-tier proof block to the landing page.

Deliverable: 40 DMs per day cadence running

Day 16Content

One long-form post

  • Publish 'why your PDF proposal went cold' with a real analytics screenshot.
  • Cross-post to Indie Hackers and LinkedIn.

Deliverable: One long-form post live

Day 17New segment

Retainer senders

  • Build a 60-prospect list of bookkeepers and design-retainer freelancers.
  • Send 30 DMs to this segment.

Deliverable: 60-prospect list, 30 DMs sent

Day 18Paid test

Only if organic works

  • If organic reply rate exceeds 8%, put $50 into one sponsored post.
  • Log signups and cost per signup.
  • Otherwise keep ad spend at zero and add 20 DMs.

Deliverable: Documented paid-spend decision

Day 19Product

One unblocking feature

  • Ship the top requested feature under 3 hours of work.
  • Follow up on all unpaid demos with the guarantee.
  • Check delivery cost per customer stays below price.

Deliverable: One shipped feature, 5 follow-ups sent

Day 20Proof

Real social proof

  • Collect three permissioned quotes or screenshots from buyers.
  • Add a proof block to the landing page.
  • Fix any broken sheet sync reported by a customer.

Deliverable: Proof block live on the landing page

Day 21Midpoint

Tier decision

  • Send 40 DMs and review collected cash to date.
  • Decide whether Founding or Agency is the real engine.
  • Reallocate all outreach to the winning tier.

Deliverable: Midpoint review with tier decision

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

Landing page performance

  • Send 40 DMs and 20 follow-ups, targeting 5 conversations daily.
  • Put a 2-minute demo video at the top of the landing page.

Deliverable: Higher landing conversion, 60 touches

Day 23Expansion

Upgrades and re-engagement

  • Offer founding members an Agency upgrade at a $150 delta.
  • Contact everyone who opened a proposal but never replied, once.

Deliverable: Upgrade offer sent to all existing buyers

Day 24Operations

Support load

  • Write a repeatable onboarding script and cut activation under 5 minutes.
  • Fix every reported sheet sync issue the same day.

Deliverable: Onboarding script v2

Day 25Distribution

Video and referrals

  • Post a 60-second demo on LinkedIn and X.
  • Ask three buyers for a named referral introduction.

Deliverable: Two posts live, three referral asks sent

Day 26Scarcity

Closing window

  • Send 40 DMs with a last-week-of-founding-pricing angle.
  • Re-contact all unconverted demos with the guarantee.
  • Confirm Stripe pricing and links still work end to end.

Deliverable: Scarcity campaign live, 40 DMs sent

Day 27Refunds

Honor and learn

  • Honor any refund request within 24 hours and log the reason.
  • Fix the top refund cause or stop selling that segment.
  • Reply to every support email.

Deliverable: Refund log with one shipped fix

Day 28Reconciliation

Verified numbers

  • Reconcile Stripe balance against collected revenue; confirm every charge is inside the window.
  • Export the customer list and refund list for verification.
  • Confirm per-customer delivery cost stays below price.

Deliverable: Reconciled revenue ledger

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

Last outreach wave

  • Send 40 DMs and answer every open community thread.
  • Close remaining pipeline conversations before the deadline.
  • Verify no payment lands after 16 Dec 13:00 UTC.

Deliverable: Final pipeline closed out

Day 30Close

Report and recap

  • Send receipts and confirmations to all buyers.
  • Submit the revenue, refund and customer report for verification.
  • Publish a public 30-day recap post.

Deliverable: Final verified revenue report submitted

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: 3 paid customers from roughly 120 personalized DMs and 2 community posts, all on the $149 founding tier.
  • Base: 8 paid customers, a mix of 6 Founding at $149 and 2 Agency at $299, giving a blended ARPU of $186.
  • Upside: 20 paid customers, 16 Founding at $149 and 4 Agency at $299, giving a blended ARPU of $179, helped by one high-traffic community post.
  • All scenarios are one-time charges only; no recurring revenue is assumed inside the 30-day window.
  • Payment fees assumed at 5% blended of collected revenue, covering Stripe card fees and international card or currency conversion on small tickets.
  • Refunds: 0 in conservative, 0 in base, one $149 refund in upside under the 30-day guarantee.
  • Chargebacks: 0 in all scenarios; a dispute would be absorbed as an unmodelled cost.
  • Ad spend: $0 in conservative and base because acquisition is organic direct outreach; $150 in upside for one sponsored community post test.
  • Operating costs cover domain, Vercel, Supabase, Resend and Google API quota: $25 conservative, $50 base, $95 upside.
  • No customer, payment or revenue exists before launch day; every figure is a projection.
  • Delivery cost per customer stays far below the $149 price, so no sale is below cost.
  • No LLM inference is used in delivery, which keeps marginal cost per customer near zero.

Conservative

3 customers
$447
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$22
Paid marketing
$0
Hackathon profit
$425
Operating costs
$25
Business profit
$400

Base case

8 customers
$1,488
collected revenue · avg payment $186
Refunds
$0
Chargebacks
$0
Payment fees
$74
Paid marketing
$0
Hackathon profit
$1,414
Operating costs
$50
Business profit
$1,364

Optimistic

20 customers
$3,580
collected revenue · avg payment $179
Refunds
$149
Chargebacks
$0
Payment fees
$179
Paid marketing
$150
Hackathon profit
$3,102
Operating costs
$95
Business profit
$3,007

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,192
Payment fees (3.9%)
$46
Paid marketing
$0
Hackathon profit
$1,146
Business profit
$1,096

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.

These scenarios are projections derived from stated assumptions. They are not verified revenue, customers or traction, and no payment, customer or partnership exists at the time of writing.

Section 7 of 8

Main risks and validation experiments

Risk 1Google OAuth verification delays block the live sheet sync that is the core promise.

Mitigation

Submit the consent screen on day 2, run the app in testing mode with up to 100 test users, and build a CSV paste fallback for publishing.

Validation experiment

Have 5 external accounts complete the connect flow end to end by day 4 and record each failure point.

Kill criteria

If connect fails for more than 2 of 5 testers and no fix lands by day 6, ship the CSV fallback as the primary path.

Risk 2Buyers distrust a lifetime deal from an unknown solo founder.

Mitigation

Lead with the live demo Loom, state the 30-day money-back guarantee in every message, and publish the build openly.

Validation experiment

Send 60 DMs across two message angles and compare reply rate and objection type.

Kill criteria

If reply rate stays under 3% across both angles on 60 DMs, change the segment or the offer before spending more outreach.

Risk 3The product is perceived as a feature and not worth $149.

Mitigation

Price against one recovered deal, ask in every demo what a stale proposal cost them, and keep the Agency tier visible.

Validation experiment

Run 10 demo calls and record how many convert and which objection repeats.

Kill criteria

If fewer than 1 in 10 demos converts after 15 calls, cut the price to $49 or bundle setup as paid scope.

Risk 4LinkedIn outreach is limited or flagged as spam, cutting reach.

Mitigation

Keep volume near 20-40 personalized DMs per day, personalize the first line, and run community channels in parallel.

Validation experiment

Track reply rate per channel and watch for restricted-account warnings during week 2.

Kill criteria

If the account is restricted, shift all effort to email plus Indie Hackers and Reddit within 24 hours.

Risk 5Google Sheets API rate limits or schema changes break the pricing sync for paying customers.

Mitigation

Cache sheet data in Postgres, refresh on publish and cron, add manual refresh, and surface the last-synced timestamp on each proposal.

Validation experiment

Load test 50 concurrent public views plus a mid-session price edit before launch day.

Kill criteria

If sync fails during the day-5 test, ship manual refresh as primary and cap cache refresh at 15 minutes.

Risk 6Prospects or customers object to view tracking as a privacy issue.

Mitigation

Disclose tracking in the public page footer, store no cookies for prospects, and keep analytics at section level, not individual reading.

Validation experiment

Ask 5 buyers directly whether the disclosure blocks their use of the link.

Kill criteria

If more than 2 of 5 say the disclosure would stop them sharing, add a per-proposal analytics toggle.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Vercel and Supabase projects and deploy the Next.js scaffold.
  • Buy the pitchsheet domain and attach it.

Output: Deployed scaffold reachable on the real domain

Hours 3-6

  • Confirm the Stripe account is the TrustMRR-connected account and create $149 and $299 one-time prices.
  • Build the Checkout session and the webhook that writes the entitlement row.

Output: Test-mode checkout that grants access via webhook

Hours 7-11

  • Write and deploy the landing page with the founding offer, guarantee, FAQ and demo placeholder.
  • Draft the 100-prospect LinkedIn search and open the tracking sheet.

Output: Live landing page plus the prospect sheet template

Hours 12-16

  • Register the Google Cloud OAuth client with sheets.readonly and configure test users.
  • Build the connect flow and store the encrypted token for one test account.

Output: Working Google Sheets OAuth connect for a test account

Hours 17-24

  • Build the column mapping and render a pricing table from the test sheet on a preview URL.
  • Send the OAuth consent screen for verification and log the first 20 prospects.

Output: Preview URL showing live pricing plus 20 prospects logged

Complete report

Full 30-day launch report

Read the full generated report

PitchSheet - 30-Day Launch Report

Ship or Die $100K Hackathon, 16 Nov 2026 13:00 UTC to 16 Dec 2026 13:00 UTC. Solo founder. Every revenue and profit figure in this report is a projection derived from stated assumptions - not verified revenue, customers, partnerships or traction.

1. Product opportunity and positioning

PitchSheet sells one outcome: a proposal link that is never out of date. Independent consultants, freelance designers and developers, and 1-10 person agencies send 5-20 proposals a month. They build them in Google Docs or Canva, export a PDF, email it, and rebuild the document every time a rate moves. Afterwards they learn nothing - no open signal, no idea which section the prospect read before going quiet.

The wedge stays narrow on purpose. The original BUNKR insight holds: exported, static documents rot the moment the numbers behind them change. The mistake was selling a general presentation platform to everybody. PitchSheet applies the same insight to the single artifact where staleness costs money - the priced proposal - and to the buyer who can approve $149 on a card in one conversation.

The JEV score of 64.2 (band C) reads true: speed to first revenue and solo build feasibility are the strong axes; monetization potential is the weak one. This plan answers that weakness rather than ignoring it. The $299 Agency tier gets pitched from day 8, every message is priced against one recovered deal instead of document features, and a recurring plan is introduced for buyers after the window while founding members keep lifetime access.

2. Smallest sellable MVP

The sellable unit is a founder-side dashboard that connects one Google Sheet, publishes one template-based proposal at a public URL with pricing rendered live from that sheet, and emails the owner on every view. Nothing else gets built before day 5.

Seven features carry it: a block editor (intro, scope, pricing, terms) with reordering; Google Sheets OAuth connect with column mapping; publish to a slug-rendered proposal page; view logging with per-section dwell time; Resend notifications; Stripe Checkout with webhook entitlement; and a dashboard showing view counts, last-opened time and a duplicate action for repeat proposals.

Explicitly out of scope for the whole 30 days: e-signature, CRM, custom domains, white-labeling, AI writing, non-Sheets integrations and prospect comment threads. Each of those would add a week and move the buyer from a solo consultant to a procurement committee.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres, auth and row security, Google Sheets API v4 behind OAuth with the sheets.readonly scope, Stripe Checkout plus webhooks, Resend for email, Tailwind for UI, and a Vercel cron for revalidation.

The critical architectural decision is caching. Public proposal pages render from a Postgres cache row holding the mapped sheet values, refreshed on publish, on a 15-minute cron, and on manual refresh. A prospect visit never blocks on a Google API call, and an API outage degrades to a slightly stale table instead of a broken page. OAuth tokens are stored encrypted per user and refreshed server-side. The Stripe webhook writes the entitlement row that unlocks the dashboard, so payment and access cannot drift. View and dwell beacons post to a thin endpoint that inserts into view_events and fires one Resend email per prospect session.

The hardest technical risk is not the editor - it is OAuth: an unverified app shows an interstitial, and refresh tokens expire silently, which breaks exactly the promise being sold. Submit the consent screen on day 2 and test the full connect flow with five external accounts by day 4. No LLM inference is used in delivery, so marginal cost per customer stays near zero.

4. Pricing and monetization

Two one-time tiers, sold through Stripe Checkout: Founding Member at $149 for solo consultants, and Agency at $299 for up to 5 seats with shared templates. Both include unlimited live links, sheet sync, view notifications and analytics; both carry a 30-day money-back guarantee.

The Agency tier is not decoration. On day 8 it becomes the primary pitch to shops with visible staff, because five seats justify the higher price and one Agency sale equals two Founding sales. Blended ARPU across the base scenario is $186.

After the contest window, new buyers move to a recurring plan while founding members keep lifetime access. That gives the business a second act without changing the offer being tested in these 30 days. No money is collected before launch day, and every charge runs through the TrustMRR-connected Stripe account.

5. First-customer acquisition

One channel: personalized LinkedIn DMs, backed by two community posts. Build a 100-row prospect sheet from LinkedIn searches for freelance consultants and agency owners in the US, UK, Canada and Australia at 1-10 employees, plus r/freelance and Indie Hackers posters who describe pricing or proposal problems.

The message names the prospect's actual service, states the stale-pricing problem in one line, describes the live link and the open notification, and ends with the $149 founding deal plus the guarantee and a two-minute demo ask. Non-responders get one follow-up after three days with a 45-second Loom of a price edit propagating to a live link. Demo calls run on the founder's own live proposal and the Stripe link goes out inside the call, never after.

Week-one goal: 100 prospects collected, 70 DMs sent, two community posts live, first payment link sent.

6. Thirty-day execution roadmap

Days 1-5 are pure build. Day 1 ships the landing page and test-mode checkout. Day 2 delivers the OAuth connect and column mapping. Day 3 publishes a real proposal at a public URL. Day 4 adds view tracking, Resend notifications and the dashboard. Day 5 is the MVP deadline: three real sheets tested including a mid-view price edit, a 90-second Loom recorded, Stripe switched to live, launch thread posted.

Days 6-14 convert. The prospect list is built on day 6 and DM volume ramps from 20 to 45 per day. Demos start on day 8 and the Agency tier is pitched the same week. The first-sale target is day 12 - one $149 checkout, an onboarding email, and a referral ask. Day 14 reviews reply rate, demo rate and close rate per message angle and kills the weakest.

Days 15-21 scale. Cadence hits 40 DMs per day on the winning angle, a long-form post and a 60-second video go out, and a retainer-sender segment (bookkeepers, design retainers) opens a second list. A $50 sponsored post runs only if organic reply rate clears 8%. Day 21 is the midpoint tier decision.

Days 22-30 close and reconcile. Upgrades are offered to existing buyers, activation drops under five minutes, scarcity messaging runs in the final week, refunds are honored within 24 hours, and days 28-30 reconcile Stripe against collected revenue, confirm every charge sits inside the window, and submit the verification report.

7. Revenue and profit scenarios

All three scenarios are projections from stated assumptions.

Conservative - 3 customers at $149 blended ARPU: $447 gross, $22 payment fees, no refunds, no ad spend, $25 operating cost.

Base - 8 customers, 6 Founding plus 2 Agency, $186 blended ARPU: $1,488 gross, $74 payment fees, no refunds, no ad spend, $50 operating cost.

Upside - 20 customers, 16 Founding plus 4 Agency, $179 blended ARPU: $3,580 gross, $179 payment fees, one $149 refund, $150 ad spend, $95 operating cost.

Payment fees assume a 5% blend of Stripe card fees plus international conversion on small tickets. Ad spend is zero in conservative and base because acquisition is organic outreach. Operating cost covers domain, hosting, database, email and Google API quota - it does not include founder time, which is not deducted.

8. Main risks and validation experiments

OAuth verification delay: submit on day 2, test with five external accounts by day 4, keep a CSV paste fallback. If connect fails for more than two of five testers by day 6, the fallback becomes primary.

Lifetime-deal distrust: lead with the Loom and the guarantee. Send 60 DMs across two angles and compare reply rates. Below 3% on both, change segment or offer before spending more outreach.

Feature-not-product perception: run 10 demo calls, record objections. Fewer than one conversion in fifteen calls means the price drops to $49 or setup becomes paid scope.

Channel restriction: hold volume at 20-40 personalized DMs daily and run communities in parallel. A restricted account means shifting to email plus Indie Hackers and Reddit within 24 hours.

API fragility: cache sheet data, expose last-synced timestamps, load test 50 concurrent views plus a mid-session edit before launch.

Tracking objections: disclose in the page footer, store no prospect cookies, and add a per-proposal analytics toggle if more than two of five buyers say the disclosure would stop them sharing.

9. First 24-hour action plan

Hours 1-2: create Vercel and Supabase projects, deploy the Next.js scaffold, buy and attach the domain.

Hours 3-6: create the $149 and $299 Stripe prices, build Checkout and the webhook entitlement writer, confirm the account is the TrustMRR-connected one.

Hours 7-11: deploy the landing page with the founding offer, guarantee and FAQ; draft the prospect sheet.

Hours 12-16: register the Google OAuth client with sheets.readonly, build the connect flow, store one test token.

Hours 17-24: build column mapping and render a live pricing table on a preview URL; submit the consent screen; log the first 20 prospects.

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 →