Calling a climate-tech service SaaS can make a high gross margin seem natural. Yet a livestock-methane platform may provide sensors, gateways, installation, connectivity, field support, data review, and verification readiness together. Even if the interface is software, the cost of visiting farms and replacing equipment to deliver the promised outcome is part of the business’s core structure.

Conversely, hardware does not make a low gross margin inevitable. Equipment standardization, remote diagnostics, partner services, automated quality checks, and carefully defined contract scope can reduce recurring costs. The key is not whether the company is called SaaS or an equipment provider, but identifying precisely which resources are repeatedly consumed to deliver1 won of revenueaccurately.

Misconception to correct first: gross margin is not cash balance or operating margin

Gross profit is generally revenue minus cost of revenue, and gross margin is that amount divided by revenue. Sales and marketing, product R&D, and headquarters overhead may generally be treated as operating expenses, so a high gross margin does not mean the company as a whole is profitable. Conversely, if an initial standardization investment is booked as R&D, the contract’s actual cash burden and accounting gross profit may look different.

Which costs belong in cost of revenue depends on accounting policy and contract form. IFRS IAS 2 explains the principle that inventory cost includes purchase costs, conversion costs, and other costs incurred in bringing inventory to its present location and condition. IFRS 15 has separate requirements for recognizing costs to obtain or fulfill a contract. The distinctions below describe a management-accounting structure; actual financial-statement classification must be determined with an accounting professional under the applicable standards.

Another trap is recording installation fees as large one-time revenue while omitting later support costs from subscription costs. Gross profit may look good at the point of sale, but equipment failures, calibration, and data review can accumulate and reduce cash as customer count grows. View fulfillment costs over the full period for each contract cohort.

Cost structure 1: equipment and replacement cycles

The first category includes sensors, sampling pumps, filters, tubing, gateways, power supplies, enclosures, and spare parts. Include not only purchase price but also shipping, duties, inspection, defects, warranty replacements, and useful life. Revenue recognition and cash-collection timing also differ depending on whether sensors are sold, leased, or included in a subscription.

Equipment cost cannot be calculated from the initial BOM alone. Record, by cohort, actual replacement cycles for filters and pumps in humid, dusty, ammonia-rich barns; sensor drift; cable damage; inventory shortages; and obsolescence risk. If pricing assumes a 1% failure rate but the actual annual replacement rate is 8%, warranty costs can rise faster than software growth.

Cost structure 2: installation and field onboarding

The second category includes pre-site surveys, deployment design, wiring, power and connectivity work, installation labor, travel, training, and initial stabilization. Even with the same sensor count, costs differ between open barns and mechanically ventilated barns and between farms with prepared power and connectivity and those without. One standard price for every site makes easier farms subsidize harder ones.

Manage installation cost through qualification diagnostics. Score barn type, distance, power, connectivity, work at height, explosion-protection and safety requirements, and customer readiness, then set price tiers. Measuring first-install success, engineer hours, repeat visits, and days to commercial operation reveals the effect of standardization.

Cost structure 3: connectivity, cloud, and software operations

The third category includes SIMs and lines, message ingestion, storage, backups, data transfer, compute, logs, monitoring, external APIs, and software licenses. Collection costs rise with sensor count and sampling frequency, while storage costs accumulate with longer raw-data retention and multi-region replication. Logs, time-series queries, and customer exports may cost more than model inference.

Separate unit costs per farm, sensor, GB, and API call, and design retention policies for normal and anomalous periods. Do not arbitrarily delete raw data needed for verification to reduce cost; that damages product value. Define retention tiers, customer contracts, and legal requirements first, then apply compression, aggregation, and cold storage.

Cost structure 4: customer support and field maintenance

The fourth category includes inquiry handling, remote diagnostics, firmware updates, calibration schedules, consumables shipping, emergency dispatches, and customer retraining. Unlike ordinary software support tickets, farm-equipment problems are affected by distance, weather, and access windows. Even as revenue grows, low regional density can make travel costs and response time grow faster.

Support cost is hidden when viewed only as a customer average. Track ticket volume, resolution time, and field-dispatch rate by farm type, device generation, installation partner, region, and contract tier. Instead of making 24-hour response a default for every customer, distinguish service levels for safety functions and carbon-reporting support and reflect them in pricing.

