INDIVIDUAL
Watch, listen, buy, subscribe, create or publish without configuring an organisation.
HEADTURNED STUDIO
Watch one thing. Buy one Work. Subscribe to a Channel. Create something. Run a Project. Bring together a Team or Organisation. STUDIO introduces structure only when the work needs it.
One STUDIO
STUDIO is deliberately progressive. An audience member can simply discover and watch. A creator can publish one Work. A substantial project can add collaborators. Repeated work can gain a Workspace. Teams and Organisations appear when they solve a real institutional problem—not because the platform wants more setup.
Choose your depth
Find work. Watch, listen and return.
Pay for a Work without adopting a subscription.
Build an ongoing relationship with Channels you value.
Begin with one Work and grow a Catalogue.
Use Projects when work needs collaborators and structure.
Add Workspaces, Teams and Organisations when sustained institutional work genuinely needs them.
Publishing + working
STUDIO brings two complementary capability families into one product: publishing and commercial technology around Channels, Works, Catalogues, discovery, purchases, subscriptions and earnings; and working technology around Projects, Workspaces, Teams and Organisations.
Who is STUDIO for?
The same platform can stay deliberately small for one person and provide substantially more structure for collaborative and institutional work.
Watch, listen, buy, subscribe, create or publish without configuring an organisation.
Build Channels, Works, structured releases and a Catalogue; publish and participate commercially.
Bring collaborators around a defined piece of work without forcing a larger structure first.
Support courses, practical projects, media, collaboration and knowledge that can move between learners and real work.
Use contained working structures, Projects, reusable groups and governed collaboration when institutional scale requires them.
Governed collaboration
Projects are private by default. Workspaces provide contained environments for sustained collaboration. Membership of a Workspace, Team or Organisation does not automatically expose every Project, every piece of working media or every publishing surface.
Begin privately. A Project can exist for one person or add explicit collaborators without opening the rest of your working environment.
Access follows the relationship actually granted. Being part of a Workspace or Team does not silently grant access to unrelated confidential Project material.
Use a Workspace when multiple Projects, recurring collaborators, shared resources or institutional governance need a durable working boundary.
Work with people from your own organisation and, where an explicit invitation relationship permits it, bring the right external collaborator into the specific work that needs them—without making everything else visible.
Working together does not automatically grant publishing or commercial authority. A private working relationship stays separate from what is deliberately released through a Channel.
Projects can remain simple. Workspaces, reusable Teams and Organisation governance are introduced progressively when the scale and responsibility of the work justify them.
Schools · colleges · universities
STUDIO can connect structured learning with Projects, people, working media and publishable Works. A course can sit within a much larger environment in which learners and educators create, collaborate and connect knowledge with practical work.
Institutional structures can be introduced where governance, repeated collaboration, multiple Projects or reusable Teams require them, while the individual experience remains focused on the work in front of them.
Commercial choice
STUDIO supports individual purchases as well as subscriptions. The commercial model does not require every audience relationship to become recurring simply because recurring payment exists.
HEADTURNED STUDIO
Audience, creator, educator, learner, collaborator, project team or organisation—STUDIO is designed to reveal its power progressively rather than demand complexity up front.