Why we're talking — one clear sentence

• In one short sentence, what outcome would make this conversation worth your time today? Options: Eliminate NAV breaks, Real-time position visibility, Clear compliance gating pre-trade, Reduce reconciliation costs, Other (I will explain)
• What event or trigger brought this issue to the surface for you (pick the single most important)? Options: External audit finding, Client reporting error, Internal NAV discrepancy, Regulatory notice, Planned platform review, Other (please describe)
• Who on your leadership and ops teams should be part of diagnosing and approving a solution? Options: COO, Head of Investment Ops, Head of Investment Technology, CIO/Portfolio Manager, Head of Compliance, Head of Risk, Head of Custody/Settlement, Procurement/Legal
• How would you describe the emotional tone this problem creates among your executives and front office (briefly)? Options: High anxiety / urgent, Frustration with legacy tooling, Concerned but tolerable, Embarrassment / reputational worry, Optimistic if fixed
• Tell us a single recent story where a reconciliation failure or NAV error changed a decision or client outcome — what happened and how did it feel?

If a NAV error hit your flagship fund tomorrow...

• If a NAV error hit a flagship fund tomorrow, what would be the immediate operational and commercial consequences?
• How many NAV-related incidents affecting client reporting or valuations have you had in the past 24 months? Options: 0, 1, 2–3, 4–6, 7+
• When you investigated past incidents, which root causes appeared most often? Options: Custodian feed mismatches, Trade capture gaps from OMS, Manual spreadsheet errors, Reference data mismatches, Corporate actions processing, Other
• How do you currently detect NAV or compliance breaks—automated alerts, daily reconciliations, audits, or ad-hoc client complaints? Options: Automated real-time alerts, End-of-day reconciliations, Weekly/monthly audit cycles, Client reporting triggers, Manual spot checks
• On average, how long does it take to identify a NAV discrepancy vs. how long to fully remediate it? Options: Identify < 1 hour / Remediate < 1 day, Identify < 1 day / Remediate 1–3 days, Identify 1–3 days / Remediate 1–2 weeks, Identify 1+ weeks / Remediate 2+ weeks, Varies widely

Who's actually steering the ship — and how much risk will they accept?

• When a tradeoff arises between keeping trading live and guaranteeing perfect data during migration, which option typically wins here? Options: Business continuity (keep trading live), Data perfection first (pause risky flows), Depends on asset class, Case-by-case escalation
• Which decision-makers must sign off on a migration, integration, or SLAs before you proceed? Options: COO, Head of Investment Ops, Head of Investment Technology, Head of Compliance, CIO/Portfolio Manager, Legal/Procurement, Custodian/Agent bank
• What timeline would count as accelerated, normal, or slow for a migration project of this scope? Options: Accelerated: < 3 months, Normal: 3–6 months, Slow: 6–12 months, Long-term: 12+ months
• How would you describe your leadership’s appetite for shared vs. vendor-held migration risk (choose the best fit)? Options: Vendor takes most risk, Shared responsibility with clear SLAs, Client retains most remediation risk, Undecided / negotiation required
• What non-negotiable legal or commercial clauses typically block your team from accepting migration risk (brief examples)?

What the system map really looks like (no euphemisms)

• If I asked for a single diagram showing where positions, trades, and corporate actions flow, how accurate would your current map be: a complete picture, something passable, or chaos? Options: Complete and audited, Passable but incomplete, Fragmented and partially documented, No reliable map / chaotic
• Which systems hold canonical position data for each asset class today (select all that apply)? Options: Custodian feeds, OMS/EMS, Portfolio accounting system, Risk system, Spreadsheets, Third-party reconciler, Other
• Which asset classes create the most reconciliation headaches for you? Options: Equities, Linear fixed income, Derivatives/OTC, Private debt/credit, Fund-of-funds / nested structures, FX/Cash, Other
• What specific reconciliation failure modes recur most often (e.g., broken corporate actions, trade timing, mismatched identifiers)?
• Do you have recent audit findings or internal post-mortems related to NAV/compliance incidents that we can review? Options: Yes - formal audit report, Yes - internal post-mortem, Informal notes only, No documented findings
• Can you provide a list of representative sample portfolios (by strategy, liquidity, and size) that we should use for parallel testing? Options: Yes, full list available, Yes, but limited subset due to privacy, We need guidance on which to extract, No, not available yet

What 'good' actually looks like for your COO and Head of Investment Ops

