J1 Describe the proprietary client portal — technology stack, hosting environment, and the internal team that maintains it.
J2 What does “real time” mean in the portal today — streaming, intraday refresh, or prior day close?
J3 Which specific data must the portal consume from the performance vendor — positions, transactions, calculated returns, benchmark returns, allocation, rendered PDF reports?
J4 At what granularity must data be available to the portal — position, sleeve, account, household?
J5 What integration methods are acceptable — REST API, streaming or event-based feeds, scheduled file delivery, database replication, direct data warehouse access?
J6 What is the required latency for each data type, expressed in measurable terms?
J7 Must performance be calculated on demand in response to a portal request, or can it be pre-calculated and served?
J8 What is the expected API call volume, peak concurrency, and acceptable response time?
J9 Must clients be able to retrieve historical PDF report packages through the portal?
J10 Will the firm pull data from the vendor, or must the vendor push to the firm?
J11 Is there an internal data warehouse or data lake the vendor must feed?
J12 What authentication model is required between the portal and the vendor?
J13 Is any vendor-rendered content to appear in the portal, or is the integration data only?
J14 Which other internal systems consume performance data today?
J15 Is there a proprietary advisor workstation as well as the client portal?
J16 Which CRM, planning, proposal and billing systems are in use, and which exchange data with reporting?
J17 Does the billing system supply fee data to reporting, consume performance data, or both?
J18 Where does model, strategy and money manager metadata originate?
J19 What integration monitoring, error handling and reconciliation exists between systems today?
J20 What internal technology resources are available to build and maintain the integration?