Finance & models
AuraScore 81/100

Private Wealth Fee Schedule Restructuring Plan

Design a strategic transition plan to migrate private client assets to a tiered advisory and performance fee structure.

Use this template when modernizing fee architecture for wealth management practices facing margin compression. It delivers a phased commercial rollout plan that preserves client retention and models revenue impact.

Template

Role: Managing Director of Pricing Strategy and Advisory Operations in Private Wealth Management.

Context

  • Firm profile: {{firm_profile}}
  • Current pricing model: {{current_fee_structure}}
  • Proposed fee architecture: {{proposed_pricing_model}}
  • Client segmentation: {{client_segmentation_tiers}}
  • Assets under management: {{aum_under_management}}
  • Target transition window: {{transition_timeline}}

Task

Author a comprehensive operational and commercial migration plan to transition the existing advisory book from {{current_fee_structure}} to {{proposed_pricing_model}}, protecting net margins while preventing client attrition across all tiers in {{client_segmentation_tiers}}.

Method

  1. Quantify baseline revenue contribution across each tier using {{aum_under_management}} and {{current_fee_structure}}.
  2. Model client-level fee delta distributions under {{proposed_pricing_model}}, pinpointing accounts facing fee increases above 15%.
  3. Segment existing accounts into retention risk cohorts (High, Moderate, Protected) based on relationship tenure and wallet share.
  4. Design tier-specific value articulation toolkits for advisors, detailing new service entitlements and unbundled capabilities.
  5. Establish exception-governance rules outlining maximum allowable discretionary fee discounts and sign-off authorities.
  6. Sequence the outreach schedule across {{transition_timeline}}, staggering high-touch clients ahead of mass-affluent accounts.
  7. Define billing system cutover milestones, custodial notification requirements, and contract re-papering workflows.
  8. Build an operational KPI dashboard to track realized yields, client retention rates, and unbundled service uptake.

Constraints

  • MUST include grandfathering guidelines for sensitive or legacy multi-generational accounts.
  • MUST NOT recommend across-the-board discounts that erode the target margin expansion.
  • Every client tier must show a mapped correlation between fee changes and tangible service value.
  • Operational timelines must account for regulatory re-contracting notice periods.

Output format

  • Section 1: Financial Impact & Revenue Sensitivity Model (summary table by tier)
  • Section 2: Account Segmentation & Cohort Strategy (risk categorization criteria)
  • Section 3: Advisor Enablement & Exception Governance Framework (rules and approval tiers)
  • Section 4: Operational Cutover & Re-papering Roadmap (chronological milestone table across {{transition_timeline}})
  • Total length: 1,000 to 1,400 words.

Self-review

  • Ensure the revenue impact accounts for all segments identified in {{client_segmentation_tiers}}.
  • Confirm clear exception approval thresholds are stated for advisor discounting.
  • Verify that operational deadlines respect the overall boundary set in {{transition_timeline}}.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-finance
financial-services
wealth-management
pricing-strategy
private-banking