Firebase Auth con dominio personalizado en Next.js

Firebase Auth with Custom Domain in Next.js

How to Promote Your Music Portfolio on Social Media

Music Producer Income: 6 Revenue Streams Beyond Beats

Remote Music Collaboration: Working with Artists Worldwide

5 Ways to Get More Clients as a Music Producer

How to Create a Music Producer Portfolio [2026 Guide]

OBRA Editorial on OBRA

<p> Muestra el mensaje "Elegir una cuenta para continuar en <strong>myweb.com</strong>" en vez de <em>firebaseapp.com</em> al iniciar sesión con Google. Esta guía cubre la configuración completa: DNS, Firebase Hosting y Google Cloud Console. </p><section id="passage-01" data-heading="1-por-que-necesitamos-firebase-hosting"><h2 id="1-por-que-necesitamos-firebase-hosting"> 1. ¿Por qué necesitamos Firebase Hosting? </h2><p> Firebase Auth redirige a la ruta <code>/__/auth/handler</code>, que solo existe en Firebase Hosting. Si tu dominio no está conectado, recibirás un 404. Para usar un dominio personalizado en la pantalla de login, necesitas apuntarlo a Firebase Hosting. </p></section><section id="passage-02" data-heading="2-opciones-de-configuracion"><h2 id="2-opciones-de-configuracion">2. Opciones de configuración</h2><p>Tienes dos opciones:</p><ol><li><p> Alojar <strong>toda tu web</strong> en Firebase Hosting (ej. <code>myweb.com</code>). </p></li><li><p> Usar un <strong>subdominio</strong> solo para autenticación (ej. <code>auth.myweb.com</code>) y mantener tu sitio en Vercel u otro hosting. </p></li></ol><p> La opción 2 es la recomendada si ya tienes tu app en Vercel. Mantienes tu pipeline de despliegue intacto y solo delegas la autenticación. </p></section><section id="passage-03" data-heading="3-conexion-del-dominio-en-firebase-console"><h2 id="3-conexion-del-dominio-en-firebase-console"> 3. Conexión del dominio en Firebase Console </h2><p> En Firebase Console, añade tu dominio en la sección de Hosting. Verifica la propiedad con un registro TXT y apunta los registros DNS: </p><ul><li><p><strong>Dominio raíz:</strong> Registros A apuntando a las IPs de Firebase. </p></li><li><p><strong>Subdominio:</strong> CNAME apuntando a <code>tuproyecto.web.app</code>. </p></li></ul></section><section id="passage-04" data-heading="4-configuracion-en-google-cloud-console-oauth"><h2 id="4-configuracion-en-google-cloud-console-oauth"> 4. Configuración en Google Cloud Console (OAuth) </h2><p> En la <a target="_blank" rel="noopener noreferrer nofollow" href="https://console.cloud.google.com/apis/credentials"> Google Cloud Console </a> , edita el "OAuth 2.0 Client ID": </p><ul><li><p><strong>Authorized JavaScript origins:</strong> <code>https://myweb.com</code> y/o <code>https://auth.myweb.com</code>, más <code>http://localhost:3000</code> para desarrollo local. </p></li><li><p><strong>Redirect URIs:</strong> <code>https://tudominio.com/__/auth/handler</code></p></li></ul></section><section id="passage-05" data-heading="5-configurar-firebaseconfig-en-tu-proyecto"><h2 id="5-configurar-firebaseconfig-en-tu-proyecto"> 5. Configurar <code>firebaseConfig</code> en tu proyecto </h2><p> Cambia el valor de <code>authDomain</code> en tu configuración de Firebase: </p><pre><code>// Dominio principal
authDomain: "myweb.com"

// Subdominio
authDomain: "auth.myweb.com"</code></pre></section><section id="passage-06" data-heading="6-despliegue-a-firebase-hosting"><h2 id="6-despliegue-a-firebase-hosting">6. Despliegue a Firebase Hosting</h2><p>Si tu sitio va completamente en Firebase:</p><pre><code>npm install -g firebase-tools
firebase login
firebase init hosting
firebase deploy</code></pre></section><section id="passage-07" data-heading="7-solo-autenticacion-en-firebase-subdominio"><h2 id="7-solo-autenticacion-en-firebase-subdominio"> 7. Solo autenticación en Firebase (subdominio) </h2><p> Si mantienes tu sitio en Vercel, conecta solo <code>auth.myweb.com</code> a Firebase Hosting. Configura <code>authDomain: "auth.myweb.com"</code> y asegúrate de que la Cloud Console tenga este subdominio y su handler URI. </p></section><section id="passage-08" data-heading="8-pruebas-locales"><h2 id="8-pruebas-locales">8. Pruebas locales</h2><p> Añade <code>http://localhost:3000</code> y <code>http://localhost:3000/__/auth/handler</code> como orígenes y URIs de redirección en la Cloud Console. Prueba el flujo de login y verifica que redirige correctamente. </p></section><section id="passage-09" data-heading="9-problemas-comunes"><h2 id="9-problemas-comunes">9. Problemas comunes</h2><ul><li><p><strong>404 en /__/auth/handler:</strong> El dominio no está conectado a Firebase Hosting. Revisa los registros DNS. </p></li><li><p><strong>SSL no emitido:</strong> Espera unos minutos después de cambiar los DNS. Firebase genera el certificado automáticamente. </p></li><li><p><strong>Origen no autorizado:</strong> Los valores en <code>firebaseConfig</code> deben coincidir exactamente con la Cloud Console. </p></li><li><p><strong>Subdominio mal configurado:</strong> El CNAME debe apuntar a <code>tuproyecto.firebaseapp.com</code>. </p></li></ul><h3>Resumen rápido</h3><ol><li><p>Conecta tu dominio o subdominio a Firebase Hosting.</p></li><li><p>Configura OAuth en Google Cloud Console.</p></li><li><p> Cambia el <code>authDomain</code> en tu app. </p></li><li><p>Haz deploy si alojas todo en Firebase.</p></li></ol></section>

