ScopeSeal

ScopeSeal is a zero-backend change-order generator for freelancers and small studios. It converts an out-of-scope client request into a priced, client-ready approval message.

Commercial hypothesis

• Buyer: English-speaking freelancers and 1–5 person agencies doing fixed-price client work.
• Pain: Small additions are performed for free because asking for approval feels confrontational and preparing paperwork takes too long.
• Free wedge: A useful change-order message in under one minute, with transparent scope, price, timeline impact, and approval language.
• Paid offer: $9 one time for 12 editable scripts covering revisions, rush work, approval follow-ups, late payment, paused projects, and cancellation. No subscription.
• Primary CTA: “Request Pro early access.” Until checkout exists, it opens a prefilled public GitHub issue instead of implying that payment can be collected.
• Validation signal: Count unique visitors, completed calculations, CTA clicks, and genuine early-access emails. Do not interpret visits alone as purchase intent.

Run locally

No build or dependency installation is required.

python3 -m http.server 8080

Open http://localhost:8080/experiments/scope-seal-change-order/ when serving from the repository root, or http://localhost:8080/ when serving from this directory.

Verify

Requires Node.js 18 or newer:

node test.mjs

Also inspect the page at mobile and desktop widths and test clipboard/download behavior in a real browser; those browser APIs are not covered by the Node test.

Privacy and operating cost

• All calculations run in the browser.
• No inputs are transmitted or stored.
• There are no cookies, analytics, API calls, AI services, or third-party assets.
• The static files can be hosted for free on GitHub Pages, Cloudflare Pages, or Netlify.

Gates before revenue

1. Deploy to a public static host (requires owner account/login or an existing authorized repository).
2. Add a checkout only after the offer receives genuine interest. Stripe Payment Links, Lemon Squeezy, or Gumroad each requires an owner account, payout details, terms acceptance, and possibly identity/tax verification.
3. Create the promised 12-template Pro pack before accepting payment.
4. Add privacy/terms/refund pages appropriate to the selected merchant and seller jurisdiction.

Nothing in this prototype constitutes confirmed revenue. A click or email is validation evidence; only settled, withdrawable payment counts as revenue.