Baseline first
Before a change we record the current state and a metric to compare later. Without it nobody knows whether the change helped.
About
Vis-Sol: automation, AI and websites for businesses, Toruń
We design, deliver and maintain solutions that take manual work off companies. Problem first, then change, then measurement.
Accountability
The architecture has an owner. So does the result.
Vis-Sol combines interface design, web systems, automation and VSA with a diagnostic approach: dependencies and constraints first, then controlled change, and finally measuring the effect. This makes solutions that can be maintained, developed and, if needed, safely stopped.
Headquarters: Toruń, 87-100, Poland. Service area: the Kuyavian-Pomeranian Voivodeship and all of Poland (remotely). The first call takes 15–30 minutes and ends with a concrete next step, not a sales deck.
We develop our own AI assistant platform, VSA (Vis-Sol Auto Assist). Each company gets its own separate environment and an assistant for one specific job. Vis-Sol maintains the platform.
About the author
Kamil Kosiorek „Kosior”
Business owner of Vis-Sol / Visuals and Solutions · author and owner of the whole process
Responsible for the entire process — from diagnosing the problem, through architecture and delivery, to maintenance and measuring the effect. Author of the concept, architecture and development of the VSA platform.
- Over 10 years of technical experience across the railway, technical, industrial and logistics sectors
- Specialist in railway vehicle operation and technical systems
- Vis-Sol developed since October 2025 — from the first websites for local service providers to tools, automation and VSA
- 01 · Observation
- 02 · Diagnosis
- 03 · Dependency analysis
- 04 · Controlled change
- 05 · Measuring the result
Good practices
Six principles we stick to.
Every change can be rolled back
Critical changes have a backup, checkpoint or rollback path. An experiment must not turn into an outage.
The system reports its state
Logs, statuses and simple diagnostic signals are part of the solution, not an add-on after a failure.
Minimal complexity
We do not add services or AI just because they exist. Every component has a clear role.
One failure does not stop everything
Simplified mode, an alternative channel or manual work where it matters.
Every element has an owner
It is clear who owns the data, process, updates, monitoring and shutdown of the solution.
How we work
Four steps we never swap
- 01
Discovery
Current state, constraints, users and the concrete result to achieve.
- 02
Direction
Choosing the architecture, interface, data and the way the solution will be validated.
- 03
Delivery
Staged implementation, change control and a working check before the scope grows.
- 04
Measurement
The result decides whether we develop, maintain or close the scope.
Is there a process that eats up your team's time?
Describe it in your own words. We will come back with a concrete first step, scope and price.