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.
Use when owning how a region or category wins: go-to-market strategy, operating model, market entry, and category ownership.
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.
Run this when owning how a region or category wins — the go-to-market (GTM) strategy, the operating model, market entry, and category ownership.
The region or category, the revenue and margin targets, the current coverage and pipeline, the regulatory landscape, and the partner and competitive set.
Where we play, how we win, and what winning costs. Name the segments, the plays, and the number each play must deliver. A strategy with no number is a wish.
Coverage by segment, deal governance per region, the partner attach motion, and the revenue-operations, product, and marketing owners. Every line has one owner and one date.
Licensing, data, tax, and employment rules that gate selling. A market with uncleared gates stays in plan, never in forecast.
Publish how we win the vertical with proof, battlecards, and reference wins. Review quarterly against win rate and cycle time; a category with no proof gets no plays.
Budget, volume, margin, and headcount. Read progress monthly in one GTM read: pipeline created, coverage, and the resource moves the numbers demand.
One-page strategy, operating model with owners, market-entry gate map, category win pack, and the regional plan with monthly reads.
No regulatory read: list the gates as UNKNOWN and ask for legal before any entry date. No segment data: draft from CRM history and mark the model INFERENCE.
Nothing exec-facing sends and no market entry or headcount commitment is final 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.