“Let’s connect our scenes” is a good opening sentiment and an incomplete project brief. Two crews can share musical interests while having different budgets, schedules, audiences, and definitions of success. The first useful step is to reduce the proposal until each side can explain what it contributes and what it expects in return.
The framework here is a suggested working method, not an existing USDNBDJ exchange program. The named organizations elsewhere in this publication are discovery references, not committed partners. Start through their real public contact routes, and do not use a crew’s name or logo in an announcement before it has agreed.
Choose one outcome before choosing a format
Decide what you want the collaboration to change. Help listeners discover another city’s selectors? Introduce local producers to a relevant audience? Learn how a different crew approaches an opening set? Each goal suggests a different scope.
For a first project, consider a paired listening recommendation, a short jointly edited interview, or a small exchange of original written introductions to existing authorized recordings. These proposals can be easier to coordinate than a physical event. That does not mean they require no labor: listening, editing, graphics, and publication still need owners.
Write a one-sentence outcome that avoids vague growth claims. “Introduce each audience to two selectors they can follow at the source” gives you a concrete standard. “Become the biggest network in the country” does not help decide what to deliver next week.
Research the overlap without inventing an affiliation
Read both sides’ own descriptions and listen to their output. Note where your interests genuinely meet and where they differ. An overlap in careful selection, local support, or radio programming can be more meaningful than identical genre labels.
US organizations may combine several functions. Driven AM’s own about page, for example, describes label, artist-management, and event-promoter activity. That is a reason to identify the appropriate role for your request, not to assume one person handles every opportunity or that the organization wants a partnership.
Keep the initial research modest: one relevant recording or release, one accurate observation, and the correct public contact channel. If your proposal depends on a connection you have not confirmed, mark it as a question rather than presenting it as an established relationship.
Design a small pilot
A hypothetical first pilot might pair two existing recordings with short introductions from their selectors. Each side contributes one introduction and checks its own credits. One editor assembles the page; both participants approve how their names appear. The recordings remain at their authorized original destinations.
This is an example project structure, not an offer or a report of something already arranged. Replace its components with what the actual participants want. They may prefer an interview, a private knowledge exchange, or no publication at all.
Define what is excluded. A written introduction does not automatically include a live booking, unlimited social clips, future appearances, or permission to distribute audio files. A clear boundary makes a small yes possible without accidentally promising a much larger commitment.
Put the working agreement in plain language
A one-page project note should answer the following:
- Purpose: who the project is for and what they should gain.
- Contributions: exactly what each participant supplies.
- Ownership: who edits, checks credits, uploads, and communicates changes.
- Timing: delivery dates, review time, and a realistic publication window.
- Resources: agreed fees or expenses, and what happens if the scope changes.
- Permissions: approved text, artwork, audio destinations, and promotional uses.
- Exit: how either side can pause before publication and how corrections are handled afterward.
For money, specify an actual amount and payment arrangement when you reach that stage. “Exposure” and “we will sort it later” leave different people carrying different expectations. If the pilot has no budget, say that early and let contributors decline without pressure.
Plan for the boring failure points
Use a single shared document as the current version. Give each asset a clear name and place the approved links beside the credit text. Set one contact on each side so a change does not disappear across several direct-message threads.
Allow review time across work schedules and time zones. A same-day request may be convenient for the organizer and impossible for a contributor. Agree on when silence means “wait,” rather than interpreting it as approval.
For a physical event, the project becomes substantially larger. Venue arrangements, equipment needs, travel, payments, ticketing responsibilities, and cancellation decisions need direct agreement among the actual organizers. Do not use a low-risk editorial pilot’s checklist as evidence that a show is ready to announce.
Review before publishing
Ask both sides to check names, city descriptions, links, images, and any statement that implies endorsement. Separate an artist’s location from the location of a label or promoter. Confirm that the recording destination remains accessible and that its owner is comfortable with the proposed presentation.
If audio reuse is part of the plan, check the actual hosting service’s terms and obtain the permissions required for that use. The Mixcloud copyright and licensing help section is one source for projects using that platform; it is not a universal clearance for other services.
Keep a short approval record. It need not be elaborate: the final text, the approved assets, who confirmed them, and the date. If someone requests a factual correction, make it promptly and tell both sides what changed.
Judge the pilot by what happened
After publication, review outcomes you can actually observe. Did the agreed material appear? Were contributors credited correctly? Did listeners find working routes to the artists? Did the workload match what each side expected? Do not treat a handful of clicks as proof that a scene has been transformed.
Ask participants what they would keep, remove, or change before proposing another edition. A project that ends clearly can be more useful than an indefinite collaboration nobody owns.
Use the connect brief to organize a proposal, then contact the intended collaborator through their own published channel. For finding relevant people, begin with scenes and community. The next project should grow from a completed agreement and mutual interest, not from pressure to keep a brand-looking initiative alive.