Softwr

Travel · head to head

Egencia vs Little Hotelier

Egencia logo

Egencia

Travel

Corporate online booking and travel management from Amex GBT for mid-market and enterprise programmes

From
On request
Rated
-
Little Hotelier logo

Little Hotelier

Travel

SiteMinder owned front desk and distribution system for properties under twenty rooms

From
On request
Rated
-

The short version

  • Each has a real cost: Egencia pricing is per transaction and offline touches cost several times an online booking, so a programme with many complex multi-leg itineraries pays far more than the headline online fee suggests.; Little Hotelier the product is capped by design at small properties, so a hotel growing past roughly twenty rooms faces a migration rather than an upgrade, usually into SiteMinder plus a separate PMS.
  • They diverge on capability: Egencia covers Policy and approval engine, Little Hotelier covers Simplified front desk.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Egencia and Little Hotelier actually diverge.

Attributes where Egencia and Little Hotelier differ
AttributeEgenciaLittle Hotelier

Identical on both: starting price (On request), pricing model (quote), free tier (No), platforms (Web, iOS, Android), user rating (Not yet rated), category (Travel).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Egencia

  • Policy and approval engine
  • Negotiated rate loading
  • Traveller tracking
  • Agent support
  • Concur Expense integration
  • AI booking assistant

Only in Little Hotelier

  • Simplified front desk
  • Channel management
  • Direct booking engine
  • Payments
  • Mobile app
  • Guest communication

What people use each for

The jobs each tool is most often brought in to do.

Egencia

  • A company of several hundred travellers wanting negotiated hotel rates without paying for a high-touch TMCnot Little Hotelier
  • A finance team standardising on SAP Concur that wants booking data pre-populating expense reportsnot Little Hotelier
  • A multi-country employer needing consolidated duty of care reporting on where staff are travellingnot Little Hotelier
  • An organisation moving off a regional TMC and wanting one supplier across Europe and North Americanot Little Hotelier

Little Hotelier

  • A ten room guesthouse where the owner works reception and wants OTA sync without a separate channel manager contractnot Egencia
  • A hostel needing reliable Booking.com and Hostelworld connectivity more than deep property management featuresnot Egencia
  • A rural B and B replacing a spreadsheet and manual OTA extranet updatesnot Egencia
  • A small property already comfortable with SiteMinder support and wanting one bill for distribution and front desknot Egencia

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Egencia

  • Pricing is per transaction and offline touches cost several times an online booking, so a programme with many complex multi-leg itineraries pays far more than the headline online fee suggests.
  • It is now a service tier inside Amex GBT rather than an independent supplier, so a competitive process that shortlists both Egencia and Amex GBT is not really two bids.
  • Regional content and service quality are uneven, and companies with travellers in smaller markets often find local fares and hotels missing from the tool and end up going offline.
  • Implementation to load negotiated rates and configure policy typically runs months, and rate loading errors surface as travellers seeing the wrong prices rather than as a clean failure.
  • Because the platform underwent a relaunch on new architecture, customers migrating from the older Egencia stack have faced feature parity gaps and retraining during the transition.

Little Hotelier

  • The product is capped by design at small properties, so a hotel growing past roughly twenty rooms faces a migration rather than an upgrade, usually into SiteMinder plus a separate PMS.
  • Reporting is limited to basic occupancy and revenue summaries, which leaves owners exporting to a spreadsheet for anything an accountant or lender asks for.
  • Rate and package logic is simple, so properties with seasonal packages, meal plans or complex tax handling end up adjusting rates manually.
  • The non-distribution integration list is short, so accounting, door lock, POS or CRM tools outside the small supported set have to be handled by rekeying data.
  • Pricing is banded by room count and paid monthly per property, so an operator with three small properties pays three subscriptions with no consolidated view worth the name.

Pricing, plan by plan

Egencia

On request
  • Egencia$undefined/year
    • Per-transaction booking fees, online and offline rates differ
    • Optional annual platform or management fee
    • Implementation and rate loading charges

Little Hotelier

On request
  • Little Hotelier$undefined/month
    • Monthly subscription banded by number of rooms
    • Booking engine and channel manager included
    • Card processing charged per transaction

Which should you pick?

Choose Egencia if

  • You need policy and approval engine.
  • You work on Web, iOS, Android.
  • You also want negotiated rate loading.

Choose Little Hotelier if

  • You need simplified front desk.
  • You work on Web, iOS, Android.
  • You also want channel management.

Questions people ask

Is Egencia or Little Hotelier better?
Neither clearly leads. Egencia starts at On request and Little Hotelier at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Egencia or Little Hotelier?
Egencia starts at On request and Little Hotelier at On request.
Does Egencia or Little Hotelier run on more platforms?
Both run on Web, iOS, Android, so platform support will not decide this one for you.
What is Egencia best used for?
Egencia is most often used for a company of several hundred travellers wanting negotiated hotel rates without paying for a high-touch tmc, a finance team standardising on sap concur that wants booking data pre-populating expense reports, a multi-country employer needing consolidated duty of care reporting on where staff are travelling, an organisation moving off a regional tmc and wanting one supplier across europe and north america. Of those, a company of several hundred travellers wanting negotiated hotel rates without paying for a high-touch tmc and a finance team standardising on sap concur that wants booking data pre-populating expense reports are not what Little Hotelier is typically brought in for.
What can Egencia do that Little Hotelier cannot?
Egencia covers Policy and approval engine, Negotiated rate loading, Traveller tracking, Agent support. Little Hotelier covers Simplified front desk, Channel management, Direct booking engine, Payments.

Answered from the vendors’ own pages

Egencia: Is Egencia still sold under its own name?

Yes. Amex GBT bought it in 2021 and kept the brand, relaunching it in 2026 with a conversational AI assistant and a Concur Expense integration.

Little Hotelier: Who owns Little Hotelier?

SiteMinder. It is the small property product line of the same company that sells the SiteMinder channel manager.

Egencia: How is it different from Amex GBT itself?

Egencia is the more self-service, lower-touch tier of the same company, aimed at mid-market programmes; Amex GBT proper is the high-touch enterprise service.

Little Hotelier: What happens when the property outgrows it?

Most operators move to a fuller PMS and keep SiteMinder for distribution. Expect a data migration rather than a plan change.

Egencia: Does it replace an expense system?

No. It books travel and feeds data to expense tools such as SAP Concur; you still need an expense product.

Little Hotelier: Does it include a channel manager?

Yes, built on the SiteMinder network, which is the main reason to choose it over other small property tools.

Little Hotelier: Can one login manage several properties?

Each property is a separate subscription and the multi-property view is thin, so operators of more than two or three properties usually look elsewhere.

Share

Related pages

Other head to heads