Waitlist To Access Reconciliation
Reconcile confirmed waitlist records, invitations, actual access and first use with consistent units and cutoffs before reporting a launch funnel.
Read this resource as Markdown
When to use this template
Use this before a launch or beta report when separate systems show subscribers, invitations and accounts. Choose a cohort and cutoff, then verify what each state actually means.
Choose another approach when: You intend to sum overlapping stages as unique people, call email delivery successful access, or expose identifiable application records in a public report.
Gather these inputs
- Aggregate counts or appropriately controlled internal records with stable definitions.
- The actual waitlist, invitation, access and first-use processes.
- A reporting cutoff, cohort rule and documented handling of duplicates or expired access.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
Fictional example: a founder sees more invitation events than confirmed pilot applicants because some invitations were retried. The reconciliation counts unique eligible applicants separately from repeated send attempts. Another report shows account creation, but the team has not verified that every account has the required pilot access. Those accounts are not automatically counted as activated users. An expired invitation remains distinct from a person who tried the product and failed a task. The final internal report explains the differing totals and preserves unresolved matches. Its public summary contains aggregates only. No contact details are exported, and a provider’s delivery result is not presented as proof of the recipient’s working journey.
How to use it
- Fix the reporting cohort, cutoff and unit before collecting stage counts.
- Separate current states from period transitions and reconcile repeated or unmatched records.
- Validate actual access and first use before publishing a bounded aggregate funnel.
Check before using it
- Retries and overlapping lifecycle stages do not inflate the unique-person total.
- Invitation delivery is not substituted for access or successful use.
- Unmatched records remain visible without exposing private applicant data.
What to measure
Track duplicate transitions, unresolved state conflicts and verified gaps between invitation, access and first use. Compute only comparable eligible transition rates. Reconciled records can support an operational report; they do not establish consent, product-market fit or a frictionless journey for everyone.
Research and sources
HubSpot distinguishes lifecycle stages; Google explains why funnel definitions affect counted progress. This original reconciliation ledger defines its own waitlist/access states and does not assume a CRM stage or email result proves product access.
- HubSpot: Use contact and company lifecycle stages — checked 2026-10-24. 20October2026 documentation distinguishing subscription, qualification and customer stages, with customizable definitions. Not a universal lead score or proof of consent/access.
- Google Analytics: Funnel exploration — checked 2026-10-24. Explicit funnel entry, ordered steps and timing conditions affect counted users. GA4-specific counting behavior is not generalized to every provider.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.