B2B Signature Platform Redesign
When brand becomes a system: a token-based design system and the core flows of an eIDAS-compliant e‑signature platform for B2B.
Client
eIDAS e‑signature platform (B2B SaaS)
Role
Senior product designer, first on the team
Year
May – December 2025
Services
Design system architecture · Token-based theming · Component library · Information architecture · Workflow design

01
Context
A from-scratch redesign of an eIDAS-compliant B2B e‑signature platform, used by enterprise customers for legally binding document workflows. I was the first designer on the product; the team grew later and built on what I set up.
02
I started with a logo and a colour palette — and needed a product.
A separate studio had set the brand: logo, palette, typography, voice. Everything between brand and product was missing — the system that turns a few visual decisions into a working interface, and the core flows built on it.
Two problems at once:
For users: signing, finding documents and managing settings had to be fast and unambiguous — these are legally binding actions.
For the business: the platform was entering a new growth phase, and more designers would join. The foundation had to hold in other people's hands.
03
Constraints
Fixed brand. Built on the foundations from the prior studio — not around them.
Legally binding (eIDAS). No ambiguity about what a user signs, or when.
An established enterprise ecosystem. The product is sold on Microsoft Marketplace, so it had to feel familiar to enterprise users — while still carrying its own brand.
One designer now, a team later. Every decision had to make sense to people who weren't in the room.
Eight months, May to December 2025 — from first wireframe to a shipped product.
04
A proven base, the brand as a layer on top. Instead of a system from scratch, I extended an established enterprise design framework: its type ramp, elevation and component logic stayed, and the brand came in through tokens.
Built in a deliberate order: icons → tokens → components → screens. Each layer constrained the one above it, so the screens demonstrated the system instead of driving it.
Alongside the design work, I ran an accessibility review of the key screens — home, inbox, document upload, recipients, templates, settings and search.
The core flows went through many iterations with the team before reaching the versions shown here.
Gallery

Colour: five ramps of thirteen steps plus a neutral ramp, each with its light and dark primary

Type: one family, eight heading styles that scale across three sizes, eleven body and caption styles that stay the same

A value becomes a global token, then an alias — the same alias works in light and dark

Buttons: five variants in every state, plus menu and split buttons — all built from the same tokens

Inputs: seven states in three display modes, including errors with a message

Feedback: message bars in four intents and two widths, toasts in light and dark
05
Key decisions
1. Extend an established framework instead of building from scratch.
Instead of a fully custom system, I built on an established enterprise design framework — 19 text styles from Caption (10/14) to Extra Large (80/96), elevation styles, familiar component behaviour — because enterprise users already know those patterns. Trade-off: less visual freedom, so the brand had to come through tokens, colour and icons.
2. Icons first.
Icons were the first decision: they touch every screen — nav, forms, empty states, toasts — and set one visual voice from the first button. I used the Remix set and made it work inside the system — organised by category and size, and consistent in weight and spacing with the rest of the components.
3. Three token layers instead of one.
Global → alias → component: global values change without touching components, aliases (surface.primary, border.subtle) carry intent across light and dark, and a new component binds existing aliases instead of inventing new values. Trade-off: more setup up front, in exchange for a system other designers could extend safely.
4. Signature creation as one surface — with every state designed.
One dialog with four tabs — saved, draw, type, import — and import sources (device, URL, cloud) expanding inline, because many options had to feel like one decision. Then I designed the states around it, desktop and mobile: an empty canvas that tells you what to do, a character counter before the limit is hit, Save disabled until an imported image is valid, optional crop, a clear message when the plan limit of five signatures is reached, and a toast that confirms without leaving the dashboard.
5. Search that works before typing.
Search went through several iterations before the final version. It opens as an overlay with recent searches, quick links and action items already visible — because in a high-volume document environment, search is the main way people find anything. Results are grouped by type and work the same way on mobile.
6. Settings by what users manage, not by backend.
Enterprise settings tend to become long lists grouped the way the backend was built. Instead: four surfaces — sending, signing, delivery, notifications — so users go straight to what they came for. The same card-based entry layout repeats for account and subscription settings, so every settings area works the same way.
Gallery
Flow A — Signature: every method, every state

One dialog, four methods: saved, draw, type, import — on desktop and mobile

Draw — saving an empty canvas shows an inline error instead of failing silently

Draw — once there's a signature, Save becomes active

Type — choose from generated styles

Import — three sources in one place: device, URL and cloud

Import from URL — Save stays disabled until the image is valid

Import from cloud storage — browse and pick a file without leaving the dialog

Import — crop, rotate or remove the image before saving
Flow B — Search: useful before you type

Before typing: recent searches, quick links and action items — on desktop and mobile

While typing: suggested searches match as you type, the same on desktop and mobile
Flow C — Settings: organised by what users manage

Digital signature settings: sending, signing, delivery, notifications — each a clear entry point
06
The platform shipped in 2025 and is live on Microsoft Marketplace.
When the team grew, other designers built on the foundation. Some decisions held and others changed; the token architecture absorbed both without breaking — a system that can't be changed isn't a system, it's a style guide.
on Microsoft Marketplace


