Case study · 0 to 1 · Kolsquare

Building an influencer
marketing platform from scratch

RoleProduct Designer (solo), reporting to the CEO
Timeline2 years (2018 – 2020)
ScopeBrand · Design system · SaaS platform · Chrome extension · 4 developers
My role in this initiative

I joined Kolsquare as its first and only designer, when the company had no brand and a bootstrapped product embryo. Reporting directly to the CEO and working with a team of four developers, I built the three foundations a startup needs to sell: the brand identity, the design system, and the product itself, from the influencer search engine to a free Chrome extension that became our acquisition engine. The mandate was simple: ship an MVP fast enough to sign our first clients, then turn those clients into pioneers who would help us design the rest.

The problem

Brands were spending on influencers blindly. And Kolsquare had nothing to show them yet.

In 2018, influencer marketing was booming, but brands were running it on gut feeling. They had no tool to find the influencers that actually matched their audience, and no data to prove what a campaign had delivered once it was over. Selection happened through spreadsheets, agency networks and follower counts that said nothing about who was really listening.

Kolsquare wanted to bring data to that market. But the starting point was a blank page: no visual identity, no design language, and a bootstrapped product that the founders could demo, but not sell. Everything a B2B startup needs to earn a client's trust had to be created, at the same time, by one designer.

"Where Brands and Influencers find their perfect match."

Kolsquare brand promise, defined in the brand guidelines

The initiative

Three foundations, built in parallel, with one rule: MVP first.

Time was the main constraint. Speed mattered more than polish, because the goal was to sign clients quickly and bring them on board as pioneers: early users who would shape the product with us. Every design decision was weighed against one question: does this help us sell, or help a client succeed, this quarter?

Core goals

  • Create a brand credible enough for international advertisers, from logo to sales collateral
  • Ship a first version of the platform that solves the two core jobs: finding the right influencers and proving campaign impact
  • Turn early clients into co-builders, with a feedback loop close enough to replace large-scale testing
  • Systematize as we grow, so that four developers and one designer could keep shipping without the interface drifting
Kolsquare brand guidelines: logo and symbol, colour palette with navy, blue, turquoise, pink and lavender, graphic patterns and typography
Brand guidelines: logo system, colour palette, patterns and typography (Playfair Display + D-DIN), created from scratch.

Discovery

Few clients, close relationships: a feedback loop instead of A/B tests.

30
Pioneer clients involved in discovery and testing, shaping the product with us
4
Developers, shipping alongside me with a direct line to the CEO
0
A/B tests: too few clients for statistics, so we tested with them directly

With a small client base, quantitative testing made no sense. What we had instead was a very close relationship with every client. I ran user interviews, tested prototypes and early releases directly with them, and used sales feedback as a constant source of signals.

That sales feedback needed filtering. Some requests were one-off needs or ultra-specific to a single account, and following them would have pulled the product away from its direction. Part of my job was to separate the recurring problems from the individual wishes, and to turn the recurring ones into simple features that worked for everyone.

Whiteboard from a product workshop exploring several navigation options for the platform, including a marketplace entry point
Workshop, October 2018: exploring navigation options as the product grew from search to campaigns and a marketplace.

The solution

A search engine for influencers, built on data brands could trust.

The platform was built around one promise: help a brand find the right voices, and know whether they are worth it. Behind the interface, Kolsquare collected public data from social networks. My job was to turn that raw data into decisions a marketing manager could make in minutes.

Kolsquare search results: a grid of influencer cards with photo, name, category and audience size per social network, with filters on the left
Influencer search: filter panels on the left, influencer cards with reach per network at a glance.

Key features shipped

  • Social network data collection: public data gathered from Instagram, YouTube, Facebook, Twitter and later TikTok, the raw material behind every screen.
  • Influencer profiles with community quality: not just follower counts, but audience credibility, engagement rate, demographics, interests and languages, so brands could spot fake or irrelevant audiences.
  • Search with filters by social network, community size, community quality and theme, the core of the product.
  • Search by brand name: find which influencers already talk about a brand or its competitors, a shortcut to the most relevant profiles.
  • Campaign reporting: posts, engagement and reach consolidated per campaign, the proof of impact brands were missing.
