When you do not need Frontbox
Six situations where we advise against Frontbox and what to choose instead: keep what works, a one-off project, Site Search, Content Factory or support. And when Frontbox does fit.
Read moreAbout - A team with its own product. A product with a team behind it.
We're engineers who have been shipping online stores and enterprise portals for mid‑market teams on 1C‑Bitrix, Next.js, Laravel and Elasticsearch since 2015. In 2024 we packaged our headless stack into our own product — Frontbox — and started more complex projects with a 15-minute brief and compact discovery.
We are useful when "rewrite everything" is too risky: a live catalog, SEO, ERP and CRM integrations, active revenue, user roles and accumulated technical debt. First we separate the base from optional work, then choose a safe first slice.
Two bases — Saint Petersburg and Almaty. A partner presence in Dubai. Working languages — Russian, Kazakh, English. Compliance — 152‑FZ for Russia, GDPR for the EU, on‑prem / FSTEC for gov and fintech.
- in e‑commerce and 1C‑Bitrix
- 10+ yrs
- Saint Petersburg + Almaty
- 2 HQs
- own platform for online stores
- Frontbox
- before fixed estimates for custom scope
- Discovery
Before an estimate
What we check before the project becomes a black box
Fixed price fits packaged Frontbox formats. For custom development, replatforming and integrations we first build a compact map of requirements, risks and the safest first step.
Current stack, release process, access model and parts of the system that cannot go down.
Critical flows: catalog, search, cart, checkout, account area and content operations.
Integrations: ERP, CRM, payments, delivery, analytics, external APIs and data constraints.
Base / optional / client-specific: what belongs in the first release and what should wait.
Acceptance criteria: speed, SEO, roles, control URLs, analytics events and review criteria.
The safe first step: a 15-minute brief that clarifies options and a budget range.
What we prioritize - Brief first, your data stays yours, scope aware — never six months of slides
We're building a studio where speed does not replace engineering checks. First we map constraints, agree the scope, and only then promise timelines, metrics and budget.
- Brief first, not spec first. The first step is a 15-minute brief with a product owner and developer. If the task needs it, we then define a verifiable scope instead of a 200-page spec.
- Your data stays yours. Frontbox sits on top of your backend: catalog, orders and domain stay with you. After the storefront is switched off you keep one month of cabinet access to export your catalog, blog and materials.
- Discovery before promises. For custom work we separate base scope from optional features and check data, integrations, roles and acceptance criteria before estimating.
Leadership
Elena Zhilyakova
Founder / CEO
Founder and CEO of WebGoodPeople. Elena leads key client engagements, sets the studio strategy, and represents the company publicly.
From the blog
We write about storefronts on top of Bitrix, zero‑downtime moves and AI content — from real projects, not theory.
Shopper query: product page, category or article?
A shopper types a query and the store opens the wrong page, or none at all. We use our Frontbox demo store to show how a query tells you which page should answer it, and how to check your own catalog with ten queries and one table.
Read more