Let's Start with Who's at the Table

• Who will be most involved in evaluating a new client-reporting platform? Options: Head of Client Reporting, Chief Operating Officer (COO), Chief Technology Officer (CTO), Head of Operations, Compliance Officer, Relationship Managers, Investor Relations, Portfolio Accounting Lead, External Auditor/Consultant, Other
• For each person you selected, what is their single biggest concern or non-negotiable for this project?
• Who holds final sign‑off authority for selecting a vendor and approving commercial terms? Options: Head of Client Reporting, COO, CFO, CTO, Procurement, Legal, Board/Investment Committee, Other
• Who will be the day‑to‑day owner for integrations and data feed validation once work begins? Options: Internal Integration/Tech Team, Head of Operations, Vendor Implementation Lead, Third‑party Consultant, Shared responsibility, Other
• Which stakeholders must receive regular progress updates and what cadence do they prefer? Options: Weekly written update, Bi‑weekly meeting, Monthly executive summary, Real‑time dashboard access, Ad‑hoc/call only for issues
• Is there an investor, regulator, or external auditor whose comfort must be explicitly satisfied before any cutover?

Why Do Migrations Terrify Your CTO?

• What about your last 18‑month migration effort left your technical team most frustrated, delayed, or risk‑averse?
• What is the maximum migration or parallel‑run timeline your technical leadership would accept before it becomes a project blocker? Options: 1–2 months, 2–4 months, 4–6 months, 6–12 months, Unsure / depends
• How much disruption to quarter‑end reporting is tolerable during migration? Options: No disruption allowed (parallel only), Minor impact (≤1 business day), Moderate (2–3 business days), Major (>3 days) with approvals, Only scheduled weekend windows
• Which contingency or rollback capabilities are non‑negotiable for your CTO to greenlight a migration? Options: Full rollback plan, Parallel production for 1–2 cycles, Read‑only test environment with live data, Automated validation checks before cutover, Dedicated on‑call vendor support, Other
• Which technical metrics will your team use to evaluate success (pick all that apply)? Options: Data match/match rate, Integration latency, Throughput at quarter close, Reconciliation exception rate, System uptime/availability, Security/compliance posture, Other

When a Quarter Misses the Mark, Who Feels It?

• How close did you come to losing a client after your last late or inaccurate reporting cycle—and what made that moment feel most urgent?
• How often in the past 12 months have reports been delivered late or with material inaccuracies? Options: Every quarter, 2–3 times, Once, Never, Unsure
• In the last incident, approximately how many client accounts required manual correction? Options: 1–50, 51–200, 201–400, 401–1,000, 1,000+
• Roughly how many staff‑hours were consumed resolving that quarter's issues (total across teams)? Options: 0–50 hours, 51–200 hours, 201–500 hours, 501–1,000 hours, 1,000+ hours
• Who managed investor communications during the incident, and how did investors respond (tone/asks)? Options: Investor Relations, Relationship Manager, Head of Client Reporting, COO/Executive, Legal/Compliance, Other
• What formal escalation path exists today when a reconciliation exception threatens delivery? Options: No formal path (ad‑hoc), Standard operating procedure, Cross‑functional war room, Escalation to executive committee, Other
• Did compliance, auditors, or major clients raise formal concerns after the incident? Options: Formal finding, Written warning/observation, Informal concern/discussion, No external concern, Unsure

If Reports Were Always Right and On Time, What Would Change?

• If you could guarantee reconciliation accuracy and on‑time delivery every quarter, what would your team stop worrying about and start doing instead?
• Which delivery SLA after quarter close would represent a meaningful improvement for you? Options: Same day, Next business day, Within 48 hours, Within 5 business days, Other
• What minimum data/performance match rate would you require to consider a new system acceptable? Options: >99.99%, 99.9%–99.99%, 99.5%–99.9%, 99%–99.5%, <99%
• Which investor‑retention signals would you monitor to prove the platform's business value? Options: Renewal/retention of institutional clients, Reduction in investor inquiries, Improved NPS/CSAT, Stability/growth of AUM, Fewer regulatory findings, Other
• How much client‑level formatting flexibility do you require (branding, disclosures, custom pages)? Options: Highly customized per client, Templates with minor variations, Standardized templates by segment, Minimal customization required, Other
• Who across ops, compliance, and RM must sign off that 'good' has been achieved? Options: Operations, Compliance, Relationship Management, COO/Executive Sponsor, Head of Client Reporting, Other