• What single metric would make the COO say the program succeeded (e.g., zero NAV breaks for X months, reduction in reconciliation FTEs)? Options: Zero NAV breaks for X months, < X reconciliation errors per month, Reduce manual reconciliation hours by X%, Real-time positions for all traded assets, Other (please specify)
• Which measurable success signals should we include in an acceptance criteria dashboard (pick up to five)? Options: NAV parity with legacy system, Real-time position latency < X seconds/minutes, Compliance check latency < X ms/s, Settlement mismatch rate < X%, Performance attribution accuracy within tolerance, Data lineage and auditability present, Reduction in time-to-report
• How tightly does the Head of Investment Ops want to define tolerances for parity during parallel testing (e.g., exact match, 99.9%, materiality-based)? Options: Exact match required, 99.9% parity acceptable, Materiality band per asset class, Open to negotiation after pilot
• How will you measure success culturally — what behavior change by PMs/Ops would signal real adoption? Options: PMs trust the platform and stop manual checks, Ops reduce ad-hoc spreadsheet workflows, Compliance uses platform for pre-trade gating, Fewer urgent late-night reconciliation tasks, Other
• What would be the reputational or financial cost if the program met technical targets but failed to convince stakeholders (i.e., technical success but no adoption)?

The migration and testing pressure cooker — can we survive the heat?

• If our platform cannot reconcile your sample portfolios to agreed parity during parallel, would you pause the rollout, continue with mitigation, or renegotiate scope? Options: Pause rollout, Continue with mitigation plan, Renegotiate scope and timelines, Escalate to executive review
• What specific sample portfolio characteristics must be included in testing to give you confidence (examples: illiquid private assets, nested fund structures, derivatives exposure)?
• What parity threshold and time window would you accept for different asset classes during parallel testing (e.g., equities 100%, private assets 99% within 48 hours)?
• Are your custodians and prime brokers prepared to support a parallel-run test environment and extended debug windows? Options: Yes, fully supportive, Some will support, some will not, Not sure — need to check, No, not currently supportive
• Who will provide the test datasets, and are there legal or privacy steps we must take before ingesting them? Options: Client provides sanitized datasets, Vendor extracts and anonymizes samples, Legal needs to approve NDA/data processing, We cannot provide live samples
• What is your ideal duration for a parallel run before making a go/no-go decision? Options: 1 week, 2–4 weeks, 1–3 months, Longer than 3 months

Who owns what when things go wrong — accountability and escape hatches

• If migration causes a NAV restatement or settlement delay, who is expected to own remediation and client notification? Options: Vendor owns remediation and client comms, Client owns remediation, vendor supports, Shared ownership with joint playbook, Undecided — needs negotiation
• What SLA levels and financial/remedial remedies are necessary before your legal team will sign off? Options: 99.9% availability with penalties, SLA + service credits, Operational playbook + no financial penalty, Specific indemnities required
• What are your non-negotiable rollback conditions during cutover (examples: X unresolved parity exceptions, Y failed compliance checks)?
• Who are the escalation contacts (roles and backup) for incidents during parallel and cutover windows?
• How do you prefer remediation ownership to be recorded—SLA ticketing, joint war-room, or formal change orders? Options: SLA ticketing system, Joint war-room with daily standups, Formal change orders and acceptance tests, Ad-hoc coordination

What would make you commit — practical next steps and clear asks

• What single thing would make you say 'Yes — schedule the parallel run within 30 days'?
• What internal approvals or committee reviews are required before you can schedule a parallel test (and their typical lead times)? Options: COO sign-off, Investment Ops sign-off, Compliance sign-off, Procurement/Legal, Board/Executive committee
• Which of these would you be willing to commit to in the next two weeks to accelerate readiness? Options: Provide sample portfolios, Grant test environment access, Schedule custodian calls, Share recent audit findings, Allocate ops lead for war-room
• What is your preferred communication cadence and forum during a discovery-to-parallel phase (e.g., weekly exec sync, daily ops standup, Slack channel)? Options: Weekly exec sync, Twice-weekly ops standup, Daily war-room during cutover, Email updates only, Dedicated Slack/MS Teams channel
• Please list the practical deliverables we should expect from you in the next 30 days (contacts, data extracts, approvals).
• Who should we loop in next to move these items forward? (Name, role, preferred contact method — if comfortable)

Getting Oriented — A Quick Map of Your Stack