Muestra el mensaje "Elegir una cuenta para continuar en myweb.com" en vez de firebaseapp.com al iniciar sesión con Google. Esta guía cubre la configuración completa: DNS, Firebase Hosting y Google Cloud Console. 1. ¿Por qué necesitamos Firebase Hosting? Firebase Auth redirige a la ruta /__/auth/handler, que solo existe en Firebase Hosting. Si tu dominio no está conectado, recibirás un 404. Para usar un dominio personalizado en la pantalla de login, necesitas apuntarlo a Firebase Hosting. 2. Opciones de configuración Tienes dos opciones: Alojar toda tu web en Firebase Hosting (ej. myweb.com). Usar un subdominio solo para autenticación (ej. auth.myweb.com) y mantener tu sitio en Vercel u otro hosting. La opción 2 es la recomendada si ya tienes tu app en Vercel. Mantienes tu pipeline de despliegue intacto y solo delegas la autenticación. 3. Conexión del dominio en Firebase Console En Firebase Console, añade tu dominio en la sección de Hosting. Verifica la propiedad con un registro TXT y apunta los registros DNS: Dominio raíz: Registros A apuntando a las IPs de Firebase. Subdominio: CNAME apuntando a tuproyecto.web.app. 4. Configuración en Google Cloud Console (OAuth) En la Google Cloud Console , edita el "OAuth 2.0 Client ID": Authorized JavaScript origins: https://myweb.com y/o https://auth.myweb.com, más http://localhost:3000 para desarrollo local. Redirect URIs: https://tudominio.com/__/auth/handler 5. Configurar firebaseConfig en tu proyecto Cambia el valor de authDomain en tu configuración de Firebase: // Dominio principal authDomain: "myweb.com" // Subdominio authDomain: "auth.myweb.com" 6. Despliegue a Firebase Hosting Si tu sitio va completamente en Firebase: npm install -g firebase-tools firebase login firebase init hosting firebase deploy 7. Solo autenticación en Firebase (subdominio) Si mantienes tu sitio en Vercel, conecta solo auth.myweb.com a Firebase Hosting. Configura authDomain: "auth.myweb.com" y asegúrate de que la Cloud Console tenga este subdominio y su handler URI. 8. Pruebas locales Añade http://localhost:3000 y http://localhost:3000/__/auth/handler como orígenes y URIs de redirección en la Cloud Console. Prueba el flujo de login y verifica que redirige correctamente. 9. Problemas comunes 404 en /__/auth/handler: El dominio no está conectado a Firebase Hosting. Revisa los registros DNS. SSL no emitido: Espera unos minutos después de cambiar los DNS. Firebase genera el certificado automáticamente. Origen no autorizado: Los valores en firebaseConfig deben coincidir exactamente con la Cloud Console. Subdominio mal configurado: El CNAME debe apuntar a tuproyecto.firebaseapp.com. Resumen rápido Conecta tu dominio o subdominio a Firebase Hosting.Configura OAuth en Google Cloud Console. Cambia el authDomain en tu app. Haz deploy si alojas todo en Firebase.

<p> Want the "Continue with Google" button to say "Choose an account to continue to <strong>myweb.com</strong>" instead of showing your Firebase project URL? This guide covers the full setup: DNS, Firebase Hosting, and Google Cloud Console configuration. </p><section id="passage-01" data-heading="1-why-firebase-hosting-is-required-for-auth"><h2 id="1-why-firebase-hosting-is-required-for-auth"> 1. Why Firebase Hosting Is Required for Auth </h2><p> Firebase Auth redirects to <code>/__/auth/handler</code>, a route that only exists on Firebase Hosting. If your domain isn't connected to Hosting, this route returns 404 and breaks the OAuth flow. You need to point your domain (or a subdomain) to Firebase Hosting for this to work. </p></section><section id="passage-02" data-heading="2-configuration-options"><h2 id="2-configuration-options">2. Configuration Options</h2><p>You have two paths:</p><ol><li><p> Host your entire site (e.g. <code>myweb.com</code>) on Firebase Hosting. </p></li><li><p> Host only auth on a subdomain (e.g. <code>auth.myweb.com</code>) and keep your main site on Vercel or another service. </p></li></ol><p> Option 2 is recommended if you're already deployed on Vercel. It keeps your deployment pipeline intact while still getting custom domain auth. </p></section><section id="passage-03" data-heading="3-firebase-console-setup-connecting-your-domain"><h2 id="3-firebase-console-setup-connecting-your-domain"> 3. Firebase Console Setup: Connecting Your Domain </h2><p> Go to Firebase Hosting and add your domain or subdomain. Firebase will ask you to verify ownership with a TXT record, then point DNS: </p><ul><li><p><strong>Root domain:</strong> Use A records pointing to Firebase's IPs. </p></li><li><p><strong>Subdomain:</strong> Use a CNAME pointing to <code>yourproject.web.app</code>. </p></li></ul></section><section id="passage-04" data-heading="4-configuring-auth-in-google-cloud-console"><h2 id="4-configuring-auth-in-google-cloud-console"> 4. Configuring Auth in Google Cloud Console </h2><p> In the <a target="_blank" rel="noopener noreferrer nofollow" href="https://console.cloud.google.com/apis/credentials"> Google Cloud Console </a> , edit your OAuth 2.0 Client ID: </p><ul><li><p><strong>Authorized JavaScript origins:</strong> <code>https://myweb.com</code> (or <code>https://auth.myweb.com</code> ), plus <code>http://localhost:3000</code> for local dev. </p></li><li><p><strong>Redirect URIs:</strong> <code>https://yourdomain.com/__/auth/handler</code></p></li></ul></section><section id="passage-05" data-heading="5-configuring-firebaseconfig-in-your-next-js-project"><h2 id="5-configuring-firebaseconfig-in-your-next-js-project"> 5. Configuring <code>firebaseConfig</code> in Your Next.js Project </h2><p> Update the <code>authDomain</code> field to match your custom domain: </p><pre><code>// For root domain
authDomain: "myweb.com"

