Three levels and their price
Market prices vary enormously — not because somebody is greedy, but because three different products all get called “an online store”. The price is set by functions, not by the name: in our configurator a Telegram bot starts at $1,500 while an enterprise CRM reaches $150,000 — and even within one product the range can be tenfold. Here are the reference points for a store — the same ones as in the configurator on this site; other products are covered in the Cost & timelines rubric. The detailed breakdown is on the online store development page with pricing.
What the price is made of
The cost of development is almost always the team’s time, and time goes not into “making it pretty” but into logic. Here is what genuinely moves an estimate.
- Catalogue size and structure. A hundred products with two attributes and ten thousand with sizes, colours and per-warehouse stock are different projects.
- How the price is calculated. A fixed price list is cheaper than segment discounts, promo codes, loyalty points and quantity-based pricing.
- Payment and delivery. One payment provider and click-and-collect is one thing; three providers, instalments and address-based delivery pricing is another entirely. How the connection works is on the Payme and Click integration page.
- Integrations. The exchange with an accounting system, a warehouse or a CRM is almost always the most expensive part, because it depends on someone else’s system rather than on us. More on the 1C integration page.
- Design. Template design on a ready-made system is ×0.85 of the estimate, branded design built around you is ×1, premium design with motion and award-level detail is ×1.35.
Where cutting corners is a mistake
- Payments. A failure at this step is money lost, not an inconvenience.
- Speed. Every extra second of load on mobile measurably reduces conversion — that is no longer a debatable claim.
- The admin panel. If changing a price requires a developer, the store starts going stale a month after launch.
- Analytics. Without it you will never learn where buyers drop out, and you will be improving things blind.
Speed deserves a note of its own: it is lost in places nobody looks. We showed the method on our own site — how we cut LCP from 6.4 to 2.2 seconds.
How long it takes
Start takes about 5 weeks, Business about 10, Chain about 18. The first weeks go into catalogue structure and design, then development runs in sprints with a demo every two weeks: you see each new version on a staging environment before it goes live. It can be compressed by roughly a third by expanding the team, but not halved: some of the work is inherently sequential. Ranges for every product are collected on the pricing page.
Frequently asked questions
Can it be done for less?
The Start level — $6,000–12,000 and about 5 weeks — is exactly the sensible start when you need to test demand: a catalogue of up to 500 products, payments, delivery and an admin panel, with 1C exchange, loyalty points and customer accounts arriving at the next level. If the store is meant to be your main sales channel from day one, price the Business level: building discount logic and integrations on top of a solution made to test a hypothesis costs more than designing them in from the start.
Off-the-shelf or custom?
If your business process is standard, take something off the shelf — and we will say so plainly. Custom development is justified when you have your own logic: complex discounts, multiple warehouses, your own delivery pricing, or an integration with production. Do the maths over three years, licences and customisation included.
What does support cost after launch?
Bugs after launch are fixed free of charge, with no time limit. Support starts at $600 a month: monitoring, backups and critical bugs fixed within hours. The Business plan with an SLA and 20 hours of improvements is $1,500 a month; Premium with 24/7 on-call and 50 hours is $3,500.
Who owns the store once it is paid for?
You do: the rights to the source code and data pass to you once it is paid for, and the domain and service accounts are registered to you. No lock-in: any other developer can pick the work up, because we hand over the documentation too.
These articles are written by engineers working on the projects and published under the desk’s name. The studio and the desk’s published rules stand behind every text, not a single author; articles about our own open-source code carry the author’s name.
How we write and what we verify