We build the half of business travel nobody solved.
Buying a flight was solved a long time ago. What was never solved is everything around it: the approval, the policy, the receipts, the report and the close.
Mission
A business trip should end with a closed report — not with a folder of receipts and a finance team working the weekend.
ITNA puts the request, the approval, the booking, the spend and the close into one flow: the company keeps the control and the data, and the person travelling keeps their evening.
Who is building it
We are a small product team building one thing rather than a suite of modules. The rules we hold ourselves to are written here because the product is written by the same rules.
We only show what exists
Anything not built yet is labelled as not built — on the landing page, in the product and on this page. Where a screen is still a placeholder it carries a "soon" chip, not a promise.
The close is the product
Most tools stop at the booking. We start where the finance team starts: the document, the tax treatment and the report that has to survive an audit.
Local where it matters
Currencies, tax rules and accounting formats are not a settings screen — they are a per-market implementation. We build them market by market instead of pretending one format fits everyone.
Where we are
ITNA is built in Tashkent — for companies whose people cross borders and whose books still have to close under local rules.
Tashkent
Where the product is built, and where we meet the companies we are building it with.
Wherever your people fly
We design for companies whose teams travel constantly and whose books still close under local rules — exactly the gap the global platforms leave open.
Several languages, several currencies
Because the companies we build for already work in several of each — not because a translation layer was bolted on afterwards.
See it on your own trips
The fastest way to judge ITNA is to watch it run one of your own routes.