When a site needs a new feature
The signals come from the business: managers retype the same quotes every day (a calculator would do it), clients call to ask "where is my order" (an account would answer), the catalog has 4 000 items and search is the only navigation (filters would save it), or a partner wants orders via API and the site has no endpoint. Each of these is lost hours or lost deals — the feature pays for itself by removing the manual work or the friction. We start every project by naming that payoff: a feature is built when the math works, not when the technology is fashionable.
Typical modules
Cost calculators — from simple form-based estimators to multi-step configurators with PDF quotes; they pre-qualify leads and typically lift conversion of the pages they sit on by 15–30%. Smart forms with conditional logic, file uploads and CRM delivery. Catalog filters — by properties, price, availability — fast on large catalogs, SEO-safe with proper URL handling. Customer accounts — registration, order history, documents, repeat orders. API integrations — payment systems, delivery services, 1C, CRMs, SMS and messengers. Anything beyond the list starts with a prototype and an estimate, not with a promise.
The development process
One contractor from idea to launch. First the specification: what the feature does, edge cases, integrations, success criteria — written, agreed, priced. Then the prototype: you see and click the logic before it is built, and corrections cost minutes instead of weeks. Development follows on a staging copy with regular demo points, then testing — functional, mobile, edge cases — and launch with a rollback plan. The price is fixed in the contract after the prototype; scope changes happen only by your decision, with the cost shown before we proceed, never discovered in the invoice.
SEO and speed from day one
New features routinely kill what the site already earned: a filter that generates a thousand duplicate URLs, a heavy widget that doubles the load time, a calculator that blocks rendering. We build with those traps on the checklist: canonicals and robots rules for filter URLs, lazy loading and deferred scripts, server-side rendering where the search engines need it. Before launch the affected pages are re-measured — speed metrics and markup verified — so the new module adds functionality without subtracting positions. If the feature must be visible to search, its content is crawlable by design, not bolted on.
Cost and timelines
A calculator — from 25 000 RUB (3–5 days). A complex form with logic — from 20 000 RUB. Catalog filters — from 40 000 RUB (1–2 weeks). A customer account — from 80 000 RUB (2–4 weeks). An integration with an external service — from 30 000 RUB. The exact estimate follows the specification and prototype; the price is fixed in the contract. Support rides on the site maintenance plan: updates, minor rework, monitoring. Larger modules grow along a roadmap built with you — each next step priced before it starts.
Why development at ZXY
We develop on the sites we run — and on foreign ones — and we know where both kinds of skeletons are buried. Features ship as documented code with tests, not as a black box only the author understands: your developers can pick it up from the passport we leave. The prototype-first process means you never pay for the wrong feature. And the same team that builds the module keeps the site fast, indexed and monitored afterwards — development without SEO damage is a discipline, not an afterthought.
