Design System SaaS — UI Library

Design Tools · UI LibraryAnonymised

A design system built a demand engine and then a community.

The client entered a market dominated by names every designer already knew — Material, Ant, Chakra, Tailwind UI, Shadcn. We built a multi-channel marketing system from scratch and turned an unknown UI library into a thought-led, fast-adopting design system.

Industry

Design Tools · UI Library

Engagement

Founder-led · 6 mo

Services

GTM · Content · SEO · Community

Audience

Designers · Devs · Agencies

The Challenge

A new design system in a market full of household names.

The client launched into a category where every designer already had a default — Material, Ant, Chakra, Tailwind UI, Shadcn. The product was strong. The problem was that nobody knew the product existed, and nobody was looking for a new option.

We were starting from zero on every axis that mattered: zero organic traffic, no community, no content, no demand. And we were doing it in a market where the audience splits across three very different personas — freelance designers, in-house developers, and creative agencies — each of whom evaluates a design system through a different lens.

A single-channel push wouldn't move the needle. The strategy had to be multi-channel from day one, and tightly tied back to one place: documentation and adoption.

The shape of the work

Design system demand engine — interconnected, not stacked

The product

Docs · Sign-up

SEO

Blog · Use cases

Tutorials

How-to · Demo

Social

LinkedIn · X · IG

Influencer

Thought leaders

Compound outcomes

Each channel reinforced the others.

  1. 01

    +200% traffic

  2. 02

    3.3K design users

  3. 03

    2K library users

  4. 04

    40% engagement

Four channels feeding into one product surface — docs and sign-up. Every channel was measured against adoption, not vanity.

The Approach

Five layers, one funnel.

01/ 05

Market research & persona work

Started with competitive analysis across the design system landscape and built detailed personas for the three audiences — freelance designers, in-house developers, and creative agencies. Each had a different "moment of need" and a different channel where that moment showed up. The marketing plan was structured around that split, not around channels.

02/ 05

Content-driven awareness

Built a library of SEO-optimised blog posts, use-case write-ups, and visually compelling explainer content. Each piece was designed to capture a specific search intent and feed back into product documentation. Tutorials and demos extended this — content that taught the audience while showing the product in motion.

03/ 05

Documentation as a demand channel

Treated product documentation as a top-of-funnel asset, not a post-sale resource. Clear how-to docs, walkthrough videos, and structured guides made the product easy to evaluate without a sales conversation — which is the only way a design system gets adopted by designers.

04/ 05

Social and community

Built distinct presences on LinkedIn, Twitter (X), and Instagram, each with platform-specific content rhythm. Partnered with influencers and thought leaders in the design space to amplify reach into communities that don't respond to paid acquisition.

05/ 05

Measurement & iteration

Set up tracking against the metrics that mattered — traffic, sign-ups, library adoption, engagement — and ran A/B tests across messaging and creative. Every channel had a kill criterion. Two channels were dropped within the first quarter because the data said so.

The Results

From unknown library to fast-adopting design system.

Within six months, website traffic was up 200%. The Figma community page hit 3.3K design users; the developer-facing UI library crossed 2K. Social channels were producing a 40% engagement rate — the kind of number that only comes from getting the content–audience match right, not from spend.

The compound effect was the more interesting one. The client moved from "design system I haven't heard of" to "design system I keep seeing" in the conversations that matter — freelance design communities, indie hacker circles, and the LinkedIn networks of senior designers at scale-ups. That shift in perception is what made every subsequent campaign cheaper, faster, and easier to scale.

Behind the GTM

Walkthrough coming soon

How an emerging design system built a demand engine in a crowded market

60–90s product walkthrough or founder interview. Suggested arc: 1) the crowded design system market, 2) the multi-channel strategy in 30s, 3) the adoption metrics, 4) what is next for the client.

Build your demand engine

Crowded category? Unknown brand? That's the brief I take.

The client did not have a budget, a brand, or an existing audience. It had a product worth knowing. Most B2B SaaS founders are in a similar position. A 30-minute call costs nothing — and tells you whether your unknown is actually a marketing problem.

Book a Call