Custom website · Product showcase and private access · 2026
Neovela
Neovela is a creator-owned platform for vertical drama — shorts, series and novelas made with real actors, and fans who help shape what happens next. We built the site that carries it through beta and toward its Indiegogo launch: a public showcase where visitors can operate the product rather than read about it, a plain explanation of how creators keep their rights and get paid, and a private investor presentation that stays private at the server, not just in the navigation.
Our role
Brand direction · Site design & build · Interactive product demos · Private access control · Story authoring tools

Neovela
A pre-launch homepage for creator-owned vertical drama, heading to Indiegogo.
1 / 5

The product, in motion
Tabbed live demos — episode player, actor and character, troupe studio, feeds, events — run on labelled concept data.
1 / 5

The movement
Clear explanations of IP ownership, shared troupe income, and direct performer income.
1 / 5

The troupe studio
A production console, script assistant, and living show bible for the whole ensemble.
1 / 5

Connect and create
Fans follow actors in and out of character; creators build their own series in the Writers Room.
1 / 5
A showcase you can operate
The homepage presents the platform through a tabbed set of working demonstrations rather than static screenshots: an episode player where a cliffhanger becomes a fan vote, actor and character views, the troupe and AI studio, a browse feed, actor feeds, and events and pop-ups. Each runs on clearly labelled concept data held in memory, so nothing implies a live payment or an AI call that has not been made.
The troupe studio view goes further. Production metrics, revenue splits, cast allocation, and fate-vote management sit in one console, alongside script assistant and living show bible views, so a visitor can see how an ensemble would actually run a show.
Explaining the deal plainly
The movement section sets out what makes the platform different in direct terms: no AI actors, creators keep their characters and worlds, clear e-contracts for every split, and revenue that flows both to the troupe and directly to performers.
A connect-and-create section then routes each audience to its path — fans toward actors, fan clubs, pop-ups, and fate votes; creators toward building their own series in the Writers Room.
The writers room, built as a tool
The writers room is a working authoring application, not a mockup: a show bible, storyboarding across series, season, episode, and beat, dialogue writing, and a filming prompter mode. A long story paragraph can seed the structure in one pass.
Signed-in writers get a cloud story library — projects and members held in the backend, shared by email, with access enforced at the data layer. Without an account the same tool falls back to local storage, so nothing is lost while the account system matures.
Investor material behind a real gate
The investor presentation is not simply a page that is hard to find. Its sections are delivered only after a server-verified session check, and the public bundle never carries the investor copy. Older section URLs redirect into the gated presentation, and search engines are told not to index it.
The financial package — budgets and supporting documents — is served through the same session check, so access to one does not quietly grant access to the other.
A party game that proves the workflow
The Neovela Game turns the same story process into a group activity: gather a crew, spin a melodrama challenge, plan it in minutes, shoot it on a phone, and post it for votes. AI-written story seeds and a seed box of your own keep the rounds moving.
It also works as an internal test of the plan-shoot-vote flow the platform itself will ask of troupes, exercised long before that path is finished.
Built to move
The platform is web-first on standard browser APIs — camera, media, push — so the same codebase can be wrapped for the app stores later without a rewrite.
The production studio that follows is planned the same way: the browser records an edit decision list and a server worker renders the final master, because in-browser video rendering is unreliable on mobile.
Outcomes
- Public demos that operate the product instead of describing it
- A creator-rights and earnings story told in plain language
- A writers room with cloud story libraries and data-layer sharing rules
- Investor and financial material readable only after a server-side access check
- A party game that exercises the plan-shoot-vote workflow
- One web codebase positioned to wrap for app stores later

