agentleFS
gokulsvisiongokulsvision/crewm8-cfo-skills/skills/strategic-advisory/cost-optimization/SKILL.md

cost-optimization

Skill2 starsChanged 7 months agoMITView on GitHub

Identify and execute cost optimization opportunities — vendor renegotiation, tool consolidation, process automation, efficiency improvements, and structural cost reduction for startup efficiency.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use observability, git-workflow and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run systematic cost optimization — not knee-jerk cutting, but disciplined, ongoing improvement of the company's cost structure.

    line 18
  2. Distinctive:

    Start with clean data from spend, subscriptions, and budget sources.

    line 65
  3. Distinctive:

    Pre-product-market-fit: don't optimize. Focus entirely on finding PMF.

    line 189
  4. Distinctive:

    Vendor dependency risk: if you're deeply integrated with a vendor, price negotiation leverage is limited.

    line 191

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cost Optimization

Run systematic cost optimization — not knee-jerk cutting, but disciplined, ongoing improvement of the company's cost structure. Renegotiate vendors, consolidate tools, automate processes, and find structural efficiencies. Goal: every dollar of spend is intentional and efficient.

Purpose

Cost optimization in startups is a constant tension: spend enough to grow, but not so much that you run out of runway. Most startups either ignore costs until a crisis (leading to panic cuts that damage the business) or slash indiscriminately (cutting growth investment along with waste). This skill provides a structured, phased approach to cost optimization — quick wins first, then structural improvements, with strategic restructuring only when necessary. The goal is to find the waste without cutting the growth.

When to Use

  • "Optimize our costs"
  • "Find savings in our OpEx"
  • "Renegotiate vendor contracts"
  • "Are we overspending anywhere?"
  • "Cost reduction sprint"
  • "Run a zero-based budget review"
  • "Find 10% to cut without hurting growth"

Inputs Required

  • Current spend data by vendor and category (from AP and subscription management)
  • SaaS subscription list with users, features, and cost
  • Vendor contracts and renewal dates
  • Cloud infrastructure spend (AWS, GCP, Azure)
  • Contractor roster with rates and hours
  • Headcount data (salary, benefits, tools per person)

Quick Reference

PhaseTimelineSavings PotentialRisk
Quick Wins1-4 weeks5-15% of OpExLow
Structural Improvements1-3 months15-30% of targeted areasMedium
Strategic RestructuringCrisis only20-30%+ of total burnSevere
Cost Category% of Total SpendTypical Savings
Headcount (salaries + benefits)65-85%10-30% (crisis), 0-5% (ongoing)
SaaS / Software5-15%15-30%
Cloud Infrastructure3-10%20-40%
Professional Services2-8%20-50%
Marketing / Ads2-10%20-50% with smarter spend
Office / Rent2-8%20-40%
Travel & Entertainment1-3%50-80%

Procedure

Phase 1: Diagnostic (Understand the Baseline)

Start with clean data from spend, subscriptions, and budget sources.

Break down every cost into types and assess optimization difficulty.

Phase 2: Quick Wins (1-4 weeks)

These can be done immediately with minimal business disruption:

ActionEstimated SavingsTime to ImplementRisk
Cancel unused SaaS subscriptions (< 1 active user)$500-5,000/mo1-2 weeksLow (verify no dependencies)
Downgrade over-provisioned SaaS plans (seats, tiers)$200-2,000/mo1-2 weeksLow
Switch SaaS subs to annual billing (save 15-20%)$1,000-10,000/yr2-4 weeksLow (cash flow timing)
Renegotiate top 5 vendors (ask for 10-20% off)10-20% of vendor spend2-4 weeksLow-Medium
Cut unused or low-ROI marketing channels$1,000-10,000/mo1-2 weeksLow-Medium (verify attribution)
Audit and right-size cloud resources (idle instances, old snapshots)20-40% of cloud spend2-4 weeksMedium (engineering time)
Cut travel budget, move to virtual events50-80% of travel spendImmediateLow
Audit contractor roster (still needed? full-time cheaper?)10-30% of contractor spend2-4 weeksMedium

Phase 3: Structural Improvements (1-3 months)

Deeper changes that improve efficiency long-term:

ActionWhat It MeansSavingsEffort
Tool consolidation2-3 tools that do similar things → pick 120-50% of those tool costsMedium (migration)
Negotiate multi-year contracts2-3 year lock with 20-30% discount20-30% of vendor spendMedium (commitment)
Insource vs outsourceBuild internal capability vs rely on agencies/contractorsCase-by-caseHigh
Process automationAutomate manual finance/ops workflowsTime savings (1-2 FTE)Medium-High
Vendor RFP / competitive biddingBid out your top 3 vendor categories10-25% of those categoriesMedium
Office rationalizationSublease unused space, renegotiate lease20-50% of office costsMedium

Phase 4: Strategic Restructuring (Only in Crisis)

These hurt but save large amounts:

ActionSavingsImpact
Hiring freeze~5-10% of annual burn (headcount stays flat)Slows growth
Layoffs (10-20% of team)10-25% of total burnSevere — culture, morale, momentum
Salary cuts10-20% of payroll for cuts appliedHigh flight risk for top performers
Kill a product / feature area10-30% of associated team costStrategic — refocuses the company
Pivot business modelHard to quantify upfrontExistential — but sometimes necessary

Vendor Negotiation Playbook

The Framework

1. Know your leverage:
   - How much do you spend? (total, growth rate)
   - How hard would it be to switch?
   - Are you a logo they want? (brand value)
   - Is it renewal time? (max leverage is 30-60 days before renewal)

2. Always ask for:
   - Better pricing (10-20% off is standard ask)
   - Better terms (net-30 → net-45, annual billing discount)
   - Added value if they won't move on price (more seats, premium features, training)

