Who’s Behind It
EC:{Dev} Labs is a senior engineering studio in Timisoara, Romania, founded in 2022. From day one it has run on a direct line: the person answering your questions is the architect writing your code, so nothing has to survive a relay of account managers first.
How I work
I scope the work, lead the build, and answer for what ships.
Direct clients
On larger products I assemble and lead the team the build actually needs (engineering, UI/UX, front-end, QA), from collaborators I have worked with before. However many people that turns out to be, you deal with one point of contact, and it is me.
Agencies, EU and US
I plug in as a senior engineer and architect on your bench, white-label and NDA-ready: the work ships under your name, and how you introduce me is your decision. Most of these engagements run async, which is how I work anyway.
Agentic AI, and the architecture behind it
Agentic AI is the newest lane of the studio, run with the same discipline as the back-end work. Agents act through the APIs you already have, and every action a model takes is one someone can review and undo.
What holds that up is systems architecture: authentication, permissions, an audit trail someone can actually read. Familiar back-end problems, with a model at the other end of the API call.
Who you’ll work with
Elvis Claudio
Writing software professionally since 2013: back-end and cloud first, then mobile, then AI integrations. Zend Certified Engineer since 2019. Licensed trainer (2023) and certified coaching specialist (2024), both certified by Romania’s Ministry of Education. MSc and BSc from the Polytechnic University of Timisoara.
I lead systems architecture and delivery on every engagement, and I am your single point of accountability, whether you hire the studio directly or bring me in through your agency. Back-end and architecture are the studio’s default lane; pixel-level UI design is not, and you’ll hear that on the first call.
Not sure whether an individual subcontractor or a full team fits better? Mention it in the contact form and we’ll work it out on the scoping call.
What people check before hiring a studio
Who owns the code and the IP when the work is done?
You do, from the first week. Work happens in your repositories and, wherever possible, your cloud, domain, and store accounts, so ownership never has to be transferred at the end. That goes in the contract in writing, and I keep nothing back as leverage: no license fees on code written for you, no accounts registered to the studio that you have to buy back. On agency subcontracting the same principle applies one level up: your client owns what ships, under your existing agreement with them.
What happens if a collaborator leaves mid-build?
The build doesn’t stall, because the parts that hold it together aren’t in anyone else’s head. Architecture, code review, and the deployment setup stay with me on every engagement; collaborators work in your repositories against a written scope, and what they produce is reviewed before it lands. If someone becomes unavailable, their replacement reads the same documentation your next engineer would, and you hear it from me, not from a missed deadline.
Work with the studio
Describe what you’re trying to ship: a senior engineer on your bench, or a full build with the team.