Claude Skill

procurement-and-sourcing

Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists. Use this to run an RFP or vendor selection, negotiate a purchase, consolidate spend across a category, decide between single and multiple suppliers, or bring un

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download cbrock84-headcount-plugins_operations_skills_procurement-and-sourcing-98d1c17.zip · 3 KB
Part of cbrock84/headcount — 160 skills

Install

skills CLI npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/procurement-and-sourcing
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
Git git clone https://github.com/cbrock84/headcount.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cbrock84/headcount collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Procurement and sourcing

This is everything before signature: deciding what to buy, from whom, and on what terms. operations:vendor-management takes over afterward — performance, renewals, exit.

Specify the need, not the product

Most bad purchases are decided before any supplier is contacted, when a requirement is written as a product someone already wanted. Specify the outcome and the constraints; let suppliers propose how.

Separate genuine requirements from preferences, and be honest about which is which. A requirements list that only one supplier satisfies is a purchase order with extra steps, and everyone involved knows it.

Involve the people who will live with the choice. Procurement that optimizes price against a specification the users did not agree to produces a cheap thing nobody uses.

Competition is the leverage

Price is set by the credible presence of an alternative, not by negotiating skill. The single most effective act in sourcing is having a real second option — and being willing to take it.

Run a fair process: same information to every bidder, same questions answered for all, scoring agreed before responses arrive. Scoring invented afterward reliably rediscovers the preferred supplier.

Where genuine competition is impossible — an incumbent with switching costs, a sole source — acknowledge it rather than staging a process. Then negotiate on the things still open: term length, renewal caps, service levels, exit assistance.

Total cost, not price

The quoted figure is a fraction of what you will spend. Model implementation, integration, training, the internal effort to run it, and what leaving costs.

Watch for cost that arrives later by design: per-seat pricing that grows with headcount, usage pricing with no cap, renewal uplifts, and support tiers that turn out to be mandatory. Ask what this costs in year three, and get the answer in the contract.

Category strategy

Aggregate spend before negotiating it. The same category bought independently by four teams is four weak negotiating positions and usually four overlapping tools.

Segment by leverage: high-spend commodity categories reward consolidation and hard negotiation; low-spend specialist ones are not worth the process cost. Concentrating everything on one supplier buys a discount and sells an exit — see operations:business-continuity-and-resilience before deciding that trade.

Route the resulting terms through legal-risk:contract-review, and anything touching customer data through legal-risk:privacy-and-data-protection before signature rather than after.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Procure-to-pay: Coupa, SAP Ariba, Zip, Precoro, and similar. At smaller scale a request form plus the accounting system's purchase orders does the same work.

Spend visibility: Ramp, Brex, Vertice, and similar, read against the ledger.

Vendor risk lives in the GRC tooling, not here — but the intake form is where the security and privacy review has to be triggered, or it never happens.

Never

  • Write a requirement that only the preferred supplier can meet.
  • Agree scoring criteria after responses arrive.
  • Negotiate on price without modeling year-three total cost.
  • Consolidate a critical category onto one supplier without pricing the exit.
