Remix

Make your own version of Global Live

Get an exact, working copy in your account, then change anything with chat.

Original by He Wa

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

# GLOBAL LIVE — PROFESSIONAL GIG & FESTIVAL BOOKING PLATFORM

Build a fully functional, realistic music industry booking platform called GLOBAL LIVE. It is a practice simulator for concert promoters, festival programmers, venue bookers and tour managers. It must use real-world artists, bands, venues, festivals and music industry workflows wherever verified data is available.

The platform should feel like professional live-music industry software, not a basic gig-listing website.

## 1. MAIN DASHBOARD
Create a professional dashboard with:
- Overview
- Artist Directory
- Booking Requests
- Gig Planner
- Festival Planner
- Venues
- Tours
- Offers & Contracts
- Budgets & Finance
- Calendar
- Contacts
- Reports
- Settings

Show upcoming events, pending booking offers, artist availability status, confirmed bookings, budget summaries, venue enquiries and recent activity.

Use a polished desktop-first interface with a dark navy sidebar, white content panels, subtle purple accents, professional tables, search filters and realistic industry terminology.

## 2. REAL ARTIST DATABASE
Create a searchable global artist database covering bands, solo artists, DJs, orchestras, tribute acts and emerging artists.

Include artists across:
- Rock and indie
- Pop
- Alternative
- Metal
- Punk
- Electronic and dance
- Hip-hop and rap
- R&B and soul
- Jazz and blues
- Folk and country
- Classical
- World music
- Local and emerging music

Support artists from every country and artists of different sizes, from grassroots acts to international stadium headliners.

Use a music metadata API such as MusicBrainz where available to import real artist names, genres, origins and other supported metadata. Use additional permitted data sources where practical. Provide artist search, pagination, filtering, imports and duplicate detection.

Never claim the catalogue contains every band in the world unless that is demonstrably true. Display the number of artists actually stored and provide a working way to expand the database.

Allow users to create custom artists where real-world information is unavailable.

Each artist profile should include:
- Artist or band name
- Genre
- Country and city of origin
- Active years
- Biography
- Official website, where verified
- Music links, where available
- Members, where verified
- Booking contact, if publicly available and verified
- Typical event suitability
- Artist status: emerging, established, major or legacy
- Estimated booking fee range, if supported by credible data
- Technical and hospitality rider fields
- Availability records
- Previous and upcoming simulated bookings

Keep real-world facts separate from simulated booking information. Never invent official management contacts, confirmed availability or exact artist fees.

## 3. ARTIST BOOKING WORKFLOW
Make it possible to:
1. Search the artist directory.
2. Open an artist profile.
3. Select a venue or festival.
4. Choose a proposed date and performance slot.
5. Enter an offer and estimated fee.
6. Set performance length and billing position.
7. Add travel, accommodation, production and hospitality requirements.
8. Send a simulated booking enquiry.
9. Record an agent or management response.
10. Accept, reject, negotiate or withdraw the offer.
11. Confirm the booking and generate a booking record.

Booking statuses:
- Researching
- Contact to identify
- Enquiry drafted
- Enquiry sent
- Awaiting response
- Offer submitted
- Negotiating
- Provisionally held
- Confirmed
- Declined
- Cancelled

Clearly label all simulated correspondence and responses. Do not actually contact artists or their representatives.

## 4. GIG PROGRAMMING
Build a gig planner for one-off concerts, club shows, theatre gigs, arena shows and outdoor concerts.

Allow the user to select:
- Event name
- Date and running time
- Venue
- Capacity
- Promoter
- Headliner
- Support acts
- Running order
- Ticket prices
- Expected attendance
- Production requirements
- Marketing budget
- Artist fees
- Other event costs

Provide a visual running-order editor with drag-and-drop support if practical. Prevent overlapping performance times and flag insufficient changeover time.

Calculate projected revenue, total expenditure, break-even attendance and projected profit or loss.

## 5. FESTIVAL PROGRAMMER
Build a dedicated festival planning studio for multi-stage, multi-day events.

Support:
- Single-stage festivals
- Multi-stage festivals
- Indoor festivals
- Outdoor festivals
- Camping festivals
- Boutique festivals
- Large UK and international festivals

Allow custom stages, stage capacities, festival dates, performance slots, curfews, changeovers, headliners and support acts.

