Alexander Zakharov / Business Architect
I map how work actually happens, find where data goes stale, and build a practical control layer — invoices, inventory, tools, statuses, notifications, upcoming payments, and management analytics — without unnecessary weight.
By the numbers
Figures from active and pilot workflows at a manufacturing company. Company names and operational data are anonymized.
The problem
ERP, spreadsheets, email, and chat can hold plenty of information. Yet leaders still have to ask: where is that invoice, what is actually in stock, what is available to sell, what is already reserved, which payments are about to hit cash flow, and where the process is stuck.
I turn these gaps into event-driven systems: every action is recorded, status updates automatically, balances and summaries are calculated, and the right people get notified at the right time.
About
I'm Alexander Zakharov. I design and implement applied systems for operational accounting and management control — from invoice approvals and warehouse balances to cash flow and production workflows.
My work does not start with a tech stack or "let's build an app." It starts with the real process: who is involved, what events happen, where data goes stale, what decisions need to be made, and what picture leadership actually needs.
What I help with
Invoices, requests, approval routes, roles, statuses, files, comments, notifications, and action history. The system shows where a document is now and who owns the next step.
Event-based tracking of receipts, check-outs, returns, shipments, and write-offs. Current balances, replenishment thresholds, and alerts — without constant physical counts.
Operational invoices, recurring payments, expected inflows, and cash movement in/out. The system helps surface cash-gap risk before it becomes urgent.
Work planning, actuals capture, resource load, material availability, workstation readiness, and constraints — without a heavy ERP rollout.
Case studies
These were not demos — they ran as part of day-to-day operations: with users, documents, balances, notifications, and management decisions.
Roughly 150 unique invoices per month, 10 users, and 11 statuses — from review and approval to payment pending, paid, or cancelled. Email chains were replaced with a web system: files, comments, history, notifications, and analytics.
Outcome: statuses, overdue items, upcoming payments, and owners are visible in one place.
400 unique tools in 27 categories. Each month records about 230 check-outs and roughly 100 purchase or receipt events. Every check-out is posted to the production chat.
Outcome: full physical inventory cycles became rare; balances stay current through daily use.
214 unique finished-goods SKUs. Receiving, shipping, and write-offs are captured through forms; operations flow to Telegram, and weekly summaries show movement stats.
Outcome: on-hand stock and sellable availability are clear without manual reconciliation.
Financial layer
A dedicated automated workbook pulls data from operational workflows and gives owners and executives a consolidated view with drill-down into details.
This is not post-factum bookkeeping — it is a planning tool for payments, inflows, and upcoming risk. The module is evolving toward earlier cash-gap warnings.
Interfaces
A useful system reflects the current state of the business: statuses, amounts, dates, owners, action history, overdue items, and upcoming decisions.
Test environment fragments with mock data. Real scenarios; anonymized counterparties and amounts.
Engagement formats
One or two sessions: who is involved, what events happen, where data is lost, what leadership needs to decide, and which first automation step is worth taking.
A fast operational loop for events, balances, thresholds, notifications, and management visibility — without heavy custom development.
When you need roles, statuses, files, action history, notifications, access control, and a proper interface for daily use.
I do not replace ERP or spreadsheets for the sake of replacement. If current accounting works, I build a control layer alongside it that closes the management gap.
Approach
Who is involved, what events occur, where data is lost, and which manual reconciliations keep the process alive.
Roles, statuses, transitions, constraints, owners, thresholds, exceptions, and management questions.
The shortest path from event to outcome — no extra complexity, but with real users from day one.
Audit trail, reports, overdue tracking, financial slices, and risk signals come after the base loop works.
The system grows based on what actually helps leadership, warehouse, production, and owners.
Who it's for
When to reach out
Contact
Message me on Telegram. A short note is enough: which process you want to review, where data is lost or outdated, who is involved, and what leadership needs to see.
Message on TelegramTelegram: @AlexZakharov. Best to start with one area: documents, inventory, payments, production, or another operational workflow.