n8n workflows, Telegram bots, CRMs, integrations, self-hosted
infrastructure. I take subcontract work from agencies.
Available nowUTC+7 — 5–6h ahead of CETEnglish · Ukrainian · RussianDa Nang, Vietnam
Production, not tutorials
80workflows built
29running right now
973nodes across them
All of it runs on infrastructure I set up and maintain myself:
self-hosted n8n, PostgreSQL, Docker, Cloudflare. Not a managed account with
three demo flows. I'll walk you through the instance on a screen share.
One of the 80 — a moderation queue that lives in Telegram. An item is
pulled from the queue, previewed with its image, and the admin approves it, rejects it,
rewrites the text or swaps the photo. Every branch writes back to Postgres before the
post goes out. Pulled straight from the live instance — node names and wiring are
exactly what runs; only the layout is redrawn, because n8n scatters nodes across the
canvas and that does not fit on a page.
Interfaces
Clinic CRM — everything the owner runs the place with, in one placeDay schedule by doctor. A new appointment is one click on a slotAI assistant — takes and places calls, writes the outcome back to the cardMoney: income, payouts, balance — without a separate spreadsheet
Screenshots are from a demo instance with synthetic data — no real
patient or client records are shown anywhere on this page.
Sites
mtdk-ai.com — my own product, built and shipped end to end. This is the
page for online schoolsSame product, page for dental clinics. One codebase, a page per
vertical
Selected work
CRM for a language school
The school ran on a dozen Google Sheets — schedule, payments, leads, debts.
Every one of them maintained by hand. Replaced with a single system.
Leads from the web form and Instagram land in one queue instead of four places
Group scheduling, attendance, teacher load
Payment tracking with automatic reminders for unpaid months
n8n · PostgreSQL · Telegram Bot API · migration off Google Sheets
Telegram CRM with AI agents
A sales flow that lives entirely inside Telegram. The customer never leaves
the chat, and neither does the operator.
Button-driven qualification with session state in Postgres
LLM agents for classification and reply drafting, structured JSON output
Retrieval over the client's own documents (pgvector)
Handoff to a human with the full conversation as context
I work under your brand and do not approach your clients. Happy to sign whatever confirms that
Rate
$25/hour, or a fixed price per defined scope — whichever you prefer to work with
Availability
30 hours a week, starting immediately
Timezone
UTC+7. Work handed over in your evening comes back done in your morning
Handover
Documented workflows, credentials in your accounts, no lock-in on me
The client clause is listed first on purpose. It is the thing
agencies actually worry about with a subcontractor, and it deserves a straight
answer rather than a hint.