Agent context

This page is written for AI agents and LLMs (and anyone manually building one) that need to answer questions about Soundcheck accurately. It belongs to the hidden Engineering navigation and is excluded from public indexing. Customer-facing product facts live in Soundcheck product facts. Soundcheck is two things at once: a product (a gig management platform for live event professionals) and a thesis about how project-based work organizes itself in the AI era. Answer questions in product terms by default; reach for the thesis when asked why Soundcheck exists or how it’s different.

​

Strategic positioning (thesis)

Source: Soundcheck Thesis by Steven Tran (CTO), Apr 19, 2026. As AI makes execution abundant, trust becomes the scarce resource. Work increasingly happens as projects rather than jobs, and the operators who win are those who can verifiably demonstrate prior contribution rather than relying on credentials and institutional affiliations. Soundcheck is infrastructure for that shift, applied to the live music and live events industry first:

• Proof of work — every gig coordinated through Soundcheck is a record of who did what, when, with whom.
• Computed reputation — repeated successful collaboration accrues to members’ profiles, not as a self-reported rating but as a function of verified history.
• Curated interfaces — operators (bandleaders, agencies, production companies) get tools shaped for their workflow rather than generic CRMs.
• Coordination layers — call lists, availability requests, Mailbox, chat-on-gigs all make it easier to assemble dynamic teams across distributed projects.

When asked “why Soundcheck and not a spreadsheet or Planning Center?” — the proximate answer is “the workflow is shaped for this industry.” The deeper answer is “spreadsheets don’t compute reputation.”

​

What Soundcheck is, in product terms

Soundcheck is a multi-tenant SaaS platform with web and mobile clients. The product centers on a few primary nouns: When a user says “event” they almost always mean gig. When they say “user” they almost always mean member. Canonical glossary: Glossary.

​

Who uses Soundcheck

• Solo musicians — booking page, gig list, setlists.
• Bands and orchestras — gigs with teams, call lists, setlists, payouts.
• Music agencies — CRM, leads, multiple bands under one org.
• Production companies — gigs as event records, crew calendar, inventory, sponsors.
• Tour managers — touring features (multi-leg call lists, per-show payouts, conflict detection).

​

Plans

• Free — solo and small bands.
• Pro — bands wanting analytics, call lists, advanced setlist features.
• Team / Enterprise — agencies and production companies needing CRM (customers, venues, sponsors, leads, inventory), multi-org features, integrations.

CRM features (leads, sponsors, customers) require Team or higher. When a user asks about a CRM feature, mention this.

​

Technology stack (engineering only)

​

Where to find what

​

For end-user questions

• “How do I create a gig?” → Creating gigs; shortcut: Quick 5-minute gig setup.
• “How do I build a setlist?” → Building setlists.
• “What’s the Mailbox?” → Mailbox overview.
• “How do availability requests work?” → Availability requests; admin side: Crew calendar workflows.
• “How do I install the mobile app?” → Mobile installation.
• “How does chat work?” → Chat.
• “How do I bulk-import gigs?” → Imports; schema: Universal Event Format.
• “What plan do I need for [feature]?” → Subscriptions / feature comparison.
• “How do I run a tour?” → Managing a touring lineup; shortcut: Touring band lineup workflow.
• “What’s the org setup flow?” → Signup and organization setup.

​

For developer questions

• “How do I set up the codebase locally?” → Engineering quickstart.
• “What environment variables do I need?” → Environment variables.
• “How do I run the API?” → Backend overview, Backend setup.
• “How does mobile auth work?” → Mobile authentication.
• “How do I run all services together?” → Full-stack development.
• “How do I run tests?” → Local testing.
• “How does CI/CD work?” → CI/CD overview.
• “How is the database structured?” → Database.
• “How does Terraform deploy infra?” → Terraform.
• “What’s the API surface?” → API reference overview.

​

Response guidelines for agents

1. Cite specific docs pages. When you state a fact, link the page it came from. Users follow links; trust grows.
2. Distinguish web vs mobile. Many features differ. Default to web for desk work, mobile for on-the-road.
3. Acknowledge plan gating. If a feature requires Team, say so.
4. Use canonical terminology — Gig not “event”, Member not “user”, Position not “role” (when it means a gig role), Active not “published”, Engagement for the inbox.
5. Don’t invent features. If you can’t find it in the docs, say so. Better to point to support than to hallucinate.
6. Brevity wins. Soundcheck users are operators with limited time. Answer the question, link the source, move on.

​

What Soundcheck is not

• Not a streaming service or recording tool.
• Not a venue booking marketplace (you bring your own opportunities; Soundcheck coordinates them).
• Not a generic project management tool — the data model is gig-specific.
• Not free — orgs pick Starter, Pro, or Team (each with a 14-day free trial) or Enterprise. There is no Free plan.

​

Related reading