about
Who you are handing your editor to.
Every other page on this site says “one person” at some point. This is the page where that stops being a turn of phrase. You are about to give a stranger read access to a live business application, and you are entitled to know exactly who.
- who
- Lucian Lutas
- Founder, and the only person who does the work.
- when
- to noon Eastern
- Calls run to noon Eastern, 11am Central, 10am Mountain and 9am Pacific. Everything else is asynchronous.
the background
Where the experience actually 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 a Bubble migration. The rest of the CV is not your problem.
aiudapp.com, migrated and then joined
AiudApp was preparing to grow, and the no-code builders had become the boundary: Workload Units constrained the system while the builders constrained what the interface could become. I moved the ecosystem to code so every layer could be controlled directly. The outcome was a partnership in the business rather than an invoice at the end of it.
Node.js and React, hosted on AWS
The far side of a migration, shipped in production for years rather than picked for this website. When the target stack is argued for on the migration page, it is argued for from having run it.
SaaS web applications are the specialty
Which happens to be what most Bubble apps are by the time they outgrow Bubble. Multiple roles, subscriptions, background work, an admin surface nobody planned for.
No-code from the inside
Bubble, WeWeb and Xano, built with rather than read about. Knowing where a platform's edges actually are is the difference between quoting a migration and guessing at one.
Mobile, when the app has one
React Native and Flutter. A Bubble app that grew a mobile companion does not stop needing it the day the web app moves to code.
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: taking over an application nobody documented means holding the whole thing in one head, and that does not divide across a team.
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
Read access to the Bubble editor. Nothing in your app is changed during an audit, and no export of your database is taken.
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 when the document arrives; nothing on our side needs it afterwards.
the work sample
This site is the argument
It is built on the stack clients get migrated to, which makes it the one piece of work you can inspect before paying for anything. Not a screenshot of a case study: the actual thing, open to view-source.
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 a migrated app gets.
The numbers are traceable
Every price and vendor figure comes from one config file that carries the date it was last checked against the vendors' own pricing pages, and the page prints that date. A test fails when it goes stale.
The calculator can tell you not to buy
It returns a stay-on-Bubble verdict when the arithmetic says so, and there are tests asserting it still can. A tool that always recommends the expensive option is an advert.
Next.js, Supabase, Vercel
The same three the migration pages recommend. Nobody here is selling a stack they do not run.
That is the person. The work starts with the audit.
One week on your actual app, $500, half of it credited against a migration if one follows. It is allowed to conclude that you should stay on Bubble.
If you want to meet before handing over access, virtual coffee is a 30-minute conversation. It is not a discovery requirement and the published prices do not move on the call.