• Which systems and tools do you currently use for each of the following: portfolio management, order management, accounting/NAV, compliance, market data, and reporting? (select all that apply) Options: Proprietary in‑house system(s), Excel / Spreadsheets / Macros, OMS (third‑party), PMS (third‑party), Accounting/NAV engine, Compliance engine / Pre‑trade checks, Custodian portals, Data warehouse / ETL tools, Risk / Analytics tool, Other (please name)
• How are those systems currently connected and how often do they exchange updates? Options: Real‑time APIs / streaming, Near‑real‑time (minute intervals), End‑of‑day batch, Daily ETL jobs, Manual CSV/Excel exports, Ad‑hoc point‑to‑point scripts, No formal integrations
• Which parts of the stack are still primarily maintained in spreadsheets or manual processes? Options: Position aggregation / master book, Corporate actions handling, Valuation adjustments for private assets, Trade blotter reconciliation, Cash & settlement sweeps, Client reporting / performance tables, None — fully automated
• Who are the primary internal owners for each system class (e.g., ops, trading, compliance, external vendor)? Please list role/title rather than person if possible.
• Roughly how many discrete data sources feed your NAV calculation (count systems, custodians, price vendors, spreadsheets)? Options: 1–3, 4–6, 7–10, 11–15, 16+

If One NAV Error Shipped Tomorrow — Who Would Pay the Price?

• If a NAV error triggered investor redemptions tomorrow, which teams or functions would be most exposed and why? Options: COO / Operations, Head of Investment Ops, Portfolio Managers, Client Relations / IR, Compliance / Legal, CFO / Finance, External auditor, Other
• How often have you experienced NAV or compliance incidents in the last 24 months? Options: Never, Once, 2–3 times, 4–6 times, More than 6
• What was the most recent incident’s downstream impact (select all that apply)? Options: Corrected NAV published, Client inquiries / complaints, Investor redemptions, Regulatory notification / fines, Delayed reporting, Extra headcount hours / overtime, No material impact documented
• When incidents have occurred, how long did it typically take to diagnose and remediate the core data issue? Options: Minutes to 1 hour, 1–4 hours, 4–24 hours, 1–3 days, More than 3 days
• How does the risk of an NAV or compliance error affect your team’s day‑to‑day behavior or decision‑making?
• If you had to quantify worst‑case commercial exposure from a single NAV error (lost AUM, reputational loss, fines), how would you describe it? Options: Insignificant / manageable, Moderate — needs remediation plan, Material — could trigger redemptions, Existential / firm‑level crisis, Unknown / not measured

Where Data Breaks First — Pinpointing the Fragile Links

• Which single data element, when stale or incorrect, has most often triggered reconciliations and NAV breaks (e.g., positions, prices, corporate actions, fees)? Options: Positions / quantities, Market prices / valuations, Corporate actions, Cash balances / FX rates, Trade lifecycle / statuses, Fees / allocations, Reference data (ISIN/CUSIP/LEI), Other
• Which asset classes create the largest reconciliation headaches for you? Options: Equities, Fixed income, Derivatives (options/futures), OTC derivatives / swaps, Alternatives / private equity, Private credit, Fund‑of‑funds / nested structures, Cash / FX
• Describe the typical reconciliation failure mode you see (pick the closest and then expand if needed). Options: Missing records (no feed), Mismatched quantities, Price/valuation gaps, Timing/settlement mismatches, Corporate action misprocessing, Duplication / double counting, Manual override errors
• How many daily exceptions (average) does your reconciliation process generate across the book? Options: 0–50, 51–200, 201–500, 501–2,000, 2,000+
• When exceptions are raised, what percent are resolved automatically vs requiring manual intervention? Options: >90% automated, 70–90% automated, 40–70% automated, <40% automated, Almost all manual
• Tell us about one recent, specific reconciliation story — what happened, how was it found, and how was it fixed?

Who Gets the Fire Alarm? Roles, Ownership, and Escalation

• When a material reconciliation exception or NAV discrepancy is detected, who has the authority to halt publication or trades, and who is immediately notified? Options: Ops Lead / COO, Head of Investment Ops, Portfolio Manager, Compliance Officer, CFO / Finance, External Auditor, No single owner / ad‑hoc
• What are your current SLAs for responding to critical exceptions during business hours and after hours? Options: <30 minutes, <2 hours, <8 hours, By next business day, No formal SLA
• Describe the escalation path and how many people are typically involved from detection to remediation.
• Do you have a documented runbook for NAV or compliance incidents (who does what), and how often is it updated? Options: Comprehensive and updated regularly, Exists but rarely updated, Informal / tribal knowledge, None
• What tools or alerts do teams rely on to surface critical exceptions (email, dashboard, pager, slack, ticketing)? Options: Email alerts, Monitoring dashboard, Slack/Teams channels, Pager / SMS, Ticketing system (Jira/ServiceNow), No automated alerts
• Where do you see ownership gaps today that allow errors to persist or reoccur?