What’s Hidden in Your Reconciliation Failure Modes?

• What recurring mismatch or data trap keeps showing up in your reconciliations despite repeated fixes?
• Which exception types occur most frequently in your quarter‑end reconciliations? Options: Custodian feed/price mismatch, Corporate actions posting, Cash posting differences, Security identifier mismatches, FX/valuation timing differences, Position breaks, Other
• For a typical exception, what is the average time‑to‑resolution today? Options: Under 4 hours, 4–24 hours, 1–3 days, 3–7 days, Over 7 days
• How many manual touchpoints does resolving an exception usually require (triage, research, approval, correction)? Options: 1–2 touchpoints, 3–4 touchpoints, 5–7 touchpoints, 8+ touchpoints
• Which tools or tracking methods do you rely on to manage exceptions today? Options: Spreadsheets, Internal ticketing system, Dedicated reconciliation software, Emails/Slack chains, Custom internal app, Other
• What change—technical, process, or people—would most relieve the stress on your team who resolves exceptions?

If We Ran One Quarter Together, What Would Make You Say Yes?

• What single outcome from a sample‑quarter test would be the clearest signal that we should proceed to a pilot or contract?
• Which acceptance criteria will you require for the sample quarter (pick the items you will check)? Options: Match rate threshold, Formatting and disclosures sign‑off, On‑time delivery target, Exception count ceiling, Audit trail & reproducibility, Integration stability
• What match‑rate band would you accept as passing for the sample quarter? Options: >99.99%, 99.9%–99.99%, 99.5%–99.9%, 99%–99.5%
• For the sample quarter, which delivery timing would you accept as a pass? Options: Same day, Next business day, Within 48 hours, Within 5 business days
• Which report elements must be demonstrably customizable during the test (select all that will be evaluated)? Options: Branding and logos, Legal disclosures and footers, Page ordering and TOC, Table and chart formatting, Granularity/aggregation by client, Export formats (PDF, XLSX)
• Who will provide official sign‑off after the sample quarter and what evidence will they require?
• What level of vendor support during the test will feel sufficient to you? Options: Full hands‑on vendor support, Regular scheduled check‑ins, On‑demand support with SLAs, Self‑service with docs and templates, Other

Who Will Own Day‑One After Cutover?

• If something critical broke the weekend after cutover, who do you want on the phone immediately and why?
• Who will be responsible for data remediation tasks post‑cutover (internal team, vendor, shared model)? Options: Vendor responsibility, Internal operations team, Shared responsibility (vendor + internal), Third‑party consultant, Other
• Which governance checkpoints must be completed before we flip the switch (choose all that must be green)? Options: End‑to‑end data validation, Compliance/legal sign‑off, Advisor/trainer sign‑off, Integration verification, Stakeholder executive sign‑off
• What concrete rollback triggers would cause you to revert to legacy reporting during/after cutover? Options: Critical client report mismatch, Regulatory non‑compliance, Unresolved exceptions above threshold, Investor escalation/complaint, System availability outage
• Who will own post‑cutover triage, priority assignment, and SLA enforcement? Options: Vendor support team, Internal operations team, Joint war‑room model, Dedicated program manager (internal), Other
• What runbooks, playbooks, or documentation do you require to feel confident on day‑one? Options: Integration diagrams and schemas, Step‑by‑step runbooks, Escalation matrix with contacts, Test logs and validation reports, Training recordings and quick‑start guides

How Do You Want Us to Keep You Calm and Informed?

