Skip to content
cccskills
FreePublished on GitHub

ops-vendor-and-procurement

Use when the user names a vendor to evaluate, asks what renews soon, hands over a quote or statement of work, or wants to buy something and needs it approval-ready.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Run vendor and procurement ops

Use this when the user names a vendor to evaluate, asks what renews soon, hands over a quote or a statement of work (SOW), or wants to buy something.

What you need first

The spend source — a connected sheet, an accounting or card export, or a pasted CSV — the vendor list, the quotes or SOWs under review, and the name of the procurement approver.

No spend source means you build the inventory from their pasted list and mark spend UNKNOWN. One quote only means you score it and name the missing comparison.

Build the inventory first

One row per vendor: purpose in five words or fewer, owner, cadence, trailing spend, last charge, and renewal date. Dedupe on vendor name. A purpose or owner you cannot source stays Unknown, never guessed.

Segment each vendor by spend plus criticality — strategic, preferred, transactional, tail. Review effort follows the tier.

Evaluate new vendors three-wide

  • Total cost of ownership (TCO): price plus implementation plus run and maintenance plus downtime risk, minus residual value.
  • What switching costs.
  • The instrument flags.

Pick the instrument by purchase type: a request for information (RFI) to explore, a request for proposal (RFP) when solutions differ, a request for quote (RFQ) when the spec is fixed and only price moves.

Agree the weighted 1-5 criteria before quotes arrive — default 35 cost, 30 fit, 20 track record, 15 timeline — and let the composite total decide. Publish the criteria, batch every vendor question and answer to all vendors at once, negotiate only after scoring, and track delivery against the winning proposal. Never score on sticker price alone. Document why the winner won, in one line.

Run renewals inside the 90-day window

Current terms, usage against commitment, SLA hit rate, and the counter — a comparison table plus a draft note, draft-only. Check the term end and the notice period before you propose anything.

Draft SOWs and purchase orders from the facts

Scope, deliverables, term, price, and exit. Route every SOW to Legal and every purchase order (PO) to the procurement approver. Version each draft. You draft, they sign — never give legal advice.

Score vendors on a tiered cadence

Strategic vendors monthly or quarterly; the rest semi-annual or annual. Weigh each scorecard so trade-offs are explicit — default fit 30, cost 30, risk 20, delivery 20, summing to 100 — and compute a total per vendor.

Every score cites the SLA or contract clause it is measured against. A vendor with no written SLA gets flagged as a risk. Spend without outcomes gets flagged, never auto-renewed. With the approver's yes, share each strategic vendor's scorecard with the vendor and ask for their feedback on us as a buyer.

Rules

Never sign a contract, place an order, or send a vendor note without the approver's yes. Never invent a price, a term, or a renewal date.

Save the inventory as the sheet the team edits, with dated scorecards under vendors.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill