AI agents and automation pipelines that qualify leads, answer customers, and move data — without manual follow-up.
Four areas where automation moves the needle most.
Multi-agent systems for email, calendar, support, and lead qualification — Claude, GPT-5, Gemini with real memory, not scripted chat.
End-to-end systems in n8n, Make, and Zapier connecting CRMs, inboxes, and marketing tools — follow-up in seconds, not hours.
Pipelines, snapshots, white-label builds, and AI chatbots wired into the CRM your team already runs on.
Documents turned into a searchable, AI-answerable knowledge base with vector embeddings.
Simplified simulation of my Gmail & Calendar Assistant — one goal in, the agent plans and executes.
"Find tomorrow's available meeting slots and email John."
Email sent to John — 10:00–10:30 AM proposed, calendar invite attached.
An n8n-style view — click a node to step through. Simple or Technical.
A new lead arrives — form, webhook, or inbound message. The run starts here.
Simplified view of my RAG pipeline — documents in, grounded answers out.
"What's your refund policy?"
"Refunds are available within 30 days of purchase, provided the item is unused and in its original packaging. Contact support with your order number to start a return."
One pipeline shape — a request comes in, an AI agent reasons, automation executes, the result lands where your team can see it.
Something happens — a form fill, a message, a missed call.
A form submission, inbound message, missed call, or scheduled trigger fires a webhook, passing a structured payload into the pipeline.
AI reads the request and figures out what to do next.
Claude, GPT-5, or Gemini processes the payload — using function calling and structured outputs to classify, qualify, or decide the next action.
The right steps happen automatically, in the right order.
n8n, Make.com, or Zapier orchestrates branching logic, retries, and routing across connected nodes.
The AI talks to the other apps your business already uses.
REST APIs and webhooks pass authenticated requests between the AI layer and connected tools.
The record gets saved and moved to the right stage.
GoHighLevel or HubSpot's API updates the contact record, sets the pipeline stage, and triggers the next touchpoint.
Information is stored so it can be found again later.
PostgreSQL or a vector store (Pinecone) persists structured data or embeddings for retrieval.
The task gets done — no one had to do it by hand.
The pipeline resolves to a logged, auditable outcome — timestamped, with a status a human can check.
The same lead, handled two ways.
Two things separate a real system from a demo — when to ask a human, and what to do when something breaks.
For anything with real stakes — money, a customer message, a record change — the system pauses for a human instead of guessing.
Good automation doesn't only handle the happy path. It knows what to do — and who to tell — when something goes wrong.
Grouped by what they do in a real system. Hover for detail.
Proven in production, working daily, or actively learning — filter to explore.
LEDP · 2020–2021
Foundation program — the API-integration base behind my automation work.

BSc in Computer Science & Engineering. I design the pipelines that qualify leads, answer customers, and close the loop — so teams stop copying and start shipping.
Dhaka · Remote (GMT+6) · sohag@sohaggain.com
Production systems and AI agents — full source on GitHub.
Multi-agent assistant for email and calendar from text or voice, with contact lookup and memory.
Documents into Pinecone as embeddings, then grounded answers with memory-enabled semantic search.
Answers service questions, qualifies leads, detects booking intent — with human handoff for edge cases.
Not adjectives — here's what you're getting.
Start with the bottleneck, not the tool — so the system fixes what's slowing you down.
BSc in CSE — APIs, data, and logic under the workflow, not just drag-and-drop.
AI for judgment calls, deterministic automation for everything else.
Discovery → design → build → test → handover. One owner, no handoff gaps.
Remote, hybrid, freelance — let's figure out what actually needs automating.