Anjin Media

Contact

Bring your own footage.
The demo runs on it.

Send a session or two before the call - a town hall, a webinar, a long interview - and we load it, write a brief while you watch, and read the plan that comes back with you.

Enterprise demos · procurement questions

What a demo covers

Three things, in this order.

The work that makes a demo worth having happens before the call, which is why we ask for footage first.

01

Your footage

Whatever you send is ingested before we speak: transcribed with timecodes, angles registered, speakers separated. What you watch afterwards is your material - your speakers, your subject matter, your vocabulary.

02

A live brief

You describe the edit you want while we are on the call, in a sentence or a paragraph. The platform plans it: segments chosen from what was actually said, ordered to carry the argument, timed to the length you set. Strike a segment or reorder the plan and the running duration recomputes in front of you.

03

A provenance walkthrough

Then the part a technical buyer came for: the plan read against the source, each segment naming the group and timecodes it came from, and the finished render with its captions, EDL and QC report - the artefacts your team would audit.

If the conversation is about an archive rather than a single project, the packages and the roadmap are already written down - the enterprise page →

Where to write

Two addresses.

Both are read by people, and both are new - see the note underneath.

No form, on purpose

A contact form that fails quietly costs you a reply and tells us nothing about it, so this page publishes addresses it can be held to instead. Those mailboxes are being set up ahead of launch: if a message bounces before launch day, that is the reason, and clearing it is on us.

Found a security issue? The reporting address, the acknowledgement we commit to and the safe-harbour terms are set out on the security page →

The rest is one upload away.

One video or an entire archive.