Experience
Andrei Lisikov's experience is best understood through increasing responsibility: from software and architecture decisions to product and engineering leadership, company-wide operations and transaction responsibility.
The selected evidence below distinguishes employment, company leadership, external enterprise engagement and strategic advisory mandates. It does not imply that every named organization was an employer or client endorsement.
Before taking on full company leadership, Andrei built technical and delivery depth across complex enterprise project environments in automotive, mobility, robotics and industrial technology.
WiredMinds — technology, product and company responsibility
Relationship
CTO and later Managing Director of WiredMinds; current company leader after WiredMinds became part of Dealfront.
Context
WiredMinds is an established B2B SaaS business in website-visitor intelligence and sales technology. Its next phase required more than an isolated engineering upgrade: product, platform, data, operating structures, commercial priorities and company economics had to develop together.
Leadership and accountability
Andrei progressed from leading technology to leading product and platform direction, engineering and infrastructure. He also carried company-wide accountability across data, customers and partnerships, commercial initiatives, finance and operations.
Decisions and ownership
- Modernized platform and infrastructure foundations while maintaining the operation of an established product.
- Developed engineering and release capability together with data and management visibility.
- Connected product packaging and portfolio decisions with customer segments, enterprise integration needs and commercial priorities.
- Led beyond technology across customers, partnerships, marketing initiatives, finance and company operations.
Qualitative change
The work strengthened the product and operating foundations of the business, expanded the product portfolio and its commercial possibilities, and returned WiredMinds to profitability. The company subsequently completed a successful acquisition by Dealfront.
Business relevance
This is the clearest evidence of Andrei's central differentiation: architecture and engineering judgment applied under product, commercial and full company responsibility.
Public corroboration
WiredMinds product-portfolio announcement · WiredMinds and Dealfront
Related Perspective
Modernize, re-platform or rebuild: what evidence should decide?
Dealfront acquisition — diligence through integration
Relationship
Andrei represented the company side as Managing Director of WiredMinds. Dealfront was the acquirer; Creathor Ventures, WiredMinds' main shareholder, owned transaction negotiations.
Situation
The acquisition required a coherent company view across technology, product, finance, legal matters, organization and operational risk. After close, many of the same facts and decisions became inputs to integration.
Responsibility
Andrei was the primary company-side executive across legal, financial and technology due diligence. His scope included coordinating information and buyer questions across architecture, software, infrastructure, security, data and privacy, product, technical debt, the engineering organization, vendors and costs, together with the wider company-side legal and financial workstreams.
Continuing ownership
After the acquisition, his responsibility continued into key integration topics spanning people, product, data, commercial systems, customer continuity and AI.
Business relevance
The experience links transaction readiness with post-close operating responsibility. Diligence is not presented as a checklist or sponsor-side credential; it is part of understanding a business deeply enough to carry decisions into integration.
Public corroboration
Dealfront acquisition announcement · Independent transaction announcement by YPOG
Mercedes-Benz environment — enterprise architecture and delivery
Relationship
External technology engagement in the Mercedes-Benz environment. This was not direct employment by Mercedes-Benz.
Context
Connected-mobility and commercial-vehicle initiatives brought together customer-facing software, enterprise platforms, data, privacy and multiple delivery parties.
Responsibility
Andrei worked across architecture and technical coordination for connected-vehicle, digital-assistant and B2B commercial-vehicle contexts. The work required translation between product intent, enterprise architecture, privacy-by-design, delivery dependencies and operational constraints.
Qualitative change
The engagement expanded his responsibility from designing systems to coordinating complex technology decisions across organizations and delivery boundaries.
Business relevance
This experience provides enterprise-scale context for later company leadership: how to create decision clarity where product, architecture, risk, vendors and delivery have different owners.
Earlier enterprise & industry experience
Before taking on full product, technology and company responsibility, Andrei built his technical foundation across complex enterprise project environments. Selected environments included BMW, SIXT, ABB Robotics, KUKA, Bosch and TÜV SÜD across automotive, mobility, robotics and industrial technology.
The work progressed from software development through architecture, enterprise integration and complex multi-party delivery. It formed part of the technical foundation for his later product, engineering and company leadership.
Applied AI in industrial software and product strategy
Selected technology mandates in Switzerland extend Andrei's operating experience into two distinct AI decision contexts: controlled product capability in industrial software and agentic-AI product and business-model work.
The related Perspective When industrial AI should not ship examines the production boundary between probabilistic capability, deterministic validation and human accountability.
Perspectix AG
Relationship
External strategic technology advisory mandate for Perspectix AG.
Situation
Perspectix develops sophisticated industrial configuration software in which product rules, data, traceability and maintainability matter as much as an AI demonstration.
Responsibility and decision scope
Andrei evaluated the feasibility and product implications of AI-enabled natural-language input and configuration suggestions. The work considered product logic, data quality, explainability, integration, maintainability and economics.
Business relevance
The central decision was not whether AI could produce an impressive result. It was where AI could become a controlled, maintainable product capability in a rule-heavy environment.
Zurich-based MarTech venture
Relationship
External strategic technology mandate. The company remains anonymous.
Responsibility and decision scope
Andrei contributed to an agentic-AI platform, product strategy and AI-enabled business models, including questions of platform architecture, product direction and commercial logic.
Business relevance
The mandate connects emerging AI capability with the decisions required to turn it into a coherent product and business—not a collection of tools.
What connects the work
Across these contexts, the recurring progression is from technical possibility to accountable company decision:
- understand the architecture and constraints deeply enough to challenge assumptions;
- connect product and platform choices with customers and commercial priorities;
- build organizations and operating structures that can execute the decision;
- understand the financial and transaction consequences;
- remain responsible after the decision moves from plan to operation.
For the career progression behind these examples, read the profile.