Service · Headless Pilot
A full migration without a pilot puts the entire budget on an unproven hypothesis. First we select a category, measure the baseline and lock scope, KPI and refund terms in the contract. Bitrix backend, 1C, CRM untouched. Source code yours either way. Pilot cost credited toward replatform.
Frontbox · core
SSR · ISR · edge cache · facets · synonyms · auth
What you get
Before build we lock the baseline, selected category, data sources and acceptance criteria. If agreed KPIs are missed through our fault, the refund terms are already written into the contract.
Metrics and responsibility before code
One category in production on real traffic in 2–4 weeks. Not staging, not a demo — production metrics: LCP, CR, bounce.
Real data, not slides
The first 3 days separate the base pilot from optional work: integrations, content, unusual roles and complex checkout scenarios. Then we sign a clear scope and milestone payments.
from $5.5K · no hidden scope
Decide not to continue after the pilot — all code is transferred to you anyway. Vendor lock-in eliminated.
Code yours from day one
We connect to Bitrix via API (read-only): products, stock, prices. Backend, 1C, CRM, marketplaces stay unchanged.
Zero risk to your current store
Cases
We take on pilots where we can deliver a measurable outcome. Here is what happened.
How the pilot runs
Each stage ends with a concrete deliverable: preview on your data, a working storefront, a metrics report.
We review your site, stack, speed and catalog and audit Bitrix: payments, delivery, 1C sync, marketplaces. The output is a bottleneck map and the category for the pilot. We share similar cases so you know what to expect.
Frontbox on the selected category: PDP, listing with filters, cart. Elasticsearch configured for your attributes — morphology, synonyms, autocomplete.
Connect one payment and delivery provider. Load testing, SEO, cross-browser. Sign-off with your team on staging.
Deploy to production subdomain or A/B split. Measure LCP, CR, bounce before and after. Report with metrics and a go / no-go recommendation.
Comparing approaches
Two paths to headless. Pilot is for those who want data before the decision.
Pricing
Pilot cost is credited toward the first phase of Headless Replatform if you continue.
For e-commerce stores on 1C-Bitrix after category audit
One category in production: PDP, listing, cart, checkout. LCP and CR measured before and after — in numbers, not impressions.
| Item | Included | Not included |
|---|---|---|
| Audit | Yes, first 3 days | |
| One payment / delivery provider | Yes | |
| Metrics report | Yes | |
| Full catalog | Next phase: Replatform | |
| AI personalization | Separate: AI Pilot |
KPI, scope and refund terms are fixed after the 3-day audit. Source code transferred regardless.
Guarantees
Every item is in the contract before kickoff. Not in a deck — in a document.
Metrics, baseline, selected category and acceptance criteria are written into the contract before build.
Price and scope are fixed after we check the catalog, integrations, data and current Bitrix constraints.
First 3 days — a technical audit of your site, stack and catalog. A bottleneck map and the category for the pilot.
LCP, TTFB, CR, bounce before and after. Executive format — no technical jargon.
Code transferred even if you decide not to continue. Vendor lock-in eliminated.
If you move to replatform, pilot cost goes toward the first phase.
FAQ
First we run the audit, select a category and lock baseline LCP/CR plus technical constraints. Then we write KPI, acceptance criteria and refund terms into the contract. If agreed targets are missed through our fault, we follow those terms. Source code is transferred regardless.
The audit is included in the pilot cost and takes the first 3 days: we review your site, stack, speed and catalog and map the bottlenecks. If you have already had a technical audit — we credit it and shorten the pilot timeline by 3 days.
We decide together on the first call. Usually we pick your highest-revenue category with a mobile CR drop — results are clearest there. Or the category with the worst LCP.
No. After the pilot you make the decision based on real metrics. If you do not want to continue — code is transferred to you and we part without issues.
Yes. The pilot cost is credited toward the first phase of Headless Replatform if you continue.
Headless Replatform cost depends on catalog size and number of integrations — typical range starts from $15K. Pilot cost is credited toward the first phase. We prepare a detailed estimate after the pilot based on its results.
No. We connect to Bitrix via API in read-only mode: products, stock, prices, categories. Backend, 1C, CRM and marketplaces are not modified.
In 3 days — the audit results: a bottleneck map, baseline measurement, scope of work and fixed pilot scope. In 2–4 weeks — one category live in production with real LCP and CR metrics.
If you need the full catalog migrated at once — see Headless Replatform. If there is no technical way to isolate a test category, or you need AI personalization from day one — see AI Pilot. If you are not sure the pilot is the right step, start with the free audit — in 48 hours we show the bottlenecks and a quote.
Quote ready in 48 hours. If pilot is not the right fit — we will say so and suggest an alternative.
A lighter entry before the pilot: we review your site, stack, speed and catalog — a bottleneck map and a fixed quote.
ServiceThe full cycle after the pilot: catalog, integrations, conversion growth.
ComparisonAn honest comparison of approaches: speed, cost of ownership, risks.
