AI intake & lead qualification
Answer recurring questions, capture the details sales needs, and route the conversation to a person when it needs judgment.
See Lifetrek’s assistant & CRM ↗Rafael Almeida · GTM engineering for B2B products
I build the connective tissue between product, marketing and revenue: AI assistants, CRM workflows, content systems and internal tools for teams handling technical questions, documents and customer follow-up.
GTM engineer · Tampa, FL · English & Portuguese
What I build
For manufacturers and B2B teams managing detailed inquiries, handoffs and recurring work. Each engagement starts with one workflow and an agreed measure of success.
Answer recurring questions, capture the details sales needs, and route the conversation to a person when it needs judgment.
See Lifetrek’s assistant & CRM ↗Connect messages, customer state, payments and next steps so the team can see what needs attention.
See the WhatsApp workflow ↗Turn inputs and internal knowledge into useful drafts, reviewed documents and repeatable work. Keep approvals visible.
Explore technical documentation ↗Connect content production, campaign planning and reporting, with a clear view of owners and next actions.
Explore the NVIDIA work ↓Tools used in delivered work include WhatsApp, email, ClickUp, Supabase, Stripe and Mercado Pago. Other integrations are assessed during scoping.
Selected work

Manufacturing · Lifetrek Medical
A website assistant and CRM for a precision manufacturer, plus tools for technical documentation and recurring content work.
Service operations · DietProck
Two agents routed by customer state, payment integrations, PDF meal plans and an admin app. Built for a paying partner and live with paying clients.
See intake, payment & follow-up ↗Marketing operations · NVIDIA
Across two internships: ClickUp automation reported to save 500+ hours annually, a nurture program serving 120,000+ contacts, and campaign tools for marketing teams.
The contact count describes program scale, not attributable revenue. The time saving is an annualized figure.
Read the scope and my role ↗Also built for clinics and wellness practices, consulting firms and founders. Browse the wider portfolio ↗
A collaborator’s perspective
Had the opportunity to work with Rafael during his 2026 Summer stint at NVIDIA. He was an amazing resource for everyone who worked with him: helping manage communications, fleshing out marketing efforts, and building sustainable workflows that are still used today. The preparation and thoughtful insights he brings to every conversation make him incredible to work with. 10/10 would recommend. I know he will do great wherever he goes.
A client’s perspective · DietProck
Nutritionist and the client behind DietProck. Watch his recommendation from a conversation with Rafael.
25-second video · Portuguese
Explore the system built for his practice ↗How projects work
A focused first build gives us something concrete to validate before expanding across the business.
Review the inputs, tools, handoffs and exceptions. Agree on the first workflow and how to measure its value.
Use representative examples to test the workflow. Identify where automation helps and where a person must decide.
Connect the agreed systems. Define access, approvals, failure handling and the checks needed before launch.
Document how it works, walk the team through it, and agree on support and future changes.
Bring one recurring process. We scope the workflow, deliverables, acceptance criteria, timeline and price together before implementation. Ongoing support is agreed separately.
Before we start
A recurring process with clear inputs, an identifiable owner and a measurable outcome: qualifying incoming inquiries, preparing documents, routing requests or coordinating follow-up. Start with the workflow your team can explain and test.
Yes, integration is part of scoping. I review available APIs, account access and the limits of your current systems before proposing a build. The solution may use a workflow tool, custom code, AI or a combination.
That depends on the workflow, integrations and testing required. After the initial review, I propose a defined scope with a price and timeline. Share your current process and target outcome below so we can establish a useful starting point.
We define which actions can run automatically, which need approval and which should go to a person. High-stakes decisions remain with the responsible professional. Failure handling and human handoffs belong in the scope from the start.
Account ownership, access, documentation and maintenance responsibilities are agreed before work begins. Support after delivery is scoped explicitly so your team knows who to contact and what is covered.
Start a conversation
Tell me what happens today, where it slows down and what a better result would look like. We’ll use that to discuss a focused first build.
