The core of BRAND_OS is BRAND_OS CORE. This is where the brand's criteria are structured: the decisions already in place, the rules that need to be maintained, the available resources and the correct way to apply them. Tools change, and so do AI models, very quickly. The value lies in having those criteria defined, organised and ready to be used with those technologies and in the day-to-day work of the company.

No. First, we look at where your brand is now and what it needs. If the visual direction hasn't been defined yet, we start with Territories: three different routes to compare and choose between before building the identity (€350). If there is already a clear identity, we start with a System Setup: we keep what works and only build what's missing. Both routes lead to a complete Identity Setup, with BRAND_OS CORE and the AI chat ready to use. If we start with Territories, the Identity Setup has a maximum price of €1,500, in addition to the initial €350. With a System Setup, the price is lower depending on how much of the work is already in place. After that, you can expand the system with the modules you need.

Traditional brand guidelines document decisions. BRAND_OS starts from the same criteria, but is designed to put them to use: it connects rules, files, resources and tools so that every team can work with the brand. The difference is moving from consulting documentation to working with a system.

A tool can help you design, write or produce a piece of content. BRAND_OS works one level earlier: it defines the criteria those decisions should be based on, what belongs to the brand, which resources can be used and which rules need to be maintained. It doesn't replace your team's tools. It gives them a common foundation to work from

No. BRAND_OS is designed to work alongside them. Part of the system can live in Notion, another part in Figma, other applications can use Creative Cloud resources, and certain modules can connect to production or AI tools. BRAND_OS organises the system and decides where each element should live so that it is genuinely usable, without forcing the team to learn and maintain another platform.

Yes. BRAND_OS CORE is delivered through tools such as Notion or Figma, and you can duplicate it into your own workspace at any time. It's yours from day one and remains yours, whether you work with me or with someone else. Your brand knowledge isn't tied to a single tool or provider.

No. BRAND_OS CORE works independently of the AI layer. You can consult the documentation, access resources, use the files and work with the system without using the chat. AI is simply an additional way to access your brand knowledge and work with it more efficiently.

No. The main value of BRAND_OS doesn't depend on maintaining an AI subscription. You only pay when you use it. And if you prefer not to use it, all your brand knowledge remains available in BRAND_OS CORE, with no associated usage costs.

Each company's information is kept separate within its own workspace, and conversations are stored in encrypted form. When you use AI features, BRAND_OS works through paid APIs that do not use your content to train their models. Providers may temporarily retain certain data for security and abuse-prevention purposes, in accordance with their own retention policies.

Yes. Many internal requests don't need a new creative decision: they need to know which version is approved, where the right file is or what criteria a piece should follow. When that knowledge is structured in BRAND_OS CORE, the team gains autonomy and design can spend its time on the problems that genuinely require design.

No. BRAND_OS can be used by design, marketing, product, development, sales, leadership... Each team can access the rules and resources it needs through the tools it already works with, while everyone works from the same brand criteria.

Yes. The BRAND_OS chat responds in the language it's asked in, so different teams, collaborators or markets can consult the same criteria without duplicating the documentation.

The system is updated. A brand adds new products, channels, teams, technologies and needs over time. BRAND_OS is modular by design, so new decisions, resources or applications can be added without having to rebuild all the documentation every time.