what the studio builds.
twelve things, all built custom, all on domains you own. most engagements take two or three of them and leave the rest. the tier is where the number starts, and the scope decides the rest.
contents
- 01. Record label platforms
- 02. Artist and release properties
- 03. Release and campaign launches
- 04. Beat and stem stores
- 05. Licensing engines
- 06. Catalog and rights infrastructure
- 07. Royalty and splits dashboards
- 08. Fan clubs and memberships
- 09. Interactive audio
- 10. The intelligence layer
- 11. Identity and art direction
- 12. Wikipedia and entity publishing
Record label platforms
a label running more than one artist.
the label's own platform with the roster underneath it. one catalog storefront, one customer list, and a property per act instead of a page each on somebody else's site.
- a property per artist, at whatever stage each one is
- one storefront across the whole catalog
- one customer list, wired to the CRM you already use
- a login for everyone at the label who needs one
Roster tier
yourlabel.comlabelartist-one.comliveartist-two.comliveartist-three.combuildArtist and release properties
one signed artist, or a record that needs its own room.
built to the artist's identity rather than to a template. it does not wait on a tour or a merch line to look like something, and the store switches on when there is something to sell.
- release pages, tour dates, booking
- email and SMS capture from day one
- direct checkout in your merchant account
- a dashboard anyone at the label can open
Artist tier
artist.com
list first. store when there is one
Release and campaign launches
a record with a date on it.
the drop built as its own thing: preorder, countdown, the moment it opens, and the week after. release night is when a rented checkout fails, so this one is load tested before the date rather than on it.
- preorder, drop and post-release states on a schedule
- bundles, variants and limited runs that actually run out
- load tested before the date, and covered on the night
- the campaign page kept, not thrown away after week one
any tier, scoped per release
release day
preorderdropday twocheckout holds at 2amBeat and stem stores
producers selling licences, on the roster or on their own.
your own marketplace instead of a booth inside beatstars or airbit. on those the catalog sits next to every competitor's, the marketplace keeps the buyer, and it takes a cut of inventory you already own.
- licence tiers you set, priced how you want
- instant delivery, files zipped and sent on payment
- the buyer lands on your list, not a marketplace's
- one seller, or every producer on the roster
Artist for one seller, Catalog for a marketplace
in client workjakeangelbeats.studioraine.artmp3 lease$29trackout$99exclusive$1,200your tiers. your buyer
Licensing engines
anyone selling rights rather than objects.
every sale writes its own licence agreement, stamps it with the buyer's name and the terms they bought, and zips it with the files. the paperwork stops being a job somebody does by hand on a monday.
- custom licence tiers, exclusive and non-exclusive
- an agreement generated and stamped per sale
- the contract delivered with the files, not after
- a record of who bought what, on what terms
in scope at Artist, custom engine at Catalog
licence.pdfstampedgenerated per sale, zipped with the files
Catalog and rights infrastructure
a back catalog, an estate, or a publisher.
when the thing you need does not exist yet. a property per release across a catalog, the metadata to run it, and the pipes that move it between the systems you already pay for.
- a property per release, generated rather than typed
- bulk metadata, ingest and DDEX delivery
- integrations with the systems you already run
- multi-entity checkout where the catalog spans companies
Catalog tier
one property per release
DDEXRoyalty and splits dashboards
any release where more than one person gets paid.
who is owed what, and just as importantly what each side is allowed to see. the deal terms get written down once and applied every period, instead of a spreadsheet somebody rebuilds each quarter. the studio builds the ledger to your terms. it does not administer rights, audit a distributor, or sign off the numbers.
- distributor and DSP statements read in, not retyped
- split mapping per release, per track, per party
- advances and recoupment tracked against each deal
- a statement per party, showing only their own numbers
Catalog, or scoped onto a Roster build
writer a45%writer b30%label25%each side sees only its own row
Fan clubs and memberships
a roster with an audience that would pay monthly.
the part of direct-to-fan that recurs. a paid tier, a vinyl club, early access and presales, billed in your own account rather than a platform's.
- paid tiers, billed monthly or yearly
- member-only releases, presales and early access
- subscriptions in your merchant account
- members in your list, cancellations included
Roster and above
freemembervinyl clubbills monthly, in your accountInteractive audio
when the record itself should be the thing people play with.
stem players, browser mixers, loop and preset demos that run before anyone buys. this is the part that needs someone who has actually used a DAW, which is why most agencies quietly skip it.
- stem players and browser mixers, no plugin needed
- preview before purchase, on the product page
- preset and template demos that run in the page
- audio that works on a phone, not just a desktop
scoped on its own, on any tier
in client workjakeangelbeats.studioraine.artdrumsbasskeysvoxfxThe intelligence layer
after the channel is owned and the data is finally yours.
the platforms that do this are built for retail, priced for enterprise, and assume the buyer has a data team to run them. this is the same engineering, built onto the channel you already own.
- segments that mean something in music, not age brackets
- who to email first, scored on your own buyers
- streaming data sat next to what people actually bought
- a back catalog read in one pass, described in your voice
included in Catalog, scoped on Roster
preorders every timevinyl, never merchbought once at a showlapsed after the last recordemail in this order, not all at once
Identity and art direction
an artist with no visual system, or a label whose look predates the catalog.
the design the platform gets built in: type, palette, layout, motion, and a wordmark where there is not one already. this is direction of the build. photography and video production stay outside the scope, and the pricing page says so in writing.
- a visual system the platform is built in
- a wordmark, where the artist or label has none
- art direction across every property on the platform
- your existing brand honoured instead, where you have one
part of any tier, and it moves the number if built from scratch
Aadisplay / mono
the system, before the build
Wikipedia and entity publishing
an artist, producer or label with real, documented achievements and no page.
the gold record exists. the chart history exists. what does not exist is the page that search engines and AI assistants read before deciding you are real. this is that work, done the way Wikipedia actually requires: a notability audit first, neutral sourced writing, and the paid contribution disclosure filed with it.
- a notability and source audit before a word is written
- a complete draft article, written to Wikipedia's sourcing and neutrality standards
- the Articles for Creation filing, with the paid contribution disclosure Wikipedia requires
- a Wikidata item and the structured data that feeds knowledge panels and AI search
Artist tier
in client workthree draft articles, embedded in fullthe page the machines read first
if what you need is not here, it is still worth asking. this is what gets built most, not the edge of what can be built.
what gets built around it.
the twelve above are the systems. this is everything that has to exist for one of them to actually ship, and it is all in scope rather than a list of things to go and arrange yourself.
Sites and pages
- full platforms, like the ones already live
- campaign and release pages for a single drop
- storefronts and product pages
- booking pages built around your calendar
- landing pages for one offer at a time
Into the stack you already run
your automations, untouched
- forms that create a tagged contact in your CRM
- leads dropped into the stage you pick
- the automations you already built, untouched
- calendars embedded on any page
- every word on it editable by you
Everything around it
copy, brand, search, speed
- copy written in the artist's voice, not filler
- brand and identity where a project needs one
- technical SEO and the search side
- speed, mobile and accessibility
- press kits, print and web
At scale
one build becomes the template
- as many properties as the roster needs
- one build becomes the template for the next
- your brand on it, never the studio's
- you keep the account, the data and the relationship
- nothing to migrate, ever
none of it is rented.
whichever of these an engagement covers, the terms are the same. the code is assigned to you, the domains and the merchant account are in your name, the customer list is yours, and the platform itself never carries a monthly licence.

