Most software sold to businesses is used by two people who never meet. One of
them opens a console every morning and spends the day setting things up:
services, capacity, pricing rules, staff, permissions. The other one arrives
from a search result, books something, and leaves. They are looking at the
same records through two completely different windows.
Template catalogs do not have a shape for that. A software product page is
assumed to be one screenshot, three benefit cards and a pricing table, which
is right for a single-surface app and wrong for a platform. The thing a
platform has to explain is not its feature list. It is the line between the
two surfaces: what an operator changes, and where that change shows up.
So this template puts that line in the data. Every module records which
surface it lives on, and the platform page builds its three sections from that
field, so adding a module changes the shape of the page. Plans hold a typed
reference to the modules they open, so a pricing table and a feature list
cannot quietly disagree; break the reference and the build stops.
The interfaces on the page are drawn rather than photographed. A screenshot of
a product that does not exist yet is a picture of nothing, and a buyer cannot
edit a JPEG into their own product. Every console and storefront shown here is
HTML with real content in it: it reflows at 360px, it reads in a screen
reader, and replacing the copy replaces the product.
It is also the loudest template in the catalog, and that is a decision rather
than a mood. The other five carry a broken, low-saturation accent taken from a
material: copper, terracotta, fir, sea, brass. That is the right voice for a
room a customer walks into. A software product is not a room. Its color
comes from a screen, and a screen’s color is saturated.
