Skip to main content
Request a demo
Request a demoPart of Katalyst House

Technology recommendation policy

A software recommendation should survive the referral fee.

Katalyst advises on hospitality systems and may, in future, hold referral or reseller relationships with some vendors. This page states how those two things are kept apart, so a client can judge a recommendation on its reasoning rather than on trust alone.

Current position

Katalyst currently holds no formal technology partnerships, reseller agreements or referral arrangements. No vendor pays Katalyst, and no recommendation made today carries compensation of any kind. The systems named under Selected Systems Experience are products the team has operated, configured, implemented, migrated or evaluated in current and prior roles — that is experience evidence, not a commercial relationship, and none of those vendors is a Katalyst partner.

If that changes, this page changes with it, and the disclosure below becomes active rather than hypothetical.

How a recommendation is made.

01

Requirements come before products

A recommendation starts from the commercial decision the system is meant to improve, the data it has to hold, the workflow it has to support and the people who have to use it. A shortlist assembled before those are written down is a preference, not a recommendation.

02

Realistic alternatives are considered

Including the alternative of changing nothing. A recommendation that never compares the incumbent, a cheaper option and doing without has not been tested against the only question that matters: whether the change is worth its cost and disruption.

03

Software cost and implementation cost are separated

Licence fees are the visible number and rarely the largest one. Migration, integration, configuration, training, parallel running and the internal time to adopt a system are stated separately, because a cheaper licence with a heavier implementation is frequently the more expensive decision.

04

Fit, integration, data portability and total cost govern the choice

Specifically including what happens on exit. If the data cannot be extracted in a usable form, the real cost of the system is not its annual fee — it is the cost of never being able to leave.

05

Partnership does not equal recommendation

A commercial relationship with a vendor never makes that vendor the default answer. Where a relationship exists and the product is genuinely the right fit, the relationship is disclosed and the reasoning is shown. Where it is not the right fit, it is not recommended.

06

No vendor is called a partner before formal acceptance

Not "in discussion", not "applied", not "we use it". A partnership is a written acceptance from the vendor, and until that exists no partner status, tier or mark appears anywhere — on this site, in a proposal or in a pitch.

The disclosure, if a relationship ever exists.

Katalyst may receive referral or reseller compensation from selected technology providers. Any commercial relationship is disclosed. Recommendations remain based on business requirements, implementation fit, total cost, integration needs and commercial value.

It is published here in advance deliberately. A disclosure written after money starts moving is a defence; one written before is a standard. If a relationship is ever entered into, it will be named on this page and in the proposal that relies on it — not disclosed only if someone asks.

The reasoning behind decision-first systems selection is set out in Hospitality systems fail at the decision, not the software, and the capability itself sits under Technology & Automation.