“Enshittification.”
“Excuse me?”
“Sorry. But that’s what I’m hearing.”
Darren had interrupted somewhere between feature rationalisation and reduced cognitive burden, two expressions which, translated out of Corporate, meant that the next version of Ledgerly would do less and congratulate itself for the improvement.
For twenty minutes he had listened to the proposed disappearances. Advanced reporting: hidden. Campaign scheduler: perhaps removed. Customer segmentation: simplified. A handful of smaller functions, each used by some statistically embarrassing minority, were being discussed in the past tense while still technically alive.
“We should be explaining why customers need these features, not burying them.”
Priya, whose presentation he had just hijacked, invited him to continue. Not warmly.
“Has anyone read my proposals?”
They had.
“All of them?”
Graham assured him that eighty-three slides had not passed unnoticed.
“Then why are we going backwards?”
They weren't going backwards. They were reducing friction.
Of course they were.
Friction had become the carbon dioxide of software: invisible, omnipresent, morally suspect. Every click was friction; every decision was friction; reading was friction; knowing what you were doing was increasingly regarded as an edge case.
Ledgerly served tradespeople. Plumbers, electricians, roofers, painters, tilers, window cleaners: men and women who spent their working lives negotiating electricity, gravity, combustion, water pressure and the occasional structural opinion of a Victorian terrace, but who were apparently liable to psychological collapse in the presence of a fourth dropdown menu.
“Why are we underestimating them?”
“We're not.”
“Then stop taking their tools away.”
The numbers, unfortunately, had numbers on their side. Thirteen functions accounted for nearly ninety per cent of routine activity. Whole provinces of Ledgerly existed almost without human visitation. Management saw waste. Darren saw undiscovered country.
“Teach them.”
Graham took off his glasses. “Darren, nobody here disputes that you're the smartest person in the room.”
Michael raised a hand. “I dispute it provisionally.”
“Thank you, Michael. But our customers aren't Darren.”
“No,” said Darren. “They're people who can find an electrical fault behind a wall.”
“And they want to send an invoice without doing a course first.”
This was the difficulty. Graham believed software should remove decisions. Darren believed software should create possibilities. Both called the result simplicity and regarded the other's version as madness.
A week earlier Darren had been asked to rethink Ledgerly. He had made the elementary mistake of believing the verb.
His proposal began with the information the software already possessed and everybody else appeared content to waste. Ledgerly knew what a customer charged, where he worked, what jobs made money, which clients paid late, which services were growing, which Tuesdays contained nothing but existential space. To Darren, data without consequence was merely digital hoarding.
A plumber finished a bathroom. Three photographs. Tap: JOB COMPLETE.
Why should the intelligence stop there?
The photographs could update his portfolio. The job could become a local case study. The customer could receive a review request at the moment experience suggested gratitude was ripest. An empty Thursday could provoke advertising for precisely the work the plumber wanted, in precisely the radius he would travel, at a price informed by what his own accounts said rather than by whatever number entered his head while standing in someone's kitchen.
Now they were listening.
Then Darren ruined it with APIs.
“We educate the customer base just a little.”
He pinched perhaps two millimetres of air.
“API keys. Integrations. Nothing heroic. Once they understand that, we've opened everything. Mapping data, review sites, directories, advertising, suppliers, their CMS, anything with an endpoint. And the advanced users can have proper granularity. Thresholds, rules, basic expressions, the most rudimentary coding—”
Michael's hand returned.
“Coding.”
“Barely.”
“They're plumbers, Darren.”
“They're not some protected species. I think we can risk a settings page.”
“Why does a plumber need to know what an API key is?”
“Why does he need to know what all the things in his van are, even if he only uses half of them most of the time? Because knowing things is useful.”
There it was again: knowledge, appearing without permission.
The modern interface had developed a curious ambition to resemble a boiled egg. Smooth, white, featureless, nourishing enough, impossible to operate incorrectly. Darren wanted machinery with the casing available for removal.
“Three questions for ordinary users,” he said. “That's all. What do you do, where do you do it, what work do you want more of? Big friendly button. Done. But if somebody wants to get underneath—let him.”
“With what?”
“Rules. Expressions. Hell, allow him to write batch files.”
The room stopped.
“Batch files,” said Michael.
“It was an example.”
“From the reign of George W. Bush.”
“They still work.”
“So does a trebuchet.”
At least that was an objection with some velocity.
Darren glanced at the time and discovered, with mild disbelief, that only thirty-eight minutes had passed. The meeting seemed to have developed a local gravitational field. People began sentences whose conclusions arrived in Darren's head while their owners were still selecting verbs. Twice he answered before an objection had finished and twice Graham told him not to interrupt. Darren apologised sincerely on both occasions and considered both apologies unjust.
During a discussion of support overhead he opened the small case beside his laptop, swallowed the day's remaining capsules and half-tablets with cold coffee, and returned to the discussion before the discussion had noticeably advanced. He had spent six months adjusting the stack: concentration, recall, wakefulness, verbal fluency, sleep efficiency. The dosages were in a spreadsheet. Naturally.
Graham looked at him for a moment, then back at the proposal.
The automated marketing stayed interesting. So did the website work, the review system, the capacity analysis. They would take another pass. Incorporate as much as they reasonably could. Preserve the ambition without requiring a roofer in Wolverhampton to become a systems architect between estimates.
It was, Darren thought, progress.
At the door Graham stopped him.
“And I meant it, by the way. Smartest guy in the room.”
Darren smiled.
“Then occasionally let me finish a sentence.”
Graham laughed.
Darren left pleased.
It had taken them forty-seven minutes to understand him.
He supposed everyone had their own processor speed.

