02 / Create
Create a song in three steps.
It can start with a hum, a verse, or a voice note. You don’t need a finished song.
- 01
Record your voice.
Sing it, hum it, or choose an audio file.
- 02
Hit Upload.
Your recording goes to your private workspace.
- 03
Make it together.
BCMC connects musicians to your song.
Your place in the music
Start with you.
Sign in with Google or an email code. Your recordings and conversations stay in your private workspace.
Sign in to create a songListening is always open. Explore the demos →
A little more about the music
From the first idea to the finished record.
The first three steps open the door. Here is how the working circle, decisions and project record develop around your music.
Project path
The network grows around the song, then resolves into a record.
The sequence makes room for instinct while giving every contributor a dependable point of reference.
- 01
Hear the premise
Understand the source material, creator's intent, present stage and the quality that must not be lost.
Creative signal - 02
Build the circle
Identify the people, knowledge, room and resources that this work—not a generic workflow—requires.
Network - 03
Agree the project
Set scope, responsibilities, credits, permissions, decision points and any contractual participation in writing.
Terms - 04
Make and listen
Produce through sessions, versions and review moments that keep creative intent visible.
Production - 05
Release with context
Confirm the master, artwork, metadata, credits and public route before the work leaves the project room.
Release - 06
Keep the record alive
Maintain the approved catalogue information when a new use, correction or live form appears.
Continuity
Project record
A serious collaboration remembers who decided what—and why.
Documentation is not bureaucracy when it protects clarity between people who depend on one another.
| Record | What it keeps clear | Working evidence |
|---|---|---|
| Creative premise | What is being made and what must remain true | Brief, references and repertoire notes |
| Contribution map | Who brings which work or resource | Named roles, sessions and deliverables |
| Decision trail | What changed, who approved it and which version is current | Dated reviews and approvals |
| Permissions | What may be recorded, released or reused | Project terms and relevant clearances |
| Public package | What audiences will encounter | Master, artwork, metadata and credits |
| Continuing record | What changes after publication | Corrections, new uses and catalogue updates |
The record should be proportionate to the work; clarity matters more than document volume.
Project framework
Clarity is a creative resource.
A project does not need identical terms; it needs enough definition for every participant to understand the exchange.
| Area | Question | Project record |
|---|---|---|
| Intent | What are we making, and what must remain true? | Creative brief |
| Contributions | Who is bringing which work, knowledge or resource? | Role and deliverable map |
| Credits | How will accepted contributions be publicly named? | Approved credit record |
| Participation | Is a fee, ownership interest or continuing economic share agreed? | Written project terms |
| Authority | Who decides at each material review point? | Decision map |
| Release | Which public or restricted route is approved? | Release or presentation plan |
The framework makes questions visible; it does not supply a universal contract or ownership split.
Rights + credits
A name in the credits is important. It is not the whole agreement.
Credit, fee, ownership, permission and approval can sit beside one another without meaning the same thing. Burnt Chapati's model asks the project to state each instrument directly so no participant has to infer it from a title or conversation.
- Credit
- The agreed public attribution for accepted work; credit alone does not establish ownership or payment.
- Fee
- Compensation for defined work when the project terms provide for it.
- Ownership
- A project-specific legal interest in a defined asset, created only through the applicable agreement.
- Permission
- Authority for a stated use of material, performance, knowledge, name or image.
- Approval
- Decision authority over a specified matter, held only to the extent the project assigns it.
Participants should seek independent professional advice where the project's rights or economics require it.