Telltale Portfolios — The Small Number That Break the System

• Which types of portfolios have historically caused NAV breaks or reconciliation chaos in your books? Options: High‑turnover trading books, Illiquid private asset portfolios, Derivatives‑heavy strategies, Multi‑currency / FX hedged funds, Fund‑of‑funds / nested structures, Client custom reporting accounts, Model portfolios
• Do you have sample portfolios we can use for testing (anonymized) and how many would be representative? Options: Yes — 3–5, Yes — 6–20, Yes — 21+, No but can prepare, No / not permitted
• For those sample portfolios, which attributes are essential to reproduce the failure (select all that apply)? Options: Private asset valuations, Long/short derivative positions, Daily corporate actions volume, Custom fee/allocation rules, Cross‑fund transfers, Unsettled trades / breaks, External manager NAVs
• Have you tried parallel runs before on representative portfolios? What went well and what failed? Options: Yes — successful, Yes — mixed results, Yes — unsuccessful, No, never tried
• Are there legal, privacy, or custodian restrictions we should know about before requesting sample data? Options: Custodian restrictions, Client confidentiality, Internal policy, None, Other (please describe)
• Which portfolio from recent incidents would you nominate as a 'must‑test' for any migration and why?

Audit Echoes — Past Findings That Predict Future Risk

• What recurring audit findings have reappeared over multiple cycles? Options: Incomplete reconciliation evidence, Valuation governance gaps, Insufficient controls over manual processes, Custodian discrepancy handling, Lack of end‑to‑end traceability, Compliance rule configuration issues, Other
• Which audit finding do you consider highest priority to remediate before any migration? Options: Valuation controls, Reconciliation coverage, Access / segregation of duties, Data lineage / traceability, Compliance rule validation, Third‑party vendor management
• How many open audit/high‑risk remediation items currently exist and what is their average age? Options: 0, 1–3 (under 6 months), 4–10 (6–18 months), 11+ (some legacy)
• Have regulators or auditors ever required specific evidence (e.g., reconciliation logs, valuation models) that you struggled to produce? Options: Yes — frequently, Occasionally, Once, No
• How confident are you in your ability to reproduce historical NAVs after a data migration? (preserving track record is critical to some buyers) Options: Very confident, Somewhat confident, Unsure, Not confident
• Which controls or reports would you insist remain unchanged post‑migration to satisfy auditors or clients?

If You Could Wave a Wand — Outcomes That Actually Matter

• Imagine a day with zero manual reconciliations and real‑time, accurate positions — what behaviour at your firm would change first?
• Which measurable success signals would convince you the project was successful? (pick up to three) Options: Zero NAV breaks in 12 months, Real‑time positions for all asset classes, Compliance pre‑trade latency under X ms, Reduction in exception volume by %, Historical performance preserved exactly, Faster client reporting turnaround
• What timeline would you consider realistic for achieving those success signals after kickoff? Options: <3 months, 3–6 months, 6–12 months, 12+ months
• What level of temporary divergence vs your legacy system would you tolerate during a parallel run (e.g., small % differences vs zero tolerance)? Options: Zero tolerance — must match exactly, Tight tolerance (<0.1%), Moderate tolerance (0.1–1%), Larger tolerance acceptable during learning
• Which stakeholders need to be visibly reassured by success metrics (select all that apply)? Options: COO, Head of Investment Ops, Portfolio Managers, Compliance, CFO / Finance, Client Relations / Sales, External Auditor
• What would be a deal‑stopper even if the platform met most technical goals (e.g., custodian unsupported, historical performance altered)?

Hard Constraints — What Would Make You Walk Away?

