# Case study BluEmi s.r.o.
BluEmi s.r.o. is a small trading company specialising in the trading of measurement equipment in the field of radio communications, measurement of optical properties of radiation sources and materials, and also testing equipment for the automotive industry. It cooperates with domestic companies as well as with foreign partners in Europe, America and Asia. As time went on, the company became increasingly successful and it became very difficult to manage customer interaction effectively. Without a centralized system to completely manage interactions with customers or suppliers, the company had difficulty processing and evaluating information in a quality manner. These are necessary to properly approach the customer and track the complete business opportunity. BluEmi decided to address these issues by implementing a CRM solution.

### Problems to solve
Before implementing Collega, BluEmi faced several challenges:
- The management of customers, suppliers and their contacts was kept in several Excel files stored on a shared drive. These files grew quickly and were very difficult to work with.
- Nowhere was information about business opportunities, customer meetings and requirements kept. This information was traceable either in email or in the salesperson's personal notes. This caused frequent errors in subsequent offers and sometimes the sending of an offer was completely forgotten.
- Making offers and generally the whole process of a business case is a complex thing, especially if you are trading in multiple currencies. BluEmi had a predefined template in MS Office for all documents (quote, order confirmation, delivery note, etc.) and then copied the customer information or items sold into it. Creating a single document could take up to units of hours, which completely reduced the efficiency of the processes.
- The products offered by the contracted suppliers (as well as our own) were spread over various documents across the company, including their purchase and selling prices. This information was handled manually and all calculations (total price, discounts, VAT...) were calculated manually.
- The overall process of the business case required a lot of manual work and increased the time needed to process the task, which did not please the company management.

