Magento development
We have worked with Magento since 2015: installation and custom modules, untangling inherited code, upgrading versions nobody wants to touch, and speeding up the storefront.
What's included
- Store and custom module development on Magento 2
- Migration from Magento 1 and upgrades to the current version
- Storefront performance: caching, indexers, Hyvä
- Security patches, newer PHP versions and extension updates for Magento 2.4
Technologies
Related services
How we work
- 01
Brief and estimate
We look at the task, your current system and constraints, then name the timeline and budget and suggest how to work together.
- 02
Specification
We capture requirements and acceptance criteria in a specification — it is what we build against and how the result is accepted.
- 03
Iterative development
You see the result after every iteration; we test and fix before anything goes into a release.
- 04
Launch and support
We ship with no downtime, monitor the product after launch and stay on for support if you need it.
Cost and timeline
Hourly Rates: from 1 800 ₽ to 3 500 ₽ / hour — depending on specialist qualification.
We give an exact timeline and budget after a brief: we break down the task, fix the scope and suggest a format — a fixed plan or hourly work.
See plansFAQ
Can you take over a Magento store built by another team?
Yes. We start with an audit of custom modules, third-party extensions, server configuration and bottlenecks. You get a list of risks and a work plan, and then we take the project over for support and further development.
How does a Magento 2 upgrade or a Magento 1 migration work?
We migrate the data, replace or rewrite incompatible extensions and adapt the theme to the new version. Every upgrade runs on a staging copy first and goes live only after the key flows are checked: catalogue, cart and checkout.
How much does Magento customisation or performance work cost?
Cost and timeline depend on the scope and the state of the code, so we estimate them after a short brief and an audit. For performance we usually look at caching, indexers, search and the frontend, including a move to the Hyvä theme, and estimate each step separately.