Co-owner, CEO and CIO experience inside a real operating business.
// OWNER × SYSTEM ARCHITECT
Business experience before technology.
I work directly with business owners because I have sat on the same side of the table — as a co-owner, CEO and CIO responsible for people, money, operations and growth.
Today I turn that experience into commerce, CRM, back-office and AI systems that fit the business rather than forcing the business into a software template.
// THE OWNER'S PERSPECTIVE
A business system is valuable only when it improves capacity, control or economics.
Employees at the scale of the group under management.
Different commercial models, internal operations and a proprietary ERP.
Applied mathematics, finance, business administration, TACIS and technical programmes.
// EXPERIENCE AS A SYSTEM
Three layers. One way of thinking.
The value is not a list of past positions. It is the combination of analytical training, operating responsibility and the ability to turn business logic into working technology.
Analytical thinking
Applied mathematics and programming created the habit of decomposing complex situations into objects, relationships, rules and measurable constraints. Finance, business administration, TACIS and technical programmes added the economic and managerial context.
The owner's side
As a co-owner, CEO and CIO, I worked with B2B and B2C models, a group of up to 600 employees and the daily reality of sales, finance, operations and organisational change.
Technology as leverage
Building a proprietary ERP and management processes showed where standard software is enough and where custom logic creates real advantage. Tenderate applies that judgement to client systems today.
// WHAT THE CLIENT GETS
Less translation. More working system.
Direct owner-to-owner work keeps the business question, architecture and implementation in one area of responsibility.
Economics before features
We begin with how the company earns, where capacity is lost and what change can justify the investment.
Architecture without ceremony
A proven platform is used when it saves time and money. Custom development is used where business-specific logic matters.
One context from idea to launch
The person who studies the business remains responsible for system logic and the final result instead of handing the task through layers of roles.
Specialists where they add value
Partners and focused experts join openly for their part of the project without forcing the client to fund a permanent delivery structure.
Evolution after launch
A working system is supported and developed through flexible arrangements matched to the client's needs, pace and resources.
// PUBLIC PRACTICE
Ideas tested in real projects.
I publish in English, Russian and Latvian, speak with business owners about practical digitalisation and AI, and use public writing to explain the trade-offs behind architecture decisions.
// DIRECT CONVERSATION
Start with the business. Then design the system.
Tell me what the company wants to change and what currently blocks growth. I will help frame the problem and propose a realistic next step.
WHATSAPP / +371 25 123 661 ↗↗