Please describe your company, your role, and the industry you operate in.
Étoile Technologies SAS is a Construction business headquartered in Lyon, France. As Directeur Technique I'm responsible for the whole technology agenda — infrastructure, product, and how we pick vendors. Every decision we make on the technology side has to tie back to a clear business case before it gets approved.
What specific problem or business challenge led you to hire this company?
Our Game Development capability had become the thing slowing everything else down. New feature requests, client asks, internal initiatives — all of it kept queuing up behind a platform that had been stretched way past what it was originally built for. We needed a proper rebuild, not another patch.
What services did the company provide for your project?
The scope ran the full Game Development lifecycle — discovery, requirements, architecture, development across roughly a dozen sprints, integration testing, performance validation, deployment, and a four-week hypercare window afterward. They also handed over full documentation and ran a knowledge transfer session for our internal team.
Why did you choose this company over other providers you considered?
A peer in the Construction space had used them for something similar in Game Development and recommended them without hesitation. Our own due diligence backed that up. Domain knowledge, Game Development depth, and a track record of actually delivering — that combination made the decision easy.
How clearly did the company understand your requirements and business goals?
Thoroughly. The requirements document was detailed enough that our own QA team used it directly to build acceptance criteria. Every user story had a clear business reason attached, and nothing was left open to interpretation. That discipline early on paid off through the rest of development and testing.
How was your overall experience with their communication and project management?
Proactive and well-calibrated. Technical detail for the engineering side, plain summaries for the steering group, and risk flags that came with a proposed fix attached rather than just a problem statement. The biweekly sprint reviews kept our stakeholders in the loop without requiring them to sit in on every working session.
Did the company deliver the project on time and within your expected budget?
Both, yes. One sprint hit a one-week delay from a third-party API dependency outside anyone's control. The team flagged it three weeks ahead of time, laid out two options, and we picked an approach that clawed the schedule back within the same sprint. That's the kind of foresight that separates real project management from just reacting to problems.
What tangible results or business impact have you seen since the project was completed?
The clearest measure is how the system's actually performing in production. In the four months since go-live we've had zero major incidents, our page performance scores improved across every Core Web Vitals metric, and two enterprise clients who'd previously flagged our old platform's limits during renewal talks signed again without raising it.
What did you like most about working with this company?
What they did after launch. A lot of vendors treat go-live as the finish line. This team treated it as the start of a different phase — the hypercare period was substantial, the documentation held up in practice, and they checked back in at the thirty and ninety day marks to go over production metrics with us unprompted.
Would you recommend this company to others, and would you work with them again?
Absolutely, with one caveat worth mentioning: the value really starts in discovery, so clients who take that phase seriously will get the most out of it. We put real effort in upfront and it clearly paid off in what got delivered.