--- title: what a business already gets from ecosystem services canonical_url: https://ensurance.app/guide/what-a-business-already-gets-from-ecosystem-services markdown_url: https://ensurance.app/guide/what-a-business-already-gets-from-ecosystem-services.md subtitle: the supplier you already use and do not have a contract with category: ecosystem-services --- # what a business already gets from ecosystem services *the supplier you already use and do not have a contract with* Your plant has a supplier with no vendor number. It has never sent an invoice, never missed a delivery you logged, and never come up in a procurement review. It is the river above your intake. It changes the load the skid has to treat. Coagulation and filtration still happen at the plant. There is a line in your operating budget that moves when that river does. Most plants have never traced it. By the end of this post you will know which line, and who at the company already feels it move. ## the supplier you never contracted Take one operation and stay with it. A food plant on a river. Process water comes in through an intake, passes screens, coagulant, filters, and disinfection, and goes to the line. The plant manager owns the skid. Maintenance owns the filters. Procurement owns the chemical contract. Everyone owns a piece of the water after it arrives. Nobody at the company owns the water before it arrives. The land that drains to the intake does that part. Cover on the slopes holds soil in place when it rains. A channel with a stable bank keeps its soil out of the intake. A floodplain that still floods slows a storm pulse before it reaches you. None of that is on an org chart. The skid was sized for the river the designers expected, which is not a promise the river still matches that day. That work is an **ecosystem service**: a function a living system performs that the operation already counts on, and would have to buy, build, or stop without. The skid was sized for the river in the condition the designers saw. The river keeps that condition or it does not. The plant has received the output of that work every shift since startup, and the only time it shows up on paper is when it stops. ## what an ecosystem service is, for a business The textbook version sorts what living systems do into categories. The paired post in the other series does that in plain words — four kinds of work the land does for you, and the one decision each can change. Read [what ecosystem services actually do for you](/guide/what-ecosystem-services-actually-do-for-you?from=guide) when you want the sort. A finer list of nineteen flows lives on this site too, at [the 19 ecosystem services](/guide/19-ecosystem-services-natural-capital-flows?from=guide). You do not need either to pass the test below. For a business, the useful version is narrower. **Ecosystem services for businesses** are the living functions an operation already uses, named by the job they do inside that operation. Not "clean water" in general. Water the plant can treat with the chemistry and filter run it budgeted. Not "flood regulation." A storm that arrives at the intake slow enough for the skid to keep up. That narrowing is the whole move. A category is something a consultant can describe. A function is something a plant manager can lose. ## the trap: something standing in for the function Three things get mistaken for the function, and each one is honest work that still leaves the river where it was. A **nature program** is a department with a budget and a slide. It can run for years without anyone asking what the plant would do if the river above the intake stopped holding its soil. A **disclosure chapter** can name the dependency in a sentence. Reporting frameworks increasingly ask for that sentence, and it is worth writing. It is not the function. A named dependency and a managed one are different lines in different budgets. A **partnership logo** says the company is present in the watershed. Presence is not the same as the slope above the intake keeping its cover through the next storm. You may be thinking: that is what the treatment plant is for. Fair. Treatment handles the variance the design assumed. The river decides how often you leave that range. When the land above the intake changes — a cleared slope, a burn scar, a channel cutting a new bank — the plant does not get a new design. It gets a new river. The skid did not fail. The supplier changed the spec and nobody at the company was the account owner. You may also be thinking: this belongs to sustainability, not operations. It belongs where it fails. Sustainability can write the chapter. The plant manager approves the overtime. ## the test: three names Run this on the one operation you picked. It takes a meeting, not a study. | name | at this plant | |---|---| | the function | Water the plant can treat with the chemistry and filter run it budgeted | | what stops if it fails | Doses climb, filter runs shorten, a line idles while the skid catches up, a batch goes on hold | | who already feels it | The plant manager who signs the overtime, the maintenance lead who logs the changeouts, the buyer who reorders coagulant off cycle, the finance lead who sees consumables over budget and calls it weather | If you can fill all three rows, you have a dependency your books can carry. If you can fill only the first, you have a sentence for the sustainability report. Both are fine. Only one of them changes what the plant does next quarter. Two things to notice about the third row. First, the people are already on payroll. Nobody has to be hired to feel the river. Second, none of them has ever met in a room to talk about the river. Each of them has a separate name for the same event. ## why your books cannot see it The function enters the books only as variance. It has no cost center because it never sent an invoice. When it holds, its number is zero, which looks exactly like a function that does not exist. When it fails, the cost lands in three or four other lines under other names: chemicals, maintenance, downtime, overtime. Nobody adds them up because nobody was asked to. :::johnson **you already use it. the question is whether your books can see it.** — The river above the intake works whether or not anyone at the company has a line for it. Finance can name the function, or keep paying the failure under four other names. [the next jab: an avoided cost is the benefit you can book →](/guide/an-avoided-cost-is-the-benefit-you-can-book?from=guide) ::: There is an accounting for the failure that did not happen. It has rules, and the first rule is that if you cannot name the invoice you did not get, you do not have it yet. That is the next post in this series. For now, the job is only to name the function. ## what the business gets by naming it Three things, none of which require a new department. Operations and finance agree on one sentence about what the plant depends on. That is rare. Most companies have a sustainability sentence and an operations sentence, and they do not match. A budget line stops being weather. The consumables variance gets a cause you can point to on a map: the land that drains to the intake, in the condition it is in this year. A cause on a map is something a plant can watch. Weather is not. When someone proposes spending upstream — a watershed group, a utility that shares the river, a landowner above you — the plant can judge it against a job it already has. Does this keep water the skid can treat arriving at the intake? That is a yes-or-no question for operations. Without the named function, the same proposal reads as a donation request, and goes to a different desk with a smaller budget. The river above the intake exists whether or not the company has a nature program. A solution is the fit between that living system and the job you already have. [Ensurance](https://ensurance.app/?from=guide) funds the living system. It is not the org chart, and it is not a new department. The plant is the program. The river is the supplier. The question this post leaves you with is which line moves when it does. ## frequently asked questions ### what are ecosystem services for businesses? Ecosystem services for businesses are the functions a living system performs that an operation already depends on: water a plant can treat, a slope that stays put above a site, a season a crop or a visit still follows. The business test is whether you can name the function, what stops when it fails, and who at the company already feels that stop. ### is naming the dependency in a disclosure the same as managing it? No. A disclosure names the dependency in a sentence. Managing it means someone in operations owns the function and the budget line that moves when it fails. Both are useful. They are different jobs held by different people. ### our water comes from the city, not a river. does this still apply? Yes, one step removed. The utility owns the intake and inherits the condition of the land above it. Your plant inherits the utility's water, and its rate case, and its boil notices. The function is the same; the account owner is a public utility instead of your plant manager. The third post in this series is written for that utility. ### do we need a nature program to run the three-name test? No. The test takes one meeting with the plant manager, the maintenance lead, and whoever owns the consumables budget. The output is three names, not a strategy document. ### what does the plant get if the river holds? The same thing it got last year: water the skid was designed for, at the dose and filter run it budgeted. That is why nobody notices. The value of the function is the quarter that was boring. ## next The next jab in this series is [an avoided cost is the benefit you can book](/guide/an-avoided-cost-is-the-benefit-you-can-book?from=guide) — the rule for turning a failure that did not happen into something finance can carry. The paired post in the services series is [what ecosystem services actually do for you](/guide/what-ecosystem-services-actually-do-for-you?from=guide) — the four kinds of work the land does, and the one decision each can change. ## the series 1. [what a business already gets from ecosystem services](/guide/what-a-business-already-gets-from-ecosystem-services?from=guide) 2. [an avoided cost is the benefit you can book](/guide/an-avoided-cost-is-the-benefit-you-can-book?from=guide) 3. [what source water protection already does for a utility](/guide/what-source-water-protection-already-does-for-a-utility?from=guide) 4. [what natural capital solutions are for](/guide/what-natural-capital-solutions-are-for?from=guide) ## the other series 1. [what ecosystem services actually do for you](/guide/what-ecosystem-services-actually-do-for-you?from=guide) 2. [an ecosystem service benefit is a bill you don't get](/guide/an-ecosystem-service-benefit-is-a-bill-you-dont-get?from=guide) 3. [which ecological restoration job to do first](/guide/which-ecological-restoration-job-to-do-first?from=guide) 4. [when ecosystem services consulting pays for itself](/guide/when-ecosystem-services-consulting-pays-for-itself?from=guide)