Design partners wanted: 15-min Stripe test-clock parity check (we send a short report)

[geminimir]

What this is: we’re looking for 2–3 usage-billed SaaS teams to run a 15-minute parity check on Stripe test clocks with StripeMeter.
Goal: prove that pre-invoice drift goes to 0 after replay. You’ll get a short, anonymized parity report you can share internally.

---

What you get

• A live parity run on test clocks (~15 min)
• A concise parity report (parity-report.json + summary)
• Priority on bug fixes / feature requests that block parity

What we’ll do together (fast)

1. Spin up the demo (Codespaces or local)
2. Send a small batch of events (we can use your test event shape or our demo)
3. Show drift before replay → run replay → confirm drift = 0
4. Hand you the report + next-step notes

What we need from you

• Test-mode only (no prod keys or PII)
• A rough idea of your usage metric & expected counting rules
• 15–20 minutes on a call or async via comments

---

Data & privacy

• Test mode only.
• We don’t store your secrets in the repo or in CI.
• Any public artifacts are anonymized (tenant IDs, emails, org names removed or replaced).
• You approve any case-note text before we add it here.

---

Where to start

• 5-min Quickstart: link in the README top.
• Parity Demo: docs/demos/parity-scenario-test-clocks.md
• Run in CI (optional): see .github/workflows/parity-check.yml (uploads parity-report.json)

---

Comment template (copy, fill, and post below)

Company / project (anonymized ok):
Metric you meter (e.g. requests, seats, rows scanned):
How you count (one line):
Event rate ballpark (dev/test is fine):
Time zone + 2–3 slots (15–20 min):
Contact method (GitHub DM or email):
Anything special we should test (late %, duplicates %, window):

We reply within 24 hours. If you prefer async (no call), mention it and we’ll run the demo with a synthetic shape close to yours, then share the report here.

Thanks! 🙌