Blog
We write for people who order software: what drives the price, how to plan the first version, when to choose a ready-made system over your own and how to work with a contractor.
RSS feedCost · Planning
How much does custom software development cost
A mid-sized web service costs RUB 5–6 million and takes 3–5 months; a corporate system or CRM starts at RUB 6.8 million and takes 5–7 months. Here is what the price is made of, what moves it and why a starting price is not yet an estimate.
7 min read
Cost · Mobile apps
How much does it cost to develop a mobile app
An MVP for iOS and Android costs from RUB 2.1 million and takes 2–3 months; a mid-sized app with its own backend costs RUB 6–7 million and takes 4–5 months; a complex one starts at RUB 15 million. Here is how platforms, backend, design and life after launch change the price.
5 min read
Planning · Mobile apps · Web development
What you can realistically ship in three months: the MVP
In three months you can release a working first version with one main scenario: 5–8 screens, sign-in, the key feature and a simple admin panel. Here is how to spend those weeks, what to postpone and how to tell whether the idea works.
5 min read
Planning · Web development · Mobile apps
Web app or mobile app: which to build first
There is no universal answer, but there are questions that point to one: where and how often people use the product, whether they need notifications and the camera, whether they are customers or employees. Here are the criteria and the typical situations.
5 min read
Planning · Corporate systems
Off-the-shelf system or custom software: how to choose
A boxed product wins when processes are standard and a quick start matters. Custom software wins when processes give the company an edge, when customising the box costs as much as a new system or when per-user licences grow faster than the benefit. Here is how to work it out.
5 min read
Integrations
API integration: where to start and where the risks are
An integration starts not with code but with deciding which system owns each kind of data. After that the risks are predictable: weak documentation, errors and retries, data drifting apart and changes to someone else's API after launch. We go through each one.
5 min read
Corporate systems
Corporate portal: which features you need first
A portal takes root when it solves everyday tasks from day one: IT support requests with statuses, contacts and the org chart, HR processes and notifications. News and "culture" features can wait. Here is how to put together the first version.
5 min read
Working with a contractor
How a client can keep control of software development
Control is not daily calls or reading code. It is a rhythm: a demo of a working version every two weeks, a short report, acceptance against scenarios agreed in advance and a few well-chosen questions for the contractor. Here is how to set it up.
5 min read
Working with a contractor
What the warranty covers after launch
A warranty means free fixes for bugs in the delivered work; ours lasts 6 months. New features, changes in other systems and product development are support. Here is where the line usually runs and how to prepare a project handover.
5 min read
