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

CostClause

CostClause turns a Terraform plan or a 12-question stack form into a branded, client-signable monthly cloud cost estimate — low/expected/high ranges plus an assumptions-and-change-clause page — so small cloud agencies stop eating fixed-bid overages.

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.15/10
MVP build (solo)
5 days
Launch price
$39
Sales to $1,000 revenue
26 customers
First paying customer
Reverse-demo DM to agencies already publishing fixed-price cloud work, with a finished branded PDF attached before the first message.
Who pays

Owner or lead engineer at a 2-25 person cloud/dev agency or MSP (US/EU) selling fixed-price builds and monthly run contracts, triggered by a proposal, RFP or scope change due this week.

Biggest execution risk

Market demand 4.3/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

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

Product opportunity and positioning

Target customer

Owner or lead engineer at a 2-25 person cloud/dev agency or MSP (US/EU) selling fixed-price builds and monthly run contracts, triggered by a proposal, RFP or scope change due this week.

Why now

The AWS Price List Bulk API is public and cacheable, so a deterministic dollar-per-resource engine is days of work, and the buyer's trigger — a quote due this week — recurs weekly and is owned by one person with no procurement or security review.

Problem

Agencies quote a fixed monthly infrastructure number from memory, the real bill lands far above it, and the agency absorbs the difference because there is no fast way to price a Terraform plan and no client-signed record of the assumptions.

Solution

Upload terraform plan JSON or answer a 12-question stack form; a deterministic AWS price engine returns a co-branded PDF and share link with low/expected/high monthly ranges, a per-service table, top-5 cost drivers, and a one-page Cost Assumptions & Change Clause the client approves in-browser.

Differentiation · The free AWS calculator is manual, unbranded and produces nothing the client signs; CostClause prices the exact plan the agency already wrote and adds a signed assumptions page the calculator cannot produce.

Product opportunity and positioning

CostClause sells into a moment, not a market. A 2-25 person cloud agency has just finished a Terraform plan for a fixed-price build and needs a monthly infrastructure number for a proposal, an RFP or a scope-change note. Today that number comes from memory or from the free AWS Pricing Calculator pasted into a Google Doc. When the bill arrives three times higher, nothing in writing says what the quote assumed, and the agency absorbs the delta.

Two conditions make this sellable now. The AWS Price List Bulk API is public and cheap to cache, so a deterministic dollar-per-resource engine is days of work rather than a data-licensing problem. And the trigger is weekly and personally owned by the agency lead: a quote due this week. No procurement, no security review, no engineering adoption campaign.

Positioning is narrow on purpose. CostClause is not a FinOps dashboard, not a pull-request cost comment, not a recurring client-reporting service. It is a branded PDF plus a signed approval link. The differentiator is page two: a Cost Assumptions & Change Clause the client approves in-browser with a typed name and a timestamp. The number is the commodity; the signature is the product, and the free calculator cannot produce it.

JEV scores the concept 61.5/100 (band C, confidence 0.62), strongest on speed to first revenue (8.57) and reachable customers (7.07), weakest on market demand (4.33) and operational simplicity (4.5). The 30 days below answer that directly: reverse-demo selling from day 8, and deliberately manual concierge delivery while volume is under 25 accounts.

Smallest sellable MVP

One page, one upload, one PDF. The buyer drops a terraform plan JSON onto a page, or answers twelve questions about the stack, and receives within minutes a co-branded PDF and hosted share link containing a monthly AWS total in low/expected/high ranges, a per-service table, the top five cost drivers, and the approval clause. Eight services are priced: EC2, RDS, S3, EBS, ELB, Lambda, CloudWatch and NAT. Everything else is labelled not priced rather than guessed.

Not built: no AWS account connection, no bill ingestion, no CI step, no Azure or GCP, no dashboards, no anomaly alerts, no team roles. Each adds a credential or trust cycle a solo founder cannot close in 30 days and a proposal deadline does not require.

Flow: upload plan.json, normalizer emits a flat billable list, engine computes three ranges, renderer applies logo and colors, clause page fills editable variables, client opens the signed link, types a name, approves, and both parties get a timestamped confirmation.

Technical implementation plan

Next.js on Vercel, Neon Postgres, Stripe Checkout and Billing, Resend, React-PDF, and a cached price table from the AWS Price List Bulk API. Terraform plan JSON is flattened with hcl2json plus a normalizer mapping resource blocks to SKU, region and quantity rows.

Five build days. Day one, ingestion. Day two, pricing with 0.7x, 1.0x and 1.6x multipliers and ten fixtures checked by hand against the public calculator. Day three, the branded renderer and the twelve-question form. Day four, the assumptions page, typed-name approval, timestamp and IP capture, expiring signed links. Day five, Stripe, metering, delivery email, landing page.

