We rebuild apps made with AI tools until you can sell them.
Built with Lovable, Bolt, Replit, v0 or Cursor, and it works until you touch it? The screens are the cheap part, and the tool did them. A fleet of AI agents rebuilds the rest around the clock, supervised by Mykola, a senior engineer with 25 years building software. €4,900 a week. Stop after any week.
For the person holding an app that demos but can't be sold.
A pre-seed or seed founder with something built in Lovable, Bolt, Replit, v0 or Cursor, by them or a freelancer. Or a team inside a larger company, with a prototype for something new that now has to run for real.
Those tools are good at a first version and bad at a twelfth. They build whatever you ask on top of whatever is there, and nothing is ever removed. That is not a mistake you made.
- What you have demos but doesn't ship.One change breaks another, and nobody inside can say why.
- You know the domain better than any engineer you could hire.That is the half nobody can build for you, and the reason anyone will pay for the result.
- You have raised, you are selling, or a company is paying.This is not a small purchase.
- You already have something.Nobody comes here with only an idea. There is always an app, a prototype, or at least a spec. The tool was the right first step; this is the second.
Not for a website or phone app that is mostly screens, and not for an idea with nothing behind it. The tool does those well and cheaply: start there, or stay there.
The screens were never the problem.
The tool drew them, and drew them well. What it could not build is the layer under them, and that layer is the work.
The demo works because the screens work; any tool or agency draws those, cheaply. What the demo never shows is under them: two users at once, the thousandth record, 3 a.m. with nobody watching. An app built by a tool stops there, and more screens don't fix it. That layer is where Mykola has spent 25 years building software, and it is what a week buys.
- A million pages a day, and nobody on call.SignalsAPI, our own: 457 sources into thirty-odd services, and nobody whose job is to keep it running.
- Every change to a deal, recorded the moment it happens.KIMA, German real estate. It arrived on a spreadsheet doing the job of a database. Now the app moves on the record, and nobody has to remember a row.
- Calendars and travel time, turned into ranked slots.Ush, executive scheduling. It reads the calendars and the mailbox, ranks the slots with reasons, and drafts the email; a person sends it. Forty weeks bought, one at a time.
- Every claim in the papers, searchable in plain language.A research platform, Israel, for 15 PhDs. The answer is the quoted passage and the page it came from, not a paraphrase to trust.
None of these are screens. How each was built. If a website is what you need, the assessment says so in writing, and there is no week to buy.
An expert and the right tooling. Neither works alone.
Our own agents write the code, around the clock, on your project only. Nobody watches them type. The review is at the output: a senior engineer reads what survives, runs it on a clean machine, and tries to break it before you see it.
A fleet of agents, around the clock
Given room, an agent invents work that doesn't need doing, so the fleet runs and whatever comes back wrong is binned. Volume is cheap; judgement isn't.
A senior engineer in charge
Review is at the output, not the keystroke. He finds the one shape under your app, and agents fill a shape in; they don't find it. Today that is Mykola Vorobiov, who built the fleet after 25 years building software, on the layer under the screens.
Yours, from day one
The owner field on the repository is the proof, and anyone can verify it in a minute. Any developer can pick it up from the notes.
An agency shows a customer something in month two. Here, it's the first Friday.
Buying Photoshop does not make you a designer. A tool is only as good as the expert running it, and an expert is only as fast as the tools.
| Hire an engineer | Hire an agency | Buy an AI coding tool | Sellable Software | |
|---|---|---|---|---|
| What you get | One person | A team, on their schedule | A tool | A fleet of agents and an expert running them |
| Strongest at | Whatever they built last | Design and screens, then the rest | Screens, and a first version | Logic and data that run with nobody watching |
| Working on your app | Office hours, when not ill or away | Two-week sprints, after discovery | Whenever you drive it | Around the clock |
| Who decides what goes | Them, if they are senior | Their project manager | You | Mykola, a senior engineer |
| A customer sees something | Once they have ramped | Month two | Today, until you touch it | The first Friday |
| Starts | In three to four months | After the discovery phase | Today | Next Monday |
| Costs | A salary, plus the search | Discovery first, then a team's monthly bill | A subscription, plus your time | €4,900 a week, stop after any week |
| You end up with | It depends who you found | Production software, on their timeline | Something that works until you touch it | Something you can sell |
Hiring in-house has one real advantage this does not: the capability stays inside your company. If that is what you need, we say so.
One week at a time. Each version is built on the last.
Monday to Thursday
The fleet builds and tests. In week one, your app moves into your own accounts.
Thursday
A short recording of the week's work. Nothing to write up: the app is the brief.
Friday
One hour on a call. You decide what goes into the next week, or that there isn't one.
€4,900 a week. Stop after any week.
A week
- In euros, invoiced before the week starts, company to company
- Building, testing, hosting and security included
- No setup fee, no minimum, no notice to stop
- Repository and cloud accounts in your company's name from day one
The assessment, first
- Two days after we see your app, in writing
- Yes or no, and why
- What stays, what gets redone, what we would build first
- How many weeks, and what it will cost to run
- Comes off your first week
There is no total on this page, and that is not an omission. You buy a week at a time. The seven terms are on one page.
Questions people ask before they send it.
Do you own it?
Yes. Repository and cloud accounts in your company's name from day one. The owner field is the proof, and anyone can verify it in a minute.
Can you really stop after any week?
Yes. Say so on the Friday call. No notice, no fee. What you have that day works, and it keeps running in your account.
What if Mykola is ill or away?
The code, cloud accounts and data are in your company's name from day one. The docs are tested on a fresh machine by someone who didn't write them, architecture decisions are written down, and you pay a week at a time. The build keeps moving when Mykola is away. If illness costs you a paid week, the week moves or you get it back.
How many weeks does it take?
The assessment gives a number in writing, with what would change it. The longest client stayed 40 weeks, buying one week at a time, and could have stopped after any.
What do we need from you?
One hour a week, from someone who knows the business. Nobody technical, and no spec: you react to working software.
AI code got you here. Why is this different?
The tool adds whatever you ask on top of whatever is there. Here Mykola finds the one shape under your app and decides what goes. Agents fill a shape in; they don't find it.
Do you build websites or phone apps?
No. The tool does those well and cheaply, and so does any agency. The work here is the logic and data under the screens, where an app built by a tool stops.
What if it isn't worth rebuilding?
Then the assessment says so, in writing, in two days rather than in month four.
What happens after you stop?
It keeps running in your account. Anything needed later is a week, or a conversation about whether it is one. Nothing to subscribe to.
Where are you?
Fredrikstad, Norway, on CET: a full UK or European working day, and a US morning in your afternoon.
Show us what you have.
A link, a login, a file. Two days later you know, in writing, what we'd keep, what we'd redo, and how many weeks. Or book twenty minutes, free, and leave with the scope of the first version and how many weeks it takes. The rest follows once you start.