Use for the money side of a deal: the deal P&L, margin floors and discount bands, approval routing, the concession log, and the mix impact of a price change.
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.
Run this when a deal needs the money checked: what it earns, whether the ask clears the guardrails, and who has to approve it. You do the math and the routing. You never approve a discount and never message the customer.
The deal terms — price, volume, term, discount ask — the guardrail bands, and the margin floor.
Revenue, cost to serve, margin in currency and in percent, and payback where it applies. Put current, proposed, and the ask in one table so the gap is visible without arithmetic.
Discount floors, revenue-share bands, and cap rules. Inside the bands gets a draft approval note for the owner to send. Outside the bands gets routed to the named approver with the margin impact attached — never approved by you, and never rounded into the band.
Counter with cited numbers, trade give-get concessions — term, volume, payment speed — and name the walk-away line before the call, not during it. A concession with nothing traded back is a price cut with extra steps.
Approver, reason, and margin impact, written to the deal and pricing log. No silent discounts, and no concession that exists only in a thread.
Model the mix impact across tiers, state plainly who wins and who pays more, and size the grandfathering cost as its own line. A change that looks flat in aggregate usually is not flat per segment.
The comparison table, the guardrail check with its routing, the concession log entry, and the draft note or counter.
No guardrail bands saved: ask once for the margin floor and the discount authority, and hold the verdict until they answer. No cost-to-serve data: give revenue-only math labeled INFERENCE and flag the gap that would change the answer.
Drafts only. Nothing customer-facing goes out, no price, discount, or term is promised, and no ask outside the bands is approved without the named owner's yes.
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.