• What vendor communication habit has felt worst to you in past engagements—and what would be the exact opposite that would restore your confidence?
• What update cadence would feel right during discovery, integration, parallel production, and cutover phases? Options: Weekly, Bi‑weekly, Twice weekly, Daily standups during critical windows, On‑demand for major issues
• Which formats do your stakeholders prefer for progress and issue updates? Options: Written status report, Live demos/walkthroughs, Shared dashboard access, Recorded walkthroughs, Executive one‑page summary
• Which KPIs would you like visible on a shared dashboard throughout the engagement? Options: Data match rate, Open exceptions count, Time‑to‑deliver, Migration progress %, Sample test pass rate, Number of active incidents
• Who should be included in executive‑level briefings versus operational check‑ins (list names/roles for each)?
• How should urgent issues be escalated to ensure immediate attention? Options: Phone call to escalation list, SMS for critical incidents, Dedicated Slack/Teams channel, Email with high‑priority flag, On‑call rotation

Quick Pulse: Who You Are and What Just Happened

• Tell us your role and the team that will be most involved in the next quarter-end review. Options: Head of Client Reporting, Chief Operating Officer, Chief Technology Officer, Fund Administrator Lead, Operations Manager, Other
• In one sentence, summarize what went wrong on the last quarter close and how late reports impacted external stakeholders.
• How many accounts and client reports were affected by the last reconciliation issue? Options: Fewer than 50, 50–199, 200–399, 400–999, 1,000 or more, Unsure
• Who is the primary internal audience for the quarter-end reports (who complains first when things go wrong)? Options: Relationship Managers, Compliance/Legal, Portfolio Management, Institutional Sales, Client Services, Other
• How would you rate the emotional tone after the last late/incorrect report—were people frustrated, panicked, resigned, or something else? Options: Very frustrated, Annoyed but pragmatic, Concerned about client loss, Resigned—this is normal, Other

If Next Quarter Missed Again, Who Actually Pays the Price?

• If a similar late or inaccurate delivery happened next quarter, what is the most likely business consequence you fear? Options: Loss of an institutional investor, Regulatory/compliance escalation, Damage to firm reputation, Internal leadership consequences, Increased operational cost, Other
• How confident are you that a single late or wrong report could trigger investor attrition in your top clients? Options: Very confident, Somewhat likely, Possible but unlikely, Highly unlikely, Unsure
• Which investors or client segments are most sensitive to reporting delays and accuracy issues? Options: Institutional investors, High-net-worth individuals, Family offices, Advisory/relationship-managed clients, All of the above, Other
• When you think about the worst-case downstream impact of a missed deadline, what specific outcome keeps you up at night?
• Who internally would have to be convinced that a change is worth the risk—list the decision roles and one-line concerns each would raise.

Walk Me Through a Quarter-End—Give Me the Blood and Guts

• Describe the exact sequence of steps from receipt of custodian/PAF files to final report delivery—who touches what and when?
• Which systems and feeds are involved today (select all that apply)? Options: Custodian feed A, Custodian feed B, Portfolio Accounting System, Market data vendor(s), Internal spreadsheets, Custom middleware, Other
• How long does each major stage typically take (data ingest, reconciliation, calculations, formatting, QA, delivery)? Please provide estimated hours or days per stage.
• Who is accountable for resolving a reconciliation exception during close, and how is that handoff tracked? Options: Client Reporting Lead, Operations/Back Office, Portfolio Accounting, IT/Integration Team, Shared responsibility, Other
• What checkpoints or QA gates do you have before client reports are signed off? How often are they bypassed under time pressure? Options: Multiple formal gates, rarely bypassed, Some gates, occasionally bypassed, Informal checks only, often bypassed, No formal QA gates, Unsure
• When a reconciliation mismatch is discovered, what is the most common immediate workaround used to meet the deadline? Options: Manual spreadsheet adjustment, Exclude affected accounts from run, Generate estimates/pro-forma numbers, Escalate and delay delivery, Other

Where the Process Breaks: The Reconciliation Pain

• What reconciliation failure modes happen most often—missing positions, pricing mismatches, corporate actions, mapping errors, or something else? Options: Missing positions, Pricing mismatches, Corporate actions, Data mapping errors, Trade breaks, Other
• How frequently do reconciliation exceptions occur per quarter and how many require manual intervention? Options: Less than 10 exceptions, 10–49, 50–199, 200–499, 500+, Unsure
• For exceptions that need manual correction, what is the average time-to-resolution and who performs that work?
• What proportion of manual fixes are repeat issues (same root cause reappearing each quarter)? Options: Most are repeats, Some repeats, Few repeats, Hardly any repeats, Unsure
• When you dig into root causes, are problems usually upstream (custodian/PAF), inside mappings/transforms, or downstream in your report templates? Options: Upstream (custodian/PAF), Mapping/transforms, Downstream templates, Multiple layers equally, Unsure
• Tell us about a reconciliation exception that became a near-loss event—what happened, who responded, and what was the outcome?

