Revenue operations asks for an active-subscription plan mart. Deliver clean current subscriptions, one row per plan, a table, data tests, and an owned dashboard exposure. Keep unknown plans visible.
Pulse Path revenue operations needs a small dataset another analyst can adopt without a meeting. You'll deliver current subscriptions, an active-plan summary, a stored output, and the tests and descriptions that define its use. The data includes missing plan names and repeated subscription updates, so start by establishing the current-state grain.
The final handoff should state what one row means and which conditions are tested. It should also name the downstream owner.
Documentation is part of the artifact, not a substitute for validation: a description claiming one row per plan must agree with the SQL and its uniqueness test. Keep the model's measure named monthly_amount rather than making a wider revenue claim. The exercise doesn't provide exchange rates, invoicing rules, or collections data.
select subscription_id, user_id, coalesce(lower(trim(plan)), 'unknown') as plan, lower(trim(status)) as status, monthly_amount, updated_at from {{ source('pulse', 'subscriptions') }} where subscription_id is not null qualify row_number() over (partition by subscription_id order by updated_at desc)=1
The example shows the connected analytics project pattern. Follow the stated business rule when applying it.