Pavel Khaustov
I build AI systems that businesses actually use — agents that close deals, RAG knowledge bases that answer real questions, voice robots and bots that handle the work nobody wants to do manually.
I take them the whole way: research, design, frontend, backend, integrations, deployment. One person instead of a team.
Eight years of automating sales and marketing operations taught me what to build. A DevOps background makes sure it's still running on Monday.
~/AI Solutions
AI Solutions
Systems running in production. Built solo, end to end.
Corporate AI Portal — a Company OS
Task
Company knowledge and numbers lived in a dozen disconnected systems. A simple question — which campaign actually brought the money, why costs jumped in May — took days and three people to answer.
Solution
Built the whole thing solo: six services, 57 database models, 30 screens. Seventeen connectors pull from the LMS, web analytics with offline conversions, the mailbox, video hosting, uptime and cloud billing into one company database, and from there into a RAG layer an assistant reads directly over MCP. On top: AI reports on a schedule, sales attribution down to first touch, call-quality tied to revenue, and a built-in messenger with full-text search across messages and voice transcripts. The market now calls this category a company OS.
Coach Marketplace with AI Matching
Task
Build a marketplace from zero: match a person with the right coach, run the session, take the money, pay the coach — and stay inside the law while doing it.
Solution
Ran the entire project alone: research and design, then frontend, backend, database — 33 models. AI matching on vector embeddings reads what the user is actually asking for. Sessions run as in-browser video with background blur and noise suppression; group events have their own catalog, seat purchase and waitlists. Scheduling covers availability windows and exceptions; money covers packages, balances, promo codes, payouts and refunds across several acquiring providers. Plus the compliance layer marketplaces usually discover too late: published executor details with checksum-validated tax IDs.
Integrations That Do Not Exist Yet
Task
Sales and campaign data sat in an LMS that publishes no API for mailings. The numbers the company steered by were assembled by hand, and nobody could say which campaign actually brought the money.
Solution
Worked out the protocol and wrote our own access layer, then wired the data into the corporate portal and pushed payments back into analytics as offline conversions — so revenue could finally be attributed to a specific campaign. Supplier invoices are read straight out of the mailbox by a vision model and filed into the expense register. This is the part of the job that has no documentation: the system you must integrate with was never designed to be integrated with.
E-commerce AI Sales Agent
Task
Handle inbound sales conversations without a human on the other side.
Solution
An autonomous agent wired into the backend: it holds the conversation, checks inventory over API, and carries the customer through to the order. It runs the funnel with no operator involved and brings in $3,000–4,000 a month.
LLM-Powered Sales QA Pipeline
Task
Sales calls were reviewed by hand, which meant most of them were never reviewed at all.
Solution
A pipeline that transcribes call audio, analyzes the conversation with an LLM against the script and the actual outcome, then returns structured metrics for management and specific feedback for each operator. Weekly summaries flow into the company AI base, where call quality sits next to the sales funnel — so a drop in one can be read against the other.
A Second Brain the Assistant Can Write To
Task
Every AI session started from zero: re-explaining the projects, pasting context by hand, losing decisions made last week.
Solution
A task manager and notes base with its own Model Context Protocol server, so the assistant reads and writes the database directly instead of being spoon-fed context. Notes arrive by voice from Telegram and a model structures them; "ask the base" answers semantically across everything written. Kanban with realtime updates on top. Integration between AI and internal systems at the protocol level, not through ready-made plugins.
Voice Robots & Operational Bots
Task
Repetitive outbound calls and routine operational chores eating the team's day.
Solution
Voice robots that make the calls and act on the answers, plus Telegram bots for data collection, notifications and internal routines. The boring half of operations runs without anyone touching it.
Personal Finance AI Advisor
Task
Get useful answers about household money instead of typing receipts into a spreadsheet.
Solution
Receipts are caught straight out of the mailbox from four different senders, deduplicated by Message-ID and parsed line by line into product groups — so "where does the grocery budget actually go" has an answer. On top: planning with subscriptions and credit schedules, month-over-month analytics, and a RAG advisor over PostgreSQL with pgvector. Personal project, and the place where I test RAG patterns before taking them to client work.
~/About Me
About Me
Pavel Khaustov
AI Integration Engineer
For four years I ran technology inside high-traffic EdTech companies. My customers were internal — marketing, sales, e-commerce, launches — and the job was never to ship code, it was to make their numbers move. When a launch broke, everyone knew exactly whose fault it was.
That is where I learned the part most AI projects miss: the technology is rarely the hard part, the process around it is. These days I build the systems myself instead of managing people who build them — agents, RAG pipelines, integrations — then wrap them in containers, CI/CD and monitoring so they survive contact with real users. The market has a name for this shape of work now: forward deployed engineer — sit with the people who have the problem, build against their real data, stay until it is actually used.
If a process needs a human doing the same thing twice, it's a candidate for automation. If it's running in production, it's monitored.
Location
🇱🇹
Lithuania
Vilnius
EXPERIENCE
8
years in automation · 2 with AI
Philosophy
"The technology is the easy part. Understanding what actually needs automating is the job."
Fun fact
I run a bare-metal K3s cluster at home — mostly so I can host my own vector databases and run AI agents without handing my data to someone else’s cloud.
~/How I Work
How I Work
From business problem to running system
Understand the process
I start with how the work happens today: who does what manually, where the money leaks, what "done" looks like. AI applied to a broken process just breaks it faster.
Design and prototype
Rapid prototyping with LLM APIs, low-code orchestration (n8n, Make) and AI-assisted IDEs. Fast enough to throw away if the idea does not hold.
Build it properly
Frontend, backend, database, integrations, RAG layer. Written to be maintained, not demoed once.
Ship and keep it alive
Containers, CI/CD, monitoring, backups. Most AI projects die in the gap between prototype and production, and this is where the DevOps background pays off. Then I stay until the team is actually using it — a system nobody opens is a failed project, not a delivered one.
~/Live Infrastructure
Live Infrastructure
Most AI demos die the moment real traffic hits them. This is the part that keeps mine alive — a real cluster, running right now. Everything below pulls live data.
Kubernetes Cluster
Task
Run containerized workloads with zero-downtime deployments under unpredictable traffic spikes.
Solution
Self-hosted K3s on bare metal, deployed via GitLab CI + Helm. Namespace-isolated, heavily utilizing RBAC, and configured for aggressive auto-scaling.
Live pods from devops-portfolio namespace:
GitLab CI/CD Pipeline
Task
Fully automated build, scan, and deploy on every git push.
Solution
5-stage pipeline: test → build → Trivy scan → staging → manual prod gate. ChatOps bot sends Telegram approval request.
Monitoring Stack
Task
Full observability across the cluster.
Solution
Prometheus Operator scrapes metrics, Grafana visualizes, Loki + Promtail aggregates logs.
Disaster Recovery
Task
Automated backups with point-in-time recovery because staging always breaks.
Solution
Velero snapshots entire namespaces weekly to Cloudflare R2 (S3-compatible). Full cluster restore tested and verified in under 15 minutes.
~/Tech Stack
Tech Stack
AI & LLM
Claude API · OpenAI API · RAG · pgvector · Prompt Engineering
Automation & Integration
n8n · Make · Telegram Bot API · Webhooks · REST APIs
Development
Python · JavaScript/TypeScript · Nuxt · PostgreSQL · AI-assisted IDEs
CI/CD & Security
GitLab CI · GitHub Actions · Jenkins · Trivy
Orchestration
Kubernetes · K3s · Helm
Containerization
Docker · Docker Compose
Monitoring & Observability
Prometheus · Grafana · Loki · Promtail · Uptime Kuma
IaC & Config Mgmt
Ansible · Terraform
Networking & Ingress
Traefik · Nginx · Cert-Manager · Cloudflare
Cloud & Backups
Selectel · AWS · Hetzner · Cloudflare R2 · Velero
Version Control
GitLab · GitHub
~/Experience
Experience
AI Integration Engineer
5 Prism · EdTech / consulting
- ›Built the corporate AI knowledge portal end to end: portal → centralized company database → RAG layer → corporate Claude instance.
- ›Develop AI agents and bots for lead generation, sales and internal automation: voice robots, Telegram bots, Make / n8n scenarios.
- ›Designed and shipped the coach marketplace with AI matching solo — research, design, frontend, backend, database.
- ›Run the infrastructure behind it myself: Docker, Kubernetes, GitLab CI/CD, monitoring and centralized secrets.
AI Infrastructure (Personal Lab)
Self-Hosted Environment
- ›Self-host vector databases and run my own AI agents on hardware I control, without handing data to someone else’s cloud.
- ›Run a bare-metal K3s cluster with Traefik, Velero backups and Cloudflare in front.
- ›Built a Python ChatOps Telegram bot that gates production deployments behind an explicit approval.
AI Integration Lead
Wello AI
- ›Led the technical integration of the e-commerce AI sales agent and set up the autonomous funnels behind it.
- ›Built the LLM sales QA pipeline: call analysis → metrics reports for management, covering the whole department.
- ›Set up CI/CD and infrastructure for stable AI product releases, including the cloud cost decisions.
Head of IT / Automation & Integration Lead
Birchcenter · EdTech, systems integration
- ›Built the IT function from scratch for an EdTech platform and carried large product launches across RU and Kazakhstan.
- ›Designed fault-tolerant automated funnels for sharp traffic spikes — thousands of concurrent users on webinars.
- ›Integrated CRM, international payment gateways and SaaS services over APIs and webhooks across several geographies.
- ›Set up secured email infrastructure (SPF, DKIM, DMARC) for deliverability.
Technical Automation Engineer
Online Schools · EdTech
- ›Designed and automated marketing funnels by integrating CRM, payment systems and third-party services over APIs and webhooks.
- ›Automated routine sales and marketing processes, cutting the share of manual work.
- ›Administered infrastructure for mass email campaigns — deliverability and IP warm-up.
Education & Certifications
DevOps Engineering course · TeachMeSkills
March — October 2025Got a process that should have been automated last year?
Tell me how it works today and I'll tell you what can actually be handed to AI and what it would take. Working remotely — contracts, B2B, consulting.