We would love to hear from you whether you are curious about our services, looking for help or interested in a partnership. We are ready to answer any and all questions.

Every journey starts with a first step, based on the information provided in our early meetings and based on the quality of information provided in the early stage, we will support you with a primary cost/resource estimation. At this stage this is only an orientation estimation, to help you with your project budget.  

Game Design Document (GDD) is the most important step in your project implementation and documentation. Our expert will be preparing a detailed description of the game*s mechanics, loops, ties and visual guides. This stage is the most time consuming before the development work kicks off. This deep dive in technicality will help not only in setting the roadmap of the release but also give us an exact estimate on the resources needed for implementation and avoid any misalignment between project goal and scope. We use GDD to estimate a timeline for development and use it as a reference point in every aspect of our work.

After getting to know your game and all its aspect and upon clarifying all the requirements and the allocated resources needed for a successful implementation. We will be able to support you with an an accurate  resources estimation needed for the implementation. In this stage we will be able to provide you with the budget needed for a MVP release. Depending the complexity of the project, the delivery of the final estimation is usually within two weeks.

Within gamedev, MVP, a Minimum Viable Product, is a game with, for instance, the first quest from the main storyline and a few of its substories. We release MVP to figure out how players would react to the world, narrative, and core mechanics.

Then, we can also estimate a budget, required to release MVP and extrapolate the numbers on the entire game. We deliver the final estimation within a week or two, once again — depending on the scope.

Upon your agreement on the final estimation, the development stage will kick off and our experts will be working hard to deliver all the functionality described in GDD within the allocated resources and help us monitoring the velocity on the work done. We will be reporting our progress and our milestones regularly. We are committed to transparency and would love to have regular meetings to present out work done. This will increase  the interaction between us. Moreover you will always be updated on the work progress. In addition if you feel that some changes are needed, we can adapt swiftly.

We develop the game in cycles, increments, and each of them is about two weeks on average. After 1.5-2 months of development, we start to show you our progress at the end of each cycle, so you could test, check, and, in general, give feedback on some of the functionality we’ve developed. After the third month, you can try the MVP version of the game and direct the process if that’s something you want.

The process is entirely transparent, and we provide reports via meetings (in any comfortable form for you) and project management software (usually Jira, but if you use something else, — we can easily adapt to it.)

Timelines depend on the scope of work.

In this stage our QA and testers will be working side by side to test your product for any potential bugs, that might raise. This step is very important to make sure that our project is bug-free and meeting your expectation fully. In addition this will help us gather enough feedback from test players and you can measure their engagement and observe your game from their perspective.

After a successful completion of testing phase, we will be gladly introducing this product in the market with basic features, but enough to get the attention of your customers. This will also help you collect, users feedback on potential improvements, changes or adaptations. Perhaps we can collect some data from players outside the test environment. Thus make sure a user friendly environment and adaptive solution for the market.