I build the software your business runs on.
Platforms, applications, internal tools and the infrastructure underneath - designed, written and put into production by one senior engineer. Seven years, 90+ systems in production: CRMs, ERPs, clinical systems under HIPAA and GDPR, booking and lead engines, online stores, AI platforms whose models I trained myself, and a blockchain delivered fully functional.
THE STACK I ACTUALLY WORK IN
One person, the whole stack. That is the offer, not a limitation.
There is no handoff between whoever designs the database and whoever builds the screen, because they are the same person. The decisions that normally get lost between three suppliers get made once, in context, by someone who then has to live with them.
Five steps. No surprises in any of them.
-
01CALL
Thirty minutes. You describe the problem, I tell you whether I am the right person for it. If I am not, I say so plainly, and I may point you towards people I have worked with over the years.
-
02DISCOVERY
A fixed-price, fixed-length stage that ends with a written scope, an architecture and a real number. The document is yours whether or not you continue with me.
-
03BUILD
Staged delivery against the agreed scope. You will have working software on a test environment from the first stage, so you can judge the product itself rather than a status report about it.
-
04HANDOVER
Documentation, tests, a deploy your own team can run, and every account and repository in your name. From day one, not on request or at the end.
-
05AFTER
Maintenance under an SLA if you want it, and no contract lock-in if you do not. A system you cannot leave is an unprofitable one for the client.
Things people ask before we start.
What does a project cost?
It depends on what has to be built, and I will not pretend otherwise - but the ranges are not a secret. A focused site or internal tool usually lands between €1,000 and €15,000. A platform a business actually runs on is typically €5,000 – €40,000. Beyond that, the latter is a system with several products inside it.
What I will not do is give you a number before I understand the problem. That number would be wrong, and we would both spend month three renegotiating it. A short paid discovery produces a real figure and a written scope, and the document is yours whether or not we continue together.
How long does it take?
Discovery takes 1-2 weeks. The build, usually between 2 and 16, depending on how much there is to do.
Throughout the project you see working software on a staging environment from the first stage, not a demo at the end. That matters more than the total: it means you are looking at the platform itself while it is being built, and can judge in real time whether something needs to change, while there is still time.
Do you work alone? What if you are unavailable?
Yes, alone. For one company's core system, the coordination cost of a team usually exceeds what the extra hands buy, and the quality comes from one person holding the whole model in their head.
The honest risk is exactly the one you are asking about, so I answer it structurally rather than with reassurance: everything is documented, tested and deployable by somebody else, and every account and repository is in your name from day one. If I disappeared tomorrow you would hand another engineer a working system and a written architecture, not a mystery.
Who owns the code?
Yours, from the first commit. Repositories, servers, domains, DNS and third-party accounts are created in your name from the start; they are not transferred at the end.
There is no moment at which the work is held hostage, because there is no moment at which I hold it. I have taken over too many systems locked up by whoever built them to ever do that myself.
Can you take over a system somebody else built?
Often, yes. I read the code first and tell you honestly what is salvageable.
Sometimes the answer is that it is fundamentally sound and needs a week of work rather than the rewrite you were bracing for. Sometimes it is that a rewrite really is cheaper than continuing. You get whichever of those is true, including when it costs me the larger project.
Where are you based, and do you work remotely?
Bucharest. Most of my clients are somewhere else.
I work across the EU routinely and have worked on US time zones. Hosting is in the EU by default, or wherever you want it; data is handled under GDPR and US standards such as DNC and HIPAA; and the contracts and invoicing are the ones your finance and legal departments want to see.
What happens after launch?
Maintenance with a response time agreed in the contract, if you want it, and absolutely nothing, if you do not.
The second option is deliberate. A system you cannot leave is not a system you should be buying, so the handover is designed to work whether or not I stay involved: documentation, tests, a deploy your team can run, and monitoring that reaches a person before a customer notices.
If you want it, I can handle maintenance, and - depending on the platform I build for you - introduce you to people who specialise in marketing and lead generation to take on the promotion side.
My platforms are built to help marketing departments, and over the years I have worked with some brilliant marketing people who proved their worth and from whom I learned a great deal about digital marketing and how it interconnects with IT.
Do you build AI features, and should I want one?
Where AI earns its place, I build it properly: retrieval grounded in your own documents, with citations; scoring trained on your own data; a provider abstraction so a price change is a config edit; and an evaluation harness that shows how it behaves before it reaches a customer. An AI feature nobody has measured is not a feature, it is an unpriced risk that demos beautifully. Where a simple rule or a well-designed form does the same job at a hundredth of the cost, I tell you straight away.
Tell me what you are trying to build.
Six questions, about two minutes. What you get back is a straight answer on whether it is a fit, a realistic range, and a time - not a brochure.