Learn · Systems
The law of parsimony, applied to business.
Occam's razor is older than software, and it is a better test for a company's systems than most software vendors will tell you. What the principle actually says, where it comes from, and what it looks like applied to the order flow, the inventory count, and the support queue of an ecommerce business.
In this explainer
What It Says
What the law of parsimony actually says.
The law of parsimony, better known by its popular name Occam's razor, is a principle from philosophy of science and logic: when two explanations both account for the same facts, prefer the one that assumes less. It is named for William of Ockham, an English Franciscan friar and logician working in the early 14th century, whose writings applied the idea of preferring fewer assumptions to problems in logic and theology.
The line most often printed as "his" quote — that entities should not be multiplied beyond necessity — is not a verbatim sentence from Ockham's surviving texts. Later scholars condensed his position, expressed across several of his writings, into that one tidy Latin line. The sentiment is genuinely his. The specific wording is a paraphrase, and this page will not print it as a direct quote, because it is not one.
What the principle is not, is a claim that the simplest explanation is always the correct one. Reality is not obligated to be simple, and a genuinely simpler account that leaves out a fact the more complicated account explains is not preferred — it is just wrong. The razor is a tie-breaker, not a truth detector: between two explanations that both fit the evidence equally well, it tells you which one to prefer until new evidence says otherwise. Adding an assumption is a cost. It should buy you something.
Terms
- Occam's razor
- The popular name for the principle: it "shaves away" assumptions an explanation does not need.
- The law of parsimony
- The formal name for the same principle, used in philosophy of science and logic.
- Parsimony
- The underlying property being preferred: an account, model, or system with fewer independent parts.
The Translation
From philosophy of science to running a company.
Ockham was weighing explanations, not spreadsheets or software stacks. But the same test transfers cleanly to a company's systems, because a system is a kind of explanation: it is a company's standing account of how a fact gets from one place to another — how an order becomes a shipment, how a lead becomes a customer, how a receipt becomes a line on a closed set of books. Every extra tool, every extra hand-off, and every extra exception is an added assumption in that account, in exactly the sense the razor is skeptical of.
A company that runs the same process through four disconnected tools has not explained the process four times more thoroughly. It has added three more places the account can disagree with itself: three more logins, three more chances that the number in one system is not the number in another, three more people who have to remember which system is the real one this week. None of that complexity is buying the company anything the simpler version would not also buy it. That is the test the law of parsimony sets: not "how few tools can we use," but "does this additional part earn its place, or is it here because nobody removed it."
The three sections below apply that test to the parts of a company most operators recognize on sight: the systems that hold the data, the hand-offs between them, and the exceptions that grow around every rule if nobody prunes them. The examples are written generically, drawn from the shape of ecommerce operations rather than any one company's specifics — the order flow, the inventory count, and the support queue.
Applied
Fewer systems, fewer hand-offs, fewer exceptions.
- 01
Fewer systems
One system of record beats three systems that each hold a partial, disagreeing copy of the same fact.
An order lives in one place — the ledger that tracks inventory, invoicing, and fulfillment together — instead of a cart platform, a spreadsheet, and an accounting tool that all claim to know the current stock count.
- 02
Fewer hand-offs
Every hand-off between a person, a spreadsheet, or a disconnected tool is a place data can be re-typed wrong, delayed, or dropped.
A support agent who can see the order, the shipment, and the refund status without opening a second tool and asking a colleague to check resolves the ticket once, not three times.
- 03
Fewer exceptions
A rule with fourteen exceptions is not a rule. Every special case is a place the system will eventually be wrong, and a place a new hire has to be told about by hand.
A restock rule that triggers the same way for every warehouse is a policy a machine can run. A restock rule with a separate exception for each region is a policy that only lives correctly in one person's head.
Order flow is usually where the extra systems accumulate first, because it touches marketing, sales, fulfillment, and accounting in sequence. A parsimonious order flow has one record of an order, updated in place as it moves through the stages, instead of a separate record created in each department's own tool and reconciled by hand at the end of the month. The test is not whether marketing, fulfillment, and accounting all need to see the order — they do — it is whether they need three different copies of it to do that.
Inventory is where a hand-off that looks harmless quietly becomes an exception. A count that is updated in one system and then re-typed, on a delay, into a second system that a different team actually uses for reordering is not two systems working together — it is one system with a lag built into it, and the lag is exactly where a stockout or a duplicate order comes from. Removing the second copy does not remove any information a team needs; it removes a step where the information could go stale.
Support shows the fewer-exceptions principle most clearly, because support policy is where exceptions are proposed first. A refund window, a return policy, an escalation rule — every one of these is a candidate to grow a special case for a particular customer, a particular product line, or a particular region. Each special case is defensible on its own the day it is added. A year of special cases later, the policy is no longer something a new hire, or an AI agent trained on it, can apply consistently, because it is not really one policy anymore. The parsimonious version keeps one rule and treats the case for an exception as a decision that has to be made again, in the open, rather than silently encoded as a permanent branch in the system.
Operator's Note
Why the company is named Parsimony.
The name comes from this principle, and nowhere else. It is the standard the company holds its own recommendations to: when an ERP implementation, an automation, or an AI agent build is scoped, the question asked first is not what could be added, but what is the fewest systems, hand-offs, and exceptions that still get the job done correctly. Read the reasoning that standard comes from, and the people applying it, on the about page.
FAQ
Common questions.
- 01
What is the law of parsimony?
A principle from philosophy of science, closely associated with the 14th-century English Franciscan friar and logician William of Ockham: when two explanations account for the same facts, prefer the one that assumes less. It does not say the simpler explanation is always true — only that it should not be discarded in favor of a more complicated one without a reason to.
- 02
Is Occam's razor the same thing as the law of parsimony?
Yes, they name the same principle. "Occam's razor" is the popular name — it "shaves away" unnecessary assumptions. "The law of parsimony" is the more formal name used in philosophy of science and logic. Both describe a preference for the explanation, or the system, that needs the fewest extra parts to work.
- 03
Did William of Ockham actually write "entities should not be multiplied beyond necessity"?
That exact Latin sentence does not appear in his surviving texts, even though it is the phrase most commonly attributed to him. Ockham's actual writings state related versions of the same idea in several places, and later scholars condensed his position into the line now printed in textbooks. The principle is his; the specific wording is a paraphrase.
- 04
Why is the company named Parsimony?
The name comes directly from this principle. It signals the standard the company holds its own work to: the fewest systems, hand-offs, and exceptions that still get the job done correctly, applied to ERP, automation, and AI agents.
More on how these systems are actually built: the Cloud ERP explainer, the rest of the Learn hub, and the about page.
Pricing
Automate is public.
ERP and agents are quoted.
Parsimony Automate has public monthly plans — see Automate pricing. Chat agents, voice agents, and Cloud ERP are quoted to the job. Call or send the form and we put a package together.
- 01Quoted
Cloud ERP
Managed ERPNext on Frappe Cloud. Quoted to the job.
- 02$59 / $199 / $497 a month · self-serve
Automate
CRM, funnels, two-way text, workflows, and websites on one login.
- 03Quoted
AI chat and voice agents
Chat on your site and help desk, voice on your phone line. Quoted to the job.