The Human Cost: Who’s Burning Hours and Why?

• Estimate the total staff-hours spent per quarterly cycle on reconciliation, manual calculations, and report assembly (exclude automated processing). Options: Under 40 hours, 40–159 hours, 160–399 hours, 400–999 hours, 1,000+ hours, Unsure
• Which roles absorb the overtime when close gets messy—junior ops, senior analysts, RM team, or contractors? Options: Junior operations staff, Senior analysts, Relationship managers, IT/Integration, Contractors/temps, Other
• How does the recurring workload affect retention, morale, or the ability to focus on higher-value work (sales support, analysis)?
• Have you quantified the cost of manual work (including escalations and error remediation) over the trailing four quarters? If so, please share the figure or how you estimate it.
• Are you currently using temporary headcount or consultants during quarter-end? If yes, how often and why? Options: Yes, every quarter, Yes, sometimes, Rarely, Never, Unsure

Why Migration Fears Persist—What's the Real Risk?

• When your CTO says migration took 18 months last time, what specifically were the pain points—data loss, business disruption, resource drain, or stakeholder fatigue? Options: Data loss issues, Business disruption during cutover, Resource/time drain, Vendor/partner coordination problems, Stakeholder fatigue, Other
• What are the top three non-negotiable risks the tech team wants mitigated before approving any platform change?
• How tolerant is leadership for a phased parallel run versus a big-bang cutover—are time-to-value and reduced disruption prioritized differently across stakeholders? Options: Prefer parallel phased approach, Open to either with safeguards, Prefer big-bang to shorten timeline, Undecided/depends on vendor plan
• What historical integration points or custom interfaces are likely to require the most engineering effort?
• If we could guarantee no missed reporting cycles during migration, what would be the single most persuasive argument for your CTO to engage?

If We Could Snap Our Fingers: What Would Change?

• What target delivery SLA and accuracy thresholds would feel genuinely transformational to your team and your most sensitive clients? Options: Same-day delivery with 99.9% accuracy, Delivery within 24–48 hours with 99% accuracy, Delivery within 3 business days with 98% accuracy, Other
• Describe in practical terms what a successful sample-quarter test looks like for you—what outputs, metrics, and stakeholder signoffs are required?
• Beyond timing and numbers, what formatting or customization capabilities would delight your relationship managers and reduce escalations? Options: Branded templates per RM, Dynamic disclosure blocks, Client-specific performance views, Interactive/digital delivery, Other
• Which compliance or third-party standards (e.g., GIPS) must be demonstrably met before you can consider production cutover? Options: GIPS, Internal compliance checklist, Client-specific contractual requirements, External auditor signoff, Other
• If investor retention improved, how would you prefer to measure that impact—retention rate, NPS, reduced service tickets, or ARR impact? Options: Retention rate, Net Promoter Score (NPS), Reduction in service tickets, Revenue/ARR impact, Other

Proof, Not Promises: What Would Make You Say Yes?

• What are the non-negotiable acceptance criteria for a sample-quarter run to be considered valid?
• Which comparisons matter most in the side-by-side test—calculation parity, row-by-row numbers, formatting fidelity, or delivery timing? Options: Calculation parity, Row-by-row matching, Formatting fidelity, Delivery timing, All of the above
• How will your team validate differences that arise—do you want a joint triage session, documentation of transforms, or configurable audit trails? Options: Joint triage session, Detailed transform documentation, Configurable audit trails, Automated reconciliation reports, Other
• What sample-quarter dataset would you be comfortable sharing for a blind test (number of accounts, asset classes, and any redaction requirements)?
• Who needs to sign off on the sample-quarter results for you to move to parallel production? Options: Head of Client Reporting, COO/Operations, CTO/IT, Compliance/Legal, External auditor, Other
• What would be a fair timeline for running, reviewing, and agreeing acceptance on the sample-quarter output? Options: One week, 2–3 weeks, One month, Longer than one month, Unsure

