Watch demoAI voice agents for CRM & ERP
Phone agents that identify the caller, answer order and stock questions, book appointments, and write everything back into HubSpot.
LiveKitHubSpotPostgrespgvectorPythonGitHubFull Stack AI Engineer
I build the ones that do. Voice agents that answer the phone and write to a CRM, assistants that answer from a company’s own documents, and the evaluation and deployment underneath them that keeps working on the days nobody is watching.
How I work
I built the specialists-behind-a-router architecture everyone recommends for voice agents, measured it against a single agent, and deleted it. Same eval score, 2.3x slower on the first turn, plus two failure modes the split introduced.
Every agent I ship has eval cases that name the tool it must call, the tools it must not, and what the answer has to contain. They run from the command line and fail loudly, which is the only reason the comparison above was possible.
Reads happen immediately. Writes wait. An assistant that can send email will eventually misread something, so nothing that changes state runs unattended, and the confirmation lives in the data model rather than in a prompt.
Containers, TLS, CI that deploys on push, health-gated rollout and one-command rollback. I hand over the runbook, not just the repository. A system nobody can operate is not finished.
About
I’m Aziz, a full stack AI engineer with six years of shipping software other people depend on, across pharma, financial platforms and enterprise systems.
I work across the whole thing. Backend at close to senior level, and frontend from high-traffic applications down to the responsive interface someone actually uses. Most of what I have built sits where a product meets the messy systems around it: a CRM that has to stay correct, an ERP that owns the numbers, a queue that must not process the same request twice.
I have been building with language models since 2023, when I shipped an OpenAI plugin with fine-tuning and chatbots to a paying WordPress audience. Now it means agents: voice agents that answer the phone and write to the CRM, assistants that answer from a company’s own documents, the evaluation harnesses that decide which design survives, and the deployment underneath all of it. The interesting problems are the same ones they always were, and the model is rarely the hard part.
I like fixing things, building things, and delivering on time.
What I work with
Experience
Graphnoe, own practice, remote
Uravo, remote
Stylemixthemes, remote
WP Webhooks, remote
Zmarket, Tashkent
Selected work
Watch demoPhone agents that identify the caller, answer order and stock questions, book appointments, and write everything back into HubSpot.
LiveKitHubSpotPostgrespgvectorPythonGitHub
Watch demoAnswers from a company's documents and reaches into Gmail, Calendar and Drive, proposing every write before it makes it.
ClaudeLangGraphFastAPIpgvectorDeepgramGitHub
Watch demoA form submission becomes a Slack message a coach can claim, without two coaches claiming the same one.
AWS LambdaSQSDynamoDBHubSpotSlack
Recruiter and candidate messaging with attachments, on a platform handling thousands of records.
ReactReduxLaravelAWS S3MySQLContact
Tell me what it needs to do and which systems it has to reach, and I’ll tell you whether it’s worth building.