RETREVE

Retreve began with an ambitious idea: make enterprise intelligence as natural as asking a question. While organisations had invested heavily in data platforms and reporting tools, accessing meaningful insights often remained dependent on technical expertise. The opportunity wasn't to build another dashboard. It was to rethink how people interacted with enterprise knowledge.

The engagement started with a founder's vision rather than a fully defined product. Engineering commenced in parallel, but many of the decisions that would ultimately shape the platform had yet to be made. Before software could be built with confidence, the product itself needed direction, its purpose, positioning, interaction model and commercial narrative all required definition.

Extant's role was to transform that early vision into a product that people could understand long before the platform reached technical maturity. Through product discovery, market research, strategic positioning, brand development, experience design and successive Product Experience Models, the idea evolved into something customers could experience, investors could evaluate and engineering teams could confidently build towards.

The result was more than a product design engagement. It demonstrated that commercial validation and technical development do not need to happen sequentially. By allowing both to evolve together, Retreve entered development with greater clarity, stronger alignment and a much clearer understanding of the product it was becoming.

The temptation with every new product is to begin designing solutions.

We deliberately did the opposite.

Before defining features, interfaces or workflows, we spent time understanding the people who would ultimately depend on the platform. What questions were they trying to answer? Why did existing business intelligence tools continue to frustrate experienced users? Where did confidence disappear between asking a question and receiving an answer?

One insight surfaced repeatedly.

The problem wasn't access to data. Most organisations already had more data than they knew what to do with. The challenge was transforming that data into something people could confidently use without depending on technical specialists.

That changed the conversation.

Instead of designing another analytics platform, the product evolved around a different objective: reducing the distance between a business question and a trusted answer. Every decision that followed, from information architecture and interaction design to AI conversations and workflow prioritisation, was measured against that principle.

By understanding the problem before defining the product, engineering gained clearer direction, stakeholders aligned around a common vision and the product developed around genuine user needs rather than technical assumptions.

Traditional business intelligence platforms were designed around navigation.

Users were expected to know where information lived, which report to open and how to interpret the results. Finding an answer often meant navigating through layers of dashboards, filters and visualisations before arriving at a useful insight. For experienced analysts this became routine. For everyone else, it became a barrier.

Retreve challenged that assumption.

Instead of asking users to learn the system, the system was designed to understand the user.

Conversation became the primary interface because it reflected how people naturally think. Business leaders don't wake up wanting to explore dashboards, they ask questions. *How did sales perform this quarter? Why has customer churn increased? Which region is underperforming?* Those questions became the foundation of the product experience.

Designing those conversations required far more than placing a chat interface on top of enterprise data. Every interaction needed to establish context, understand intent and guide users towards meaningful answers without overwhelming them with unnecessary information. The experience had to feel intelligent without becoming unpredictable, and powerful without becoming complicated.

This led to a significant shift in how the product was designed. Navigation became secondary to intent. Workflows were organised around conversations instead of screens, allowing users to move naturally from one business question to the next. Rather than forcing people to adapt to the product, the product adapted to the way people already worked.

By the time the interaction model was complete, Retreve no longer felt like another analytics platform.

It felt like a conversation with the organisation's knowledge.

One of the biggest challenges in early-stage product development is that engineering and commercial momentum rarely move at the same pace.

Software takes time to build.

Markets don't wait.

Investors need something to evaluate, early customers need something to experience and product teams need meaningful feedback long before the platform reaches production. Waiting for engineering to answer every question often delays learning until it becomes expensive to change direction.

Retreve followed a different path.

While development progressed in parallel, the product itself continued to evolve through successive Product Experience Models. These weren't prototypes created to imitate software. They were strategic representations of the product, designed to communicate how it would behave, how people would interact with it and why it mattered.

Each version became a catalyst for conversation.

Customer demonstrations revealed where expectations differed from assumptions. Investor presentations tested whether the product proposition was commercially compelling. Internal workshops aligned engineering, product and business teams around a shared understanding of what was being built. Every discussion generated insights that shaped the next iteration before those decisions became embedded in code.

The Product Experience Models also transformed the way the product was presented.

Rather than explaining ideas through documents or presentations, stakeholders experienced the product directly. They could navigate workflows, explore conversations and understand the value proposition in a way that static specifications could never communicate. The product became tangible long before it became technically complete.

This approach fundamentally changed the relationship between product strategy and engineering.

Development no longer carried the responsibility of validating every assumption. By the time functionality was implemented, many of the most important product decisions had already been challenged, refined and aligned through real-world conversations.

Retreve demonstrated that commercial readiness doesn't begin after development.

It can evolve alongside it.

The Product Experience Model became the bridge between vision and execution, allowing the product to mature through understanding before it matured through software.

For Extant, this has since become a core principle of how products are shaped.

The first version people believe in is often more important than the first version they can install.