TillyGen and Salesforce

What this is about

Salesforce is the system of record for enterprise revenue: accounts, opportunities, contracts, dashboards leadership actually reads. When a media team or production vendor works with such organizations, the video project exists twice — as an opportunity that must report cleanly, and as a production that must shoot on real days. The bridge is documents and discipline: the TillyGen plan attaches to the opportunity as a file, delivery milestones in Salesforce mirror the schedule, and where volume justifies it, the TillyGen API feeds status into the fields reporting reads. Neither system pretends to be the other.

An integration is good when nobody talks about it any more: the data is where it is needed and nobody exports anything.

What runs differently here

In planning terms, that means:

• The opportunity carries the current plan PDF as an attached file — procurement and legal read the same schedule the crew shoots
• Milestone fields in Salesforce quote the TillyGen schedule, which keeps forecast dashboards honest about delivery
• With the TillyGen API and an integration layer, plan status can update opportunity fields on a schedule instead of by mail
• Account history accumulates: every past production's plan sits on its opportunity, searchable when the client scales up

Step by step

This order gets you there fastest:

1. Define at contract stage which plan artifacts the account team needs — usually schedule and delivery dates — and who updates them.
2. Plan the production in TillyGen and attach the exported PDF to the opportunity before the first internal forecast review quotes dates.
3. Mirror only milestones into Salesforce fields: shoot window, delivery date, review gates — never shot-level detail.
4. Where productions are frequent, connect the TillyGen API through the company's integration layer to update those fields on schedule.
5. At closure, leave the final plan and delivery confirmation on the record — enterprise clients audit, and the record answers.

Common pitfalls

What most often goes wrong in practice:

• Opportunity milestones maintained by hand drift from the schedule, and leadership plans revenue on dates production abandoned weeks ago
• Shot-level detail copied into Salesforce fields nobody reads — maintenance cost without a reader
• The plan attached once at kickoff and never refreshed: auditors later find a contract-stage schedule next to a very different delivered reality

With TillyGen

Salesforce reports the production's existence to the enterprise; TillyGen determines its shape. Milestones flow outward from the schedule, files carry the detail, and the working plan never lives in a CRM field.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.