Over the past weeks, we’ve been thinking about how to share progress in a way that’s actually useful. Daily updates don’t add much, especially in a market that moves in waves. At the same time, a lot is happening behind the scenes. A weekly update gives us the space to show what’s being built, why it’s being built, and how it’s being used in practice.

The Product

Last week was a strong one for Nexus, because several pieces came together in a way that reflects how the product is evolving: driven by real usage instead of isolated roadmap ideas.

One of the bigger additions is the introduction of dashboards. Users can now create multiple views, each composed of configurable widgets. These widgets can represent different charts or statistics, all built on top of live queries. The important part is the workflow it unlocks, users can now persist insights and monitor them continuously. This feature came directly from a client need, and it immediately resonated with others who saw the same pattern in their own workflows. It also marks the start of a broader layer within Nexus where outputs are structured and reusable assets.

We also rolled out export to document functionality, supporting both PDF and DOCX. This started from a simple requirement: clients generating reports from their data needed a clean way to share results outside the platform. What began as a targeted solution quickly proved to be broadly useful. It’s one of those features that doesn’t change how Nexus works at its core, but makes it significantly more practical in day-to-day use, especially in environments where decisions still rely on documents.

Under the surface, work went into improving agent orchestration. As more workflows rely on multiple agents interacting in the same environment, clarity becomes critical. Agents now operate with better context awareness, reducing confusion when multiple roles are involved. On top of that, orchestration capabilities have been expanded so certain agents can take on a more coordinating role, managing others as part of a task in order to make multi-agent setups more predictable and reducing the need for manual correction during longer workflows.

Group chat, which is increasingly central to how teams use Nexus, has benefited directly from these improvements. With better instruction handling and clearer agent roles, conversations become more structured without losing flexibility. It improves how usable the system feels when multiple people and agents are working together in the same thread.

Alongside these releases, a significant part of our time is still spent building directly for client use cases. That includes a range of RAG implementations across different types of unstructured data, as well as complex, custom data pipelines tailored to specific environments. Each one forces us to deal with real-world constraints such as inconsistent data, fragmented systems, and performance trade-offs. The outcome is that many of the features now being rolled out have already been tested in production-like conditions, with learnings and parts of the underlying implementations being reused to form the foundation of a more generic RAG pipeline within Nexus.

This also explains why some parts of Nexus are still being finalized. The current priority is getting clients live, particularly on the Web2 side. That means certain features are developed just far enough to support real usage, and then iterated on as new requirements come in. It’s a different approach from building purely against a roadmap, but it ensures that what gets shipped actually holds up in practice.

The Business

On the business side, focus remains tight on a few regions. In Qatar, an ongoing pilot is starting to create internal reference points within organizations. That makes follow-up conversations more concrete, because teams can relate to existing use cases instead of abstract demos. In India, we’re working through a set of smaller proof-of-concepts with companies that came through our network. The dynamic is similar. Once there’s a recognizable pattern, it becomes easier to move forward into deeper engagements.

At the same time, we’ve started mapping out the landscape of comparable solutions. The goal here is straightforward. Understand what others are offering, where Nexus differentiates, and which customers they are serving. This is still in the analysis phase, but it will transition into more direct outreach in the coming weeks, targeting companies that are already exploring similar approaches.

Not everything is moving as fast as planned. One example is deployment through Google Marketplace. Getting Nexus to run as a one-click deployment is proving more complex than expected. The deployment to GCP is ongoing, and while it adds some short-term friction, it’s necessary to support more flexible and scalable deployments going forward.

Overall, the current phase is more about tightening the product through usage. The combination of custom pipelines, dashboards, document export, and improved orchestration shows how Nexus is becoming more complete as a system for real world usage.