demographic

be targets different audiences based on it's level of maturity.

Initially, be is targeted at:

1. Home users looking to start projects and collaborate remotely.
2. Free communities, like Blender and it's surrounding ecosystem of projects.
3. Those who favour quantity over quality, such as Third Floor here in London and similar studios working with pre-vis, which is a growing trend with little infrastructure support (no shotgun or ftrack for those guys, it's too slow).
4. Schools/students looking to learn from projects with coherent sets of content.

Later, be targets:

1. All of the above
2. Feature film
3. Web
4. Music

a story

This is the story of the freelancer on his first day at Studio Omega.

1. <-> Greetings
2. <-| Project brief
3. <-| Here's your computer
4. |-> Where are the files?
5. |-> How do I save files?

todo

target audiences at each extreme

Local features include the templating engine, environment management and presets, whereas remote features include the sharing of presets, projects and content.

Remote features lay the groundwork for adoption, as home users can instantly find value within the first 10 minutes of using the product. But local features are what will make users stick around. Once a company does adopt, the remote features will be less relevant and all eye will be on local capabilities.

The balance to be struck is where both ends have a low enough of a learning curve for users to want to invest their time in, for the remote side to withstand the pressure of a global adoption of mostly home users (i.e. with less focus on enterprise features, such as security) whilst the local side must withstand the test of time. To be flexible enough to build a strong reputation and ultimately last across multiple projects.