All essays

Paul's Thoughts

What Makes a Profit Earned?

I want my business to make a profit. I want it to pay people well, buy good equipment, survive a difficult stretch, and have enough room to do work properly. There is no virtue in building a business that can remain solvent only by exhausting everyone involved.

But “it makes money” is an incomplete defense of a business practice.

A profit figure tells us something about the financial result. It does not, by itself, tell us whether the company solved an important problem, accepted a worthwhile risk, found a more efficient way to deliver value, or simply acquired enough control over a customer’s circumstances to demand more money.

Those possibilities deserve different judgments. Defending capitalism should leave us able to make them.

When I call a profit earned, I mean that there is a defensible relationship between the reward and the value contributed: useful work, knowledge, organization, capital, risk, responsibility, and continuing service. I also mean that the exchange respects the people involved and the commitments made to them. That is an ethical position. An accounting identity cannot prove it, and an economics paper cannot choose it on our behalf.

Economics can, however, help explain why the way a business earns money matters.

Start with an ordinary engineering example. A specialist identifies a fault that has been interrupting production and corrects it in an afternoon. The customer may receive value far beyond the hours spent on that particular visit. The specialist’s ability reflects prior learning, tools, preparation, and the judgment to recognize the problem. A substantial fee can be entirely reasonable if the scope and terms are understood.

There is no reason to demand that expertise become cheaper as it becomes more effective. Nor should a business be penalized for solving a problem efficiently. Rewarding only visible effort would give us a peculiar incentive to make everything take longer.

Innovation presents another legitimate claim on profit. Someone must commit resources before knowing whether a new product will work or whether customers will want it. The successful project may have to support unsuccessful experiments as well as the effort required to maintain the result. Judging its return only against the cost of producing the next copy ignores much of the decision that made the product possible.

Kenneth Arrow’s work on invention examines why uncertainty and the difficulty of capturing the benefits of knowledge complicate investment in research. It also recognizes the tension between encouraging the production of knowledge and making existing knowledge widely useful. [1] That tension deserves more thought than either “all information should be free” or “whatever protects the owner’s revenue must be justified.”

I can defend a company’s right to charge for useful intellectual work and still ask whether a particular restriction serves a reasonable purpose. The need to finance innovation establishes a problem to solve. It does not automatically validate every mechanism someone proposes for collecting revenue.

The distinction becomes clearer when we consider customer dependence.

Imagine a customer who purchases a piece of industrial equipment and builds a production process around it. Training, integration, validation, and operational experience accumulate over time. Changing suppliers now requires more than comparing two purchase prices. Even a better alternative may be unattractive if the transition is disruptive enough.

Paul Klemperer’s research on switching costs explains how those costs can give suppliers market power over existing customers, while also creating incentives to compete for customers earlier in the relationship. His discussion includes several sources of switching costs, including compatibility, transactions, and learning. [2] The mechanism is more complicated than a simple claim that every long supplier relationship is abusive.

Some dependence is a consequence of useful specialization. Training takes effort. Qualification takes effort. A supplier who has spent years understanding an application may be expensive to replace because that understanding is valuable. I would expect a capable supplier to benefit from doing good work over time.

My objection is to deliberately increasing a customer’s difficulty of leaving when that difficulty contributes little to the product’s purpose. Withholding an agreed deliverable, obstructing the use of customer data, or introducing an unnecessary incompatibility can make an existing relationship more profitable without making the customer’s system better.

The resulting revenue may be legally collectible in some circumstances. That would not settle whether I regard the practice as defensible. Legal permissibility and professional integrity ask different questions.

Subscriptions are a useful example because the billing interval alone tells us very little. Continuous hosting, maintained infrastructure, timely updates, support, and access to ongoing development can justify recurring payment. A customer may also reasonably prefer a subscription that spreads costs instead of an upfront purchase. Those are legitimate arrangements when their terms and consequences are understood.

