1,000,000company pages a day, nobody on duty
Runs while nobody watches.
Fetched, cleaned and served through one API.
SignalsAPI, own product
Paid per version stop after any of them
An idea is enough. Running by the first Friday, and yours from day one.
The screens, the data, the AI, the servers, the connections to your other systems. I decide what gets built. AI models write the code, and I check everything that comes back. Tested, demoed and deployed: something new running every week.
app.yourcompany.com
Weeks
✓Week 1 running
✓Week 2 running
●Week 3 this week
·Week 4 next week
Week 3 of version 1 is runningDemo video, 6 min
Built this week
- Every source imported overnight, duplicates removed
- Search across all your documents, cited to the page
Still working from week two
- The first screens, now on the new data
If there is a version 2
The reminder emails your users asked for.
Nothing to cancel. Code and cloud accounts are already yours.
Six systems, each written up the same way.
- KIMAGermany
- UshUnited Kingdom
- Research platformIsrael
- SignalsAPIown product
- Virtual BDRown product
- Volkswagen HR insightsGermany
No spec needed. Start from what you have.
A vibe-coded system that works half the timeIt hit the ceiling of the tool that wrote it.
An idea, and nothing built yetThe domain, a direction, and money behind it.
A pipeline that only runs on one laptopGood work, days per run, one user.
The whole product, not the part that demos.
Screens are the easy part to vibe-code, and they break as easily as anything under them. I build all of it, with tests, demos and deployment.
Schematic — shape only
No discovery phase. You react to working software.
The spec comes out of the work, checked against real data, real calendars, real load.
CRMadapterqueue
your rulesqueueCRM
+ next CRMadapternothing else changes
The next CRM is one adapter.
Queues and adapters. New features plug in without touching what works.
KIMA, Germany
Tue 10:00, Shoreditch94%8 min from the 9:00. No wait before the 11:30.
Tue 14:30, Soho71%32 min travel. Usually declined after lunch.
Thu 09:00, remote58%Thursday mornings are kept free.
Ranks the options, and says why.
Calendars, mail, travel time, the habits nobody wrote down. A person sends.
Ush, United Kingdom
Runs for a team, not one laptop.
Fifteen scientists, one platform: a shared store, and compute that comes up for a run and shuts down after. What one builds, the rest use the same day.
Research platform, Israel
Your cloud account
Your own servers
A machine with no internet
Runs where you say.
The AI model is installed there, not called over the web. Never on my servers, and it keeps running after you stop.
Yours from the first commit.
Code and cloud accounts in your company’s name. The handover is rehearsed in version 1, not promised for the end.
An agency shows a customer something in month two. I show it on the first Friday.
When a customer first sees something running
Each version here is built on the last. Nothing starts over. Schematic — shape only
“Nothing else breaks.”
“We ask Codex to build another feature and it just does it, out of the box. Nothing else breaks. That’s how we knew the architecture was right.”
K
KIMADeal management for real-estate firms, Germany. Arrived with a Codex-built repo that half worked, and nobody knew which half.
10 wksfrom a repo that half worked to one their own tool extends
40 wksUsh bought one week at a time, and could have stopped after any
15 PhDson one platform, no engineers, deploying their own tools
For teams with an idea, the domain and the money behind it.
The smallest client so far was three people: an investor, a manager and the domain expert. Others are larger companies starting something new.
- ✓You have an idea, or something half-built.
Shaping the idea is part of the work. Half-built means screens that demo but don’t ship, a process on a spreadsheet, or data for something new.
- ✓You know the domain better than any engineer you could hire.
That is the half nobody can build for you.
- ✓There is money behind it.
You have raised, you are selling, or the company is paying.
All three true? This is for you.
A version is a week of scoped work. The first is one to four.
$5,600CAD $7,900£4,200€4,900*a week
Where is your company?
Prices in USDCADGBPEUR ·
- ✓No setup fee, nothing to cancel, minimum one version
- ✓A written definition of done, agreed before work starts
- ✓Every architecture call dated, with the alternative that lost
- ✓A demo video the day before each weekly call
*Per week. How long version 1 runs is agreed on the scoping call.
Not for you if you want a demo that only has to look right: then vibe-code it. Nor if you want a fixed quote against a frozen spec.
Full price and terms, compared against a freelancer, an agency and hiring in-house.
Twenty minutes with me, and you’ll know what I’d build first.
- The call
Free, twenty minutes, with me, Mykola. Describe what should exist, or show me what you have. No deck, no proposal.
- Four answers
What is buildable, what I’d build first, what is hardest, and what I’d talk you out of. Some ideas shouldn’t be built. You hear it on the call, not in month four.
- The first week
Starts the week after the call. Your side is one call a week. After each version, you decide whether there is another.
Whoever scopes it is on every weekly call. That’s me.
Mykola VorobiovThe engineer who does the work. Fredrikstad, Norway.
Or write: [email protected]
Or write: [email protected]
Or write instead
I read these and reply within a working day.
If this was forwarded to you as the engineer, start at how it runs.