Experts

Evidence needs
more than one perspective.

Technology, people and analytics specialists examine the same question from different directions. Senior review connects the findings, challenges assumptions and clarifies what leadership should decide next.

Michal is the accountable lead. The proposal defines which experts participate and their bounded responsibilities. This is a scoped investigation, not full-time staffing or a substitute executive team.

Experts

A senior team for one connected investigation.

We examine technical constraints alongside how work is organized and how performance is measured. The team brings these findings together in one scoped map, diagnosis and action plan.

Technology & Systems

Michal Barodkin

CTO at Ancient Remedies; founder of HeartScan and NeuroEdit. MBA.

Leads architecture, systems, data and AI investigation, connecting technical evidence to commercial priorities.

Reviews findings with HR and analytics and prepares technical verification and handover within the agreed scope.

Michal Barodkin on LinkedIn (opens in a new tab)

People & Organization

Andrei Zhurauleu

HR lead with leadership experience at BotConversa.

Reviews roles, ownership and how work moves between teams.

Stakeholder interviews, role-brief context and handover ownership within the agreed scope.

Andrei Zhurauleu on LinkedIn (opens in a new tab)

Analytics

Sergey Kadomsky

Head of Analytics; user-behavior analytics and audience research at Wargaming (2012-2018).

Examines metric definitions, reporting logic and the data behind decisions.

Checks competing explanations and the data needed to distinguish them within the agreed scope.

Sergey Kadomsky on LinkedIn (opens in a new tab)

Michal is the accountable lead, coordinating the investigation and joint review. Expert participation, responsibilities and interview scope are agreed in the proposal; the diagnostic does not provide full-time staffing.

Client-controlled environment

Your sources. Your access boundaries.

Work takes place in a Google Cloud environment provisioned and controlled by your company. We agree selected sources, permissions, exclusions, recipients, and retention arrangements before starting.

Model API boundary

External processing is explicit.

Model requests use client-supplied API access and an agreed provider configuration set not to retain request data. Approved requests may leave your GCP environment for that provider's API. Client control does not mean data never leaves the environment.

Read the data-handling boundaries

The right scope first

Bring the decision your team needs to make.

Discuss your situation