Use when the user names a manual recurring job, asks whether something can be automated, or hands over an automation idea to size against a real before-after measure.
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 user names a manual recurring job, asks whether something can be automated, or hands over an automation idea to size.
The desired outcome, the current trigger, the steps, the owner, the volume, what goes wrong today, and what success looks like.
No volume figure means you size on their time estimate and mark the return on investment (ROI) as INFERENCE. No owner means nothing automates until someone owns the outcome.
Trigger, inputs, steps, decisions, owner, handoffs, output, recipient, and what proves it finished. Show the map first.
SOPs, trackers, and automations already covering this job. Overlap means improve or merge — never a second system doing the same thing.
In order: no change; stop or simplify the job; clarify ownership; fix the process or the source data; one-time AI help; human plus AI; deterministic automation; a new agent or standing cadence.
Say why the smaller options fail before you pick a bigger one.
The slice it covers, the window, the rollback, and the before-after metric — manual hours, cycle time, or error rate. Name the test that proves it works before it touches live work.
Report before-after and the ROI in hours saved. Fold kept automations into the SOP and into the automation backlog with effort and impact on each.
Never automate a process the owner has not approved for change. Never present an estimated saving as measured.
Save under automations: the decision brief, the pilot read, and the backlog.
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.