case-studies / jan-lafko
Case Study: Jan Lafko — From First Container to Sold Work
The best evidence a workflow works is what someone else does with it when you are not watching.
Jan Lafko, 22, an independent developer in Europe, took the Turbo Flow workflow from a blank machine to a paying client project — and then made the tooling better.
The pull quote
If I had just taken naked Claude Code on my Windows machine, I would not be where I am right now. Full stop.— Jan Lafko
Where he started
Jan found the workflow through the agentic coding community and went all in: "I am 22, and this is the first real thing I have gotten into. Properly, all the way in." His first container — a 600+ agent environment — was, in his words, "a real tough battle, the kind you only fight because you genuinely want to".
What made the difference was not the agents; it was the structure around them. Working in isolation, planning before building, verifying before deploying: "If I were doing my agentic development in a non-isolated environment, I would be cooked by now."
The work: a Gore-Tex company website
His project: a website for a Gore-Tex company, built on the Medusa open-source e-commerce backend. His sequence once the workflow clicked:
Plan → Research → PRD → ADRs → Swarm the rest
When a new Node version broke the build, the discipline held: a fresh worktree, Docker-in-Docker with the Railway CLI, testing against the previous container, deploying from the isolated branch — the failure contained by the environment instead of spreading through it.
He ran the project as a 12-day sprint with the AI task system, planning day by day for himself and the agents. The site sold for what he describes as a very lucrative sum — which, as he notes, he immediately spent on AI tokens.
The contribution: tf-verify
Then he gave back. tf-verify is his shell program: 220 quality gates checking the whole agentic container, not just the end of a build — one command, one check per gate, and when a gate trips you fix the underlying setup instead of adding an exception. He wrote it for Turbo Flow 4.0 to prove the stack was wired end to end, and donated it to the project:
I donated it because it is exactly what I would have killed for when I was fighting to get my first container up.— Jan Lafko
What the case proves
Not that the workflow is magic — that it is learnable. A motivated developer with no enterprise budget went from zero to paid delivery, and the parts he valued most were the boring ones: isolation, planning, verification, gates. That is the same shape as team onboarding, and the environment is Turbo Flow.
Talk it through with someone who runs this stack on his own systems every day.