Demo · Headless PoC
E-commerce category in headless mode
This demo represents an e-commerce category (e.g. furniture) rebuilt with Next.js, BFF/APIs and a headless CMS, to show how the experience changes compared to a legacy frontend.
Sample scenario: stack, content and data are mocked but aligned with real-world cases.
UI snapshot
Realistic headless category UI (staging)
A quick look at what the PoC looks like before the metrics: desktop category, reusable product card, and mobile layout.
Category UI preview
Desktop category view — filters, sorting and product grid. Designed to connect to real catalogue APIs.
Tip: use these screenshots to align marketing + IT before looking at Core Web Vitals.
Results snapshot
A quick, measurable before → after overview.
LCP
4.2s→2.1s
Mobile, key template
INP
280ms→160ms
Interaction responsiveness
Delivery
5 days
PoC scope, handover included
Output & methodology (anonymized)
What you get after the PoC
Concrete artifacts you can keep, share internally, and use to decide next steps.
Included artifacts
Documentation + walkthrough summary to transfer the PoC to your team.
Tip: use these assets to align marketing + IT before moving to rollout.
What changed (and what didn’t)
What we changed
- Headless UI layer on a limited scope (safe PoC)
- BFF/API stitching to isolate legacy complexity
- Performance-focused rendering + asset optimization
What we didn’t change
- No full replatforming or CMS migration
- No disruption to existing backend processes
- No lock-in: code and handover are yours
Deliverables
Concrete assets you can keep and extend after the demo.
- PoC implementation (frontend + BFF layer)
- Core Web Vitals before/after snapshot
- Repo + PR structure (review-ready)
- Walkthrough video (Loom)
- Handover pack (setup, notes, next steps)
What this demo covers
The goal is to show you a category in headless mode, ideally connected to your existing catalogue and ready to be measured.
- Product listing with images, title, price and badges
- Filters and sorting designed for mobile
- Product detail page with key information
- Modern routing and smooth transitions
Technical aspects we highlight
In the demo we also peek behind the scenes to understand how this could sit on top of your stack.
- Simplified diagram of integration with existing APIs/catalogue
- Use of a BFF layer to orchestrate multiple data sources
- How Core Web Vitals would be measured on the PoC
- Potential rollout strategy (one category at a time)
How it maps to your real PoC
We use the demo to define a concrete scope: which section of your site makes sense to test and with which KPIs.
- Identify the most promising category or section
- Define KPIs: LCP, conversion, bounce rate, etc.
- Assess IT constraints and minimum required integrations
- Sketch a roadmap: from PoC to production without a big bang
Need real numbers before changing stack?
We start from a single category or section and use the demo to align expectations, scope and next steps.