Dmytro and Vitalii, the name, and how we work
We are two engineers. One leads teams and delivery, the other builds AI features end to end, and together we ship our own apps, each in under a month. We take on at most two clients at a time, build their products and put AI into their products and processes, and both of us work on each one. This page is about who we are, the name, and how working with us goes.
On the knee
Nakolini comes from the Ukrainian на коліні, on the knee. It's what you say about a thing made quickly and well, with what's at hand, by someone who knows the job. That's the tool we want to build for you: small, close to the person who uses it, and done.
Mostly in writing, with a call when it helps
Email or whichever messenger your team uses, a short call when a thread isn't enough, and a video call when that isn't either. One of us replies within one working day. Each day's work lands in your own accounts: the repository, the cloud, the tool's log.
Every invoice lists who worked which hours on what. Both of us know every system we build, and if one of us is away for more than a week, the other takes over.
Both of us work on every project
There is nobody else at Nakolini, so nobody else touches yours.
Dmytro Hryb
Engineer · delivery and teamsHas led engineering teams through the changes he now sells: reorganised them into small squads releasing every week or two, brought engineers into product decisions and moved manual QA into automated tests. At Nakolini he leads the diagnostic, the delivery changes and the release rhythm.
Vitalii Kikot
Engineer · AI features and automationBuilds AI features end to end, from the model call to the screen. In Anonimo the face model runs on the phone and nothing leaves it; in Expenny receipts and voice notes reach the model with personal data removed first. He works in front-end and iOS, deep in React Native. At Nakolini he builds the tools and the product features.
Whose hours go where
A tool for one routine takes 10 h a week of our time, split by name in the contract. With an engineering team we design the change and lead it, about 10 h a week between us, and your engineers do the hands-on work, so the skills stay when we leave. A first version of a product gets 30 h a week, and we write the code ourselves, one build at a time.
Before we start, the contract says whose time we need from your side. For a tool that's the person who does the routine, for about an hour a day in the first week. For a pilot it's usually the team lead for 2 h a week and one engineer one day a week on test automation.
Your contract, and our limit
Our contract with you assigns everything we write for you to you; the small library our tools share stays ours, and you get a permanent licence to it at no charge. We never work for a direct competitor of a current client.
We take at most two active engagements at a time, and a product build counts as both. Care plans after a handover are separate, and outages on them get a reply within one working day. Until then the tool's switch sends every case back to your people, and the work carries on without us.
Write to us.
Say what you want built, or which job you want handed to a model, and what you run it on. We both read it, and if we're not the right people we'll say so on the first call.