Every shoot day crewed. Every round accounted for.

Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected project creation, edits, the crew and vendor store and resource setup. They preserve native account permissions, unrelated custom fields and row history, enforce the production rules and the storage guard on the server, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.

One contact-linked opportunity is one video project. It holds the client and project labels, the recorded stage with the date it was entered, budget and deposit as recorded references, the recorded lock days, a release-forms-on-file flag, a usage term with its expiry, an editable checklist, and stable child rows: shoot days with a call time, location label and location, gear hold and contact confirmed flags; crew roles with the role label the company uses and a crew reference or an empty one meaning unfilled; deliverables with a format label, due date, rounds included and state; and versions with their position in the chain and the date each was sent. Crew and vendors live in the kit’s own store behind a server-owned revision, because a freelancer exists before any project books them.

Callsheet stores no files, no footage, no link with a user name and password inside it, no talent identity document and no payment detail. Release forms are a recorded on-file yes or no flag and nothing more, and every free-text field refuses credential links, government identifiers and card-like digit runs in the browser and again on the server while still accepting a plain review link, a timecode, a phone number and a purchase order reference. That is a guard against accidental entry, not a guarantee. A shoot day is flagged only when it sits inside the lock days that project recorded and still has a role unfilled or a location nobody has confirmed, and the lock day itself is inside the window. A cut is late strictly after its due date, and rounds used are the recorded versions after the first. There is no file storage, review player or version hosting, no editing software or asset manager integration, no crew payroll or booking marketplace, no permit, insurance or release management, no music licensing, no scheduling engine, no automated messaging and no payments or invoicing.

Four optional pipeline templates and nine inactive workflow drafts. 12 fictional in-memory projects with 6 shoot days and 17 deliverables.

Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.