Chase Dining: Premium
From an unused benefit to a reason to keep the card
Goal
Turn a benefit obligation into a dining capability the firm can defend.
Problem
Dining, the most frequent lifestyle spend, was a line item: no team, no point of view. A benefit nobody finds is one nobody uses — and use is the argument for the fee.
Customer Promise
"Your card gets you to the table — and the table is worth getting to."
Constraints
- Tech: partner APIs, each its own data model.
- Partner: editorial independence preserved.
- Compliance: benefit terms accurate everywhere.
- Time: greenfield, small team.
Options Considered
- Option A: license a white-label platform. Generic within a quarter.
- Option B: build bespoke: taste plus utility. Slower, defensible.
- Option C: extend the travel team’s remit. Never the priority.
Decision
Option B. Editorial taste times reservation utility is a moat competitors cannot buy on the same terms. It meant a team built from zero.
The Mechanism
Metrics
- Primary: benefit discovery and repeat use.
- Guardrails: partner satisfaction, reservation completion, editorial integrity.
- Strategic: integrations competitors cannot assemble.
Risks & Mitigations
- A small team → V1 was reservations and editorial, nothing else.
- Partner drift → a liaison embedded with each partner.
- The voice diluted → product bends to it, never the reverse.
What Changed
- A compliance obligation became a premium pillar.
- Partnerships became a moat, not a vendor list.
- A team built from zero to own the category.