When we establish the prices, we create a list of user stories according to the customer’s requirements. Sometimes the client already has this list – this is an ideal case- , but if they don’t have it, we create it together. Based on this list, we make a series of estimations of the development effort, which are translated into cost per hour.

The roles of employees involved in the project – our tariffs are different for Front-end, Back-end, DevOps, UI / UX Design, Business Analysis, Software Architecture, and Project Management roles.
The technologies we use – PHP, NodeJS, Python, VueJS, WordPress.
The seniority of our team members – junior, middle, senior, and sometimes architects.
Timeframe – if the delivery time is very tight, then the price may increase because there is a need to form the team in a very short time which usually means paying an over the market cost to quickly dislocate resources and bring them in the team.

We don’t differentiate between short-term and long-term projects because most of the time one-off projects have become long-term collaborations. So, even if initially there are projects that we estimate to last three to four months, usually we continue our collaboration and continuously develop new functionalities while providing maintenance and support services for the business.

But what we want our clients and potential clients to remember is that we have great flexibility – customized costs per project, time and material, flexibility in working with client resources (programmers, product owners, designers) – and always try to accommodate all the needs they have.

You can see more of our projects and how we worked with the client teams on our case studies page.