Decision Signals: Who, When, and What Needs to Happen Next

• Who are the decision-makers and influencers that must be engaged in the next 30 days to keep momentum?
• What internal evidence or reports do you need to present to get a budget or pilot approved (cost-savings, risk reduction, client impact)? Options: Cost-savings estimate, Risk mitigation plan, Client impact case studies, Operational runbook, Other
• What are the biggest internal objections you expect to hear, and which stakeholder will raise each objection?
• If we proposed a parallel-run plan that left production untouched for one quarter, how likely would you be to proceed? Options: Very likely, Somewhat likely, Unsure, Unlikely
• What would you like our team to deliver before the next meeting to help you build the internal case (technical checklist, timeline, cost estimate, sample test plan)? Options: Technical checklist, Integration timeline, Cost estimate, Sample test plan, All of the above, Other

Where Do You Really Stand? — A quick confidence check

• How confident are you that your team could support a parallel production run alongside the legacy process this quarter? Options: Very confident, Somewhat confident, Concerned, Not possible this quarter
• Who would be the day-to-day owner for the parallel run and cutover? Name and title, please.
• What is the single biggest fear your team has about running parallel production?
• How much staff capacity (full-time equivalents or hours per week) can you realistically commit to onboarding, parallel testing, and cutover support? Options: < 10 hours/week, 10–20 hours/week, 20–40 hours/week, > 40 hours/week
• Do you currently have a documented runbook or playbook for quarter-end production that we can review? Options: Yes—up to date, Yes—but outdated, No, Partial/under development

If We Tried to Turn This On Tomorrow, What Would Break?

• If we switch to parallel production tomorrow, which parts of the quarter-end workflow do you expect will need the most human intervention? Options: Custodian data reconciliation, Account mapping & identifiers, Corporate actions processing, Manual performance adjustments, Report formatting exceptions, Other
• How many reconciliation exceptions (custodian vs portfolio accounting) typically require manual investigation each quarter? Options: 0–20, 21–100, 101–400, 400+
• Which reconciliation failure modes are most common for you? Give specific examples (e.g., missing ticker mapping, cash breakout, corporate action timing).
• How often do ad-hoc template or disclosure requests during the cycle create last-minute production changes? Options: Very often, Occasionally, Rarely, Never
• Are there known data transforms or manual spreadsheets that are critical to your current delivery (list names or describe purpose)?

Who Would Be Fired Up or Furious? — Stakeholder map and politics

• Who are the decisive approvers for go/no-go on a parallel run and final cutover (names/titles/functions)?
• Which functions must sign off on production readiness before we can proceed (select all that apply)? Options: Reporting/Client Services, Operations/Back Office, Technology/CTO, Compliance/Legal, Risk, Investor Relations
• Which stakeholder is most likely to block or delay a cutover, and what has motivated that stance in the past?
• How do your governance and escalation paths work during a failed cycle—who gets notified, and in what order?
• Are there internal politics or vendor relationships (e.g., incumbent vendor contracts) that we should anticipate influencing timeline or decisions? Options: Yes—contractual/penalty concerns, Yes—political preference, No, Unsure

Can Your Data Actually Tell the Story We Need?

• Which custodians, portfolio accounting systems, and market data providers are in scope for the parallel run? (Please list all.)
• Select the types of data feeds we will need to ingest and test during parallel production. Options: Custodian trade/position feeds (SFTP/API), Portfolio accounting exports (CSV/XML), Pricing/market data (vendor API), Corporate actions feed, Benchmarks/indices, Other
• Are deterministic mapping keys consistent across systems (account IDs, ISIN/CUSIP, client codes), or do we expect crosswalk tables and manual mapping? Options: Mostly consistent, Some inconsistencies—need mapping, Largely inconsistent—requires extensive mapping, Unknown
• Do you have a sample quarter dataset we can load that represents common edge cases (multi-currency, corporate actions, illiquid assets)? Options: Yes—anonymized sample available, Yes—but not anonymized, No sample exists, Can create if guided
• If a sample dataset exists, how many accounts and what asset mix does it contain (approximate counts and percentages)?
• Are there regulatory or client confidentiality constraints that prevent sharing raw data even for testing (and what anonymization level is required)? Options: No constraints, Anonymized data only, Encrypted/controlled environment only, Other restrictions

