Contracted travel agencies
Digitally connected travel agencies trading on negotiated rates, allotments and credit terms held as structured contracts, not a shared rate sheet.
TESSMA Holdings · United Arab EmiratesA single booking touches ten systems.
A single booking touches ten systems.
TESSMA makes it one.
Contracting, revenue, finance and operations working from one record — so a rate change, a contracted term and a settlement line all point at the same booking, on the same day.
- Built for
- Hotels, groups & commercial partners
- Delivery
- Cloud, multi-tenant
- Registered
- United Arab Emirates
- Markets live
- Coverage — to confirm
The core business
Hotel contracting first. Commercial operations second.
TESSMA’s first job is contracting — negotiating and holding hotel rates, allotments and terms as structured agreements, not a rate card in a PDF. Its second job is managing that contracted supply commercially for trusted business buyers, kept closed to the open public market and priced only on the terms each buyer actually holds.
- A hotel contracts its inventory in once, with TESSMA
- TESSMA vets and onboards the buyer side of the trade
- Every buyer sees only the rate and terms they negotiated
- Contracted
- Not open market
Corporate travel accounts
Companies with negotiated corporate programmes, where volume terms and credit apply automatically at the point of booking.
Offline & local agent networks
Smaller, community-based travel agents who transact by phone and email rather than through digital channels — brought onto the same contracted terms as every other buyer.
The ecosystem
Not fifteen products. One system with sixteen surfaces.
Most hospitality software is bought one problem at a time, then wired together afterwards. TESSMA starts from the opposite end: one commercial record, and every capability reading from it. Select any domain to see what it does and what it touches.
TESSMACommercial core
Commercial Operations
One rate, every channel
Rates, availability and inventory publish from a single record.
Platform
The commercial picture, on whatever screen you have.
Revenue managers work in spreadsheets at a desk. General managers check pace on a phone between meetings. Reservations teams live in a queue all day. Same data, three very different jobs.
TESSMA is built so the interface changes and the numbers do not.
- Rate, inventory and restriction changes apply once and propagate
- Every figure carries the rule and the source that produced it
- Role-based access, so finance and reservations see what they should
- Same record
- Desk, tablet, phone
Who it is for
Three sides of the same transaction.
Hotels & resorts
Sell the right room at the right rate
Independent properties and managed hotels that want commercial operations, pricing and reporting to agree with each other without a weekly reconciliation meeting.
For hotelsCommercial partners
Book on the terms you agreed
Agencies, tour operators and corporate buyers who need contracted rates, credit terms and settlement to hold from search through to invoice.
For commercial partners
Groups & operators
Compare properties honestly
Multi-property owners and management companies that need one definition of performance across a portfolio, not one per hotel.
For groups
Built on Trust.Driven by Excellence.
Two sentences we are willing to be measured against. Trust is what a partner extends before the first booking. Excellence is what keeps it there after the thousandth.
- Change once
- Publishes everywhere
Commercial Operations
Demand arrives from everywhere. Inventory should not care.
Demand may arrive through a global agency, a corporate programme or a wholesale contract. Each of those has different terms, and most systems treat them as different worlds.
TESSMA keeps one inventory position and applies the terms of whoever is asking. The hotel sees one availability picture. The buyer sees the rate they contracted.
- Channel-neutral inventory with rate rules resolved per buyer
- Restrictions and stop-sells honoured in the same pass
- Every published change written to an audit trail
Revenue
A price you can explain is worth more than a price you cannot.
Revenue teams are asked the same question every week: why is this rate what it is? If the answer takes an afternoon to assemble, the rate stops being defensible.
TESSMA shows pace, constraints and the rule that produced the number in the same view — so the conversation with an owner, a GM or a buyer takes minutes.
- Every rate
- Shows its rule
What the platform covers
Commercial, financial and operational, in one place.
Commercial Operations
One inventory position, published to the commercial channels a property actually sells through, with the terms of each buyer applied at request time.
Commercial Marketplace
A contracted marketplace where commercial partners see what is genuinely bookable to them, at the rates they hold.
Revenue & commercial intelligence
Pace, market position and channel mix, with the rule behind every recommended price kept visible.
Finance & payments
Bookings, commissions and settlement carry one reference from quote to ledger, so month-end reconciles.
Connectivity & API
Documented, versioned interfaces for the systems a property already runs and the partners who build on top.
Operations & automation
Recurring commercial and service tasks run on schedule, each with an audit trail of what ran and why.
Artificial intelligence
Useful when it shows its work.
Hospitality does not need a system that guesses confidently. It needs one that drafts the proposal, summarises the account, flags the contract clause — and shows exactly which data it read.
TESSMA’s assistants sit inside the workflow rather than beside it, and every output is attributable, reviewable and reversible by a person.
- Drafting and summarisation for commercial and contracting work
- Anomaly and exception flags on live commercial data
- Human approval retained on anything that changes a rate, a term or a payment
Analytics
Two teams, one definition of the same number.
Most reporting disputes are not disagreements about performance. They are disagreements about what was counted. Finance nets commission; the commercial team does not. Both are right, separately.
TESSMA holds shared metric definitions at the platform level, so a figure means the same thing in a revenue meeting as it does in a board pack.
- Shared definitions across commercial operations, revenue and finance
- Drill-through from any summary to the underlying bookings
- Exports that keep the definition attached to the data
- One metric
- One definition
- Every action
- Attributable
Trust
Trust is an engineering decision before it is a marketing one.
A partner hands TESSMA their rates, their contracts and their money. That is not a relationship that survives on assurances.
So access is scoped narrowly, administrative actions are recorded, financial calculations are centralised rather than repeated, and nothing important happens without a trace of who did it.
- Role-based permissions enforced at the service layer, not the interface
- Audit records for contract, rate and payment changes
- Data separation between tenants as a structural property, not a filter
Technology
Boring infrastructure, so the commercial layer can be ambitious.
The interesting part of TESSMA is what it lets a commercial team do. That only works if the layer underneath is unremarkable: typed, tested, versioned and observable.
We would rather ship a smaller surface that reconciles than a larger one that needs explaining.
- Partner model
- Contract first
Partnership
We would rather sign fewer agreements and keep all of them.
Commercial partnerships fail in the same place every time: the commercial terms and the technical integration are agreed by different people, six weeks apart.
TESSMA treats a contract as structured data from the first conversation, so what was negotiated is what the system sells.
- Terms, allotments and conditions captured in structured form
- One onboarding path for commercial, technical and finance sign-off
- Named ownership on both sides for the life of the agreement
Global outlook
Built in the Emirates, for markets that never stop trading.
TESSMA is registered in the United Arab Emirates — a market where a single hotel routinely serves leisure, corporate, wholesale, government and crew demand in the same week. It is an unusually demanding place to build hospitality software, which is the point.
Multi-market by default
Currency, tax treatment and language handled as configuration rather than as separate deployments.
Regional compliance
Built with regional tax and invoicing obligations treated as first-class requirements.
Time zones that overlap
Operations designed around markets whose business days do not line up.
Offices
Locations — to confirmRegistered address and operating locations are published on the Company page.
Next step
Bring one real problem. We will show you where it lives in TESSMA.
No slide deck first. Tell us the rate that will not update, the report two teams disagree about, or the reconciliation that takes a week — and we will walk through it in the platform.