Business Systems Analyst | CRM, API Integrations & Automation

Open to international roles · relocation ready · UTC+3

From messy requirements into working CRM, automation and AI workflows.

Business Systems Analyst with 3+ years of client-facing delivery experience across 37+ CRM, integration, automation and AI projects. I turn ambiguous stakeholder needs into AS-IS / TO-BE process models, BPMN flows, requirements, user stories, integration logic and production-ready systems.

Isty · Nov 2022 — present  ·  remote-friendly  ·  hands-on with n8n / APIs / CRM

Nikita Tsyzhman at work
how-i-work.ts Delivery loop
  1. Discovery Complete
  2. Requirements Complete
  3. Workflows & APIs In progress
  4. Testing Up next
  5. Rollout Planned
About

Between business process and working system

My work sits at the intersection of business analysis, systems integration and technical implementation. Across 37+ client projects, I have led discovery, mapped AS-IS / TO-BE processes, structured BPMN flows and user stories, defined acceptance criteria, and stayed involved through implementation, UAT, rollout and adoption.

I'm comfortable being the translation layer between customers, developers and AI specialists: business language on one side, APIs, webhooks, JSON and system states on the other.

  • Hands-on integrations. Real n8n workflow implementation, REST APIs, webhooks, JSON and data mapping — not diagram-only analysis.
  • Requirements engineering. Ambiguity becomes AS-IS / TO-BE models, BPMN flows, user stories, business rules and acceptance criteria.
  • AI that lands in operations. Voice and chat agent outcomes become structured statuses, CRM actions, routing and escalation logic.
  • Ownership through rollout. From stakeholder discovery and technical specifications to UAT, documentation and production validation.
Nikita Tsyzhman — portrait
Expertise

The toolkit behind delivered implementations

Business analysis

  • Requirements elicitation
  • AS-IS / TO-BE
  • BPMN
  • User stories
  • Acceptance criteria
  • Process mapping
  • UAT
  • Stakeholder discovery

Automation & orchestration

  • n8n
  • JavaScript Code nodes
  • Expressions
  • Conditional routing
  • Error / fallback logic
  • Validation

Integrations

  • REST APIs
  • Webhooks
  • JSON
  • Data mapping
  • OAuth concepts
  • API docs → logic

CRM platforms

  • amoCRM
  • Bitrix24
  • RetailCRM
  • Pipelines & stages
  • Deduplication
  • Lead routing

Voice AI & telephony

  • Voice agents
  • Chat agents
  • Status mapping
  • Sipuni
  • Calltouch
  • Asterisk / SIP

Data & reporting

  • SQL / PostgreSQL
  • Metabase
  • NocoDB
  • Metric validation
  • Reconciliation

Self-hosted stack

  • Docker
  • Caddy
  • Git
  • Ollama
  • DNS / certs / webhooks
Case stories

Selected work, told as stories

Real client implementations from my work at Isty — what was broken, what I built, and what changed for the business.

Case 01 · Retail · Voice AI

The flower company: from random calls to a revenue-generating voice robot

One of my clients, a flower company, had no call scripts at all. Their managers were handling incoming calls completely randomly, without any structure.

I developed a professional sales and service script for them, integrated it into a voice robot, and set up full automation between the robot and their CRM — including logging call results and automatic follow-ups.

The resulting system standardized the first line of communication, automated CRM follow-ups and surfaced previously unstructured customer demand. One of the insights from those conversations led the client to introduce balloons as an additional product category.

  • Voice robot
  • Sales & service scripts
  • CRM automation
  • Call-outcome logging
  • Follow-ups

A chaotic first-line process became a structured, automated workflow with consistent conversations, CRM-recorded outcomes and systematic follow-ups.

Case 02 · Healthcare education · AI chat agent

Prenatal support platform: from a 3-day callback to a one-minute qualification

A company in prenatal education and support for expectant parents came to us because their managers couldn't keep up with incoming leads. Everything was getting stuck, and they assumed the problem was simply low conversion.

I started by reviewing their traffic channels and how they handled them — then went through the process as a real customer. The finding: it took 3 business days from the moment a lead submitted a request until a manager actually called. In their industry, that's far too slow.

We proposed an AI agent for messengers that immediately qualifies the lead and answers questions in real time — literally within a minute.

3 days → ~1 minfirst response to a lead
~$0.10incremental AI cost per qualified lead
  • Messenger AI agent
  • Lead qualification
  • Traffic review
  • Customer-journey walkthrough