// For subdomain
authDomain: "auth.myweb.com"</code></pre></section><section id="passage-06" data-heading="6-deploying-to-firebase-hosting-root-domain"><h2 id="6-deploying-to-firebase-hosting-root-domain"> 6. Deploying to Firebase Hosting (Root Domain) </h2><p>If you're hosting the full site on Firebase:</p><pre><code>npm install -g firebase-tools
firebase login
firebase init hosting
firebase deploy</code></pre></section><section id="passage-07" data-heading="7-hosting-only-auth-on-firebase-subdomain"><h2 id="7-hosting-only-auth-on-firebase-subdomain"> 7. Hosting Only Auth on Firebase (Subdomain) </h2><p> If you keep your site on Vercel, connect only <code>auth.myweb.com</code> to Firebase Hosting. Set <code>authDomain: "auth.myweb.com"</code> in your config and make sure the Cloud Console contains this subdomain and its handler URI. </p></section><section id="passage-08" data-heading="8-local-testing"><h2 id="8-local-testing">8. Local Testing</h2><p> Add <code>http://localhost:3000</code> to Authorized Origins and <code>http://localhost:3000/__/auth/handler</code> to Redirect URIs in the Cloud Console. Test the login flow and verify the redirect works correctly. </p></section><section id="passage-09" data-heading="9-common-issues-and-solutions"><h2 id="9-common-issues-and-solutions">9. Common Issues and Solutions</h2><ul><li><p><strong>404 on /__/auth/handler:</strong> Your domain isn't connected to Firebase Hosting. Check DNS records and the Hosting console. </p></li><li><p><strong>SSL certificate issues:</strong> Wait a few minutes after DNS changes. Firebase provisions SSL automatically but it takes time. </p></li><li><p><strong>Mismatched origin:</strong> Make sure the domain in <code>firebaseConfig</code> matches exactly what's in the Cloud Console. </p></li><li><p><strong>Subdomain not redirecting:</strong> Verify the CNAME points to <code>yourproject.firebaseapp.com</code>. </p></li></ul><h3>Quick Summary</h3><ol><li><p>Connect your domain or subdomain to Firebase Hosting.</p></li><li><p> Set authorized domains and redirect URIs in the Google Cloud Console. </p></li><li><p> Update <code>firebaseConfig</code> with your custom <code>authDomain</code>. </p></li><li><p>Deploy your app or host only the auth handler on the subdomain.</p></li></ol></section>

Want the "Continue with Google" button to say "Choose an account to continue to myweb.com" instead of showing your Firebase project URL? This guide covers the full setup: DNS, Firebase Hosting, and Google Cloud Console configuration. 1. Why Firebase Hosting Is Required for Auth Firebase Auth redirects to /__/auth/handler, a route that only exists on Firebase Hosting. If your domain isn't connected to Hosting, this route returns 404 and breaks the OAuth flow. You need to point your domain (or a subdomain) to Firebase Hosting for this to work. 2. Configuration Options You have two paths: Host your entire site (e.g. myweb.com) on Firebase Hosting. Host only auth on a subdomain (e.g. auth.myweb.com) and keep your main site on Vercel or another service. Option 2 is recommended if you're already deployed on Vercel. It keeps your deployment pipeline intact while still getting custom domain auth. 3. Firebase Console Setup: Connecting Your Domain Go to Firebase Hosting and add your domain or subdomain. Firebase will ask you to verify ownership with a TXT record, then point DNS: Root domain: Use A records pointing to Firebase's IPs. Subdomain: Use a CNAME pointing to yourproject.web.app. 4. Configuring Auth in Google Cloud Console In the Google Cloud Console , edit your OAuth 2.0 Client ID: Authorized JavaScript origins: https://myweb.com (or https://auth.myweb.com ), plus http://localhost:3000 for local dev. Redirect URIs: https://yourdomain.com/__/auth/handler 5. Configuring firebaseConfig in Your Next.js Project Update the authDomain field to match your custom domain: // For root domain authDomain: "myweb.com" // For subdomain authDomain: "auth.myweb.com" 6. Deploying to Firebase Hosting (Root Domain) If you're hosting the full site on Firebase: npm install -g firebase-tools firebase login firebase init hosting firebase deploy 7. Hosting Only Auth on Firebase (Subdomain) If you keep your site on Vercel, connect only auth.myweb.com to Firebase Hosting. Set authDomain: "auth.myweb.com" in your config and make sure the Cloud Console contains this subdomain and its handler URI. 8. Local Testing Add http://localhost:3000 to Authorized Origins and http://localhost:3000/__/auth/handler to Redirect URIs in the Cloud Console. Test the login flow and verify the redirect works correctly. 9. Common Issues and Solutions 404 on /__/auth/handler: Your domain isn't connected to Firebase Hosting. Check DNS records and the Hosting console. SSL certificate issues: Wait a few minutes after DNS changes. Firebase provisions SSL automatically but it takes time. Mismatched origin: Make sure the domain in firebaseConfig matches exactly what's in the Cloud Console. Subdomain not redirecting: Verify the CNAME points to yourproject.firebaseapp.com. Quick Summary Connect your domain or subdomain to Firebase Hosting. Set authorized domains and redirect URIs in the Google Cloud Console. Update firebaseConfig with your custom authDomain. Deploy your app or host only the auth handler on the subdomain.

<p> You built a portfolio. Now what? The best portfolio in the world doesn't help if nobody sees it. Social media is where you drive traffic to your work, but most producers use it wrong: they post finished tracks and hope for the best. </p><p> Here's a more effective approach, platform by platform. </p><section id="passage-01" data-heading="your-bio-link-is-the-most-important-real-estate"><h2 id="your-bio-link-is-the-most-important-real-estate">Your Bio Link Is the Most Important Real Estate</h2><p> Before worrying about content strategy, fix your bio link. Every social platform gives you one clickable link. That link should go to your portfolio, not your Spotify, not a Linktree with 12 links nobody clicks. </p><p> Your <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art"> OBRA </a>  profile works as a centralized hub: it shows your credits, streams, and services on one page. When someone taps your bio link, they should land on a page that answers "who is this person and are they legit?" </p></section><section id="passage-02" data-heading="instagram-behind-the-scenes-wins"><h2 id="instagram-behind-the-scenes-wins">Instagram: Behind the Scenes Wins</h2><p> Finished tracks get likes. Process content gets clients. What works on Instagram for producers: </p><ul><li><p><strong>Reels</strong> showing beat-making in real time (30-60 seconds of you building a track) </p></li><li><p><strong>Stories</strong> from studio sessions with quick commentary </p></li><li><p><strong>Carousels</strong> with production tips or before/after mixing comparisons </p></li><li><p><strong>A pinned post</strong> that introduces who you are and links to your portfolio </p></li></ul><p> What doesn't work: posting cover art with a "link in bio" caption. That's what every other producer does, and it blends into the noise. </p></section><section id="passage-03" data-heading="tiktok-show-your-process"><h2 id="tiktok-show-your-process">TikTok: Show Your Process</h2><p> TikTok rewards raw, unpolished content. The "studio setup" and "making a beat in 60 seconds" formats still work because they give viewers a window into how music gets made. </p><p> Producers like Kenny Beats built massive followings by recording their sessions. You don't need their audience to benefit from the same approach at a smaller scale. Post consistently (3-5 times per week), use trending sounds when relevant, and always include your portfolio link in your bio. </p></section><section id="passage-04" data-heading="twitter-x-join-the-conversation"><h2 id="twitter-x-join-the-conversation">Twitter/X: Join the Conversation</h2><p> Twitter is where music industry conversations happen. A&amp;Rs, managers, artists, and other producers are all active there. Engage with threads about production, share your takes on industry topics, and occasionally post your work. </p><p> The ratio should be roughly 80% conversation, 20% promotion. When you do share your work, include your portfolio link rather than just a streaming link. It shows more of your story and gives people a reason to explore further. </p></section><section id="passage-05" data-heading="linkedin-the-underrated-platform-for-producers"><h2 id="linkedin-the-underrated-platform-for-producers">LinkedIn: The Underrated Platform for Producers</h2><p> Most producers ignore LinkedIn, which is exactly why it works. Labels, sync libraries, ad agencies, and film production companies all use LinkedIn to find talent. </p><p> A well-written LinkedIn profile that positions you as a music professional (not just "beatmaker") can open doors to corporate gigs, sync placements, and B2B opportunities. Post about your recent projects, share industry insights, and connect with people in adjacent fields. The competition on LinkedIn for music content is almost nonexistent. </p></section><section id="passage-06" data-heading="consistency-over-virality"><h2 id="consistency-over-virality">Consistency Over Virality</h2><p> One viral TikTok won't build a sustainable client pipeline. Consistent posting (even just 2-3 times per week across one or two platforms) builds familiarity and trust over time. </p><p> Pick one platform to start with, learn what resonates, and expand from there. Every post should make it easy for someone to find your portfolio. Pin it, link it, and mention it naturally. See how producers like <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art/liamgarner"> Liam Garner </a>  use their OBRA profile as their single link destination. </p></section>

You built a portfolio. Now what? The best portfolio in the world doesn't help if nobody sees it. Social media is where you drive traffic to your work, but most producers use it wrong: they post finished tracks and hope for the best. Here's a more effective approach, platform by platform. Your Bio Link Is the Most Important Real Estate Before worrying about content strategy, fix your bio link. Every social platform gives you one clickable link. That link should go to your portfolio, not your Spotify, not a Linktree with 12 links nobody clicks. Your OBRA profile works as a centralized hub: it shows your credits, streams, and services on one page. When someone taps your bio link, they should land on a page that answers "who is this person and are they legit?" Instagram: Behind the Scenes Wins Finished tracks get likes. Process content gets clients. What works on Instagram for producers: Reels showing beat-making in real time (30-60 seconds of you building a track) Stories from studio sessions with quick commentary Carousels with production tips or before/after mixing comparisons A pinned post that introduces who you are and links to your portfolio What doesn't work: posting cover art with a "link in bio" caption. That's what every other producer does, and it blends into the noise. TikTok: Show Your Process TikTok rewards raw, unpolished content. The "studio setup" and "making a beat in 60 seconds" formats still work because they give viewers a window into how music gets made. Producers like Kenny Beats built massive followings by recording their sessions. You don't need their audience to benefit from the same approach at a smaller scale. Post consistently (3-5 times per week), use trending sounds when relevant, and always include your portfolio link in your bio. Twitter/X: Join the Conversation Twitter is where music industry conversations happen. A&Rs, managers, artists, and other producers are all active there. Engage with threads about production, share your takes on industry topics, and occasionally post your work. The ratio should be roughly 80% conversation, 20% promotion. When you do share your work, include your portfolio link rather than just a streaming link. It shows more of your story and gives people a reason to explore further. LinkedIn: The Underrated Platform for Producers Most producers ignore LinkedIn, which is exactly why it works. Labels, sync libraries, ad agencies, and film production companies all use LinkedIn to find talent. A well-written LinkedIn profile that positions you as a music professional (not just "beatmaker") can open doors to corporate gigs, sync placements, and B2B opportunities. Post about your recent projects, share industry insights, and connect with people in adjacent fields. The competition on LinkedIn for music content is almost nonexistent. Consistency Over Virality One viral TikTok won't build a sustainable client pipeline. Consistent posting (even just 2-3 times per week across one or two platforms) builds familiarity and trust over time. Pick one platform to start with, learn what resonates, and expand from there. Every post should make it easy for someone to find your portfolio. Pin it, link it, and mention it naturally. See how producers like Liam Garner use their OBRA profile as their single link destination.

