Omnia Partners

Omnia Partners — A portal partners stopped routing around

A twelve-month redesign of Omnia Connect from an underused hub into a data-first partner portal — dashboards, user management and a design system built to carry growth.

Role
UX Design · Creative Direction
Team
Sagepath Reply · Omnia Partners core team
Years
2021
Industry
Group purchasing
Headline result
$50B

Transaction volume the redesigned partner portal was built to support, with dashboards for contract savings, supplier opportunity and pipeline health.

A twelve-month redesign of Omnia Connect from an underused hub into a data-first partner portal — dashboards, user management and a design system built to carry growth.
Primary surface
Fig. 01

[ The problem ]

Omnia Connect was meant to be the hub where partners tracked contract savings, supplier opportunities and performance. In practice it was siloed and out of date, so partners bypassed it and asked for information directly — which cost everyone time and quietly told them the portal could not be trusted. Without intentional design the hub delivered neither value nor credibility, and engagement followed.

[ Goals ]

Engagement — make the portal worth opening by putting real data where people look first. Simplicity — present the numbers that matter without the noise around them. Adaptability — a framework that can carry new dashboards without a redesign. Credibility — layouts that make partners trust the information enough to act on it.

    Approach

    Twelve months, run as a series of decisions rather than a single reveal. Moodboards first, to get stakeholders agreeing on what credible looks like before any screen existed. Then the dashboards, one at a time, each tested with the people who would live in it: partners for the partner view, sales leadership for the pipeline view, administrators for user management. Every round asked the same question of the data: what does this person need to decide, and what can be cut so they can decide it faster?

    [ Scope and constraints ]

    What I owned
    Constraints
    How it was tested

    [ The work ]

    The surfaces.

    BeforeAfter
    1

    Moodboards

    Agree what credible looks like before designing a single screen.
    Objective

    Agree what credible looks like before designing a single screen.

    Process

    Built moodboards around type, colour and component language, and used them as the decision surface with executives rather than showing early screens.

    Outcome

    Stakeholders aligned on a modern, trustworthy tone — and stopped debating aesthetics once the dashboards arrived.

    omnia-partners-connect
    2

    Homepage dashboard

    Make the first screen immediately worth the visit.
    Objective

    Make the first screen immediately worth the visit.

    Process

    Key metrics, curated news and featured opportunities in a strict hierarchy — brevity over completeness, so the page answers before it asks.

    Outcome

    Busy users get the state of things in one glance instead of a menu.

    omnia-partners-connect
    3

    Partner dashboard

    Let a partner assess value without asking someone for it.
    Objective

    Let a partner assess value without asking someone for it.

    Process

    Contract savings, supplier opportunities and partnership metrics in a single view, prioritised for clarity over density.

    Outcome

    The portal became a collaborative tool partners open first, instead of a hub they route around.

    omnia-partners-connect
    4

    Sales dashboard

    Give internal teams and executives a shared read on pipeline health and growth.
    Objective

    Give internal teams and executives a shared read on pipeline health and growth.

    Process

    Simple visualisations of pipeline and trend, designed to be read in a meeting rather than studied at a desk.

    Outcome

    Performance and opportunity visible in one place, driving alignment across the organisation.

    omnia-partners-connect
    5

    User management

    Make access and permissions secure without making them a chore.
    Objective

    Make access and permissions secure without making them a chore.

    Process

    A simplified structure that reduces friction for administrators while giving partners confidence in managing roles and permissions.

    Outcome

    Administrators move faster and partners trust the system with their own access.

    omnia-partners-connect
    6

    Design system

    Keep every dashboard — and every future one — consistent without a designer in the loop.
    Objective

    Keep every dashboard — and every future one — consistent without a designer in the loop.

    Process

    A lightweight system of reusable components and visual guidelines, sized to the team that would maintain it.

    Outcome

    A scalable framework that supports growth; the next feature inherits the system rather than reinventing it.

    omnia-partners-connect

    [ The system underneath ]

    [ Results ]

    $50B | Transaction volume supported 5 | Dashboards designed and shipped 12 mo | Redesign, research to release

    Omnia Connect went from a portal partners routed around to one they opened first. Contract savings, supplier opportunities and pipeline health each got a view built for the person reading it, and the shared system underneath meant the next dashboard cost a fraction of the first. Credibility was the real outcome. Reliable, well-ordered data presentation restored trust in the portal as the source of truth — which is what a self-service model needs before it can scale.

    What I carry forward

    Balancing what partners need against what executives need taught me that the most persuasive thing a dashboard can do is leave things out. Intuitive data presentation is a strategic decision, not a visual one.

    ← All work

    More work