If Edicek raised money tomorrow, I already know the first two people I'd hire. One for marketing. One for video.
Not a developer. The product is the part I can carry myself. Marketing and video are where one person runs out of hours first.
And neither of them would start from a blank page.
On day one they'd get the brand. The colors, the Figtree font, the logo and the paper cut-out style, all of it public at edicek.com/brand.
They'd get the illustrations as a system, not as a folder of files. Ten kinds of pictures, from a changelog entry to a YouTube thumbnail to an email icon, and each kind has its own written rules.
They'd get the video tool I built with Claude Code. Its newest scene is 17 seconds of the old browser extension turning into the new one, and the post about that launch shows how both the pictures and the videos get made.
And they'd get the history. Everything I decided about Edicek is written down in files an AI model can read: 17 guidelines, from how a changelog entry should sound to how a video script is built, 47 commands for the jobs that repeat, and a knowledge file that's almost 2,000 lines long. On their first day they could ask an AI how a changelog entry should read and get my answer, not a generic one.
A good hire would onboard themselves. They'd open the repository in Claude Code and ask what we do, why we do it and what they could take off my shoulders. Then they'd keep asking until everything is clear. If something is missing, they'd ask me and then update the repository, so the answer is there for whoever asks next. Almost everything is already in those files, and I couldn't tell them much more myself.
That also makes it a good test of fit. A missing detail is normal. But if they need me to explain what we do, why, and what they could take off my shoulders, then either I made a mistake and I'm not ready for them yet, or I need someone with more expertise and they're not the right fit.
If they're the real thing, people with a track record at a level I've never reached, I'd let them lead. I'm not going to hire someone that good and then make them follow my checklists.
But I'd want them to build on top of this, not next to it. A new marketer shouldn't spend the first month finding out what Edicek looks and sounds like. That part is answered. Their time should go into the things I can't do alone.
The funny part is why any of this exists. I didn't build it for a future team. I built it because I couldn't afford one. My last project stalled because its product came from people I paid and couldn't steer. They were building the system for me, not the other way round. So Edicek had to work with just me. Every job that repeats became a system.
This time the system is already there, and whoever I hire first plugs into it on day one.
