Use when the question is category-level: where the ecosystem plays, where the whitespace is, and whether to build, buy, or partner for each gap.
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 question is category-level rather than partner-level. Start from the category, the current partners, CRM account overlaps, and any technology-stack or market signals on hand.
Who plays in each category, split by motion — solutions and services against independent software vendors (ISVs) and technology partners — our coverage per category, and the evidence behind every placement.
A category with no evidence behind it is UNKNOWN, not empty.
Each gap gets potential, strategic fit, and reachability, with one evidence line each. Add integration-attached retention as a value signal: accounts with an integration live retain better, and that is worth naming.
Rank the gaps. Cut the ones with no path — a gap we cannot reach is not an opportunity.
One paragraph of rationale per gap. A partner gap gets a candidate thesis: the partner type, the value exchange, and the first three prospect names where the evidence supports them.
One card per opportunity — potential, impact, fit — and hand the qualified names to the sourcing motion with the thesis attached, rather than as a bare list.
The category map, the ranked whitespace list, the build/buy/partner calls, and the opportunity cards.
Thin CRM data means a shorter map built from public research, marked INFERENCE, with the data that would grow it named explicitly.
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.