The listings ceiling

A directory ends where the money starts: it introduces two parties and exits. Everything that determines whether the gig actually works — terms, payment, reliability, what happens when someone cancels — stays informal and invisible. That ceiling has two consequences: users get no protection, and the platform accumulates no transaction data. Directories know who exists; they never learn who delivers.

What sits behind GigXchange's front door

• A booking state machine covering offers, counters, declines, cancellations and completion — the real lifecycle, not an enquiry form.
• Digital contracts generated and signed on every booking.
• Protected payment via Stripe, held and released after the gig, following a short dispute window.
• Emergency cover — a cancelled slot re-lists to matching available acts automatically.
• Verified reviews — creatable only from completed bookings, building reputation no listings site can offer.

Why the difference decides the category

Transaction ownership is what generates the compounding assets — confirmed fees, reliability history, demand density — that listings sites structurally cannot collect (Defensibility). It is also what users increasingly expect: the wider category is moving from digitising the advert to digitising the transaction (category analysis). GigXchange runs the directories BECAUSE they feed the transaction layer — not as the product itself.