If the Parallel Run Fails, What's Your Plan B?

• Do you currently have a documented rollback plan for production changes of this magnitude? Options: Yes—tested recently, Yes—but untested, No, Partial plan
• What are your acceptable recovery time and recovery point objectives (RTO/RPO) for quarter-end reporting? Options: RTO within hours / RPO within minutes, RTO within 24 hours / RPO within an hour, RTO 24–72 hours / RPO within a day, Longer—depends on circumstances
• Who would execute the rollback and who must approve it? Provide roles rather than names if needed.
• What are the non-negotiable acceptance gates that must be met before a full cutover (e.g., reconciliation match rate, SLA times, compliance signoffs)?
• If a parallel run uncovers systemic calculation differences from legacy output, how do you prefer we handle client communications and remediation? Options: Pause cutover and reconcile, Document differences and proceed, Escalate to compliance/legal before client contact, Other

Regulators and Compliance: Who Signs Off and How Fast?

• Which compliance frameworks or audit standards must the output meet (e.g., GIPS, internal compliance, external auditors)? Options: GIPS, Internal Compliance Policy, External Auditor Requirements, Client-specific requirements, Other
• Who is the compliance lead that must sign off on parallel production artifacts and who will approve final reports?
• What artifacts does compliance require for signoff (e.g., reconciliation logs, calculation traceability, change control records)? Options: Reconciliation reports, Calculation provenance, Access logs, Test results, Change approvals, Other
• How long does your compliance/legal signoff cycle usually take from submission to approval? Options: Same day, 1–3 business days, 4–10 business days, Longer than 10 business days
• Are there specific internal or external audits scheduled around your next quarter-end that could affect availability for testing or signoff? Options: Yes—internal audit, Yes—external audit, No audits scheduled, Unsure

Logistics: Timing, Access, and Test Windows

• What are your preferred windows for integration and parallel testing (days of week, hours, blackout periods)?
• What types of access will we need and how are they provisioned (VPN, IP allowlist, SFTP credentials, API keys)? Options: VPN, IP allowlist, SFTP credentials, API keys/tokens, Other
• Who controls credential issuance and how long does it typically take to grant external vendor access?
• Do you have weekend or after-hours staff who can support a cutover or will support be limited to business hours? Options: 24/7 support available, Extended hours/weekend support available, Business hours only, Limited on-call support
• Are there IP or network restrictions we must plan around (e.g., strict egress rules, proxy requirements, restricted ports)? Options: No restrictions, Basic egress restrictions, Strict proxy/VPN required, Other—details required
• Do you have a staging/testing environment that mirrors production for validation, or will we be testing directly against production feeds with safeguards? Options: Full staging environment, Partial staging (subset of accounts), Direct production with safeguards, No staging—needs setup

How Will We Know We Succeeded? — Acceptance, metrics, and fallout plan

• What are the measurable acceptance criteria for parallel production (e.g., reconciliation match rate %, performance calculation parity, report formatting accuracy)?
• For sample-quarter validation, what tolerance ranges are acceptable for differences vs legacy (select common thresholds)? Options: Exact match required, Differences <= 0.1%, Differences <= 0.5%, Differences <= 1%, Higher—by agreement
• Who will be the final signatory that declares the parallel run successful and authorizes cutover?
• What post-cutover monitoring windows and SLAs do you expect for issue resolution and investor impact mitigation? Options: 24/7 immediate response first 48 hours, Business hours response first week, Tiered response SLA, Other
• How should we document and surface reconciliation exceptions and remediation steps during the parallel run for auditability? Options: Shared ticketing system, Daily exception report, Weekly audit package, Real-time dashboard, Other
• If investor-facing differences are discovered, what is the preferred client communication approach (proactive disclosure, wait until fixed, tiered messaging)? Options: Proactive disclosure with context, Fix first, then inform, Tiered messaging based on materiality, Other

