Work
Selected work across products, platforms, and technical organizations.
Each case below is written as a set of decisions — the context, what was refused, what it cost, and what it taught — rather than as a list of deliverables. Where a number is not verifiable, it is not here.
Cases
AI product systems Building a seven-server MCP ecosystem as a developer product, not a code dump Seven Model Context Protocol servers published on npm, six in Rust and one in TypeScript. The interesting decisions were about credentials, install friction, and tool granularity — not about the protocol.- The product problem was not protocol support. It was that connecting an agent to a real account meant pasting long-lived credentials into a config file.
- Tool granularity is the core product decision in an MCP server: too coarse and the agent cannot compose, too fine and it wastes context discovering what it can do.
- Every app here exists because a constraint was interesting, not because the category was underserved — which is a real strategy and a real limitation.
- Cresum's product is a refusal: no account, no server-side storage, all state in the URL. The constraint is the feature.
Where the evidence lives
Context for the work
- 2024 — CTO, Guinea Mobile Telecom and IoT: an MVNO platform where other companies build connectivity products. Product, technology, operations and organizational design.
- 2020 — Technology consultant, Grupo Anta Digital transformation work across sectors, combining technical delivery with strategy.
- 2018 — 2023 Co-founder and CTO, Syma POS and electronic invoicing for the Peruvian market under SUNAT compliance rules. Intellectual property sold in 2023.
Full profile on about.