• Which of the following constraints are non‑negotiable for your program? Options: No change to historical performance records, Custodian integrations must be native, No trading downtime during market hours, Compliance rules must be verifiable before cutover, Data residency / privacy constraints, Budget caps, Other
• What minimum level of custodian coverage is required before you would consider switching (percentage of AUC)? Options: >95%, 80–95%, 60–80%, <60%
• How many full‑time internal project resources can you commit during parallel run and cutover windows? Options: <2, 2–5, 6–10, 10+
• What migration risks do you consider unacceptable (select all that apply)? Options: Data corruption of historical records, Loss of audit trail, Unrecoverable trade statuses, Misstated client NAVs, Extended settlement failures, Operational overload during cutover
• Are there legal, compliance, or client notification obligations that restrict cutover timing (e.g., blackout periods)? Options: Yes — strict blackout windows, Some restrictions but flexible, No significant constraints, Unsure / need to check
• What procurement or governance approvals will be required to start a pilot or parallel run? Options: CIO approval, COO approval, Compliance sign‑off, Procurement/Legal contract, Board / Investment Committee, Other

A Practical First Test — What Would Prove the Hardest Part?

• What single, low‑risk pilot could we run in 30–60 days to prove the most challenging capability (e.g., private asset valuations, derivatives lifecycle, custodian reconciliation)?
• Which acceptance criteria would you require to sign off a pilot as successful? Options: Reconciliation parity with legacy, Valuation parity within tolerance, Compliance rule parity, No material client reporting differences, Performance within SLA thresholds
• Who must be part of the pilot working group from your side (roles, not names)? Options: Ops lead, Head of Investment Ops, Portfolio Manager, Compliance lead, CIO/IT rep, Custodian contact, External auditor/consultant
• What sample data, permissions, or technical access would you be willing to provide for the pilot, and how quickly could you provision it? Options: Anonymized sample portfolios (3–5) within 2 weeks, Representative feeds with test credentials in 2–4 weeks, Full client test dataset in >4 weeks, Unable to provide until contract signed
• What would make you immediately say 'no' to a proposed pilot? Options: Requires live production cutover, Exposes client confidential data, Needs heavy internal engineering effort up front, Doesn't include custodian test, Other
• If we run the pilot and meet acceptance criteria, what is the quickest realistic next step you would commit to? Options: Expanded parallel run, Build detailed scope & SOW, Executive briefing & approval, Procurement / contract negotiation, No commitment without further evidence

Quick introductions — who’s in the room?

• How often have you experienced NAV calculation errors or compliance breaches in the last 12 months? Options: Multiple times a month, Monthly, Quarterly, Once or twice, None
• Which title best describes your role for this project? Options: COO, Head of Investment Operations, Head of Investment Technology, CIO/Portfolio Manager, Head of Compliance, Other
• Which of your funds or business lines are most likely to be impacted if a NAV error occurs?
• Who is the ultimate decision owner for investing in a new portfolio platform (name/role)? Options: COO, CIO, Board/Executive Committee, Head of Ops, Head of Technology, Other
• How would you describe the current urgency for fixing reconciliation-driven NAV/compliance risk? Options: Immediate — must act in weeks, High — in next 1–3 months, Medium — this quarter, Low — within 6–12 months, Undecided

What’s keeping your NAV awake at night?

• If a single NAV error hit a flagship fund tomorrow, how would that play out for the business? Options: Minor internal scramble, Investor redemptions likely, Regulatory reporting breach possible, Significant reputational harm, Catastrophic/unknown
• What financial or client-impact examples can you share from a past NAV or compliance incident (losses, redemptions, fines, or client escalations)?
• Which outcome worries you more emotionally: losing client trust or getting hit with regulatory penalties? Please explain why. Options: Losing client trust, Regulatory penalties, Both equally, Other
• How would you rank the following impacts of a NAV/compliance failure for your firm? Options: Redeeming investors, Regulatory penalties, Operational overtime costs, Delayed settlements, Loss of distribution/clients, Reputational damage
• When you think about that worst-case scenario, what’s the single change that would calm you the most?

Where do the pieces actually fall apart?

• Which system, handoff, or process do you suspect causes most reconciliation gaps today? Options: Custodian feeds, Order Management System (OMS), Execution / Broker reports, Accounting system, Risk/Analytics tool, Manual spreadsheets, Market data/reference data, Other
• Which asset classes tend to trigger the most NAV or position breaks for you? Options: Equities, Fixed income, Derivatives (options/futures/swaps), Private assets (private credit, PE), Funds of funds, FX, Other
• Describe a recent incident where portfolio positions or valuations didn’t match across systems — what mismatch happened and which teams intervened?
• On average, how many manual reconciliation interventions occur for a typical trading day or reporting cycle? Options: None, 1–5, 6–20, 21–50, 50+
• Who formally owns the reconciliation process and who usually ends up fixing the problem (roles, not names)? Options: Middle Office, Operations, Accounting, Investment Technology, External vendor, Other
• Are there recurring data fields or reference-data mismatches (e.g., identifiers, corporate actions, security types) that always seem to be at the root?

