Build your catalogue
Start from one service line, not from an org chart.
A suggested order
Create a service line
With the name you use in your own meetings, not the one on your website.
Put services under it
The things you actually quote for. Each service can carry a short description and a one-line tagline.
Get the order right
Both lines and services can be reordered. What you sell most should sit at the top.
Revisit after a few engagements
The best catalogue is written after ten real engagements, not before the first one.
The technical identifier makes itself
Every line and service gets a short identifier that the system derives from the name. You do not write it, and if you send one it is ignored.
If two names would produce the same identifier, the system disambiguates. A name with no usable letters still gets one.
A few words are reserved because they are already part of the catalogue's own page addresses; a name landing on one of those gets a different identifier.
Engagements without a service
If an engagement existed before its service did, it appears in reporting under an "unmapped" bucket.
The moment you create the matching service, those engagements move under it by themselves. You do not have to reassign them.
Read this next
- Service catalogueRename, retire and deleteThree different actions with three different outcomes — and which one keeps the history.
- Service catalogueCatalogue statisticsWhich line actually brings in work — and what "unmapped" means.
- Service catalogueWhat the catalogue isTwo levels: line and service. And why it ships empty.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.