A specialist catalogue, not a generic one
Components, sizes and compatibility matter to this audience, so product data and recommendation logic carry the shopping experience.
Case study · Embedded team · B2C e-commerce
Futurumshop: a high-personalised webshop and mobile app, run by the same team for 15+ years
A high-end cycling and outdoor retailer in the Netherlands, Belgium and Luxembourg needed a webshop that could be personalised for enthusiasts — then an app, when two out of three visits turned mobile. Bintime has built and run both since 2008 as the client's embedded engineering team.
- 15+ yrs
- Continuous partnership
- 16 → 8
- Team at peak → today
- 60%
- Mobile traffic that triggered the app
- 3
- Markets served: NL · BE · LU
About the client
A specialist retailer for people who take cycling seriously
Futurumshop sells equipment, apparel and nutrition for cyclists and mountain bikers. It started in 2000 as the idea of an online bicycle shop and became one of the best-known sporting-goods stores in the Netherlands, Belgium and Luxembourg, focused on high-end cycling, outdoor and running — while Futurum Quality Gear ships its own gear worldwide.
That audience compares components, sizes and compatibility before buying. A generic catalogue does not survive contact with it: the shop has to behave like a knowledgeable shop assistant, which is a data and personalisation problem long before it is a design one.
- Industry
- E-commerce · B2C · Marketplace
- Location
- Apeldoorn, NL · Emmerich, DE
- Partnership period
- 2008 – present · ongoing
- Engagement
- Embedded team · client-owned roadmap
Services
Expertise delivered
Technologies
Business challenge
Build a high-end shop for enthusiasts — then keep it modern for two decades
Founder and owner Harmen van der Meulen wanted a shop that met the standards of customers who are outdoor-sports fans first and shoppers second. In 2008 Futurumshop needed a new webshop; Bintime built, managed and supported it. In 2019 mobile visitors reached 60% of traffic, and personalisation had to follow them onto the phone.
Mobile became the primary channel
With 60% of visits on phones, a responsive site was no longer enough — the shop needed a native-quality app experience with push.
Growth without downtime
Expansion across NL, BE and LU and into Futurum Quality Gear had to happen on a live shop carrying seasonal peaks.
One long-lived codebase
Fifteen years of features on the same platform only stays maintainable with static analysis, CI/CD discipline and deliberate refactoring.
Lean engineering budget
The team was deliberately reduced from its peak. Output had to hold with fewer, more senior people rather than more hands.
Retail-grade reliability
A B2C shop has no maintenance window it can hide behind — support and release quality are part of the product.
Approach
One team inside the client's process, not a vendor on the outside
The Product Owner and Project Manager sit on the client side and own priorities, roadmap and project management. Bintime supplies a full-stack team that plans, builds, tests, releases and supports — the same people, year after year, which is why context does not have to be rebuilt every quarter.
Client quote“We have been working with Bintime for more than 15 years. They are dedicated and will always help to find a solution for our wishes and problems.”
Gerco Vermeer · Development Manager, Futurumshop.nl
- 01
Agile delivery on a live shop. Short iterations, feature flags and staged releases so trading is never blocked by engineering.
- 02
T-shaped seniority. Mostly senior engineers who can move between backend, frontend and infrastructure instead of waiting on a specialist.
- 03
Quality gates in the pipeline. PHPStan static analysis, automated and manual QA, containerised deploys on Docker and Kubernetes.
- 04
One codebase for two platforms. React Native for the app, with native modules where iOS and Android genuinely differ.
- 05
Knowledge transfer as policy. Rotation and pairing keep the platform independent of any single engineer, even as the team size changed.
Value delivered
Three products, delivered and then kept alive
The project was delivered and then extended — each stage building on the platform underneath rather than replacing it.
A highly customised B2C online store
Built from scratch and supported end to end since launch: catalogue, checkout, promotions and the integrations behind them, on PHP/Laravel with React and Vue.js front ends.
Highlights
- End-to-end support of the webshop, including seasonal peak load
- Personalised product recommendations for each shopper
- Relevant promotional banners driven by behaviour, not a fixed schedule
A React Native app for iOS and Android
One codebase, two platforms, full customisation. Push notifications were integrated natively through platform-specific libraries to carry personalised product news, launches and offers.
Highlights
- Native push integration for personalised product and news messages
- Stack navigator keeping navigation history so screens and routes stay predictable
- Shared business logic with the webshop instead of a parallel implementation
Support, automation and the loyalty roadmap
Today the team covers app development, technical support, email marketing automation and client-support services, while the next wave of features follows the retailer’s market strategy — including loyalty inside the app.
Highlights
- Very low production-support overhead and high operational stability
- Email marketing automation tied into shop and app behaviour
- Loyalty bonus programme integration planned inside the mobile app
Team & collaboration model
Sixteen at peak, eight today — and the same platform knowledge
The client scaled the team down deliberately a few years ago. What kept delivery steady was seniority and continuity: no juniors on rotation, no restart of context.
Team lead
Technical direction, estimates and release quality on the Bintime side.
Full-stack developers
Middle and senior engineers covering backend, frontend and webshop support.
2 QA engineers
Manual and automated testing across webshop and mobile releases.
Mobile engineering
React Native development and native module work for iOS and Android.
Product owner & PM
Client-side: product priorities, roadmap planning and project management.
Results & business impact
What fifteen years of the same team actually buys
A trusted long-term technology partner
Continuous delivery and support since 2008, through platform generations and market expansion.
Webshop, mobile app, automation stack
All three built and still run by the same team, sharing one set of business rules.
Very low production-support overhead
High operational stability, so engineering time goes to features rather than firefighting.
Team size, without losing delivery
Cost optimisation absorbed by keeping senior engineers and transferring knowledge inside the team.
The honest metric in this engagement is not a launch date — it is that a retailer in a competitive, seasonal market has trusted one external team with its revenue-critical shop for more than a decade and a half.
FAQ
Questions we get about embedded e-commerce teams
What does an embedded team actually own?
Here: frontend and backend development, webshop support, the mobile app, email marketing automation and client-support services. Product ownership and the roadmap stay with the client.
Which technologies run the platform?
PHP/Laravel with Python and JavaScript services, React and Vue.js, REST APIs, MySQL/PostgreSQL, Redis, CI/CD with PHPStan, Git, Docker and Kubernetes — plus React Native for mobile.
How does a team stay effective over fifteen years?
Seniority and continuity. Sixteen people at peak, eight today — middle and senior developers, two QAs and a team lead — with knowledge kept inside the team.
Why React Native for a retail app?
One native codebase for iOS and Android, room for deep customisation, and native push integration through platform-specific libraries.
Start a conversation
Need a team that will still be here in ten years?
Tell us what your shop or app looks like today. We will come back with a team shape, an onboarding plan and the first ninety days — including how we take over an existing codebase without a freeze.
- Reply within 24 hours from someone who can scope it
- Reference calls with existing clients, where they agree
- NDA signed before any detail is shared
Thank you
We will get back to you within 24 hours with a proposed team shape and next steps.