Case Study

Does the takeover of an app by another software house have to be painfulunderline?

Are you in a situation where your current software development team doesn't meet your requirements? Wondering how to get out of this? If so, keep reading...

Case study
Natalia Migdal
Marketing Specialist

Imagine you've hired a software company to bring your brilliant app idea to life. You've had numerous meetings, consulted with experts, and embarked on the development journey with high hopes. It all seems like smooth sailing from here, but as many have experienced, the path to a successful software project can be fraught with challenges. These challenges range from inaccurate estimations and communication gaps to missed deadlines and Much More!

Now, you might be wondering: "What can be done in such a situation? Is there an easy way out?". The answer is a resounding: "Yes!". While the journey may have its twists and turns, your dream of creating an amazing app is still very much attainable. The key lies in seeking help from experts who have navigated these waters before.

Drawing from the experiences of our client, we are here to share that the process of taking over an app from another software house doesn't have to be painful; in fact, it can be quite enjoyable!

Beginnings of collaboration with Zielone Pogotowie

In December 2022, we started a collaboration with Zielone Pogotowie, a company renowned for its diverse range of goods and services catering to the world of gardens. Their expertise primarily revolved around crafting gardens and outdoor spaces. But that's not all! In 2014, they ventured into the world of digital content by launching a YouTube channel dedicated to gardening enthusiasts. Following this success, they introduced the mobile app - Plantis, which has become arguably the most prominent of its kind in Poland. Garnering over 100,000 downloads on Google Play and amassing an impressive YouTube following of more than 440,000 subscribers, Zielone Pogotowie has firmly established itself as a leader in the gardening community.

Unfortunately, the app didn't initially perform as expected. Moreover, the owners didn't have a positive experience with their previous software houses. Before approaching us, they had collaborated with two other companies in the past. So, what went wrong in those cases, and how did we address these issues?

The difficulties of taking over an app and how MuchMore handled them

MuchMore Software House became the third development team to work on Zielone Pogotowie since its inception. Cooperation with the previous two teams had its challenges, including:

  1. Inaccurate Estimations: One of the significant issues Zielone Pogotowie faced was receiving inaccurate estimations from the previous software houses. These estimations pertained to the number of hours required for specific features or tasks. However, the actual development often took much longer than originally projected, resulting in budget overruns.

How We Handled It: We addressed this challenge by providing accurate and realistic time estimations for each feature. Our transparent approach helped Zielone Pogotowie in budget planning and ensured that they did not encounter financial surprises along the way.

  1. Missed Deadlines: Another frustrating problem Zielone Pogotowie encountered was the failure to meet project deadlines by the previous software houses. This not only delayed the project's progress but also affected their time-to-market.

How We Handled It: To mitigate this issue, we implemented a robust project management approach, which included weekly sprints and regular progress monitoring. This allowed us to keep the project on track and ensured that deadlines were met consistently.

  1. Lack of Technical Documentation: Perhaps one of the most significant challenges was the absence of technical documentation for the project. This lack of documentation made it difficult to understand the existing codebase and architecture.

How We Handled It: We overcame this challenge by conducting a thorough code audit and analysis. Our team invested the necessary time to comprehend the existing code, allowing us to continue development seamlessly.

  1. Third Development Team: Zielone Pogotowie had already engaged with two previous software houses before our collaboration. These prior partnerships hadn't yielded optimal results, leading to concerns about engaging with yet another development team.

How We Handled It: We instilled confidence in Zielone Pogotowie by demonstrating our commitment to the project's success. Through transparent communication and consistent results, we were able to assure them that our collaboration would be different and more productive.

Phases of project implementation

Step 1 - Verification and Assessment

The first step from the client's side was to verify whether, as a new development team, we would be able to ensure:

1. Continuity of Development Work

The first concern was ensuring that development work would continue without significant interruptions. Zielone Pogotowie needed a partner capable of maintaining the project's momentum and driving it forward.

2. Code Quality

Given the challenges faced with previous software houses, the client was keen on ensuring that code quality would be a top priority moving forward. They needed a partner who could not only address existing issues but also uphold high coding standards throughout the project.

3. Business Understanding

Understanding the intricacies of Zielone Pogotowie's business was paramount. This encompassed comprehending their product, revenue generation strategies, key priorities, goals, and product roadmap. The new partner needed to align with Zielone Pogotowie's vision and objectives.

Step 2 - The Challenge of Missing Technical Documentation

The next crucial step was connected to a significant challenge - there was a complete lack of technical documentation for the project. This absence would become a recurring issue during our collaboration. Without this essential documentation, we had to carefully study the project's code. We had to dig deep into the code to really understand how it was built, how it worked, and all the details involved.

Step 3 - Initiating the Collaboration

After conducting an exhaustive examination of the source code, holding a series of discussions with Zielone Pogotowie's team, and scrutinizing the project's specifications, we made the pivotal decision to move forward with the collaboration.

Our initial steps were to introduce subtle corrections and modifications to the existing codebase. This approach allowed us to gain a deeper insight into the project's architecture and functionality.

Step 4 - Implementing Agile Methodology

To ensure the project's swift revival and smooth progression, we swiftly introduced the Agile methodology. This included the implementation of weekly sprints and the establishment of regular meetings to monitor progress, identify areas for improvement, and make necessary adjustments to the development process.

These steps were crucial in quickly filling the gaps and solving the issues left by the previous teams. Our Agile approach helped us deal with challenges and set the project on a path to success.

Collaboration outcomes and conclusions


As we progress through Zielone Pogotowie's project, it's essential to highlight the results and impacts of our collaboration:

Continuity in Development Work: We successfully continued development without significant interruptions. This allowed us to maintain project momentum and meet objectives effectively.

Enhanced Code Quality: Our efforts led to a substantial improvement in code quality. This enhancement translated into more reliable and efficient software.


The lessons learned from our collaboration with Zielone Pogotowie have illuminated several critical factors that can make or break a project:

Expectation Communication Is Key: Clear and open communication of expectations is paramount for project success. Understanding what each party anticipates and needs is fundamental.

Transparency Is Vital: Transparency on both ends is indispensable. It fosters mutual understanding, trust, and alignment of goals.

Lack of Documentation Isn't Insurmountable: Although not having technical documentation is a challenge, carefully studying the code can help fill the gap.

Complete Code Audit Is Essential: It's crucial to thoroughly look at the project's code to understand all the details.

Client Testimonial

After this long journey, we are delighted to share Wojciech's testimonial:

"I am very pleased with my decision to switch software houses. I was concerned about how the takeover process would go, how it would disrupt our existing work, and how it would effect the project's schedule and budget. This adjustment has clearly paid off in the case of MuchMore. The development process is efficient, consistent, and of high quality. The team swiftly took over and smoothly continued the task, delivering the quality and speed we expected." - Wojciech Tyszkowski - Growth


In conclusion, it's crucial to emphasize that app takeovers should not be a source of fear or hesitation. Instead, they present an opportunity for growth, improvement, and a brighter future for your project. The key lies in selecting the right partner and adopting the appropriate approach to manage this transition effectively.