Analyst Portfolio: Decision Architecture — Where Standard Approaches Fail
These are not showcase projects. Every system presented below is actively used today in a real company — as part of day-to-day management, controlling, or investment processes.
Origami Effect combines the role of financial analyst and decision systems architect. The outcome is not reports or presentations — it is systems that transform how companies operate: from manual reporting to real-time performance steering.
The projects below include financial models for investors and banks, advanced financial-operational models, controlling and management accounting systems, dashboards built with React and MongoDB, data automation in Python and VBA, and ERP integrations. Every project was created in response to a specific business problem — without templates and without off-the-shelf solutions.
What makes this portfolio different from standard analytics projects?
Origami Effect delivers a system — a tool the company can use independently, one that updates with the data and answers questions before management even asks them.
Core characteristics shared by every project
Private equity mindset — Origami Effect originates from working with PE and VC funds. This means approaching data not like a technical analyst, but like someone who had to extract investment decisions from that data. Different questions, different priorities, a different level of expectations toward numbers — and a different understanding of what truly creates company value.
Rapid understanding of the problem — clients do not need months of explanations or lengthy onboarding processes. One good meeting is enough to understand where the problem is and how to address it. This comes from years of working with companies across different industries and at different stages of growth.
Single point of responsibility — every project is handled by one person. Not a team, not a department, not a project manager standing between the analyst and the client. This ensures full understanding of the problem, fast decision-making, and direct communication.
End-to-end execution — from problem to working system. Every project covers the full cycle: understanding the business problem, designing the architecture, building the model or system, integrating operational data, creating the visual layer, and transferring knowledge. No handoffs between analyst, developer, and consultant. One person understands the whole system — and is responsible for the whole system.
Tools I would want to use myself — every project passes through one filter: is it intuitive? does it truly work? is it something you can rely on? There is no room here for “showcase solutions” — only for systems tested and validated in real-world operations.
