Founder & Technical Lead · SaaS, APIs & AI Agent Operations
Building software businesses since 1997 — connecting technology, products, and real-world operations.
Website · Get in touch · Lead Protocol
I'm the founder and technical lead behind Lead Solutions and First Shop, with software businesses operating across Brazil, the United States, and Europe.
My work connects product decisions, software architecture, and day-to-day operations. I build SaaS platforms, B2B/B2C APIs, and marketplace infrastructure, with a particular focus on the automotive parts market.
Today, that also means working with AI agents as part of the engineering process: defining scope, coordinating implementation and independent review, and validating what actually ships.
📍 Florida, US · São Paulo, BR
Software platforms and integrations for businesses that need their catalogs, commerce, and operational systems to work together. My focus spans SaaS products, APIs, and automotive parts marketplace infrastructure.
Operational continuity for AI agents. When a session ends or another agent takes over, the work should not start from zero.
Lead Protocol keeps handoffs, decisions, lessons, and session state in structured files. It is vendor-neutral, with a substrate-agnostic core and optional tooling for repository-based workflows.
The project grew out of a practical need: keeping agent-assisted engineering coherent across sessions and tools, with explicit ownership and a record of why decisions were made.
Explore the project · Published releases
A 3D-printing e-commerce business — another place where product, technology, and physical operations meet.
- Define the work first. Scope, constraints, and acceptance criteria come before implementation.
- Separate implementation from review. Give agents clear responsibilities and use independent review to challenge the result.
- Make continuity explicit. Record decisions, pending work, and handoffs so another session can resume with context.
- Verify the real result. Run the code, exercise the workflow, and distinguish tested behavior from assumptions.
- Keep people in control. Sensitive actions need explicit approval; access should be limited to what the task requires.
Lead Protocol is the public expression of that approach: practical rules and tooling built around the work, rather than a dependency on one model or agent platform.
Products & integrations
SaaS · B2B/B2C APIs · E-commerce · Marketplaces · Automotive parts
Application development
Laravel · Node.js · Flutter · REST APIs
Infrastructure
AWS · Linux
AI-assisted engineering
Agent coordination · Specification-driven workflows · Independent review · Operational continuity · Evidence-based validation
Much of my commercial engineering work lives in private repositories. This profile highlights the public projects and the way I approach building software; it is not a complete inventory of client or company systems.
I care about the connection between a technical decision and the business it serves: who uses it, how it is operated, and what happens after deployment.
Interested in SaaS, commerce integrations, or practical AI-agent workflows? Let's talk.