Working solo: when (and how) to bring others in
Founder-led isn't a marketing pose — it's a real constraint. Here's where the constraint bends, and the actual names of the contractors who get brought in: Lalə M., Bəxtiyar M., Aydan Ə.
“Founder-led” reads well on a site. It signals that one person is responsible, one person answers the email, one person ships the work. But once you’re inside the work, the phrase shows up two ways: as a real operational constraint, and as a marketing pose.
The difference is visible: a real founder-led studio writes its constraint down. A pose-led studio hides it.
What my actual constraint is
Qaynaq is a one-person studio. I, Elvin, do the bulk of the design and engineering. Every page on this site, the audit pipeline, the case study writeups — all of it goes through my hands. That’s a structural choice, not a marketing detail.
But “solo” is not absolute. There are three concrete situations where I bring someone else in. The three situations are written down — somewhere different from the AI-restraint document I wrote about earlier, but the same mechanic: explicit, in advance.
Trigger 1 — the capability isn’t mine
The clearest case. Some work isn’t in my domain, and doesn’t need to be.
Concrete examples:
- 3D / motion — when a case study calls for it, I bring in Bəxtiyar M. He’s one of the few people in Baku doing real-time motion and commercial 3D at the level the work needs. His credit goes on the case study; partners see the name.
- Local-flavour AZ illustration — when a brand identity needs distinctive illustrative output, Lalə M. is the partner. Her illustration sits in contemporary AZ language — modern, not pseudo-historical, which is the local default failure mode.
- Multilingual brand voice — for AZ + EN + RU copy that has to land natively in all three, I sometimes work with Aydan Ə. She’s one of the few people I’ve found who can hold all three voices without one of them collapsing into translation.
These aren’t fictional names. Real people, real work, signed credits on every case study they touch. Partners know who did what.
Why naming matters: in the Azerbaijani market, the word “agency” routinely hides a chain of subcontractors. The partner pays the agency a high rate, and a freelancer at half the rate does the actual work — the partner never sees the substitution. I refuse the convention. If Lalə M. did the work, the case study says Lalə M. did the work.
Trigger 2 — timeline I can’t ship alone
Second case: the partner needs the work in less time than I can carry alone.
The written rule for this case: if I genuinely can’t hold the timeline, I tell the partner first. The options are:
- Extend the timeline — if the partner is flexible, we widen the window and I ship solo.
- Trim the scope — push some elements into a later phase.
- Bring in a contractor — when timing is non-negotiable.
In the third case, the contractor’s name and hourly rate go in the contract appendix. The partner won’t see it on the headline page, but the appendix is explicit: “this stage involves Lalə M. at 60 AZN/hour for 24 hours.” I add a margin on top, and the margin is also written.
This is not a “we” hiding where the money goes. It’s an open supply chain. Rare in the industry, but the only honest path for long partnerships.
Trigger 3 — conflict of interest needs a second voice
The third trigger is the thinnest, and the most important. Some decisions put a doubt against my own judgment, and a second professional voice needs to be in the room.
Examples:
- Senior code review — I’ve been an engineer, but on large product surfaces some calls deserve a second senior. A backend engineer I’ve known for years runs review on those.
- Complex brand-position questions — even when I’m sure of my answer, sometimes the partner’s sector is too specific. I bring in a sector strategist for short consults. Often combined with Aydan Ə. to triangulate the brand voice and reference works.
- Legal questions — never me writing. Outside legal handles it; I present back to the partner. Legal services are billed separately.
The third trigger matters most because it addresses the biggest weakness of the founder-led model: a single person can’t see their own judgment errors without a second voice. Avoiding the echo chamber needs deliberate structure.
”Why not just hire a team?”
Asked routinely. Two-part answer.
Part one: team-building has its own dynamic. With three to five people, project quality depends on team dynamics — who reports to whom, who decides what, where the seams are. Managing that is its own skill, and it’s not my primary skill.
Part two: the partner sees the difference. With one person, the partner knows who they hired. With a team, you get the relay race — discovery with one person, design with another, build with a third. The relay is expensive and weakens over each handoff.
Consequence: Qaynaq doesn’t take nine projects. Qaynaq takes three or four, goes deep on each, and my name is on the final result. That caps growth, but I treat the cap as a feature.
Why this matters in the local context
In Azerbaijan, “agency” is more or less synonymous with hidden contractor chains. The partner pays 10K AZN, the agency hands a 4K AZN freelancer the work, and the partner accepts the result thinking it’s “the agency’s.” That structure is a value gap on the partner side — they don’t actually know who they paid.
The founder-led model closes this gap, but only if you keep the contractor cases visible. If Lalə M. worked on the project, “Lalə M. worked on it” is on the page. If Aydan Ə. wrote the brand voice, “Aydan Ə. wrote it” is on the page. The partner sees where the money went, and that creates a different kind of trust — one the word “agency” doesn’t reach.
Don’t blur the triggers
A note: these three triggers don’t get mixed. “I don’t have time” doesn’t auto-trigger a contractor — first I talk to the partner about timeline and scope. “I want a second voice” doesn’t auto-trigger a contractor — first I write down why my own judgment is wavering. Each trigger has its own rule, because if the triggers blur, “founder-led” turns back into a marketing pose.
How to ask about it
In a discovery conversation, partners often ask: “how many people will work on this?” My answer is consistent: I run the core work with you. Specific specialised stages bring in named contractors. The contract appendix lists who, how many hours, at what rate.
That answer is mundane on paper, but in the local market it tends to surprise — partners aren’t used to this level of specificity. Most of the partners I’ve signed have signed because of this directness, not in spite of it.
If you run a one-person studio and want to argue this differently, write me: salam@qaynaq.com.