Production quality from the first line
Tests, observability and security from day one. I don't ship a prototype dressed up as a product: I ship something that holds up to real users.
Service · From zero to production
Your product, from zero to production — in weeks, not quarters.
I design and build your product from scratch, with production quality from the first line. I take few projects at a time so I can go deep on each one —I move fast, I use AI to build, but senior judgment decides the architecture and owns what ships.
The context
Custom software doesn't fail on the idea. It fails on how it's built.
Too many custom projects end up late, expensive and far from the problem that started them. The flaw is almost never the idea of building custom, but the how: handoffs, middle management, prototypes dressed up as products. With senior judgment and AI used to build faster, a small, well-directed project delivers sooner than a traditional factory — without paying for the speed in technical debt.
Six things I do differently.
Senior end-to-end, on few projects at a time
You talk to whoever designs and writes the code. I take few projects at a time precisely so I can be end-to-end on each one, in depth, with no middle management to dilute the context.
Fast, with AI to build
I use code assistants and agents in my own workflow. I deliver much faster than the traditional model, at the same quality bar.
No shortcuts that get paid for later
The architecture is designed to scale. Speed doesn't turn into technical debt six months down the line.
Integrated with your stack
I connect to your ERP, CRM, GeneXus KBs, data lake or whatever you have. I don't propose tearing down what works.
AI where it adds value, not decorative
If your product needs AI, it goes into the core flow — it decides, responds, automates. If it doesn't, I don't add it for fashion.
The kind of product I deliver.
Vertical SaaS
End-customer products for specific industries. Design, backend, admin panel and billing — ready to charge.
Internal tools and portals
Applications for real processes: support, procurement, legal, operations. They know your data and answer with context.
Agents and automations
Flows that run real tasks —reading mail, generating documents, classifying, following up— with a human in the loop where needed.
Natural-language dashboards
Dashboards you query in plain language that respond with charts, not tables nobody reads.
Semantic search over your data
Production-grade RAG over documents, tickets, contracts or KBs. Sourced answers, not hallucinations.
Products around GeneXus
If your backbone runs on GeneXus, I build around it —portals, integrations, modern experiences— without touching what already works.
From the first call to software in production.
- 01
Discovery
I understand the process, the users and the data. I come out with a scope proposal, an architecture and a fixed price by phases. No surprises.
- 02
Functional prototype
A real MVP with the critical flows. Touchable, testable with internal users, and you decide whether it's worth continuing.
- 03
Iterative build
Periodic demos with software running in your environment. Joint prioritization and quality and adoption metrics visible from day one.
- 04
Go-live and handoff
Deployment, monitoring, documentation and transfer. You keep the code, the infrastructure and a team able to operate it.
- 05
Support and evolution (optional)
If you prefer, I keep accompanying you. If your team takes over, that works too. I never tie you to the vendor.
This service is for you — or it isn't.
We'd rather say no than oversell. If something here doesn't add up for you, we'll talk it through on the first call.
It makes sense if…
- You want to launch a new product and need to build it from scratch, fast and well.
- You already ran a POC and now need to take it to serious production.
- Your internal team is saturated and you need to accelerate without hiring six people.
- You operate on GeneXus and want to build modern experiences without migrating the backbone.
It's not for you if…
- You want to train your team to build with AI, not have me build it: that's what Training in AI architecture and development is for.
- You need to add devs to your team by the hour: this service isn't the right fit, and I'm happy to point you to someone.
- You're after the cheapest or fastest vendor at any cost: I take few projects in depth, this isn't a volume service.
Why this service exists
Custom software earned a bad reputation for a reason: too many projects delivered late, expensive and disconnected from the problem that started them. I believe that has more to do with how things are built than with the idea of building custom.
Today the tools have changed. A project led by a real senior and assisted by AI can deliver much faster than the traditional model — without losing quality, with more contact with the business and better architecture decisions. That’s my starting point.
How I think about projects
I’d rather deliver something small and real than promise something big and far away. You see software running in your environment from early on. If something isn’t serving, I change it there — not in a late retrospective.
I treat AI as one more piece of engineering: with tests, measured costs, fallbacks for when the model goes down or answers badly. I don’t put it where it isn’t needed. Where it is needed, I put it well.
What you won’t find here
I don’t do staff augmentation or sell pool hours, and I don’t deliver mock-ups with no code behind. If you need to add five devs to your team, there are better vendors for that — happy to recommend one.
What I do is take a business problem, design a solution and ship it working, ready for production.
What people ask before starting.
How is this different from hiring a software factory?
Two concrete things. First, you own the context: you talk to whoever designs and writes the code, with no handoffs to dilute the idea. Second, I use AI to build: I deliver faster than a traditional factory, at the same quality bar.
What stack do you use?
By default: TypeScript end-to-end (React/Next on the front, Node on the back), Postgres, and the models that best fit the case when there's AI. If your current stack is .NET, Python or GeneXus, I work on top of what you have.
How much does it cost and how long does it take?
The initial discovery is fixed-price. From there I close per phase with clear scope and price, with a calendar agreed at each one. The product is delivered by increments — there's never a distant big bang.
Who owns the code?
You do. The whole repository, infrastructure and documentation are delivered in your name. Nothing stays tied to me.
Do you have GeneXus experience?
Yes, it's part of my track record: I've spoken at the GeneXus community since 2003. If your product has to coexist with or extend a GeneXus backbone, I know the terrain.
Other services
Have a product in mind?
I take few projects at a time, so there isn't always an open slot right away. An initial call is enough to know if the project makes sense — and if it does, I propose a fixed-price discovery to get started.