Case study · Design

One brand system, replacing three blues and four button shapes

Ritorica's decks, banners, emails and website each looked like a different company. As the only designer I wrote the brand and UI system that put them on one hue, then built the work on top of it: four event-banner directions, four whitepaper covers, an Arabic logo, and print-ready files for a hoodie and a business card.

  • Role: the only designer, from the token layer to the print files
  • Covers: colour, type, shape, voice, components, slide and email templates, logo rules
  • Built with: Figma, Canva, Claude Design, HTML and CSS
  • Published by the company: the system, the event and print work, and the whitepapers
The foundations page of the Ritorica design system: the brand stats, the company and product context, and the voice and tone rules.
The foundations: what the company is, how it speaks, and the one blue everything is built from.
What this proves: I can turn a scattered brand into rules other people can follow, and then produce the finished assets myself, down to the print file the printer needs.
1 hueRitorica blue and its tints, in place of three competing blues and four button shapes
4event-banner directions, built from the same parts
4whitepaper covers, each 1200 × 675
3candidate typefaces for the Arabic logo, letters outlined so it needs no font
330 mmhoodie back print, with a two-ink chest lockup; cards at 94 × 54 mm

The problem

The brand lived in two source decks and a licensed display font nobody could install. Every new asset was traced by hand from an old file, so each one drifted a little further: three shades of blue, four button shapes, headings in whatever typeface was to hand.

What the system fixes

  • One hue. Ritorica blue and its tints carry every accent, chip, chart and call to action, with a single diagonal gradient for heroes and primary buttons. No new hues; semantic green, amber and red only for delivery status.
  • Type with a licence-free substitute. The brand display face is licensed, so the system names an open substitute and says exactly where each is allowed.
  • Shape and depth as rules, not taste. Fixed radii per element, and blue-tinted shadows rather than grey ones.
  • Voice written down. Person, casing, tone, vocabulary, and the pattern the copy follows: promise, then mechanism, then proof. Numbers lead.
  • Components, not pictures. Tokens and components in code, so a deck, a landing page and an email start from the same parts.
The Arabic logo study: the wordmark set in three typefaces, each shown on light and dark, with the speech bubble mirrored so its tail points the Arabic way.
The Arabic logo. The speech bubble is the original artwork, mirrored so its tail points the right way, sitting over the alef exactly where it replaces the dot in the Latin wordmark. Three typefaces to choose from, then the letters go to outlines so the logo needs no font.
The slide template set: eleven slides in the sidebar and the title slide open, with the logo, the rounded-square motif and a blue angled panel.
Slide templates for sales and partner decks.
An event banner: the stats block, a short product paragraph and a coverage map with channel pins.
One of four event-banner directions, built from the same parts.
Four whitepaper cover designs: a benchmark report, a deliverability playbook, a WhatsApp Business API guide and a cascade routing strategy, each with a tag pill and one illustrative object.
Covers for the whitepapers, one per paper. Each is 1200 × 675, shows one object that stands for the paper's idea, and keeps everything important 84 px clear of the edge so it survives rounded-corner cropping.

What got built on it

  • Slide templates and a webinar deck.
  • Four event-banner directions, plus booth material for two international telecom events.
  • Email templates, including the whitepaper campaigns.
  • Four whitepapers with their own landing pages, each tied to a LinkedIn series and an email campaign.
  • Print files: a company hoodie taken from mockup to a print-ready vector at 330 mm with a two-ink chest lockup, and a business-card template at 94 × 54 mm with 2 mm bleed, CMYK and type converted to outlines.

The website in the ritorica.com case study is built on the same system.

Two hoodie layouts with print sizes in millimetres: the back carries the slogan Level up your business, we handle the rest, under a pixel rocket; the front carries the Ritorica logo on the left chest.
The hoodie print file. Back: the slogan and a pixel rocket, 330 × 370 mm. Front: the logo on the left chest, 140 × 54 mm. Two inks, white and Ritorica blue, all vector.
The front and back of a Ritorica business card. The back's name, QR code and contact details are blurred.
The business card, 94 × 54 mm with 2 mm bleed. Front: the logo on the rounded-square motif. Back: name, QR code and contacts. It belongs to a colleague, so the personal details are blurred here.

What I'd do differently

I wrote the system after the assets, from whatever the old decks happened to contain. Writing the token layer first would have meant less archaeology and fewer judgement calls about which of three blues was the real one.

← All work