What It Takes to Build Multiple SaaS Companies with Multiple Teams simultaneously – Part 1

Have you ever wondered what it takes to build multiple SaaS companies with multiple teams simultaneously? Then this 3-part interview is for you (part 1).

Have you ever wondered what it takes to build Software as a Service (SaaS) companies? And not just one SaaS company with one team, but multiple SaaS companies with multiple teams at the same time? Then this is for you. Today we are talking to our Lead Software Engineer at betascale Labs, Bleron. In this interview, he talks about the challenges he faces on a daily basis, shares what leadership and company culture mean to him, the importance of mentors in software development, and what advice he would give to aspiring software engineers. But the interview doesn’t stop there: Bleron also shares his approach towards a healthy work-life balance, his future career goals, and what message he would write on a billboard for millions of people to see.

This is part 1 of a 3-part interview series. In the first part, we explore the challenges Bleron faces at betascale Labs and how he addresses them.


Senior Software Engineer and Team Lead at betascale Labs

Bleron is 27 years old and was born in Prishtina, Kosovo. His professional career started in 2017 as a Full Stack Developer at ProxiBay, which was fundamental for him as this role allowed him to gain hands-on experience in software development for almost three years. In early 2020, he then joined Incodeks, this time as a Software Engineer, where he deepened his expertise by working on various projects that expanded his technical skills. These two stations finally led him to betascale Labs in January 2023, where he has been working as Senior Software Engineer and Team Lead ever since. In this role, Bleron currently leads three projects: Acquify, gut geregelt and Widgetino.

Working at betascale Labs

First of all, I’m always curious about what a typical working day looks like. But as Senior Software Engineer and Team Lead in a fast-paced company, is there even such a thing as a typical working day?

Yes, although it can vary due to different circumstances, I do have a typical working day. For me, a typical working day includes daily stand-up meetings with the various teams that I lead. These meetings are important to discuss progress, address technical problems and coordinate work. After the stand-ups, I dedicate myself to hands-on development with the team I’m assigned to that day. My role often requires me to switch between different projects throughout the week so that I can ensure a dynamic and collaborative working environment.

Looking back at your career so far, were there any pivotal moments that shaped your path as a software engineer?

Yes, absolutely! A pivotal moment in my early career that significantly shaped my path as a Software Engineer was the opportunity to work on diverse projects that required both my effort to take projects on my hand. This experience helped me develop a comprehensive understanding of software development and played a crucial role in my growth towards more advanced roles in the field.

What was the deciding factor for you to join betascale Labs? Have your expectations been fulfilled?

The key factor that influenced my decision to join betascale Labs was the unique opportunity presented to me: the possibility to build multiple SaaS companies with multiple teams simultaneously as a Senior Software Engineer and Team Lead. This role allows me to have a direct impact on shaping the companies’ objectives, which I find particularly rewarding. betascale has surpassed all my expectations, as it has afforded me the chance to engage in numerous projects and operate at my utmost capacity.

On another note: It seems that Kosovo has recently positioned itself strongly on the global map of software development. Would you agree?

Indeed, Kosovo, including Prishtina, has developed a robust culture in software development. In recent years, the region has experienced significant growth in the field of Software Engineering. This development is highlighted by its collaboration with large global companies and the numerous products that are being successfully delivered from here.

Widgetino is a testament to our team’s capabilities and spirit of collaboration. It shows the tremendous efforts and potential of our interns to achieve impressive results.


What are some common challenges you face in your role, and how do you address them?

In my leadership role, I encounter a variety of challenges. One of the biggest challenges is choosing the appropriate tech-stack for application development. Additionally, addressing technical issues is crucial, especially when they hinder our work progress. Ensuring that all developers are aligned and on the right track with their development tasks is another vital aspect of my role. Furthermore, handling client interactions to smoothly integrate new requests into our pipeline is another aspect of my role that comes with its own unique set of challenges.

What are the most challenging aspects of building multiple SaaS companies with multiple teams at the same time?

The most challenging aspects involve ensuring that all team members and projects are on the right track. This requires meticulous oversight, including reviewing every line of code to identify and correct any deviations from the intended path.

How do you forecast and plan for future projects and resource needs, taking into account the current workload and the team’s capabilities?

Forecasting and planning for future projects and resource needs at our company is primarily dependent on the influx of new project requests. This approach allows us to gauge whether additional resources are necessary to accommodate growth and the successful development of these new projects, taking into consideration our current workload and the team’s capabilities.

Building multiple Software as a Service (SaaS) companies with multiple teams at the same time requires meticulous oversight. The main challenges are to ensure that all team members and projects are on track.

How do you handle the aspect of managing expectations and feedback from multiple stakeholders?

This is a critical aspect of my role. To effectively handle this, I prioritize clear and consistent communication, ensuring that all stakeholders are kept informed about the progress of each project and any challenges that arise. This involves actively listening to their feedback and expectations, and integrating this input into our project planning and execution. By maintaining an open line of communication and addressing concerns promptly, I strive to align stakeholder expectations with our project goals and capabilities.

Can you highlight a particularly complex company you currently are working on (or have worked on in the past)?

Acquify stands out due to its complexity, driven by its extensive range of features. This company requires a deep understanding of various user needs and sophisticated data management strategies. Previously, I worked on the Sutro project, where my responsibilities centered on digitizing data from logs and ensuring the efficient delivery of the product to an estimated 10,000 users across the US every month. My experience in these projects, particularly in handling large volumes of data and catering to a substantial user base, showcases my ability to manage challenging technical tasks in dynamic project environments.

Are there any particularly exciting SaaS companies that your teams are working on at the moment?

Certainly! gut geregelt and Widgetino come to mind. Each company comes with its unique set of features and challenges, and we’re very excited about the impact they will have in the future.

This wraps up part 1 of this 3-part interview series. Continue with part 2, where we dive into what leadership means to Bleron and what makes the team at betascale Labs so special!

About betascale

The future is not shaped by dreamers nor managers. But by doers. betascale unites doers from the entrepreneurial, corporate and financial worlds and supplies them with what they need, when they need it. From idea to exit.