The hardest risk is SKU matching. Terraform gives an instance type and a region; AWS gives a wall of SKUs, and a confident wrong number destroys the only asset. Mitigation: cache only eight services, fail loudly to not priced instead of guessing, and run the ten hand-verified fixtures on every deploy. No model sits in the pricing or delivery path; numbers stay deterministic, with an optional LLM drafting assumption bullets, off by default.

Pricing and monetization

Two tiers. Single Estimate at $39 one-time for a freelancer quoting one project: one branded PDF, one approval link, the clause page. Studio at $99 per month for a 2-25 person agency: unlimited estimates, saved brand profile, approval links, version diffs at scope change, and a concierge build for the first ten accounts.

$99 sits under the owner's approval threshold, so nobody needs a finance review to buy, and it is less than an hour of an agency's billable rate. The offer to send this week: the first branded estimate free, then Studio. One-time purchases count as upside and stay out of the projections. Growth path: more client estimates per account, then a per-seat price once a second person starts quoting.

First-customer acquisition

The only channel is reverse-demo DM. Build a 60-agency list from Clutch cloud-consulting listings, AWS Partner Network listings and LinkedIn searches for FinOps and cloud consultants at 2-25 people. For fifteen of them, read a public case study, price a stack of the same shape, render it with their logo and colors, and attach the finished PDF to a three-line message. The work is already done when they read it.

Message: 'I priced a stack like the one in your case study: monthly range, per-service table, and an assumptions page your client signs. PDF attached, it is yours. Want the next one free?'

Supporting motions: a five-free-cost-sheets post in r/msp, r/aws and two MSP Slacks, and a 72-hour follow-up showing the same stack at a 4x range framed as overage exposure. Week-one goal: fifteen sends, five free builds, one paying account by day 8.

30-day execution roadmap

Week 1, days 1-5, is build: ingestion, engine, renderer, signature layer, Stripe. It ends with a live product that can take money. Days 6-7 build the list and fifteen personalized PDFs.

Week 2, days 8-14, is the first revenue push. Batch one out day 8, community drop day 9, concierge delivery day 10, the exposure follow-up day 11, batch two day 12, funnel instrumentation day 13, estimate versioning day 14 so a scope change becomes a second sellable artifact.

Week 3, days 15-21, is accuracy and objections: batch three on a QBR angle, a better range model, explicit not-priced handling, a public samples page, batch four, and a written midpoint retro that kills any channel with zero replies after 30 sends.

Week 4, days 22-28, is wave two: non-responders, list expansion to 100, saved brand profiles, DOCX and CSV exports, a resale-margin angle, referral asks, hardening, and a 90-second demo video.

Days 29-30 close the window: a 20-prospect final wave with a 48-hour $39 offer, then Stripe reconciliation against TrustMRR and a public recap using only real figures.

Revenue and profit scenarios

All three scenarios are projections built from stated assumptions, not verified revenue. There are no customers today.

Conservative: 3 Studio accounts at $99, $297 gross, $12 in processing fees, $25 operating. Base: 10 accounts, $990 gross, $39 fees, $45 operating. Upside: 25 accounts, $2,475 gross, $50 refunds, $97 fees, $150 of paid promotion and $90 operating, giving $2,178 hackathon profit and $2,088 business profit.

The entire spread is one variable: whether 60 targeted DMs carrying finished artifacts produce 3, 10 or 25 paying agencies. Everything else is small. Payment fees assume Stripe at 2.9% plus $0.30, blended to roughly 4% on international cards. Hosting is Vercel, Neon, PDF rendering, Resend and a domain.

Risks and validation experiments

Free-tool sufficiency: the AWS calculator plus a Google Doc may be good enough. Test by sending ten DMs offering only the free PDF with no product behind it and counting replies asking how it was made. Stop if fewer than two of ten respond.

SKU accuracy: price ten public reference stacks by hand and diff against the engine; anything above 10% variance blocks that service from launch. Ranges read as guesses: put the assumptions above the fold and ask five free-build recipients whether the range is credible; stop the range format if three call it arbitrary.

Sporadic proposal cycles: ask every paying account for their next quote date; if none names a date within 30 days, make the $39 one-time the primary tier. Concierge overload: cap at five builds per week and time each one; anything above 30 minutes becomes the next product feature.

First 24-hour action plan

Hours 1-2: claim the domain, create Vercel and Neon projects, confirm the TrustMRR-connected payment account is ready, put a one-paragraph landing page online.

