Product development and team formation from scratch
Launching a new application and assembling a team at the same time required specialised expertise to create a tailor-made product that meets the client’s specific needs.
Case study · NDA · Headless B2B e-commerce
A large online IT reseller needed a new application, a team to build it, ERP integration, and someone to look after the legacy estate in the meantime. Bintime delivered all four with a 19-person dedicated team over four years.
About the client
The client is a prominent online IT reseller offering a wide range of IT products and supplementary services for businesses, public entities and individual consumers. It specialises in seamless procurement — a single destination for organisations that need reliable IT solutions without assembling them from a dozen suppliers.
The catalogue spans hardware, software and newer technology categories. Bintime was approached for three things: developing a new application from the ground up, integrating it with the client’s ERP services while supporting the legacy applications, and migrating those legacy applications into the modernised system.
Business challenges
None of these could wait for the others. The new product needed a team that did not exist yet, and the old systems had to keep serving customers while it was being built.
Launching a new application and assembling a team at the same time required specialised expertise to create a tailor-made product that meets the client’s specific needs.
Embedding the new application into the existing ERP infrastructure demanded precise coordination, so data and processes converge instead of running as two parallel truths.
The existing legacy applications needed ongoing maintenance. Bintime took the role of dedicated caretaker, keeping them operationally efficient throughout the development phase.
Moving from legacy applications to a modern system is where most programmes stall. Migration expertise made the shift to an integrated, future-ready infrastructure a controlled transition.
Approach
Over four years the collaboration covered the full development cycle — architecture, web development, DevOps and QA/QC testing — with Bintime operating as an integral part of the client’s organisation rather than a supplier at the edge of it.
The Agile framework was implemented inside our own operations too, to strengthen the Scrum processes the team had established from scratch. Everything was centred on AWS, with microservices and infrastructure as code as the default rather than a later optimisation.
Team compositionRecruitment for the team was part of the engagement — HR and recruitment sat inside the service, not outside it.
Agile and Scrum, scaled with LESS. Process was built from scratch alongside the product, then scaled as the team grew past a single squad.
Headless commerce. The storefront is decoupled from the commerce services, which is what allows a legacy front end to be replaced without touching the operational core.
Microservices on AWS with IaC. Environments are described in code, so scaling and recovery are repeatable operations rather than tribal knowledge.
CI/CD with automation QA inside the pipeline. Two AQA engineers alongside three manual testers meant release confidence at the pace the roadmap required.
A T-shaped team. Engineers who can move across the stack, so a queue in one discipline does not stop the sprint.
Value delivered
A fully dedicated team attuned to the client’s requirements, covering every part of the technology need rather than a slice of it.
The new application integrates smoothly with the ERP services, and the existing ERP was connected to the D365 ERP system — one operational infrastructure instead of two.
Continuous maintenance of the legacy applications kept operations efficient throughout the development phase, with no gap in service.
The migration from legacy applications to the modern system went through without a stop-the-world cut-over, keeping the client competitive while it happened.
What contributed to success
KPIs were defined and tracked at each project milestone, keeping focus on business results rather than delivery volume.
Clear and open updates on progress made the client’s team part of the collaboration instead of an audience for it.
Beyond technology, the team immersed itself in the client’s business and proposed improvements before they were requested.
Industry-specific knowledge meant solutions matched the particular constraints of B2B commerce rather than generic web delivery.
Expanding cooperation
What began as a new application and a team assembled around it became a continuous engagement. Bintime keeps supporting the platform as the client’s needs and its customers’ expectations change.
The partnership has produced software that enriches the shopping experience, supports sales and validated the client’s original business idea — and it remains a working asset rather than a completed project.
FAQ
The engagement runs under an NDA. The identity, a reference call and the full architecture can be shared under a mutual NDA.
Both at once: recruiting 19 people across engineering, QA and DevOps, establishing Scrum from scratch, and delivering the first version of a tailor-made application.
The new application was embedded into the existing ERP infrastructure so data and processes converge. Bintime also facilitated integration between that ERP and the D365 ERP system.
They keep running and keep being supported. Bintime maintained the legacy estate throughout the development phase, then migrated it — so stability was never traded for progress.
PHP with Symfony, Vue, Java, and AWS with infrastructure as code. Agile and Scrum scaled with LESS, CI/CD, microservices and a T-shaped team approach.
Yes. HR and recruitment were part of the service here, which is what made assembling a 19-person team around a new product possible at all.
Start a conversation
Tell us what has to be built and what has to keep running. We come back with a team shape, a migration path and the first ninety days.
We will get back to you within 24 hours with next steps.