Simon Jun

COO @ Clipster - We're hiring! - From 0 to $2M monthly GMV in 18 months | Sharing the systems, hires and fuckups behind fast growth

[Simon Jun @simonjun_]

@lukeredien using your brain is OP. Not many people know.

[Simon Jun @simonjun_]

One of our guys spent 10 hours every week copying numbers into a spreadsheet. By hand.

Built a claude schedule that does it automatically.

Took me 20 minutes.

It’s not about wether it’s possible but wether you tolerate it.

[Simon Jun @simonjun_]

@ClipsterKonne you're welcome

[Simon Jun @simonjun_]

Boring processes are what let a small team do the work of a big one.

[Simon Jun @simonjun_]

@clipsterfilip looks like a reality show

[Simon Jun @simonjun_]

@lukeredien lmao

[Simon Jun @simonjun_]

@turanselvi will always be a step ahead anyways

[Simon Jun @simonjun_]

We created a Figma plugin that pushes design changes straight to production.

One click in Figma, live in dev.

It saves us 8 hours of handoff every week. Here is exactly how it functions.

Design tokens live only in Figma. Engineers use tokens too, on their side, in code. The problem: the two sets aren't connected.

So every change means a ticket or a Slack message.

The plugin we’ve built solves all of this:

It starts with design tokens. In Figma, the design decisions live as a variable → colors, font styles, paddings, border radius.

A button is just a combination of them: background color + radius + font + weight.

To turn those tokens into code, the plugin runs two steps:

Step 1️⃣ → It translates the naming.

Android, iOS, and web all use different naming conventions. Same token, three syntaxes.

The plugin rewrites our tokens per platform, so both sides finally speak about the same token.

Step 2️⃣ → It pushes everything to GitHub.

The tokens land directly in our three repositories: web and both mobile apps. In the exact format the engineers work with.

Few clicks in Figma → synchronized to GitHub → one click → live on production.

Shipping design changes almost daily without any handover.

Some teams might not need it.

But we move fast and change core design decisions constantly.

Building this pipeline was the only way to keep up.

I care about this topic a lot. Design and engineering speaking the same language, connected by tools instead of tickets. I even wrote a book about it.

If your design tokens and code tokens still live in two disconnected worlds, this is your sign to fix it.

PS: Ask me any question about the plugin in the replies!

[Simon Jun @simonjun_]

@ClipsterKonne what was the CPM?

[Simon Jun @simonjun_]

@clipsterfilip we fought really hard on getting API access. Not easy.

[Simon Jun @simonjun_]

@turanselvi 😂

[Simon Jun @simonjun_]

The onboarding when I joined Clipster kind of shocked me:

"Here is an ocean. Enjoy."

No documentation. No process. Nothing.

So I built the onboarding process myself.

That was 4 months ago.

Today every new person gets it on day one.

This is just what scaling looks like.

Our growth outpaced our systems.

But since I joined, we are catching up.

Amazing to build in such an environment.

Did you ever have a similar onboarding experience?

[Simon Jun @simonjun_]

@lukeredien 🙏

[Simon Jun @simonjun_]

@ClipsterKonne 🔥

[Simon Jun @simonjun_]

@clipsterfilip are you watching the game

[Simon Jun @simonjun_]

@lukeredien you'll also learn 10x faster there

[Simon Jun @simonjun_]

@clipsterfilip 700K for free, lol

[Simon Jun @simonjun_]

@ClipsterKonne @clipster why did it blow up like that?

[Simon Jun @simonjun_]

When I joined @clipster, creators and brands were coming in faster than the team could handle. Growth like that is really rare to see, and when you see it, you pay attention.

[Simon Jun @simonjun_]

@lukeredien sharing some life lessons. I like it @lukeredien