ABOUT US
A small engineering studio from Kraków.
Senior team. One project at a time. Hands-on, not advisory.
Oleksandr Kotliarov
Founder · Engineering Lead
Founders need a partner who works hands-on, not someone who shows up with a deck and leaves a memo. From an MVP at pre-seed to a delivery rebuild at Series A — the engineering challenges differ, but the operating posture doesn't.
I take one retainer client at a time, plus shorter audits and sprints alongside. That gives each engagement enough oxygen to actually ship — not just produce written recommendations.
Beyond me there are senior engineers, plus design and writing; the team is assembled against the engagement rather than fixed in advance, and names are available after NDA.
What I don't do: I'm not a label-based fractional CTO. I don't sit on board calls or write 40-page strategies. I don't sell AI hype. If a problem doesn't need an LLM, I'll say so.
— Oleksandr
Career record, roles, and selected work →Senior-only, assembled per engagement.
Names available after NDA. We don't list public team pages because most of the team works elsewhere full-time and joins us on focused engagements.
Oleksandr Kotliarov
Founder · Engineering Lead
Technical leadership and delivery
Senior Backend Engineer
Backend / Architecture
8 years · names available after NDA
Senior DevOps / SRE
Infrastructure / Observability
7 years · names available after NDA
Senior Frontend Engineer
Frontend / Product
6 years · names available after NDA
Designer
UX / Product design
Per project
Researcher / Writer
Content team
Part-time
Six operating principles.
1 · One project at a time
One retainer client at any moment, with audits and short sprints alongside. That gives each engagement enough hours to ship.
2 · Hands-on, not advisory
We work with code, processes, hires, and customers. Not with strategy decks.
3 · Senior-only team
Every engineer on a project has 5+ years in production. No junior staff augmentation.
4 · Outcome-anchored contracts
Fixed-fee on audits. Fixed-scope on sprints. Milestone billing on transformations. We write commitments we can defend.
5 · Written-first delivery
Weekly written updates and a monthly executive review on every engagement. If it isn't written down, it didn't happen.
6 · Honest no's
If we aren't the right team, we say so on the discovery call and recommend an alternative.
What we test for the next client.
Open-source contributions
Internal tools we use in delivery — review checklists, readiness templates — released publicly.
AI tooling research
Where LLMs actually help an engineering team and where they don't. Tested quarterly with client permission. Findings published in /writing.
Field data
Aggregated patterns from current engagements. Published as anonymized field notes.