One of the challenges with software and product development is making sure there is always something meaningful to share. Not every week brings a major feature launch or headline announcement. Sometimes progress is measured by solving underlying challenges, validating assumptions, and laying the groundwork for future releases.

Focus on Web3 and Token Infrastructure

As mentioned last week, part of our focus shifted from Nexus development toward several outstanding topics surrounding the NAI token and broader Web3 infrastructure.

Alongside this, the team continued work on the claim portal smart contracts to ensure a smooth and reliable release process for the remaining tokens while maintaining the highest possible level of security and predictability.

Completing the token release process also creates an opportunity to revisit the proxy contract structure and address questions raised by the community. As many of you understand, changes to smart contracts require extremely careful planning. Decisions made today have long-term implications and, unlike traditional software, cannot simply be rolled back if mistakes are made.

As a result, a considerable amount of research and analysis took place this week. Over the coming weeks we expect to provide a clearer update on both the token release timeline and the options surrounding the future of the proxy contract.

Improving Nexus Through Real-World Usage

On the product side, a large portion of our effort was spent improving Nexus based on feedback gathered from active Proof of Concepts.

One recurring theme is understanding why Nexus provides certain answers in specific situations. Interestingly, in many cases we find that Nexus is actually providing the correct answer, but validating that answer requires a deep understanding of the customer's data landscape and business context.

Since the underlying data belongs to the customer rather than ourselves, this investigation process can be time-consuming. However, these exercises provide valuable insights that help us continuously improve both the platform and the user experience.

Alongside these investigations, several smaller improvements were made throughout the platform.

Within Group Chat we addressed issues related to agent aliases and improved the visibility of online and offline participants. We also implemented a number of backend improvements related to data handling and source selection, helping Nexus make better use of available information when generating responses.

While these updates may seem minor on the surface, they contribute directly to the overall reliability and usability of the platform.

Dashboard and Connector Improvements

The frontend team continued enhancing the dashboard experience and widget configuration framework.

Based on feedback from demonstrations and pilot users, additional flexibility has been added to dashboard configuration, making it easier for users to tailor dashboards to their specific needs.

We also introduced improvements to the connector experience. Users can now see underlying data sources directly within the virtual data lake representation inside Nexus.

This provides greater transparency around connected systems and available data sources. As we continue positioning Nexus around Operational Intelligence, these capabilities become increasingly important.

Understanding the Competitive Landscape

As part of the final evaluation process for one of our ongoing Proof of Concepts, we have been spending time analyzing Microsoft Copilot Enterprise in greater detail.

As mentioned previously, we are directly competing against Copilot in certain scenarios. Understanding where Copilot excels, where its limitations exist, and where Nexus provides differentiated value allows us to better demonstrate our strengths during customer evaluations.

This process is both challenging and valuable. Enterprise AI platforms continue to evolve rapidly, and understanding competitive solutions helps us sharpen our positioning and improve our demonstrations.

Our findings so far continue to reinforce what we have observed before: while document-centric AI assistants perform strongly within their intended domain, there remains significant opportunity around connecting operational systems, combining structured and unstructured information, and enabling operational intelligence across fragmented environments.

Business Development Continues to Build Momentum

Business development activities continued across healthcare, sports, and real estate.

The process remains what enterprise business development often is: a combination of persistence, relationship building, and a significant number of outreach efforts before opportunities begin to materialize.

The encouraging part is that we are seeing gradual but consistent progress. Partnership discussions continue to develop, new organizations are showing interest, and our sales calendar is becoming increasingly active. While these conversations take time to mature, the growing level of engagement provides confidence that our positioning and use cases are resonating with the market.