Lead operations, connected
I build reliable automation systems for lead qualification, customer messaging, appointments, CRM workflows, and internal operations.
From the first website submission to WhatsApp qualification, appointment booking, reminders, and CRM handoff — designed as one connected system.
What I build
Each system works on its own — and becomes more valuable when it shares the same data, rules, and conversation context.
A configurable lead qualification system that turns form submissions into structured WhatsApp conversations and CRM-ready data.
A scheduling workflow that understands requests, checks real availability, proposes suitable alternatives, and keeps reminders aligned with the current conversation state.
A customer-friendly control layer for managing campaign questions, messages, appointment rules, reminders, templates, and runtime configuration without editing workflows.
One connected lead journey
Instead of combining isolated automations, I design the complete path from submission to qualified lead, appointment, and operation.
A campaign needed to turn landing-page submissions into structured WhatsApp conversations while supporting appointments, reminders, CRM updates, and different campaign configurations.
Workflow logic was separated from campaign configuration, with a published runtime layer, conversation-state guards, appointment routing, and reminder safety checks.
How we can work together
Design workflow boundaries, state management, data models, runtime configuration, and failure strategies before complexity becomes expensive.
Build production-oriented workflows for messaging, CRM, scheduling, email, and internal operations.
Review broken routing, duplicated sends, inconsistent state, unsafe reminders, fragile connections, and data-write problems.
Connect landing pages, WhatsApp, Airtable, Notion, email, and internal workflows into one operational process.
Build repeatable conversation and workflow tests for the paths that matter most to your customers and team.
Engineering principles
Campaign differences belong in configuration, not copied workflows.
Qualification, appointments, and reminders must agree on the current customer context.
Messages are checked for eligibility before they reach the customer.
Workflow behavior should be measurable and reproducible, not only manually tested.
About Alex
Gellert-Innovation is where automation design meets practical engineering: connected systems with clear rules, useful configuration, and a focus on the situations that usually break first.
Automation n8n · Webhooks · scheduled jobs
Customer operations Twilio WhatsApp · email · appointment workflows
Data & configuration Airtable · Notion CRM · structured runtime contracts
Infrastructure Linux · Docker / Podman · TLS · monitoring
Start a conversation
Let’s map the workflow, identify the fragile points, and build the next reliable step.
