webgoodpeople Logo
Contact

Service · Catalog Probe

Upload your catalog — a live headless store in 3 days

Send us a CSV or XML export from Bitrix. We spin up a Frontbox storefront on a subdomain. In 3 business days you see real TTFB, search in 88 ms, and a mobile view — all on your actual data, not demo content.

Upload catalogGet pricing
  • 3 business days
  • Fixed price
  • Backend untouched
  • Probe cost credited to pilot
Web storefront
iOS + Android
PWA

Frontbox · core

Next.js + Elasticsearch

SSR · ISR · edge cache · facets · synonyms · auth

~120msTTFB
1.9sLCP
88mssearch
1C‑Bitrix
1C
CRM / ERP

What you get

Four results in 3 business days

  • TTFB 80–150 ms

    Typical result on a real catalog. Not on demo content — on your data. Core Web Vitals in the top range.

    5× faster than standard Bitrix

  • Search in 88 ms

    Elasticsearch with morphology, synonyms, and facets. A customer types "warm jacket" and finds the right down coats. Zero-results share drops to near zero.

    at 100k+ products

  • Go/No-Go on numbers

    TTFB, search time, Core Web Vitals — before/after comparison and conversion uplift projection. Ready-made arguments for CFO and CTO, based on data — not promises.

    decision in 3 days, not a month

  • Backend untouched

    No VPN, SSH, or access to Bitrix and 1C required. Just CSV or XML. Your current store keeps running without any changes.

    fixed price, fixed timeline

How it works

Three steps — from export to a working store

The entire process takes 3 business days. You spend 1–2 hours preparing the file — we handle everything else.

  1. 01Day 1

    You send your catalog export

    CSV or XML: standard Bitrix format, Yandex.Market YML, or 1C. If the format is non-standard — we adapt it in 1–2 hours on our side. No server access required.

  2. 02Day 1–2

    We index the catalog in Elasticsearch

    We configure field mapping, morphological analyzer, synonyms, and facets based on your attributes. We deploy a Frontbox storefront on a test subdomain with your catalog.

  3. 03Day 3

    You open a working store

    A link to the subdomain: product listing, search, product cards, filters, mobile view. Plus a report: TTFB, search response time, Core Web Vitals, and a comparison with your current site.

Data flow

Backend unchanged. Probe is a separate layer.

source

CSV / XML

indexing

Elasticsearch

storefront

Frontbox · subdomain

Clients

Running on real catalogs

Probe runs on real catalogs — Bitrix, 1C, custom formats. The same clients came back for pilots and full builds.

Pricing

One format — one result

Catalog Probe is a fixed-scope service. No options, no "from". One price, three days, a report with metrics.

Proof of Concept

Data only, no obligations

Catalog Probe

A live headless storefront on your catalog. Full metrics. The decision is yours.

on requestfixed fee

Price quoted on the discovery call. Launch a pilot afterwards — Probe cost is credited.

Timeline
3 business days
Where it runs
WGP subdomain
What you get
Metrics report + project files
  • Elasticsearch indexing of your catalog
  • Frontbox storefront on a subdomain
  • TTFB / LCP / search — measured on your data
  • Comparison with your current site
  • Technical report + conversion uplift projection
  • Probe cost credited to pilot
Upload catalog

What's included — what's not

ParameterIncludedNot included
Access to your serverNot needed—
Bitrix integrationNot done—
Custom designNot done—
Elasticsearch indexing✓—
Frontbox storefront on subdomain✓—
Metrics report✓—

Probe is the entry point. The next step, if you decide to continue, is Headless Pilot: one catalog section in production in 2–4 weeks.

Comparison

Catalog Probe vs "start the pilot right away"

The main competitor of Probe is not another agency. It's the decision to launch a full pilot without any prior data.

Parameter
Catalog Probe
Full pilot right away
  • Time to first data
    3 business days
    2–4 weeks minimum
  • Budget risk
    Fixed Probe cost
    Full pilot budget upfront
  • Data for the decision
    Your real metrics
    Promises in a deck
  • Backend access
    Not needed
    Required (integration)
  • Commitments
    None
    Project contract
  • If headless did not fit
    Report with arguments — No-Go
    Pilot already paid for

Results

What Probe measures

  • TTFB
    80–150 ms
    Typical result on a real catalog
  • Search
    88 ms
    Elasticsearch at 100k+ products
  • LCP
    1.7–2.2 s
    Core Web Vitals in the top range

What Probe removes

Five risks Probe resolves before the pilot

Each of these questions blocks the headless decision. Probe answers all five in 3 days.

  • Will headless be slower on our catalog?

    Probe measures TTFB and LCP on your products, not someone else's. You see the numbers yourself.

  • Does search only work on demo data?

    Elasticsearch is indexed with your catalog, your attributes, your prices.

  • We can't stop our store

    Backend, Bitrix, 1C — untouched. Probe runs on a subdomain, the current site keeps working.

  • How do we justify the pilot budget?

    A report with real metrics — ready-made arguments for CFO and CTO.

  • What if we pay and don't go further?

    No obligations. Stop — you get the report and project files. Continue — the Probe cost is credited.

FAQ

Common questions

  • What format does the catalog export need to be in?

    CSV or XML: standard Bitrix format, Yandex.Market YML, or 1C. If you have a non-standard format — we adapt it in 1–2 hours on our side, nothing extra needed from you.

  • Do you need access to our server or CMS?

    No. Just the catalog file. No VPN, SSH, or access to Bitrix, 1C, or any backend.

  • Does Catalog Probe commit us to buying a pilot?

    No. It is a standalone service with a fixed price. After Probe you decide yourself: move forward or not. If you continue — the Probe cost is credited towards the pilot.

  • What happens after Probe?

    You receive a link to the subdomain and a technical report with metrics. If the next step interests you — we will propose a Headless Pilot: one catalog section in production in 2–4 weeks. If not — you keep the report and project files.

  • How much time do we need to invest?

    1–2 hours to prepare the catalog export file. If the file already exists — just send it. We handle everything else.

  • What's in the report?

    Measurements of TTFB, LCP, and search response time on your catalog. Comparison with your current site. Conversion uplift projection based on speed data. Technical details of the Elasticsearch configuration.

  • What catalog sizes have you handled?

    Elasticsearch handles 100k+ products without search degradation. If your catalog is larger — we will discuss index configuration separately.

  • Does Probe work with non-Bitrix catalogs?

    Yes. Probe accepts any CSV or XML with product data. Bitrix is simply the most common source among our clients.

  • Can I see a Probe example before ordering?

    There is no public Probe demo — Probe is always built on a specific client catalog. To see speed and search in production conditions, check ur-met.ru and vostok-watches24.com — both run on Frontbox right now.

Send your catalog — get the numbers in 3 days

Fixed price, fixed timeline. Backend untouched. If you decide to launch a pilot after Probe — the cost is credited.

Upload catalogGet pricing →

Tell us about your project

Contact us

Our offices

  • Russia
    Saint Petersburg, Rizhskaya st. 5, bldg. 1, office 402
    +7 (967) 555-90-32
  • Kazakhstan
    Almaty
    +7 (707) 340-29-12
Discuss project