KLYKmanagement
Book a demo

The platform

Ten modules on one core.

Every module stands on its own. A venue can take Weddings and nothing else, or the staff side and not the sales side. They share a core, and they never require each other.

Included with any module

The core

Buy one module and this comes with it. Buy a second and it is already there, which is what makes the second module so much cheaper than the first.

Tenancy and properties

One account can hold several sites. A group with three hotels runs them side by side, with figures that roll up and permissions that do not.

Users, roles and permissions

Granular, per department and per module, enforced on the server rather than by hiding a menu. Staff see their world. A head chef sees the kitchen. The general manager sees everything.

A dashboard that fits the job

Widgets filtered by role, editable per role and per person within what that role allows. A kitchen porter and a sales coordinator sign in to two different screens.

Calendar and notifications

One engine for repeating and one off dates: licence renewals, repeating health and safety checks, bin days, birthdays. Every module feeds it, and reminders go by email and in the app.

Audit log

Who did what, and when. It is the difference between saying the check was done and showing it, which matters the day someone asks.

The modules

What each one covers

Live means in daily use at Whitley Hall. In build means the data is already in the platform and the screens are being written. Planned means exactly that, and we would rather say so.

01

Weddings

Live

The flagship, and the template every other booking module is cut from.

  • Enquiries, viewings, provisional holds with expiry, confirmed bookings and cancellations with a reason that feeds reporting
  • Payment schedules computed from the wedding date, with statuses derived nightly rather than set by hand
  • Bonds: charged, held, repaid and tracked
  • Couple portal for quotes, payments, the bedroom block, meal choices and final details
  • Guest links with no login, for meal choices and paying for a room
  • Function sheets and rooming lists produced from the details the couple already entered
  • Year on year reporting, per wedding worth, and the sales office bonus
02

Shift procedures and reports

In build

Sixteen shift reports across every department, from the reception handover to the bar closedown.

  • Procedures as checklists on a phone, not a laminated sheet by the till
  • Handover and closedown reports filed at the end of the shift
  • Comments and escalation, so a report that needs a manager reaches one
  • Every historic entry is already in: 2,385 reception reports, 1,621 night porter handovers, and the rest
03

Staff management

In build

The HR side of a venue with a hundred people on the books and a rota that changes weekly.

  • Employee records, new starters and leavers
  • Rotas built and published, with the department's cover visible while you build
  • Clocking, overtime approval and hours ready for payroll
  • Holiday and sickness, requested on a phone and approved in one place
  • 4,474 historic holiday requests already migrated
04

Health and safety

In build

The checks a venue has to do anyway, with the evidence kept for you.

  • Fire alarm tests, food safety and temperature checks, bedroom checks, EHO checks
  • Repeating requirements on a schedule, with reminders before they fall due
  • Risk assessments, incident and accident reporting
  • A compliance overview that answers the question an inspector actually asks: show me
05

Maintenance

In build

Faults reported by the person who found them, from wherever they found them.

  • Report a fault in seconds with a photograph attached
  • Triage into a job list with an owner and a priority
  • Planned and repeating maintenance alongside reactive jobs
  • Damages and contractor records, 969 maintenance requests already imported
06

Training, SOPs and memos

In build

The things everyone is supposed to have read, with a record of who has.

  • A versioned SOP library, so the current version is the one on the screen
  • Training records with renewal dates and overdue flags
  • Training tests, marked automatically
  • Memos distributed with read receipts
07

Events and functions

Planned

The wedding machinery pointed at everything else the venue sells.

  • Christmas parties, festivals, ticketed events and private dining
  • The same enquiries, quotes, payments, comms and portals
  • Event costs and organising lists
08

Restaurant operations

Planned

The restaurant's own work, sharing the menu machinery Weddings already needs.

  • Pre-orders and food tastings
  • Menus, courses, dietary needs and allergens, built once and used everywhere
09

Stock

Planned

The last of the spreadsheets.

  • Ordering, stocktakes and par levels
  • Supplier lists and gross profit
10

Marketing

Planned

The front of the business, on the same calendar as the back of it.

  • Content calendar and promotions
  • Open days, with check-ins

How buying works

Per property, per module.

A subscription for each property, priced by the modules that property uses, with bundles where several go together. The core comes with the first module you buy.

Switching a module on is a row in a table, not a deployment. Navigation, routes and dashboard widgets all check the same entitlement, so a module you have not bought is not hidden from you, it is genuinely not there.

What that means in practice

  • Start with one module and add the next when it earns its place
  • A wedding venue with no bedrooms pays for none of the bedroom machinery
  • Adding a second property does not mean a second system
  • No setup project, no consultants, no six month rollout

Which module would you turn on first?

Tell us what the venue is drowning in and we will show you that part of the platform, not a generic tour.

Book a demo

Or email jak@klyk.uk and ask anything.