How are you testing change today — and why it’s not enough

• Why do your current parallel runs or UAT feel like a checkbox rather than a defensible proof of readiness? Options: Insufficient sample portfolios, Too short duration, Metrics are vague, Lack of custodial participation, No clear rollback criteria, Other
• What does your current parallel-run look like in practice (sample size, duration, teams involved, and who signs off)?
• Which of the following metrics do you currently track during tests? Options: NAV parity, Position parity, Compliance check latency, Settlement matches, Performance attribution parity, Other
• How are sample portfolios chosen today — by stress, representative coverage, key clients, or convenience? Options: Stress cases (edge), Representative mix, Highest AUM clients, Problem accounts, Ad hoc/convenience, Other
• What has consistently prevented your tests from being conclusive (e.g., missing data, custodian access, time constraints)?

What would real confidence look like?

• If you were fully confident the platform would stop false compliance flags and broken NAVs, what measurable signals would prove that to you? Options: Zero NAV breaks across samples, Position parity within tolerance, Compliance latency < X ms/s, Full multi-asset coverage, No manual reconciliation for key processes, Other
• What numeric tolerances or thresholds would you accept for NAV parity and position differences? Options: Exact match required, <= $1 per trade, <= 0.01% NAV, <= 1bp variance, Other
• Who in your organization must be satisfied for you to call the migration a success (roles and their top concern)?
• How do you want to see validation delivered — dashboards, automated reports, daily sign-offs, or formal audit reports? Options: Real-time dashboards, Automated daily reports, Weekly executive summaries, Formal audit package, Other
• How much time and resource are you willing to commit to a parallel run to reach that confidence? Options: 1–2 weeks, 3–4 weeks, 1–3 months, 3+ months

What would giving control back to your team actually change?

• If portfolio managers had reliable real-time positions tomorrow, what would they start doing differently next week?
• Which operational metrics do you expect to improve if reconciliation work is eliminated (select all that apply)? Options: Trade turnaround time, Time to publish client reports, Headcount hours on reconciliations, Number of manual corrections, Client satisfaction, Other
• What worries you most about the human side of change — adoption, process rework, rule misconfiguration, or governance challenges? Options: Adoption resistance, Process rework, Rule misconfigurations, Governance issues, Other
• What training or enablement would your PMs and Ops teams need to feel comfortable on day one post-cutover? Options: Hands-on workshops, Role-based playbooks, Shadowing during parallel run, Recorded training + docs, Dedicated go-live support, Other
• Tell us a story about a time a small improvement in visibility changed a trading or reporting outcome — what happened and why did it matter?

The practical constraints no one talks about

• What single logistical constraint could derail migration even if the software works perfectly? Options: Custodian API limits, Poor legacy data quality, Key resource availability, Regulatory reporting windows, Contractual/legal delays, Other
• Which custodians and external counterparties must be part of the parallel run and do any require pre-approved connectivity?
• Do you have the required sample datasets ready today (historical trades, corporate actions, valuations, reference data)? Options: All ready, Most ready, Some available, None available
• What windows (month-end, quarter-close, customer reporting) are off-limits for cutover or heavy testing? Options: Month-end close, Quarter-end/valuation, Year-end/audit, Client reporting cycles, None
• What is your rollback risk tolerance — would you accept partial rollback, full rollback, or prefer staged fallback with manual workarounds? Options: Full rollback only, Partial rollback allowed, Staged fallback with manual fixes, No rollback preference yet
• Who will be the assigned owners on your side for parallel runs, data prep, and rollback decisions (roles/names)?

Decision, timeline, and the reality behind ‘soon’

• If you had to put your calendar and budget where your concerns are, what’s the earliest realistic date for full transition? Options: Within 1 month, 1–3 months, 3–6 months, 6–12 months, Over 12 months
• What budget band is available (or will be requested) for this initiative this fiscal year? Options: <$100k, $100k–$500k, $500k–$1M, >$1M, TBD
• What procurement, legal, or compliance approvals typically slow down projects of this type at your firm? Options: Procurement review, Legal terms/SLAs, Security review, Regulatory/compliance sign-off, Budget approval, Other
• What SLAs or contractual terms are non-negotiable for your team (e.g., uptime, support response, data retention)?
• Who outside your immediate team needs to be engaged before you can sign (e.g., custodian relationship manager, compliance officer, CFO)?

Let’s define the parallel test we’d actually trust