![case_study_problemy.png](https://datasession.cz/backend/uploads/case_study_problemy_c179bd71b8.png)

### Solution
After evaluating several options, the company chose the Collega system. Once the system was in place, all the problems mentioned above were solved. This solution allowed the company to largely automate the business case process and the problems were eliminated. The key points that led to this are:
- The creation of a central system to manage customer interactions. With Collega CRM, all customer interactions were recorded, making it easier for the team to manage requests and respond in a timely manner.
- Automating the process of opportunities, quotes and business cases led to big savings in time and money. Automatic document generation eliminated time-consuming manual work and allowed the team to focus on business issues.
- The product database and import saved a lot of time, money and reduced the overall error rate.

![pripadova_studie_result.png](https://datasession.cz/backend/uploads/pripadova_studie_vysledek_16203c80aa.png)

### Result
Since the implementation of Collega in early 2022, we can see a great impact on the functioning and efficiency of the entire company. Here are some numbers for 2022:
- The sales team was able to communicate with customers more effectively, which **improved average customer response time by over 50%** and reduced the number of forgotten opportunities to 0.
- Automated document generation combined with effective UX design accelerated the proposal and sales case process by **over 100% on average**.
- Compared to 2021, **sales increased by 22%**.
- Negative customer feedback due to incorrect information or poorly offered items has virtually disappeared.

### Conclusion
While using the system, BluEmi had excellent ideas that would have made their job easier and made our product even better. We are very grateful for such input and have implemented the new functionality in collaboration with them. We are always happy to hear feedback and requests for new functionalities or improvements and we are ready to discuss them personally with each of our customers.

Implementing Collega can help smaller and medium-sized companies like BluEmi to improve customer relationships, streamline sales processes and gain valuable insights into customer behaviour. With the right solution and effective implementation, companies can gain significant benefits from using the system.

### If you are interested in Collega, try it for free [at this link](https://icollega.cz).

pripadova_studie_Kreslicí plátno 1.png

Case study BluEmi s.r.o.

At the beginning of March we had enough of the gloomy weather and sitting behind the computer. So we got together as a group and went for a long weekend on a glacier in Austria. The goal of the trip was accomplished, the energy was replenished and we are back working on our projects in full force. 

Happy skiing! 🎿⛷🍻

IMG_4066.JPG

Na začátku března jsme už měli dost pochmurného počasí a sezení za počítačem. Tak jsme se jako celá parta sebrali a odjeli na prodloužený víkend na ledovec do Rakouska. Cíl výletu byl splněn, energie doplněna a v plné síle se zase můžeme věnovat našim projektům a klientům. 

Lyžování zdar! 🎿⛷🍻



Report z teambuildingu 2023

Report from teambuilding 2023

Customer Relationship Management (CRM) is a vital tool for any business that wants to build long-lasting relationships with its customers. By using CRM software, businesses can organize, automate, and synchronize sales, marketing, customer service, and technical support processes to better serve their customers and grow their business.

There are many benefits of using a CRM system, including increased sales productivity, improved customer satisfaction, and better customer retention. With a CRM, businesses can track customer interactions across multiple channels, gain valuable insights into customer behavior and preferences, and provide personalized experiences that build trust and loyalty.

One particular CRM that stands out in the market is Collega. Collega is a comprehensive CRM solution designed specifically for small and medium-sized businesses. With Collega, businesses can manage all aspects of their customer relationships, including sales, marketing, customer service, and support, from a single, centralized platform.

Collega offers a range of features that make it an excellent choice for businesses looking to streamline their CRM processes. These features include lead management, pipeline management, contact management, email marketing, social media integration, and reporting and analytics.

One of the unique advantages of Collega is its intuitive and user-friendly interface. The platform is easy to navigate and requires minimal training, making it a great option for businesses that want to get up and running with their CRM quickly.

Overall, Collega is an excellent choice for businesses that want to improve their customer relationships and grow their business. With its comprehensive feature set, intuitive interface, and affordable pricing, Collega is a top pick for businesses of all sizes.

Customer Relationship Management (CRM) is a vital tool for any business that wants to build long-lasting relationships with its customers. 

co-je-to-crm.png

What is CRM?

Requirements analysis is the process of gathering, documenting, and analyzing the requirements for a project or product. It is a crucial step in the software development process, as it helps to ensure that the final product will meet the needs of the end-users and stakeholders. In this blog post, we will discuss the importance of requirements analysis, the different methods used to gather and document requirements, and how to analyze and prioritize them.

The importance of requirements analysis cannot be overstated, as it is the foundation on which the entire project is built. Without a thorough understanding of the requirements, it is impossible to develop a product that meets the needs of the users and stakeholders. Requirements analysis also helps to identify any potential risks or issues that may arise during the development process, and allows teams to plan and budget accordingly.

There are several methods that can be used to gather and document requirements, including interviews, surveys, focus groups, and workshops. Each method has its own advantages and disadvantages, and the best approach will depend on the specific project and stakeholders. For example, interviews are useful for gathering detailed information from individual stakeholders, while workshops are ideal for brainstorming and collaboration.

![brainstorming.jpg](https://datasession.cz/backend/uploads/brainstorming_27a1ce90b8.jpg)

### Interviews
This method involves one-on-one conversations between a project team member and a stakeholder. Interviews are useful for gathering detailed information from individual stakeholders and can be conducted in person or over the phone.

### Surveys
Surveys are a useful tool for gathering requirements from a large group of stakeholders. They can be conducted online or in print and can be used to gather both quantitative and qualitative data.

### Focus Groups
A focus group is a moderated discussion with a small group of stakeholders. This method is useful for gathering requirements from a diverse group of stakeholders and can be used to gather both qualitative and quantitative data.

### Workshops
Workshops are a collaborative method of gathering requirements. They involve a group of stakeholders working together to identify and document requirements. Workshops can be used to gather both functional and non-functional requirements, and they are also useful for brainstorming and problem-solving.

### Prototype
A prototype is an early sample, model or release of a product, which can be used to gather feedback from stakeholders. They can be used to gather feedback on the design, usability and other user-experience related aspects of the product.

### Observation
Observation is a method where a team member observes stakeholders as they use a similar product or a competitors product. This method is useful for identifying pain points and areas for improvement in the product.

It's important to note that, these methods can be used alone or in combination, depending on the specific project and stakeholders. For instance, interviews can be used to gather detailed information from individual stakeholders, while workshops are ideal for brainstorming and collaboration. Surveys can be used to gather requirements from a large group of stakeholders, while prototypes can be used to gather feedback on the design and usability of a product.

![meeting.jpg](https://datasession.cz/backend/uploads/meeting_5f3c5a84c1.jpg)

Once the requirements have been gathered, it is important to analyze and prioritize them. This can be done by identifying which requirements are essential and which are nice-to-have. It's also important to consider the dependencies between different requirements and how they will impact the project. A weighting system can be used to prioritize the requirements, based on factors such as feasibility, importance, and urgency.

In conclusion, requirements analysis is a crucial step in the software development process. It helps to ensure that the final product meets the needs of the users and stakeholders, and allows teams to plan and budget accordingly. By using a combination of methods to gather and document requirements, analyzing and prioritizing them, and considering dependencies and impact on the project, teams can make sure that the final product is aligned with the stakeholders' needs and objectives

Requirement analysis is the process of gathering and documenting the needs, constraints and objectives of a project or system to ensure that it meets the needs of stakeholders.

kanban-board.jpg

Analýza požadavků je proces shromažďování potřeb a cílů projektu nebo produktu a jejich dokumentace. Jedná se o klíčový krok v procesu vývoje softwaru, protože pomáhá zajistit, aby výsledný produkt splňoval potřeby koncových uživatelů a zúčastněných stran. V tomto příspěvku na blogu se budeme zabývat významem analýzy požadavků, různými metodami používanými ke shromažďování a dokumentování požadavků a způsobem jejich analýzy a stanovení priorit.

Význam analýzy požadavků nelze přeceňovat, protože je základem, na kterém stojí celý projekt. Bez důkladného pochopení požadavků není možné vyvinout produkt, který by splňoval potřeby uživatelů a zúčastněných stran. Analýza požadavků také pomáhá identifikovat případná rizika nebo problémy, které mohou vzniknout během procesu vývoje, a umožňuje týmům odpovídajícím způsobem plánovat a sestavovat rozpočet.

Ke shromažďování a dokumentování požadavků lze použít několik metod, včetně rozhovorů, průzkumů, ohniskových skupin a workshopů. Každá metoda má své výhody a nevýhody a nejlepší přístup závisí na konkrétním projektu a zúčastněných stranách. Například rozhovory jsou užitečné pro shromažďování podrobných informací od jednotlivých zúčastněných stran, zatímco workshopy jsou ideální pro brainstorming a spolupráci.

![brainstorming.jpg](https://datasession.cz/backend/uploads/brainstorming_27a1ce90b8.jpg)

### Rozhovory
Tato metoda zahrnuje individuální rozhovory mezi členem projektového týmu a zúčastněnou stranou. Rozhovory jsou užitečné pro shromažďování podrobných informací od jednotlivých zúčastněných stran a mohou být vedeny osobně nebo telefonicky.

### Průzkumy
Průzkumy jsou užitečným nástrojem pro shromažďování požadavků od velké skupiny zúčastněných stran. Mohou být prováděny online nebo v tištěné podobě a lze je použít ke sběru kvantitativních i kvalitativních údajů.

### Focus Groups
Focus group je moderovaná diskuse s malou skupinou zúčastněných stran. Tato metoda je užitečná pro sběr požadavků od různorodé skupiny zúčastněných stran a lze ji použít ke sběru kvalitativních i kvantitativních údajů.

### Workshopy
Workshopy jsou metodou sběru požadavků založenou na spolupráci. Zahrnují skupinu zúčastněných stran, které společně pracují na identifikaci a dokumentaci požadavků. Workshopy lze použít ke shromažďování funkčních i nefunkčních požadavků a jsou také užitečné pro brainstorming a řešení problémů.

### Prototyp
Prototyp je raný vzorek, model nebo verze produktu, který lze použít ke shromáždění zpětné vazby od zúčastněných stran. Lze je použít ke shromáždění zpětné vazby k designu, použitelnosti a dalším aspektům produktu souvisejícím s uživatelskou zkušeností.

### Pozorování
Pozorování je metoda, při níž člen týmu pozoruje zúčastněné strany, jak používají podobný produkt nebo konkurenční produkt. Tato metoda je užitečná pro identifikaci bolestivých míst a oblastí, které je třeba v produktu zlepšit.

Je důležité poznamenat, že tyto metody lze použít samostatně nebo v kombinaci, v závislosti na konkrétním projektu a zúčastněných stranách. Například rozhovory lze použít ke shromáždění podrobných informací od jednotlivých zúčastněných stran, zatímco workshopy jsou ideální pro brainstorming a spolupráci. Průzkumy lze použít ke shromáždění požadavků od velké skupiny zúčastněných stran, zatímco prototypy lze použít ke shromáždění zpětné vazby k designu a použitelnosti produktu.

![meeting.jpg](https://datasession.cz/backend/uploads/meeting_5f3c5a84c1.jpg)

Po shromáždění požadavků je důležité je analyzovat a stanovit jejich priority. To lze provést tak, že se určí, které požadavky jsou zásadní a které jsou "nice-to-have". Důležité je také zvážit závislosti mezi jednotlivými požadavky a jejich dopad na projekt. Pro stanovení priorit požadavků lze použít systém vah na základě faktorů, jako je proveditelnost, důležitost a naléhavost.

Závěrem lze říci, že analýza požadavků je klíčovým krokem v procesu vývoje softwaru. Pomáhá zajistit, aby výsledný produkt splňoval potřeby uživatelů a zúčastněných stran, a umožňuje týmům odpovídajícím způsobem plánovat a sestavovat rozpočet. Kombinací metod shromažďování a dokumentování požadavků, jejich analýzou a stanovením priorit a zvážením závislostí a dopadu na projekt mohou týmy zajistit, že konečný produkt bude v souladu s potřebami a cíli zúčastněných stran.

Analýza požadavků je proces shromažďování a dokumentování potřeb, omezení a cílů projektu nebo systému s cílem zajistit, aby splňoval potřeby zákazníků.

Projects

Services

About

Blog

Contact