Hours 3-5: pull the AWS Price List bulk index for us-east-1 and eu-west-1 and write the normalizer for the eight covered services; output a CLI that turns a sample plan.json into a flat billable list.

Hours 6-8: build the price table and three usage multipliers, hand-verify ten resources against the public calculator, and commit the fixture suite.

Hours 9-11: build the 60-row prospect sheet with site, published stack, contact route and trigger event.

Hours 12-14: generate one complete branded PDF for a synthetic agency stack, end to end, and read it as a client would. That artifact goes into the first DM tomorrow.

Section 2 of 8

Smallest sellable MVP

Upload a terraform plan JSON or fill a 12-question stack form and receive within minutes a co-branded PDF plus hosted share link with a monthly AWS total in low/expected/high ranges, a per-service table, top-5 cost drivers, and a one-page Cost Assumptions & Change Clause the client approves in-browser.

Must-have features

  • Terraform plan JSON parser covering EC2, RDS, S3, EBS, ELB, Lambda, CloudWatch and NAT
  • 12-question stack form as the no-Terraform input path
  • Deterministic AWS price engine with 0.7x/1.0x/1.6x usage multipliers, region-aware, cached price table
  • Branded renderer: agency logo, colors, per-service table, range bars, top-5 cost drivers, print-to-PDF
  • Editable Cost Assumptions & Change Clause page with typed-name client approval, timestamp and IP
  • Signed expiring share link for the hosted estimate
  • Estimate versioning with a v1-to-v2 monthly total diff for scope changes
  • Stripe Checkout for a $39 one-time pack and a $99/mo subscription with per-account metering
  • Resend delivery email carrying the PDF and approval link

Explicitly out of scope

  • No AWS/GCP account connection or bill ingestion
  • No pull-request comments, CI steps or auto-fix PRs
  • No Azure or GCP pricing in v1
  • No optimization recommendations, anomaly alerts or dashboards
  • No team roles, SSO or procurement features
  • No MCP or agent interface
  • No recurring white-label client reporting

Demo flow (what the buyer sees)

  1. Agency uploads terraform plan JSON or answers the 12-question stack form
  2. Normalizer produces a flat billable resource list
  3. Price engine computes low, expected and high monthly totals
  4. Renderer applies agency logo and colors and builds the PDF
  5. Clause page generates editable assumptions and change variables
  6. Client opens the signed share link, types their name and approves
  7. Both parties receive a timestamped confirmation email with the link
Build plan

Technical implementation plan

Stack

Next.js 14 on VercelNeon PostgresAWS Price List Bulk API with a cached price tablehcl2json plus a custom Terraform plan normalizerReact-PDF for the artifact rendererStripe Checkout and BillingResend for delivery emailVercel Blob for signed PDF storage

Architecture

A single Next.js app on Vercel serves the upload page, the stack form and the signed estimate link. A serverless route normalizes terraform plan JSON into a flat resource list, which the pricing module joins against a Postgres price table seeded from the AWS Price List Bulk API and filtered to eight services in two regions. The pricing module applies three usage multipliers and returns three totals plus a per-service breakdown. The renderer turns that structure into a branded PDF stored in blob storage behind a signed, expiring URL. The clause page stores editable assumptions, and an approval route writes typed name, timestamp and IP against the estimate record. Stripe webhooks flip the account to paid and meter estimate counts.

Build steps

  1. Seed Postgres with on-demand prices for eight services in us-east-1 and eu-west-1 from the public bulk index
  2. Write the hcl2json wrapper and normalizer mapping resource blocks to SKU, region and quantity rows
  3. Implement the pricing module with low/expected/high multipliers and ten hand-verified fixtures
  4. Build the upload page and the 12-question stack form
  5. Build the branded PDF renderer with logo, colors, per-service table, range bars and top-5 drivers
  6. Generate the Cost Assumptions & Change Clause page with editable variables
  7. Add typed-name approval capturing timestamp and IP, and issue expiring signed share links
  8. Integrate Stripe Checkout for the $39 one-time and $99 monthly tiers with per-account metering
  9. Wire Resend delivery email and webhook-triggered PDF generation
  10. Ship estimate versioning with a v1-to-v2 diff view
  11. Deploy to Vercel with Neon and add an uptime check on the generate and checkout routes

AI components

  • Optional LLM copy assist that drafts the plain-English assumption bullets from the resource list, off by default; no model touches pricing or delivery
Hardest technical risk: SKU matching between a Terraform resource block and the correct AWS price row. A plausible but wrong match produces a confident wrong number and destroys the product's only asset, so unmatched resources must fall through to an explicit not-priced state rather than an estimate.
Section 3 of 8

