Confirmed Research Artifact

Transaction Map - Crew

Canonical transaction model for Crew's checkout, payment, fulfillment, receipt, refund, dispute, and trust-state flows. The map stays provider-agnostic because no payment provider, monetization artifact, policy, or product code exists yet.

status: confirmed product path: research/crew/ canonicalized: 2026-07-07

Canonical Outputs

Transaction mapresearch/crew/transaction-map.md

Interview companionresearch/crew/transaction-map-interview.md

Basisresearch/crew/{journey-map,conversion-map,lifecycle-metrics,expansion-map}.md

Transaction Principle

Do not sell a governance promise until the account can be provisioned into the matching governance state. Payment success is only one state; paid Crew accounts also need provider health, attribution coverage, team/cost-center mapping, billing records, role access, and support paths.

Transaction Types

Type	Buyer Path	Required Handling
CTO self-serve subscription	Fast card checkout after an `aha_surprise_logged` event	Immediate access, receipt, simple cancellation path
Platform team rollout	Platform Lead after `cfo_question_answered`	Team/provider scope, billing profile, Finance records, security packet, invoice escape hatch
Invoice or PO-assisted purchase	Finance, Procurement, VP Eng, Platform Lead	Quote/invoice request, owner/date, pending entitlement state
Product-line add-on	Existing Crew or Trace account	Shared account billing, module entitlement, no duplicate account
Expansion, renewal, cancellation, refund, dispute	Active account	Records, proration/renewal logic, policy-backed support handoff

Critical States

Checkoutcheckout_started, plan_selected, quantity_or_scope_selected, billing_profile_started

Paymentpayment_method_submitted, payment_succeeded, payment_failed, invoice_request_submitted

Fulfillmentsubscription_active, account_provisioning_started, account_provisioned, module_added

Recordsbilling_contact_updated, receipt_sent, invoice_sent

Supportrefund_requested, cancellation_requested, payment_dispute_opened, allocation_dispute_opened

Trust RiskPayment success must not imply chargeback readiness when provider data, role mapping, or attribution coverage is incomplete.

Open Gaps

Monetization and packaging are undefined: no plan names, prices, limits, billing interval, or seat/usage model.
No payment provider is selected, so checkout, webhook, tax, invoice, dunning, and dispute mechanics remain open.
Refund, cancellation, dispute, data-retention, support SLA, tax/VAT, invoice, and PO policies are not defined.
Attribution coverage and provider granularity must be validated before selling chargeback-ready governance.
The onboarding map remains in review, so post-payment setup should stay provisional until approved.

Next Steps

Run monetization or packaging research before choosing plan names, prices, seat/usage model, invoice thresholds, or refund eligibility.
Run $retention-map research/crew to connect paid account health, dunning, cancellation, and monthly budget-review rituals.
Use $lifecycle-metrics research/crew outputs as the event schema seed when transaction instrumentation is implemented.

This page is a confirmed summary of the canonical markdown files. Edit the markdown artifacts first when changing substance.