The One-Man Company Stack
The software that lets one person be a fragrance house: what earned its keep, what got deleted, and the rule that decides.
The house is one person, and the readers who arrive here from the Ideas essay on that arrangement usually ask the same practical question next: how, mechanically, does one person do the work of a company? Part of the answer is scope discipline, covered elsewhere. The rest of the answer is software, and since the Signal section exists to discuss technology with the same taste standards as everything else, here is the stack, audited honestly, with the rule that governs admission.
The rule first, because the rule is the article: a tool earns a place by removing a category of work, not by promising to organize it. The distinction sounds small and decides everything. Organizing tools multiply, they invite tending, they turn the proprietor into their secretary, and a one-person operation dies of secretarial load first, long before it dies of competition. Removal tools subtract: the storefront that handles payment, tax math, and hosting is a finance clerk and a webmaster removed; the accounting layer that ingests transactions automatically is a bookkeeper removed. Every January the stack gets re-audited against the rule, and whatever demanded more attention than it deleted gets deleted itself.
The load-bearing layer is boring on purpose. Commerce runs on a hosted storefront rather than anything custom, because a custom store is a second product and one person cannot afford two. Payments, invoices, and the arithmetic of selling across currencies ride the same rails. Communication is plain email, answered personally, because the customer wrote to a house and deserves the house, not a ticketing macro; the day that becomes impossible will be a good problem announced by its own arrival. Logistics is a shipping aggregator and the patience of the national post. None of this is interesting, which is the point: infrastructure should be forgettable so attention can be spent where the house is unsubstitutable, at the bench.
The layer above is the memory. A one-man company's single point of failure is the skull of the proprietor, so the house keeps an external one: a plain-text vault of linked notes, formulas and their revisions, supplier histories, maceration observations dated like lab entries, the accumulated why behind every decision. Plain text, deliberately, files that will open in forty years on anything, because this journal has covered the durability of the notebook and practices what it published. The vault is the closest thing the house has to an employee: it never forgets, never resigns, and works weekends.
Then the new hire: the AI layer, which the house wrote about with fresh astonishment in the field report and can now describe with a year's sobriety. In practice it functions as a research assistant with infinite patience and no taste, drafting the regulatory paperwork summaries, translating supplier correspondence, roughing out page code for this very site, holding one end of a thinking-out-loud conversation at two in the morning. The employment terms are strict: it drafts, the house decides; it never touches a formula; nothing it writes ships unread. Applied to the rule, it removes the category of first drafts, and first drafts were the largest unpaid department in the building. It is the best hire the house never made, precisely because it is not allowed to be the perfumer.
The refusals define the stack as much as the roster. No social media scheduler, because the house posts when there is something to say, and a queue of pre-written spontaneity is a small lie told weekly. No analytics dashboard beyond the storefront's own, because a one-man house steering by dashboards develops a dashboard-shaped product; the correspondence from customers is richer telemetry, one letter at a time. No CRM: the customers fit in a text file and, mostly, in actual memory, which is after all the house specialty. No project management suite for a team of one, a to-do list in the vault has never once dropped a task on the floor. Each refusal was a small war against the industry default, and each is re-fought at every renewal price.
What the stack buys, added up, is the only metric that matters here: hours at the bench. The honest accounting says the machines took over perhaps two-thirds of what a nineteen-nineties version of this house would have needed staff for, and the remaining third, composing, smelling, deciding, writing to you, is precisely the third that was wanted. The Ricardo essay in the Curriculum explains why that division holds: the software's hour is cheap at clerical work and worthless at the bench, and the proprietor's hour is the exact reverse. The stack is comparative advantage, installed and configured.
The closing advice travels to any craft run by one pair of hands. Audit every tool against the removal rule annually, keep the memory external and in plain text, let the machines have the drafts and the drudgery, and guard the deciding for yourself, because deciding is the product. The company is not the software. The company is the taste; the stack just keeps the lights on around it.