Franchise agreement assembly

The deal doesn't start in a file drop — it starts in Salesforce. When an opportunity moves to “Agreement,” Grain picks up the operating agreement, info sheet, and current FDD from the deal record; a deal-desk email with attachments works just as well. From that moment it's one durable task per deal.

Before anything is assembled, Grain builds the deal ledger — the owners table from the operating agreement, cross-checked against the info sheet — and runs the eligibility rulebook: state registration, disclosure timing, bonds, sanctions, trademark rules. A wrong rider voids a deal, so the rulebook is a hard gate: while anything blocks, no packet gets assembled.

The facts land organized and traceable — entities, owners, territory, FDD edition, clocks. Then the checks, and here the info sheet and the operating agreement disagree about which entity signs. That's not a footnote; it's a blocking question, and it goes straight to the deal owner.

The output is the agreement packet itself: the assembled agreement with the right state riders, the signature-field map, the transmittal email — plus the proof layer underneath. Validations list anything unresolved (the entity mismatch sits here until Marcus answers), an independent pass verifies the template edition against the FDD on file, and one page ties the whole deal together for review.

Marcus answers the entity question right in the chat, and Nia re-runs assembly from the checkpoint — seconds, not a fresh grind. When he approves, the transmittal goes out through the firm's own systems and the signature packet through DocuSign. Nia watches what comes back: signed documents wake the task, and she flags anything that changed since disclosure.