Models Operations model

Spend and tools

Battle tested

Who may spend what, how it is approved, how to find tool waste, and what to get right in Germany.

57% of facts from primary sources, 12 of 2121 verified facts, last checked 29 Oct 2026Primary source: primary sourceSecondary: secondary sourceEstimate: estimate

Who approves what, and how

Six questions. The rust line is your path. Each faint branch is where the other answer leads. Turn the dial to your stage; slide or type your headcount.

  1. Can the tool record or analyse employee behaviour or performance, for example usage logs, activity analytics, AI assistants with logging or time tracking?

    • Yes: More questions
  2. Does the vendor process personal data of staff or customers?

    • No: More questions
  3. Is a data processing agreement signed and the vendor reviewed for security?

    • No: Block until the checks are done
  4. Is the cost below your auto-approve limit?

    • Yes: More questions
  5. Is it a commitment of more than 12 months, or above the CEO’s delegated limit?

    • Yes: CEO and finance approve
Your outcomePractice: practice

Budget owner approves

Within one working day, with finance checking VAT and coding. Add the renewal date to the tool register.

Stage

How it runs

Four flows. Each step has an owner, a time cost and a document.

  1. Check the register and ask

    See whether an approved tool already does the job. If not, submit what, why, cost, term and data touched.

    RequesterDay 0, 10 minutes (estimate)Purchase request

  2. Budget owner decides

    Approve or decline within one working day.

    Budget owner5 minutesApproval record

  3. Privacy, security and works council gate

    Only if the tool touches personal data or can monitor staff. In Germany, HR joins.

    Ops or IT lead, HR in Germany30 to 60 minutes per new tool (estimate)Vendor review checklist, DPA on file

  4. Pay by virtual card

    Merchant-locked, with a limit equal to the contract.

    FinanceSame day, 5 minutesCard issue record

  5. Receipt, coding, register

    Capture the invoice, mark reverse-charge vendors, code to the cost centre, and add owner, seats and renewal date to the register.

    Requester, then finance and opsWithin 7 days, 10 minutesReceipt and coding, tool register entry

Practice: practice

Rules by country

General information, last checked 29 Oct 2026. Not legal or tax advice.

Who handles what

Set by the dial on the instrument. It follows your headcount until you turn it.

Runs it
CEO, with the first ops hire as backup. A Chief of Staff or ops lead can own the finance rhythm and spend.
You keep
New recurring tools and the limit.
Hand off
Receipts, coding, the tool register.

My stance

Company tools on one central card, so changes are managed in one place. Virtual cards for the rest.

Efficiency savers

What each step saves. Where nobody publishes the number, it says so.

  • Reclaim unused licences

    Vendor data, and it disagrees. Zylo: 54% of licences used, 46% unused or underused. Productiv: 53% unused in 2023. Gartner via Torii: up to 30%. Your estimate is seats x unused share x price. For example, 40 seats at EUR 30 a month with 25% unused saves EUR 3,600 a year.

    Zylo 2026 SaaS Management Index (vendor data): primary source (opens in a new tab)
  • Virtual card per vendor, with a limit

    No independent data. Vendor case studies only.

    Practice: practice
  • Auto-approve below a data-derived limit

    No published data. Removes most routine approvals from the founder’s week.

    Estimate, no published data: estimate
  • Renewal calendar, 90 days ahead

    No published saving. Prices rise: Vertice reports 12.7% average SaaS inflation in August 2026 and 14.3% preliminary for September. Vendor data.

    Vertice SaaS inflation index (vendor data): primary source (opens in a new tab)
  • Offboard through single sign-on

    No published data.

    Practice: practice
  • Consolidate overlapping tools

    No data on how much overlap there is. Zylo reports a median portfolio of 240 apps and an average of 305. Vendor data.

    Zylo 2026 report page (vendor data): primary source (opens in a new tab)

How spend control goes wrong

Failure modes

  • Control costs more than the spend

    Approval for every EUR 20. Set a limit from your own data.

  • Shadow tools

    Productiv’s 2023 vendor data put shadow apps at about 51% of the portfolio. Use single sign-on and card discovery, then an amnesty and a register.

  • Tool live before the works council

    A tool that can log staff goes live without the §87(1) Nr. 6 BetrVG step. Make it a gate.

  • Reverse charge missed

    Foreign SaaS booked with the wrong VAT treatment. Flag the vendor at coding and have a Steuerberater review it.

The biases behind them

  • Sunk cost

    You renew a tool because of the time spent rolling it out. Ask: would I buy this today at this price?

  • Planning fallacy

    Adoption and return are overestimated. Pilot with a small group and a usage target.

  • Parkinson’s law

    The budget gets spent because it exists. No use-it-or-lose-it.

  • Status quo bias

    Auto-renewal becomes the default. Review each renewal 90 days ahead and ask for a competing quote.

Where the evidence disagrees

How big is SaaS waste

All vendor data. These companies sell optimisation tools, use different definitions, and none is independent. Treat 30 to 53% as a range.

Tight control or speed

Control

ACFE estimates organisations lose about 5% of revenue to fraud.

ACFE 2024, via Ohio CPA: secondary source (opens in a new tab)

Speed

Approval for small items costs more than the spend. This is practice, not data.

Practice: practice

No benchmark exists for approval thresholds by stage. One vendor template uses USD 5,000 for manager approval alone, and that is one example, not a norm.

Disagree with a stance, or have data that should be here?

Email me