Product-Market Fit, UX, Data, Systems

Does the co-pilot focus on a specific industry (eg. FSI, healthcare), function (eg. HR, F&A), persona (eg. developer, contact center associate) or a system (eg. System of Engagement)?

If the above isn’t true, do the multiple focus areas have some form of synergies in the form of systems interfaced or data types supported.

Does the underlying process have redundant & unnecessary steps that may not be needed once the process is transformed? If yes, is the co-pilot re-engineering to address the redundancies?

When applicable, does the co-pilot have the capability to cross-functionally operate across multiple functions, or layers of offices to finish the end to end use case?

If it does cover an end to end process, is it architected to serve individual tasks for individual micro-processes, while creating strong connections across each stage in the lifecycle?

Does the co-pilot cover various channels of engegement that the use case demands? If yes, is product development efforts prioritized efficiently based on the volume of engagement by channel?

Is the co-pilot able to solve for a repeatable business process conducted by several FTEs, at a high cadence in a linear way consistently across multiple FTEs, multiple times a day with little variance?

Are they solving for a wide variety of business processes, done by one of multiple FTEs, thus leading to a higher sum total of overall transaction volume?

Does the co-pilot address or provides mechanisms to address any financial risks associated with incorrectly inferring inputs or generating inaccurate outputs?

Does the co-pilot achieve an error rate low enough to be not substantial enough to avoid any financial losses? Is the variance in the output relatively consistent?

Does the co-pilot have adequate controls & experience design to address for regulatory risks, if there are any?

Does the co-pilot effectively break down the information it needs into various steps? Does it properly utilize those steps in cross-referencing information with source systems, automatically pulling up information that can be referenced to still optimize for user input?

Are the steps designed to be in-sync with the current workflow, while optimizing for the process re-engineering efforts?

Is the intended agent workflow consistent across several team members, but at the same time accounts for the differences in the nature of micro-processes that they do?

Is the workflow collaborative enough to split the work item transaction volume across multiple team members? If how does it enable auto-assignment, check-in / check-out, triaging and supervisor review?

Has the co-pilot been built to be stateful? Does it have the capability to augment information from key source systems? Does it remember past transactions and can a user import inputs & outputs from such past transactions?

Is the co-pilot suggestive? Does it provide users with suggestions via augmentation of information from existing knowledge bases and memory and does that help in creating added layers of controls?

Is the co-pilot workflow editable to accomodate for business changes? If yes, is this change less resource intensive and time consuming?

If the use case requires unstructured data extraction, is the co-pilot capable enough to extract data such as free-form text, complex tables, highly variable key value pairs from varied input sources such as emails, scanned documents, chats, calls?

For use cases with low quality or missing data, can the co-pilot identify gaps in data quality, extrapolate them, find references in source systems or triage them to source users for achieving completeness?

Does it have integrations with the major systems specific to that vertical or function such as CRMs, ERPs, HR / Payroll?

Does it integrate with the major types of systems such as record, action, engagement, reference and insight to create a stateful, multi-modal and connected experience?

Can it interface with both modern and legacy applications? Does it have OOTB connections & tools to quickly integrate custom APIs?

For non-API based systems, is there any screen scraping? If yes, how sensitive is the screen scraping to changes in the underlying system?

Does the co-pilot integrate with systems of insights & store historical transactional information to generate unique insights over the course of the usage?

Does the co-pilot have the capability to integrate across a vastly fragmented set of tools based on its use case and target market segment?