Your prototype looks like it works. Your first customer will find out it doesn't.
Version a Week turns prototypes and ideas into production software that your first ten customers can actually use. A version takes a week and costs €4,990. It ships deployed on your domain, secured, tested, documented, and yours.
Six founders in the last twelve months, in the UK, Germany and Israel. Engagements from ten weeks to ten months.
The two ways founders build today, and what goes wrong
Prompt it, or pay someone €500 to
Lovable, Claude Code, Codex, or an Upwork freelancer running the same prompt. Fast, cheap, and it looks like it works.
Then a real user signs up. Login fails open, data sits in the wrong place, the second customer can see the first one's records, and the demo never becomes a product. Doors and walls built after the house is already full.
Hire an agency
A discovery call, then a forty-page proposal that admits they understood nothing and asks for six people and two years.
What ships is obsolete on arrival, every change is a change request, and you've spent your runway before your first customer.
Version a Week
A fixed unit of work you can actually buy: scoped in writing, priced before you commit, delivered in about a week, live on your domain.
What an in-house team ships in six weeks, in one. When the first version works, buy the next.
What a version is
Think of your product as a building your customers will live in. Each version adds structure, in the order that lets you sell early and still scale later.
Version 1: works for one customer
Single-tenant. Not scalable yet, and it doesn't need to be. One real customer gets the value you promised, which is the moment your investor conversation changes.
Version 2: works for many
Multi-tenant. Registration, login, and every customer's data walled off from every other customer's. You onboard the first ten yourself.
Version 3: scales with spend
An architecture that grows by paying for infrastructure, not by rebuilding. Customer 100 or 10,000 is a hosting bill, not a rewrite.
Version 4 and on: features
Every further version is the same unit: a week, €4,990, a scope you approved. Stop whenever you like.
Every version ships with
This is the part a prompt skips, and the part your first customer will test.
- A live URL on your domain, not a file on someone's laptop or a link inside a chat
- Registration, login and permissions that fail closed
- Customer data stored properly and kept separate per customer
- A security and compliance baseline
- Automated tests and documentation
- A plain-language walkthrough, so you can explain what you own to a customer, an investor or a future CTO
- The code and the IP, in accounts you own
How it works
Scoping call
You tell us what the product must do for the first customer. We ask the questions an agency would turn into a proposal.
Written scope, within two days
What version one does, what it doesn't, and the price. You approve it or change it. Most founders approve the first one or two and then trust the process.
Version, within a week
A working version on your domain, plus a walkthrough call so you understand what shipped and why.
Your call
Book the next version, pause, or hand everything to an in-house team. No retainer, no lock-in.
Investors used to fund an MVP. Now they ask who is already paying you.
Anyone can prompt a prototype, so a prototype proves nothing. What earns the meeting is a product with a few real customers in it, and the only way to have real customers is software that survives them.
Version a Week builds the layer between your prototype and your first ten customers, so you walk into the room with traction instead of a demo.
Who this is for
Founders we work best with
- You know your market deeply: an ex-consultant, an operator, a scientist
- You're backed by private money, whether your own, a family office, an angel or a partner, and your round isn't public yet
- You're non-technical and would like to stay that way for now
- You have a prototype, a deck, a design file, or just a clear idea
- You want a customer using the product this quarter, and a raise after
Probably not for you if
- You need a demo for a pitch and nothing more. Prompt it; that's what prompting is for
- You already have an engineering team
- You want a fixed eighteen-month specification. That's an agency job
Agents do the typing. An engineer answers for what ships.
Version a Week is Mykola Vorobiov and a fleet of coding agents he built and operates. The speed comes from the agents. The reliability comes from an engineer who spent years building and running outsourced product teams for British, German and Norwegian companies, and who designs the architecture, reviews what the agents produce, and answers for it.
The agents aren't something you can buy. Without an experienced operator they break, which is exactly why this isn't another prompt.
Recent work
United Kingdom
A venture backed by two family offices, with domain experts on the team and no product. Working software within the first months; ten months of versions in total, up to the point where the founders took it to venture investors in San Francisco.
Germany and Switzerland
A consultant with deep domain knowledge and a private investor. No deck, no landing page, no product. We built the product, and the first deck, together.
Israel
A deep-tech team of fifteen PhDs. Software was the smaller part of a hard problem. We built that part so the scientists could stay scientists.
Pricing
- A version is a scoped, approved unit of work, delivered in about a week
- No discovery fee, no retainer, no minimum number of versions
- Pay per version, stop whenever you like
- Code and IP transfer to you on payment; infrastructure is set up in accounts you own
- Prices exclude VAT where it applies
A typical path is three versions in three weeks, €14,970: a product you can onboard customers into and scale.
Questions founders ask
Will it scale?
Scaling is one more version. Version three makes the architecture grow with infrastructure spend. What we never do is build version one in a way that makes version three impossible.
My prototype is vibe-coded. Is that a problem?
It's the normal starting point. Send us the URL and we'll audit it for free: within 48 hours you'll know what survives a real customer and what doesn't.
I'm not technical. How do I know what I'm getting?
Every version comes with documentation and a plain-language walkthrough. You'll be able to explain your own product to a customer, an investor, or the CTO you hire later. Nothing depends on trusting us: the code, the infrastructure and the explanations are in your hands.
What happens when we raise and investors want an in-house team?
You hand them clean code, tests, documentation and infrastructure in your own accounts, and we help onboard them. Until that day you've been spending thousands per week instead of paying a team before you had customers.
Who owns the IP?
You do, from the moment you pay for a version. It's written into the contract.
Where are you based?
Norway. Clients so far have been in the UK, Germany and Israel, and the work is remote: a weekly call, a written scope, a live URL.
How do I start?
Book a scoping call, or send a prototype URL for a free audit. Either way you'll have a written scope and a price within two days, and a decision to make that costs you nothing until you say yes.
Two ways to start
Book a scoping call and get a written scope within two days. Or send a prototype URL for a free audit, and within 48 hours you'll know what breaks before a customer finds it.