Pricing and monetization

Single Estimate

Entry offer
$39 one-time

For Freelancer or solo consultant quoting a single project

  • One branded PDF estimate
  • Hosted client approval link
  • Assumptions and change clause page

Studio

$99 / month

For 2-25 person cloud agency producing proposals every week

  • Unlimited estimates
  • Branding and logo upload
  • Client approval links
  • Version diffs at scope change
  • Concierge build for the first 10 accounts

Model: Self-serve two-tier: a $39 one-time estimate pack for freelancers and a $99/month Studio subscription with unlimited branded estimates and approval links.

First revenue offer: Your first branded client-ready estimate free within 12 hours: send the plan file or answer 12 questions, get the signed-link PDF back, keep it and send it to your client. Then $99/month for Studio.

Expected ACV: $99

Upsell path: Same agency adds more client estimates per month, then a per-seat price once a second person produces quotes, then an annual prepay at ten months for agencies quoting every week.

Target customers
22
Revenue model
$2,178
Costs
$120
Profit model
$2,058
Section 4 of 8

First-customer acquisition

Primary channel

Reverse-demo DM to agencies already publishing fixed-price cloud work, with a finished branded PDF attached before the first message.

Where to find them

  • Clutch cloud-consulting listings filtered to 2-25 employees in US/EU
  • AWS Partner Network directory listings for small MSPs
  • LinkedIn search for FinOps consultant and cloud consultant at 2-25 person firms
  • Agencies publishing fixed-price AWS migration packages on their own sites
  • r/msp and r/aws threads where owners ask how to quote cloud costs
  • Two MSP Slack or Discord communities

Exact outreach motions

  • Build a 60-agency list with site, published stack, contact route and trigger event
  • Pick 15, read one public case study each, and price a stack of the same shape
  • Render each estimate with that agency's logo and colors and export the PDF
  • Send a 3-line LinkedIn DM with the PDF attached and no deck
  • Email the same 15 from the founder address as a fallback two days later
  • Post a five-free-cost-sheets offer in r/msp, r/aws and two MSP Slacks
  • Deliver every free build within 12 hours and ask for a yes/no on a $99 month
  • Send a 72-hour follow-up showing the same stack at a 4x range as overage exposure

Message template

I priced a stack like the one in your case study: monthly range, per-service table, and an assumptions page your client signs. PDF attached, it is yours to send. Want the next one free?
Week-one goal: 15 reverse-demo DMs sent, 5 delivered free builds, 1 paying Studio account by day 8.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 830 days planned
Week 1 · Build & validate · 7 days
Day 1Price engine core

Terraform ingestion

  • Pull the AWS Price List bulk index for us-east-1 and eu-west-1.
  • Write the hcl2json wrapper and normalizer for the eight covered services.
  • Define the flat billable resource schema in Neon.

Deliverable: CLI that prints a flat billable resource list from a sample plan.json.

Day 2Deterministic pricing

Price table and multipliers

  • Cache on-demand prices into Postgres keyed by service, SKU and region.
  • Apply 0.7x, 1.0x and 1.6x usage multipliers for low, expected and high.
  • Hand-verify ten resources against the public AWS calculator.

Deliverable: Price engine with a passing ten-fixture test suite.

Day 3Branded artifact

Renderer and stack form

  • Scaffold Next.js on Vercel with Neon and a signed upload route.
  • Build the 12-question stack form as the no-Terraform path.
  • Render logo, colors, per-service table, range bars and top-5 drivers.

Deliverable: A branded PDF generated from a realistic agency stack.

Day 4Signature layer

Assumptions and approval

  • Generate the Cost Assumptions & Change Clause page with editable variables.
  • Add typed-name approval capturing timestamp and IP.
  • Issue signed, expiring share links.

Deliverable: An estimate link a client can approve in the browser.

Day 5Payments and launchMVP shipped

Ship the paid product

  • Wire Stripe Checkout for $39 one-time and $99 per month.
  • Meter estimates per account and gate the PDF behind payment.
  • Wire Resend delivery email and publish the landing page.

Deliverable: CostClause live and able to take money.

Day 6Prospect list

60 agencies

  • Collect Clutch cloud-consulting listings at 2-25 employees, US and EU.
  • Add AWS Partner Network listings and LinkedIn searches.
  • Log name, site, published stack, contact route and trigger per row.

Deliverable: 60-row prospect sheet with contact routes.

Day 7Reverse demos

15 personalized PDFs

  • Read one public case study for each of 15 agencies.
  • Generate a branded estimate using their logo and colors.
  • Export the PDF and draft the 3-line DM for each.