Cost structure 5: data quality, measurement, reporting, and verification (MRV), and verification readiness

The fifth category includes reviewing calibration records, classifying missing data and outliers, reconciling activity data, updating baselines, rerunning calculations, analyzing uncertainty, preparing reports, and responding to third-party questions. Even with an automated dashboard, monthly manual handling of farm-specific exceptions is recurring service cost.

If “verifiable” is part of the product promise, define the required evidence and response scope. Decide whether the company or customer contracts and pays the external verifier, and who bears re-verification and data-completion costs. Data operations needed to satisfy the boundaries, baselines, and monitoring required by GHG Protocol project accounting must also be included in pricing.

Cost structure 6: allocation to partners, channels, and data providers

The sixth category includes reseller discounts, sales commissions, installation-partner costs, data, mapping and weather API fees, licenses, and performance sharing. Partner channels can reduce internal sales costs, but continuously share a percentage of revenue and create training and quality-audit costs. Consider allocation and support responsibilities at renewal, not only in the first contract year.

Distinguish the accounting question of recording revenue gross or net from management contribution margin. Regardless of presentation, payments to partners and headquarters support costs belong in contract economics. Include the risks of a free data API becoming paid and of exchange-rate changes in sensitivity analysis.

Calculating gross margin with a hypothetical contract

This is a general calculation example, not a specific company’s performance. The gross margin here is a management metric and may differ from capitalization of contract-acquisition or fulfillment costs under IFRS 15 or from financial-statement presentation. Assume one farm generates KRW 40 million in annual revenue: KRW 9 million for equipment and warranty, 5 million for installation and onboarding, 2.4 million for connectivity and cloud, 3.6 million for support and maintenance, 4 million for MRV and verification readiness, and 3 million for partners and licenses. Total direct cost is KRW 27 million, gross profit is KRW 13 million, and management gross margin is 32.5%.

If equipment and installation costs fall sharply the following year and renewal revenue is KRW 24 million with recurring costs of KRW 9 million, renewal gross margin could be 62.5%. But concentrated sensor replacements and field dispatches can reverse the result. Separate new-installation and renewal cohorts, hardware and services, and direct sales and partners.

Improving gross margin is not only about passing costs on. Screen out unsuitable farms in advance, reduce the installation BOM, prevent dispatches through remote diagnostics, incorporate causes of manual review into the product, and tier prices by service level. But margin created by cutting data-quality checks or safety procedures may hide future failure, verification, and customer-churn costs.

Operating standards

Record benchmark unit prices and assumptions for the six costs at the contract-quotation stage. After installation, review variance against the estimate and feed it into the next quote. Record engineer and analyst time with work codes rather than treating it as free, and distinguish product development from customer-specific fulfillment.

The dashboard should show gross margin together with equipment replacement rate, installation time, field-dispatch rate, cloud cost per farm, manual review time, partner allocation rate, 12-month renewal rate, and cash-collection period. To judge scalability, identify which unit costs decline as customers grow and which remain linear.

Execution checklist

  • Have gross margin, operating margin, and cash flow been distinguished?

  • Does equipment pricing include defects, warranty replacement, consumables, inventory, and obsolescence risk?

  • Are installation difficulty and travel/revisit costs reflected by farm type?

  • Are connectivity and cloud costs tracked per sensor, farm, GB, and API?

  • Are customer support and field dispatch viewed by contract tier and cohort?

  • Are manual data review and verification response hours included in direct cost?

  • Are training, audits, and remediation of mis-selling costs calculated in addition to partner commissions?

  • Are gross margins separated for new installation and renewal, and direct sales and channels?

  • Before raising prices, have the causes of unsuitable customers and recurring exceptions been reduced?

  • Is actual accounting classification finalized with a professional under the applicable standards and contract?

Conclusion: Gross margin is an operating metric showing product repeatability

Climate-tech service gross margin is not explained by a single cloud bill. Equipment and replacements, installation, software operations, customer support, MRV and verification, and partner allocation recur when fulfilling customer contracts. Omitting these six costs can make the income statement look better as the business grows while cash flow worsens.

Good gross-margin management is not cutting quality. It means finding recurring field exceptions, standardizing products and procedures, and pricing to the service level customers require. As actual costs accumulate by farm and contract cohort, gross margin becomes operating data showing product scalability, not merely an investor ratio.

Sources