With AI agents, I build as much as an entire team

I build scalable web and mobile applications for founders, startups, and companies that want solid, maintainable digital products, ready to evolve over time.

I handle both the first version of a product and more structured applications, with authentication, payments, dashboards, integrations, automations, AI, and complex backend logic.

In a software house, your project passes through many hands: sales reps, project managers, designers, developers, and technical leads. Every handoff adds time, cost, and room for misunderstanding.

With me, the relationship is direct. You talk to the person who makes the technical decisions, designs the architecture, and builds the product. I'm more efficient because I work solo, with no coordination chains slowing things down, and at the same time more productive because I rely on dozens of AI agents developing in parallel under my guidance.

What that means in practice: less ambiguity and fewer slowdowns, faster timelines, and a cost that often lands around half of what a traditional structure charges.

I build products designed to grow.

Even when we start from a first version, I aim for a solid technical foundation rather than a throwaway prototype: maintainable code, clear architecture, a well-designed database, manageable integrations, and a structure ready to evolve.

I work with a method built on agentic coding, spec-driven development, and AI automations.

First I define exactly what needs to be built, then I coordinate dozens of AI agents working in parallel to speed up development, review, testing, documentation, and iteration. This lets me work with the output of a much larger team while keeping direct control over technical quality.

Yes. AI is part of my development process, but it never replaces technical responsibility.

I use it to speed up writing code, analyzing edge cases, generating tests, documentation, and review, and automating operational tasks. Architectural decisions, product quality, and final validation stay firmly under my control.

No, as long as it runs inside a serious technical process.

AI used without method creates confusion. AI used with clear specs, technical review, and continuous oversight increases speed, precision, and the quality of the work.

For founders, startups, and companies that want to build a web or mobile application on a serious technical foundation, without hiring an in-house team right away or committing to a heavy structure.

It fits anyone who wants to move fast while avoiding fragile software that's hard to maintain.

It's not a fit for anyone looking for "a coder by the hour" or a quick solution with no attention to quality.

My work delivers the most for founders and companies that want to build a real product, make decisions quickly, and invest in a technical foundation that can grow over time.

Yes. You don't need a complete technical document already in hand.

I can help you turn the idea into a clear spec, define the priority features, choose the right architecture, and work out the first version that actually makes sense to build.

Yes, and I treat it as a real foundation rather than a rushed prototype.

Even the first version has to be built with scalable logic: it should let you validate the market, gather feedback, and keep evolving without rewriting everything from scratch a few months later.

It depends on the complexity of the product.

A well-defined first version can take a few weeks. More complex applications, with multiple user roles, payments, dashboards, integrations, AI, or a mobile app, call for more extensive planning.

It depends on the type of application, the level of complexity, and the stage the project is in.

After an initial analysis, I prepare a clear proposal covering scope, timeline, ways of working, and the investment required.

Yes. A big part of my work is designing a solid technical foundation: backend structure, database, authentication, permissions, payments, integrations, APIs, deployment, and future scalability.

The goal is to avoid weak technical choices that turn into problems once the product grows.

Yes. I can work alongside founders and companies as a Fractional CTO, helping make technical decisions, define the product roadmap, set up the architecture, evaluate vendors, or prepare for a more structured development phase.

Yes. I can collaborate with existing teams, both on development and on introducing more efficient processes built on AI, agentic coding, and spec-driven development.

Yes. I teach the same method I use to build products: agentic coding, spec-driven development, AI automations, and the practical use of modern tools in software development.

The goal is to show AI as a real part of the development process, well beyond a simple chatbot.

Yes. When it's needed, I bring in a designer I work with.

The goal is to build applications that work and that are also clear, usable, and credible in the market.

Yes, when the project calls for it.

I can support the post-launch phase with bug fixing, new features, improvements, feedback analysis, and planning the next versions.

Yes. The product built for the client belongs to the client, according to the terms defined in the proposal and the contract.

I choose the stack based on the project.

I typically work with modern technologies for web apps, mobile apps, serverless backends, databases, authentication, payments, AI, and automations. The technical choice always follows the product, its scalability, and future maintenance.

Yes. I've worked on SaaS, marketplaces, mobile apps, dashboards, AI tools, fintech/crypto products, and software for companies.

Alongside client projects, I also build products of my own, and I bring the same method to every project I take on.

We start with an initial consultation where we go through your goal, current state, constraints, priority features, and technical direction.

From there, I prepare a proposal with scope, timeline, and ways of working.