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 the market needs a new category no single vendor can name alone: the category thesis, the lighthouse coalition, and the launch beats.
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 market needs a new category and no single vendor can name it alone. Start from the market shift the category rides, the lighthouse partners and analysts in play, the existing joint proof (wins, numbers, quotes), and the launch window and budget.
The shift. The old way and why it breaks. The new way in one sentence. The written point of view the coalition evangelises — world changed, old way broken, new way, stakes — which has to be true even if we did not exist. The category name with its ownability tests: analyst adoption, the budget-line-item test, and the would-this-have-an-encyclopedia-entry-in- three-years test. And the three proof points that must exist before launch.
Each claim names its evidence or stays UNKNOWN. A thesis with no named shift is positioning, not a category.
At most five lighthouse partners, each with a named executive sponsor and a dated commitment. Two analysts briefed early. One lighthouse customer per partner where possible.
Each member gets a role — proof, reach, or credibility — and a dated deliverable. A member with no dated deliverable is a logo, not a coalition partner.
One shared story every partner tells. Objection-mapped proof: closest-customer-first, every number sourced, partner claims kept in their own words.
Then a dated beat plan — analyst briefings, the joint launch, lighthouse wins, event moments.
Proof the owner has not approved stays internal. Nothing partner-facing leaves without the owner's yes.
One ignition moment three to six months after the point of view lands — broad reach plus direct outreach, aimed at the category rather than the product — with 30-day success criteria written before it fires.
Then dated beats, each with an owner per side, a success line, and a recap inside 48 hours with owners and dates.
After launch, track the category signals quarterly — analyst mentions, inbound using the name, win-rate lift — against a year-one, year-two, year-three flywheel, and reallocate beats toward what moves. A beat that misses twice gets one fix, then it is cut.
The one-page thesis, the coalition roster with its dated commitments, the shared narrative with its proof, and the beat plan with its recaps.
No lighthouse partners yet means thesis first, with coalition seats marked UNKNOWN for the owner to fill. No budget means a proof-first plan — the narrative plus one lighthouse win — before any launch beat.
No thesis, narrative, proof, or launch beat goes to a partner, an analyst, or the public 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.