About this account

Source: UVISION founder Michael Kisilenko’s account, supplied on 14 October 2026 and summarized on our homepage. The client remains anonymous. Business figures below are company-reported, not independently audited here.

The starting point: systems that constrained change

The client was a traditional tour operator working with outdated software. According to the founder’s account, those systems could not support the business change the company needed, and annual turnover was approximately $1 million.

The engagement became a long-term development relationship spanning the customer-facing business, agent interfaces and internal operations. That scope is central to the story: the website was one part of a wider software platform.

The scope: customer channels and internal operations

UVISION became the company’s development arm and built the technology serving several parts of the business. The reported scope spans external interfaces and internal business software.

  • A B2C website for the customer-facing business.
  • B2B interfaces for human and automated agents.
  • An internal ERP and APIs connecting software capabilities.
  • MCP and the continuing move toward AI-agent workflows.

What changed during the relationship

The founder reported annual turnover growing from approximately $1 million to approximately $10 million within two years and approximately $20 million after five years, while UVISION built and continued developing the platform.

These are business figures reported by UVISION, not an isolated measure of engineering impact. They should not be read as proof that software alone caused revenue growth, or as a forecast for another client.

The durable result described by the account is an ongoing development relationship covering both business-facing channels and internal systems.

The next stage: AI within a continuing system

MCP and AI agents are the current direction of continued development. They extend a relationship that already covers customer channels, business interfaces and internal software.

For another traditional business, the relevant question is where a new capability fits into the systems and processes it already depends on. UVISION brings that question into ongoing development, with the appropriate plan defined for each business.

Common questions

What did UVISION develop for the tour operator?

The reported scope includes a B2C website, B2B interfaces for human and automated agents, an internal ERP and APIs, with MCP and AI-agent workflows part of the continuing direction. The account describes a long-term development role rather than a single website project.

Are the revenue figures independently verified?

No independent audit is presented here. The figures come from UVISION’s founder account: approximately $1 million initially, $10 million within two years and $20 million after five. They describe business growth during the engagement, not a measured causal effect of software alone.

Does this case establish a measured result from AI agents?

No. MCP and AI agents are described as part of the continuing direction. This account does not report a measured AI outcome, a specific production rollout or agent autonomy. Those claims would require separate evidence.