Skip to content

Enterprise Design / Product Design / System Thinking

Intelligent Enterprise Search Platform

A platform for AI-powered enterprise search — built so finding anything across an organisation is as simple as asking a question. It connects a company's existing tools into one knowledge base and answers in plain language, with every source shown.

Enterprise search platform overview
Client
UnifyApps
Platform
Web & Mobile
Timeline
2025 - Present
My role
Lead Product Designer

Engagement

Unifying enterprise knowledge into one intelligent experience

We led the end-to-end product design of an AI-powered enterprise search platform — built to be deployed and sold across large organisations — working directly from the client brief through to Final-for-Dev handoff, representing ICD as the design partner for UnifyApps. The platform replaces fragmented tool-switching with a single intelligent interface, connecting search, agents, integrations, and administration on a shared knowledge index that works from the same understanding of who each user is and what they have access to.

The Problem

Good intentions. Broken handoffs.

Organizations already had the information they needed, but it was scattered across documents, communication tools, and business applications. Finding the right answer meant searching multiple systems, checking permissions, and piecing information together manually. The challenge wasn't access to data—it was making that knowledge easy to discover, trust, and use.

Search returned files instead of answers.

Users received a list of documents rather than a direct answer. They still had to open multiple files, compare information, and find the right context themselves.

Knowledge was spread across disconnected systems.

Information lived in different applications with no single place to manage or understand what AI could access. This made knowledge difficult to maintain and trust.

Results treat everyone the same

Search has no understanding of who is asking or what they need. Everyone gets the same results regardless of their role or context.

Teams couldn't adapt the platform to their needs.

Different teams had different workflows, but the experience remained the same for everyone. Customizing it required engineering effort, limiting flexibility and adoption.

Limited transparency reduced trust.

When teams have no way to see how a system handles their data, they can't trust it enough to use it.

Discovery

Three roles. Three different expectations.

The product team defined the roles and led the research. The brief gave us three working roles — we turned those findings into clear design decisions for each.

Employees needed answers they could trust.

Users wanted more than fast search results. They needed clear, reliable answers with supporting sources so they could act confidently without manually verifying everything.

Administrators needed control without engineering.

Administrators understood their organization's needs but couldn't configure the platform on their own. They needed the ability to manage integrations, permissions, and settings without depending on engineering teams.

Compliance teams needed visibility.

Compliance reviewers needed to understand what data the platform could access and how it was being used. Clear permissions, auditability, and transparency made approvals faster and more reliable.

Together, these insights shaped our strategy: build a platform that delivers trusted answers for employees, gives administrators control, and provides compliance teams with the visibility they need to confidently approve adoption.

Roles and expectations map

Design Strategy

One platform. Different levels of responsibility.

We designed the platform as a copilot: Search, Chat, Agents, Spaces, and Apps working as one system, on a shared knowledge index and a single interaction model. The same product then opens up as responsibility grows — from asking a question, to configuring how the product behaves, to governing what it can reach. Nobody is asked to trust a system they cannot see inside.

Ask

Search in natural language and receive clear answers with supporting sources. Designed for users who simply want to find information and take action.

Configure

Connect data sources, manage integrations, and customize the platform without relying on engineering. Designed for administrators responsible for maintaining the experience.

Govern

See what the system reaches, set its boundary, approve on evidence.

Connect Applications

One place to bring in everything the organisation knows.

Search can only answer from the knowledge it can access. By connecting tools like Slack, Jira, GitHub, and Google Drive, teams can create a single shared knowledge base without depending on IT. Clear connection statuses show exactly what data is available, making the platform transparent and easier to trust.

Connect applications screen
Connector setup screen

Manage Connections

The place where someone stays responsible for the data.

Connecting a source is easy. Keeping it right is the work. Here, administrators check that data is still updating, choose what should and should not be included, and see clearly what has failed. It turns the knowledge base from something assumed to be correct into something anyone can check — which is the difference between a system people trust and one they quietly stop using.

Manage connections screen
Sync health and filters

Personalised Results

An answer to the question, not a list of files to read.

Connecting a source is easy. Keeping it right is the work. Here, administrators check that data is still updating, choose what should and should not be included, and see clearly what has failed. It turns the knowledge base from something assumed to be correct into something anyone can check — which is the difference between a system people trust and one they quietly stop using.

Personalised answer with sources

Customise Enterprise Search

The controls that let a company make the product its own.

Every organisation that buys the platform works differently, so the product has to feel like theirs rather than ours. Administrators set how search looks, sounds, and behaves — the branding, the wording, the tools that are switched on, the AI model behind it — on their own, without engineering. The settings are written in plain language, so the person who knows what the organisation needs is the same person who can go and change it.

Search customisation settings
Branding settings
AI model settings

Agent Marketplace

Where finding an answer turns into getting the work done.

Search answers a question. An agent does the task. This is where teams find ready-made agents for finance, legal, sales or operations and put them straight to work. Making it a store rather than a builder was the point: what one team proves useful, every team can reuse. Each agent shows what it does and whether it has been checked — because the hard part is never finding an agent, it is being allowed to trust one.

Agent marketplace

Outcomes

Real client outcomes built on this platform.

These are UnifyApps' published figures from a large financial institution's consent and communications deployment, built on this platform's automation and governance layer. We did not measure them. The configuration, governance, and review flows shown above are what made the timeline possible.

$5.5M
Projected annual cost savings from replacing fragmented, manual consent processes with automated, governed workflows.
800K+
Consumer consents captured in the first two weeks of deployment.
90% faster
Time-to-market — traditional builds of this kind take 12 to 18 months; this shipped in two weeks.
37%
Improvement in message delivery rates after consolidating 27+ messaging systems into one governed channel.

Published in UnifyApps' customer story for this engagement.
unifyapps.com/resources/customer-story

Reflections

In enterprise AI, trust is the product.

Building this platform showed me that AI performance alone isn't enough. People need to understand, verify, and rely on the system before they'll use it in their daily work. The biggest design challenge wasn't creating AI—it was designing experiences that people could confidently trust.

Trust starts with every answer.

Users trust AI more when they can immediately see where an answer came from. Showing sources and context alongside each response makes information easier to verify and reduces the need for manual checking.

Transparency builds confidence.

A trustworthy product doesn't hide problems. Showing failed syncs, pending connections, or unverified agents helps users understand the system's current state and gives them confidence that nothing is being hidden.

Design for everyone involved in the decision.

The people using a product aren't always the ones deciding whether it gets adopted. Administrators and compliance teams also need visibility and confidence in how the system works. Designing for all stakeholders is essential for enterprise AI adoption.