Feature → Payment Mapping: A Wiring Diagram to Turn Product Moments Into Charge Points

Start by mapping product moments (the user actions that deliver value) to candidate charge points (what you could plausibly bill). Work left-to-right: user intent → first-value action → repeatable measurable event → pricing unit. Treat this as a wiring diagram — each moment is a node with inputs (preconditions) and outputs (value delivered).

Once you have candidate charge points, decide how to surface them in onboarding and your pricing page. Surface only the charge points that are discoverable and defensible — those where the user clearly sees the benefit and can’t easily replace it with workarounds. Finally, instrument the events and run acceptance tests to validate that a) the event correlates with value and b) customers will tolerate paying for it.

Onboarding is where value and willingness-to-pay meet. Use onboarding to deliver the first paid-worthy moment and make the payment trigger obvious. A good rule: the onboarding path should make one paid moment achievable within 5–7 minutes or one key interaction (the ‘first-value action’) — anything longer and you’ll lose momentum.

Screenshots, plan cards, and empty states must communicate the same wiring diagram. If a charge point is an API call, show a small ‘units used’ preview. If it’s a creative export, show the export example. Avoid jargon — show the concrete outcome users care about and pair that with the pricing unit (e.g., exports/month, seats, AI calls).

Acceptance tests answer two questions: does the event equal value, and will customers accept being charged for it? Build lightweight experiments that tie instrumented events to simple price asks. Example tests: gate an advanced export after the free trial with an in-app paywall and measure % who convert after experiencing the export; or implement a metered preview of an API call and measure upgrade rate when quota is exhausted.

When you select a pricing unit, prefer the simplest, most intuitive meter that maps to user value: per-seat for collaboration, per-export or per-report for creative and analytics tools, per-call/per-token for AI/APIs, and storage or bandwidth where retention is the main cost. Where possible, align units to product telemetry already tracked by your systems to reduce fragility.

1) Collaborative design app (Figma-like): Moment = first shared file export or presentation. Charge point = per-export (high-value targets) + seats for team access. Surface: onboarding creates a demo file, prompts user to invite one teammate, then shows the share/export preview with an export quota. Acceptance test: gate exports after X free exports and measure upgrade. Pricing unit: exports/month + seats.

2) Analytics/dashboard app: Moment = scheduled report delivery or API data pull. Charge point = reports/month or API calls. Surface: empty state shows a sample scheduled report and a modal that explains 'X free reports included'. Acceptance test: allow free creation, then block scheduling beyond free tier and track conversion. Pricing unit: scheduled reports/month or API requests.

3) AI assistant / API product: Moment = useful model call that returns production output. Charge point = per-call or per-token (for LLMs) and feature SKUs for higher-capacity models. Surface: show example prompt → output in onboarding and display a live usage counter. Acceptance test: metered sandbox that stops at quota and prompts upgrade with cost examples. Pricing unit: calls or tokens, model-specific multipliers.