Explosion of Internal Software

#concept

Summary

The layer of organisational life that used to be one Excel file, one wiki page, and one hacky script is about to be replaced by actual software, because building it now costs an evening instead of a quarter. thorsten-ball encoded his 20-person club's ordering process in ~2 hours of typing on his phone. This is the corpus's strongest external validation of the webinar's thesis — little tools you make for yourself.

Current Understanding

The before/after. Before, internal software was whatever survived the cost-benefit test against a spreadsheet — which almost nothing did. Now the test is trivially passed, so the Excel/wiki/hack layer gets replaced by real, purpose-built tools.
Two variables separate winners from losers, per Thorsten: (1) knowing how to use agents, and (2) having the token budget to do it. Scope matters on the second, and was corrected here 2026-07-28: he is describing metered fleet work (parallel orbs, parked agents), not a subscription. At individual scale the corpus's own practitioners run large agent setups on flat consumer plans without reporting a ceiling — so for a non-engineer this is a skill divide, and the budget is one subscription. See the scoping note on enterprise-ai-reality.
The velocity claim: "You cannot take a programmer who doesn't use AI, they're going to get crushed by a mediocre programmer with AI." Stated about programmers, but the internal-software argument extends it to any role that has ever maintained a spreadsheet.
The hard part is not building. His printer anecdote is the whole skill in one exchange: asked to build an app so a tablet prints a paper receipt for the kitchen, he answered "Why do you need a printer? Why not a second tablet?" Seeing the workflow underneath the request is the surviving competence — see product-ownership and the first-principles section there.

Why this matters for the webinar. It is the outside evidence for thesis T5 in 2026-07-28-webinar-theses — the claim that had been the talk's least provable. eugene's arc (chat box → your own OS) lands on exactly this: "It dissolved — into the operating system. Into little tools you make for yourself… You don't buy it. You build it — one small tool at a time." Thorsten reaches the same endpoint from a frontier-engineering starting point and with a non-technical audience (a 20-person social club, a menu photo, a phone). That convergence is usable evidence: the pitch is not an engineer's fantasy about non-engineers, it is what happens when someone with the skill applies it to an ordinary group of people.

Evidence

Excel/wiki/hack replacement, the club ordering app in ~2 hours of phone typing, the token-budget variable, "crushed by a mediocre programmer with AI," the printer anti-example — 2026-07-28-agentic-engineering-10x-developer.
The webinar's convergent framing — "little tools you make for yourself," the OS arc — raw/notes/Webinar script.md (raw, not yet ingested).
Non-engineer capability ceiling and the same build-it-yourself instinct — levels-of-ai-usage, personal-ai-operating-system.

Concepts: emacsification-of-software (sibling mechanism — remixing rather than building), maintenance-is-the-real-cost (the bounding counterweight), personal-ai-operating-system, levels-of-ai-usage, product-ownership, shedding-weight, enterprise-ai-reality (token budget as access), solve-first-then-skillify
Entities: thorsten-ball, eugene, allie-miller, virtido

Contradictions / Uncertainty

Survivorship. Thorsten is a founding engineer at an agent company building for a club he belongs to. The corpus's actual non-engineers (nina, yulia, larysa) hit friction, integration-dead-ends and memory loss well before "2 hours on a phone." His datapoint proves the ceiling is high, not that the floor is low. Status: tentative.
Nobody owns the result. Internal software built in an evening still needs to survive its author leaving, a schema change, or an incorrect order going out. The source treats creation cost as the only cost — the same gap emacsification-of-software has around maintenance. (Upgraded 2026-07-29 from self-criticism to a sourced contradiction: 2026-07-29-what-if-we-vibe-code-it makes this objection its whole thesis — maintenance-is-the-real-cost — and supplies the corpus's only observed outcome of this pattern in the wild: a company that built its own Jira clone in March 2026 and returned to a bought tracker by July. Partial reconciliation: the club app passes that source's own build-vs-buy checklist — tiny, no SLA, no external users — so the disagreement is about where the threshold sits, not whether one exists.)
The token-budget variable is named and then dropped. Who pays, how much, and what happens to people or teams without the budget is unaddressed in the source. Partly resolved by scope (see above): under flat-rate consumer pricing it appears not to bind at individual scale, and the corpus has two practitioners running large setups to show it. It remains open for metered pricing and fleet scale — and eugene's prediction that prices rise ("what I now buy for 200 will cost about 1,000") would reopen it for everyone if it holds. Status: tentative.

Next Questions

What is the realistic first internal tool for the webinar's HR audience — and does it survive contact with the friction Nina and Yulia describe?
Is there a threshold above which internal software must graduate to being owned like a product (an on-call rota, a schema, a backup), and where is it? (Sharpened 2026-07-29: maintenance-is-the-real-cost supplies a checklist for the question — size, ongoing support, operational load, second-business willingness — but not the line itself.)

5.9 KiB Raw Permalink Blame History