<p> Surviving on beat sales alone is brutal. The producers who build sustainable careers are the ones who diversify. They don't just make beats. They offer services, teach, and license their work across multiple channels. </p><p>Here are six revenue streams worth exploring.</p><section id="passage-01" data-heading="1-mixing-services"><h2 id="1-mixing-services">1. Mixing Services</h2><p> If you already know your way around a mix, offering mixing as a standalone service is a natural extension. Many artists and producers can make great music but struggle with the technical side. </p><p> Rates vary: $150-$500 per song for independent projects, $500-$2,000+ for label work. Start with a portfolio of 3-5 well-mixed tracks and a clear turnaround time. The key differentiator? Showing your work. Before/after examples, genre-specific mixes, and client testimonials all help potential clients choose you over the next mixer. </p></section><section id="passage-02" data-heading="2-mastering"><h2 id="2-mastering">2. Mastering</h2><p> Mastering requires less gear than people think. A well-treated room, good monitoring, and trained ears matter more than expensive hardware. </p><p> Many producers add mastering as an upsell: "I'll mix your track for $300, or mix and master for $400." This increases your revenue per project with minimal extra time. If you want to position yourself as a dedicated mastering engineer, build a separate section in your portfolio that highlights mastering-specific credits. </p></section><section id="passage-03" data-heading="3-beat-licensing-and-placements"><h2 id="3-beat-licensing-and-placements">3. Beat Licensing and Placements</h2><p> Beat stores like BeatStars and Airbit let you sell the same beat multiple times under different license tiers. Non-exclusive licenses at $30-$50 add up. Exclusive licenses can go for $500-$5,000 depending on the buyer. </p><p> The real money in licensing comes from sync placements: TV shows, ads, films, and games. Sync libraries like Artlist, Musicbed, and Epidemic Sound accept submissions and pay per use. A single TV placement can pay more than months of beat sales. </p></section><section id="passage-04" data-heading="4-teaching-and-mentorship"><h2 id="4-teaching-and-mentorship">4. Teaching and Mentorship</h2><p> Your production knowledge has value beyond making music. Online lessons ($50-$150/hour), courses on platforms like Skillshare or Udemy, or private mentorship programs all generate recurring income. </p><p> Teaching also builds your reputation as an expert. Students become fans, and fans become advocates who recommend you to others. It's a flywheel that compounds over time. </p></section><section id="passage-05" data-heading="5-sound-design-for-media"><h2 id="5-sound-design-for-media">5. Sound Design for Media</h2><p> Video games, podcasts, YouTube creators, and film projects all need custom sound design. This is a less competitive space than beat-making, and the clients tend to have actual budgets. </p><p> Start by reaching out to indie game developers or YouTubers who are scaling their production quality. Offer a small project at a competitive rate to build your portfolio in this niche, then raise rates as you build credibility. </p></section><section id="passage-06" data-heading="6-session-work-and-features"><h2 id="6-session-work-and-features">6. Session Work and Features</h2><p> Playing instruments on other producers' tracks, providing vocal production, or contributing arrangement ideas are all billable services. Session rates typically range from $100-$500 depending on the scope and turnaround. </p><p> These gigs often come through networking. Being active in production communities and having a clear portfolio that shows your versatility helps you get discovered for these opportunities. </p></section><section id="passage-07" data-heading="showcase-all-your-services"><h2 id="showcase-all-your-services">Showcase All Your Services</h2><p> The challenge with multiple revenue streams is communicating them clearly. On <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art"> OBRA </a> , you can define multiple roles (Producer, Mixer, Mastering Engineer) and tag each project with the specific service you provided. Someone looking for a mastering engineer sees your mastering credits. Someone looking for a producer sees your production credits. One portfolio, multiple entry points. </p><p> Check out <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art/garabatto"> obra.art/garabatto </a>  to see how a multi-role producer organizes their credits by service type. </p></section>

Surviving on beat sales alone is brutal. The producers who build sustainable careers are the ones who diversify. They don't just make beats. They offer services, teach, and license their work across multiple channels. Here are six revenue streams worth exploring. 1. Mixing Services If you already know your way around a mix, offering mixing as a standalone service is a natural extension. Many artists and producers can make great music but struggle with the technical side. Rates vary: $150-$500 per song for independent projects, $500-$2,000+ for label work. Start with a portfolio of 3-5 well-mixed tracks and a clear turnaround time. The key differentiator? Showing your work. Before/after examples, genre-specific mixes, and client testimonials all help potential clients choose you over the next mixer. 2. Mastering Mastering requires less gear than people think. A well-treated room, good monitoring, and trained ears matter more than expensive hardware. Many producers add mastering as an upsell: "I'll mix your track for $300, or mix and master for $400." This increases your revenue per project with minimal extra time. If you want to position yourself as a dedicated mastering engineer, build a separate section in your portfolio that highlights mastering-specific credits. 3. Beat Licensing and Placements Beat stores like BeatStars and Airbit let you sell the same beat multiple times under different license tiers. Non-exclusive licenses at $30-$50 add up. Exclusive licenses can go for $500-$5,000 depending on the buyer. The real money in licensing comes from sync placements: TV shows, ads, films, and games. Sync libraries like Artlist, Musicbed, and Epidemic Sound accept submissions and pay per use. A single TV placement can pay more than months of beat sales. 4. Teaching and Mentorship Your production knowledge has value beyond making music. Online lessons ($50-$150/hour), courses on platforms like Skillshare or Udemy, or private mentorship programs all generate recurring income. Teaching also builds your reputation as an expert. Students become fans, and fans become advocates who recommend you to others. It's a flywheel that compounds over time. 5. Sound Design for Media Video games, podcasts, YouTube creators, and film projects all need custom sound design. This is a less competitive space than beat-making, and the clients tend to have actual budgets. Start by reaching out to indie game developers or YouTubers who are scaling their production quality. Offer a small project at a competitive rate to build your portfolio in this niche, then raise rates as you build credibility. 6. Session Work and Features Playing instruments on other producers' tracks, providing vocal production, or contributing arrangement ideas are all billable services. Session rates typically range from $100-$500 depending on the scope and turnaround. These gigs often come through networking. Being active in production communities and having a clear portfolio that shows your versatility helps you get discovered for these opportunities. Showcase All Your Services The challenge with multiple revenue streams is communicating them clearly. On OBRA , you can define multiple roles (Producer, Mixer, Mastering Engineer) and tag each project with the specific service you provided. Someone looking for a mastering engineer sees your mastering credits. Someone looking for a producer sees your production credits. One portfolio, multiple entry points. Check out obra.art/garabatto to see how a multi-role producer organizes their credits by service type.

