Look, then check again
Looking at one screen and opening another to check happens again and again, every day.
KIND CONNECT
Your software stays as it is. KAI reads the screen and clicks only what it has verified.
For teams using business software without integration features. KAI works by reading the screen on a dedicated PC.
Pricing is a quote, given after we confirm the scope.

Today
Looking in one program, checking in another.
Looking at one screen and opening another to check happens again and again, every day.
A program with no API, or one that won’t open it, is stuck before any integration even starts.
A wrong line is found much later. Who changed what, and when, lives only in someone’s memory.
What you need is not a faster hand, but a hand that checks and keeps a record.
How it works
It reads the screen a person would read, and presses only the right place.
KAI takes a picture of the dedicated PC’s screen and reads the text and its position.A spot becomes a candidate to press only when the expected text, position, screen state and surrounding clues all match.Just before pressing, it checks once more that the screen is the same, then presses only once. After pressing, it reads the screen again.If it can’t tell which one is meant, it doesn’t choose. It doesn’t press, and hands the case to staff.
We first check whether it works with your program’s screens.
Features
It all happens on the screen. Your program doesn’t change.
Pressing a button isn’t the end. KAI reads the program again and marks something “Confirmed” only when the record is there.
Time, screen, action and result are kept for every task, in order. Screenshots, text that was read and customer names are never recorded.
When staff ask for a handover, KAI’s actions are blocked at once. “Staff can use it” appears only after KAI is confirmed to have stopped. A person and KAI never operate one PC at the same time.
Each site gets one dedicated virtual PC for KAI to work in. Request, approval, setup, access check and task link: a person checks at every step.
Tell us the repetitive task you want to hand over.
What people decide
| People decide | KAI does |
|---|---|
| Which tasks to hand over | Reads and matches the screens of the agreed tasks |
| When to switch a task on. Only after four checks on site | Presses only what is confirmed, and reads again |
| Which one is meant when it’s unclear | Doesn’t choose, and stops |
| Whether to retry when it’s unknown if a press landed | Doesn’t resend on its own, and waits |
| Approving and ending a dedicated PC. Whoever requested it can’t approve it | Works only inside the dedicated PC |
| While staff are using the PC | Steps aside |
A KIND BIZ administrator checks the dedicated PC and the task before opening them, and a refusal always comes with a reason.
Start
Finishing one step doesn’t move you to the next on its own.
Tell us the systems you use, the tasks you repeat and your daily volume. A person will contact you.
Name · contact · business nameWe tell you what can be connected and which points need checking.
You receive: scope · points to checkThe site’s dedicated PC is opened in order: request, approval, setup, access check.
A person checks at each stepSite staff check the program version, install method, test data and whether remote access is allowed. Who checked, when, how and on what basis is recorded.
No task goes live until all four are confirmedWe start with one task on test data and widen the scope by reviewing the activity log.
Never tested first on live dataProof
Each promise is written down as a rule and checked in our own tests.
Confirmed on test business screens, on our own test PC. These are not results from a customer site.
Compare
Compared with staff moving between two programs by hand.
| Topic | Today · staff by hand | KIND CONNECT |
|---|---|---|
| Program | You keep using it | Left as it is. No API development needed |
| Who looks at the screen | Staff | KAI on a dedicated PC, moving only when sure |
| When it goes wrong | May be found much later | Matched before pressing, and the result is read back to confirm |
| When it’s unclear | A person judges each time | It stops without choosing. Staff decide |
| Records | Notes and memory | Time, screen, action and result, kept for every task |
| Getting started | Right away | Starts with a consultation, a scope check, then a pilot run |
If there is an API or a supported file exchange, that may be simpler. We check that first, in the consultation.
Security and data
The program stays as it is, and access and records are kept narrow.
Which PC belongs to which site is set only by an assignment table. One PC can’t be attached to two sites.
The dedicated PC is never exposed to the internet and is reached only through an approved management channel. It connects only when both the person and the device are verified.
Access passwords are read only at the moment they are used and are never kept in any record.
Screenshots, text that was read and names that were looked up are not stored. What remains is the time, the result, and a marker that points to which screen it was.
Staff handle only the sites they are assigned. If permission is withdrawn, even a control right already held is blocked at the next action.
We neither read nor write the data or internal connection features inside the program. Only what is visible on screen is handled.
A consultation request collects only your name, contact, business name and message. The purpose is the consultation, and it is kept for one year after the consultation ends.
FAQ
Windows programs that can be used by screen on a dedicated PC. Once we confirm the program’s name, version and install method, we tell you what can be connected.
It reads the screen, presses a button it has verified exactly, reads again, stops and hands the case to staff, and keeps a log. Which tasks can be handed over is decided together in the consultation, by looking at the program’s screens.
No API development is needed. But the program version, install method and test data have to be confirmed on site, and you need a vendor contact to ask when screens change.
If there is an API or a supported file exchange, that may be simpler, so we check that first in the consultation.
Before pressing, it matches the text, position, screen state and surrounding clues, and just before pressing it checks once more that the screen is the same. If it still can’t tell the result, it doesn’t resend: it stops and hands the case to a person.
We start on test data, not live data, and widen the scope by reviewing the activity log.
KAI works on the site’s dedicated PC. When staff want to use that PC themselves, they request a handover. At that moment KAI’s actions are blocked, and once KAI is confirmed to have stopped, it changes to “Staff can use it”. A person and KAI never operate one PC at the same time.
Reading accuracy is measured separately for each screen language, and KAI does not move on a screen that falls short of the standard. We check with the program’s real screens first, then set the scope.
There is no fixed price list. We give a quote after confirming the scope. In the consultation, start by telling us the systems you use, the tasks you repeat and your daily volume.
Once KAI is stopped, no further action goes out. Ending the use of a dedicated PC is handled by a KIND BIZ administrator, who records the reason. Contract terms come with the quote.
The activity log keeps no screenshots, no text that was read and no names that were looked up. What remains is the time, the kind of screen, the action and the result.
A consultation request collects only your name, contact, business name and message, and is kept for one year after the consultation ends.
We quote speed and volume only from what a pilot run measures on the target program. There is no figure we promise today.

Tell us the program you use and the task you repeat. We first confirm what can be connected.
Please give your name, contact details and business name. No passwords are needed.