The harder case is a supplier using an established dependency to change the bargain: making essential access contingent on newly imposed terms, or charging mainly because the customer cannot practically recover its own work elsewhere. I would want to examine what was promised, what is still being delivered, who bears the transition costs, and whether the customer had a realistic opportunity to plan for them. Calling every recurring charge exploitation would obscure that examination.

There is another objection worth taking seriously: customers voluntarily choose integrated products because those products are convenient and work well together. Demanding that every component be independently replaceable can increase cost and weaken accountability.

Coase’s analysis of the firm provides a reason to respect that objection. Coordinating through markets has costs, and organizing activities together can reduce them. [3] In a particular product, common ownership and a tightly coordinated design may deliver a result that is difficult to achieve through separately contracted components.

I have no interest in making a product worse merely to satisfy an abstract preference for how its suppliers should be organized. A customer can knowingly choose an integrated solution and accept its limitations. The relevant obligations include explaining material dependencies honestly, delivering the promised benefits, and treating the customer’s accumulated investment with care.

Consent matters, but it becomes less informative if material consequences were concealed or if the terms change after a customer has become dependent. Saying “they can always leave” is a weak response when leaving now means abandoning years of productive investment. There may still be a defensible reason for a price change or a discontinued service. The supplier should be willing to explain that reason and address the transition fairly.

This standard also has to apply inside the business. It would be inconsistent to celebrate fair exchange with customers while treating the people doing the work as disposable. Owners can contribute capital, judgment, coordination, and personal risk. Employees and collaborators contribute knowledge, effort, and responsibility of their own. A principled defense of profit should be compatible with fair compensation, truthful recognition of contributions, and keeping commitments to the people who helped create the value.

None of this produces a universal acceptable profit margin. A high margin can reflect a remarkable invention, a highly effective service, or a temporary reward for taking a risk that others declined. A low margin does not certify good conduct. The percentage alone cannot do the moral work.

I am also not arguing that a business must preserve every product or support arrangement forever. Resources are limited. Products become uneconomic. Technical changes can make an old approach impractical. Responsible conduct in those circumstances includes honest notice, respect for existing commitments, and a reasonable effort to avoid stranding customers unnecessarily. Continuing indefinitely at a loss is not the only alternative to indifference.

For an engineering business, the practical implications show up in unglamorous decisions. Explain the limits of a solution. Price valuable expertise confidently. Deliver the information the customer was promised. Charge for real support and real new work. Make significant dependencies visible before they become expensive surprises. Be willing to recommend a simpler solution even when it produces a smaller invoice.

That last decision may not maximize the revenue from one engagement. It can still be the right professional decision. I would rather be able to explain why the customer needed the work than become skilled at explaining why the customer could not escape it.

Profit gives a business the means to continue. The work should give customers a reason to want it to continue. I want the next contract to be an informed decision to hire us again, made by someone who understands the alternatives and still thinks we are worth it.


Sources

1. Kenneth J. Arrow, “Economic Welfare and the Allocation of Resources for Invention,” in The Rate and Direction of Inventive Activity: Economic and Social Factors (Princeton University Press, 1962), 609–626. NBER publication record; original chapter. See especially the discussions of uncertainty and information as a commodity, pp. 609–616. Arrow’s analysis concerns economic incentives and resource allocation; the ethical standard argued here is the author’s. 2. Paul Klemperer, “Competition when Consumers Have Switching Costs: An Overview with Applications to Industrial Organization, Macroeconomics, and International Trade,” The Review of Economic Studies 62, no. 4 (1995): 515–539. Publication record; Oxford archive record. See §§1–2 for the mechanism and the different sources of switching costs. 3. R. H. Coase, “The Nature of the Firm,” Economica 4, no. 16 (1937): 386–405. Publication record; university-hosted paper. See especially pp. 390–395. The discussion supplies a counterargument to treating integration itself as evidence of improper conduct.