<p> Five years ago, remote collaboration was a workaround. Now it's how most of the music industry operates. Producers in Madrid work with vocalists in Lagos. Mixers in LA finish records for artists in Seoul. Geography stopped being a barrier the moment file-sharing and real-time communication tools got good enough. </p><p> But working remotely across borders introduces challenges that don't exist when everyone's in the same studio. Here's what actually matters. </p><section id="passage-01" data-heading="remote-collaboration-is-the-new-normal"><h2 id="remote-collaboration-is-the-new-normal">Remote Collaboration is the New Normal</h2><p> The shift started before 2020, but the pandemic made it permanent. Today, most producers maintain clients they've never met in person. The entire workflow, from beat selection to final master, happens through file transfers and video calls. </p><p> This opens up the market for you. Instead of competing only with the producers in your city, you can work with anyone who finds your portfolio. Your online presence becomes your main pipeline for new work. </p></section><section id="passage-02" data-heading="essential-tools-for-remote-sessions"><h2 id="essential-tools-for-remote-sessions">Essential Tools for Remote Sessions</h2><p> The tools that matter most for remote music collaboration: </p><ul><li><p><strong>File transfer:</strong> Google Drive or Dropbox for stems and sessions. Avoid WeTransfer for ongoing projects since links expire. </p></li><li><p><strong>Communication:</strong> Discord for ongoing projects (organized channels, voice chat, screen sharing). WhatsApp for quick back-and-forth. Email for contracts and formal communications. </p></li><li><p><strong>Session streaming:</strong> Audiomovers or Listento for streaming high-quality audio in real time during mixing sessions. This lets the artist listen in and give feedback as you work. </p></li><li><p><strong>Project management:</strong> A shared Google Doc or Notion page with deadlines, revision counts, and deliverables. Sounds basic, but it prevents 90% of miscommunication issues. </p></li></ul></section><section id="passage-03" data-heading="managing-time-zones-and-communication"><h2 id="managing-time-zones-and-communication"> Managing Time Zones and Communication </h2><p> The biggest challenge in international projects isn't the music. It's the logistics. Set a communication window that works for both sides. If you're in Europe working with someone in Japan, maybe that's your morning and their evening. Document this at the start of the project. </p><p> Use async communication as the default. Send files with detailed notes about what you changed and what you need feedback on. Don't rely on real-time calls for every small decision. </p><p> Be clear about response times. "I'll reply within 24 hours" sets expectations and reduces anxiety on both sides. </p></section><section id="passage-04" data-heading="setting-rates-and-expectations-upfront"><h2 id="setting-rates-and-expectations-upfront"> Setting Rates and Expectations Upfront </h2><p> International projects often involve different currencies, payment methods, and expectations about what "finished" means. Always use a contract or at least a written agreement. Include: </p><ul><li><p>Scope: how many tracks, how many revisions</p></li><li><p> Payment terms and currency (PayPal, Wise, and bank transfer cover most scenarios) </p></li><li><p>Delivery timeline</p></li><li><p> Credit agreement: who gets what credit, in what format. Agree on this before work begins to prevent disputes at release time. </p></li></ul></section><section id="passage-05" data-heading="showcasing-international-work"><h2 id="showcasing-international-work">Showcasing International Work</h2><p> International credits are strong social proof. They signal that your work transcends borders and that you can handle the logistics of cross-cultural projects. </p><p> On your <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art"> OBRA </a>  portfolio, each project shows your specific role and the collaborators involved. When a label sees you've worked with artists from multiple countries, it signals versatility and professionalism. </p><p> The key is making this visible. Don't just mention "international experience" in your bio. Show the actual projects with artists, streaming data, and roles clearly labeled. See how it looks in practice at <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art/garabatto"> obra.art/garabatto </a> . </p></section>

Five years ago, remote collaboration was a workaround. Now it's how most of the music industry operates. Producers in Madrid work with vocalists in Lagos. Mixers in LA finish records for artists in Seoul. Geography stopped being a barrier the moment file-sharing and real-time communication tools got good enough. But working remotely across borders introduces challenges that don't exist when everyone's in the same studio. Here's what actually matters. Remote Collaboration is the New Normal The shift started before 2020, but the pandemic made it permanent. Today, most producers maintain clients they've never met in person. The entire workflow, from beat selection to final master, happens through file transfers and video calls. This opens up the market for you. Instead of competing only with the producers in your city, you can work with anyone who finds your portfolio. Your online presence becomes your main pipeline for new work. Essential Tools for Remote Sessions The tools that matter most for remote music collaboration: File transfer: Google Drive or Dropbox for stems and sessions. Avoid WeTransfer for ongoing projects since links expire. Communication: Discord for ongoing projects (organized channels, voice chat, screen sharing). WhatsApp for quick back-and-forth. Email for contracts and formal communications. Session streaming: Audiomovers or Listento for streaming high-quality audio in real time during mixing sessions. This lets the artist listen in and give feedback as you work. Project management: A shared Google Doc or Notion page with deadlines, revision counts, and deliverables. Sounds basic, but it prevents 90% of miscommunication issues. Managing Time Zones and Communication The biggest challenge in international projects isn't the music. It's the logistics. Set a communication window that works for both sides. If you're in Europe working with someone in Japan, maybe that's your morning and their evening. Document this at the start of the project. Use async communication as the default. Send files with detailed notes about what you changed and what you need feedback on. Don't rely on real-time calls for every small decision. Be clear about response times. "I'll reply within 24 hours" sets expectations and reduces anxiety on both sides. Setting Rates and Expectations Upfront International projects often involve different currencies, payment methods, and expectations about what "finished" means. Always use a contract or at least a written agreement. Include: Scope: how many tracks, how many revisions Payment terms and currency (PayPal, Wise, and bank transfer cover most scenarios) Delivery timeline Credit agreement: who gets what credit, in what format. Agree on this before work begins to prevent disputes at release time. Showcasing International Work International credits are strong social proof. They signal that your work transcends borders and that you can handle the logistics of cross-cultural projects. On your OBRA portfolio, each project shows your specific role and the collaborators involved. When a label sees you've worked with artists from multiple countries, it signals versatility and professionalism. The key is making this visible. Don't just mention "international experience" in your bio. Show the actual projects with artists, streaming data, and roles clearly labeled. See how it looks in practice at obra.art/garabatto .

