Skip to main content

Launch Checklist

Use this checklist before showing the site to paid users. It keeps launch work separate from product claims: do not mark an item complete unless the corresponding release artifact, policy, or configuration is actually ready.

Site Build​

  1. Run pnpm install --frozen-lockfile.
  2. Run pnpm validate:config.
  3. Run pnpm typecheck.
  4. Run pnpm build.
  5. Open the built site locally and check the home page, pricing, download, docs, FAQ, and security pages on desktop and mobile widths.
  1. Set SITE_URL to the production origin.
  2. Set download links in src/config/links.ts:
    • DOWNLOAD_MAC_URL
    • DOWNLOAD_MAC_ARM64_URL
    • DOWNLOAD_MAC_INTEL_URL
  3. Set purchase links to hosted Stripe Payment Links:
    • BUY_FOUNDER_URL
    • BUY_PRO_MONTHLY_URL
    • BUY_PRO_ANNUAL_URL
  4. Set SUPPORT_EMAIL and SUPPORT_MAILTO_URL.
  5. Set GITHUB_URL and RELEASES_URL only if public destinations exist.
  6. Leave unpublished platform artifacts empty so the Download page hides them.

Release Artifact Checks​

  1. Confirm the latest version string.
  2. Confirm the release date.
  3. Verify every published DMG link.
  4. Verify SHA256 checksums from a clean download.
  5. Confirm the minimum macOS version.
  6. Confirm whether the build is signed and notarized before enabling that claim.
  7. Update v0.1.0 with artifact metadata before announcement.

Pricing and Purchase Terms​

  1. Confirm Free, Founder Lifetime, Pro Monthly, and Pro Annual prices.
  2. Confirm Founder Lifetime scope, update window, transfer rules, refund terms, and support expectations.
  3. Confirm Pro subscription renewal, cancellation, invoice, and license-expiry behavior.
  4. Confirm that the pricing page, FAQ, and license page describe the same plan limits.
  5. Do not change checkout links unless written purchase terms match the site copy.
  6. Run pnpm validate:config:payments before deploying live checkout.
  1. Review Privacy, Terms, License, Refunds, and Security before publishing changes.
  2. Confirm governing law, refund windows, warranty language, liability language, and commercial license restrictions.
  3. Confirm the responsible disclosure contact path.
  4. Make sure public policy pages match the current purchase and support flow.

Content and Claims​

  1. Product name should be PastePrompt.
  2. Core positioning should remain: local-first macOS context builder for auditors and developers using LLMs on large codebases.
  3. Avoid claims that PastePrompt finds vulnerabilities by itself.
  4. Avoid claims that LLM results are guaranteed.
  5. Avoid claims that secret scanning prevents every leak.
  6. Avoid SOC 2, ISO, GDPR, HIPAA, legal-compliance, customer-logo, or testimonial claims unless separately verified and approved.
  7. Confirm all screenshots are real product screenshots or app recording stills.

Documentation Coverage​

Check that launch users can find practical instructions for:

  1. Installing on macOS
  2. Creating the first context bundle
  3. Importing a license
  4. Using the secret scanner
  5. Using Git diff mode
  6. Opening files in an editor
  7. Troubleshooting install issues
  8. Troubleshooting repo scan errors

Support Readiness​

  1. Confirm the support email works.
  2. Confirm support guidance tells users not to send source code, secrets, private repository URLs, or client-confidential material in first contact.
  3. Confirm paid-user support expectations are conservative and match the purchase terms.
  4. Prepare a safe support-report template that asks for app version, macOS version, release channel, and sanitized error details.