$31.7B
Recorded music revenue in 2025
IFPI reported 6.4% global growth, which keeps music software pointed at a large and active market.
IFPI 2026
Use market size as permission, not positioning.
See the songs. Shape the release. Build the operating surface around that habit.
A deeper product, research, UI, activation, and revenue map for turning Liner from a beautiful canvas into the music workspace independent artists return to during real release work.
Sneakin Drinks
Alt pop / 128 BPM
Flying
Indie pop / 122 BPM
Daydreamer
Bedroom pop / 100 BPM
Only Romantics
Release closer / Export
$31.7B
IFPI reported 6.4% global growth, which keeps music software pointed at a large and active market.
IFPI 2026
Use market size as permission, not positioning.
13.8K
Spotify says this many artists crossed $100K in 2025, with independents generating roughly half of royalties.
Spotify Loud & Clear
The wedge is serious career artists below superstar scale.
$200B
Goldman Sachs expects music revenue to nearly double from 2024 to 2035 as formats and monetization expand.
Goldman Sachs
Plan for multi-surface release work, but do not claim the whole stack yet.
$1.02M
Internal model: 90K users, 9% paid conversion, and $10.50 blended monthly ARPU.
Liner model
Revenue depends on habit and Pro clarity, not signup volume alone.
The product should not claim to replace the DAW, distributor, catalog manager, or analytics suite. Liner wins if it becomes the one visual surface where songs, references, notes, blockers, and sequence are legible enough to act on.
Decision layer
songs, context, blockers, next move
Ideas
voice memos, lyric scraps, hooks
Production
DAW files, bounces, stems
Feedback
texts, links, comments
Planning
calendar, docs, runbooks
Distribution
metadata, uploads, stores
Promotion
posts, assets, playlists
The near-term UI should organize around reusable music primitives and visible decision state, not more isolated pages. The current canvas, library, panel, public-board, and activation work can line up into one coherent platform.
Song object
Audio, source, metadata, waveform, state
Frame
Album, EP, single, vibe, campaign, batch
Note
Lyric, task, reference, feedback, blocker
Version
Bounce, mix, master, source history
Signal
Readiness, share, export, return, Pro intent
Handoff
Public board, export, template, share link
Now: Spatial boards, frames, notes, song cards
Next: Board readiness overlays and release lanes
Later: Multi-board project maps
Now: User-level songs referenced into boards
Next: Source match confidence and duplicate resolution
Later: Catalog health and rights-aware views
Now: Manual, local, Spotify, Apple Music, link sources
Next: Streaming enrichment, lyrics, credits, version signals
Later: Automated metadata repair workflows
Now: Activation events and board completeness
Next: Decision rail: blockers, next move, export readiness
Later: AI-assisted sequencing and release QA
Now: Public boards, templates, discover pages
Next: Signed-out use-template funnel
Later: Creator profiles and team showcases
Now: Pricing, account, Stripe foundation
Next: Sync, history, continuity, export value
Later: Team review rooms and client handoff
Each bet has to show up in the interface as a repeatable pattern. The page, app shell, panels, cards, public boards, and exports should all teach the same mental model.
A song should remember where it sits in the project: pile, sequence, release frame, feedback state, and nearby references.
Canvas objects, frames, proximity, minimap, public board views.
Waveform, source, key, tempo, lyrics, version, credits, and listening state become reusable primitives across every surface.
Global library, metadata enrichment, panel completeness, embedded player.
Boards should show the next action: unresolved note, missing metadata, weak sequence, share-ready export, or release blocker.
Board readiness, action launcher, release plan bar, status panels.
Shared boards and examples should teach the product while creating acquisition paths back into first-board creation.
Discover, public canvas, templates, use-template CTA.
Audio staying local is not just architecture. It is a brand promise that makes cloud value more honest.
Local files, cloud sync, history, export, collaboration as paid expansion.
The platform direction can serve a broad music workflow, but the wedge stays anchored in import, structure, decide, share, and export. Paid value should map to the deepest repeat use, not generic feature breadth.
Capture
Core
Plan
Core
Sequence
Core
Share
Core
Analyze
Useful
Capture
Core
Plan
Core
Sequence
Useful
Share
Core
Analyze
Later
Capture
Useful
Plan
Core
Sequence
Core
Share
Core
Analyze
Core
Capture
Later
Plan
Core
Sequence
Useful
Share
Core
Analyze
Core
Capture
Useful
Plan
Useful
Sequence
Later
Share
Core
Analyze
Core
The first serious instrumentation pass should make the board habit visible. A board is useful when the user has enough songs and enough structure to make a real project decision.
Aware
landing_page_view
Understands Liner as a visual release board
Explore
landing_cta_click / discover_board_opened
Opens app, example board, or template
Capture
song_added / link_pasted / file_dropped
Adds 2+ songs, links, notes, or files
Structure
frame_created / note_created / sequence_changed
Adds a frame, note, sequence, or release intent
Aha
first_useful_board_reached
Board has songs plus structure and can support a decision
Handoff
share_link_copied / export_completed
The board leaves private thinking and becomes useful externally
First useful board
Ship2+ songs plus frame, note, sequence, or share intent
Activation
Board readiness
PrototypeMissing metadata, unresolved notes, sequence gaps, export state
Product
Public proof quality
InstrumentSigned-out view, use-template click, creator source, return path
Growth
Pro reason
InterviewSync, history, export, continuity, or collaboration named by user
Revenue
Each competitor validates a nearby pain, but Liner should keep its center: the spatial decision surface before catalog handoff, distribution, or campaign reporting.
Milanote
General visual planning
Untitled
Private WIP music folders
Boombox
Storage, feedback, AI, distribution
DISCO
Catalog management and sharing
Liner
Spatial release decision layer
The $1M ARR case is plausible only if activation creates repeated board value. The first paid story should be continuity, history, sync, and export. Team grows after shared review becomes a proven behavior.
Conservative
45K users / 7% paid / $10 ARPU
$378K ARR
Credible growth
90K users / 9% paid / $10.50 ARPU
$1.02M ARR
Accelerated
150K users / 10% paid / $11 ARPU
$1.98M ARR
The next sprint should ship fewer concepts and more proof. Every week should either reduce time-to-first-useful-board, improve public proof, or validate paid reasons with real creator behavior.
Ship first_useful_board_reached and review raw event quality before optimizing copy or funnels.
Lead with release starter boards and reduce blank-canvas anxiety before pushing broad imports.
Refresh flagship public boards: EP sequence, single rollout, demo pile, and feedback room.
Watch 10 to 20 serious artists and producers build a real board; record hesitation points.
Improve use-template, share, and export CTAs so public boards become product education.
Ask activated users whether sync, history, continuity, export, or collaboration is worth paying for.
Operating rule: no broad artist operating-system claim until activation, retention, and paid intent prove the narrower release workspace.
Start the board