About

A small Glasgow engineering team building for hotel operators.

LodgingMods is the trading name of Clydebridge Software Ltd, a software company in Glasgow, Scotland. We build plug-in modules that sit alongside — never inside — hotel property-management systems and license them per month, per property.

Who we are

Both founders came from hotel operations before writing code full-time. We spent years explaining to owners and finance directors which third-party tool was worth its licence next to the native PMS feature set — and which was duplicating a function already shipped. Eventually we started writing the ones we thought were honestly missing, and licensing them to the operators who had asked for them.

The company is Clydebridge Software Ltd, Scottish-registered under company number 15102839 at 7 West Nile Street, Glasgow G1 2PR, Scotland, United Kingdom. Directors: Iain McAllister, Priya Shah.

How we work

Every module we publish is written against a vendor's official API, with a scoped credential the operator mints inside their own PMS console. We do not ask for logins, we do not shadow-login, and we never touch the core PMS configuration.

Every module release ships with a change-log and a regression-test summary against the PMS vendor's current release notes. The first run of any writing module is supervised by the engineer who authored the connector; one supervised cycle is included at no extra cost.

What we refuse to do

  • We do not take a percentage of your room revenue or your bookings. The licence price is the whole price.
  • We do not accept paid placement for a module we have not actually built — the catalogue reflects what the engineering desk has shipped, not what we hope will sell.
  • We do not run marketing retainers or growth consulting. We are a software company that writes connectors and support them.
  • We do not resell PMS vendor products. We license our own modules, which work on top of yours.

Where we sit in the stack

The native PMS vendor and their own first-party modules remain your system of record. Our modules read what they need over the API and, where applicable, write back the same way. If something our module writes conflicts with a change your team made manually inside the PMS, the manual change wins — we never overwrite a human-made edit without an explicit audit entry explaining why we would need to.

Contact

Editorial notes, module requests, security disclosures and press: [email protected]. Scottish/UK business hours: +44 141 628 0719.

Basket 0