Create a visual timetable where artists can be assigned to stages and time slots. Flag schedule clashes, travel-time issues between stages and artists booked simultaneously at different stages.

Include a festival line-up builder with separate tiers for headliners, sub-headliners, mid-card artists, emerging acts and local bands.

Add a booking tracker that shows confirmed acts, offers, negotiations, unavailable artists and remaining budget.

## 6. VENUE DATABASE
Create a directory of real venues around the world, including pubs, grassroots music venues, clubs, theatres, concert halls, arenas, stadiums and festival grounds.

Where verified information is available, show:
- Venue name
- Location
- Venue type
- Capacity
- Website
- Facilities
- Stage and production specifications
- Accessibility information
- Booking enquiry details
- Estimated hire costs, if verified

Include UK venues and festivals, with useful coverage of the North East of England, Teesside, Newcastle, Middlesbrough, Saltburn, Manchester, Leeds, Glasgow and London.

Allow users to create custom venues and stages.

Do not invent venue contacts, capacity figures or availability. Mark estimates and unknown fields clearly.

## 7. TOURS
Create a tour-planning module for routing real artists through multiple venues.

Allow the user to create a tour, select artists, add dates, assign venues, manage support acts and record travel, accommodation and production requirements.

Display:
- Tour dates
- Cities
- Venue capacities
- Booking statuses
- Estimated show costs
- Travel distances
- Projected attendance
- Revenue and expenses

Flag overlapping dates and unrealistic travel schedules. Allow festival appearances to be integrated into an artist's tour.

## 8. CONTRACTS AND INDUSTRY DOCUMENTS
Create realistic practice templates for:
- Booking offers
- Artist enquiry emails
- Offer confirmations
- Performance schedules
- Hospitality riders
- Technical riders
- Settlement sheets
- Production schedules
- Festival running orders
- Venue hire enquiries

Documents should be editable and exportable where supported. Label generated contracts and offers as practice documents, not legally reviewed agreements.

## 9. FINANCES
Build a complete event budget system.

Track:
- Artist fees
- Venue hire
- Sound and lighting
- Staging
- Security
- Medical provision
- Staffing
- Insurance
- Transport
- Accommodation
- Catering
- Marketing
- Ticketing fees
- Licensing
- Contingency

Calculate total projected costs, expected ticket income, sponsorship, other revenue, break-even point and projected profit or loss.

Support GBP, EUR and USD. Clearly distinguish estimates from confirmed costs.

Allow different event budgets and prevent a booking from exceeding the remaining available budget without a warning.

## 10. CONTACTS AND RELATIONSHIPS
Create a CRM for venues, promoters, agents, managers, production suppliers, sponsors and festival partners.

Track notes, enquiries, simulated conversations, last contact, next follow-up and relationship history.

Use real publicly verified business information where possible. Never fabricate personal email addresses or claim that a real person has responded.

## 11. CALENDAR AND REPORTING
Include daily, weekly, monthly and annual calendar views.

Show:
- Confirmed gigs
- Festival dates
- Artist holds
- Enquiry deadlines
- Tour dates
- Payment deadlines
- Production meetings

Generate reports for booking expenditure, artist fees, event profitability, festival line-up completion and booking conversion rates.

## 12. DATA AND TECHNICAL REQUIREMENTS
Build a genuinely working web application with a persistent database, functional search, filters, forms, editable records, saved events and interconnected modules.

Use a scalable artist and venue data model. Add pagination and search so a large catalogue remains usable. Provide CSV import and export where supported.

Integrate external APIs through secure server-side functions. Keep API keys out of frontend code. If an API requires a key, explain how to configure it and provide a useful fallback.

Never load a tiny hard-coded artist list and claim it represents the global music industry. Start with a useful real-artist catalogue, then support progressive imports and user-created records.

Use realistic practice data for booking negotiations and event finances, but clearly label simulated information.

## 13. FINAL PRIORITIES
Build these features first:
1. Artist search and database.
2. Artist profiles.
3. Gig and festival creation.
4. Booking offers and negotiation workflow.
5. Multi-stage festival timetable.
6. Venues and availability tracking.
7. Event budgeting and profit calculations.
8. Saved projects and document generation.

Make every major button and workflow functional. The result should feel like a professional booking office used to programme gigs, book festival line-ups and coordinate tours across the live music industry.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.