The architecture by which the company operates.
Bom Blueprint™ organises knowledge, decisions, dependencies and work cadence around the market, brand foundations, business model, operations, marketing and growth.
Six segments and more than sixty chapters record decisions, owners, dependencies and sources of truth in one business-architecture environment.
Four layers that keep the architecture in motion.
The system creates a working foundation used by decision-makers, teams, partners, contractors and AI tools. Decisions receive a status, owner, repository location, links to other areas and a path for further use.
The substantive layer
The six segments take you through the market, brand foundations, business model, operations, marketing and development. Each segment is responsible for a specific area of decisions and data.
Documentation layer
Repository, Index, statuses, SOT, registers, transfers, readiness, briefs and archive give the work a form that can be directed, handed over and updated.
Rhythm layer
The annual rhythm distributes studies and transfers over months and quarters. The system works on the appropriate chapters when they are needed for the client's activities.
Learning layer
The learning loop returns data from activities to the appropriate places in the architecture. Results, signals and observations update subsequent decisions and transfers.
Artefacts that continue to work.
Strategic artefacts
approved segment decisions, decision cards, conclusions, directions, dependency maps, Wardley maps, recommendations and priorities
Documentary artefacts
SOT, Index, Decision Register, Transfer Register, readiness boards, syntheses, archive and repository with a governance layer
Performance artefacts
transfers, briefs, checklists, HTML dashboard, materials for the team, partners, communication, sales, operations and AI
Rhythm artefacts
annual agenda, review cycles, update points, learning loop and data return map to the system
Six segments, more than sixty chapters.
Governance
The governance layer works on the structure of segments: Master Index of the entire environment, standard for naming artefacts, status register and rules for converting material from draft to source. Index, together with the governance layer, serves as an architecture repository: one place where the entire organisation finds applicable sources, decisions, connections and standards.
Market Analysis
Creates the LOGOS layer of the system. It provides data about the industry, competition, customers, demand, trends, regulations and indicators that influence decisions in subsequent segments.
Brand foundations
They describe the brand's identity, ethos, language, experience and standard of decision-making. The segment combines the ETHOS, PATHOS and LOGOS dimensions.
Business Model
It defines how value is created, delivered, monetized and developed. A segment combines offerings, customers, channels, revenues, costs, resources and partnerships.
Operations
It describes how the model is intended to work in practice. It connects roles, processes, work rhythm, resources, standards, technologies, KPIs and risks.
Marketing
Translates brand, business model, segmentation and sales goals into communications, content, channels, campaigns and measurement.
Development
It guides the directions of growth, scaling, investments, partnerships, technology, risks and monitoring.
The sequence of work follows the client's situation. Segment numbering organises the map, while the annual cadence and process configuration establish the working sequence.
From source to update.
Bom Blueprint™ guides work through a sequence of sources, development, decisions, approvals, transfers, use, updates and analysis. The learning loop closes one cycle and opens the next.
Collecting input materials, data, interviews, documents, results and observations.
Material assigned to a segment
Analysis and draft editing of a specific chapter or area.
Draft ready for review
Reading, comments, revisions and decisions by Bom Dia Creation™ and the client.
Arrangements ready for approval
Record of the decision with the DEC code, source and consequences.
Decision in the register
Closing the current version of knowledge for the area.
Active basis of work
Transferring data, decisions or conclusions to the next area.
Transfer package with TR code
Assessment of the readiness of the material for further use.
Readiness status and condition list
Use of material in team work, briefing, communications, operations, sales or analysis.
Work launched on approved architecture
Results, observations, tensions, changes, new data and signals from action.
Material for learning loops
Returning data to the correct segment, decision, transfer or checklist.
The system learns by using
Assessment of what the change brought: which decisions were confirmed, which ones require correction and what the consequences are for the overall architecture.
Requests assigned to segments
Closing the cycle and opening the next one. Conclusions return to sources, studies and decisions to the extent resulting from the intention and need of the task.
An ending is a new beginning
Status, version, owner, dependency.
This layer allows you to separate input material from development, development from decision, decision from approved source, approved source from transfer, transfer from brief, and active version from archive.
Click a segment or transfer type to see its connections. Click on a card to trace its dependencies and read what exactly it conveys.
Registers and documentation standard
Each thesis file is described by a uniform convention: status in square brackets, substantive name and date. Example: [draft] Offer structure and pricing strategy [2026-05-08].
The basic unit of work in the register is the decision card: a proprietary artefact describing the full cycle of decisions in twenty-five fields. After completing the full architecture, the client has a catalogue of several dozen to several hundred cards, which is a living record of the choices that define the company.
The architecture works to an annual cadence.
Each card is assigned a return cycle based on how quickly that area changes in a typical organisation.
The order in which the segments are developed results from the rhythm of the business year and the dependencies between the segments. January starts with communication strategy because you need to know why you collect data before you start collecting it. Segment 1.0 Market Analysis is revised throughout the year; market monitoring is carried out continuously.
It results from the assigned rhythm. You open the worksheet with the VERIFY CONSISTENCY or REVIEW action, assess whether the decision is valid and close the session with confirmation or update.
Initiated by a change in the organisation or in the market that requires a fresh decision. It comes when you need it, at any point in the year.
Delivery tests the assumptions.
The learning loop brings knowledge from activities back to the architecture. Data from campaigns, sales, conversations, implementations and operational work can update decisions, language, scopes, processes and subsequent recommendations.
The basemap below has 181 documented connections, 25 of which are reverse transfers. In the full client architecture, the number of connections increases to approximately 297 and return transfers to 46, i.e. every sixth connection leads knowledge back to previous decisions.
Full annual rhythm and return-transfer examples
Operations verify the model
Actual operating costs, channel conversion, segment profitability and resource efficiency update the business model. In the cards written as: data against assumptions.
Development returns to foundations
The results of the growth cycle update the business model, review the consistency of brand foundations, and initiate a new round of market analysis.
Market reaction goes back to definition
Communication and sales results verify the accuracy of the value proposition, brand language and analysis priorities.
Implementation corrects the definition
Operating results and customer feedback show whether the defined experience standard is achievable and whether the value proposition is being delivered as promised.
Closing a cycle opens another one
Three return transfers to segments 1.0, 2.0 and 3.0 close the first pass through the architecture and open another one with richer context.
Context infrastructure for AI.
Management standards describe how to run an AI system in an organisation. Regulations specify the legal requirements for its use. Bom Blueprint™ describes what this system is about: providing approved identity, decisions, constraints and dependencies. AI works within system chapters, in an approved context, under human control.
Standards and methodological grounding
Article 50 of the EU AI Act sets transparency obligations for specified uses of AI. Their scope depends on the type of system, its use and the role of the provider or deployer. Dates and exceptions should be checked against the current legislation. Wyjaśnienia Komisji Europejskiej ↗︎
The system works on proven methods of business architecture, analysis and quality management, and combines them with proprietary mechanics of decisions, transfers and rhythm.
The price depends on the level of responsibility.
The investment reflects the number of segments, the level of direction, Bom Dia Creation™’s responsibility, the working cadence, repository, transfers, AI readiness and the scope of decisions. The pricing structure clarifies the scope conversation: it shows whether the work calls for one segment, guided entry into a system, a full architecture, an annual review or a GTM extension.
Each scope has a lower and upper threshold. The final price depends on the scale of the company, the maturity of the materials, the number of decision-makers and the scope of work.
The range describes the Polish market. Projects on European and global markets, including multilingual ones and those subject to compliance requirements, work at separate thresholds.
Combining Bom Blueprint™ with another system in the Bom™ environment uses package pricing, discounted against the sum of the individual scopes.
Preparation for ISO audits and compliance with the EU AI Act are separate scope items, selected to suit the client's regulatory situation.
An annual review and a constant rhythm of collaboration constitute a continuation of the system and architecture development, carried out after the implementation.
All ranges are expressed in EUR net. The contract includes a provision for expanding the scope during work.
What influences the price: number of segments, quality of input materials, number of decision-makers, scope of analysis, number of transfers, Index level, work on SOT, AI ready, approval rhythm and responsibility for coordination.
Configuration establishes the entry conditions: scope of work, materials, decision-makers, repository, Index, cadence, review gates and the initial pricing logic.
Six systems. Two layers. One architecture.
Each system has equal importance, its own moment of use and its own product family. The definition layer designs the decisions, the execution layer puts them into reality. Blueprint belongs to the definition layer and combines segments into one dependency map.
recognition of the situation, calibration of the entry point, decision on the appropriate path of collaboration
recommends the scope and feeds segment 1.0 with market data and hypotheses
brand foundations, positioning, language, personality, identity and communication standard
builds 2.0 and 3.0 segments on which the entire architecture works
business architecture: offer model, operations, marketing, development, source of truth and system readiness
combines all segments into one dependency map
identification, website, decks, campaigns and materials ready for real use
works on foundations from 2.0 and communication from 5.0
the path from the value of the offer to customer decisions, service and relationships
develops processes and data of the 4.0 segment in sales and e-commerce
standards, responsibilities, quality rhythm, knowledge and readiness to work with AI
runs segment 6.0, annual rhythm and time-return transfers
It is not a system. This is a format for continuing the relationship after implementation: reviews, updates, quality rhythm and further architecture development.
Architecture that grows with the company.
Each completed scope opens up further opportunities to work while maintaining continuity of data, decisions and standards.
Start
The first step is the scope adapted to the client's stage: a single segment, guided entry into the system or a full architecture. The entry point is indicated by the Bom Entry Map™.
Extension
The completed segment feeds subsequent areas through transfers. The client extends the architecture with subsequent segments in the order resulting from decisions, seasonality and business priorities.
Rhythm
After implementation, the system works on an annual basis: the Annual Blueprint Review updates decisions and transfers, and constant collaboration in the Bom Rewards™ formula keeps the architecture in motion.
Directions
The architecture opens up work with the remaining core systems: recognition in Bom Perspective™, identity and language in Bom Identity™, and execution in Bom Creation™.
Architecture feeds the next system.
Bom Creation™
Materialisation of recorded decisions in the identity, website, presentations and campaigns.
↗︎Bom Flow™
Value movement design: customer decision path, inquiry flow and performance measures.
↗︎Bom Runtime™
A cadence of reviews and a standard of work that maintains the architecture in line with the state of the company.
↗︎Bom Identity™
Closing the core of the brand when the architecture reveals a lack of written value or position.
↗︎Bom Perspective™
Market research before deciding on the next segment or new direction.
↗︎Selection of the scope to the stage of the current architecture.
The entry point is indicated by the Bom Entry Map™. The first conversation serves to recognise the situation and choose a proportional move.
Getting into architecture starts with recognising the situation and determining the proportional scope of the first move.