Retail Fund Distribution
High-stakes financial decisions requiring trust, structured diligence, and coordinated stakeholders.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Investment Needs Discovery
Align on the buyer's investment objectives, model portfolio constraints, fiduciary and ERISA requirements, and platform availability priorities.
Discovery Questions
Starting point: how you currently pick funds
- Tell me briefly how your team normally builds a client or plan model portfolio
- Which buyer role are you representing in these decisions
- How often do you review or rebalance your model portfolios or plan lineups
- When you select a new fund, which three data points matter most in your decision
- Describe the last fund you added to a model or plan menu and why it made the cut
- If adding that fund were easy and low risk, how quickly could you deploy it to your models or menus
Where the current lineup actually falls short
- Which recurring problem with existing fund choices most frustrates you or your committee
- How frequently does that problem cause you to remove or replace a fund in a model or menu
- Who on your team feels the operational pain first when a fund experiences an issue, and what do they do next
- What downstream cost or risk does that failure create for your firm or plan sponsors
- Which single acceptance criterion would make you stop considering a new fund immediately
- Tell me about a recent time a fund addition went poorly and what you would change about that process
Fiduciary realities and ERISA constraints that actually move decisions
- How do ERISA or fiduciary requirements change the way you evaluate share classes for a plan menu
- Which documents or certifications must a fund provider already have in place before your team will even start due diligence
- Who signs off on fiduciary comfort at your firm and what stops them from approving a fund
- To what extent does fee benchmarking against plan-level share classes determine the final approval
- Which ERISA or compliance finding would kill a placement for you right away
- Describe an internal approval checkpoint that typically delays or blocks a fund from being added
Platform realities: where integrations and availability actually break the plan
- Which platform or recordkeeper categories must a fund be available on for you to consider it seriously
- How do gaps in platform availability change your willingness to approve a fund
- Which integration details create the most operational risk when onboarding a fund
- Who owns integrations and endpoint provisioning on your side, and do they have capacity for onboarding this quarter
- Which single technical or operational constraint would stop your operations team from accepting a new fund right now
- Describe any past onboarding where an integration issue caused a weekslong delay and what prevented it
How you actually evaluate funds under pressure — selection in action
- When you run a candidate through your selection process, what does the scorecard look like and which fields are mandatory
- How many fund candidates do you typically run through due diligence before selecting one for a model or menu
- Walk me through a recent selection where platform constraints forced you to pick a second-best fund
- Which part of the selection exercise takes up the most time for your team
- Which acceptance threshold on your scorecard, if unmet, will make you walk away from a deal
- If a fund demonstrated performance and fee parity in a pilot, what internal step would allow you to sign off immediately
Who you are comparing us to, and why you might stay where you are
- Which alternatives are you actively evaluating beyond external fund providers
- Name the incumbent or internal option in broad terms and tell us what would have to be true for you to keep going with them
- Has anyone on your team proposed building an internal solution instead of adding an outside fund, and who argued for that
- Which competitive feature or capability would cause you to pick another provider this quarter
- If you stayed with the incumbent, what reporting or monitoring improvement would need to change to keep you from switching
Operational readiness: the constraints that decide timelines
- Which of these operational prerequisites can you confirm are already in place on your side
- Who will be the single point of contact for operations during provisioning and testing
- How many hours per week can your ops contact commit to onboarding work during the next 8 weeks
- Are there any regulatory approvals or internal committee dates that will gate launch windows this quarter
- Which single missing operational item would force us to pause or cancel a planned onboarding
- Describe any recent onboarding where a resource shortage on your side extended timeline and how you resolved it
Decision drivers, deal killers, and the timeline that actually matters
- Which single commercial or operational commitment from a seller would accelerate you from evaluation to signed inclusion this month
- If the pilot demonstrates the expected outcomes, what internal approval closes the deal that week
- Which contractual term tends to take the longest in your negotiations and could derail timing
- Who are the essential approvers we must convince before anything can be placed on a live menu
- Which scenario would make you walk away from a potential placement in the next 30 days
- Realistically, what is your target window for having a new fund available on your primary platforms
Concrete next steps and acceptance signals we need to get moving
- Which documents should we prepare first to speed review on your end
- Who will approve a pilot and who will sign a full placement if the pilot meets objectives
- Describe one quick win we could deliver in the next two weeks that would materially increase your confidence
- Which acceptance criterion, once met, will cause your team to move to contract within 7 days
- How would you like us to report progress during onboarding, and how often
- Who should we schedule a follow-up with to confirm these next steps and by when
-
Solution Experience
Walk through how the fund lineup, share-class options, and distribution support address the buyer's portfolio construction, fee benchmarking, and platform constraints using real selection scenarios.
Solution Experience
- Solution Experience: Fund Lineup and Share-Class Scenarios
- Confirm the current state and its cost
- You confirm the demonstrated fund and share-class choices eliminate the fee-mismatch and selection rework described in Discovery.
- Provide the two prioritized model-portfolio scenarios and the target platform list to be used for the proof run, including any ERISA/share-class constraints.
- You confirm the demonstrated options meet your plan-level fee benchmarks and ERISA/share-class constraints for the run scenarios.
- Review prioritized selection scenarios
- Run the fee-benchmark and share-class availability checks for the two scenarios and deliver a comparison report with recommended fund/share-class selections before the follow-up decision meeting.
- You agree on the remaining evidence and tasks required to move the selected funds to your target platforms and accept them into your model portfolios.
- Demonstrate the selection and fee-benchmark proof
- Confirm the required registration and ERISA documentation needed per platform and deliver an onboarding dependency checklist.
- Show platform availability and distribution support plan
- Confirm your acceptance criteria and the timeline you need for shelf placement so the deployment plan matches your deadline.
- Validate the outcome
- Solution Experience: Fund Lineup and Share-Class Scenarios
- Solution Experience Deck
- Solution Brief — Fund Lineup and Distribution Fit
- meeting
- slides
- document
-
Solution Scope
Define which funds and share classes will be offered, required documentation and servicing modules, responsibilities, and measurable acceptance criteria.
Scope Configuration
- Produce Fund Fact Sheets
- Publish Monthly Performance Reports
- Provide Prospectus and Regulatory Disclosures
- Deliver Manager Due-Diligence Packets
- Provide ERISA Fee Documentation and Schedules
- Enable Share-Class Setup on Recordkeeping Platforms
- Provide Model Portfolio Files for Platform Integration
- Deploy Portfolio Construction Toolkit to Advisors
- Provide Regional Wholesaler Coverage
- Deliver Advisor-Facing Webinars and Trainings
- Publish Quarterly Market Commentary
- Supply Fee-Benchmarked Performance Data for Plans
Scope Questions
Produce Fund Fact Sheets
- List the exact fund tickers and share-class identifiers you want individual fact sheets produced for
- Specify the mandatory data fields for each fact sheet (for example: top 10 holdings, expense ratio, assets under management, inception date, 1/3/5/10-year returns)
- Which output formats do you require for fact sheets
- Provide the name and role of the person who will approve fact-sheet creative and compliance wording
- Identify the distribution endpoints for the fact sheets (for example: advisor portal asset library, platform compliance mailbox, recordkeeper content portal)
- How many historical performance periods do you want displayed on each fact sheet
Publish Monthly Performance Reports
- When delivering monthly performance reports, list the funds and share classes that must be included in the monthly package
- Who should receive the monthly performance report distribution (for example: your platform rep, your home office due-diligence inbox, recordkeeper performance feed)
- Confirm the performance metrics you require in the monthly report (for example: month net-of-fees return, year-to-date net-of-fees, benchmark comparison, volatility)
- Select the file formats and delivery method for the monthly report
- Describe your required lookback history for monthly reporting (how many months/years of NAV and price history must be included)
- Attach the list of benchmark mappings you use today for peer-comparison so the monthly report can align to your peer groups
Provide Prospectus and Regulatory Disclosures
- Name the share classes that require prospectus or Statement of Additional Information updates for this scope
- Specify the delivery channels required for regulatory disclosures (for example: upload to recordkeeper compliance portal, deliver to platform compliance mailbox, file with custody portal)
- Which regulatory documents do you need included (for example: prospectus PDF, shareholder reports, fund supplement, offering memorandum)
- Describe who on your side will provide legal sign-off for disclosure language and the expected turnaround time
- Indicate any jurisdictional or plan-level restrictions that must be reflected in the prospectus distribution (for example: retirement-only share class, advisory-only share class)
- Provide the exact filename and metadata conventions you require for each uploaded regulatory document
Deliver Manager Due-Diligence Packets
- List the due-diligence artifacts you expect in each packet (for example: portfolio manager bios, team org chart, strategy fact sheet, compliance incidents log)
- Specify the preferred packet format and maximum file size (for example: single PDF, zipped folder, PPT for presentations)
- Identify any home-office due-diligence checklist items we must fill out (for example: operational risk questionnaire, custody arrangements, sub-advisor agreements)
- Describe the required frequency for refreshing the manager packet (for example: quarterly update, event-driven on manager change)
- Who on your team will be responsible for reviewing and accepting the due-diligence packet
- Provide any quantitative manager metrics that must appear in the packet (for example: strategy AUM, 3-year annualized return, turnover, top 10 holdings)
Provide ERISA Fee Documentation and Schedules
- Which plan-level share classes and plan types need ERISA fee schedules (for example: 401(k) plan R-shares, 403(b), institutional classes)
- Specify the fee elements that must appear on the schedule (for example: expense ratio, 12b-1 fees, sub-transfer agent fees, revenue share)
- Confirm whether you require a fee-benchmarking report comparing proposed share-class fees to peer plans and what peer universe to use
- Confirm whether the signed fee schedule or a plan-level compliance upload is the acceptance evidence required by your recordkeeper
- When must fee schedules be delivered relative to anticipated deployment date
- Who on your team will sign or approve ERISA fee schedules (name and role)
Enable Share-Class Setup on Recordkeeping Platforms
- Define the acceptance criteria that will confirm a share class is correctly provisioned on a recordkeeping platform (for example: active ticker, correct CUSIP mapping, NAV history present, price history matching our source)
- List the recordkeeping platforms and platform identifiers where share classes must be enabled
- Map the required mapping keys you will provide for each share class (for example: CUSIP, ticker, internal share-class code, prospectus effective date)
- Specify any testing steps you require prior to go-live (for example: test ticker trade, historical NAV import, reconciliation report)
- Who will be the operations owner responsible for responding to recordkeeper setup questions during provisioning
- Attach or describe the legal and registration documents you will supply to enable share-class registration on each platform
Provide Model Portfolio Files for Platform Integration
- Provide sample model portfolio files (CSV or JSON) that reflect your schema and include share-class allocations and rebalancing rules
- Map the model portfolios you require (name each model and list primary share-class per sleeve)
- Specify the file format, schema, and field-level requirements for model ingestion (for example: holdings CUSIP, weight decimal, effective date, target tax lot treatment)
- Describe the frequency and versioning policy for model updates (for example: nightly refresh, monthly versioned files with effective date)
- Define the success criteria for model-file ingestion (for example: import without mapping errors, mapping rate >= 99%, no unmatched CUSIPs)
- Who will maintain and sign off future model changes and what is your expected SLA for responding to mapping exceptions
Deploy Portfolio Construction Toolkit to Advisors
- List the toolkit components you expect delivered (for example: asset allocation calculator, glide path generator, risk-profile questionnaire)
- Specify how you want the toolkit delivered to advisors (for example: embedded widget in advisor portal, downloadable Excel/PDF, API access)
- Indicate the data sources the toolkit should use for performance and benchmark calculations (for example: monthly NAV series, custom benchmark mapping)
- Describe required access controls or firm-level restrictions for advisor firms using the toolkit
- Who on your distribution team will coordinate advisor roll-out and training for the toolkit
- Outline any pre-built model portfolios you want preloaded into the toolkit at launch
Provide Regional Wholesaler Coverage
- List the geographic territories or advisor channels that require dedicated wholesaler coverage
- Specify minimum coverage expectations (for example: number of advisor meetings per month, minimum call frequency)
- Identify the materials wholesalers must carry to meetings (for example: fund fact sheets, model portfolio printouts, prospectus summaries)
- Describe reporting cadence you expect from wholesalers (for example: weekly activity report, monthly pipeline update)
- Who will be the regional contact for escalation if a wholesaler cannot meet coverage commitments
- Estimate the number of advisor relationships per wholesaler to be supported at launch
Deliver Advisor-Facing Webinars and Trainings
- Choose the primary topics for initial webinars (for example: fund overview, portfolio construction using model kits, ERISA considerations for plan sponsors)
- Select desired webinar cadence and duration
- Indicate whether you require continuing education (CE) credit accreditation for webinars and the accrediting bodies required
- Specify the webinar delivery format you prefer (for example: live with Q&A, pre-recorded with on-demand access, hybrid with local follow-ups)
- Who will be your primary audience segments for trainings (for example: independent advisors, broker-dealer wholesalers, retirement plan committees)
- Provide your acceptance threshold for webinar attendance or engagement (for example: minimum live attendance, post-webinar satisfaction score)
-
Mutual Commit
Finalize commercial and legal terms, platform availability commitments, registration and ERISA documentation, and the mutual obligations needed to proceed.
Agreement Modules
- Master Distribution Agreement (MDA)
- Offered Funds & Share Classes Schedule (Exhibit A)
- Commercial Terms & Fee Schedule
- Platform Availability Addendum
- ERISA & Fiduciary Documentation Package
- Registration & Listing Confirmation
- Operations Onboarding Agreement
- Data Security and Regulatory Addendum (conditional)
- Mutual Acceptance & Go-Live Signature Page
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm readiness facts the onboarding depends on — custodial/recordkeeper endpoints, document owners, submission timelines, and required approvals.
Pre-Deployment Questions
Environment and access
- Which custodial / recordkeeper environments must be enabled for this onboarding (select all that apply) — we use this to plan endpoint checks and sequencing.
- Are the buyer's production integration endpoints provisioned and accessible to the seller's operations team? (This determines whether we schedule live submissions or start in sandbox.)
- If not yet available, what date will the production endpoints be available? (date — so we can schedule final provisioning/cutover)
Data and configuration
- Has the share‑class mapping approach been finalized for this lineup? (We need a clear mapping approach before generating deployment configs.)
- If an owner is assigned, who is the share‑class mapping owner (name and role)? (This person will approve the final mapping in the deployment plan.)
- Are the expected file formats and record layouts for platform submissions confirmed for each target platform? (Yes/partial/no — tells us whether to build custom exporters.)
People and ownership
- Who is the primary approval authority for legal/registration package submission (name and role)? (We will route final documents to this approver.)
- Please list operational owners for these streams: onboarding submissions, testing & verification, and escalations (one name + role per stream).
- Has the platform/recordkeeper designated a document owner for ERISA and registration paperwork? (Identifies who will accept and version legal docs.)
Timing and constraints
- What is the target date for the funds to be available on‑platform? (date — so we can derive submission lead times and milestones.)
- Are there known blackout windows, compliance review cycles, or governance meeting dates that will block submissions or go‑live? (List dates or enter 'none'.)
- Is there a required final approval gate before live provisioning (select all that apply) — and please provide the expected decision date in the next field.
- If a final approval gate is required, what is the expected decision date and who signs? (date + name/role)
-
Configuration Details
Capture exact onboarding values the operations team will use — share-class mappings, platform identifiers, file formats, and integration credentials.
Configuration Details
Environments & Endpoints
- Select the integration environment this configuration applies to (Default: Production).
- Enter the platform integration endpoint URL this build will call (format: https://... — enter the exact base URL to paste into the connector settings).
Share-class & Fund Identifier Mappings
- Select the canonical fund identifier used across mapping files and API calls (this is the single identifier the build will match on).
- Enter the canonical mapping file location the build will consume (format: https://... or s3://... or absolute file path). This file contains fund → share-class → platform mappings.
- Select the file format for the share-class mapping file the build will parse.
- Enter the exact field/column name in the mapping file that contains the share-class code (case-sensitive).
File Formats & Transfer
- Select the primary bulk provisioning file format the platform will accept for onboarding submissions (Default: CSV).
Integration Credentials & Exchange
- Enter the non-secret integration identifier the platform will reference (client ID, integration username, or API key name). Do not paste secrets here.
- Enter the team or person who owns the credential and will coordinate the secret exchange (format: 'Team Name — Primary Contact').
- Select the secure channel you will use to exchange the credential secret with the platform (the secret itself will be exchanged via the selected secure channel at deployment).
-
Distribution Onboarding
Execute submissions, provisioning, testing, and verification steps with clear owners, sequencing, and escalation paths to place funds on agreed platforms.
-
-
Success
Monitor adoption and performance against agreed success signals, capture feedback, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live Health Check (Week 1-4)
- First Measurement Review (Week 4-10)
- Acceptance Gate Review (Day 90)
- Quarterly Success Review (Ongoing)
Issues & Enhancements
- Close or reclassify stale operational tickets and assign resolution dates for remaining high-priority items.
- Restate acceptance criteria and targets
- Produce a documented acceptance decision for each numeric criterion recorded in Solution Scope.
- If conditional or failed items exist, agree remediation tasks and a verification date to close them.
- Capture the named signatory or buyer owner decision and publish the acceptance record.
- Publish the acceptance record showing pass/fail per criterion and any conditional remediation with deadlines.
- Execute remediation tasks for conditional items and schedule a verification checkpoint after completion.
- Archive the evidence pack used for the acceptance decision in the shared channel for auditability.
- Trend review of key metrics
- Confirm the solution continues to meet or make progress toward the Solution Scope targets for platform availability and advisor adoption.
- Ensure open operational issues are actively progressing and high-impact enhancements are scheduled.
- Maintain a clear escalation path and cadence for recurring problems so metric drift is addressed promptly.
- Publish quarterly metrics dashboard with platform availability, advisor activity, and net inflow trends for shared review.
- Create a prioritized enhancement backlog with target delivery quarters and acceptance criteria for each item.
- Re-confirm commitments and owners
- Confirm that all deployment tasks required to begin measurement are complete or have committed remediation plans.
- Document high-severity blockers with owners and resolution ETA.
- Ensure the buyer has at least one live path to place orders or include funds in a model portfolio for measurement.
- Publish the deployment validation checklist with status and remediation ETAs.
- Resolve any critical endpoint or registration failures and report completion before the first measurement meeting.
- Collect initial usage logs and onboarding completion data for the first measurement review.
- Present first-measurement data
- Establish whether platform availability and early adoption metrics are tracking to the targets recorded in Solution Scope.
- Agree a prioritized corrective action list with resolution dates to close any gaps before the acceptance gate.
- Confirm the evidence package required at the Acceptance Gate and the named signatory role for the buyer decision.
- Deliver a data pack with platform-by-platform availability, advisor activity by firm segment, and net inflow figures for the acceptance review.
- Implement agreed corrective actions for the top two drivers of underperformance and report progress weekly.
- Compile outstanding documentation (ERISA, registration, share-class mappings) needed to validate platform availability for Solution Scope review.
- Deployment and connectivity validation
- Persistent issues and ticket burn-down
- Root-cause diagnosis
- Present outcome data against each criterion
- Corrective action planning
- Document pass, conditional pass, or fail per criterion
- Enhancement requests and prioritization
- Early adoption signals and usage patterns
- Confirm timeline to Acceptance Gate
- Open issues and defect triage
- Capture formal acceptance decision and signatory confirmation
- Support SLA and escalation review
- Agree remediation plan for unmet criteria
- Immediate remediation plan