Record why you lost a project

Not every enquiry books, and the ones that don't are worth as much as the ones that do — but only if you write down why. Gliss asks for a reason every time you mark a project lost, and this is where you decide what those reasons are.

Marking a project lost

Open the project and move it to your pipeline's Lost stage. Gliss asks for a reason before it will save, and you can add a note alongside it.

The project doesn't disappear — it stays on the board in the Lost column, so a "maybe next year" enquiry is still there when next year comes around. Moving it back out reopens it.

Editing the list of reasons

Settings → Lost reasons. Every org starts with a sensible set — Budget, Date unavailable, Chose another studio, Ghosted, Not a fit, Other — and none of that is fixed. Rename them into your own words, or add the ones you actually keep hearing.

Renaming is safe. The identifier underneath a reason (shown in grey beside the name) never changes, so a reason you rename keeps every project already marked with it, and the reporting keeps counting them together.

Retiring one

Retire takes a reason out of the picker for new work without touching the projects that already carry it — those keep showing their reason, and past numbers stay intact. Retired reasons move to their own list at the bottom, and Restore brings one back.

One reason always has to stay live. Marking a project lost requires picking something, so Gliss won't let you retire the last one — the button is disabled once you're down to one.

Why bother

Six months of "Budget" means something different to six months of "Date unavailable." The first is a pricing conversation; the second is a calendar one. Reasons only tell you that if you use the same handful consistently — which is the argument for editing this list down to the answers that are true for your studio, rather than piling on new ones.