Fable
The river port accountant counted every bag of salt back to its owner
At the river port there was a fleet that ran errands for merchants. The boatmen checked accounts, delivered goods, asked prices, and wrote replies, and at month's end they simply consolidated firewood, labor, and dock fees into one total account.
As the business expanded, the general ledger grew higher and higher. Large merchants said they paid more, small merchants said they used less, but the fleet could not explain which type of work truly burned money.
The port master first split costs evenly by number of merchants. As a result, quiet merchants paid for high-frequency merchants, complex orders were subsidized by simple orders, and several profitable customers actually lost more the more they did.
He then charged by voyage. Some split a complex task into many small voyages, others stuffed high-risk queries into ordinary voyages. The books looked fair, but gross margin remained chaotic.
The new accountant hung a source tag on each bag of goods: which merchant it came from, which process it belonged to, which ship was used, how many times translation was requested, how many reruns were done, and what result was finally delivered.
He discovered that what really swallowed profit was not the customer with the most ships, but those processes that required checking old files every time, repeatedly changing their story, and triggering manual review.
The port master reworked pricing accordingly. High-cost, high-value processes were quoted separately; cacheable, batchable, low-risk processes were priced lower; abnormal retries and manual review were explicitly counted into cost.
Finance, engineering, and sales looked at the same ledger together for the first time to discuss: which customers were worth expanding, which features should be optimized, and which packages must be repriced. Only then did the harbor master see that costs become business judgment rather than cloud bills only when they are attributed to customers, tasks, and outcomes. Later, an even trickier job arrived. On the surface it looked like an old problem magnified, but in fact it forced out all the gaps hidden in the process: who takes over first, who can make changes, and how to return to the previous step when something goes wrong. Places that used to be glossed over by familiarity and tacit understanding now all had to be made clear. The person in charge did not urge everyone to be more careful again; instead, he walked the site again. He had people record every handoff, every failure, and every remediation, which places were merely slow, which places would harm the result, and which places would be hard to recover once wrong. After the new rules were rolled out, the first few days were not smooth. Some complained about an extra check, and some felt their old experience was being insulted. But when the next anomaly appeared, everyone could for the first time follow the traces to find where the problem occurred, instead of gathering around the result and guessing at each other.