Start from an idea, a mockup, a prototype, or a system that is online but not ready. We make it production grade: a first version real users can sign up for in one to four weeks. Then a new version every week, from what they say.
Prototyping with Lovable, Codex or Cursor? Keep going. Not? Fine too. We work in your GitHub and answer in your Slack.
In two days, in writing: the scope of the first version, and how many weeks it takes. The rest follows once you start. Ready to forward to whoever else signs.
Helps, if you have it: a link, a repo, mockups, docs, a few lines. Nothing written down is fine.
Goes straight to Mykola. Rather talk? Twenty minutes on a call does the same.
The same offer, read two ways. Take the one that is yours.
You have a product that cannot take real users yet — whoever built it. What you get, what it costs, how it runs, and who else we have done it for: that is this page, top to bottom.
You have to review it before it can be bought: how the work is bought, the standard every version is graded against, IP, data handling, liability, and who signs. The master agreement is sent on request before any signature.
Every way across the gap is too thin for users, or too slow for them.
Six months of calendar, two ways. Red is users waiting. Green is users having it.
In your Slack. Reads what you have, listens to your users, signs off every version.
Writes, tests, documents, deploys. Team output, one hire's price.
Scope is set every Monday from what users said on Friday. Agencies can't afford that. We can.
What we find in week one, whoever built it.
The fix: one core every feature runs through, tests on every change. Your screens stay. Then the checks outside your code: an app that signs users in with Google, or reads their mail or calendar, has to pass Google’s review before real users can use it, and Google is stricter now that so much is vibe-coded. The complete guide to what that takes.
What “proper” means on this page.
The acceptance test: real users sign up, use it, and nothing falls over.
You decide. We collect feedback, propose, build, and hand you a version. Every week.
From you, or straight from your users. Who stays, who leaves, what they ask for.
What users liked, what they didn't, what to build next. You approve or redirect.
Through the core, with tests, in your cloud. A tweak or a pivot, live within the week.
Live, tested, documented, demoed. Ready for new users.
Six founders in twelve months, across the UK, the US, Germany, Switzerland and Israel. Six client products, plus two of our own. The longest client stayed 40 weeks, buying one week at a time, and could have stopped after any.
Fixed price per version, scoped and itemized before it starts: you see exactly what is included and what is not. Nothing to hire, nothing to manage.
A version takes a week, unless you want us to go slower or need more time to prepare the inputs. A first version: one to four of these. A full rebuild: about ten. Three weeks: €14,700.
Questions and small requests, by the day.
Monitoring, updates, patches, a monthly check on the core.
Send what you have, or twenty minutes on a call. Then one demo a week, and your feedback.
Yours. Your cloud, your GitHub, documented, with handover notes. Scoped one week at a time, so you can stop any Friday. The contract says so.
Mykola. He reads what you send, answers in your Slack, and signs off every version.
Five questions, answered in the words we use on the call.
We're not an agency and not a freelancer. You get a senior engineer in your Slack with an agentic team behind him, working in your GitHub. The software is yours as it lands — we don't take your product away.
€4,900 a version. €1,200 a day at the Slack desk. Once you're live, 7% of build hours a month for maintenance.
One Slack channel — everything lives in it, no standups. Every version is tagged, demoed and comes with a changelog, and your feedback sets the next one's scope.
Your company is responsible for the software it owns and runs, exactly as it would be if it had been built by an agency you hired or by engineers on your own payroll. We are responsible for doing the work to the delivery standard, with reasonable skill and care — and for fixing it at our cost if it does not.
The build keeps moving when Mykola is away. The code, the cloud accounts and the data are in your name from day one. The docs are tested on a fresh machine by someone who didn't write them, and architecture decisions are written down. You pay a week at a time. If illness costs you a paid week, the week moves or you get it back.
The scope of the first version, and how many weeks it takes. Two questions at the top, or a call.