SenseOn: Integrations Redesign

Discovery: Understanding the problem

Through user interviews and internal feedback sessions (including with our SOC team), several key themes emerged:

• The platform’s integrations were difficult to find and understand: Integrations were hidden within the settings menu, meaning customers were often unaware that this functionality existed. In addition, integrations that had not yet been configured were hidden by default, making it unclear which options were available.
• Complicated Setup Process: The integration setup journey was unintuitive, leading to user frustration and increased reliance on support.
• Our customers increasingly expected to use SenseOn as a single pane of glass, but the integration options were really limited.
• The existing UI felt outdated and inconsistent with the rest of the platform.

Stage 1: Redesigning the Integration Experience

First, I focused on redesigning the existing UI. The goals of this phase were to:

• Make the UI more usable and modern, while maximising product-led growth
• Improve the visibility and discoverability of the feature
• Use the UI to gather insight into which integrations customers would have liked to see included in the product

First concepts

I analysed the current flow and created a new low fidelity design, which I used to start a conversation with users, developers and stakeholders.

Design iteration

Following user testing and stakeholders’ and developers’ feedback, I introduced several key updates:

• Clear Status Indicators Users could easily distinguish between integrations that were already active and those requiring configuration. Moreover, customers needed the possibility of connecting to the same integration multiple times.
• Logical Grouping Integrations were grouped into categories to aid navigation. Microsoft integrations were surfaced more prominently, aligning with our Ideal Customer Profile
• Navigation Shift Based on research highlighting the importance of integrations in customer workflows, we moved the page from the Settings area to the main navigation. This reflected the platform’s strategic direction, positioning integrations as a core part of the SenseOn experience, especially as customers increasingly looked to use it as a single pane of glass

Finally, I added the elements that would allow us to drive some product-led growth:

• Integration Request Tile and Coming Soon Tiles Dedicated tiles allowed users to request new integrations, helping us prioritise development based on actual demand

Delivery

I worked closely with developers to support implementation, respond to technical constraints, and ensure the designs were accurately translated into production.

Design system

I also updated our design system with the new components, setting a standard for future platform expansions.

Stage 2: EDR Integrations

After Stage 1, we shifted focus to enabling deeper operational workflows, beginning with Endpoint Detection and Response (EDR).

Why edr first?

Microsoft Defender emerged as the most requested integration via the new request tile. This was unsurprising given that our Ideal Customer Profile is Microsoft-centric.

What changed

• Enabled new tiles for supported EDR platforms, beginning with Microsoft Defender

Updated the Investigate UI to:

• Surface third-party device telemetry directly within cases
• Allow analysts to take response actions (e.g. isolate a device) without switching tools

These updates positioned SenseOn as more than just a detection tool, it became a better response platform that streamlined analyst workflows across integrations.

Stage 3: Identity Integrations

As Microsoft 365 alert adoption grew (enabled by the Stage 1 improvements), we noticed a shift: more investigations were centred around users, not devices.

Why identity became a priority

• M365 telemetry led to a surge in user-related cases
• SOC analysts needed richer user context to assess threats (e.g. knowing whether a user is a developer vs an HR employee)
• Containment actions like disabling accounts or revoking sessions became increasingly important

Key outcomes

• We integrated identity providers like Microsoft and Okta
• For Microsoft-connected environments, user details and response actions were automatically surfaced within investigations

For other providers, we launched a brand-new “Identities” page where users could:

• Search for identity data using usernames
• Perform containment actions such as disabling accounts

The Identities page was a major new feature for the platform. We launched it with a simple, focused UI, enabling us to observe usage patterns and determine future enhancements.

All designs were also created in dark mode, to maximise accessibility and customisation.

Results

The integrations redesign delivered substantial product and business value, transforming how customers interact with and derive value from SenseOn’s platform:

• Drove revenue growth through integrations The redesigned integration experience became a key revenue driver, contributing approximately 80 % of upsell revenue through strategic integration visibility and embedding within the core product experience.
• Accelerated Product-Led Growth adoption For the first time, customers could discover and configure integrations autonomously, reducing reliance on sales or support and enabling a scalable self-serve motion that supported the company’s broader Product-Led Growth strategy.
• Improved conversion through clearer product value By surfacing integrations more effectively (via the new Integration page) and enhancing contextual visibility in the Investigate workspace, the product demonstrated its extensibility, contributing to higher conversion rates across key user journeys.
• Dramatically reduced integration delivery time What previously took multiple quarters to design and ship could now be delivered in weeks, thanks to streamlined workflows, modular UI components, and closer collaboration with engineering.

Testimonials