Knowledge & data

Knowledge catalog for offer, rooms and FAQs

How many people fit in the vault room? The website says something different from the quote PDF – and on the phone the owner quotes a third number. Not because anyone's careless, but because the house's knowledge lives in five places.

Knowledge catalog

01Intro

The knowledge catalog brings this knowledge into one place and into clear building blocks: rooms with capacities and tech, offers and packages with price ranges, processes from inquiry to teardown, and the FAQs that otherwise land on the phone three times a day. Every building block has a status and an owner – change the room hire and it changes everywhere it appears. Everything benefits at once: the website becomes consistent, Google and AI systems understand your offer, the team answers uniformly – and a later FAQ assistant has a base to draw from instead of guessing.

Straight up: this is structural work, not tech magic – the knowledge is ordered first, then a tool is added. A catalog lives on being current: skip planning the upkeep responsibility and in a year you've got five truths again. That's why responsibilities and a review rhythm are part of the project.

02Demo

simulation · fictional event venue

The catalogue of the fictional “Alte Mühle” event venue. Ask a question – and look under the answer to see where it comes from: rooms, prices and processes stem from maintained blocks, not out of thin air.

// building block in the catalogue

This is what the catalogue looks like from inside: knowledge blocks with clear fields – and three output channels fed from SEVERAL blocks. If a price changes, it changes everywhere it's needed.

// the building blocks ServicesDescription · for whom · duration · from-price FAQsQuestion · answer · applies to · updated Prices & rangesService · range · conditions · updated ProcessesSteps · duration · responsibility // the output channels Website Search & AI systems Team (internal)

Ask a question in the “try it out” tab – the block the answer came from lights up here along with its channels.

03How it works

  1. 01

    Gather the knowledge

    Website, quote PDFs, menus, email modules, the owner's knowledge: everything that exists about rooms, offer and rules comes onto the table – including the contradictions. Finding those is part of the work.

  2. 02

    Structure the building blocks

    Rooms, offers, prices/ranges, processes, FAQs: each area gets clear fields (capacity seated/standing, tech, valid-from, conditions) instead of running text with the number hidden in it.

  3. 03

    Flag gaps and dead wood

    What's missing, what's outdated, what contradicts itself? The catalog makes it visible – the 2024 price list flies out, the missing answer to the most common wedding question comes in.

  4. 04

    Make it usable

    The building blocks feed their channels: website pages and structured data for search and AI, an internal overview for the team, a base for assistant and event inquiry. One source, many outputs.

  5. 05

    Anchor the upkeep

    Per area an owner and a rhythm: prices with the seasonal menu, rooms on refurbishment, FAQs continuously from real guest questions.

04Stages

The entry point is deliberately small: one area of knowledge, cleanly structured – usually the one that hurts most right now.

Tier 1

Entry: one area, clean

Rooms and capacities OR offer and prices as a structured model – the one truth for the area asked about most often.

Tier 2

Extended: the full catalog

All areas structured, technically marked up on the website – Google and AI systems understand rooms, offer and FAQs (closely interlocked with the AI-ready upgrade).

Tier 3

Full build: the living base

The catalog feeds the FAQ assistant, event inquiry and internal use – with a maintenance process and owners, so it stays the one truth.

05Technical implementation

  • Knowledge store to suit the house: the website's CMS collections, Airtable/Notion or a Markdown structure – what's decisive is the field model, not the tool.
  • Structure: clear content types (rooms, offers, prices/ranges, processes, FAQs) with status and owner fields.
  • Output: website pages, JSON-LD/Schema.org (LocalBusiness, FAQ, event structures), an internal overview, later assistant context.
  • Optional AI in the build: a language model helps sort the stock and track down contradictions – curating is done by people.
  • No RAG project: at the usual scale of a house, structured context is enough – more honest and cheaper.
  • Maintenance: a review date per area, upkeep in everyday work (a new guest question → a new FAQ building block).

for context · This shows how something like this usually gets built – not how it has to be built for you. What actually fits is worked out in the project: around your existing setup, your team, and what stays easy to maintain.

06Related building blocks

See all levers for your business