Map of the recipient’s needs
We collect questions with which the client comes to the website: what the service concerns, for whom it is intended and how to start cooperation.
Offer / BXM Multimedia
Architecture and content of the website First order, then design.
We plan the structure of the company website: service subpages, navigation and content needed by the client before contact.
Let’s discuss your projectArchitecture and content of the websiteIdea → project → implementation
Customised to your company
What can we prepare?
A separate page or a fragment of the offer?
The new sub-page makes sense when it responds to a separate need and can present its own scope, examples and conditions.
Materials ready for design
The result of the work is a website map, content distribution and a list of missing materials.
Service Guide
How to organize content so that the customer finds the right service
The architecture of the content combines the company's offer with the language and needs of its customers. It includes the distribution of topics, website hierarchy, navigation and links between materials.
Inventory: what we already have and what we lack
We collect existing addresses, texts, realizations, documents and questions that come back in conversations with our customers. Each material is assessed for the actuality, relevance and role in the selection process. This way, we know what to keep, what to complete, and which pages to connect.
In a company offering several services, the problem is a common description, which shows no differences between them. Other times, separate pages repeat the same introduction and none answer specific questions. The result of inventory is a list of editorial decisions, not automatic removal of everything that has little movement. Short instructions for current customers can also perform an important function.
Expand Subject:
A separate subpage only if it has its own task
The division of the offer should result from differences in needs, scope and way of implementation. If two variants can be compared fairly in one text, they do not always need two addresses. If they require other materials, examples and processes, separate subpages help the user.
We also distinguish the aggregate and detailed page. The first order of opportunity and leads to the right solution. The second describes the service thoroughly enough to evaluate the match and prepare the query. In the guide we explain the problem, and in the implementation we show the application. We do not try to make each page answer all questions simultaneously.
Expand Subject:
Menu, page path and links in context
In the menu we place understandable names without knowing the company's structure. Short labels are intended to help you choose, not to present internal department names. With a more extensive offer you need a clear path back to the category and the possibility of moving to the related service.
The link in the text should announce what is on the other side. The link “how to prepare materials for the store” says more than a few repeated “read more”. We do not connect each page with each page. We select moments where another material answers the question arising during reading, e.g. the transition from shop design to the integration of payments and systems.
Content model must be supported in CMS
We design not only the finished view, but also the way in which the data is entered. The implementation may need separate fields for industry, scope and photos, and service for variants, stages and questions. Fields should reduce accidental errors and facilitate the re-use of information.
It is important to distinguish between content and appearance. The editor should be able to change the description or add an example without building from the beginning of the whole layout. We determine who can publish, which requires approval and how to update common contact details. A good structure reduces the number of places where the same information needs to be corrected manually.
Expand Subject:
How do we check if the structure works?
We go through scenarios, such as finding the right service, comparing two options and sending a query. We also check them on the phone, where the extended menu and long names reveal problems more quickly. It is worth inviting a person who did not participate in the design of the website to this attempt.
After running, we analyze page entries, use search engines and repeated questions. No contacts from an important area may result from unclear name, poor description or difficult form. The structure is developed on the basis of these signals. When changing addresses, we maintain a redirect map and update links to avoid losing previous paths.
Expand Subject:
Good start.
From Chatting
to a particular plan.
We set the goal, scope and way of receiving the work. We develop the project on the basis of agreed needs and materials.
See our realizationsWhat is worth preparing for the conversation?
- Address of the current page and description of needs
- Materials and decision-makers
- Priorities, limitations and planned deadline
You don't have to have the specifications in place, and we'll work out the most important decisions together.
Before the first conversation
It's worth knowing.
Do you have to write all the texts right away?
In the beginning, you need enough scope and most important information. Before approving the layout, it is worth having representative content for each type of page to check their length and readability.
Your next step
Let’s talk about your project.
Tell us what your company needs. We operate all over Poland.
Let's start with your idea.
Write a few sentences about the project or call me.