Use when a partnership hits its lifecycle tail: change control mid-term, the renewal play from 120 days out, and clean exits with dated transitions.
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 a partnership reaches its lifecycle tail. Start from the agreement (term, renewal, notice, exit clauses), the partnership health and delivery reads, the renewal or change request itself, and who owns the commercial call.
Log the requested change, its commercial and delivery impact, and the approval it needs. No change takes effect without the owner's yes and a dated amendment note.
Scope creep with no change record behind it gets called out, not absorbed.
Open the renewal window 120 days out with a health grade, a wins-and-gaps record, and the renewal motion: auto-renew, renegotiate, expand, or exit.
The 90-day mark is the standard non-renewal notice deadline, and the play has to beat it rather than meet it.
A renegotiation draft pairs every ask with a concession, and every concession sits inside the guardrail bands.
The notice-period timeline, the client and pipeline transition, the knowledge handover, and the joint statement draft.
Exits are staged as drafts with their evidence. The owner makes the call.
Every renewal, amendment, and exit, dated with its trigger and its outcome, so the next cycle starts from evidence instead of recollection.
The change log, the renewal play with its drafts, the exit plan where one is called for, and the updated lifecycle log.
No agreement on file means drafting from owner-stated terms marked INFERENCE, and flagging Legal review as the first step. No health read means running the portfolio health scan before the renewal play.
No renewal term, amendment, or exit notice goes to the partner 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.