PEOPLE
WHO YOU
WORK WITH.
Two founders, no layer in between. The person who scopes your project is the person accountable for it, and you will know both of us by name before the first invoice.
Oleksii Hashkov
Founder & CEO
Engineer first, founder second.
Oleksii has been building for the web since 2015 and has not stopped writing code since - which is the part most agency founders quietly drop. He came to software the long way round: a first master's in power engineering, five years running a telecom infrastructure business, then a second master's in computer science at Kharkiv Polytechnic. That order matters. He learned how systems fail in the physical world before he learned how they fail in JavaScript.
What started as solo delivery on Upwork became a studio with a client list across five markets - the UK, the USA, Australia, Germany and Spain. Along the way the work moved up the stack: from front-end contracts, to full product delivery, to the architecture calls that decide whether a platform survives its second year. Enterprise clients arrive with the hard version of the problem - legacy systems that cannot go down, compliance that cannot be hand-waved, stakeholders who have been promised this before.
He now runs Smart-AI as the technical counterpart to a sales conversation: the person on the call who will tell you when a feature is not worth building, price the thing you actually need, and then stay on the project until the numbers move. Discovery, architecture and the final quality gate are his signature, not a delegated task.
TRACK RECORD
- building since
- 2015
- markets delivered in
- UK · US · AU · DE · ES
- education
- MSc Computer Science
- languages
- EN · ES · UA · RU
OWNS
- Architecture & technical strategy
- AI delivery and automation design
- Scoping, estimates and the fixed price
- Final quality gate before release
Roman Kryvda
Co-founder & COO
The reason your project has a rhythm.
Roman came out of a military university, and it shows in the best way: he thinks in structure, sequence and accountability. Where a project has moving parts, dependencies and people in four time zones, he is the one who turns that into a plan somebody can actually follow - and then holds the plan to it.
His background is in the projects most teams decline. Computer vision systems, where the output has to be right rather than merely plausible. Sports technology, where the deadline is a fixture list and does not move. Reporting platforms, where a number that is wrong is worse than a number that is missing. Complex is not a warning label for him; it is the reason he takes the work.
In practice, he is the founder you speak to most. He walks you through the process before it starts, keeps the weekly demo honest, and puts the closing report in your hands - the one with the metric, the before and the after. If a project is going to slip, you will hear it from Roman early, with a revised plan attached.
TRACK RECORD
- background
- Military university
- domains
- Computer vision · sport · reporting
- owns
- Delivery & operations
- you will meet him
- Week one
OWNS
- Delivery process and weekly demos
- Reporting and before/after numbers
- Resourcing and timelines
- Risk, escalation and change control
THE TEAM BEHIND US
Everyone who touches a Smart-AI project is a senior. Not as a line on an invoice - as the kind of engineer who reads an unfamiliar system for two days before changing a line of it, maps what depends on what, and then tells you the order the work has to happen in. In systems with real dependencies, the sequence is the hard part. The code rarely is.
They do not take tickets and ship them. They ask what the thing is actually for, say so when a simpler solution exists, and argue for it - including when arguing makes the project smaller. That habit has cost us revenue and kept us clients for years.
DISCIPLINES ON THE BENCH
Frontend
React and Next.js built to survive a redesign, not just a launch.
Backend
Node, Nest and Python. APIs that stay boring under load.
AI engineering
Agents, RAG and evaluation - grounded in your data, with guardrails.
QA
Automated and manual. The defects your users would have found first.
UI/UX design
Interfaces mapped to behaviour, handed over as a system, not a picture.
DevOps
Pipelines, environments, monitoring. Deploys stop being events.
Project management
Scope, sequence, and a weekly demo that tells the truth.
Business analysis
The requirements nobody wrote down, found before they cost a sprint.
/01
One working day, not two
Four countries inside a single time-zone band, CET to CET+1. Nothing waits overnight for a handoff, and a question asked at 10:00 is answered before lunch - including from the UK and Germany.
/02
The same people, project after project
Most of this team has worked together for years and across many projects. You feel that as continuity: nobody re-learns your domain on your budget, and whoever built a feature two years ago is still the person who knows why it works that way.
/03
Depth, not just delivery
A team that only executes gives you exactly what you specified. This one gets far enough into your business to tell you when what you specified is not what you need - and brings the cheaper, sturdier version instead.
WHO YOU TALK TO, AND WHEN
| Stage | Who | What happens |
|---|---|---|
| Free audit & first call | Oleksii | Scope, feasibility, what the numbers could realistically be. |
| Plan & fixed price | Both | One writes the architecture, the other writes the schedule. |
| Weekly delivery | Roman | Demos, blockers, the plan against reality. |
| Release & report | Both | Quality gate, then the metric-before-after report. |