Business Automation & CRM Specialist. I build CRM systems, automated workflows, and AI lead capture on Make, Zapier, n8n and HubSpot — so your team stops doing coordination by hand.
I help service businesses replace manual coordination with systems that run on their own.
Over the past 4+ years I've built CRM architectures, automated workflows, and integrated communication channels for consulting firms, recruitment agencies, construction companies, and B2B service providers — teams of 15 to 30 people, where every missed handoff costs money.
WHAT I WORK WITH
CRM platforms (HubSpot, Pipedrive, and custom-configured systems) · Workflow automation (Make, Zapier, n8n) · Airtable · API integrations · Cloud telephony and PBX setup · AI chatbots for lead capture and qualification · Electronic document management · Business process design
SELECTED RESULTS
Built a full CRM system from scratch for a 20-person consulting firm covering 7 roles: a 9-stage sales pipeline, cross-department kanban boards, automated task assignment and handoffs between sales, legal, product and accounting. Delivered in 4 months. It's still running in its 4th year, and the client stayed on for ongoing support — then referred me to their business network, which became the foundation of my consulting-sector expertise.
Designed and deployed a 25-line cloud telephony system with CRM integration, call recording, IVR and routing for a recruitment agency. Two weeks, full-time. First-touch contact rate went up 13%, and personal phone numbers disappeared from the sales process entirely.
Migrated a construction company off a failing telephony provider mid-outage: 38 numbers, full routing and call forwarding rebuilt in 1.5 weeks while the business was losing calls daily. No clients lost.
Built a two-channel AI lead capture system — website quiz plus Telegram bot — on Make and n8n, handling around 170 leads per month with automatic qualification and routing to the right salesperson. Average time to a qualified conversation dropped by 14 minutes.
Rebuilt document workflow for a company processing 150–400 documents monthly across 5 roles: rule-based routing by document type and counterparty, approval chains triggered by amount and entity, automated deadline control and escalation.
HOW I APPROACH A PROJECT
I start with process mapping, not tools. Before anything gets built I want to understand how work actually moves through your team — where it stalls, who waits on whom, what gets re-entered by hand. On the CRM project above, that meant seven strategy sessions with the owner before a single automation was configured.
That's the difference between a system your team uses and one they quietly work around.
If you can describe where your process breaks down, I'll tell you honestly whether automation is the right fix — and if it is, what it would take.
Work Terms
AVAILABILITY
Full-time, Monday to Friday. Based in GMT+7 (Vietnam), with reliable overlap into European business hours and early morning US Eastern. I'm flexible on scheduling calls outside those windows when a project needs it.
HOW PROJECTS RUN
Discovery first. Before any quote, a short call to understand your current process and what's actually broken. No charge for this.
Written scope. You get a clear document covering what will be built, what it will do, timeline, and price. Nothing starts until you've approved it.
Milestones. Larger projects are broken into stages with a deliverable at the end of each. You see working results as we go, not just at the end.
Documentation and handover. Everything I build comes with documentation, and I train your team to operate and adjust it. You should not need me on retainer to keep your own system running.
RATES AND PAYMENT
Hourly work: $25/hour, logged and reported transparently.
Fixed-price projects: quoted after discovery, invoiced by milestone. For projects over two weeks I ask for a deposit at the start.
All payments through Guru's SafePay.
COMMUNICATION
I reply within one business day, usually much faster. Regular written progress updates during active work — you'll never have to ask where things stand. Calls by video conference, and day-to-day written updates.
Working language: English and Russian.
WHAT I DON'T DO
I'll tell you if automation isn't the answer. Sometimes a process is broken in ways software won't fix, and building on top of it makes things worse. I'd rather say that upfront than take the project.