about
Who you are handing the technology to.
Every other page on this site says “I” and “one person”. This is the page where that stops being a turn of phrase. You are about to hand the technical side of your business to a stranger, and you are entitled to know exactly who.
- who
- Lucian Lutas
- Founder, and the only person who does the work.
- when
- 15:00–20:00 Bucharest
- Calls run in the Romanian afternoon, which is all morning in the US, to 1pm Eastern, noon Central, 11am Mountain and 10am Pacific. Everything else is asynchronous.
the background
Where the experience comes from
I have been writing code since I was six, which is a nice line and not a qualification, so here is the part that bears on your app instead. Six things, chosen because they touch owning a live business application. The rest of the CV is not your problem.
aiudapp.com, taken over and then joined
Andres came to me for a fleet tracking portal that ran on Tookan. I rebuilt it in Next.js at about 80% lower cost, then took over the whole platform and stayed as the technical owner. The outcome was a partnership in the business rather than an invoice at the end of it.
Node.js and React, hosted on AWS and Vercel
The stack your app most likely ends up on, run in production for years rather than picked for this website. Served.life is the latest: a hospitality hiring platform rebuilt from Bubble into Next.js and Supabase, live with Stripe subscriptions.
SaaS web applications are the specialty
Which is what most founder-built apps turn into once a business depends on them. Multiple roles, subscriptions, background work, an admin surface nobody planned for.
No-code and AI tools from the inside
Bubble, WeWeb and Xano, built with rather than read about, and daily work with Cursor, Codex and Claude. Knowing where a tool's edges are is the difference between owning an app built with it and guessing.
Mobile, when the app has one
React Native and Flutter. AiudApp's field workers run on a Flutter app I redesigned; a business with a mobile app needs that owned too.
Junior to technical lead, then startups
The progression happened in the corporate world. The time since has mostly been startups, which is the pace this is built around and the reason the terms are written the way they are.
The full history is on LinkedIn, where it can be checked against people who were there, which is worth more than the same claims repeated here.
the shape of it
One person, and that is the offer rather than the excuse
A larger shop would take your retainer and hand the work to whoever is free that week. The reason this stays small is that the alternative is worse for the kind of job it is: owning an application nobody documented means holding the whole thing in one head, and that does not divide across a team. You get one name, one number and one person who knows your system.
It has costs, and they are published rather than discovered in month three. Capped hours. Two business days, not two hours. No on-call at any price. A short list of retainers, because the work only stays predictable while the list is short.
your credentials
What happens to your access
This is the part that should decide whether you book anything, so it is written down rather than left to a call. All four of these are commitments the terms page repeats.
View-only is enough to start
Read access to the code, platform or hosting, matched to the work. Nothing is changed without an agreed intervention and no database export is taken just to scope the job.
One person holds it
Not a team, not a contractor, not an offshore reviewer. The number of people with your credentials is one, and this page is where you find out who.
An NDA if you want one
Send it before the walkthrough and it gets signed. If you have your own paper we sign yours rather than asking you to read ours.
Revoked the day it lands
Access exists for the work and stops when the work does. Revoke it after the takeover or engagement ends; nothing on our side needs it afterwards.
the proof
AiudApp is the named case. This site is the sample you can inspect.
AiudApp is the named example of me taking over the technology behind a business and staying on as its owner. This site is the code sample you can inspect without asking for access.
Every page is real HTML
Forty routes, all prerendered as static files. View source on any of them and the content is there, not assembled by JavaScript after the fact. That is the same discipline your app gets.
The prices are on the page
Every offer has a published price and a published boundary. Nothing is hidden behind a call, and the call does not move them.
No cookies, no banner
Analytics runs without cookies, so there is no consent banner and nothing follows you around. The one form asks for exactly what is on the screen.
Next.js, Supabase, Vercel
The same three Served.life runs on. Nobody here is selling a stack they do not run.
That is the person. Here is how you hand it over.
Book 15 minutes and tell me what your business runs on. No access needed, and the published prices do not move on the call. Two plans for founders: Build your app for $4000 fixed, or let me own the technology behind it for $2500 a month. A menu of fixed-price AI automations for small businesses, from $800. The call is allowed to conclude that you should keep things as they are.