ABOUT
I'm Niko.
I build agentic systems that run organic search and ship custom AI to production — alone, with agents, from Turku. Two kids, one golden retriever, and an unreasonable interest in how to get a working pipeline to do a team's worth of output.
WHY
Agents give me the only thing money cannot.
I have two kids and a five-year-old golden retriever named Viima. The reason I run a one-operator practice — and the reason I have spent the last two years rebuilding every part of my workflow on top of agents — is dinner at six and the dog walked before dark.
Agents are not a parlour trick to me. They are the only honest way I have found to do the volume of work a serious B2B client deserves, on a schedule that does not eat the parts of life that matter. Every system I build for a client is a system I would happily run myself.
If you are reading this and you also want a serious practice without a 60-hour week, we will get along.
- focus hours
- 09–15 EET, Mon–Thu
- walks
- before sunset, with Viima
- dinner
- 18:00, non-negotiable
- weekends
- offline · agents on duty
- oncall
- only for prod incidents
HOW I WORK
Six beliefs I work from.
Receipts over promises.
I will not tell you what I think your traffic could be. I show you what the system did last quarter, in screenshots, and we talk from there.
One operator is the feature.
No account manager, no juniors, no creative director. You get the person doing the work on every call. Agents handle the volume.
The brief is the work.
A bad brief produces a bad system. I spend a full week on the brief. Everything after that is execution.
Honest disagreement.
If your strategy is wrong, you hear it on the intro call. Cheaper for both of us than two months of trying.
One build at a time.
I take a single custom-AI client at a time. The retainer side runs in parallel, but builds get a closed window. That is how they ship in two weeks.
Async-default.
Weekly written updates, Loom walkthroughs, Slack on a 24h SLA. Calls only when the decision needs them.
WHAT I'M BUILDING
niko-os — the agent stack I run my practice on.
niko-os is the operating layer I built for myself: a small fleet of named agents — Olivia leads, Hugo runs customer ops, Lex writes, Linker handles internal linking, Scribe crawls, Ada engineers, Ledger does the books. Each one has its own model, its own tools, its own knowledge.
I sit at the operator desk and route work. The agents pick it up, run it, and surface only the decisions that actually need me. It is the same pattern I install at every retainer client — just compounded against my own practice.
Right now it runs 12 agents across 30+ clients. Built on Bun, Hono, Drizzle, Postgres, and pgvector, with the Claude Agent SDK underneath. Not for sale — it is my private edge — but the patterns are in every system I ship to you.
STACK
What I actually use.
- gpt-5.1
- Claude 4.5 Opus
- Whisper-3
- Custom rubric evals
- Inngest
- Postgres
- TypeScript
- n8n where it fits
- Schema.org
- Sitemap automation
- Internal-link agent
- Daily SERP scrape
- Linear
- Slack
- Loom for digests
- Notion for SOPs
READING ROOM
Who I read.
On building from first principles and the tokenizer-up view of LLMs.
On what these models actually understand and where the floor is.
On scaling laws and where the next jump comes from.
For the contrarian read — keeps me from getting too comfortable.
Released the day they ship. Half my prompts are screenshots of changelogs.
Where the search-side ground truth still lives in 2026.
CV