<p> Getting better at production doesn't automatically get you more clients. The producers who stay busy aren't always the most talented. They're the ones who make it easy for clients to find them, evaluate them, and book them. </p><p>Here are five things that actually work.</p><section id="passage-01" data-heading="1-make-your-portfolio-do-the-selling"><h2 id="1-make-your-portfolio-do-the-selling">1. Make Your Portfolio Do the Selling</h2><p> Your portfolio is your salesperson, and it works 24/7. But only if it's set up right. A portfolio that lists "Producer / Mixer / Engineer" tells me nothing. A portfolio that shows 15 projects with specific roles, streaming data, and recognizable collaborators tells me everything. </p><p> SUPRMODE, a management company on <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art"> OBRA </a> , uses the platform to showcase all four of their producers in one place. Each member has individual credits and streaming stats. When a label or artist visits their page, the decision is already half-made. </p><p> Your portfolio needs to answer three questions instantly: What do you do? How good are you at it? How do I contact you? </p></section><section id="passage-02" data-heading="2-go-where-the-artists-are"><h2 id="2-go-where-the-artists-are">2. Go Where the Artists Are</h2><p> Cold DMs on Instagram are a numbers game with terrible odds. A better approach: be present in the spaces where artists are actively looking for producers. </p><p> Discord servers like Bedroom Producers, r/MusicInTheMaking on Reddit, and genre-specific Facebook groups are where real connections happen. Share work, give feedback, be genuinely helpful. When someone in those communities needs a producer, you'll be top of mind. </p><p> Local studios are another goldmine. Introduce yourself to the engineers and studio managers. They're often the ones recommending producers to artists who book sessions. </p></section><section id="passage-03" data-heading="3-show-your-process-not-just-results"><h2 id="3-show-your-process-not-just-results">3. Show Your Process, Not Just Results</h2><p> Finished tracks are great, but behind-the-scenes content builds trust faster. A 30-second video of you building a beat from scratch does more for your credibility than a polished release. </p><p> Post session clips, before/after mixing comparisons, or breakdowns of your production choices. This kind of content shows potential clients what it's like to work with you, not just what the end result sounds like. </p></section><section id="passage-04" data-heading="4-price-transparently"><h2 id="4-price-transparently">4. Price Transparently</h2><p> Nothing kills momentum faster than "DM me for pricing." Serious clients want to know your rates upfront. If they have to chase you for a price, they'll move on to a producer who makes it easy. </p><p> List your starting rates on your portfolio or create a simple rate card. You can always adjust for bigger projects, but having a baseline shows professionalism and saves both parties time. </p></section><section id="passage-05" data-heading="5-follow-up-most-producers-don-t"><h2 id="5-follow-up-most-producers-don-t">5. Follow Up (Most Producers Don't)</h2><p> You met someone at a session. You connected on Instagram. You talked about collaborating. Then nothing happened. </p><p> Following up is the easiest way to get more work because almost nobody does it. A simple message two days after meeting someone: "Hey, great connecting. Here's my portfolio if you want to check out more of my work." That's it. </p><p> The producers who follow up consistently are the ones who get repeat clients and referrals. It's not about being pushy. It's about being professional. </p><p> Want to see what a portfolio that sells looks like? Check out <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art/garabatto"> obra.art/garabatto </a>  for a real example of credits organized to convert visitors into clients. </p></section>

