How do your features impact your margin?

Every finance team reports margin, they go to the board each month with a paragraph explaining why it moved, that paragraph is written at the level the data allows, which for most businesses is the total.

For a long time the total was enough, the cost of serving a customer moved slowly and the price they paid barely moved at all. Both sides now move at the level of the individual feature, a single generative capability can change what a plan costs to deliver inside a quarter, and pricing that charges for usage means revenue rises and falls with the same activity that drives the cost. A blended technology margin averages all of that into one figure, so the movement that matters most is the movement it shows least.

Which is why the commentary under a falling technology margin so often says the business grew. Growth is the explanation available, because nothing in the numbers separates a technology margin that fell because volume rose from one that fell because something became less efficient to run, both arrive as the same line in the same month, and only one of them corrects itself.

The problem isn't diligence, the three things needed to tell them apart live in three systems with three owners. Revenue sits in billing, counted per customer and per plan, cost sits in cloud and vendor invoices, counted per account and per service, usage sits in product telemetry, held by engineering and counted per event and per feature. Each is accurate on its own terms, none shares a key with the others, so the only place they reliably meet is the company total.

Technology margin explained in aggregate is commentary, margin explained by feature is evidence.

Feature-level technology margin is the revenue a feature earns less the cost it incurs, measured over the same customers and the same period. Both halves have to arrive together, cost per feature on its own is a cost unit economic, which measures efficiency and leaves open whether the feature pays, revenue per customer on its own describes the plan and leaves open which part of it earned the money, technology margin only becomes explicable where the two land on the same feature.

Product will object here, and the objection is right as far as it goes: usage is not value. Login and search dominate any measure of activity, while the quarterly export that justifies the renewal is used twice a year, so weighting revenue by usage alone makes the feature that wins the deal look like the one to cut. The answer is to treat usage as a baseline, the features every customer uses regardless of plan come out of the analysis, revenue attaches directly wherever pricing already says what a feature is worth, an add-on, a tier gate, a metered charge, a usage overage, and what remains is weighted by how customers actually use the product. Usage only undervalues the rare, valuable feature where nobody has said what that feature is expected to earn, once the business states the technology margin it expects, a measured result well below it is a question worth asking, visible on the page where before it was invisible.

OPTIMAZE attributes technology cost to the products and features that cause it, brings revenue in from the billing and finance systems the business already runs, and joins both to usage on the same features over the same period. Revenue lands on features by usage, refined by pricing data where it exists, and each result sits against the technology margin the business expects for that feature, OPTIMAZE supplies the measured figure, the judgement about what a feature should earn stays with the business that set the price.

The features that need their own technology margin are the ones where a different answer would change a decision, past that point precision costs more to produce than it returns, which is the argument made in Can there really be too much of a good thing?.

What changes first is the conversation. Finance holds revenue and a cost total, product holds usage and a roadmap, each brings half a picture to the pricing meeting and argues from it. With revenue, cost and technology margin on the same features, the commentary under the board pack says which features carried technology margin and which consumed it, finance can defend the number line by line, and product can see whether the feature it is about to invest in has ever paid for itself.

Technology Capital Performance asks whether technology spend is producing a proportionate, attributable return, and for most businesses the honest answer still stops at the company total. Taking revenue and cost to the feature is what lets that answer go further, from a technology margin the business can describe to one it can explain.

If this sounds like something you or your business needs, get in contact with our sales team.