BEDA SOFTWARE

BACKGROUND

Please describe your company and your position there.

Founder & CEO

OPPORTUNITY / CHALLENGE

For what projects/services did your company hire BEDA SOFTWARE, and what were your goals?

We wanted to develop a next generation healthcare community platform, so we hired Beda Software to handle the software development, UX/UI design, and project management.

SOLUTION

How did you select this vendor and what were the deciding factors?

Our partners worked with this company before and highly recommended working with Beda Software.

Describe the scope of work in detail, including the project steps, key deliverables, and technologies used.

At The Sovereignty Network we had a lot of ideas that we needed to validate. So there was no strict scope of work and requirements. We were looking for a technological partner who can handle technical aspects of our innovations in health-tech world. We worked together with the Beda team on identifying our goals and the scope of project MVPs. It was an iterative and continuous process. This flexibility helped us to launch MVPs, validate ideas, and pilot solutions quickly. So we built 3 full-featured applications in a 2 year timeline.

How many people from the vendor's team worked with you, and what were their positions?

We’ve been working together for about two years. The team size and structure changed depending on the project's needs at the particular product milestone. We always worked closely with the Business Analyst/Project Manager, the UX/UI designer, and a few full-stack software engineers. Usually between 5 and 7 in total.

RESULTS & FEEDBACK

Can you share any measurable outcomes of the project or general feedback about the deliverables?

For the past 2 years we have lunched 3 projects to validate market needs. The first project was called Cure8Health. It is an EHR for small clinics that provides pre-visit check-in functionality, clinical notes and insurance claims. The second project was developed for community health workers in Africa. The main goal of the app is to replace paper forms with an iPad app and extract data automatically to a hospital EHR.

The third one is clinical trial matching module for The Sovereignty Network platform. This module allows filtering patients by researcher criteria to check how much relevant data could be gathered. Then researchers can recruit patients and pay them on the platform. All three projects were delivered on time with high quality. We are proud of the quality of the software. It is flexible, has a nice look and feel (that’s important for a digital healthcare product these days), and could be customized for various future demands by our customers.

Describe their project management style, including communication tools and timeliness.

The dedicated team is assigned to work on our project. The team has a flat structure so that we can communicate directly with each team member. All of us operated as a single product team. We had weekly demo events where we could see the progress and provide feedback. We asked to use Asana and Teams for project management, and the team was fine with using these tools. Real-time communication was organized in Telegram chat.

What did you find most impressive or unique about this company?

First of all, their expertise is in the health-tech domain. The Beda team are very well familiar with the industry standards, best practices, and other existing software solutions on the market. The next important thing is their deep dive into the product we are building and the informal approach to the work. They don’t require a fully detailed explanation of what they should do and how they should do it. It’s instead vice versa: they guided us through the product development process considering the business objectives and took full responsibility for the result.

Are there any areas for improvement or something they could have done differently?

The Beda team is pretty flexible. So, when we discovered some issues in the work process, we simply discussed them, and the adjusted process was adopted quickly. It was a very efficient way to work and dynamically iterate.