Deliverable: 15 finished PDFs and 15 drafted messages.

Week 2 · Launch & first sale · 7 days
Day 8First sendsFirst sale target

Outreach batch 1

  • Send 15 LinkedIn DMs with the PDF attached.
  • Email the same 15 from the founder address as a fallback.
  • Start a 72-hour follow-up timer in the sheet.

Deliverable: 15 sends logged and the first paying account targeted.

Day 9Community drop

Free builds

  • Post the five-free-cost-sheets offer in r/msp and r/aws.
  • Post in two MSP Slack or Discord communities.
  • Reply to every response within 2 hours with an intake form.

Deliverable: At least 5 inbound free-build requests logged.

Day 10Concierge delivery

Manual builds

  • Deliver each free build within 12 hours, under 20 minutes of work each.
  • Log every question and objection verbatim.
  • Ask each recipient for a yes/no on a $99 month.

Deliverable: 5 delivered PDFs and a written objection log.

Day 11Exposure follow-up

72-hour nudge

  • Send the 4x range version of the same stack framed as overage exposure.
  • Add one line: your client signs the assumption page, not the invoice.
  • Track opens and replies in the sheet.

Deliverable: Second touch sent to all batch-1 prospects.

Day 12Batch 2

Outreach batch 2

  • Generate and send 15 more reverse-demo DMs.
  • Target agencies publishing fixed-price AWS migration packages.
  • Offer the same first-estimate-free term.

Deliverable: 30 cumulative sends logged.

Day 13Funnel

Instrumentation

  • Add event logging for visit, upload, generate, paywall and paid.
  • Build a one-screen funnel view over Neon.
  • Tag every signup with its acquisition source.

Deliverable: Working funnel view on real numbers.

Day 14Versioning

Scope-change diff

  • Ship estimate v2 with a diff of monthly total against v1.
  • Show added and removed resources with their deltas.
  • Email both parties on approval.

Deliverable: Version diff live for existing accounts.

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

QBR angle

  • Send 15 DMs to AWS and GCP partners framed around the QBR cost slide.
  • Attach a two-client sample pack.
  • Book any 30-minute calls offered.

Deliverable: 45 cumulative sends and a call list started.

Day 16Accuracy

Range quality

  • Add data-transfer and request-volume assumptions to the range model.
  • Surface those assumptions on the clause page.
  • Re-run fixtures against the public calculator.

Deliverable: Range model v2 with documented inputs.

Day 17Transparency

Unpriced resources

  • Show unpriced resources explicitly instead of omitting them.
  • Let users override any assumption inline.
  • Re-render the PDF with overrides applied.

Deliverable: No silent gaps in a generated estimate.

Day 18Proof page

Public samples

  • Publish three full sample PDFs built on synthetic stacks.
  • Add a what-the-client-signs section with the clause page.
  • Link the page from every DM.

Deliverable: Public samples page live.

Day 19Batch 4

Outreach batch 4

  • Send 15 DMs to MSPs using monthly run-contract language.
  • Open with the scope-change diff rather than the estimate.
  • Log replies and objections.

Deliverable: 60 cumulative sends logged.

Day 20Objection fixes

Copy and product

  • Rewrite landing copy around the top-3 objections from the log.
  • Ship the two smallest product fixes those objections imply.
  • Update the DM first line to match.

Deliverable: Revised landing page and DM template.

Day 21Midpoint retro

Numbers review

  • Review paid accounts, MRR, refunds and unanswered objections.
  • Kill any channel with zero replies after 30 sends.
  • Set the day-30 target from actual conversion.

Deliverable: Written midpoint decision memo.

Week 4 · Scale what works · 7 days
Day 22Wave two

Non-responders and expansion

  • Re-contact all non-responders with a different sample stack.
  • Extend the prospect list from 60 to 100 agencies.
  • Send 15 new DMs.

Deliverable: 75 cumulative sends logged.

Day 23Brand profile

Repeat friction

  • Add a saved brand profile with logo, colors, footer and contact.
  • Auto-apply it to every new estimate.
  • Track time-to-first-PDF per account.

Deliverable: Brand profiles shipped and measured.

Day 24Exports

Proposal appendix

  • Add DOCX and CSV export of the per-service table.
  • Add a copy-ready assumptions paragraph.
  • Test the output in Google Docs and Word.

Deliverable: Two new export formats live.

Day 25Resale angle

Agency margin

  • Send 5 notes showing how an agency rebills the PDF to its client.
  • Include a one-page margin example from a sample estimate.
  • Ask for one pilot client account.

Deliverable: 5 resale-angle sends logged.

Day 26Referrals

