Strategy
Research, requirements, page map and metrics before the first line of code.
Learn moreWe take the project end to end — research, design, code, deploy. Repository and documentation are handed over, so the product can grow without us.
Since 2018 — 84 projects in production, 9 people on the team.
Research, requirements, page map and metrics before the first line of code.
Learn moreKey screens, states, typography and a design system the product can grow into.
Learn moreTypeScript, React, Node, PostgreSQL. A staging demo every two weeks.
Learn moreResponse SLA, monthly hours, incident reports and post-launch growth.
Learn moreOne lead engineer and one designer per project, no management layer. We estimate as a range, then fix the price after the structure stage.
Five projects from 2023–2025 out of 84. Each with sector, year and a number you can verify in the client's analytics.
Take the full cycle or a single stage — an audit of an existing site, for example.
Research, requirements, sitemap, metrics.
Layouts, states, typography, design system.
Markup and logic, accessibility, cross-browser support.
Server side, integrations, admin panel.
Catalog, cart, payments, stock and delivery.
CI, environments, domains, certificates, monitoring.
SLA, monthly hours, incident reports.
Markup, load speed, Core Web Vitals.
The full cycle takes 6–12 weeks. After the second stage the price is fixed and does not grow.
Task, constraints, budget. Estimate as a range.
3–5 daysPage map, states, copy. Fixed price from here on.
1–2 weeksKey screens first, then the rest by system. Two rounds of edits.
2–3 weeksA staging demo every two weeks.
3–6 weeksDeploy, acceptance checklist, code and docs handover.
If the answer is not here, write to us — we reply within one business day.
The client. Repository, access and documentation are handed over at delivery.
Yes, after the structure and requirements stage. Before that we give a range.
We design them. If designs exist, we first check them for state and responsive coverage.
A staging demo every two weeks and an acceptance checklist before deploy.
Yes, after an audit. If the project cannot be maintained safely, we say so.
A couple of paragraphs about the product and timeline is enough. If the project is not a fit, we say so and recommend colleagues.