Case study · 2024 — 2026 · 6 min read

The Design Factory. Productizing a freelance practice.

Two years inside a London-based design studio, shipping 15+ SaaS and brand projects through tight weekly review loops with the Creative Director. The interesting part wasn’t the screens — it was watching a pure-craft studio re-shape itself into something that could ship senior-grade work without burning the senior who was running it.

Role
Lead Product Designer (remote, full-time)
Timeline
March 2024 — February 2026
Team
Creative Director, 1 designer (me), 2 contracted developers
Industry
SaaS dashboards · Brand sites · Productized service
Surface
15+ shipped projects, weekly review cadence, London hours from Jakarta
Stack
Figma, Auto-Layout, Variables, Notion, Loom

Context

The Design Factory was a one-person studio running on word-of-mouth. Good projects, good clients, good craft — but the founder was the bottleneck, the brand, and the QA. Every project ended with the same private question: can this scale without becoming an agency?

I joined as the second pair of senior hands. The deal was simple: my job was to ship to the same standard the Creative Director would, on a clock that was eight hours behind mine.

Approach

Research moves

I spent the first two weeks doing nothing but reading shipped Figmas. Not active projects — finished ones. Looking for the silent style guide a studio always has but never writes down. Spacing rhythms, type ramps, the way components were named, where decisions were inconsistent. By week three I had a one-page document the CD agreed represented the studio’s actual taste.

Design moves

We turned that document into a working library. Not a marketing design system — a senior-output template. Components I could pull from on a SaaS dashboard at 9 AM Jakarta and the CD could review at 9 AM London without us needing to talk first. The library cut the average project review cycle from three rounds to one and a half.

Decisions

The key call was narrowing what we said yes to. Inbound was full of mid-sized brands wanting brand work. We doubled down on SaaS dashboards and B2B brand sites — work where the senior-output template made the math work. Lower top-line, higher repeat rate, much higher hourly. The studio became smaller and more profitable in the same year.

Senior-output template · Library overview
The library that made async hand-off work — a senior-grade template, not a marketing design system.
SaaS dashboard · One of fifteen
Representative SaaS dashboard. Auto-layout, variables, responsive constraints — built so a developer in London could ship without follow-up calls.
Brand site · Conversion-focused B2B
A B2B brand site built on the same library. Reused components, different voice — the productization paying off in real time.

Outcome

Two years, fifteen shipped projects. The studio went from one bottleneck to a two-person senior bench, and from project pricing that varied wildly to a packaged offer with a predictable margin. When I left in February 2026, the engagement template I’d helped write was being reused for the studio’s next senior hire.

15+ Shipped projects
−45% Average review cycles
2 Years remote, zero on-sites
8 hr Time-zone gap, async-first
A studio is a system that protects the senior’s taste from being spent on rework. If you can’t see the system, you are the system.

Reflection

What I’d do differently next time: write the offer document on day one, not day one-eighty. We had the pricing math working months before we had the words for it. Articulating the offer earlier would have closed faster.

What I’m proud of: the studio still ships in the same voice today, with a different senior in the seat. That’s the only test that matters for productization.

Next case study Avocado — self-custody crypto that feels like a banking app. Or jump to Abadikan — building the operating system for Indonesian SMEs.