Your people already know where to click.
They lose time understanding what they clicked.
ToolTip AI is one Windows app that reads whatever is under the pointer: what the control is, what it is for, what happens if you press it, and text in another language translated in place. The reading runs with capabilities Windows already ships — UI Automation, hardware-accelerated OCR, system speech synthesis — so there is no vision service to rent and nothing leaves the machine unless you decide it does.
The enterprise line builds on that same engine. You describe the workflow that costs hours — a legacy ERP nobody documents, a quality checklist on a shop floor, a console operators stare at all shift — and we deliver the tool that fits it: same reading layer, your vocabulary, your screens, your rules. No card up front, no subscription to escape later.
The engine, before the menu.
Every custom build starts from four primitives that are already proven in the shipped apps. What changes for you is what sits on top.
It identifies the control
UI Automation. Which element is under the pointer, which process owns it, what its state says. Instant, free, and it never reads password fields.
It reads what the control hides
Windows OCR on-device. When the element does not expose its text, a region around the pointer is recognised on your hardware: games, PDFs, video, remote desktops, terminal screens.
It speaks the answer
System speech synthesis. Local voices, adjustable rate and tone. Nothing to configure in the cloud and nothing to pay per character.
It explains, if you want
Bring your own key. Gemini, OpenAI, Azure OpenAI, OpenRouter or Claude. The key is encrypted with DPAPI against your Windows user and travels only to the provider you chose.
It moves text across devices
LAN pairing with a QR code. Phone to PC in under 30 ms on the local network, no intermediate server. That is the Bridge primitive.
It stays put
No Dixi3 servers in the middle. There is no backend collecting your screens. Air-gapped and on-premise deployments are supported configurations, not exceptions.
A la carte: what we actually build.
Pick one or combine them. Each block is quoted separately, and each one inherits the reading layer instead of reinventing it.
Domain glossary and verdicts
The reader answers in your jargon, not generic Windows help: your part numbers, your error codes, your ticket states, your machine names.
Operator HUD for one screen
A pinned panel for the software your team lives in — SCADA, MES, ERP, hospital records, trading blotters — with the three facts that matter pre-computed.
Guided procedure player
Step-by-step prompts that follow what the operator is looking at, with read-aloud for hands-busy work and a log of what was actually done.
Screen-to-document capture
Point at a field or an error and it lands in a report, a work order or a compliance file. OCR plus your template, no retyping.
Onboarding copilot
The tooltip becomes training: every control explains itself the first time it is touched, and the gaps show you where new hires keep stopping.
Accessibility build
Voice-first navigation for staff who cannot use small controls, with contrast, dwell timing and pacing tuned per person and saved per machine.
Air-gapped edition
All primitives local, optional offline model, updates delivered as a signed package you approve. For regulated and OT environments.
SDK and white label
The reading layer as a library inside your own Windows application, with your brand, your installer and your licensing.
Integration bridge
Events out to your systems: what was read, what was answered, what was ignored. Webhook, database write or file drop, your choice.
How an engagement goes.
You send the brief
The form below takes five minutes. It asks for the workflow, the software involved, how many seats and what may leave the building.
We reply with a written scope
Within two business days: what exists already, what has to be built, what we would not promise, and the price per block. [email protected].
Pilot on one real screen
A short paid pilot on your machine or yours alone, measured against the time it saves. If it does not, you stop there.
Rollout and licence
Perpetual licences for the pilot outcome, an update channel you control, and documentation for whoever maintains it after we hand over.
- Response time
- 2 business daysquote is written, not a call funnel
- Reply address
- [email protected]cc: [email protected]
- Pilot length
- 2–4 weeksone screen, one team
- Licensing
- Perpetual, per seatno usage metering
- Platforms
- Windows 10 (19041+) / 11, x64Android companion via Bridge
- Data handling
- Local by defaultDPAPI at rest, your provider in transit
- Invoicing
- MXN · USD · EURtax ID on request
Read before you brief us.
- We say no to automation that replaces judgement. This engine explains and transcribes; it does not decide, approve or sign on behalf of a person.
- We do not screen-scrape for surveillance. Anything that logs what an employee reads, beyond the diagnostic events agreed in the scope, is out.
- Password fields stay unread. That is a hard rule in the shipped product and it holds in custom builds.
- Nothing is claimed that Windows does not provide. If a feature needs a model we do not run locally, you will see it priced as a separate decision.
Tell us the workflow that hurts.
The more concrete the screen, the more concrete the quote. Everything marked optional genuinely is.
Prefer plain email? Write to [email protected] with the same headings. The form exists so nothing gets lost between a subject line and a thread.