Leadership
We Didn't Hire More Designers. We Built Them a Shortcut.
Two brand designers who had never opened a terminal built the self-service hub every new hire now meets in week one.
Haim Repael · 2 min read

STAR AT A GLANCE
- Situation
- The design team kept answering the same internal requests, and engineering time for a self-service tool never came, for good reasons.
- Task
- Turn a recurring cost into a one-time investment, without new headcount.
- Action
- Taught two brand designers to build with AI coding agents in working sessions on our own problem.
- Result
- The Design Hub launched company-wide and every new hire meets it in their first week, built by the same team that existed before.
Where's the presentation template? Can you make me an email signature? What are our brand colors? Do we have a Zoom background? Can you make my deck look more "us"?
None of that is design work. All of it eats design time.
SituationThe right "no", over and over
Every design team I know answers the same five requests, again and again, from people who aren't designers and don't need to be.
I could see the pattern clearly and could do nothing about it. Every time I asked for engineering time to build a self-service tool, the answer was the same, and it was the right answer: there were bigger fires. An internal branded-asset tool was never going to beat a customer-facing bug or a roadmap commitment. I understood the math. I just didn't accept the outcome.
TaskChange what the resource needed to be
I stopped asking for the resource and changed the question. Could the people already in the room build this themselves, safely, between their real deadlines?
ActionWorking sessions, not a course
By the time AI-assisted coding was good enough to trust with real internal tooling, I had two brand designers who had never opened a terminal. I sat with them and taught them what a repository is, how a pull request works, how to prompt a coding agent and read what it gives back, and where the line is between "this works" and "this is safe to ship."
Not a course. Working sessions, on our own problem, on their own hours between real deadlines.
What we built together became the Design Hub:
- An email-signature studio people actually use on their own
- Every logo, in every size, color and format, in one place
- Presentation and document templates, and a bank of photography
- An AI Design Partner that reviews a Google Slides deck and tells you what's off-brand before you present it
- An avatar generator for people who wanted a drawn version of themselves for internal tools
ResultSame team, new skill
The Design Hub launched company-wide. Every new hire meets it in their first week, before they meet half the people they'll work with.
I never got the headcount, and I never got the small internal-tool resourcing I originally asked for. The team that built the Hub is the same brand team that existed before it, doing the same job, now with a skill nobody had budgeted for, and a tool nobody had to be talked into using, because it was built by the people who'd feel its absence first.
What travels
The Design Hub is not an AI showcase. It's an operating decision: convert a recurring cost into a one-time investment, using the people already in the room. The requests never slow down on their own.
If you're waiting for headcount to fix your team's version of this, ask a different question first: what does your team already know how to do that they don't yet think of as a tool?