How we work
One contained piece of work to start, the same engineers for as long as it is useful, and a direct line to the people doing the work.
Working together
One platform, one module, one problem.
Scoped and priced up front for a defined piece of work, with response times agreed in writing. The easiest way to find out how we work.
Datacolor started here in March 2024: support for one app. Four months later we ran its whole mobile portfolio.
Software that needs a team, long term.
A product owner, developers, QA and design inside your organization, on a monthly basis, for as long as the work is there. Our product owner works with you and, when you want, directly with your stakeholders.
Minerva University: three developers and a product owner, seven years and counting.
You have a team; it needs more senior hands.
One or two of our senior engineers join your stand-ups, your repositories and your roadmap, and stay. Same people, not a rotating bench.
Two US companies run part of their engineering this way with us today.
Whichever way you start, the goal is the same: the same people on your software for years.
The first 30 days
A half-day or more with your product owner and whoever knows the system best. We leave with access, context and an honest list of what is actually broken, or of what to build from scratch.
Repositories, environments, app stores, monitoring. By the end of the week a first fix is ready for review, so both sides see how the other works.
A backlog you can read, a release cadence that suits your team, and regular check-ins with whoever owns the product.
A release in your users’ hands and a plain review of the month: what went well, what we found, what we would do next. Then you decide.
What you can count on
The engineers who start on your work are the ones still on it in year three. Our average tenure is four years.
You work with one product or project manager on our side and with the engineers doing the work. In the first weeks Antanas, who runs Vilantis, joins too, then hands over to a senior engineer.
We always work with AI coding tools. A senior engineer still reviews every change before it ships.
Every engagement starts under an NDA, and we work in your code repositories and cloud accounts, so nothing important is locked away with us.
Fit
Your business runs on software you build, and the roadmap goes past the next release.
Someone on your side owns the product: a product manager, a product owner or a CTO.
You want the same people on your software for years, not a new vendor every project.
You are happy to start with one problem and grow from there.
A one-off build with nothing planned after it.
You need fifty engineers next month.
Nobody on your side can make product decisions.
The lowest hourly rate is the main criterion.
Not sure? Tell us what is on your roadmap for the next year, and we will say honestly whether we are the right team for it.
Tell us about itStack and tools
We always work with Claude Code, Codex and OpenCode. They make us faster; senior engineers still own every line that ships.
Does your company restrict AI tools? Then we work with the ones you provide, or with our own VAIOS setup, where your code and data do not leave our Azure account.
Languages and frameworks matter less than they used to. What matters is who is accountable for the result, and whether they are still there next year.
Location and hours
We're in Vilnius, Lithuania. Our working day overlaps the whole European day and US Eastern hours until noon, and calls in US hours are normal for us. We agree the rhythm with each client at kick-off: stand-ups, reviews, and how to reach us when something is urgent.
Working from Europe? We share your whole working day.
What is on your team's plate for the next year? Tell us, and we will say honestly whether we are the right team for it.
Tell us about your roadmap