Name: Final Video Nasdaq X Dasseti
Uploaded: 2026-06-19T09:36:36.494Z
Duration: 28 min 46 s
Description: Final Video Nasdaq X Dasseti

Transcript for "Final Video Nasdaq X Dasseti": Hello, and welcome, everyone. Thank you for joining. I'm Michael, lead product manager with Nasdaq Investment. And I'm Hass, head of solution specialist at Deseti. Today, we're focused on sharing with you a practical API integration between the DICETI Engage and Nasdaq Investment Omni. It supports how teams are already working today, managing core content through RFPs and DDQs to also include updates and institutional databases. Very excited to be sharing details about this integration with you. It's designed to improve control and speed in these workflows at the same time. Thinking about control with this integration, teams can scale the use of approved content with traceability and validation built into the workflow. And on speed, being able to leverage the API integration, first of its kind, that reduces the manual work to move data between systems. The data handoff is now automated. So in today's session, you're gonna hear from both teams, see both sides of the workflow, and leave with a clear view of how this can help you in your workflows. This is a practical working session. We're gonna get an understanding of the current state, what's new with this integration, and what to do next. So let's get grounded here. I'm gonna hand it over to Hass to walk through where things are today and how we move into the integration. Yeah. Absolutely. Thanks, Michael. So, really, what we do here at Assette is we partner with asset managers globally to help them streamline how they rate, govern, distribute their information across that due diligence life cycle. And at the center of that is our Engage solution, which is the DDQ RFP AI empowered management platform. And what it does is really provide a central source of truth for proof content, helping teams manage RFPs, EDQs, and if you any request that they receive with great consistency, governance, and efficiency. And really what we're really excited to show you today, as Michael mentioned, is how our integration with Nasdaq investment nominee extends that capability even further, creating a truly connected workflow from content creation through to database publication. So speaking about the current state today, when we speak with asset managers, regardless of the size or the team structure or the operating model that they employ, we consistently consistently hear the same challenge. Investor narratives live in too many places. Teams are often managing that content across different avenues, whether that be in spreadsheets, cross shared drive, even email threads, or other systems that they're using. In some firms, there are single teams that own that entire process. Sometimes in large organizations, those responsibilities spread across product teams, consultant relations, database management, even sales enablement teams. So really regardless of the structure, of the organization, the challenge is to maintain that consistency across these interconnected workflows, and that's what really remains difficult. If you consider one, you know, simple scenario, portfolio manager up managing one of the strategies and asset manager updates the investment process. That requires an investment process description update, a narrative update. That change needs to be reflected across multiple avenues. Any RFP response going forward, any ongoing DDQ, any questions that are being asked directly by investors and consultants, also database submissions, even marketing material and same sales enablement content. And what happens too often is that these things are happening independently. And what that results in is duplicate effort, big challenges with respect to volume control, and a huge risk of inconsistent messaging reaching ultimately the investors and the consultants. And and this is where the engaged solution already helps across the scope of RFPs, DDQs, your direct interactions, with the, with your investors and consultants. So really where we, you know, where we're looking to manually build those bridges, across those systems, the integration that we're looking to demonstrate today looks to close the gap by extending that content continuity into the Omni process. So let me hand back over to Michael, if you wanna talk about where you see those connected Omni workflows, removing the the manual effort, particularly between RFP, EDQ, database updates, and the and the opportunity there. Absolutely. Everything you said, Hass, resonates, and those pain points are things that we hear from Omni clients as well. It's a pattern that plays out consistently. As you said, larger and smaller firms alike, no matter the team structure, they're everyone's trying to accomplish the same thing and struggling with it, which is keeping that content consistent and updated in a timely way across RFPs, DDQs, as well as the database destinations that they need to reach. So a way that pain point manifests practically is that as updates, especially time sensitive updates, need to be made or something that needs to go out the door quickly or a a a top down mandated change within the firm that needs to go out quickly. They may happen in one place, but not all the places. And over time, those, unreconciled sort of changes accrue, and then you've you're left with a large project to undertake. And so the one of the opportunities here is really to eliminate the need for larger projects to reconcile or or bring things up to speed and have things kept in sync in more real time across all of the the destinations. Consistency is so important and the traceability as well. So let's visualize just with an overview of how this integration works, at a bird's eye view and then we're gonna share the systems themselves for a live demo. What you're seeing on screen is a simple depiction of the integration. Right? On the left side of the screen, we're looking at where and how asset managers are managing their data using the SETI. Right? So the wonderful thing about this integration is that as asset managers are using the SETI to update their content, they can do so with the benefit of Nasdaq investment and OmniData. Right? In the middle, we have Omni playing the role of applying validations to the data and automated distribution through to the data pay database and destinations. And then lastly, on the right are those destinations, the research and consultant databases, NASDAQ investment, and all other ones that asset managers have identified are crucial to be seen, and keep up to date profiles within. So to clarify the lines here, what exists today and continues to exist as it has before is how Omni is pushing changes, from Omni into the databases. And similarly, Dessetti continues to have its existing workflow and AI power tools to keep RFPs and DDQs, updated as they come in. So the new piece to highlight through this integration is this two way flow whereby OmniData, questions and answers both are loaded from Omni into the SETI and an API sync from the SETI into Omni so that all client initiated changes immediately and automatically flow into Omni. So with that bird's eye view in hand, let's make this more tangible. I'm gonna hand it back to Hass to walk through what this looks like inside the Desedi application. Yeah. Absolutely. Thanks, Michael. I I think this is something that we're really excited about about sharing. We're now inside Vocetti Engage. We're looking at an example of what a centralized question and answer repository could look like. But the but the real key about this is now integrated into this process are your database questions. So the narrative questions that you're being asked on investment, on Callum, on WillShare, on all of the databases across your your your database matrix that you're fulfilling for your firm level and product level data are now fully integrated into a solution that allows you to edit, revise, approve, manage using one integrated process. And and the beauty of that is that everything lives in the in the platform. So I'll go over to our OmniSync page here where you can start to to get a feel for for this. And with that in mind, what you can see here is is is what you would see as a as a as a client here. All of the databases that you are fulfilling as part of your as part of your Omni, campaign automatically and fully embedded into the Desetti q and a library. This is a very powerful tool because as Michael mentioned, that relationship of data management and transition works in both directions. So now we don't just have the data flowing in to the SETI for use in any RFP or DDQ process that you are undertaking. This process can also be used to manage any regular or ad hoc updates that you have for those databases for this type of data. So it can be leveraged across the full scope of all of your, communication exercises when it comes to the qualitative, you know, to data. So rather than maintaining separate content libraries for each channel, teams can work from a single source of truth, and it's a true single source of truth. So let's take a a sync a simple example here. So I can select, for example, one of the databases that I that I wish to manage. I can see, as as Michael Michael previously mentioned with that workflow diagram, the data of the questions and the answers have already flown through into into my library. So I can see what's already populated, what those existing answers are. I can assign any relationship that says, okay. I I want to manage a component of my data on a quarterly, an annual basis to ensure that I never miss an update, that all of my data is being presented accurately and consistently see consistently in line, with the guidelines that maybe we have internally to keep our data up to date, and so nothing gets left behind. With respect to updating the data, you're you then have a huge array of tools available to you. One being the use of AI. And the AI enabled workflows in Certi have become a very powerful tool for teams who are leveraging for the purposes of fulfillment of BDQs and RFPs that can now extend to their use in updating data or databases. I can actually wholesale take everything I have here, so this entire database, I could I could do it by product type, for example, if it's a a particular product channel that teams maintain. Depending on the nature of the responsibility the segmentation of responsibility, I should say, of the, the teams that are managing this data, we can call out and slice and dice that. With our AI enabled autofill capabilities, I can autofill any and all of these questions. I have the capacity of of leveraging my existing library. So I can actually load my entire q and a bank, and look for semantically relevant answers that I have either provided in previous RFPs or that exist in my central bank. Those answers can be leveraged for the purpose of matching questions that exist in this column database update that I'm doing. And I also have an extended capability as well. It's not just previous questions I've already answered that are structured. I can actually leverage our generative capabilities as well using what is called the SETI SmartDocs. And this is an exceptionally powerful tool because what this allows teams to do is upload unstructured content. And that unstructured content is, is read by the AI engine, and it's only that approved material that typically sits here. So approved client facing marketing material, prospectuses, policy documents, content that has information that could potentially address questions that you're being asked, but obviously don't form a q and a structure in and of themselves. I can drop any and all approved documentation of source material and have the engine run on a generative basis where the AI can analyze the content and generate and contextualize the answers directly addressing the questions that the database is asking them. Let's take a second a simple example. Let's look at the firm history. So as mentioned, we can see the existing answer. We can see that this is the question as asked by this database. We can see what the existing answer is to that question that is already published on that database or if there is not an answer, this will be empty. I have the capacity to edit and add any answer. I can come in as a user and and make an update to this answer myself. But as mentioned, I can also use the AI enabled capabilities and search across my library and database and see whether I have answered similar content before. And this is where bringing the single source of truth together and an integrated workflow is really proved a benefit because I can see there's actually many instances where I have already addressed similar questions. It may have been to, a DDQ that I received from an endowment client or an RFP that I fulfilled for Sovereign Wealth Fund. It can even be, if I scroll further down, a a data point that already exists in my question bank library, that I've already fulfilled before. All of these now are suggested outcomes that I can leverage either in a verbatim fashion or in a generative AI fashion to use to update and maintain, my answer that will be distributed to Calum. And this process can also go the other way. We're we're talking about it today as I'm updating my record in Calum. But this record for this database entry could also be used for the next time I have an RFP or a DDQ. And so it's a it's a two way workflow that benefits both teams who are fulfilling RFPs, DDQs, direct interactions with, their end clients, as well as those who are responsible for the distribution channels of of databases. So a huge benefit there. Once I've made all of my updates, I I have the integrated approval workflow. So this doesn't operate in a silo either. I can mark, I can be assigned. So I am assigned to this question here. So relevant assignments can be made to the teams responsible managing this data. And once updated, I can mark that as ready for review. And I can also then go ahead and push that through to approval once it's approved. There's an entire audit trial underpinning this this process, so any update can be seen and tracked. And there's a full audit trail of data sourcing. So if you have leveraged any AI enabled workflows, they will be tracked, referenced, and sourced. So the answer origination is always is always drawn there. But let's, let's move forward. Once I've made my updates, the next step is to sync it back to Omni, and that couldn't be simpler. Michael mentioned the existence of the API push. So no more is there the fulfillment of a template, an export, an import process, having to copy and paste back into the format that the database requires, or the process determines. All of that is preconfigured into the systems, and the simple fact of the matter is that we just select the k. I've made my updates for this database. I now want to sync my questions back to Omni. I'll select, you know, this is the period that I'm updating it for for any relevant questions that do have time stamps associated to it, and then I'll hit my confirmation and sync. And now we get to see what it looks like on the other side. So I'll give it back over to Michael. Thanks, Hass. This is the continuity anchor in the value proposition. As Hass said, no need to copy and paste, no export or manual work needed. How does the workflow continue in Omni then? The API has been triggered on the Desedi side with the sync function, And now the mutual client can log in to Omni and navigate to narratives. For clients that are already using narratives, there isn't really any retraining needed. This is a fast on ramp to a value add. I simply navigate to narratives as I would today, and I can observe all of the data that has just automatically been loaded into my environment here. So our data entry screen, as it exists today, will reflect any and all changes pushed via the API. Omni retains its role now as an opportunity to do a final preview of the data in the layout as we'll look on the databases. And then when ready, if everything looks good with the final sense check, simply hitting submit as clients do today, submit will then move all of the data, to the publish step to the databases. So again, no changes to the workflow within Omni for those clients already using narratives, and submit is the is simply all that needs to be hit to move to the final stage. Now I do wanna highlight, as Hass was mentioning within the SETI, there's version history, be able to look at what changed and how that same traceability exists within Omni's existing change tracking feature. And I'm gonna show an image here now from the change tracking feature within Omni system that shows exactly that. And you can see that the Desedi Omni API is actually identifiable here as effectively a user logged in the change tracking history. So we can see when the API moved which data or which database in which product or entity from Deseti to Omni. The change tracking feature works as it does today within Omni, so you can see a before and after of the answer, and that's all exportable to Excel for record keeping, or any other purposes. So, again, this gives us not only the speed to eliminate the manual workflows to move data across system that's not fully automated via the API. But additionally, we're also getting that confidence, that control through stronger governance, the traceability, the ability to see what changed exactly when, by whom, and to be able to export that as needed. So when Omni pushes the data through to the databases, Omni will again run its validation layer. We have moved the validation information into the SETI, so we're running the validations on both sides of the integration. So we do expect that all of those as needed with any any issues, any any data that might need remediation before it's ready to be submitted to databases, we do expect that that will be flagged in the, API itself. And so this, Hass, could you share what that looks like? So let's say there's something that, data moving from the SETI into Omni. I wanna verify whether it worked, whether there are any exceptions that I need to manage. How is the system helping me know what I need to do and when? Yeah. Absolutely. Thanks, Michael. So we're returning to the SETI now, so love to show how that transparency is maintained throughout the process. So as Michael said, Omni still runs all of the validations and and the data checks on on the portal side, but we've migrated a lot of that validation over to the the engaged side as well. So you have the capability of really viewing a complete view. So from a complete history of synchronization activity, for example. So the entire an entire page here dedicated to providing that information. You can see what was synced, when it occurred, and the status of each sync event. Yeah. If there are any validation components that need rectifying or if any exceptions have been identified, it's immediately surfaced to the user. So rather than having to retrospectively discover problems after the publication of of data, teams will will receive immediate notification and visibility into any updates that are required, any data points that need, maintenance, and users remain in full control throughout the process. Very simple example of that would be here, where you can see that, you know, there were some components that succeeded and one aspect that was a managed question that wasn't provided. So as part of an update, there was a data point that is a mandatory component of a, of a database update that where the data hasn't yet been provided. And that's immediately flagged to the team so that they can provide that issue, rectify that issue, and provide that data point, update the underlying content, and reinstate the sync immediately and push that directly back on me. In terms of types of validations, as you can imagine, for those of you who are maintaining updating databases, there are a number of rules, in place. Counter limits, time stamps in terms of as of dates of different data points, dependent questions, you know, parent child dependencies of questions. All of that logic structure is integrated into the OmniSync, where then any indication will immediately be notified to you, of what's changed, how it's changed, and what actions are are required to, successfully process the data. And, of course, we have our, client success teams and support teams on both sides of the coin that will always be available to help our clients and optimize these workflows over time. But, Michael, maybe we'll, we'll we'll conclude that point there and and maybe think about some of the, sort of the future state that we're that we're thinking about. Yes. So we've just seen a demo of the systems interacting with each other. We've seen, the data from Omni being viewable and managed within the SETI to sync to Omni by API. The existing workflow being leveraged to publish via Omni as well as the change tracking and validation layers on both sides of the workflow. Very exciting that and we're very excited to offer this to all of our mutual clients. I'm curious, Hass, if you could just reflect on this a little bit from your perspective and client conversations you've had. Where are you seeing, the most interest or demand for these connected workflows? Yeah. Great question. So we're seeing demand from firms that's actually all shapes and sizes. Really, the common theme is rather than a particular, you know, size or type of manager, it's for those firms who are looking to really create great continuity across across those workflows and synchronization. So irrespective of whether you you may be a boutique single strategy house or or a large multi asset asset manager, many organizations have been investing significantly in content management, whether that be with with the SETI, with, Nasdaq Investment Omni, across the content management space and the juditions process. But they're still relying on manual handover between the different systems that they're using for the different for the different channels. And so where we're seeing really that strongest demand is where teams really wanna extend the value of their approved content beyond the individualized use cases that they are using them for themselves. So whether it's RFPs, DDQs, consultant requests, database updates, what we're really seeing from a demand perspective is the clients want a consistent narrative supported by clear governance and traceability. And that is clearly what this integrate integration helps them achieve. But while allowing teams to continue working with familiar processes, they're now working with an integrated ecosystem with a single source of truth and a, and a governed process. But maybe, a question for me, Michael. How how should clients be thinking about Omni's forward direction here? Absolutely. So from a product perspective, we're always thinking about the future and we're extremely excited about the integration as it stands today and is available in live now. We're also excited about upcoming enhancements as this integration will only grow and evolve. So thematically, there are two things that we're tracking in our road map. And this is a collaborative road map between For sure. Omni and Dacety. So the two themes that we're tracking include, first of all, deepening the automation and the scope of the API, including to extend, more real time syncing from Omni into the SETI beyond the initial load of the existing questions. That full breadth of the existing, client, database q and a is is there, upon get go, but I think we see great opportunity to have a continuous sync from Omni into Duseti to maximize the context that's available for managing the content to Duseti. And the second theme that we're tracking in the the the road map is around simply continuously evolving the scope of the data. So all of the functionality as shown here, right, but simply adding more questions beyond the narrative questions that we have in place today. So both of those are really exciting growth, avenues for us to to build on here. So let's let's recap. I think we've got three takeaways we wanna make sure everybody walks away with. First of all, this is highly practical. This is available now, ready for mutual clients, and it's thoughtfully tailored to support existing workflows. Right? And so we've got this twofold value that we've highlighted and just wanna reiterate again, this leads to stronger data governance and faster execution. So data stays consistent across all of the channels that it needs to be distributed through, with less manual work. Right? And so we've got the governance with approved content being reusable and traceable. The validations and the auditability is built into the systems. And the execution means that you can get that time back for higher value add activity rather than having to worry about manually ferrying data via copying and pasting. So execution quality and continuity, less complexity. I think what we wanna emphasize for everybody as we wrap up is, if you're interested and you see opportunity here for this to help you in your operating model, simply reach out to your SETI and your Omni teams, just to start a conversation about this. And so we're really excited about working with you to make this integration available to you as well. Let me say thank you, Hass, for joining me in this discussion, this overview, And Awesome. Thank you everybody for for joining the discussion.