SignalDesk · B2B SaaS · News intelligence

SignalDesk

I redesigned a SignalDesk product, end to end: the marketing website first, then the web app, both built on one news data engine called BoardAPI.

SignalDesk

Role

Product designer, brand and web designer

Timeline

6 months: 2 marketing websites, 4 web app

Team

Working directly with 2 founders

Platform

Product: desktop web. Marketing: responsive web and mobile

Role

Product designer, brand and web designer

Timeline

6 months: 2 marketing websites, 4 web app

Team

Working directly with 2 founders

Platform

Product: desktop web. Marketing: responsive web and mobile

Industry

News intelligence · B2B SaaS · Data and AI

Tools

Figma, Photoshop, Illustrator

CONTEXT

A product that looked like five companies

SignalDesk grew through unconsolidated design phases, stitched together into a dated, low-contrast product. Its apps felt like separate products, and the NewsboardAPI site didn’t explain the data it sold. With churn, feedback in demos and support tickets signalling the problem, the founders needed one family of products: current, accessible, and able to show business ideas visually.

Before: stitched-together design phases. After: one family of products.

Before: stitched-together design phases. After: one family of products.

Two products, five surfaces, one priority

NO-CODE · 4 SURFACES

SignalDesk

Analysts search and track news in Monitor, Intelligence, Compare and the ESG tool.

CODE · 1 LAYER

BoardAPI

Developers pull the same enriched news into their own code. The site has to explain that data.

PRIORITY

One family

Give all five surfaces one structure, type scale and color, so they read as one company.

IMPACT

Both phases shipped in 6 months

44

product screens redesigned, across a complex product with dense graphics and inner pages.

48

marketing pages and 16 custom illustrations, designed for responsive web and mobile.

128

components and 28 screens audited for accessibility.

APPROACH

Key decisions

Three decisions turned five stitched-together surfaces into one family.

One family, not five products

DECISION 01

One family, not five products

I gave every surface the same structure, type and color, so Monitor, Intelligence, Compare, ESG and the API site read as one company.

DECISION 02

Accessibility as the baseline

I audited 128 components and 28 screens and designed out the low contrast that made dense data hard to read.

Showing data, not describing it

DECISION 03

Showing data, not describing it

I drew 16 custom illustrations so buyers could see what the enriched news data does.

INSIGHTS

What I learned from existing product

Source: internal pain points, demo feedback, countless support tickets

1

Low contrast hid the data

The users where finding it hard to analyse the data with clarity, since the contrast were too low, and the charts were not impactful.

2

Five apps felt like five different businesses

Not only the customers, but also internally the design debt accrued and there was a sentiment that the products are not a family.

3

The search was not clear on how to use it

Their advanced search required quite some learning curve. There was a missing hierarchy among search, sort and filter.

SOLUTION

Solution highlights

One screen answers: what needs my attention?

The home leads with alerts, trends and a map, so analysts start from what changed.

Top concepts and categories, readable at a glance

Top concepts and categories, readable at a glance

Dense analytics, rebuilt with accessible contrast and one chart language.

Where it is happening, on one map

Where it is happening, on one map

Events are placed on a map next to the stories behind them.

One picture explains how the data is enriched

The marketing site shows the data pipeline instead of listing features.

Same family, from desktop to mobile

Same family, from desktop to mobile

48 pages designed for responsive web and mobile, in one visual language.

LEARNINGS

What consolidating a product family taught me

LEARNING 01

Consolidation is a product decision, not a style pass.

One family needed a shared structure across five surfaces, not only a shared color.

LEARNING 02

Start where the risk is lowest.

The marketing site let us set the new visual language before it reached a complex product.

LEARNING 03

Fix accessibility at the component level.

Auditing 128 components meant one fix reached every screen that used them.

LEARNING 04

Graphics sell data products.

A picture of the pipeline explains enriched news faster than a list of features.