Service · Headless Pilot
A full migration without a pilot puts the entire budget on an unproven hypothesis. Validate your hypothesis on real data before the full replatform budget. 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 kickoff we lock in metrics in the contract: LCP ≤ 2s on 4G, conversion no lower than baseline. If we miss them — we refund the full pilot cost.
Money back if we miss
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
Quoted before signing, milestone payments. No surprise invoices mid-project.
from $5.5K · no hidden costs
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 load your CSV/XML catalog and deploy a preview on a subdomain — you see real speed and search on your data before any integration. In parallel we audit Bitrix: payments, delivery, 1C sync, marketplaces.
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
One category in production: PDP, listing, cart, checkout. LCP and CR measured before and after — in numbers, not impressions.
| Item | Included | Not included |
|---|---|---|
| Catalog Probe | Yes, first 3 days | |
| One payment / delivery provider | Yes | |
| Metrics report | Yes | |
| Full catalog | Next phase: Replatform | |
| AI personalization | Separate: AI Pilot |
KPI not met through our fault — we refund the pilot cost. Source code transferred regardless.
Guarantees
Every item is in the contract before kickoff. Not in a deck — in a document.
Metrics (LCP, CR) are written into the contract. Miss them through our fault — we refund.
Price is fixed before signing. No surprise invoices mid-project.
First 3 days — catalog load and preview on your data. You see the speed before integration.
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
Before kickoff we agree on KPIs in the contract: LCP ≤ 2s on 4G and conversion no lower than baseline. We measure two weeks after launch. If targets are missed through our fault — we refund the full pilot cost. Source code is transferred regardless.
Probe is included in the pilot cost and takes the first 3 days. If you have already run a Probe — 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 — a preview on your data (Catalog Probe). 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. The Catalog Probe concept can help you first check whether your catalog is compatible before committing.
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: a live headless storefront on your catalog in 3 days.
ServiceThe full cycle after the pilot: catalog, integrations, conversion growth.
ComparisonAn honest comparison of approaches: speed, cost of ownership, risks.
