Use when partner readiness needs a system rather than a course: academy design, certification operations, train-the-trainer, readiness coaching.
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 partner readiness needs a system rather than a course. Start from the learner population (roles, count, geographies), the current training and certification state, the academy platform, and the readiness bar per role.
Learning paths per role — sell, implement, support — with modules that name their outcomes, and a certification ladder with pass bars and a twelve-month expiry.
Each path names its owner and its refresh SLA. A path with no refresh date decays quietly, which is the failure mode worth designing out.
Enrolment targets, exam operations, the tracking dashboard, and the re-certification triggers.
Read throughput and pass rates monthly, tied to business impact — partner revenue, retention, delivery quality, satisfaction — not to completion counts alone. A path below its bar gets one dated fix window.
Certify partner trainers against a quoted rubric, hand them the kit (decks, labs, exams), and audit their first cohorts.
A trainer who misses the bar re-certifies. They do not scale.
Delivery-readiness checks per team, adoption coaching where AI tooling is in play, and a scored 1-to-5 readiness rubric per area with a banded interpretation behind the ready or not-ready call — with its evidence — before a team takes client work.
The academy blueprint, the certification dashboard read, the trainer roster, and the readiness calls with their evidence.
No platform means running from shared documents and sheets marked as interim, with platform selection as the first action. No readiness bar means drafting one from the delivery needs and confirming with the owner.
No academy content, certification grant, or readiness call goes to a 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.