What I solve
- Your operation is held together by spreadsheets and tools that don’t quite fit.
- You need to launch a product or an MVP and validate without over-building.
- You have a technical base that stalls the moment you try to grow or integrate.
Engineering
Custom software, built around how you work
When a template or a generic SaaS no longer fits, you need software designed for your operation. I design and build it with solid architecture —the same I’ve applied at IKEA, Cencosud or EssilorLuxottica— so it doesn’t turn into technical debt six months later.
What you get
- A tool built around how you work, not the other way round.
- Architecture designed to maintain and scale, with quality code and tests.
- A phased plan: ship something useful soon and evolve with real data.
What I build
- Custom web platforms and internal tools (React, Node.js, NestJS).
- Cross-platform mobile apps (React Native) from a single codebase.
- Scalable APIs and backend (REST, microservices, event-driven architectures).
- MVPs to validate demand before investing in the full product.
How I work
- Diagnosis and scope: I understand the business goal and define the minimum that adds value.
- Architecture: I decide stack, integrations and risks, with clear success criteria.
- Phased build, with concrete deliverables, tests and direct communication.
- Evolution: we measure real usage and prioritise the next improvements.
When it makes sense
- No off-the-shelf product covers your process without forcing it.
- You’re going to validate an idea and want a solid first version, not a throwaway prototype.
- You need to rebuild or scale a technical base without multiplying the debt.
The experience behind it
10+ years building software in production: Technical Lead at Cencosud, full-stack at IKEA, EssilorLuxottica, Yuvod and Walmart Tech. Own products like Fichaloop (construction management) and iPropeli (real-estate CRM).
Frequently asked questions
Custom software or a template / SaaS?
If a standard product covers your case, use it: it’s cheaper. Custom software makes sense when your process is your advantage and forcing it into a template costs you time, data or customers. I’ll tell you honestly in the diagnosis.
Can you improve something I already have without rebuilding everything?
Yes. Many projects are the evolution of an existing base: phased refactor, performance improvements, new integrations or architecture fixes, without throwing away what already works.
How do I know if I need an MVP or a full build?
If you haven’t validated real demand yet, an MVP: a minimum functional version to learn with users. If the business already works and you need to scale or systematise, a fuller build.
Does this fit your case?
Tell me the concrete problem —the process, the volume, what it costs you today— and I’ll tell you the most sensible path with judgement. No empty promises.