Files (headcount)
  • references
    • sources.md 2.3 KB
      # Sources — `operations:procurement-and-sourcing`
      
      <!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
      
      Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
      
      ## 21 CFR Part 117 — preventive controls for human food
      
      US Food and Drug Administration · US · public domain (US government) — quote freely
      
      <https://www.ecfr.gov/current/title-21/chapter-I/subchapter-B/part-117>
      
      **Authoritative for:** Whether a food operation's hazard analysis, preventive controls and supplier verification are legally sufficient. Binding law rather than guidance.
      
      ## Federal Acquisition Regulation
      
      US General Services Administration, on behalf of the FAR Council · US · public domain (US government) — quote freely
      
      <https://www.acquisition.gov/browse/index/far>
      
      Machine-readable: <https://www.acquisition.gov/far/part-31>
      
      **Authoritative for:** What a competitive sourcing process must do to be lawful — solicitation types, evaluation criteria, competition requirements, and how contract type allocates risk. Binding for federal buying and the reference everywhere else.
      
      ## Incoterms rules
      
      International Chamber of Commerce · global · **sold — cite the identifier only, never the text**
      
      <https://iccwbo.org/business-solutions/incoterms-rules/>
      
      **Authoritative for:** Exactly where risk, cost and delivery obligation transfer between buyer and seller under a named three-letter term. Courts and contracts defer to it, and the full rules text is sold — name the term, do not reproduce the definition.
      
      ## Interagency Guidance on Third-Party Relationships: Risk Management
      
      Federal Reserve, FDIC and OCC · US · public domain (US government) — quote freely
      
      <https://www.federalreserve.gov/newsevents/pressreleases/bcreg20230606a.htm>
      
      **Authoritative for:** What due diligence, contract terms, monitoring and termination planning a vendor relationship requires, scaled to how critical it is. The clearest published statement of the lifecycle, and the one regulated buyers will hold you to.
      
      ---
      
      Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.
      
  • SKILL.md 3.9 KB
    ---
    name: procurement-and-sourcing
    description: Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists. Use this to run an RFP or vendor selection, negotiate a purchase, consolidate spend across a category, decide between single and multiple suppliers, or bring uncontrolled spending under management.
    ---
    
    # Procurement and sourcing
    
    This is everything before signature: deciding what to buy, from whom, and on what terms.
    `operations:vendor-management` takes over afterward — performance, renewals, exit.
    
    ## Specify the need, not the product
    
    Most bad purchases are decided before any supplier is contacted, when a requirement is written as a
    product someone already wanted. Specify the outcome and the constraints; let suppliers propose how.
    
    Separate genuine requirements from preferences, and be honest about which is which. A requirements
    list that only one supplier satisfies is a purchase order with extra steps, and everyone involved
    knows it.
    
    Involve the people who will live with the choice. Procurement that optimizes price against a
    specification the users did not agree to produces a cheap thing nobody uses.
    
    ## Competition is the leverage
    
    Price is set by the credible presence of an alternative, not by negotiating skill. The single most
    effective act in sourcing is having a real second option — and being willing to take it.
    
    Run a fair process: same information to every bidder, same questions answered for all, scoring
    agreed before responses arrive. Scoring invented afterward reliably rediscovers the preferred
    supplier.
    
    Where genuine competition is impossible — an incumbent with switching costs, a sole source —
    acknowledge it rather than staging a process. Then negotiate on the things still open: term length,
    renewal caps, service levels, exit assistance.
    
    ## Total cost, not price
    
    The quoted figure is a fraction of what you will spend. Model implementation, integration, training,
    the internal effort to run it, and what leaving costs.
    
    Watch for cost that arrives later by design: per-seat pricing that grows with headcount, usage
    pricing with no cap, renewal uplifts, and support tiers that turn out to be mandatory. Ask what this
    costs in year three, and get the answer in the contract.
    
    ## Category strategy
    
    Aggregate spend before negotiating it. The same category bought independently by four teams is four
    weak negotiating positions and usually four overlapping tools.
    
    Segment by leverage: high-spend commodity categories reward consolidation and hard negotiation;
    low-spend specialist ones are not worth the process cost. Concentrating everything on one supplier
    buys a discount and sells an exit — see `operations:business-continuity-and-resilience` before
    deciding that trade.
    
    Route the resulting terms through `legal-risk:contract-review`, and anything touching customer data
    through `legal-risk:privacy-and-data-protection` before signature rather than after.
    
    ## Sources
    
    `references/sources.md` in this skill lists the outside authorities that settle the questions
    here — what each one is authoritative for, and what you may do with it. Check them before
    answering on anything they cover, and cite what you used. Most are free to read and not free
    to reproduce; the use note on each is binding.
    
    ## Tooling
    
    Procure-to-pay: Coupa, SAP Ariba, Zip, Precoro, and similar. At smaller scale a request
    form plus the accounting system's purchase orders does the same work.
    
    Spend visibility: Ramp, Brex, Vertice, and similar, read against the ledger.
    
    Vendor risk lives in the GRC tooling, not here — but the intake form is where the security
    and privacy review has to be triggered, or it never happens.
    
    ## Never
    
    - Write a requirement that only the preferred supplier can meet.
    - Agree scoring criteria after responses arrive.
    - Negotiate on price without modeling year-three total cost.
    - Consolidate a critical category onto one supplier without pricing the exit.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related