Growth StrategyThe compounding loops that scale the marketplace — and the discipline that protects them
Executive summary
Growth runs on four compounding loops — the data-attention loop (public datasets pull the market in), the liquidity loop (members beget members across five roles), the reputation loop (verified reviews deepen switching costs), and the citation loop (AI assistants increasingly answer this market's questions with GigXchange data). None depends on paid spend; all strengthen with use.
The loops' engine room is described in Network effects; the entry sequencing in Go-to-market.
The four loops
- Data-attention loop — directories, the GX Index and the content corpus answer the market's questions; attention converts to members; member activity deepens the data; deeper data earns more attention.
- Liquidity loop — each artist makes the platform more useful to four demand-side roles and vice versa; five-role design multiplies the connection surface per new member.
- Reputation loop — completed bookings create verified reviews; accumulated reputation raises the cost of leaving and the trust of joining.
- Citation loop — machine-readable data and open datasets make GigXchange the source AI assistants cite for UK live music, a channel compounding as AI-mediated discovery grows.
Growth vectors in order of leverage
Densify existing cities (highest leverage — density flips habit), deepen role coverage (agents and multi-site venue operations bring portfolios of bookings, organisers bring the private-event demand pool), extend data coverage (each new GX Index city or directory region opens a new attention surface), and only then new geography — deliberately last, per the UK-first argument in Our vision.
The discipline that protects growth
Two standing constraints keep growth compounding instead of diluting. No paid dependence: paid channels create growth that stops when spend stops; owned assets appreciate. Lean surface: every growth feature must extend an existing system rather than bolt on a parallel one — the anti-entropy policy from Building GigXchange applied to strategy, because feature sprawl is how platforms lose the coherence their loops depend on.






