← Back

NetBet Design System & Acquisition Template

At NetBet, buttons and forms changed from one screen to the next, and marketing built every campaign asset by hand in Photoshop. I built NetBet’s first design system in Figma, then a campaign template on top of it that cut asset creation time by around 70%.

View the template (opens in a new tab)

Figma file. Opens in a new tab.

time−70%
tickets−80%
components50
NetBet design system overview: button sizes, type styles and variables next to the live site
Button sizes, type styles and variables alongside the live site.

01 · The problem

The same parts, different every time

NetBet is an online betting and gaming company. Its website and apps didn’t look like one product: buttons had different colours and text styles, and form fields followed no shared rules. It showed in both Sport and Casino.

There was no shared base. Designers started many screens from scratch, engineers received constant changes, and the back-and-forth of revisions slowed every launch.

02 · Understand

An audit first

I audited the live designs and confirmed the differences in buttons and forms. I also studied the design system of a sister brand. It wasn’t a model to follow: it had disorganised styles, implementation errors, broken libraries and duplicated components. It became a list of what to avoid.

NetBet foundations: tokens, typography and the 8-pixel grid
Foundations: tokens, typography and the 8-pixel grid.

03 · Scope

A first phase of two to three months

The goal was to build the groundwork quickly, and to make it easy to understand and use. The first phase covered three parts:

04 · Design

Foundations, components and documentation

I started from NetBet’s brand guidelines and adjusted them to work on both web and app. I adopted an 8-pixel grid so spacing stayed the same once built.

For buttons, I kept variants to a minimum and used Figma component properties, such as booleans, for the states: hover, disabled and active. I followed the same method for inputs, cards and headers. The library grew to 50 components.

Documentation lived inside Figma, short and direct, next to each foundation and component.

The NetBet button component in Figma with its properties: size, status, type, variant and icon toggles
The button: size, status, type and variant as properties, with icons switched on by a boolean.

05 · Test

Built with the front-end developer

As the front-end developer implemented the styles and components, we kept a constant feedback loop. Their questions and suggestions, such as a clearer way to organise the colour variables, refined the system with each iteration.

Annotated specs for the button, game card and header, next to a design review with product and engineering
Annotated specs for handoff, reviewed with product and engineering.

06 · Extension

From the system to campaigns

Marketing needed to launch campaigns faster across web, CRM, social and display. Every asset was designed separately in Photoshop, with no shared structure. Updates were repetitive, and design and marketing barely worked together.

Before the template: a Photoshop file per banner size and a Jira backlog of campaign asset requests
Before: a Photoshop file per size and a Jira ticket per asset.

Acquisition campaigns were the perfect test for the system. I designed a modular template in Figma, connected to the design system. You edit the main elements once (visual, offer, CTA, terms and landing page steps) and every linked format updates.

The acquisition template in Figma: introduction, first steps, main elements and exports
The template: a guide, the main elements and the formats ready to export.
One Wimbledon free bet campaign adapted to social banners, display banners and landing pages
One campaign adapted to banners, social and landing pages from the same elements.

07 · Outcome

One base for product and marketing

The project confirmed what matters most when starting a system from scratch: working closely with engineers, documenting clearly, and choosing well what to build first. The system kept growing after this first phase.