Begin with the movement
Name where a person begins, which decision they face and which useful state should follow.
Current product edition · 2026
Bom Flow™
Bom Flow™ products and services
Choose the route depth from the movement, decision, route units, channels, evidence and ownership that must become intelligible.
02Bom Flow™
How to use this guide
Count route units and dependencies
Segments, channels, states, platforms, providers, exceptions and review gates determine product depth.
Confirm evidence and ownership
Every route ends with accepted states, owners, access, evidence, exceptions and a next review condition.
This guide is the commercial interpretation of Bom Flow™. The system publication remains the methodological definition. Open · Bom Flow™ ↗
03Bom Flow™
Contents
04Bom Flow™
Choose by the movement that must become intelligible
BN06
Recognise one bounded client path before implementation.
FLW-10
Make entry and choice intelligible for one client group.
FLW-20
Connect an accepted decision to action and onboarding.
FLW-30
Govern choice, transaction, confirmation and first use.
FLW-40
Connect the complete route across channels and relationship states.
FLW-50 / 51
Review or maintain an accepted flow through current evidence.
05Bom Flow™
Buyer-persona fit
Personas identify who carries the buying decision. Flow depth still follows the movement, authority, evidence and operating boundary.
P1
Decision, mandate, use or specialist context owner
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P2Decision, mandate, use or specialist context owner
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P3Primary route and client-experience owner
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P4Decision, mandate, use or specialist context owner
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P5Decision, mandate, use or specialist context owner
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P6Primary route and client-experience owner
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗P7Decision, mandate, use or specialist context owner
Open the exact persona definition and apply its risks, evidence needs and decision conditions.
↗06Bom Flow™
Touchpoint, readiness and evidence fit
Touchpoints locate the movement. Readiness and evidence overlays qualify whether route design can begin.
07Bom Flow™
System responsibility and product boundary
Bom Flow™
Owns movementRoute states, information order, decision moments, actions, transfers, exceptions, evidence points and next ownership.
Bom Blueprint™
Supplies governing recordsAccepted offer, decisions, roles, processes, sources, dependencies and change authority.
Bom Creation™
Supplies route materialsAccepted content, interface states, publications and production assets used by the route.
Bom Runtime™
Operates accepted routesOwners, cadence, access, tools, monitoring, incidents, updates and continuing quality.
08Bom Flow™
The governing definition of Bom Flow™
Bom Flow™ designs how value, information and decision context move from first contact through choice, action, transaction, first use and continued relationship.
Its agency result is a governed route architecture. Its organisational effect is shared understanding of what moves, who owns it, which evidence confirms completion and what happens next.
Open · complete system definition ↗09Bom Flow™
Four flow responsibilities
Entry
Connects audience situation, touchpoint and first useful information.
Choice
Connects information, offer, comparison, evidence and decision support.
Action
Connects an accepted decision to a form, conversation, proposal, checkout or commitment.
Transfer
Carries accepted context into onboarding, delivery, support, review and continued relationship.
10Bom Flow™
What a route unit means
A route unit is one named movement between two states. It is the governing unit for scope, responsibility, evidence and change.
Starting state and activating situation
Destination state and intended effect
Responsible person and decision authority
Admitted source, information or interface
Decision, action and completion evidence
Exception route and next owner
A page, message, form or system action becomes a route component when it performs a recorded movement.
11Bom Flow™
Product ladder
01
FLW-10
Entry and Choice Route
One client group needs a clear movement from first contact to an informed choice.
- Route units
- 1
- Channels
- 3
- Reviews
- 2
FLW-20
Action and Transfer Route
One accepted offer or service requires a clear movement from decision to action and onboarding.
- Route units
- 6
- Channels
- 1
- Reviews
- 3
FLW-30
Commerce and First-Use Flow
One product family needs a governed route through choice, checkout, payment, confirmation and first use.
- Route units
- 10
- Channels
- 1
- Reviews
- 4
FLW-40
Complete Customer Flow Architecture
One principal client segment requires a connected route from entry through relationship, return and referral.
- Route units
- 18
- Channels
- 4
- Reviews
- 5
FLW-50
Flow Review
An accepted flow reaches a review event or scheduled control point.
- Route units
- 18
- Channels
- 4
- Reviews
- 1
FLW-51
Flow Stewardship
An accepted flow requires a controlled monthly rhythm of evidence review and route change.
- Route units
- 18
- Channels
- 4
- Reviews
- 2
12Bom Flow™
How every price is constructed
Agency task ledger
Every task has a definition, responsible specialisation, agency hours, rate, subtotal and acceptance evidence.
Two reference constructions
Agency work uses 100 EUR per hour or 440 PLN per hour before visible product-level rounding.
External costs
Development, platforms, payment services, licences, legal review and specialist work receive separate accepted lines.
Scope change
A new segment, market, route, channel, platform, integration or service model triggers a new assessment.
13Bom Flow™
One delivery lifecycle
Qualify
Name the movement, decision, client group and smallest useful route boundary.
Admit
Confirm authority, sources, access, evidence, providers and constraints.
Design
Build route states, information, decisions, actions, transfers, exceptions and evidence points.
Review
Use consolidated gates to decide corrections across dependent units.
Transfer
Record owners, access, evidence, operation, review conditions and the next responsible route.
14Bom Flow™
Qualified architecture entries
Architecture entries answer a smaller decision before a governed flow is designed. Their accepted output can become a source for an FLW product.
15BN06
BN06 · Client Path Architecture
650 / 1,250 / 2,150 EUR2,900 / 5,500 / 9,500 PLNBasic · Medium · Max
- Activating situation
- One client group and one bounded path require a clear sequence, decisions, responsibilities and handover conditions.
- Included agency result
- A bounded path map with decisions, responsibilities, evidence and handover conditions according to the selected level.
- Next responsible route
- FLW-10 or FLW-20 when the path must become a governed operating flow.
16BN05
BN05 · Single-Page Information Route
950 / 1,650 / 2,750 EUR4,200 / 7,300 / 12,100 PLNBasic · Medium · Max
- Activating situation
- One existing page needs an information hierarchy led by one named user decision.
- Included agency result
- Page objective, user decision, section order, source, content requirements, production boundary and acceptance route.
- Next responsible route
- FLW-10 for the wider entry-and-choice route; Bom Creation™ for production.
17KT05
KT05 · architecture and Flow activation
3,400 EUR15,000 PLNarchitecture entry
- Included agency result
- One approved offer line, one website structure, content hierarchy, two Decision Cards and two execution briefs.
- Why this approach
- The accepted architecture becomes a source for production and route design without combining their responsibilities.
- Next responsible route
- FLW-10 or FLW-20 when the website and offer must operate as a connected route.
18FLW-10
FLW-10 · Entry and Choice Route
4,800 EUR · 21,100 PLN48 h · 12 to 15 business days- Activating situation
- One client group needs a clear movement from first contact to an informed choice.
- Scope
- One client group, up to three touchpoints, one decision route and two consolidated review gates.
- Included agency result
- Value-recognition map, entry map, information and offer sequence, decision criteria, route record and handover.
- Next responsible route
- FLW-20 when the choice must lead to action and onboarding; FLW-50 for review.
19FLW-10
FLW-10 · result, effect and acceptance
Included agency result
Value-recognition map, entry map, information and offer sequence, decision criteria, route record and handover.
Why this approach
A bounded route makes the first useful movement explicit before interfaces and materials multiply.
Organisational effect
A shared standard for entry, comparison and the next commercial movement.
Acceptance evidence
Every touchpoint, route state, decision criterion, source, owner and next movement has an accepted record.
20FLW-10
FLW-10 · task and price record
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate and decision boundaryConfirms client group, activating situation, decision, touchpoints, sources, owners and acceptance route. | Engagement architect | 3 | 300 | 1,320 |
| Source and evidence admissionAdmits current offer, identity, audience, content, interface and evidence sources and records conflicts. | Information architect | 5 | 500 | 2,200 |
| Value-recognition mappingDefines what the client group recognises as useful value and which evidence supports each hypothesis. | Customer-flow architect | 7 | 700 | 3,080 |
| Entry-point mappingMaps up to three touchpoints, their situations, first useful information and next movement. | Customer-flow architect | 7 | 700 | 3,080 |
| Information and choice architectureStructures information order, comparison criteria, proof and choice conditions for one route. | Information architect | 12 | 1,200 | 5,280 |
| Offer architecture in channelPlaces the accepted offer, boundaries, conditions and next action in the principal route context. | Commercial experience architect | 6 | 600 | 2,640 |
| Two consolidated review gatesCoordinates decisions and applies accepted corrections inside the route boundary. | Flow delivery lead | 5 | 500 | 2,200 |
| Route record and direct handoverRecords units, owners, sources, decisions, evidence, exceptions and the next review condition. | Documentation architect | 3 | 300 | 1,320 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | -20 |
| Fixed product price | 48 | 4,800 | 21,100 |
21FLW-20
FLW-20 · Action and Transfer Route
8,200 EUR · 36,100 PLN82 h · 4 to 5 weeks- Activating situation
- One accepted offer or service requires a clear movement from decision to action and onboarding.
- Scope
- One service, one principal channel, up to six route units and three consolidated review gates.
- Included agency result
- Decision moments, CTA and form logic, action sequence, transfer and onboarding path, route specification and handover.
- Next responsible route
- FLW-30 for transaction and first use; Bom Runtime™ for continuing ownership.
22FLW-20
FLW-20 · decision-to-onboarding sequence
Decision
Required information, evidence, authority and completion condition.
Action
CTA, form, conversation, proposal or commitment with validation.
Confirmation
Visible state, recorded evidence and the next responsible owner.
Transfer
Accepted context, scope, timing, access and exceptions move forward.
Onboarding
The first useful service movement begins with complete context.
23FLW-20
FLW-20 · task and price record I
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate and action mandateConfirms the service, channel, route units, intended action, sources, owners and access. | Engagement architect | 4 | 400 | 1,760 |
| Source, interface and constraint admissionAdmits offer, content, interface, process, legal and operating conditions and records conflicts. | Information architect | 6 | 600 | 2,640 |
| Decision-moment designDefines each decision, required information, evidence, authority and completion condition. | Customer-flow architect | 10 | 1,000 | 4,400 |
| CTA and form-routing logicDesigns calls to action, fields, validation, confirmations, alternatives and information requirements. | Interaction architect | 12 | 1,200 | 5,280 |
| Action and service sequenceConnects accepted choice to conversation, proposal, commitment or service action. | Customer-flow architect | 12 | 1,200 | 5,280 |
| Task subtotal | 44 | 4,400 | 19,360 |
24FLW-20
FLW-20 · task and price record II
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Transfer and onboarding pathCarries accepted context, responsibility, timing, evidence and exceptions into first service movement. | Service architect | 14 | 1,400 | 6,160 |
| Route prototype and implementation specificationExpresses states, content and interface requirements as a reviewable implementation specification. | Interaction architect | 8 | 800 | 3,520 |
| Three consolidated review gatesCoordinates decisions and applies accepted corrections inside the route boundary. | Flow delivery lead | 10 | 1,000 | 4,400 |
| Route register and direct handoverRecords units, owners, sources, access, evidence, exceptions, next route and review condition. | Documentation architect | 6 | 600 | 2,640 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | +20 |
| Task subtotal | 38 | 3,800 | 16,740 |
82 h · 8,200 EUR36,100 PLN
25FLW-30
FLW-30 · Commerce and First-Use Flow
14,600 EUR · 64,200 PLN146 h · 7 to 9 weeks- Activating situation
- One product family needs a governed route through choice, checkout, payment, confirmation and first use.
- Scope
- One product family, one commerce environment, up to ten route units and four review gates.
- Included agency result
- Offer and product route, checkout and payment logic, confirmation, exceptions, support and first-use architecture, implementation specification and governance record.
- Next responsible route
- FLW-40 for the complete relationship route; Bom Runtime™ for live operation.
26FLW-30
FLW-30 · commerce and first-use states
Choice
Product relation, comparison, evidence, conditions and price display.
Transaction
Basket, data, validation, payment, confirmation and recovery states.
First use
Fulfilment, onboarding, support and the first useful result.
Exceptions
Consent, failure, cancellation, return, support and escalation routes.
Platform development, payment-provider fees, licences and specialist legal or security review enter as separate accepted lines.
27FLW-30
FLW-30 · task and price record I
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate and commerce mandateConfirms product family, environment, route units, owners, providers, access and acceptance. | Engagement architect | 5 | 500 | 2,200 |
| Source, platform and commercial admissionAdmits offer, product, content, platform, payment, legal and service conditions and records conflicts. | Information architect | 10 | 1,000 | 4,400 |
| Value and entry architectureDefines recognised value, entry situations, touchpoints, first useful information and route hypotheses. | Customer-flow architect | 12 | 1,200 | 5,280 |
| Offer and product-choice architectureStructures product relationships, comparison, evidence, conditions, price display and choice sequence. | Commercial experience architect | 20 | 2,000 | 8,800 |
| Decision-moment designDefines information, evidence, authority and completion at every material decision. | Customer-flow architect | 14 | 1,400 | 6,160 |
| Checkout and payment flowDesigns basket, data, validation, payment, confirmation, failure and recovery states. | Interaction architect | 24 | 2,400 | 10,560 |
| Task subtotal | 85 | 8,500 | 37,400 |
28FLW-30
FLW-30 · task and price record II
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Post-purchase and first-use pathCarries order context into confirmation, fulfilment, support, onboarding and first useful use. | Service architect | 20 | 2,000 | 8,800 |
| Exception, consent and support routesDefines material exception, consent, cancellation, return, support and escalation paths. | Service architect | 14 | 1,400 | 6,160 |
| Route prototype and implementation specificationExpresses route states, content, interfaces, data, triggers and dependencies for implementation. | Interaction architect | 12 | 1,200 | 5,280 |
| Four consolidated review gatesCoordinates decisions and applies accepted corrections across the commerce route. | Flow delivery lead | 9 | 900 | 3,960 |
| Governance register and direct handoverRecords owners, providers, access, evidence, exceptions, measurement points and review conditions. | Documentation architect | 6 | 600 | 2,640 |
| Explicit Poland-market rounding | Commercial decision owner | 0 | 0 | -40 |
| Task subtotal | 61 | 6,100 | 26,800 |
146 h · 14,600 EUR64,200 PLN
29FLW-40
FLW-40 · Complete Customer Flow Architecture
22,000 EUR · 96,800 PLN220 h · 10 to 14 weeks- Activating situation
- One principal client segment requires a connected route from entry through relationship, return and referral.
- Scope
- One principal segment, up to four channels, up to eighteen route units and five review gates.
- Included agency result
- Complete customer-flow architecture, route specifications, exception paths, measurement framework, governance and ownership transfer.
- Next responsible route
- FLW-50 for event-led review; FLW-51 and Bom Runtime™ for continuing operation.
30FLW-40
FLW-40 · governance and organisational effect
Included agency result
Complete customer-flow architecture, route specifications, exception paths, measurement framework, governance and ownership transfer.
Why this approach
The organisation receives one governed model for how client context moves across commercial and service work.
Organisational effect
Coordinated entry, choice, action, transaction, onboarding, service, support, return and referral.
Acceptance evidence
The complete route register, specifications, owners, access, evidence, exception and review records are accepted.
The measurement framework names observable events and evidence sources. Commercial or service performance enters the evidence record only after current measurements exist.
31FLW-40
FLW-40 · task and price record I
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Start Gate and programme mandateConfirms segment, channels, units, markets, sources, owners, providers, access and acceptance. | Engagement architect | 6 | 600 | 2,640 |
| Source, evidence and constraint admissionAdmits business, offer, identity, audience, content, interface, service, platform and evidence sources. | Information architect | 12 | 1,200 | 5,280 |
| Value and audience architectureDefines recognised value, situations, roles, decisions, evidence needs and route hypotheses. | Customer-flow architect | 18 | 1,800 | 7,920 |
| Entry network architectureMaps entry conditions and next movements across up to four accepted channels. | Customer-flow architect | 20 | 2,000 | 8,800 |
| Information, offer and choice architectureStructures information, offer, comparison, evidence and choice across the accepted route. | Commercial experience architect | 28 | 2,800 | 12,320 |
| Decision and action orchestrationConnects decisions to conversations, forms, proposals, commitment or transaction through named units. | Customer-flow architect | 28 | 2,800 | 12,320 |
| Task subtotal | 112 | 11,200 | 49,280 |
32FLW-40
FLW-40 · task and price record II
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Transaction, service and onboarding architectureCarries accepted context through transaction, confirmation, onboarding, service and first useful result. | Service architect | 30 | 3,000 | 13,200 |
| Post-purchase, return and referral architectureDefines support, review, continued contact, return and referral routes with owners and evidence. | Service architect | 22 | 2,200 | 9,680 |
| Route prototypes and implementation specificationExpresses states, content, interfaces, data, triggers, dependencies and exceptions for implementation. | Interaction architect | 20 | 2,000 | 8,800 |
| Measurement and route governanceDefines observable events, evidence sources, owners, review thresholds and controlled change routes. | Measurement architect | 14 | 1,400 | 6,160 |
| Five consolidated review gatesCoordinates decisions and applies accepted corrections across dependent route units. | Flow delivery lead | 14 | 1,400 | 6,160 |
| Governance register, owner enablement and handoverRecords units, owners, sources, access, evidence, operation, exceptions and review conditions. | Documentation architect | 8 | 800 | 3,520 |
| Task subtotal | 108 | 10,800 | 47,520 |
220 h · 22,000 EUR96,800 PLN
33FLW-50
FLW-50 · Flow Review
3,000 EUR · 13,200 PLN30 h · 7 business days- Activating situation
- An accepted flow reaches a review event or scheduled control point.
- Scope
- Up to eighteen route units, current evidence and up to six correction decisions.
- Included agency result
- Review register, correction decisions, dependencies, owners, next action and review date.
- Next responsible route
- A correction scope, FLW-51 or the next recorded review.
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Review Gate and route boundaryConfirms trigger, baseline, route units, owners, evidence and correction route. | Engagement architect | 2 | 200 | 880 |
| Current source and evidence admissionAdmits current route, content, interface, data, operating and evidence records. | Information architect | 4 | 400 | 1,760 |
| Route and state reviewChecks up to eighteen units against accepted function, source, decision, ownership and evidence conditions. | Customer-flow architect | 10 | 1,000 | 4,400 |
| Up to six correction decisionsRecords finding, consequence, priority, owner, correction boundary and acceptance evidence. | Customer-flow architect | 6 | 600 | 2,640 |
| One consolidated review gateCoordinates decisions and their effect across dependent route units. | Flow delivery lead | 5 | 500 | 2,200 |
| Review handoverRecords next action, owner, review date, evidence requirement and implementation route. | Documentation architect | 3 | 300 | 1,320 |
| Fixed product price | 30 | 3,000 | 13,200 |
34FLW-51
FLW-51 · Flow Stewardship
2,000 EUR · 8,800 PLN / month20 h · monthly cycle- Activating situation
- An accepted flow requires a controlled monthly rhythm of evidence review and route change.
- Scope
- Twenty agency hours, accepted backlog, route updates, evidence control and two review gates.
- Included agency result
- Current route register, approved updates, evidence record, review decisions and month-close handover.
- Next responsible route
- The next monthly cycle or a separately accepted expansion.
| TaskWhat the task does | Responsible specialisation | Hours | EUR | PLN · Poland |
|---|---|---|---|---|
| Monthly Start Gate and route backlogConfirms backlog, affected units, owners, sources, evidence, access, capacity and acceptance. | Engagement architect | 3 | 300 | 1,320 |
| Route monitoring and evidence reviewReviews accepted events, evidence, incidents, feedback and dependencies inside the monthly boundary. | Measurement architect | 5 | 500 | 2,200 |
| Approved route updatesApplies accepted changes to units, decisions, information, interfaces or transfer records. | Customer-flow architect | 6 | 600 | 2,640 |
| Two consolidated review gatesCoordinates decisions and accepted corrections across the monthly backlog. | Flow delivery lead | 3 | 300 | 1,320 |
| Month close and handoverRecords current state, evidence, owners, dependencies, next backlog and review condition. | Documentation architect | 3 | 300 | 1,320 |
| Fixed product price | 20 | 2,000 | 8,800 |
35Bom Flow™
Common flow configurations
Segments, route units, channels, platforms, providers, sources, exceptions and reviews determine the product depth for every configuration.
Service enquiry and onboarding
Entry, qualification, brief, proposal, commitment, confirmation, onboarding and first service movement.
Product purchase and first use
Product choice, basket, payment, confirmation, fulfilment, support and first useful result.
Information and offer route
Entry source, information order, evidence, comparison, conditions, price and next commercial movement.
Relationship and return route
Support, review, continued contact, return, referral, ownership and evidence cadence.
36Bom Flow™
Applied project evidence
01
Bom Dia Creation™
Connected documentation, offer, publication, client-library and operating routes across the current ecosystem.
↗02HugMe
Brand, product, repository and editorial routes with element-level evidence boundaries.
↗03POLVALVE
Review, correction and material-transfer routes around technical product information.
↗04JednoWino
Catalogue, product-choice, print, exclusion, error and publication-stage routes with partial live-operation evidence.
↗Evidence supports the recorded route mechanisms and produced specifications. Conversion, revenue, adoption, retention, referral and service performance require current measurements for the relevant route.
37Bom Flow™
Transfers to the system family
Bom Perspective™
Supplies accepted audience context, tensions, choices and evidence needs.
Bom Identity™
Supplies meaning, promise, relationship principles and language.
Bom Blueprint™
Supplies the governing offer, decision, process, role, source and dependency records.
Bom Creation™
Supplies accepted content, interfaces and materials used by route units.
Bom Runtime™
Assigns ongoing ownership, cadence, monitoring, access and update responsibility.
38Bom Flow™
Code, source and destination index
Commercial products
BN06Open definition↗BN05Open definition↗KT05Open definition↗FLW-10Open definition↗FLW-20Open definition↗FLW-30Open definition↗FLW-40Open definition↗FLW-50Open definition↗FLW-51Open definition↗System functions and sources
FLW-01Open governing context↗FLW-02Open governing context↗FLW-03Open governing context↗FLW-04Open governing context↗BLP-03Open governing context↗BLP-04Open governing context↗BLP-05Open governing context↗BLP-06Open governing context↗PRCOpen governing context↗39Bom Flow™
Responsibilities, access, data, timing and acceptance
Client responsibility
Provide authorised sources, decision and acceptance owners, platform and provider access, consolidated feedback and decisions within the agreed calendar.
Agency responsibility
Perform accepted tasks, record sources and decisions, coordinate named work, protect route quality and supply acceptance evidence.
Access, data and third parties
The proposal and agreement record access authority, data conditions, platform roles, provider terms, rights and specialist-review requirements.
Timing and acceptance
Time begins after the complete Start Gate. Late sources or decisions, accepted changes and provider dependencies update the recorded schedule.
The accepted proposal and agreement establish transaction-specific scope, price, tax, timetable, rights, access, data, payment, responsibility and acceptance.
Bom Flow™
Take the next commercial decision
Name the movement and intended state. Confirm the source, authority, evidence and access gate. Count segments, route units, channels, platforms and exceptions. Choose the smallest flow product that can deliver an accepted and owned route.