
European off-road marketplace from scratch
A pan-European marketplace for off-road vehicles: a listings crawler, many languages and currencies, payments and AI sorting of listings. Search was live a month after the crawler.
OffroadMarket
MVP and product
An MVP is the first version of a product that a customer pays for or starts to really use. We start from a list of what will be done, even when all you have is a half-built prototype. On one project we had the first version in under 10 working days.
Have a prototype from Lovable, Bolt or Cursor? We look at the code first and tell you: continue, harden, or start over. How it works: Vibe coding to production: what the prototype is missing
On one project we had the first version in under 10 working days. We launched another project in full within a month. When the product goes live we stay with you for another 30 days, so the first weeks with users are not on you alone.
A marketplace from scratchMVP development starts with the smallest thing you can sell. Then we add to it every week or two. For a founder who had built the product himself with AI, with paying customers already, we ran an audit. He got a short verdict and an order of steps he can handle himself, without a big rewrite.
Launch is not the end. A client's online marketplace fell from 250,000 to 66,000 pageviews a month after its crawler stopped in December 2025. Since then monitoring is part of every launch.
Code, data and infrastructure are in your name. Maintainable code, clear to any next engineer, so you can hire a team or raise money without us.
How we solve it: We take over the prototype, add security, data and tests, and get it into production.
Example: An audit of an app a founder built with AI. The first sentence of Filip's verdict: "None of this is Armageddon." Case study →
How we solve it: We find out what of the work so far is usable and ship in weeks, not months.
Example: One project: the first version in under 10 working days.
How we solve it: Together we write a list: what ships first, when, and how you can check it.
Example: One project: the whole system live within a month.
How we solve it: We take over the code, data and infrastructure, document them and keep building.
Example: You can leave us too: when you do, we fix the bugs from the last month.
A vibe-coded prototype or a half-finished agency project is a common starting point. The hard part is taking it to production: login, payments, data, security, monitoring. We look at the code first and tell you whether to continue, harden it or start over.

A pan-European marketplace for off-road vehicles: a listings crawler, many languages and currencies, payments and AI sorting of listings. Search was live a month after the crawler.
OffroadMarket

The founder built the product himself with AI, and customers pay for it. We ran an audit and a security test. He got a plan he can handle on his own, not a list of complaints.
product founder
Try the first month. If we miss what we wrote down, we refund 50 %. Monthly subscription from €3,980 excl. VAT, pause or cancel any time. Or a fixed price per project: tell us what you need and we send you a quote and a list of what we deliver. Code, data and infrastructure owned by the client from day one.
Month one starts with a written list: what we deliver and how you can check it. The 50 % money back is measured against it.
Only your own hosting and AI model usage. You pay them directly to the providers, not through us.
After launch you get 30 days of support. Then you pause the subscription. When something needs changing or adding, you resume it and we carry on. After you cancel, the software, data and infrastructure stay yours. When you leave, we fix the bugs from the last month.

The first usable version of an MVP should take weeks, not months. What goes into it, what does not, what a sensible timeline looks like and how to spot a badly set scope.

Your Lovable app works, but will it hold up with customers? The code can be exported via GitHub and developed further. What to check, above all data access, and what to add without a rewrite.

You take over an app from another vendor in three steps: secure the code, access and data, have someone look into the code, and only then decide. A checklist and the three possible verdicts.
Write to us. We get back to you within two business days, and together we pick what to fix first.