Final Practicalities: Permissions, Training, and Support

• What training format will best prepare your advisors and operations team for parallel production and cutover (live workshops, recorded modules, runbooks)? Options: Live workshops, Recorded modules, Detailed runbooks, Shadow sessions during parallel run, Combination
• Will you require role-based access controls and audit trails for the vendor team in your environment? If yes, what level of segregation is needed? Options: Full RBAC with least privilege, Read-only access for most, Shared service account, Vendor limited to specific IPs
• What ongoing support model do you expect post-cutover (SLA hours, dedicated CSM, escalation path)? Options: Dedicated CSM + 24/7 SLA, Business hours support + escalation, On-demand support, Other
• Are there any third-party vendors (custodians, custodial gateways, accounting vendors) who will require separate contracts or approvals for our access? Options: Yes—custodians, Yes—portfolio accounting vendor, Yes—market data vendor, No, Unsure
• What practical blockers should we solve first to avoid timeline slips (e.g., contracts, credential lead time, resource availability)?

Quick Snapshot — Where We Are Right Now

• In one sentence, what single outcome from this sample-quarter validation would make you feel the project is on track?
• Which of these best describes the current status of the sample-quarter test? Options: Not started, Data loaded but not processed, Processed — results under review, Processed — issues found, Complete and accepted
• Which legacy artifacts will we use as the baseline for comparison (select all that apply)? Options: PDF client reports, CSV exports / ledgers, Internal reconciliations/spreadsheets, Performance summary reports, Other
• Who will be the primary contact for questions about legacy outputs, and what’s their preferred channel (email, Slack, phone)?
• How confident are you that the chosen sample quarter represents the variety of issues you face each cycle? Options: Highly confident, Somewhat confident, Not confident, Unsure — needs review

Why Are We Still Trusting Old Outputs?

• How comfortable are you relying on legacy 'accepted' reports that required manual fixes to meet deadlines? Options: Completely comfortable, Wary but pragmatic, Uncomfortable, Not applicable
• When you say 'manual fixes', what types of fixes happened most often in that quarter? Options: Reconciliations/position adjustments, Data formatting for PDFs, Manual performance adjustments, Disclosure or compliance edits, Other
• Roughly how many manual interventions occurred during that quarter’s production cycle? Options: None, 1–10, 11–50, 51–200, 200+
• Tell us a brief example of a manual correction that changed the narrative you shared with an investor (what happened and why it mattered).
• What worries you most about replicating those legacy manual fixes in an automated environment?

When Accuracy Really Mattered

• Which institutional relationship felt most exposed by late or incorrect reporting, and what would losing that relationship mean for the business?
• In the last 12 months, how many institutional clients cited reporting quality as a reason for concern or review? Options: 0, 1–2, 3–5, 6+
• How would you describe the internal reaction when quarter reports were late—informal frustration, escalations to leadership, or formal remediation? Options: Informal frustration, Escalations to leadership, Formal remediation plan, No notable reaction
• Who fields investor complaints about reporting and what is the typical time to resolution today?
• Beyond retention, what consequences worry you when custodian and accounting data don't align? Options: Regulatory/compliance exposure, Investor redemptions, Operational disruption, Delayed delivery, Other

What Would Passing the Sample Quarter Actually Prove?

• If our sample-quarter outputs match your legacy results, what concrete change would that enable you to do tomorrow?
• Which of these acceptance signals are mandatory for you (choose all that apply)? Options: Exact numeric parity, Material parity within tolerance, Formatting parity, GIPS compliance confirmed, Operational repeatability
• What numeric tolerance for small variances would you accept between legacy and new outputs? Options: 0% (exact match), 0.01–0.1%, 0.1–0.5%, 0.5–1%, Above 1% — explain in comments
• Do you require external GIPS certification, an internal compliance signoff, or both before accepting results? Options: External GIPS certification, Internal compliance signoff, Both, Neither / Unsure
• Which stakeholders must sign the acceptance (list roles) and what is each person’s pass/fail expectation?

Where Reconciliations Hide Their Secrets