Filter panels: audience scope by social network with community size and engagement rate, audience profile filters for interests, location and age
Filters: network, community size, engagement, audience profile.
Influencer profile page with key audience indicators, community size and engagement per network, location, job and languages
Influencer profile: audience quality before follower count.
Campaign reporting dashboard showing number of influencers, social accounts, publications, engagements, potential reach and likes, comments and shares
Campaign reporting: the proof of impact brands didn't have before.

A free Chrome extension as the acquisition engine

To reach brands before they even booked a demo, we designed a free Chrome extension that displays Kolsquare's audience data directly on Instagram profiles. It gave marketers a taste of the product where they already worked, and opened the door to the paid platform. I designed the extension and its Chrome Web Store presence, localized in five languages. It is still available today.

Chrome Web Store visual for the Kolsquare extension: a side panel on an Instagram profile showing audience credibility, community size, engagement and socio-demographic statistics
Chrome Web Store visual: Kolsquare's audience data, right on Instagram.

Design system

From a brand to a shared language for one designer and four developers.

As the product grew, speed started to create inconsistency. I turned the brand into a component library: buttons, form inputs, dropdowns, tags, notifications, modals and icons, each specified with its sizes, states and behaviours. Specs were defined in workshops with the developers, so that the library matched how components would really be built.

The design system came after the first version of the product, not before. It helped us keep shipping fast, but it also taught me the main lesson of this project (see below).

Whiteboard specifying a dropdown component: sizes, margins, typography, states, responsive behaviour and keyboard usage
Workshop with developers: specifying a dropdown, from states to keyboard behaviour.
Six Kolsquare brand patterns in blue, turquoise and pink gradients
Brand patterns, reused across product, website and collateral.
Overview of the Kolsquare Sketch component library: base elements, form and input elements, buttons in several sizes
The Kolsquare component library: base elements, forms and inputs, buttons.

Navigating complexity

When your data comes from scraping, design has to absorb the uncertainty.

The hardest problems weren't on the screens. They came from the data underneath them, and the design had to make that fragility invisible to clients.

Handmade data collection, at European scale
Data collection was largely handmade at the beginning. Volumes varied a lot from one market to another, and covering Europe meant collecting far more data than covering France alone, with real technical challenges for the developers. On my side, that meant designing for partial or missing data, without making the product look broken.
Loading times as a design problem
Heavy queries meant long waits on search results and profiles. Instead of leaving users in front of a blank screen, I explored loaders, placeholders and empty states so that waiting felt like progress, not failure.
A new network arrives: TikTok
TikTok took off in France while the product was live. Adding a new network touched every screen: filters, profile cards, statistics and reporting. The interface had to absorb a new data source whose metrics didn't map exactly onto Instagram or YouTube.

Impact

From a blank page to more than 100 European clients in two years.

100+
European clients after two years
3
Foundations built from scratch: brand, design system, product
5
Languages for the Chrome extension, still live today
A community of pioneers.
Our first clients didn't just use the product, they helped design it. That community of pioneers created real momentum, and gave us a feedback loop no A/B test could have matched at that stage.
A free tool that brought clients in.
The Chrome extension was much appreciated by users and acted as a lead magnet for the paid platform. It is still available on the Chrome Web Store today.
A brand that outlived my time there.
The Kolsquare brand has evolved since, but its core is still the one I created.
Speed, then structure.
The MVP-first approach got us to market fast. The design system then gave four developers and one designer a shared language to keep shipping as the product and the client base grew.

What I'd do differently

Lay the foundations on day one, and make them replicable.

Kolsquare taught me what it takes to go from nothing to a product people pay for. It also showed me where I would work differently today.

1
Design system foundations from the start
We built the design system after the MVP, and paid for it in inconsistencies to clean up. Today I would lay lightweight foundations on day one: tokens, a few core components, clear rules. Not to slow the MVP down, but so it can scale without being rebuilt.
2
AI to move faster
With today's AI tools, the cycle from idea to tested prototype to production-ready code is much shorter. I would go faster and further with the same team, the way I now ship features with AI on top of a design system.
3
A framework you can replicate
Brand, design system, MVP, pioneer community: these steps are the same for every new venture. Today I would turn them into a repeatable framework, so the next product starts from a solid base instead of a blank page.