Take a competitor apart in a way that changes a decision: what they promise, who they are built for, where they are weak, and what we should do about it.
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 someone asks about a competitor. A teardown that ends in observations has failed; it ends in a decision.
Four sources, in this order, because each one contradicts the last in a useful way:
Answer these and nothing else:
The fourth question is the one people skip. A teardown with no honest praise in it is not research, it is reassurance.
A page. Their promise, their customer, three strengths, three structural weaknesses, and one recommendation with a reason. Mark every claim as observed or inferred — a reader needs to know which parts would survive a phone call.
Never state a competitor's revenue, headcount, churn or customer count as fact unless it is published — say "inferred from" and name what you inferred it from. Never repeat a rumour. Never write a comparison that a competitor could sue over, and never recommend copying a feature without saying what it would cost us.
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.