• Which reconciliation exception pattern do you expect will cause the first automation failure—and why has it persisted upstream?
• Which feed discrepancies occur most often in your environment? Options: Position mismatches, Trade timing differences, Corporate actions processing, Currency/FX variances, Missing holdings, Other
• How are exceptions triaged today and which team owns the investigation? Options: Client Reporting, Operations / Back Office, Custodian, Third-party vendor, Shared responsibility
• On average, how many open reconciliation exceptions remain unresolved at quarter-end for the sample set? Options: 0, 1–10, 11–50, 51–200, 200+
• Which specific data fields (e.g., CUSIP, lot, settlement date, fx rate) are the recurrent root causes in those exceptions?

If We Could Flip the Switch — What Would Success Look Like?

• Imagine the next quarter runs without manual reconciliations—what would your team stop worrying about first?
• Which measurable benefits would convince leadership this cutover was worth it? Options: Faster delivery (days saved), Reduced staff-hours per cycle, Lower exception count, Fewer client escalations, Improved client satisfaction
• What target SLA for report delivery after cutover would be meaningful to your clients? Options: Same day after quarter close, 1 day, 2–3 days, Within a week
• How should we quantify investor-retention impact attributable to improved reporting (select preferred metrics)? Options: Churn rate, Client satisfaction / NPS, Net flows, Direct client feedback or surveys, Other
• Which internal KPIs will you track to prove ongoing success post-cutover? Options: Time-to-delivery, Exception count, Staff-hours per cycle, Compliance findings, Client complaints

Who Owns The Risk If Things Go Sideways?

• If the parallel run surfaces a client-impacting error, who is accountable for customer communication and remediation?
• Who is the operational owner for cutover decisions, and who is the escalation point for executive trade-offs? Options: Head of Client Reporting, COO, CTO, Project Manager, Other
• What is the rollback threshold that would trigger returning to legacy production (e.g., % of clients affected, materiality level)?
• What remediation resources are pre-authorized (internal team hours, external consultants, contingency budget) in case urgent fixes are required? Options: Dedicated internal team hours, External consultant pool, Contingency budget, No resources pre-authorized
• How should we handle investor communication if an issue reaches clients—proactive outreach, templated correction, or wait-and-see? Options: Proactive outreach by RM, Template apology + corrected report, Regulatory/legal led communication, Wait unless material

Operational Readiness — Are the Pieces in Place?

• Do your current custodial and accounting feeds and access controls allow us to recreate production-grade results, or are critical pieces missing? Options: All pieces available, Some credentials missing, Feeds incomplete, Unsure — need to audit
• Which custodians and portfolio/accounting systems must be connected for this validation (select all that apply)? Options: State Street, BNY Mellon, Northern Trust, SimCorp Dimension, SS&C/Advent, Eze/Other OMS, Other
• Are service accounts and test credentials available for our environment, or will we need access requests? Options: Yes — ready, Partially — some keys missing, No — must request, Unsure
• Which test dataset approach do you prefer: full production extract, representative sample subset, anonymized synthetic data, or a mixed approach? Options: Full production extract, Representative sample subset, Anonymized synthetic, Mixed approach
• Who must complete compliance, privacy, or legal approvals before we run live client data in the validation environment (list roles)?

Decision Momentum — Next Steps and Timeframes

• If we deliver a clean validation in X days, what concrete decision will you make and who is authorized to sign it off?
• What is your ideal target date for cutover after a successful validation? Options: Within 2 weeks, Within 1 month, 2–3 months, Longer / Depends
• Which internal approvals or governance forums must review the validation results before acceptance (select all that apply)? Options: Steering committee, Executive signoff, Compliance review, CTO/Engineering review, Client-facing review, Other
• What reasons would lead you to delay cutover even after passing validation (select likely scenarios)? Options: Undocumented edge cases found, Stakeholder disagreement, Regulatory compliance concerns, Insufficient advisor training, Other
• What format of the validation deliverable will help you make a decision (detailed diffs with reconciliation notes, executive summary, raw exports, or all of the above)? Options: Detailed diffs + reconciliation notes, Executive summary, Raw exports/CSV, All of the above
• Who should be included in the final acceptance demo and sign-off meeting (list roles and email addresses if possible)?