Sales Engineer: PoC Success Criteria Negotiator
For SEs negotiating PoC terms: builds the counter-proposal that is achievable for you AND meaningful to the buyer — so the PoC ends in yes, not we need more time.
See it work
Watch a sample run end to end: your input goes in, the agent workforce does the work, and a branded result comes back. Sample data shown for the demo.
What You'll Receive
- Problem With Their Proposal
- Counter-Proposal Metrics
- Negotiation Script
Powered by
How to Get the Best Results
- 1
Richer input = sharper output. Paste real data rather than generic placeholders — the AI reasons on specifics, not hypotheticals.
- 2
Each run is a fresh analysis. If the first result isn't exactly right, refine your input and run again — small wording changes can shift the quality of the output meaningfully.
- 3
Fill every field you can, not just the required ones. Optional fields guide the AI toward your specific context, removing generic assumptions.
KAIRO Operating Layer
What should Sales Engineer: PoC Success Criteria Negotiator help you move right now?
This tool is not a single prompt. It is a KAIRO operating lane designed to produce usable copy, workflow steps, or an operational artifact, then package the result into a usable business artifact.
Mission: Turn market timing, buyer fit, and outreach context into a revenue action that can move pipeline today.
Boardroom Assignment
Input Intelligence
What buyer proposed for the PoC
requiredPaste real notes, transcript, account context, or current copy. Dense input beats generic prompts.
What you can realistically deliver
contextUse a specific role, offer, ICP, or business constraint.
Where our product clearly wins
contextUse a specific role, offer, ICP, or business constraint.
Run Plan
- 1Read the missionKAIRO normalizes your inputs, identifies the operating lane, and frames the job as produce usable copy, workflow steps, or an operational artifact.
- 2Pull the intelligenceThe run checks CLAUDE and uses the available context without asking you to browse a separate tool stack.
- 3Assemble the boardroomA lead, specialist, scout, local reasoning lane, and critic each own a different failure mode before the output reaches you.
- 4Produce the artifactThe output is shaped into Problem With Their Proposal, Counter-Proposal Metrics, Negotiation Script.
Quality Gates
Specificity gate
Rejects generic advice and forces the result to reference the account, buyer, workflow, or constraint you provided.
Actionability gate
Every recommendation must become a next move, message, owner, score, risk, or decision point.
Confidence gate
Separates strong signals from assumptions so you know what is safe to act on.
Example Missions
Fast run
What buyer proposed for the PoC: 90-day PoC where we prove we replace ZoomInfo for the entire 8-person SDR team, contact accuracy must be 95%+
High-context run
Add the buyer, trigger, current state, and what you want KAIRO to produce next.
Boardroom run
Use this when the output will influence a customer, campaign, deal, or executive decision.
Next Actions
Copy the strongest asset
Use the most actionable section from Sales Engineer: PoC Success Criteria Negotiator as your email, brief, scorecard, playbook, or internal note.
Package the board artifact
Export the PDF or deck when the output needs to travel to a stakeholder or become part of a client file.
Chain into the next tool
Use the result as input to scoring, sequencing, forecasting, or another field-specific tool instead of starting over.
Deliverable Studio
Report and deck templates for this tool
Input
Sign-in required · 8 runs / min