Use when the partnership is about data or research: licensing and evaluation terms, academic collaboration, and IP and data-rights compliance.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when the partnership is about data or research rather than go-to-market. Start from the data or research asset, the counterparty (a company, a lab, a university), any existing non-disclosure agreements (NDAs), material transfer agreements (MTAs), or licence drafts, and the intellectual property (IP) and compliance constraints.
Define the asset — a dataset, a model, a protocol, physical samples — the permitted uses, and what is explicitly out of scope.
Evaluation access gets dated terms and a conversion path to a licence. Nothing open-ended.
Licence scope and fees, data-sharing rights, publication and IP ownership, confidentiality, term and termination.
Every clause routes to Legal before it leaves. There are no exceptions to that line.
One row per alliance: its agreements, the key dates (expiry, review, publication windows), the obligations due, and a red/yellow/green compliance grade.
Anything yellow gets a dated cure line with an owner.
Which alliances produced — papers, products, revenue — which stalled, and the renew, expand, or exit call per alliance with its evidence.
The alliance scope, the terms-spine draft, the compliance tracker, and the quarterly portfolio read.
No existing drafts means starting from owner-stated intent marked INFERENCE, with Legal review as the first step. No compliance owner means the owner holds it until one is named.
No term sheet, licence, material transfer agreement, or publication approval goes out without your explicit yes.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.