What a blueprint is
A blueprint is a packaged setup you install in one go — collections with their fields, stages, pipelines, automations and email templates, already wired together. Instead of assembling a working area of the CRM by hand, you install it, answer a couple of questions, and adapt from there. Installing is atomic and reversible, and conflicts with what you already have are checked first.
Requirements: a role that can create collections and automations in the business you are installing into.
Some setups are the same everywhere. A sales operation needs companies, contacts, and deals, with stages to move them through. An email campaign needs an audience, templates, and something that sends. You could build each of these by hand — create the collections, add the fields, define the stages, wire the automation — or you could install it already assembled. That is what a blueprint is: a packaged setup, installed in one step.
What is inside one
A blueprint is more than a set of empty tables. It carries the whole working arrangement: collections with their fields, the stages entries move through, the pipelines that organize those stages, automations that already do something useful, email templates where the setup sends mail, and the folders that keep it all tidy. The pieces arrive connected — references pointing where they should, stages attached to the right collection — which is the part that takes longest to get right by hand.
Installing is a conversation, not a dump
A blueprint asks a little before it builds. Some ask which variant you want — the CRM blueprint, for instance, can be provisioned as a B2B sales setup or as an e-commerce one with orders and products, and that choice shapes what you get. Others need to be pointed at something you already have, such as which mailbox to send from. Answer those and the blueprint has what it needs.
Before anything is created, the install is checked against your business for collisions — a collection with the same name, a template you already use. If something clashes you choose what to do with it, piece by piece: reuse what you already have, install the new one under a different name, or skip that piece entirely. Only then does it build, and it builds atomically — everything or nothing, never half a setup. If it turns out not to be what you wanted, an installation can be removed again, taking the pieces it created with it.
What is available
The catalog is small and deliberate rather than a marketplace of hundreds. Today it covers the CRM setup — companies, contacts, leads, and deals with their stages and pipelines, in a sales or an e-commerce shape — and email marketing, with audience collections, templates, and campaign automations with sending controls. The CRM blueprint is already installed for you when a business is created, which is why a new business is not an empty shell. Expect the catalog to grow; check it rather than assuming what is in it.
Yours to change afterwards
An installed blueprint is not a locked template. What it created behaves exactly like anything you built yourself: add fields, rename stages, adjust an automation, delete what you do not need. Treat a blueprint as a fast, sensible starting point rather than a contract — install it, then shape it to your operation the way you would any other collection.
Build or install?
A simple rule: install what is standard, build what is yours. If your need is a well-trodden shape — a sales pipeline, a campaign — installing saves you assembling something that already exists, and gives you a working example to learn from. If what you track is particular to your business, build it deliberately instead; a blueprint bent far out of shape is more work than a collection made for the job.
Where to go deeper
Blueprints assemble the same things you would otherwise build yourself, so it helps to know what they are made of: the data model, collections and fields, and agents and automations. Installing one, adapting it, and packaging your own have their own pages in this section.