Existing accounts

  • Ask every paying account for one intro to another agency owner.
  • Offer one free month for a converted intro.
  • Follow up on intros within 24 hours.

Deliverable: Referral asks sent to all paying accounts.

Day 27Hardening

Reliability

  • Add graceful failure for malformed or oversized plan JSON.
  • Add an empty-state guide for the stack form.
  • Set an uptime check on the generate and checkout routes.

Deliverable: Error-path coverage on both critical routes.

Day 28Demo video

Proof in motion

  • Record a 90-second Loom from plan upload to signed PDF.
  • Embed it on the landing page and in the follow-up email.
  • Cut a 15-second clip for community posts.

Deliverable: Demo video live and linked.

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

Close the window

  • Send 20 DMs to warmest leads with a 48-hour $39 Single Estimate offer.
  • Email all free-build recipients a one-click upgrade link.
  • Post the offer once in each community that replied.

Deliverable: Final outreach wave sent.

Day 30Reconcile

Close and document

  • Reconcile Stripe payouts against TrustMRR records.
  • Publish a public 30-day numbers post using only real figures.
  • Write the post-hackathon plan for the top-converting channel.

Deliverable: Reconciled revenue record and public recap.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.

Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).

The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.

Stated assumptions

  • Base case: 60 targeted reverse-demo DMs produce 10 paying Studio accounts inside 30 days (unvalidated hypothesis).
  • Conservative case: the same motion produces 3 accounts because most agencies stay on the free estimate.
  • Upside case: 25 accounts after list expansion to 100, plus 20 warm direct offers on day 29.
  • ARPU is held at $99 across scenarios; $39 one-time purchases are treated as upside and excluded.
  • Payment fees assume Stripe at 2.9% plus $0.30, blended to about 4% because some agency cards are international.
  • Operating cost covers Vercel, Neon, PDF rendering, Resend and a domain; per-estimate delivery stays under $0.10.
  • Upside carries $150 of paid promotion (a LinkedIn boost on the samples page) and a $50 refund allowance; both are zero elsewhere.
  • No chargebacks are modelled in any scenario; a single chargeback would be absorbed by the fee line.
  • All figures are projections from these assumptions, not verified revenue, customers or traction.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$12
Paid marketing
$0
Hackathon profit
$285
Operating costs
$25
Business profit
$260

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$39
Paid marketing
$0
Hackathon profit
$951
Operating costs
$45
Business profit
$906

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$50
Chargebacks
$0
Payment fees
$97
Paid marketing
$150
Hackathon profit
$2,178
Operating costs
$90
Business profit
$2,088

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
$330

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 derived from stated assumptions. These are projections only, not verified revenue, existing customers or real traction.

Section 7 of 8

Main risks and validation experiments

Risk 1The free AWS Pricing Calculator plus a Google Doc template is good enough for most small agencies, so nobody pays.

Mitigation

Lead with the signed assumptions page, which the calculator cannot produce, and price at $99 to stay under the owner approval threshold.

Validation experiment

Send 10 DMs offering only the free PDF with no product behind it; count replies asking how it was made.

Kill criteria

Fewer than 2 of 10 replies show interest in the mechanism after 10 sends.

Risk 2AWS Price List SKU matching is wrong for a visible resource, and one bad number destroys trust in every future estimate.

Mitigation

Price only eight services, fail loudly to not priced, and run ten hand-verified fixtures on every deploy.

Validation experiment

Hand-price ten public reference stacks and diff them against the engine output.

Kill criteria

Any covered service exceeds 10% variance after a full day of fixture work.

Risk 3Terraform plan JSON omits request and data-transfer volume, so low/high ranges look like guesses and weaken the clause.

Mitigation

Put the usage assumptions above the fold, make them editable, and show not-priced lines explicitly.

Validation experiment

Ask five free-build recipients whether the range is credible enough to send to their client.

Kill criteria

Three of five call the range arbitrary or refuse to send it.

Risk 4Agencies quote in bursts, so monthly Studio subscriptions churn after one proposal season.

Mitigation

Offer the $39 one-time tier as a fallback and log each account's next quote date.

Validation experiment

Ask every paying account for the date of their next client quote in the onboarding email.

Kill criteria

No paying account can name a quote date within 30 days.

Risk 5Concierge builds eat the entire build window and the product never improves.

Mitigation

Cap concierge at five builds per week during week two and time every one of them.

Validation experiment

Time each free build against a 20-minute budget and log the overrun reason.

Kill criteria

Any build exceeds 30 minutes twice, at which point that step becomes the next shipped feature.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Claim the domain and create the Vercel and Neon projects.
  • Confirm the TrustMRR-connected payment account is ready.
  • Put a one-paragraph landing page online.

