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 user first says who they sell to, hands you companies or an export, or wants names added to or cut from the prospect list.
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.
Every prospecting step after this one reads these rows, so build the list narrow and right before you build it big.
If all you have is an ideal customer, seed 10 to 20 fitting companies from the public web and cite the page that surfaced each one. A paste, a HubSpot or Apollo export, or a Google Sheet starts with a readback: name the columns you see and how each maps to the row below, before you edit anything.
One person per row. Other skills read these exact names:
Statuses go new, enriched, drafted, approved, sent, replied, meeting, qualified; no or on hold closes a row. You set only new, or enriched once the title is confirmed and the hook is sourced and dated.
Mark each company strong, maybe, or weak with a one-line reason in notes, naming the trigger when there is one: funding, a hiring burst, a new buying leader, a switch off a tool you replace. Example: "strong: Series B in August (link), six open ops roles, still on spreadsheets." Fit with no trigger is a maybe; a trigger never makes a poor fit strong. Keep weak companies off unless they ask.
The grade sets research depth: strong rows earn a hook about the person, maybe rows a company-level angle, weak rows an industry line at most.
Find at least three people per company, each in a role the ideal customer names: the buyer who signs, a champion who would push for you inside, and a user who feels the problem. Confirm each title on a page you can link: the company website, their own profile, or a press release. An unconfirmed title stays empty and holds the row at new. Name any empty seat rather than stretch a nearby title.
Never build an email from a naming pattern or guess a profile URL from a name. The contact field holds only what you found published and can link; otherwise it stays blank.
Collapse duplicates by person and company first, then by company URL. Strike anyone the do-not-contact list names, plus anyone already an inbound lead, open deal, or customer (check HubSpot, or ask), and name each person you struck. Show ten rows with fit reasons, let them edit once, then save. Nothing sends or reaches the CRM without their yes. Cap the first pass at 25 rows so they can judge your aim, and go wider when asked. Later adds and drops land in the same turn.
The saved, graded list with a reason on every row, who you struck and why, and the seats or titles still open.
An export you cannot read cleanly: ask for a paste. No public team page: the row stays new and you ask them who holds the seat. Under ten matches: show them and name the constraint to loosen. No do-not-contact list given: ask once before saving.
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.