Managers stopped spending first-line capacity on spam, junk and non-target inquiries and could focus on qualified, higher-intent leads. The overloaded manual response process became an automated qualification layer with a first response measured in minutes rather than business days.

Case 03 · Healthcare · CRM rebuild

Dental clinic: rebuilding a CRM that four contractors left broken

A dental clinic came to us after trying 3–4 CRM contractors over a couple of years. Those vendors made daily operations slightly easier but never thought about marketing, conversions, CRM hygiene or analytics. As a result the CRM had become a messy notebook: to pull anything useful out of it you first had to clean the data — and even then you couldn't really trust it.

I started with an AS-IS review of the clinic's lead, consultation, treatment and analytics processes, then designed the TO-BE CRM model around simpler funnels, fewer required fields and automation-first state transitions.

The project was handed to me with full ownership. The target model deliberately reduced operational complexity: simpler funnels, the minimum required fields and controlled state transitions designed to reduce human error.

The whole system became highly automated. Operators only fill in 3–4 required fields and choose from short lists of 5–6 values. Managers can't move deals through the pipeline manually, can't create duplicates, and can't leave a deal sitting unqualified for an extra day — because if a patient with a toothache isn't contacted within minutes, they're gone.

Marketing channels were set up correctly, analytics were connected, and everything is reconciled with the clinic's medical software: when a visit happens and generates revenue, it shows up both in the sales CRM and in the final analytics.

  • CRM rebuild
  • Error-proof automation
  • Marketing channels
  • Analytics reconciliation

The result was a CRM where operational data could be trusted for day-to-day work, marketing attribution and downstream analytics instead of requiring manual cleanup before every analysis.

Case 04 · Services franchise · First major voice AI

Barbershop franchise: my first voice agent — still running four years later

A barbershop franchise came to us with a clear constraint: no budget for a call center — and the quality of typical call centers wasn't good enough anyway. This was before the flower-company project, so I consider it my first major project of this kind.

They had no script and no real understanding of how their incoming calls actually went — or how they should go. So I built everything from scratch: the conversation script, the follow-up documents sent after each call, the consulting logic, answers to slippery questions, and a map of unexpected questions callers could bring up.

4+ yearsin continuous production
Lower operating costthan the call-center alternative
→ Repeat engagement:the same client brought us into a similar implementation at his next company

The solution has remained in continuous production for four years. The same client later brought us into a similar implementation at his next company, providing a concrete signal that the original deployment delivered enough value to repeat the approach.

Experience

Three-plus years, one deep chapter

Isty · Business Systems Analyst

Nov 2022 — present
  • Lead technical discovery across 37+ client projects, translating stakeholder needs into AS-IS / TO-BE process models, BPMN flows, functional requirements, user stories, acceptance criteria and implementation tasks.
  • Build and troubleshoot integrations across n8n, amoCRM, Bitrix24, RetailCRM, telephony platforms, databases, AI services and external REST APIs using webhooks, JSON transformation, data mapping, branching and validation.
  • Designed and validated automated first-line support workflows handling requests from 2,500+ active end customers per month for a client, including routing, intent/status handling, CRM actions and escalation logic.
  • Coordinate client stakeholders, developers and AI specialists from discovery through testing and rollout; validate delivered behaviour against agreed scenarios and acceptance criteria.
  • Coordinate validation of CRM-derived operational reporting in Metabase, reconciling business logic, drill-down behaviour, duplicate/test records and metric definitions with client stakeholders.
  • Design reusable workflow patterns for lead/contact routing, deduplication, field normalisation, CRM state transitions, notifications and system-to-system synchronisation.
  • Create technical specifications, implementation notes and reusable workflow documentation so recurring solutions can be transferred, supported and extended instead of remaining one-off fixes.

B.Sc. Applied Informatics

University of Management "TISBI", Kazan

2018 — Jun 2022
  • Systems Analysis
  • Information Systems Design
  • Software Engineering
  • Database Systems
  • Computer Networks
  • Info Security
  • Project Management

Graduation project: design and development of a Hotel Information System.

Cisco Networking Academy

Foundational certificates

Earlier education
  • CCNA R&S · Introduction to Networks
  • CCNA R&S · Essentials
  • Introduction to Cybersecurity
Next step

Let's build something that actually works

Open to international Business Systems Analyst, Technical Business Analyst and integration-focused roles — relocation or remote-first teams where business analysis, CRM, APIs, automation and AI deployment intersect.

Timezone: UTC+3