Output: Live placeholder page and provisioned infrastructure.

Hours 3-5

  • Pull the AWS Price List bulk index for us-east-1 and eu-west-1.
  • Write the hcl2json wrapper and normalizer for the eight services.
  • Emit a flat billable list from a sample plan.json.

Output: Working ingestion CLI on a real plan file.

Hours 6-8

  • Cache prices into Postgres keyed by service, SKU and region.
  • Implement the 0.7x, 1.0x and 1.6x usage multipliers.
  • Hand-verify ten resources against the public AWS calculator.

Output: Price engine with a committed ten-fixture test suite.

Hours 9-11

  • Build the 60-agency prospect sheet from Clutch, AWS Partner listings and LinkedIn.
  • Record site, published stack, contact route and trigger for each row.

Output: 60-row prospect sheet ready for personalization.

Hours 12-14

  • Render one complete branded PDF end to end for a synthetic agency stack.
  • Read it as a client would and fix the two worst layout problems.
  • Draft the 3-line DM that will carry it.

Output: The first finished artifact and its outreach message.

Complete report

Full 30-day launch report

Read the full generated report

CostClause — 30-Day Launch Report

1. Product opportunity and positioning

CostClause sells into a moment, not a market. A 2-25 person cloud agency has just finished a Terraform plan for a fixed-price build and needs a monthly infrastructure number for a proposal, an RFP or a scope-change note. Today that number comes from memory or from the free AWS Pricing Calculator pasted into a Google Doc. When the bill arrives three times higher, nothing in writing says what the quote assumed, and the agency absorbs the delta.

Two conditions make this sellable now. The AWS Price List Bulk API is public and cheap to cache, so a deterministic dollar-per-resource engine is days of work rather than a data-licensing problem. And the trigger is weekly and personally owned by the agency lead: a quote due this week. No procurement, no security review, no engineering adoption campaign.

Positioning is narrow on purpose. CostClause is not a FinOps dashboard, not a pull-request cost comment, not a recurring client-reporting service. It is a branded PDF plus a signed approval link. The differentiator is page two: a Cost Assumptions & Change Clause the client approves in-browser with a typed name and a timestamp. The number is the commodity; the signature is the product, and the free calculator cannot produce it.

JEV scores the concept 61.5/100 (band C, confidence 0.62), strongest on speed to first revenue (8.57) and reachable customers (7.07), weakest on market demand (4.33) and operational simplicity (4.5). The 30 days below answer that directly: reverse-demo selling from day 8, and deliberately manual concierge delivery while volume is under 25 accounts.

2. Smallest sellable MVP

One page, one upload, one PDF. The buyer drops a terraform plan JSON onto a page, or answers twelve questions about the stack, and receives within minutes a co-branded PDF and hosted share link containing a monthly AWS total in low/expected/high ranges, a per-service table, the top five cost drivers, and the approval clause. Eight services are priced: EC2, RDS, S3, EBS, ELB, Lambda, CloudWatch and NAT. Everything else is labelled not priced rather than guessed.

Not built: no AWS account connection, no bill ingestion, no CI step, no Azure or GCP, no dashboards, no anomaly alerts, no team roles. Each adds a credential or trust cycle a solo founder cannot close in 30 days and a proposal deadline does not require.

Flow: upload plan.json, normalizer emits a flat billable list, engine computes three ranges, renderer applies logo and colors, clause page fills editable variables, client opens the signed link, types a name, approves, and both parties get a timestamped confirmation.

3. Technical implementation plan

Next.js on Vercel, Neon Postgres, Stripe Checkout and Billing, Resend, React-PDF, and a cached price table from the AWS Price List Bulk API. Terraform plan JSON is flattened with hcl2json plus a normalizer mapping resource blocks to SKU, region and quantity rows.

Five build days. Day one, ingestion. Day two, pricing with 0.7x, 1.0x and 1.6x multipliers and ten fixtures checked by hand against the public calculator. Day three, the branded renderer and the twelve-question form. Day four, the assumptions page, typed-name approval, timestamp and IP capture, expiring signed links. Day five, Stripe, metering, delivery email, landing page.

The hardest risk is SKU matching. Terraform gives an instance type and a region; AWS gives a wall of SKUs, and a confident wrong number destroys the only asset. Mitigation: cache only eight services, fail loudly to not priced instead of guessing, and run the ten hand-verified fixtures on every deploy. No model sits in the pricing or delivery path; numbers stay deterministic, with an optional LLM drafting assumption bullets, off by default.

4. Pricing and monetization