Getting better at production doesn't automatically get you more clients. The producers who stay busy aren't always the most talented. They're the ones who make it easy for clients to find them, evaluate them, and book them. Here are five things that actually work. 1. Make Your Portfolio Do the Selling Your portfolio is your salesperson, and it works 24/7. But only if it's set up right. A portfolio that lists "Producer / Mixer / Engineer" tells me nothing. A portfolio that shows 15 projects with specific roles, streaming data, and recognizable collaborators tells me everything. SUPRMODE, a management company on OBRA , uses the platform to showcase all four of their producers in one place. Each member has individual credits and streaming stats. When a label or artist visits their page, the decision is already half-made. Your portfolio needs to answer three questions instantly: What do you do? How good are you at it? How do I contact you? 2. Go Where the Artists Are Cold DMs on Instagram are a numbers game with terrible odds. A better approach: be present in the spaces where artists are actively looking for producers. Discord servers like Bedroom Producers, r/MusicInTheMaking on Reddit, and genre-specific Facebook groups are where real connections happen. Share work, give feedback, be genuinely helpful. When someone in those communities needs a producer, you'll be top of mind. Local studios are another goldmine. Introduce yourself to the engineers and studio managers. They're often the ones recommending producers to artists who book sessions. 3. Show Your Process, Not Just Results Finished tracks are great, but behind-the-scenes content builds trust faster. A 30-second video of you building a beat from scratch does more for your credibility than a polished release. Post session clips, before/after mixing comparisons, or breakdowns of your production choices. This kind of content shows potential clients what it's like to work with you, not just what the end result sounds like. 4. Price Transparently Nothing kills momentum faster than "DM me for pricing." Serious clients want to know your rates upfront. If they have to chase you for a price, they'll move on to a producer who makes it easy. List your starting rates on your portfolio or create a simple rate card. You can always adjust for bigger projects, but having a baseline shows professionalism and saves both parties time. 5. Follow Up (Most Producers Don't) You met someone at a session. You connected on Instagram. You talked about collaborating. Then nothing happened. Following up is the easiest way to get more work because almost nobody does it. A simple message two days after meeting someone: "Hey, great connecting. Here's my portfolio if you want to check out more of my work." That's it. The producers who follow up consistently are the ones who get repeat clients and referrals. It's not about being pushy. It's about being professional. Want to see what a portfolio that sells looks like? Check out obra.art/garabatto for a real example of credits organized to convert visitors into clients.

<p> Most producers lose gigs not because their music is bad, but because nobody can find proof it's good. A&amp;Rs, artists, and managers aren't going to dig through your SoundCloud, scroll your Instagram, or ask for a Dropbox link. They want one page that shows what you've worked on, who you've worked with, and how those projects performed. </p><p> That's what a portfolio does. And if you're still relying on a Linktree with a handful of links, you're leaving money on the table. </p><section id="passage-01" data-heading="why-your-portfolio-matters-more-than-your-instagram"><h2 id="why-your-portfolio-matters-more-than-your-instagram"> Why Your Portfolio Matters More Than Your Instagram </h2><p> Instagram shows your vibe. A portfolio shows your track record. When GARABATTO (a producer with over 8 billion Spotify streams) shares his profile, potential collaborators can see every credit, every role, and how each track performed. That kind of transparency turns "I like your beats" into an actual booking. </p><p> Compare that to a bio that says "multi-platinum producer" with no supporting data. One is verifiable. The other is just a claim. </p></section><section id="passage-02" data-heading="what-to-include-in-your-portfolio"><h2 id="what-to-include-in-your-portfolio">What to Include in Your Portfolio</h2><p>A strong producer portfolio needs five things:</p><h3>1. Credits with roles clearly labeled</h3><p> Don't just list song titles. Show what you did on each track: produced, mixed, mastered, co-wrote. Clients want to know what you bring to the table. </p><h3>2. Streaming data</h3><p> Numbers tell a story. If a track you produced has 50M streams, that's proof of commercial viability. If you're just starting out, include the data anyway. Growth trajectories matter too. </p><h3>3. A clear bio with your specialties</h3><p> Skip the "passionate music creator" line. Say what genres you work in, what DAWs you use, what your turnaround time looks like. Be specific. </p><h3>4. Embedded music</h3><p> Spotify and YouTube players directly in your portfolio let people listen without leaving the page. Every extra click you force is a potential client lost. </p><h3>5. Contact information</h3><p> Sounds obvious, but plenty of producers bury their contact info or don't include it at all. Make it dead simple to reach you. </p></section><section id="passage-03" data-heading="the-streaming-data-advantage"><h2 id="the-streaming-data-advantage">The Streaming Data Advantage</h2><p> Here's something most portfolio platforms miss: verified streaming numbers. When Liam Garner (147M+ Spotify streams) shows his <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art"> OBRA </a>  profile to a label, the data isn't self-reported. It's pulled directly from Spotify and updated automatically. No screenshots, no inflated numbers. </p><p> This matters because the music industry runs on credibility. Verified data eliminates the back-and-forth of "can you prove that?" and speeds up the decision-making process for anyone evaluating your work. </p></section><section id="passage-04" data-heading="3-mistakes-that-kill-producer-portfolios"><h2 id="3-mistakes-that-kill-producer-portfolios">3 Mistakes That Kill Producer Portfolios</h2><p><strong>Listing every project you've ever done.</strong> Curate. Your portfolio should show your best 10-15 projects, not everything since your first beat in 2018. Quality over quantity, always. </p><p><strong>No clear call to action.</strong> If someone looks at your portfolio and likes what they see, what should they do next? Include a "Book a session" or "Get in touch" button. Guide the next step. </p><p><strong>Using generic portfolio sites not built for music.</strong>  General-purpose tools like Squarespace or Wix don't understand credits, roles, or streaming data. You end up doing extra work to present information that a music-specific platform handles automatically. </p></section><section id="passage-05" data-heading="real-portfolio-examples"><h2 id="real-portfolio-examples">Real Portfolio Examples</h2><p> Take a look at these profiles to see what a well-built portfolio looks like in practice: </p><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art/garabatto"> obra.art/garabatto </a>  — 8B+ streams, credits organized by role </p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art/liamgarner"> obra.art/liamgarner </a>  — 147M+ streams, clean release presentation </p></li></ul><p> Notice how each profile shows the producer's roles per project, streaming numbers, and collaborators. That's what a portfolio should communicate: your contribution, verified by data. </p></section><section id="passage-06" data-heading="getting-started"><h2 id="getting-started">Getting Started</h2><p> If you don't have a portfolio yet, start today. Sign up at <a target="_blank" rel="noopener noreferrer nofollow" href="https://obra.art"> obra.art </a> , add your top projects by pasting Spotify or YouTube links, and define your roles on each. The platform pulls in artwork, streaming data, and track details automatically. </p><p> The free plan lets you add up to 3 projects. If you need more, Pro is €12/month for unlimited projects, a verified badge, and custom themes. The point isn't to be perfect. It's to be findable, credible, and easy to evaluate. Your music deserves that. </p></section>

Most producers lose gigs not because their music is bad, but because nobody can find proof it's good. A&Rs, artists, and managers aren't going to dig through your SoundCloud, scroll your Instagram, or ask for a Dropbox link. They want one page that shows what you've worked on, who you've worked with, and how those projects performed. That's what a portfolio does. And if you're still relying on a Linktree with a handful of links, you're leaving money on the table. Why Your Portfolio Matters More Than Your Instagram Instagram shows your vibe. A portfolio shows your track record. When GARABATTO (a producer with over 8 billion Spotify streams) shares his profile, potential collaborators can see every credit, every role, and how each track performed. That kind of transparency turns "I like your beats" into an actual booking. Compare that to a bio that says "multi-platinum producer" with no supporting data. One is verifiable. The other is just a claim. What to Include in Your Portfolio A strong producer portfolio needs five things: 1. Credits with roles clearly labeled Don't just list song titles. Show what you did on each track: produced, mixed, mastered, co-wrote. Clients want to know what you bring to the table. 2. Streaming data Numbers tell a story. If a track you produced has 50M streams, that's proof of commercial viability. If you're just starting out, include the data anyway. Growth trajectories matter too. 3. A clear bio with your specialties Skip the "passionate music creator" line. Say what genres you work in, what DAWs you use, what your turnaround time looks like. Be specific. 4. Embedded music Spotify and YouTube players directly in your portfolio let people listen without leaving the page. Every extra click you force is a potential client lost. 5. Contact information Sounds obvious, but plenty of producers bury their contact info or don't include it at all. Make it dead simple to reach you. The Streaming Data Advantage Here's something most portfolio platforms miss: verified streaming numbers. When Liam Garner (147M+ Spotify streams) shows his OBRA profile to a label, the data isn't self-reported. It's pulled directly from Spotify and updated automatically. No screenshots, no inflated numbers. This matters because the music industry runs on credibility. Verified data eliminates the back-and-forth of "can you prove that?" and speeds up the decision-making process for anyone evaluating your work. 3 Mistakes That Kill Producer Portfolios Listing every project you've ever done. Curate. Your portfolio should show your best 10-15 projects, not everything since your first beat in 2018. Quality over quantity, always. No clear call to action. If someone looks at your portfolio and likes what they see, what should they do next? Include a "Book a session" or "Get in touch" button. Guide the next step. Using generic portfolio sites not built for music. General-purpose tools like Squarespace or Wix don't understand credits, roles, or streaming data. You end up doing extra work to present information that a music-specific platform handles automatically. Real Portfolio Examples Take a look at these profiles to see what a well-built portfolio looks like in practice: obra.art/garabatto — 8B+ streams, credits organized by role obra.art/liamgarner — 147M+ streams, clean release presentation Notice how each profile shows the producer's roles per project, streaming numbers, and collaborators. That's what a portfolio should communicate: your contribution, verified by data. Getting Started If you don't have a portfolio yet, start today. Sign up at obra.art , add your top projects by pasting Spotify or YouTube links, and define your roles on each. The platform pulls in artwork, streaming data, and track details automatically. The free plan lets you add up to 3 projects. If you need more, Pro is €12/month for unlimited projects, a verified badge, and custom themes. The point isn't to be perfect. It's to be findable, credible, and easy to evaluate. Your music deserves that.