In development · Interactive examples use fictional data
Production workspaceIllustrative data
EXAMPLE PROJECT
One source. Three directions.
Lead with the first action.
Type treatmentEditorial / sentence caseReview stateCandidate for review
No upload, rendering or approval service connected.
Approved sourceA deliberate set of cutsA clear review decision
Your team’s workflow
Start with the campaign
Keep the intended audience, message and call to action beside the source footage. Decide which claims have been approved before producing variations. A more efficient edit should not introduce an unreviewed claim.
EditorialMake it a small ritual.9:16 / caption treatmentDirectGOOD THINGS. START SMALL.9:16 / caption treatmentMinimalShow up again.9:16 / caption treatment
Type, placement and review context stay with the candidate.
Your team’s workflow
Give every version a purpose
A product introduction, a demonstration and a customer question each call for a different opening. Organize versions by the job they do rather than producing minor changes without a review plan.
Record which material was useful, what required rework and which formats the team actually used. The initial scope focuses on preparing and reviewing exports. Performance attribution and automated publishing are separate future capabilities.
Starting pointApproved interview / three audience questions
Keep the source and scope attached to the work.
✓
Useful handoffA candidate cut for each question, with a shared review note
The next owner needs enough context to understand the deliverable.
✓
Review decisionReview whether each cut makes sense without the full interview.
A named owner should be able to accept, revise or reject the direction.
The details matter
Make the next decision deliberate.
Build around the editorial question
An interview, demonstration or event recording can support several short pieces, but each piece needs a clear reason to exist. Start with the audience question and choose the source segment that answers it. A clip should be understandable outside the full recording. Check that editing has not changed the meaning of a quote or removed a necessary qualification.
Create a weekly review rhythm
Agree when the team reviews candidates and who can make the final decision. Keep a small enough set for a useful conversation. Once the message and framing are accepted, check captions, formats and naming before handing the package to the publishing owner. The proposed pilot ends at an agreed deliverable, not a promise of content performance.
A worked planning record
The brief stays with the work.
A source, a set of candidates and the decision that moves the project forward.
ViralCLI / Decision recordExample
01
Starting pointApproved interview / three audience questions
Keep the source and scope attached to the work.
02
Useful handoffA candidate cut for each question, with a shared review note
The next owner needs enough context to understand the deliverable.
03
Review decisionReview whether each cut makes sense without the full interview.
A named owner should be able to accept, revise or reject the direction.
A few things to make clear.
Can I use ViralCLI today?+
The public website, guides and templates are available now. The product workspace is in private development; request a pilot to discuss access and scope. Demonstrations on this site are illustrative, and automatic highlights and transcription are not available.
Do I need to use a terminal?+
No. Development includes a browser editor plus CLI and API workflows. These product tools are not publicly accessible on this website; pilot access and supported workflows are agreed separately.
Will it generate all of my footage?+
The initial scope starts with footage you own or have permission to use. Generative video is not part of the promised pilot.
What should we agree before a pilot?+
Source permissions, supported inputs, output formats, candidate limits, review rounds and the person approving the work. No video-processing service is available on this website.