Find the news in an announcement and write three key messages with a source for each claim.
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 before writing a release, a pitch, or a launch plan.
Write down in one sentence what changed, for whom, and since when. Ask why someone outside the company would care: a number that moved, a problem solved, a first, a trend it fits, or a local link. If the only answer is that the company is excited, say the news is thin and suggest what would make it stronger, such as a customer result, fresh data, or a better date.
Offer up to three angles. For each, name the reader it suits and the kind of outlet that covers it. Then write three key messages, each one sentence long, each backed by a fact the user can point to.
List every claim in the messages with:
Do not invent a figure, customer, award, or trend to make the angle work. Never present a message as approved or send it to anyone; the user decides which angle to use.
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.