The API does not exist
QuickBooks Desktop, Sage 50 and most on-premise ERPs were built before integrations were expected. There is nothing to connect to — no endpoint, no webhook, no supported export for the screen your team actually uses.
Design partner program open · Montréal
No API.
No API.
No problem.
Twennyfour automates the software everyone else gave up on — QuickBooks Desktop, Sage 50, Citrix-hosted apps, old ERPs. AI interprets your command and plans the workflow, then our deterministic engine executes it identically every single time, on your own machine. No guessing.
We reply within 48 hours · No access to your data required
Vendor
verified
Bill no.
verified
Date
verified
Amount
verified
Save & Closesaved
idle
run #1,204 · identical to run #1
- QuickBooks Desktop
- Sage 50
- Citrix
- RDP
- SAP GUI
- AS/400
- Excel
- Dynamics GP
- CargoWise
- Oracle EBS
The gap
Every automation tool assumes a door that this software never had.
Integrations need an API. Scripts need selectors. Cloud agents need a screenshot budget. Meanwhile a person opens the window and types.
In Citrix, everything is a pixel
When an application is streamed to your desktop, the code runs somewhere else. There is no DOM, no accessibility tree, nothing to hook into. Automation tools go blind exactly where regulated industries keep their software.
Scripts break, quietly
Macros and RPA flows anchor to internal identifiers. One update moves a button, the script keeps clicking, and nobody notices until the month-end numbers are wrong. The fix always lands on the same person.
How it works
The engine doesn't guess. It learns, executes, and verifies.
01 — once
Learn
The engine studies your application once and builds a private map of it: where each field lives, what a saved record looks like, what an error looks like. That map stays on your machine.
02 — every run
Execute
Every run follows the exact same verified path, at the native speed of your machine. No screenshot sent to a cloud model before each click, no per-step AI cost, no surprises.
03 — every action
Verify
After each action the engine confirms on screen that the expected result actually happened before moving on. When the software changes, the run stops rather than guessing — the map is repaired once, then execution resumes.
The order is the product: nothing runs before it has been learned, and nothing continues before it has been verified. Read how the engine works →
Where it sits
Your books can't run on a coin flip.
Two generations of automation came before us. Both break — just in different ways.
| Traditional RPA | Cloud computer-use agents | Twennyfour | |
|---|---|---|---|
| Finds elements by | Internal selectors and object IDs | A model reasoning over a screenshot | A learned visual map of your screen |
| Inside Citrix or RDP | Blind — no objects reach the client | Works, slowly | Native — pixels are all it needs |
| Same result on run #1,000 | Until the next update | Never guaranteed | Guaranteed — same verified path |
| Cost per step | Licence per robot | A model call for every click | None — execution is local |
| Where your data goes | Depends on the orchestrator | Every screen leaves the building | Nowhere — it stays on the machine |
| When the UI changes | Breaks, sometimes silently | Improvises, sometimes wrongly | Stops, repairs the map, resumes |
Control
Built for people who sign off on the numbers.
Automation is only useful if you can explain what it did. Every run leaves a record you can watch, and you can stop it at any moment.
Runs on your machine
The engine and your application map live on the workstation or server you already use. Client files never leave the premises.
Every run is replayable
Each action is recorded with the screen it acted on, so a review means watching what happened rather than trusting a log line.
You keep the last word
Watch a run live, pause it, take the mouse back. Steps you mark as sensitive wait for your approval before they commit anything.
It stops instead of improvising
If the screen isn't what the map expects, the run halts and tells you which step and which field. A stopped run is cheaper than a wrong entry.
Built for
The teams still typing data into software from another decade.
CPA & bookkeeping firms QuickBooks Desktop · Sage 50
Bulk AP bill entry from vendor PDFs, client write-ups, month-end grunt work — automated directly inside QuickBooks Desktop Enterprise or Sage 50, including hosted sessions. No API exists for this software. We don't need one.
Freight forwarders & customs brokers TMS · ABI/ACE · legacy ERPs
Your team rekeys commercial invoices and packing lists into entry screens all day. The engine reads the documents and types them in — field by field, visually verified, with a full replay of every run for audit.
Citrix, RDP & virtual desktops Pixels are enough
When software is streamed to your screen, there is no DOM, no selectors, no integration surface — only pixels. That's exactly what the engine was built to see. If a human can operate it, Twennyfour can automate it.
The vision
AI is the brain.
Twennyfour is the hands and the eyes.
We separate thinking from doing. A model may reason, hesitate, even change its mind — execution should never miss. Our engine gives AI a body that acts on any screen exactly as instructed, while you watch in real time and always keep the last word.
It starts with business software. It doesn't end there.
Questions
The six we get asked every week.
Does Twennyfour need an API or a database connection?
No. The engine operates your software the way an employee does: through the interface on screen. If a person can run it, the engine can run it — including software that never shipped an API.
Does it work inside Citrix, RDP or a virtual desktop?
Yes. In a streamed session there is no DOM and no selectors, only pixels on your screen. That is exactly what the engine reads, so a hosted session is no harder for it than a local install.
How is this different from RPA tools like UiPath?
Traditional RPA anchors to internal selectors that break on every software update, and it cannot see inside a streamed session. Twennyfour works from what is on screen and confirms each result visually before continuing.
Is it an AI agent that decides what to do at every click?
No, and that is the whole point. AI is used at the start to understand your prompt and plan the task. Once planned, execution is strictly deterministic: the same verified path, every run, with no model call per click.
Where does my data go?
Nowhere. The engine runs on your machine and the map of your application stays on it. Your invoices, ledgers and client files never leave your premises.
What happens when the software updates and the screen changes?
The run stops instead of guessing. It halts safely and alerts you exactly where the interface broke. We believe a stopped run is infinitely better than a silent hallucination.
Design partner program
Give us your team's most hated 30 minutes.
Walk us through the daily task your team dreads most. We build a deterministic pilot on a test environment with zero risk to your data. If it fits, we deploy it with you as a design partner.