Use cases/Discount and promise guard

Discount and promise guard

Partly builtLDG-2275Sales as CodePromptComputeCommitOps

Discounts and commitments wait for a person in Sales as Code. The PromptCompute card and the CommitOps promise are still to build.

Use case

Discount and promise guard: a workflow across Sales as Code, PromptCompute, CommitOps that starts from a rep or agent proposes a discount or a date on a deal.

Who would use it

Revenue teams, and the finance and engineering leads who live with what was offered.

What value it provides

Each proposed discount or commitment reaches a person with the forecast's record and the answer to can we promise this by then.

Why it matters to the user

A discount approved on evidence protects margin, and a date checked against the work protects the renewal.

The problem

Reps and sales agents offer discounts and delivery dates to close. Finance and engineering find out after the contract is signed.

Expected outcomes

Discounts approved with evidence attached: target 100%
Promises made that CommitOps marked cannot tell
Kept rate of promises made through the guard

Each run records its outcome as met, not met or not measured.

How it runs

1. Hold the proposed discount or commitment for a personSales as CodeBuilt

2. Answer can we promise this by thenCommitOpsBuilt

3. Show the forecast record and the answer on the approval cardPromptComputePlanned

4. Record the promise once approvedCommitOpsPlanned

Products and connections

Product	Role in this workflow	Docs
Sales as Code	Hold the proposed discount or commitment for a person	Reference · Sales as Code docs
PromptCompute	Show the forecast record and the answer on the approval card	Reference · PromptCompute docs
CommitOps	Answer can we promise this by then; Record the promise once approved	Reference · CommitOps docs

Outside the family: HubSpot, Salesforce or Attio.

What a person approves

Action	Default risk
`sales.discount.approve`	high
`sales.commitment.approve`	high
`sales.proposal.send`	high

Action keys are from the PromptCompute catalog.

How to access it from an agent

An agent will run this workflow through the PromptReports MCP server or API, with an ID agent token. The runner will then call each product for it. Proposed

// MCP: https://mcp.promptreports.ai/mcp (Proposed)
start_run({
  workflow: "discount-and-promise-guard",
  inputs: { "deal": "Globex, 120 seats", "discount": "18%", "commitment": "SSO by 2027-01-15" },
  dry_run: false
})
// returns { run_id, status: "running", approvals_url }
get_run({ run_id })   // poll, or subscribe to run events

curl -X POST https://api.promptreports.ai/v1/runs \
  -H "Authorization: Bearer $PROMPTREPORTS_AGENT_TOKEN" \
  -d '{"workflow":"discount-and-promise-guard"}'

Or call the products yourself, step by step:

Product	Endpoint	Tools
Sales as Code	To confirm	to confirm
PromptCompute	`https://mcp.promptcompute.ai/mcp`	`request_approval` `get_approval` `cancel_approval` `answer_approver`
CommitOps	`https://commitops.ai/api/mcp`	`whoami` `list_assertions` `get_assertion` `promised_not_started`

Set it up

Sign in at app.promptreports.ai with PromptReports ID, and pick your org.
Connect Sales as Code, PromptCompute, CommitOps on the Connections page. Link HubSpot, Salesforce or Attio through the product that uses it.
Register the agent that will run it on the Agents page, and give it a version manifest.
Set the approval policy for sales.discount.approve, sales.commitment.approve, sales.proposal.send. Start with Require approval; critical actions are never auto.
Fill in the inputs (Deal, Discount, Commitment) and choose the trigger: a rep or agent proposes a discount or a date on a deal.
Start a dry run. It will count no workflow request, and it shows which steps would record missing evidence.
Start the run. Approve each gate in the approvals inbox, then read the signed record when it ends.