Our process - How we work
We start with a Catalog Probe — 3–5 days, a live demo on your real catalog. Then we lock in the budget and timeline. After that: weekly demos every Friday, a zero-downtime launch, SLA from day one.
Discovery & Catalog Probe
Every project starts with a Catalog Probe — 3–5 working days. We connect to your catalog via API, check integrations, spin up a test environment. You get a live demo on real content and a precise cost estimate.
Not a presentation or a wireframe mockup. You see a working site running on top of your Bitrix — before signing a contract for the full project.
After the Probe you receive: a detailed spec, a fixed budget and timeline. If we misjudged the effort — we cover the difference.
Included in this phase
- Catalog Probe (3–5 days)
- Bitrix API technical audit
- Integration map
- KPIs and success metrics
- Fixed budget
- Live demo on your catalog
Development
Every Friday — a demo on the staging domain. Working code you can open in a browser and test. No slides, no ‘in progress’ status updates.
Direct access to the developer via Telegram. Priorities can shift at the start of each week. Shifting priorities doesn’t change the budget — we work within the agreed scope.
If we find a technical complexity we missed in the estimate — we absorb it. You pay what’s in the contract.
Launch
We route 5% of traffic first — monitoring errors and metrics. Then 25%, then 100%. At each step there’s an automatic rollback: if something goes wrong, we’re back in 5 minutes.
Before switching, we run automated tests (Playwright, Lighthouse) on all key scenarios: catalog, search, cart, checkout. Green across the board before we go to production.
After launch: the full repository, architecture docs, runbook. You don’t depend on us for day-to-day operations.
Included in this phase
- Testing. Playwright e2e + Lighthouse before every deploy across all key user flows.
- Infrastructure. Vercel for the frontend, your Bitrix for the backend. Need a closed environment — we deploy to your cloud.
- Support. SLA starts day one after launch. Three tiers: from 24-hour response to 24/7.
How we operate - Six rules we don't break
Twelve years in e-commerce taught us: clients don’t suffer from technical problems — they suffer from unpredictability. Here’s how we address that.
- Fixed budget. We write the estimate into the contract before we start. If we underestimated — we absorb the difference.
- Demo every Friday. Not reports — working code on the staging domain. Bring your team, test it yourself.
- Zero-downtime launch. Gradual traffic shift: 5% → 25% → 100%. Automatic rollback in 5 minutes if something goes wrong.
- Your code. After launch we hand over the full repository and documentation. No lock-in.
- Catalog Probe first. We don’t start a full project without a proof of concept. You see real results in 3–5 days, then decide.
- We say no. If a job isn’t the right fit for us, we’ll say so directly and recommend someone else. Taking everything that comes in isn’t our model.
FAQ
Common questions about our process
What is the Catalog Probe and why does it matter?
The Catalog Probe is a trial integration over 3–5 working days. We connect your catalog via API, deploy Frontbox on a staging domain, benchmark speed and test key flows. You get a live demo and a precise cost estimate. You decide whether to proceed with the full project only after seeing a real result.
How much does the Catalog Probe cost?
The Catalog Probe has a fixed price agreed before we start. Get in touch — we'll give you a specific number for your project.
How is the fixed budget guaranteed?
The budget goes into the contract before work begins. If we discover a technical complexity we missed in our estimate — we absorb it. You pay the contract amount, nothing more.
What happens if requirements change mid-project?
Priorities can shift once a week, at the start of each sprint. New features beyond the agreed scope are estimated and approved separately. Shifting priorities within the fixed scope doesn't change the budget.
How often do we see project progress?
Every Friday — a demo on the staging domain. Working code you can open in a browser. Plus daily short updates in the project's Telegram channel.
What does a zero-downtime launch mean?
We route 5% of traffic to the new frontend first, watch metrics, then 25%, then 100%. At every step there's an automatic rollback. If something goes wrong, we're back to the previous version in 5 minutes. Your Bitrix and all orders keep running throughout.
What do we receive after launch?
The full code repository, architecture documentation, a runbook for your dev team, and deployment instructions. Everything you need to operate independently.
How does post-launch support work?
SLA starts on day one after launch. Basic — 24-hour response during business hours. Professional — 8-hour response, extended hours. Enterprise — 2-hour response, 24/7. More details on the support page.
Start with the Catalog Probe
3–5 working days, a live demo on your catalog, a fixed estimate. Then you decide.