Rhodium-Partner.md
Language Markdown2.1 KB39 lines
---type: tierscope: 01-Tierstier_name: "Rhodium Partner"user_group: "Rhodium Partner"annual_volume: "$75K+ lifetime spend"source: "07-Automation/partner-thresholds.md (ltv_bands); program definitions owned by Ines Carvalho"tags: [outreach, tier, partner-program]created: 2026-06-16updated: 2026-09-28aliases: ["Rhodium Partner"]---# Rhodium PartnerPartner Program tier. Maps to the computed `user_group_correct` value **"Rhodium Partner"** in the client data. The band is set in the `ltv_bands` block of [[partner-thresholds]]; the program definitions are Ines Carvalho's. See [[00-Index]].**Lifetime spend band:** $75,000 and up (lower bound inclusive, no cap)Harlow Ridge Homes (`harlowridge.example`) sits here by override: its mailboxes are Rhodium because the relationship is with the company, not the mailbox (per-email `tier_overrides` in [[partner-thresholds]]). Hazel handles that account directly; it is never cold-emailed.## Benefits- Everything in [[Iridium-Partner]]- A branded reorder portal- A direct line to Nora Lindqvist (owner / general manager) for partnership planning## Clients in this tierFilters on `user_group_correct`, the tier the weekly driver computes. Raw `user_group` is blank on the stubs, so filtering on it under-reports to zero. `ltv` is a currency string (`"$6,887.10"`), so a Dataview sort on it would be lexical and put $9,000 above $12,000; the list sorts by most recent order instead.```dataviewTABLE WITHOUT ID file.link AS "Client", company AS "Company", email AS "Email", ltv AS "LTV", total_orders_count AS "Orders", last_order_date AS "Last Order"FROM "03-Clients/client-stubs"WHERE user_group_correct = "Rhodium Partner"SORT last_order_date DESC```## Outreach fitClients here are reached through [[Check-In-Outreach]] (Palladium / Platinum) or [[Executive-Outreach]] (Platinum+ / Iridium / Rhodium). New tier crossings and never-contacted accounts go to [[Client-Interaction]] (Partner Tier Upgrade, cat 24). Lapsed accounts (no order in 12+ months) route to [[Winback-Outreach]]. Routing rules: [[pipeline-routing-rules]].