# Design > Internal software is allowed to be as considered as the apps people choose for themselves - one design system, themes you set once, and screens you judge by looking at them Source: https://aipril.dev/docs/cms/design ## Corporate software is allowed to be beautiful Somewhere along the way B2B decided that internal software is where design does not apply. Grey forms. Tables that look like 1997. Screens that are technically complete and visibly unloved, because the buyer was not the user and the user had no alternative. A generation learned that "enterprise" means the thing you tolerate, and that good design is over there, in the apps they choose for themselves. That is not a law of the category. It is a habit. ## And it costs more than it looks **People spend eight hours a day in these screens.** At that duration a confusing layout is not a matter of taste: - It is **errors** - the field somebody fills in wrong because two fields look identical. - It is **training** - a week of it, for something that should have taken an afternoon. - It is **the workaround** - the spreadsheet people keep on the side because the real screen is unpleasant, and the shadow process that grows around it. - It is **the request never filed**, because filing it is worse than living with the problem. That one is invisible, and it is the expensive one. Bad interface is a tax, paid daily, by everybody, and it never appears on the invoice. ## The position Applications people work in should be as considered as the ones they choose for themselves. **Not loud.** Nothing here is trying to be a consumer app. Enterprise work needs density, restraint and clarity - a table that shows a hundred rows without ceremony, a form that does not make you hunt, states that are obvious rather than decorative. **But current.** The typography, the spacing, the colour, the way a component behaves under real data. Modern rather than fashionable: the point is that it should not look like it was built a decade ago, because that is what people read as "this company does not care". That position is why the widget stack was worth building instead of assembling from whatever was available. Each widget was designed against how these components are done well now, and each carries a wide palette of settings - and beyond it, detailed styling options the AI agent can reach, so "make this match our brand" or "this table is too heavy" is something you say rather than a ticket somebody schedules. ## One style, set once There is a design system underneath all of this, and themes on top of it. Pick a theme and adjust it to your company: - **Colour** - your palette, expressed once and used everywhere. - **Typography** - the families, sizes and weights, so a heading is a heading on every page. - **Density** - how much air the interface has. An operator on a tablet and an analyst on a wide monitor do not want the same density, and that is a setting rather than a hundred spacing decisions. - **Components** - where a particular component should look different in your brand, said once rather than set on every instance. - **Light and dark** - part of the theme, not a second theme somebody maintains in parallel. Then **every screen follows** - including the ones an AI agent draws tomorrow and the ones that arrived with an application you installed. That is what prevents the usual outcome: forty pages built by six people over two years, each nearly consistent with the others. Consistency here does not depend on everybody remembering the rules, because the rules are in one place and the pages read from it. How that works is [Under the hood](https://aipril.dev/docs/cms/under-the-hood.md). ## You judge it by looking at it The way designers have always judged things, and the way nobody has ever judged a specification. Screens open on a **canvas** while the application is still being prototyped: the real thing, on your own data, the way Figma puts a design in front of you instead of describing it. Select a block, move it, resize it, change what it shows, pin a comment where something is wrong and settle it with the people standing next to you. Nobody signs off a layout from a document, because nobody can. See [Built by AI, approved by you](https://aipril.dev/docs/apps/authoring.md). ## And where the catalogue stops It is not a wall. **Build your own widget** - with Claude or Codex, or with your own front-end developers - and it joins the catalogue as a first-class member: available to every page, styled by the same theme, and available to the AI agent that assembles pages. So the design ceiling is yours, not ours. ## Next [Built with AI](https://aipril.dev/docs/cms/ai.md) - why most of this never has to be assembled by hand.