Hi Ahmed — the “build, test, deploy, monitor, maintain” part of your post is the part I care about most, so here is exactly where I sit against your list.
What I have in production:
- n8n as the orchestration layer. DispatchAI (GitHub - MAhsaanUllah/DispatchAI · GitHub) runs seven authenticated webhook flows (create booking, check availability, find customer, reschedule, cancel, booking automation) behind a shared secret, with idempotency keys and conflict checks so a repeated request cannot double-book, bounded retries, error branches and a notification outbox. Workflow exports are version-controlled and the README documents what each flow connects to. 71 tests run in CI.
- Voice agents end to end. The same DispatchAI system is driven by an ElevenLabs voice agent alongside a React dashboard, so I have built the caller side of a system like your example: intent captured, details collected, booking written through the API, confirmation sent.
- LLM APIs and webhooks: OpenAI, Claude, Gemini and local models through Ollama; webhook signature verification; structured output validated with Pydantic and Zod before anything executes.
- Databases and deployment: PostgreSQL with row-level isolation, SQLite, Redis, Docker, Linux and VPS deployment, GitHub Actions CI, plus monitoring through structured logs, retries and an outbox so a failed step is visible instead of silent.
- Lead handling and messaging: a live WhatsApp agent (tarkabot.online) that qualifies incoming messages in Roman Urdu and English, structures them into orders or bookings, and hands off to a human when intent is unclear. 32 tests.
Straight about the gaps: I have not used Retell, Vapi or Twilio yet — my voice work is ElevenLabs, and my telephony-adjacent work is WhatsApp through an Evolution API bridge. The auth, webhook, booking and handoff patterns carry over, and I would rather name that up front than pretend.
How I work: sandbox first with test credentials and synthetic data, workflow exported as version-controlled JSON, documentation covering what it does, what it connects to and how to maintain it, then maintenance after launch. I keep scope written down and flag risks early rather than at the deadline.
Available 20+ hours per week, PKT (UTC+5), and I am looking for exactly this: one team, ongoing client work, not one-off tasks. Happy to start with a small paid piece so you can judge the quality before anything longer.