Career evidence, management cases, technical depth, and selected systems
Belgrade, Serbia
I help organisations make technology economically useful: increase revenue, reduce operating cost, remove critical dependency on individual employees and vendors, and give management clear control over systems, workload, spend, and risk.
My background combines 18+ years across founder-led businesses, banking, enterprise IT, and public-sector systems. I take responsibility not only for architecture, but for the operating consequences of technical decisions: ownership, adoption, continuity, cost, delivery, and maintainability.
This repository is the evidence layer behind that positioning — resumes, career history, management cases, technical proof, and project case studies.
Read the Markdown CV · DOCX · PDF · LinkedIn
General entry points: Short Resume · Portfolio Index · Detailed Experience
- Helped a service business achieve approximately 10× revenue growth in about three months after redesigning customer intake, operations, and product presentation; growth was organic, without paid advertising. Case study
- Reduced routine client-service work from hours to minutes through internal systems, integrations, and automation. Case study
- As part of the management team at ZIL, contributed to the anti-crisis turnaround that brought the organisation out of approximately RUB 30m in accumulated debt; within IT, focused spending on operational value and replaced unmanaged support with measurable service operations. Detailed experience
- Extended the useful life of approximately 150 workstations through targeted upgrades and licensing cleanup, and reconciled 800+ accounting and physical asset records, enabling formal write-off of approximately 100 missing or unusable assets. Detailed experience
- Moved 100+ employees to secure remote work during COVID without interrupting operations. Detailed experience
- Coordinated technology requirements and delivery with 100+ IT specialists across 100+ cultural institutions without direct line authority. Primary CTO CV
- Replaced a 5-hour, single-user reporting export in a city-scale information system with web-based generation typically completing in 1.5 seconds to 1.5 minutes and available to authorised users across institutions. AIS MosRazvitie
- Consolidated field operations and client workflows while migrating approximately 70,000 historical documents into a structured backend. Exit Lead
- Built an IT operating model at ZIL that remained stable after my departure and through subsequent leadership changes. Detailed experience
My recurring pattern is Transparency → Efficiency → Growth.
First, make the technology operating model visible: who owns what, where work is stuck, what systems and vendors matter, what they cost, and where the risks are. Then stabilise the critical function. After that, decide what should be automated, integrated, replaced, built, or scaled.
Typical problems I am brought into:
- delivery slows while technology cost rises;
- IT becomes a black box and management cannot connect spend to value;
- responsibilities are unclear across employees, teams, contractors, and vendors;
- critical processes depend on spreadsheets, chats, manual handoffs, or individual memory;
- key systems depend on one employee, contractor, or platform;
- CRM/ERP exists, but people continue to work outside it;
- management lacks visibility into workload, bottlenecks, service quality, risk, or the real cost of change;
- a working legacy environment needs modernisation without operational breakage.
| Question | Evidence |
|---|---|
| Can he run technology as a business function? | Management experience cases · Executive positioning · Detailed experience |
| Can he lead through both direct authority and a cross-organisational matrix? | Primary CTO CV · Detailed experience |
| Can he design teams and reduce key-person dependency? | Primary CTO CV · Management experience cases |
| Can he turn operational chaos into governed systems? | Management translation layer · Portfolio |
| Can he operate across executives, users, technical teams, and institutions? | Detailed experience · AIS MosRazvitie |
| Can he remain technically credible and hands-on? | Technical delivery positioning · Portfolio |
| Can he use AI without turning engineering into uncontrolled prompt-and-pray delivery? | AI-native delivery · PromptlessPress |
| Is there proof beyond employment history? | Public engineering projects · Portfolio index |
- Dobri Visarun — service-business automation and restructuring associated with approximately 10× organic revenue growth and routine handling reduced from hours to minutes.
- AIS MosRazvitie — industry-level information system across 100+ institutions, combining reporting, analytics, governance, integrations, and user adoption.
- Exit Lead — field operations, client workflows, automated reporting, and migration of approximately 70,000 historical documents.
- Andronyevskaya ERP — self-hosted operational system with role-based workflows, Telegram Mini App access, QR-linked assets, real-time tasks, and automation.
- PromptlessPress — AI-assisted generation system with reproducible execution flows, structured prompts, debug tooling, and engineering guardrails.
- Markdown Drive — WYSIWYG Markdown tool for Google Drive, HTTPS sources, and local files with shared theming plus client-side PDF and semantic DOCX export. Built from concept to production in approximately one week and published in the Google Workspace Marketplace, demonstrating fast product delivery through architecture, UX, OAuth/Drive integration, document rendering, export pipelines, testing, and deployment. Live
- RSLive / «Инструкция по Сербии» — maintained evidence-oriented knowledge system with a separate content source of truth, semantic indexing, editorial governance, and automated publishing. Live · Source
- humanizer_russian — source-aware Russian editorial engine with deterministic linting, provenance, conflict handling, CI integration, and controlled model evaluation. Source
- Supabase Project Starter — reusable Supabase engineering baseline for human and AI-agent delivery, with source-of-truth boundaries, shared helpers, SQL patterns, and deployment-aware rules. Source
- WeWeb Component Starter — reusable Vue/WeWeb component engineering kit covering schema/runtime/editor contracts, platform APIs, and advanced component patterns. Source
- tgs.py — Telegram operations toolkit with structured exports, automation scaffolding, packaging, licensing, and an early desktop GUI. Source
Direct leadership of specialised IT teams plus indirect functional coordination across 100+ IT specialists / 100+ institutions · organisational design with specialised roles, explicit ownership, and adjacent backup coverage · technology strategy and architecture · IT operations and service management · hiring, onboarding, mentoring, and team development · budget, procurement, vendor, and contractor management · delivery and cross-organisational prioritisation · business-process analysis and automation · ERP/CRM implementation and adoption · information security, continuity, privileged-access recovery, and access governance.
PostgreSQL Supabase SQL REST APIs JavaScript TypeScript Python Node.js Docker Linux NGINX Git/GitHub n8n Make OpenAI API WeWeb Xano Active Directory GLPI VMware
The stack is supporting evidence, not the positioning. The recurring responsibility is deciding what the business should own, automate, integrate, modernise, or stop paying for — and carrying those decisions through implementation and adoption.