E-commerce & payments
Catalogue, checkout, local payment methods (Klarna, Adyen) and reconciliation.
Platforms that operate: e-commerce, portals, event platforms and owned SaaS. Performance, accessibility and security by default.
A production web app is measured on three things: speed on mobile, stability under load and traceability of what happens. We build platforms to that standard, from e-commerce to internal systems.
Evidence: the Paperless platform at JCDecaux Mexico, the payments work with Chanel EMEA and the official app of Colombia Tech Week 2026.
We pick the stack by the case, not the fashion; the decision is documented.
Catalogue, checkout, local payment methods (Klarna, Adyen) and reconciliation.
SSO, approvals, dashboards and audit (see Paperless).
Agenda, networking, chat and maps that survive event-scale peaks.
Full-stack product with multi-tenancy, roles and billing.
Stack, performance and security decisions documented before coding.
Sprints with demos; per-page performance budgets.
Accessibility, load and edge cases on low-end phones.
Deployment, monitoring and an incident-response plan.
| Performance | Per-page budgets and Core Web Vitals targets. |
|---|---|
| Security | OWASP, headers, dependency reviews. |
| Accessibility | WCAG 2.2 AA verified. |
| CMS | Frictionless self-service content management. |
| Integrations | Payments, CRM, ERP and own APIs. |
| Observability | Logs, metrics and alerts from day one. |
Read more
Chanel · EMEA
With Chanel EMEA we opened the path to integrate local payment methods (such as Klarna) on Chanel.com without depending on the worldwide roadmap: an autonomy diagnosis, Hybris and Adyen analysis, and a secure proxy architecture on a shared Adyen merchant account.
Learn more →
Read more
JCDecaux Mexico
Paperless centralizes purchasing, inventory, work orders, advances and refunds for JCDecaux Mexico in an internal platform with Single Sign-On, approvals and audit-ready traceability.
Learn more →Both; discovery shows where rebuilding pays and where modernization is enough.
Yes; the proxy architecture we designed with Chanel EMEA is an example.
Yes: a CMS for content changes without developer dependency.
Discovery to production typically runs 8–16 weeks by scope.
Yes: version plan, monitoring and a priority-driven backlog.
From idea to production: product, design and engineering in one team.
Learn more→ SoftwareWe replace SaaS licenses with owned products your team controls.
Learn more→ MobileProduction iOS/Android apps: native or cross-platform, AI included.
Learn more→ AutoRepetitive processes, out. Robust flows with traceability, in.
Learn more→Tell us your challenge. We reply within 24 hours with an honest first read: if we can help, we'll say how; if not, we'll say who can.
I reply personally. No endless forms, no canned replies.