Disrover
Custom operations platform

I replaced Excel as Disrover's core operating system for field sales, inventory, payments, seller commissions, and reporting — without stopping daily operations.
Start with the diagnosis or go straight to building. You pick the scope; the standard of work is the same either way.
I look at how your company works from the inside: what systems you run, what is still done by hand, where you are exposed and what can be automated. It ends in a report with what needs fixing and in what order.
I build the software the diagnosis showed you are missing: web platforms, mobile apps, integrations between the systems you already run, and AI agents that do real work. Nothing that will not get used — only what pays for itself.
You have me available all month: questions, reviews and follow-up on whatever the report left open. It is the cheapest way not to lose the thread between one project and the next.
I don't do catalog pricing. Every business is different, so I design and quote each solution to fit your case — starting with a free 30-minute meeting.
See all servicesProjects where I built software that's part of the business itself, not a presentation layer around it.
Custom operations platform

I replaced Excel as Disrover's core operating system for field sales, inventory, payments, seller commissions, and reporting — without stopping daily operations.
The portfolio holds two own products today: one I design, build and use myself every day, and one I left free and open for anyone who needs it.

I already had a nutrition tracking system that worked well from my computer, but I lost continuity away from home — I had to wait until I got back to log anything. I built NutriCoach to fix that: a conversational coach that knows your context, not one more calorie calculator.
No phase ends without something you can review. If a step produces nothing to look at, it does not belong.
~1 day
Thirty minutes to understand what you need. You leave with clear scope, shape and timeline.
~2 days
I turn the conversation into a written plan, with edge cases and technical decisions spelled out. We review and sign it before any code is written.
~1 week
A first navigable version, with real data. What doesn't earn its place gets cut here, not in production.
days, not weeks
Short cycles with a demo. You see real progress every week, not a progress report.
1 day
Deploy with CI, monitoring and backups. Nothing ships without a green suite.
ongoing
What I build, I run: monitoring, improvements, and an answer when something breaks.
Architectural decisions explained. Technical trade-offs documented. Every post comes from production experience, not theory.
Agentic AI refactor methodology in four validation layers. 24 commits, 13 routes, 0 regressions. The point: how you validate that AI did it well.
One to two months to a first version in production. The range depends on technical demand: an internal dashboard ships in four weeks; a product with auth, payments and an admin panel takes eight.
Fixed price against agreed scope, not by the hour. The contract sets the deliverable and the amount before we start. No catalogue pricing: every business is different and every solution is quoted to fit.
By default Next.js and TypeScript on the front, Node and PostgreSQL on the back, Vercel and Supabase for infrastructure. I change it only when the problem calls for it, never for fashion.
It accelerates, it doesn't replace. I use it to turn conversations into specs, cover edge cases and hold pace. Architecture decisions are mine, and I answer for them.
Fully remote, with in-person meetings in Santiago when the project justifies it. Delivery doesn't depend on sharing a room.
With the brief below, or a direct email. I reply within one business day with scope, shape and timeline — or with a straight answer if I'm not the right person for it.
30 minutes to understand your case. You leave the meeting with a tailored quote in hand. You decide whether to move forward — no pressure, no commitment.