itunesindonesia.com Has Plan
31
plan.md
PREVIEW

itunesindonesia.com — Indonesian Release Intake And iTunes Submission Service

Build itunesindonesia.com as the Indonesian operating layer for artists who want to get releases properly prepared, paid for, reviewed, and submitted to iTunes and Apple Music.

Final Stack

  • Frontend/App: Next.js
  • Reason: auth, release drafts, asset uploads, billing state, admin review, and catalog history require application logic
  • Core support: asset storage, payment gateway, release DB, admin reviewer console, knowledge-base layer

Category Ambition

This should not be a glorified contact form.

It should become:

  • the easiest Indonesian-facing release intake product for Apple distribution workflows
  • the trusted service layer for artists who want assisted submission
  • the bridge between self-serve submission and managed release operations

Product Surface

Artist side

  • account
  • artist profile
  • release draft
  • file upload
  • payment status
  • revision loop
  • catalog history

Label side

  • multi-artist workspace
  • bulk release intake
  • plan-level billing
  • release queue overview

Support layer

  • article library
  • FAQ
  • metadata help
  • release checklist

Pricing Model

  • per single
  • per EP/album
  • annual artist plan
  • label/team plan
  • add-ons: metadata cleanup, artwork review, lyric prep, priority handling

Data Model

  • account
  • artist
  • label workspace
  • release
  • asset
  • contributor split
  • payment record
  • review state

AI Automation

  • metadata normalization
  • title and contributor validation
  • release-readiness scoring
  • issue explanation in plain Indonesian
  • stuck-release reminder drafts
  • support triage

Build Roadmap

Phase 1

  • landing page
  • pricing
  • account
  • release draft submission

Phase 2

  • payment flow
  • admin review
  • revision loop
  • knowledge layer

Phase 3

  • label workspaces
  • catalog analytics
  • smarter auto-validation

Final Thesis

itunesindonesia.com should operate like a lightweight release workflow product with a service edge, not a generic music blog and not a passive label site.

AI ASSISTANT

Ask AI to research, improve, or generate content.

Try: "Research competitors for this niche"

Actions