Absolutely: this is our core service. We’ve built a strong team of 700+ IT professionals – consultants, architects, developers, data scientists, security, DevOps, and QA engineers – to take charge of everything from requirements elicitation and software design to coding, deployment, and support.

Yes, depending on the project size, we might be able to get your MVP delivered in 2 weeks – 4 months. Subsequently, we can ensure releases of new functionality every 2–6 weeks. Get in touch, and we’ll work out a way to meet your needs.

Software development costs for a medium/large application may range from $50K to $1M. The total amount mainly depends on the number and complexity of software features, the number of platforms supported (web, mobile, desktop), and the type of development (custom, low-code, or platform-based). The UI design uniqueness and complexity, the number of integrations with other software systems, as well as availability, security, and performance requirements also play an important part.

You can request free project cost calculation from ScienceSoft or find more details about software development costs in our recent guide.

During the first 1–3 months after the software launch, our team:

• Answers your and users’ questions, resolves user issues (if any).
• Manages incidents, configuration changes, and updates.

When the warranty support is over, upon agreement, we’re ready to offer continuous maintenance and evolution of your software, as well as L1-L3 support (if required). We know how to nurture long-term partnerships and keep our customers happy in the long run: 62% of our revenue is coming from customers we serve for more than 2 years.

For most of our software engineering projects, we use Scrum with 2–3 week iterations. For small and midsize projects with clearly defined and unchanging requirements, projects requiring formal approvals (governmental projects and projects for big corporations), and projects with strict compliance requirements, we can opt for Waterfall. In software support and evolution projects, we mostly follow Kanban. Naturally, in many projects, it makes sense to use a combination of approaches or switch from one to another depending on the project stage. In our practice, the most common scenarios are ‘Waterfall -> Scrum’, ‘Scrum -> Kanban -> Scrum.’

We take a shift-left approach to QA, follow international coding standards, and maintain a quality management system at the level required by ISO 9001.