3. The conversation:
   "Hi [vendor], we're doing our quarterly vendor review. We value the
    product, but we're under pressure to optimize our cost structure.
    Can we discuss adjusting our plan? We're at $X/mo — would $Y/mo
    work with an annual commitment?"

4. If they say no:
   "Understood. We may need to evaluate alternatives during our next
    budget cycle. Is there anything else you can offer — maybe
    additional seats or premium features at our current price?"

5. Always get it in writing: email confirmation or contract amendment.

Top Vendor by Category — Negotiation Targets

Vendor CategoryTypical Discount AchievableLeverage Point
SaaS tools (< $5k/yr)10-20%"We're consolidating vendors"
SaaS tools ($5k-50k/yr)15-30%Annual commitment, competitive alternatives
SaaS tools (> $50k/yr)20-40%Multi-year, logo value, formal RFP
Cloud (AWS/GCP/Azure)5-15% (committed use)Reserved instances, committed spend discounts
Professional services (legal, accounting)10-30%Fixed fee vs hourly, scope bundling
Recruiting agencies15 → 10% feeVolume commitment
Insurance brokers10-20%Annual re-quote, bundle policies

Output Format

  • Spend diagnostic (spend by category, vendor, department)
  • Quick-win list with estimated savings and timeline
  • Vendor negotiation queue (ranked, with talking points)
  • Structural improvement roadmap
  • Savings tracker (projected vs actual)
  • Recommendation for CEO: what to do, what NOT to cut

Done Criteria

The skill is complete when:

  1. A full spend diagnostic is completed (spend by category, vendor, and department, with % of total).
  2. Quick wins are identified with estimated savings and implementation timeline.
  3. Top 5-10 vendors are ranked for negotiation with talking points and target discounts.
  4. Structural improvement opportunities are identified with effort vs impact ranking.
  5. A clear CEO recommendation is provided on what to cut and what NOT to cut.
  6. Savings tracker is set up to measure projected vs actual savings.

Pitfalls

  • Cutting growth to save costs — the #1 startup cost optimization error. Cutting S&M that works, reducing engineering capacity on a growing product, or trimming customer support when NPS is fragile destroys future revenue to save today's dollars.
  • Optimizing costs before you have clean data — without a full spend diagnostic, you don't know where the money is going. Optimizing blind means you might cut the wrong things and miss the real savings.
  • One-time cost-cutting sprees without ongoing discipline — the company cuts 20% in a crisis, then creeps back to the old spend level within 6 months. Cost optimization is a muscle, not a one-time event. Build the review cadence.
  • Killing the wrong SaaS tool — canceling a $200/mo tool that three engineers depend on saves $2,400/yr but costs $50,000 in lost productivity. Before canceling anything, verify usage AND impact.
  • Negotiating from weakness — starting vendor negotiations when you're desperate (e.g., "we need 30% off or we'll default") is the worst position. Always negotiate from a position of data and options, not desperation.

Heuristics

  • Don't cut growth to save costs: the #1 startup cost optimization error. Cutting S&M that works is self-defeating.
  • SaaS sprawl is the easiest win: most startups have $5-20k/yr in unused/underused SaaS. A quarterly audit is worth it.
  • Renegotiate annually: vendors expect it. If you haven't asked for a discount in 12 months, you're overpaying.
  • Cloud costs are the sneaky budget-killer: they grow with usage and nobody watches them until the bill is shocking. Weekly monitoring.
  • Fixed fee > hourly: for legal, accounting, and consulting — push for fixed-fee arrangements. Hourly billing incentivizes the wrong behavior.

Edge Cases

  • Hypergrowth mode: optimizing costs aggressively can slow growth. Be selective — cut waste, not investment.
  • Pre-product-market-fit: don't optimize. Focus entirely on finding PMF. Cost optimization is for when the model is working.
  • Burning cash with strong unit economics: it's okay to spend if LTV/CAC > 3x and payback < 12 months. The constraint is cash, not P&L.
  • Vendor dependency risk: if you're deeply integrated with a vendor, price negotiation leverage is limited. Focus on multi-year price locks instead.

Verification

Can you answer "Where is every dollar of OpEx going and which 20% of that spend is waste?" and "What are the top 3 things we should NOT cut?" and "Did we actually save what we projected from last quarter's optimization efforts?" If not, cost optimization is incomplete.

Example

User: "Find 10% savings in our OpEx without hurting growth." Expected behavior: You run a full spend diagnostic (categorize every vendor, identify unused subscriptions, benchmark cloud costs), identify quick wins (cancel 3 unused tools saving $2k/mo, downgrade over-provisioned plans saving $1.5k/mo, negotiate annual billing on 5 vendors saving $8k/yr), recommend structural improvements (consolidate 3 analytics tools into 1 saving $3k/mo, migrate dev instances to reserved instances saving $1k/mo), and clearly flag what NOT to cut (S&M spend driving 4x ROAS, customer success headcount).

User: "We need to cut $100k/mo from our burn. It's a crisis situation." Expected behavior: You quickly assess the full cost structure, identify that headcount is 75% of total spend, present a tiered menu of options with human impact (Level 1: hiring freeze saves $15k/mo, Level 2: contractor cuts + marketing hold saves $30k/mo, Level 3: 15% workforce reduction saves $70k/mo), recommend the combination needed to reach $100k/mo, provide a severance and communication plan for the difficult choices, and flag that at $100k/mo savings, runway extends from 9 to 15 months creating a path to the next fundraise.

Linked Skills

  • Budget context → budget-creation-management
  • Profitability to know what's worth keeping → profitability-analysis
  • ROI case for bigger changes → business-case-modeling

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.