Check a proposal or SOW draft for source support, scope clarity, internal consistency, approval gaps, and unsafe commitments.
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 internal approval or external send.
Verify that the customer problem and goals match the source record; deliverables have owners, dependencies, exclusions, and acceptance evidence; dates, price, terms, service levels, security claims, product claims, and customer references have approved sources; and totals, units, names, and dates agree throughout.
Flag vague scope, hidden assumptions, missing customer duties, unsupported claims, conflicting versions, empty placeholders, copied customer names, unapproved concessions, and legal language outside the playbook.
Group findings as must fix, approval needed, question, or polish. For each one cite the section, explain the risk, and draft a correction when the evidence supports it. End with a send-readiness checklist and named reviewers.
Do not mark a document final, send it, approve a commercial term, or give legal advice. Route legal clauses and departures to counsel.
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.