• What would make a parallel run feel like an audit-quality validation rather than a demo? Options: Representative sample coverage, Custodian-signed parity reports, Automated reconciliation logs, Independent verification, Clear rollback rules, Other
• How many and which types of sample portfolios would you require to feel confident (count and asset-mix guidance)? Options: 5–10 diversified, 10–25 representative, All flagship / complex portfolios, Edge cases only, TBD — need discussion
• For acceptance, which of these must be demonstrably met during parallel-run? Options: NAV parity within tolerance, Position parity across custodians, Compliance rules firing correctly, Settlement confirmation matching, Performance attribution parity
• What exact datasets (historical valuations, corporate actions, trade blotters, reference data) do we need from you to execute the parallel run?
• Who from your side must be present during cutover exercises and daily parallel checks (roles and decision authorities)?
• What would be your non-negotiable rollback condition — the single metric or event that triggers immediate rollback?

Next steps — what would make this feel like progress?

• What is the smallest pilot or experiment we could run in the next 2–4 weeks that would materially reduce your risk? Options: 5-portfolio parallel run, Custodian connectivity test, Data mapping validation, Compliance rule dry-run, Other
• What cadence and format of updates would keep your stakeholders comfortable (e.g., daily runbook, weekly exec summary, live dashboards)? Options: Daily operational updates, Weekly executive summaries, Real-time dashboards, Bi-weekly demos, Other
• Who should be invited to the kickoff meeting to make decisions quickly (roles/names)?
• Are there legal/NDA or security steps we should complete before requesting sample datasets or custodian access? Options: NDA required, Security questionnaire, Standard legal terms ok, Data sharing agreement, None
• If we asked for 3 prioritized items from you to unblock a pilot, what would those be and in what order?
• When would you like to schedule our next working session to align on sample portfolios and the parallel-run plan? Options: This week, Next week, In two weeks, Next month, Later

Tell Us the Day You Knew Something Was Wrong

• Can you briefly describe the NAV or compliance incident that prompted this evaluation?
• When was the issue first detected? Options: During audit, During month-end reporting, During client reporting, During intra-day trading, Other
• How severe was the immediate business impact? Options: Flagged with no investor impact, Minor reporting correction required, Material NAV error requiring restatement, Client redemption / reputational risk, Regulatory inquiry
• Who first surfaced the problem (role or team)? Options: PM/Portfolio team, Operations/Back Office, Compliance, Custodian, External Auditor, Client, Other
• What was the most surprising or unexpected thing you learned during initial triage?

What’s Keeping You Up at 3AM?

• If this issue escalated to a visible NAV error for a flagship fund, who would feel the consequences most acutely? Options: COO, Head of Investment Ops, CRO/Compliance, CIO/PMs, Investor Relations, Other
• How often do you encounter reconciliation mismatches that require manual investigation? Options: Daily, Weekly, Monthly, Quarterly, Rarely
• Estimate how many hours per week your team spends resolving reconciliation or position discrepancies. Options: <10 hours, 10–25 hours, 25–50 hours, 50–100 hours, >100 hours
• Which three processes suffer most when positions are delayed or incorrect? Options: NAV calculation, Compliance checks, Client reporting, Trade settlement, Performance attribution, Rebalancing/execution
• How does this problem make you feel about your ability to run the business (trust, stress, credibility)?

Where Your Data Really Lives — And Where It Frays

• Which disconnected system is most likely to corrupt a trade or position before it reaches NAV? Options: Order Management System, Execution Venue/OMS integration, Custodian feed, Pricing/Valuation tool, General Ledger/Accounting, Proprietary spreadsheets, Third‑party reconciliation tool, Other
• How many distinct systems currently contribute data to your NAV or compliance calculations? Options: 1–3, 4–7, 8–12, 13–20, 20+
• What types of data mismatches do you see most often? Options: Reference data (IDs/ISINs), Corporate actions, Pricing/valuation, Quantity/size differences, Stale/late feeds, Mapping errors between systems, Other
• Which asset classes create the most friction for data fidelity (pick all that apply)? Options: Equities, Fixed Income, Derivatives/Swaps, Alternatives/Private Equity, Private Credit, Funds of Funds/Legal wrappers, FX/Cash
• Tell us about a concrete example where a data mapping or reference mismatch caused downstream failure—what happened and how was it discovered?

Who’s Owning the Risk — and Who’s Not

