# Procurement playbook Human Guide

## What This Is For
When to Use Enterprise deals entering security/privacy review or contract negotiation. It gives the agent a clearer input/output frame for procurement playbook: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Procurement playbook agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for procurement playbook.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Procurement playbook guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Enterprise deals entering security/privacy review or contract negotiation.
- RFP/RFI responses requiring coordinated SME input.
- Situations with heavy exception requests, custom terms, or compliance evidence.
- **Requirement Intake** – capture questionnaires, policy docs, and mandatory deliverables.
- **Workstream Mapping** – assign internal SMEs (legal, security, privacy, finance) with timelines.
- **Evidence Library** – maintain templates for SOC2, penetration tests, insurance, data flows, DPIA.
- **Exception Management** – document asks, approvals, fallback positions, and decision owners.
- **Closeout** – log final concessions, expirations, and follow-up obligations.
- Procurement workback plan (deliverable, owner, due date, status).
- Security questionnaire index with sourcing notes.
- Exception request log with approval layers.
- Keep source-of-truth links updated; expired certifications stall reviews.

## Decision Points And Nuance
The original skill emphasizes: When to Use, Framework, Templates, Tips.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Starting without a clear audience or goal.
- Asking for a final artifact before sharing examples or constraints.
- Accepting a generic first draft without checking it against the intended use.

## Copy-And-Paste Prompt
```text
Use the Procurement playbook human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gtmagents/gtm-agents skill entry for `procurement-playbook`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Procurement Playbook Skill

## When to Use
- Enterprise deals entering security/privacy review or contract negotiation.
- RFP/RFI responses requiring coordinated SME input.
- Situations with heavy exception requests, custom terms, or compliance evidence.

## Framework
1. **Requirement Intake** – capture questionnaires, policy docs, and mandatory deliverables.
2. **Workstream Mapping** – assign internal SMEs (legal, security, privacy, finance) with timelines.
3. **Evidence Library** – maintain templates for SOC2, penetration tests, insurance, data flows, DPIA.
4. **Exception Management** – document asks, approvals, fallback positions, and decision owners.
5. **Closeout** – log final concessions, expirations, and follow-up obligations.

## Templates
- Procurement workback plan (deliverable, owner, due date, status).
- Security questionnaire index with sourcing notes.
- Exception request log with approval layers.

## Tips
- Keep source-of-truth links updated; expired certifications stall reviews.
- Coordinate with `cxo-briefing-kit` for executive escalations.
- Pair with `risk-register` to surface procurement blockers early.

---