Live & Booking — venues, festivals, bookers, managers

Book the scene,
not the guess.

Most lineups are built on gut, last year's numbers, or a manager's pitch. DIGSCAPE adds the missing layer: which Scenes an artist actually belongs to, which Diggers and Crates carry them, and how a Trail connects one name on the bill to the next.

Four roles, one graph.

Managers and bookers carry a roster. Venues and festivals sell tickets. The permissions follow the job, not a pricing tier.

01 / Evidence

Read a lineup before you sign it.

Every role on the live side gets Explore and Play as read access across the graph — the Scenes an artist sits in, the Trails that lead to them, the Crates that hold them, the Diggers who put them there. Not a chart position. A map of where a name actually lives.

Studio Analytics comes as elevated read: depth of interest, not vanity counts. You see whether a Drop travelled through people who dig, or sat still. Build a Crate for a shortlist and hand it to a promoter, a programmer, or a partner venue with the reasoning attached.

Explore — read Play — read Create Crate — read/write Studio Analytics — elevated read
02 / Manager & Booker

Roster CRM that sits inside the music.

Managers and bookers get Roster CRM and Booking CRM as moderated read-write — the roster, the conversations, the offers, the history. Same graph as the Scenes and Crates, so an artist record is not a row in a spreadsheet detached from the work.

Publish Stories is moderated read-write too: put context behind an act before the conversation starts. What managers and bookers do not get is the venue side — no Host Live, no Sell on Place, no publishing releases, no Ticketing. The tools stop where the job stops.

Roster CRM — moderated Booking CRM — moderated Publish Stories — moderated No Ticketing
03 / Venue & Festival

Ticketing lives here and nowhere else.

Venue and Festival/Organizer are the only roles in the entire product with Ticketing, and they hold it as full read-write. They also carry Host Live behind an approval gate and Sell on Place behind verification — a room and a bill are not something you self-declare.

Booking CRM is moderated read-write on this side as well, so the offer thread and the room live together. Roster CRM is not part of it: a venue programmes, it does not manage artists. DIGSCAPE does not process ticket payments and makes no claim about who turns up.

Ticketing — read/write Host Live — approval-gated Sell on Place — verification-gated Booking CRM — moderated
04 / Method

A bill that holds together.

A Trail is the argument for a running order: who influenced whom, which Scene the room is really in, where the night should turn. Dig Match reads two acts against each other for both shared ground and useful difference — the reason a support slot works instead of flattening the night.

DIGSCAPE is not a streaming service. Playback stays with the listening providers your team already uses; the graph supplies the taste, the context and the people. Beta access covers the booking and discovery tools only — it grants no rights to live audio, video or replay content.

Trails Dig Match Scenes Deep Dig
4
Roles on the live side — Venue, Festival/Organizer, Booker, Manager. Each with its own permission set, not one flattened account type.
2
Roles with Ticketing: Venue and Festival/Organizer. No other role anywhere in the product has it.
1
One graph behind all of it. Roster CRM, Booking CRM, Scenes, Crates and Trails read from the same source.
Beta access, by role

Book the room the music is already in.