Agentforce Commerce Is Live: Who Writes What It Says?Salesforce announced general availability of Ag…
What's Actually Pre-Composed in Laioutr's Blueprints
What's Actually Pre-Composed in One of Laioutr's 60 Industry Blueprints?
A Laioutr Industry Blueprint is a fully pre-composed storefront for a specific vertical, including a curated component selection, a content model, and design tokens, that goes live without a team starting from zero. Unlike a Growth Kit, which delivers a single component group for one use case, a Blueprint covers the entire storefront: from the category page to the checkout flow, tailored to the typical requirements of that vertical.
What Is an Industry Blueprint?
On July 2, 2026, we launched Industry Blueprints: 60 pre-composed frontends for 60 verticals, live in days instead of months. This article goes one level deeper and answers the question we've heard most often since: what exactly is pre-configured in a Blueprint, and where does the pre-configuration stop so your team can still build a distinct brand on top of it.
A Blueprint consists of three layers. First, a curated component selection from the Laioutr UI library, matched to the vertical, for example size charts and outfit-builder blocks for fashion, tiered-pricing components and minimum-order-quantity logic for B2B wholesale, or configurator blocks for furniture with variants like wood type and upholstery. Second, a predefined content model that already reflects the vertical's typical data structures, such as product attributes, category hierarchies, and filter logic. Third, a design token set as a starting point, meaning color palette, typography scale, and spacing values matched to the vertical, but fully overridable.
The Problem: Composable Setups Too Often Start From Zero
Composable commerce solves vendor lock-in, but creates a new problem: choosing a composable stack usually gets you building blocks, not a finished storefront. The frontend team has to assemble a vertical-specific storefront out of a generic component library, including every content-model decision other fashion or B2B brands have already made before. That build typically takes weeks to months before the first category page can even be meaningfully populated.
The biggest misunderstanding here: many teams assume a Growth Kit solves this problem. But a Growth Kit is deliberately narrower in scope, it delivers a component group for one specific use case, such as a bundle for cross-selling or for a loyalty program, not a full storefront architecture with a content model and vertical-specific layout. If you need to cover an entire vertical, you need more than a Kit, you need a Blueprint.
How Laioutr Solves This
Blueprints build on Laioutr's five products, with a clear pre-configuration contract. The UI library (Cockpit 2.2) provides the component base, from which a vertical-specific subset gets curated per Blueprint, instead of every team making the same selection from scratch. The theme system (Cockpit 2.3) sets the design tokens for the vertical as a starting point, but color, typography, and spacing remain changeable at any time through token configuration, so no component fork gets created.
What deliberately stays unconfigured: brand-specific imagery, your actual backend's product data connection, and every content decision that makes your brand distinct. A Blueprint is a starting point with vertical-typical structure, not a white-label theme that goes live as-is. That's exactly where the difference to a Growth Kit lies: a Kit adds a focused function to an existing storefront, for example our B2C Growth Kit, while a Blueprint is the entire starting point for the storefront itself. Teams that already have a storefront base and want to add a specific function reach for a Kit. Teams building a new vertical or a new brand from the ground up start with a Blueprint.
Combining the two is explicitly supported: a fashion Blueprint delivers the storefront base, and an additional Growth Kit retrofits a specific conversion function afterward, such as personalization blocks from our Growth Kits overview article. Blueprint and Kit aren't mutually exclusive, they work together.
Before / With Laioutr
- Time to first working category page. Before (composable setup without Blueprint) : Weeks to months for component selection and content modeling; With Laioutr Blueprint : Live in days, components and content model already curated.
- Cost of vertical-specific setup decisions. Before (composable setup without Blueprint) : Repeated engineering effort per project, no starting template; With Laioutr Blueprint : Curated once, reusable across 60 verticals.
- Quality of the starting structure. Before (composable setup without Blueprint) : Generic component library with no vertical context; With Laioutr Blueprint : Vertical-typical structure from day one, fully customizable.
FAQ
Is an Industry Blueprint a finished theme I can launch unchanged?
No. A Blueprint delivers a vertical-typical structure of components, content model, and design tokens as a starting point. Brand imagery, your actual product data, and every brand-specific content decision remain your work, just like with any other composable setup, with far less upfront effort.
What's the difference between a Blueprint and a Growth Kit?
A Blueprint is the complete storefront base for a vertical, from category page to checkout. A Growth Kit is a focused component group for a specific use case that gets added to an existing storefront. Blueprints and Kits can be combined.
Can I change a Blueprint's content model after the fact?
Yes. A Blueprint's content model is a sensible starting point, not a fixed requirement. Additional product attributes, new category levels, or different filter logic can be extended through the Cockpit without rebuilding the Blueprint base from scratch.
Next Steps
If you're launching a new brand or a new market in one of the 60 covered verticals, a Blueprint saves you exactly the weeks that would otherwise go into component selection and content modeling. Take a look at how Laioutr's Composable Headless Frontend architecture brings Blueprints and Growth Kits together on the same component base.
More from the Laioutr Platform
About the Author
Marcel Thiesies is Co-Founder and CEO of Laioutr. He spends his days on the question of how frontend architecture can make marketing teams and engineering teams faster at the same time, without either side giving up control.