Use when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
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 partners deliver client work in your name. Start from the in-flight engagement book (partner, client, scope, dates, staffing), the delivery status per engagement, the escalation history, and the client success criteria.
One row per engagement: partner, client, scope, milestone dates, the staffed team, and a red/yellow/green delivery grade with one line of evidence behind it. A grade with no evidence stays UNKNOWN.
The book is rebuilt weekly from the tracker, never from memory.
Most-at-risk first, one decision per engagement: on track, needs support, restaff, or escalate.
Before any escalation, build the peer map — functional peers with equal decision authority on both sides — and escalate peer-to-peer first.
A staffing gap gets a dated restaff line with an owner. Anything red two weeks running gets an executive escalation draft.
Name the failure mode — staffing, skill, scope, or client-side — pick one save motion with a date, and log it.
A third straight red week triggers the save-or-exit call with its evidence attached.
A per-partner delivery-quality read: on-time rate, escalation count, client satisfaction. It feeds the portfolio review and the renewal call, so delivery shows up in the commercial decision rather than beside it.
The graded engagement book, the weekly review log with its decisions, the active rescue plans, and the quarterly delivery-quality read.
No tracker means building the book from owner-pasted status notes marked INFERENCE, with standing up the tracker as the first action. No success criteria means drafting them from scope and confirming with the owner.
No staffing change, escalation, or client-facing message 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.