Vladimir Tursin and the business of being asked back

A founder’s career can look unexpectedly like a staff directory. Vladimir Tursin’s includes sales manager, recruiting manager, support manager and project manager, all within Belitsoft, the software company he co-founded in 2004. There is a whole business tucked into that list: persuade someone to buy, find people to do the work, organize the assignment, answer the questions afterward. The chief executive’s title is shorter. The earlier job descriptions explain rather more.

Software offers plenty of occasions for a grand entrance. A working relationship has to survive ordinary Tuesdays. Tursin’s career is interesting in that less theatrical territory, where the customer already knows your name and has begun to discover whether your promises were sensible.

His professional writing stays close to such concerns: the full cost of an engineering team, the choice of a working arrangement, the protection of a customer’s idea. These are the questions around the code. They determine whether anyone is comfortable commissioning it.

A company learned one job at a time

Tursin started Belitsoft with Alexander Beresnyakov in 2004. His responsibilities now include strategy, key operations, partnerships and major accounts. The spread of his previous roles gives that executive brief a practical foundation. He has worked on several sides of the relationship a software services business must manage.

Consider the different questions those jobs contain. Sales asks what a customer needs and what the company can promise. Recruiting asks who can do it. Project management turns a commitment into an organized sequence of work. Support meets the questions that remain when the delivery has been made. They are distinct responsibilities, with plenty of opportunity for one department to misunderstand another.

The attraction of a founder who has crossed those boundaries is easy to understand. A contract eventually becomes somebody’s assignment. An assignment eventually becomes somebody’s experience of the company. The organizational chart may draw tidy lines; the customer experiences the handoffs.

Tursin also had responsibility for creating Belitsoft’s core values. His business philosophy gives customer service and added value a place alongside technical capability. That is a demanding position for a software supplier. It means the quality of the relationship belongs inside the definition of the work, where it can be tested by an actual customer.

“We build trust by doing our best to deliver what’s been agreed, plus a little more than expected.”

Vladimir Tursin

Two developers, a long conversation

One of Belitsoft’s learning-platform engagements offers a concrete example of the business Tursin helped establish. The collaboration began in 2007. The company supplied two .NET and SharePoint developers within two weeks of signing the contract, beginning work on a learning management system that would develop within Microsoft’s software environment.

The assignment had an intelligible purpose: let organizations deliver training and manage certification within the tools they use for work. A useful learning platform needs courses, assessments and a way to see how people are progressing. It also needs to fit the organization buying it. That last requirement can keep a development team busy for a considerable time.

Belitsoft describes the engagement growing to several dozen people and the customer’s platform reaching more than five million users. Those are the company’s reported project results. The users belong to the customer’s product; the development work belongs to a team. Tursin’s place in the story is as a co-founder of the business supplying that team.

The revealing detail is the span of the relationship. Starting with two developers leaves room for the customer to learn how a supplier works before the assignment expands. Continued development then asks different things of the relationship: accumulated product knowledge, coordination and support. A launch gets a date. Keeping a product useful gets a calendar.

The arithmetic around the code

Tursin’s software cost analysis takes a different route into the same business. It imagines a year-long project with ten engineers: an architect, two team leaders, two senior developers and five middle-level developers. The exercise compares the expense of assembling that team in different markets.

The published calculations draw on salary information from 2015 and 2016. They belong to that period, rather than a contemporary price list. What makes the article useful for understanding Tursin is the structure of the calculation. Salary is followed by the surrounding expense of running an engineering operation, including premises, equipment, recruiting and administration.

A buyer comparing developers can overlook the business that enables those developers to work. A desk, a hiring process and a project manager are less photogenic than a finished application. They still need to be provided. Tursin’s argument puts them back into the arithmetic.

It is an appropriate subject for someone whose career includes recruiting and project management. He has occupied roles that a simplified budget can treat as incidental. His example gives those functions a cost and makes the comparison more explicit.

The broader question is how much responsibility a customer wants a supplier to carry. A dedicated team, an individual specialist and a fixed deliverable ask different things of both parties. Belitsoft offers several engagement models. Understanding the arrangement is part of understanding the price. The smallest number on a proposal can otherwise acquire a surprisingly busy life in the footnotes.

An idea needs somewhere safe to land

A second article carrying Tursin’s byline addresses a difficulty that arrives before the first line of code. A customer has to explain an idea to the people being hired to develop it. The information that makes the assignment possible may also be information the customer wants to protect.

His discussion of intellectual property gives three kinds of document a central place: the agreement between supplier and customer, the nondisclosure agreement, and the employee confidentiality contract. It connects the relationship between companies to the responsibilities of the people doing the work.

That last step matters to the business argument. A company makes a promise through its authorized representatives, while its employees encounter the material needed to fulfill the assignment. Confidentiality has to reach the people who actually handle it.

The article also describes transferring rights in the developed software and delivering source code to the customer. These are concrete concerns for a buyer commissioning something the business expects to use and control. An enthusiastic presentation cannot settle them. They need to be addressed in the working arrangement.

The piece was originally published in September 2018 and carries a March 2026 update date. Its place in Tursin’s body of writing is telling: alongside the economics of building software sits the customer’s willingness to share the idea in the first place. Trust has an administrative department, and it is entitled to ask questions.

What the buyer bought

Belitsoft’s corporate history acquired another chapter in 2021, when Softline bought the business. The group acquired control on July 16. Belitsoft now describes itself as part of Noventiq, the subsequent name of Softline’s international business.

The acquisition brought together a team of more than 350 software development specialists at the time. The business had customers in the United Kingdom, United States, Israel and Denmark. The attraction was an existing capacity to develop software for customers across borders.

Those details help explain the kind of asset Tursin and his colleagues had built. A services business brings people, customer relationships and experience together. Its value depends on those things continuing to work in combination. An acquisition can place them within a larger organization; it still needs the underlying operation to function.

Tursin remains identified as CEO and co-founder in Belitsoft’s current leadership material. His stated remit continues to connect operations with strategic partnerships and key accounts. The company has changed its ownership context while his public role remains closely associated with running the business and its commercial relationships.

A little sea air

There is a welcome change of scenery in a sailing-event listing from the Belarus IT Companies Club. Tursin recalled an earlier yachting trip in Thailand with organizer Nikita Semenov and recommended the experience to fellow club members. The listing promoted a week in the Seychelles for IT entrepreneurs in March 2022.

His recommendation was for a way to spend time with others in the same business world. It is a small detail, but an enjoyable one beside the agreements and cost calculations. A software founder can have an opinion about a holiday without turning it into a theory of leadership.

The professional recommendations attached to his LinkedIn profile bring the story back to working relationships. Lars Vestergaard describes working with him from 2011 and emphasizes reliability, business judgment and the pleasure of his company. Marcus Wilson highlights responsiveness, helpfulness and communication in dealing with Tursin and his team.

There is something appealingly specific about that reputation. Being pleasant to work with becomes consequential when people have work to get through together. Across Tursin’s career, the same question keeps returning in different forms: can the relationship carry the assignment? After sales, recruiting, delivery and support, another project is a fairly concrete answer.