• If a migration or cutover caused a NAV break, who inside your organization would be accountable for customer and regulator communications? Options: COO, Head of Investment Ops, CRO/Compliance, Head of Legal, Head of IR, Other
• Who has final authority to approve a go/no‑go cutover? Options: COO, Head of Ops, CIO, Board/Executive Committee, Cross‑functional signoff required, Other
• Which team(s) will own remediation if historical performance data is corrupted during migration? Options: Operations, Investment Operations/PMs, IT/Engineering, Vendor/Integration Partner, External Consultant, Other
• How would you describe your organization’s tolerance for NAV or compliance incidents? Options: Zero tolerance — immediate halt and rollback, Very low — significant remediation before go‑live, Moderate — acceptable for short windows, High — willing to accept minor anomalies during cutover
• Describe a past escalation where accountability was unclear—what slipped through the cracks?

What Would Perfect Actually Look Like for Your COO and Head of Investment Ops?

• If the COO said 'this is resolved' tomorrow, what single measurable outcome would prove it?
• Which of these success signals matter most to you? (select up to three) Options: Zero NAV breaks, Real‑time position parity, Compliance pre‑trade latency < X ms, Full multi‑asset coverage including private assets, End‑to‑end reconciliation within SLA, Accurate historical performance post‑migration
• What is an acceptable reconciliation delta or tolerance for you (e.g., dollar amount, bp, or percentage)? Options: Exact parity required, Tolerance by fund size (specify), Up to 0.01% / small bp, Up to 0.1% / moderate, Other
• What private or illiquid asset structures are must‑have for your proof of concept (e.g., private credit, fund-of-funds, side pockets)? Options: Private Equity, Private Credit, Alternative Funds of Funds, Real Assets/REITs, Complex legal wrappers, Other
• How would you prioritize speed vs absolute parity vs regulatory traceability during transition? Options: Parity first, then speed, Balance parity and speed equally, Speed first with tight rollbacks, Regulatory traceability is non‑negotiable

The Parallel Run: Your Most Revealing Test

• What is the single portfolio or scenario you believe will expose the most weaknesses in any new platform?
• Do you have representative sample portfolios ready for parallel testing? Options: Yes — full sample set, Partial — some complex portfolios only, No — need help preparing samples, Other
• What sample characteristics must be included (select all that apply)? Options: High turnover equity, Long‑dated bonds with coupons, Derivatives/Swaps and options, Private assets with NAV schedules, Multi‑currency exposure, Wrapped fund/legal structures
• What are your non‑negotiable pass/fail criteria for parallel run validation? Options: Reconciliation parity, Performance attribution within tolerance, Compliance rule fidelity, Settlement success rate, Latency thresholds met, Other
• Who will lead day‑to‑day coordination for the parallel run across your ops, IT, and custodian teams? Options: Head of Ops, Project Manager, IT Lead, External PMO, Custodian Liaison, Other

Acceptance: Where We Fail or Succeed

• What reconciliation parity threshold would make you comfortable switching off legacy systems entirely? Options: Exact parity for all portfolios, Parity for material portfolios only, Statistical parity within defined tolerance, Stepwise parity per asset class
• Which of the following acceptance tests must pass before full transition? Options: Reconciliation parity, Performance attribution matching, Compliance rule fidelity, Settlement verification, End‑to‑end audit trail
• What rollback conditions should automatically pause cutover (choose all that apply)? Options: Material NAV discrepancy, More than X failures in settlement, Compliance rule misses, Data migration corruption of historical records, Custodian connectivity loss
• How long can you tolerate a parallel‑run period before needing a decision to go/no‑go? Options: <1 week, 1–2 weeks, 3–4 weeks, 1–3 months, Flexible/depends on results
• Describe any hard regulatory or client contractual milestones that constrain your acceptance window.

Moving Forward — Commitments, Timing, and Barriers

• If we agreed commercial and legal terms today, what single outstanding barrier would still prevent you from moving forward?
• What internal approvals and stakeholders must sign off before vendor selection? Options: Finance/Budget, Executive Committee/Board, COO/Head of Ops, CIO/Investments, CRO/Compliance, Legal/Contracts
• What timeline would you target for a full production cutover from project initiation? Options: <3 months, 3–6 months, 6–9 months, 9–12 months, Depends on scope
• What are the top three commercial or contractual concerns you need addressed to feel comfortable (e.g., SLA, liability, data ownership)?
• What immediate next step would move this forward most effectively from your perspective? Options: Technical discovery workshop, Proof‑of‑concept with sample portfolios, Commercial term draft, Executive briefing, Other