The oldest heckle in the room
Twenty-four centuries ago, in the opening pages of Plato’s Republic, a rhetorician named Thrasymachus lost patience with a polite conversation and threw a grenade into it: justice, he said, is nothing else than the interest of the stronger. Whoever holds power writes the rules, writes them for their own benefit, and then teaches everyone else that obeying them is virtue. The shepherd fattens the sheep, he added — but not for the sheep.
Socrates out-argued him, Plato wrote the minutes, and philosophy has spent two thousand years treating the line as the villain’s opening bid. But run it through one substitution and it describes the technology market a small business buys from with uncomfortable accuracy. Nobody in software procurement says “justice.” We say “best practice.”
Who writes the rules you buy by
Think about where the rules of a technology decision actually come from.
The reference architecture that shows “how it’s done” was published by a vendor, and the way it’s done runs, by a striking coincidence, straight through that vendor’s product line. The analyst reports that grade the market are produced by research firms whose paying relationships — briefings, subscriptions, reprint licenses — flow in significant part from the companies being graded. The conference talk on the modern data stack was sponsored. The certification that makes your new hire “qualified” was designed by the platform it certifies people on, which means your training budget is also their retention program.
None of this requires anyone to lie. It only requires everyone to publish their own perspective and call it the industry’s. Each rule is genuinely a rule; the question Thrasymachus taught us to ask is merely whose interest it was written in. Per-seat pricing is “standard.” Auto-renewal is “standard.” Charging you to take your own data out the door is “standard.” Standard, in each case, for whom?
There’s a second-order version of the problem that hits a small and medium business (SMB) hardest: most “best practice” is written for enterprises, because enterprises are who the authors sell to. A control framework designed for a 5,000-seat company arrives at a 20-seat machine shop on the Front Range as received doctrine, unexamined — three layers of tooling to solve problems the shop will never have, priced in a currency the shop doesn’t print. The rules were not written against the small firm. They simply weren’t written for it, and following someone else’s rules by default is how you end up funding someone else’s roadmap.
The record is written by the winners
Here is the part of the old argument that procurement teams rediscover the hard way: the evidence you research from is not a neutral archive.
A case study is a story about a project that survived, written by the party that got paid, approved by a marketing department, and published because it sells. The Enterprise Resource Planning (ERP) implementation that cratered — blew the budget, burned the controller out, got quietly rolled back to QuickBooks — publishes nothing. It signed a mutual non-disparagement clause on the way out. The result is a public record with the failures surgically removed, which is to say: a record of the stronger party’s wins, presented as the odds.
The old proverb “nobody ever got fired for buying IBM” is the same mechanism wearing a safety vest. It sounds like risk management. Read it again and it’s an incumbent’s market position, restated as your career advice. The safe choice is safe for the person choosing, precisely because the record — who gets blamed, who gets believed — was arranged by the strong before you walked in.
And the newest research shortcut inherits all of it. Ask an artificial intelligence (AI) chatbot for the best platform in any category and you get a fluent summary of the published record — the vendor content, the sponsored comparisons, the survivor case studies. The model doesn’t launder the bias out; it compresses it and returns it with confidence. Training data is the record of whoever published most, and we’ve just established who that is. An AI answer about the market carries the politics of its corpus, delivered in a tone that suggests it carries none.
The answer Socrates gave
Plato’s rebuttal to Thrasymachus is the most useful sentence in the whole exchange for anyone who buys — or sells — expertise. No craft, Socrates argues, serves the practitioner insofar as it is a craft. Medicine, as medicine, seeks the patient’s health, not the doctor’s income. A pilot, as a pilot, gets the sailors home. The moment the practice starts optimizing for the practitioner, it has stopped being the craft and become something else wearing its badge.
That is the cleanest test of advice ever written, and it converts directly into a procurement standard: never ask whether an adviser is smart; ask whom the advice structurally serves. Not their intentions — their incentives. A consultant paid a reseller margin on the software they recommend is not lying to you, but their craft has a second client. A proposal whose every option lands inside one vendor’s ecosystem was not written by your side of the table, whatever the letterhead says.
You cannot fix this with trust. You fix it with arrangements — advice whose interests are inspectable. Recommendations in writing, with reasoning, so they can be argued with. Disclosure of what the adviser earns from each path. Deliverables you own outright: documentation, credentials, the data model, the export scripts. It’s the reason our own doctrine is vendor-neutral [[IT strategy]] and systems a client can own and leave with — including leaving us. An exit that stays cheap is the only guarantee that keeps everyone’s craft honest, ours included.
Five questions that shift the power
Thrasymachus can’t be refuted from a position of weakness — but he can be managed. The weaker party’s move is not to overpower the strong; it’s to stop mistaking their interests for laws of nature. Five questions do most of the work:
- Who wrote this rule? For every “best practice” in a proposal, find the author. If the reference architecture comes from a vendor, read it the way you’d read their bid — because it is one.
- Where are the bodies? Ask every vendor and every consultant for a project that went badly and what they did about it. The ones who can answer have been telling you the truth all along. The ones who can’t have a record with the failures removed, and now you know how to read it.
- Price the exit before the entrance. Data export — format, completeness, cost. Contract termination. Migration effort out, not just in. The total cost of ownership (TCO) includes the cost of leaving, and if leaving is expensive, the price of staying will rise to match. Lock-in is the interest of the stronger, itemized on next year’s invoice.
- Keep custody of your own record. Your chart of accounts, your data dictionary, your integration credentials, your documentation — in your tenancy, under your control. Every shell prompt encodes the principle: whoever sits at it decides what runs. Keep your business at the prompt of its own systems, not watching someone else type.
- Make advisers show their interests. Ask what they earn from each recommendation, and get the answer in writing. An honest craft survives the question. The other kind changes the subject.
None of this is cynicism. It’s the opposite: it takes the market seriously enough to read it accurately. Vendors are not villains, analysts are not liars, and the proverb about IBM contains real wisdom about integration risk. The point is smaller and sharper — every rule in your inbox was written by someone, in some interest, and a business that asks whose buys better than a business that doesn’t.
Next step
The Republic runs nine more books because the question deserved more than a heckle. Your next software decision deserves more than a case study written by the seller. If there’s a proposal, a renewal, or a “standard architecture” on your desk and you’d like a second reader whose only interest in it is yours — tell us what you’re weighing, and we’ll go through it question by question.