Two tiers. Single Estimate at $39 one-time for a freelancer quoting one project: one branded PDF, one approval link, the clause page. Studio at $99 per month for a 2-25 person agency: unlimited estimates, saved brand profile, approval links, version diffs at scope change, and a concierge build for the first ten accounts.

$99 sits under the owner's approval threshold, so nobody needs a finance review to buy, and it is less than an hour of an agency's billable rate. The offer to send this week: the first branded estimate free, then Studio. One-time purchases count as upside and stay out of the projections. Growth path: more client estimates per account, then a per-seat price once a second person starts quoting.

5. First-customer acquisition

The only channel is reverse-demo DM. Build a 60-agency list from Clutch cloud-consulting listings, AWS Partner Network listings and LinkedIn searches for FinOps and cloud consultants at 2-25 people. For fifteen of them, read a public case study, price a stack of the same shape, render it with their logo and colors, and attach the finished PDF to a three-line message. The work is already done when they read it.

Message: 'I priced a stack like the one in your case study: monthly range, per-service table, and an assumptions page your client signs. PDF attached, it is yours. Want the next one free?'

Supporting motions: a five-free-cost-sheets post in r/msp, r/aws and two MSP Slacks, and a 72-hour follow-up showing the same stack at a 4x range framed as overage exposure. Week-one goal: fifteen sends, five free builds, one paying account by day 8.

6. 30-day execution roadmap

Week 1, days 1-5, is build: ingestion, engine, renderer, signature layer, Stripe. It ends with a live product that can take money. Days 6-7 build the list and fifteen personalized PDFs.

Week 2, days 8-14, is the first revenue push. Batch one out day 8, community drop day 9, concierge delivery day 10, the exposure follow-up day 11, batch two day 12, funnel instrumentation day 13, estimate versioning day 14 so a scope change becomes a second sellable artifact.

Week 3, days 15-21, is accuracy and objections: batch three on a QBR angle, a better range model, explicit not-priced handling, a public samples page, batch four, and a written midpoint retro that kills any channel with zero replies after 30 sends.

Week 4, days 22-28, is wave two: non-responders, list expansion to 100, saved brand profiles, DOCX and CSV exports, a resale-margin angle, referral asks, hardening, and a 90-second demo video.

Days 29-30 close the window: a 20-prospect final wave with a 48-hour $39 offer, then Stripe reconciliation against TrustMRR and a public recap using only real figures.

7. Revenue and profit scenarios

All three scenarios are projections built from stated assumptions, not verified revenue. There are no customers today.

Conservative: 3 Studio accounts at $99, $297 gross, $12 in processing fees, $25 operating. Base: 10 accounts, $990 gross, $39 fees, $45 operating. Upside: 25 accounts, $2,475 gross, $50 refunds, $97 fees, $150 of paid promotion and $90 operating, giving $2,178 hackathon profit and $2,088 business profit.

The entire spread is one variable: whether 60 targeted DMs carrying finished artifacts produce 3, 10 or 25 paying agencies. Everything else is small. Payment fees assume Stripe at 2.9% plus $0.30, blended to roughly 4% on international cards. Hosting is Vercel, Neon, PDF rendering, Resend and a domain.

8. Risks and validation experiments

Free-tool sufficiency: the AWS calculator plus a Google Doc may be good enough. Test by sending ten DMs offering only the free PDF with no product behind it and counting replies asking how it was made. Stop if fewer than two of ten respond.

SKU accuracy: price ten public reference stacks by hand and diff against the engine; anything above 10% variance blocks that service from launch. Ranges read as guesses: put the assumptions above the fold and ask five free-build recipients whether the range is credible; stop the range format if three call it arbitrary.

Sporadic proposal cycles: ask every paying account for their next quote date; if none names a date within 30 days, make the $39 one-time the primary tier. Concierge overload: cap at five builds per week and time each one; anything above 30 minutes becomes the next product feature.

9. First 24-hour action plan

Hours 1-2: claim the domain, create Vercel and Neon projects, confirm the TrustMRR-connected payment account is ready, put a one-paragraph landing page online.

Hours 3-5: pull the AWS Price List bulk index for us-east-1 and eu-west-1 and write the normalizer for the eight covered services; output a CLI that turns a sample plan.json into a flat billable list.

Hours 6-8: build the price table and three usage multipliers, hand-verify ten resources against the public calculator, and commit the fixture suite.

Hours 9-11: build the 60-row prospect sheet with site, published stack, contact route and trigger event.

Hours 12-14: generate one complete branded PDF for a synthetic agency stack, end to end, and read it as a client would. That artifact goes into the first DM tomorrow.

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 →