FAQ
Questions you might be asking yourself.
Short answers on scope, how engagement usually looks, and how to start a conversation.
When does FastStore make sense?
When you need more frontend control, headless performance and a modern GraphQL BFF, and the team can own a Next.js storefront. VTEX IO is still a strong fit for deep block ecosystems and mature checkout customizations. I help choose based on the project's real constraints, not trends.
Can you review an existing VTEX architecture?
Yes. Typical scope: platform boundaries, coupling risks, checkout/integration hotspots, customization debt and a prioritized remediation roadmap.
Do you work on existing implementations or only greenfield?
Both. Most of my recent work is evolving large production platforms (e.g. Carrefour on VTEX IO) and migrations (e.g. Cetrogar to FastStore in ~90 days).
Can you work with internal teams?
Yes. That's the default in agency delivery. I define technical direction, review architecture and code, mentor, and coordinate with product, partners and stakeholders.
What kind of performance problems do you solve?
Storefront bottlenecks (IO / FastStore), API and integration latency, checkout friction, and architecture choices that hurt conversion under load.
Can you lead a team of VTEX developers?
Yes. That's my current role at Valtech: technical leadership plus hands-on delivery when complexity demands it.
How can I start a conversation?
WhatsApp, LinkedIn or email from the contact section. A 30-minute architecture conversation is usually enough to see if there's fit.
Contact
Do you have a VTEX architecture that needs a review?
WhatsApp, LinkedIn or email.
I can help with:
- Architecture review
- Technical discovery
- Migration strategy
- Performance review
- Technical leadership