--- title: "Malleability" description: "Malleability is the property of a product that bends to its user without breaking: settings, templates, scripts, free-form fields." canonical: https://moa.giglabo.com/strategies/malleability/ locale: en --- # Malleability > Markdown twin of https://moa.giglabo.com/strategies/malleability/ — the same content as the HTML page, a fraction of the bytes. > Every page of this site has one: append `.md` to any URL, or `index.md` to a directory URL. > Site structure and the full page list for agents: https://moa.giglabo.com/llms.txt Category: Transformation · Role: Morphs · Depth: — Gist: easily modified or customised ## Moats > Malleability morphs; it does not hold. A product that is easy to change is easy for anyone to change, and the ability to bend is not something a customer pays to keep, so nothing here stops a rival and no moat maps to it. A moat can appear next to it, dug by something else. When customers' configurations pile up until leaving means rebuilding them, that is Switching costs (#5), dug by the customers' own work. When third parties write extensions, that is a Developer ecosystem (#20), dug by Composability or Modularity. Malleability is the soft material those strategies shape; on its own it is a posture, not a defense. ## Summary Malleability is the property of a product that bends to its user without breaking: settings, templates, scripts, free-form fields. The edge is fit — every buyer gets a shape that matches their case, so you win deals a rigid rival loses. It is a way to follow demand, not a way to keep it: the clay does not resist a second potter. ## How it works A rigid product is a bet on one use. A malleable one lets the buyer place the bet: they reshape it around their process, their vocabulary, their edge cases, and the product ends up fitting jobs its maker never saw. That is where the edge comes from. You sell into more situations than a fixed design can, you learn what buyers actually do from the shapes they make, and a pivot costs a configuration change rather than a rewrite. The price is that flexibility is a property of the object, not a barrier around it. A rival can make its product just as malleable, and code generation is making modification cheap for everyone at once. What malleability buys you is time and information: you stay alive while the market decides what it wants, and you find out first. Whether anything durable comes of it depends on what the bending leaves behind — configurations a customer cannot walk away from, extensions other people wrote — and those belong to other strategies. ## Do you have it - Customers run your product in configurations you never designed, and you find out from support tickets, not from your roadmap. - A buyer's change request ships as a setting or a template, not as a fork of the codebase. - You have changed what the product is for at least once without rewriting it. - Sales calls end with the buyer's own case built live in the demo more often than with a missing feature. ## How to dig it - Split what changes per customer from what never changes: config, templates, hooks and scripts on one side, the core on the other. - Expose the knobs you already turn by hand for customers as settings they can turn themselves. - Leave room in the data model for a use you have not seen: custom fields, tags, free-form attributes. - Log what customers bend, and ship the three most common bends as defaults every quarter. - Track the time from a buyer's request to a shipped change and drive it toward hours. ## How it erodes - Code generation makes modification cheap for every rival at once, so a flexible product stops standing out. - Too many knobs turn the product into a kit nobody can set up, and an opinionated rival wins on ease. - Bends you never intended become a compatibility contract: every change you make now breaks someone's setup. - A customer who bent your product can bend a rival's just as easily; without accumulated configuration, nothing keeps them. ## Solo, without capital A single person can make a product malleable this quarter: settings, templates, a plugin hook and free-form fields cost design discipline, not money. For a solo builder that is the real value: you chase demand instead of guessing it, and a pivot is a weekend. Alone you cannot turn it into a defense. The moat, if it comes, is Switching costs (#5) from customers' accumulated setups, reachable solo but under attack from AI-driven migration, or a Developer ecosystem (#20), which needs an audience you lack. ## In nature, in business Nature: — Business: clay, software code, method actors - **Microsoft Excel** — A grid with formulas that users bend into budgets, schedules, inventories and games, so it ends up running processes it was never designed for. - **WordPress** — A blog engine whose themes and plugins let site owners reshape it into shops, forums and portfolios; the modification surface became the product. - **Notion** — A page made of movable blocks that users rebuild into wikis, trackers and databases, with templates passed around instead of features. ## Combines with - [Composability](https://moa.giglabo.com/strategies/composability/) — Composability takes the bends and turns them into parts that recombine, which is where a standard or a developer base can grow. - [Modularity](https://moa.giglabo.com/strategies/modularity/) — Modularity is how you keep change cheap: a unit swapped in isolation does not break the rest. - [Iteration](https://moa.giglabo.com/strategies/iteration/) — A product that bends fast can ship a short cycle; each cycle shows which bends to keep. - [Versatility](https://moa.giglabo.com/strategies/versatility/) — A product easy to reshape can honestly claim competence across many tasks instead of promising it. [This strategy on the map](https://moa.giglabo.com/strategies/?view=lanes&hl=malleability) [Map this combination](https://moa.giglabo.com/strategies/?view=lanes&hl=malleability,composability,modularity,iteration,versatility) ## Fights with - [Simplicity](https://moa.giglabo.com/strategies/simplicity/) — Every knob added for flexibility is a point of failure and a decision the user must make; Simplicity removes knobs. - [Predictability](https://moa.giglabo.com/strategies/predictability/) — A product that takes a different shape at every customer cannot promise the same experience everywhere. [Map this tension](https://moa.giglabo.com/strategies/?view=lanes&hl=malleability,simplicity,predictability) ## Source Strategy taxonomy © kepano (Steph Ango), paraphrased with attribution. Role and moat mapping © Moat Atlas. https://stephango.com/ ## Related - HTML version of this page: https://moa.giglabo.com/strategies/malleability/ - Русский: https://moa.giglabo.com/ru/strategies/malleability/ - Previous: Copycat — https://moa.giglabo.com/strategies/copycat/ - Next: Metamorphosis — https://moa.giglabo.com/strategies/metamorphosis/ - Atlas: https://moa.giglabo.com/ - Catalogue: https://moa.giglabo.com/moats/ - Calculator: https://moa.giglabo.com/calculator/ - Strategies: https://moa.giglabo.com/strategies/ - Site map for agents: https://moa.giglabo.com/llms.txt