DOIT Software

There were 3 whales behind our decision to create the company: values, passion, and experience. As a core, we took the values of founders and adapted it to business. Both of us had a passion for IT projects and we enjoy when we deliver valuable software products for our clients. Both founders (CEO and CTO) had previous experience of managing software development companies and it was natural for us to join efforts and create DOIT Software based on our values.

We have our R&D team with CTO and Project Management, as well our own strong Recruitment team that helps clients extend their in-house team with our remote developers or even build a remote dedicated team for complex projects. As the next step of our process with a dedicated team, we offer an R&D office - a turn-key solution for the client’s dedicated team with its own branding, team buildings, and our ongoing support.

Many of our clients previously have had bad experiences with freelance software developers and were careful before agreeing to start their project with DOIT as an outsourcing vendor. The best approach is to start with a 6-month length project, where we are responsible for delivery, and our R&D team is attracted to the project. That way, clients can see the whole process and decide if there is a fit.

We have several examples of us using the outsourcing model with a client and then after everything was delivered as they expected, they liked working with us and were willing to continue cooperation. It’s the best way to continue with team extension and provide the client with a dedicated developer (or developers) who works entirely on their project for 6+ months.
 

DOIT Software has previously used the steps described above to build a dedicated team with a designer, iOS developers, full-stack developers, and quality assurance engineer for a client. In total, 8 people were working remotely from our R&D center in Kyiv.

Now, you may be wondering what can be offered next in addition to a complete product team. Right now we are offering the next step -  a dedicated team in a separate branded office with all processes set up, integrated team culture, and ongoing support in technical, recruiting, and administrative areas.

Most of our clients are from healthcare tech, retail, online education, transport/navigation, and IoT areas, but we also have projects in other industries like wellness & sports, sales & marketing, social media.

With some of our clients,  we work together for more than 2-3 years and have 2 and even 3 projects. I need to say that we have a high repetitive ratio, and we’ve received good referrals from our existing clients, who have recommended us to their partners and friends.

A bunch of factors can influence the development time of a mobile application.
The main ones are:

It all depends on the number and complexity of the functionality we develop.
Usually, we help outline a set of critical functionalities that are required for the MVP version to test the business idea in the market. This stage varies on average within three months.

All further stages depend on whether they have a good marketing strategy, whether there is a vision of project development in terms of business, etc.
In our experience, I would say that the average time to develop projects is 4-6 months.

Usually, we have two main factors that influence the choice of platforms:

As I said above, it depends on several factors.

If this is an early stage, and we do not have information on budgeting or audience profiles, then we usually consider development for Android and iOS by default.
Otherwise, we make decisions based on user persona and budgets.

These concepts often have different meanings for different people :)
Therefore, applications are classified into three groups: Native apps, Cross-platform, and Hybrids.

The first group includes applications that are created for one platform, using appropriate languages such as Java or Kotlin for Android, and Objective-C, or Swift for iOS.

Cross-platform is an application we can create for multiple platforms but have one shared codebase. 
We usually use React, Native, or Flutter for this type of project.

Hybrids. 
These are applications that are developed using HTML, CSS, JS, and just run in a specific wrapper on mobile devices.
So, we work with Native and Cross-Platform stacks and for the most part, don’t work with the Hybrid type.
 

At the same time, we recommend React, Native, or Flutter if the above items are not strictly required, or when you need to optimize your budget and costs. You can have one developer for two platforms.

The project budget depends on the methodology we are considering for the project, who will be involved from the team, and the amount of work that needs to be done.
 

If we have clear requirements for the project and a client is ready for the Waterfall approach, then the client receives a file with detailed information about the evaluation of individual functional units and the cost depending on the team composition and the duration that each member needs to be involved.

This is usually an estimate that allows us to focus on the size of the budget and the development period, but we work with a T&M approach and charge only for the time that is actually spent on work.
 

In the case of the Agile Approach, we can estimate a project using the checkpoints (they can also be converted in time units if desired) and how long it will take to involve the entire team to get the desired functionality.

As for the calculations, here we are talking about the team cost for a certain period of work.

If we are talking about the project from scratch - a mobile app development or custom software development - we have a time and material (T&M) contract type for payments, so clients pay for the hours that each team member (contracted to this project) worked, and we share bi-weekly or monthly invoices with detailed reports.

If it’s a dedicated team or a dedicated developer who is contracted full-time for a client’s project, we have a monthly fee that is paid by the client for a full-time, month-long attraction (160 hours) of each dedicated developer, QA, designer, project manager, etc.

For outsourcing types of projects, we had some clients to whom we’ve built a demo version of the application, and it was around $7k-$10k.

We believe that even for large-scale apps we need to start with the Discovery phase which we have as an initial subproject from the very beginning of the development cycle. It may take from 2 to 4 weeks and have a fixed budget up to $5k and help clients to test their solution idea with real users and/or investors by having a clickable prototype and prepared documentation from our side.

30k-250k.

Despite the numerous app revenue models, we’d recommend Software-as-a-Service (SaaS), a subscription-based app monetization model.

Right now, it’s a mainstream, global trend among enterprises and startups to use Mobile SaaS app development with cloud-based technology to replace outdated commercial software.

This means that complete information from all team members as well as updates is stored in the cloud. Users rent the software on a monthly cost-per-user or usage basis instead of buying and implementing it. Also, users can scale up and down the scope of service if needed.

Referring to the benefits of this model, I’d mention that based on the number of your SaaS app users and the number of services you provide, you can plan and predict your revenue. Your clients don’t need to update software and take care of outdated hardware which removes the workload from their IT-departments. Even if something goes wrong with your servers, your customers can always go back to the previous savings with the backup log and get access to information from any device with an internet connection.