Factorial Complexity

Please describe your company, your role, and the industry you operate in.

Amazônia Digital Ltda operates in the Media & Entertainment sector out of São Paulo, Brazil. In my role as VP of Technology I am responsible for both the technology strategy and day-to-day delivery. We hold our vendors to the same standards our clients hold us to.

What specific problem or business challenge led you to hire this company?

We had a clear product vision for our next growth phase in the Media & Entertainment market but the IT Managed Services expertise we needed was not something we could recruit for on our timeline. An external specialist was the pragmatic answer.

What services did the company provide for your project?

Primarily IT Managed Services, with QA and solution architecture included in scope. They owned the build end-to-end from requirements through to go-live, including three existing system integrations. Not needing to coordinate separate QA or architecture vendors was genuinely valuable.

Why did you choose this company over other providers you considered?

We had been through a failed engagement the year before and took vendor selection seriously this time. We asked specific questions about how they handle scope change, estimate work, and communicate problems. The answers were consistent across everyone we spoke to, which suggested the process was real rather than sales-trained.

How clearly did the company understand your requirements and business goals?

Thoroughly. The requirements document they produced was detailed enough that our QA team used it directly to write acceptance criteria. Every story had a defined business outcome attached. Nothing was left to interpretation, which paid dividends all the way through to testing.

How was your overall experience with their communication and project management?

The most structured project management I have experienced with an external vendor. Sprint planning was tight, acceptance criteria were specific, retrospectives were honest and acted on. The PM treated the risk register as an operational tool, not a compliance document. I never had to ask for a status update.

Did the company deliver the project on time and within your expected budget?

Delivered on time. We had one week of unplanned delay due to an external API issue that neither party controlled. They communicated it early, proposed a workaround, and the launch date stayed the same. That is how delays should be managed.

What tangible results or business impact have you seen since the project was completed?

The ROI case we presented to the board was intentionally conservative. We are tracking to hit the payback point in under twelve months against an eighteen-month model. The efficiency gains have exceeded the forecast, partly because the data quality the new system produces enables decisions the previous one could not support.

What did you like most about working with this company?

Team continuity. The engineers who ran the discovery sessions built the system. That consistency over a five-month engagement is valuable in ways that are hard to articulate until you have worked on projects where it was absent. Every conversation built on the previous ones.

Would you recommend this company to others, and would you work with them again?

Yes. The value starts in the discovery phase — clients who invest time in that process will get the most out of the engagement. We did and it is evident in what was delivered.

Please describe your company, your role, and the industry you operate in.

I am the Chief Data Officer at Zenith FinServ Ltd, a Automotive company headquartered in Bangalore, India. My role covers product, platform, and the vendor partnerships that support them. We had reached a point where our internal team could not execute our roadmap fast enough without outside help.

What specific problem or business challenge led you to hire this company?

A competitor move accelerated our timeline by six months. A Cybersecurity investment that had been planned for next year suddenly needed to happen now. Internal build was not viable — we needed to find the right external team quickly.

What services did the company provide for your project?

The stated scope was Cybersecurity delivery. In practice they also contributed to product strategy conversations, flagged gaps in our requirements, and produced integration documentation that our partner vendors later told us was unusually thorough.

Why did you choose this company over other providers you considered?

The questions they asked during the briefing were the first signal. Vendors who ask precise questions in the sales process tend to apply the same discipline during delivery. The technical proposal was detailed, the team was senior, and the pricing was transparent. All three were factors.

How clearly did the company understand your requirements and business goals?

Thoroughly. The requirements document they produced was detailed enough that our QA team used it directly to write acceptance criteria. Every story had a defined business outcome attached. Nothing was left to interpretation, which paid dividends all the way through to testing.

How was your overall experience with their communication and project management?

Communication was proactive and well-calibrated. Technical detail for the engineering audience, executive summaries for the steering group, and risks raised with proposed mitigations rather than just problem statements. The fortnightly sprint reviews kept our stakeholders informed without pulling them into every working session.

Did the company deliver the project on time and within your expected budget?

Yes. The estimates they provided during scoping proved accurate throughout delivery, which is rare. Most vendor estimates start optimistic and drift. These did not.

What tangible results or business impact have you seen since the project was completed?

Hard to isolate perfectly given other business variables, but the metrics attributable to the Cybersecurity work are meaningful — session time up, conversion up, error rate down, NPS for the digital channel improved by double digits. Account managers say it is coming up positively in client conversations for the first time.

What did you like most about working with this company?

They kept the business objective visible throughout technical decision-making. I have worked with excellent engineers who lose the strategic thread as complexity increases. This team maintained a clear link between every architectural choice and the outcome we had agreed to achieve.

Would you recommend this company to others, and would you work with them again?

Yes, without reservation. I have already referred two peers in the Automotive sector who were facing similar Cybersecurity challenges. I gave those referrals confidently because I know the experience I described was not a one-off — it reflects how they work.

Please describe your company, your role, and the industry you operate in.

TechLyon SAS is a mid-size Events & Event Management business in Lyon, France. I joined as Co-Founder & CTO two years ago specifically to modernise how we build and buy technology. This engagement was part of that programme.

What specific problem or business challenge led you to hire this company?

A competitor move accelerated our timeline by six months. A IT Managed Services investment that had been planned for next year suddenly needed to happen now. Internal build was not viable — we needed to find the right external team quickly.

What services did the company provide for your project?

Full IT Managed Services lifecycle — discovery, architecture, development across ten sprints, integration testing, performance validation, production deployment, and a four-week hypercare period. They also produced system documentation and ran structured knowledge transfer sessions for our team.

Why did you choose this company over other providers you considered?

We had been through a failed engagement the year before and took vendor selection seriously this time. We asked specific questions about how they handle scope change, estimate work, and communicate problems. The answers were consistent across everyone we spoke to, which suggested the process was real rather than sales-trained.

How clearly did the company understand your requirements and business goals?

Very well. The discovery process was more thorough than anything we had experienced before. They challenged requirements that were vague, proposed better alternatives where our thinking was limiting, and produced a spec that our stakeholders agreed was the clearest articulation of the product they had ever seen written down.

How was your overall experience with their communication and project management?

The most structured project management I have experienced with an external vendor. Sprint planning was tight, acceptance criteria were specific, retrospectives were honest and acted on. The PM treated the risk register as an operational tool, not a compliance document. I never had to ask for a status update.

Did the company deliver the project on time and within your expected budget?

On time. Budget was within the approved ceiling, including one scope addition we introduced mid-project that was quoted fairly and handled in parallel without affecting the main delivery stream. No surprises at invoice stage.

What tangible results or business impact have you seen since the project was completed?

Hard to isolate perfectly given other business variables, but the metrics attributable to the IT Managed Services work are meaningful — session time up, conversion up, error rate down, NPS for the digital channel improved by double digits. Account managers say it is coming up positively in client conversations for the first time.

What did you like most about working with this company?

The fact that problems surfaced upward before they became crises. I have worked on enough vendor engagements to know that the ability to manage upward — to raise bad news early rather than bury it — is genuinely rare. This team did it consistently.

Would you recommend this company to others, and would you work with them again?

Yes. The value starts in the discovery phase — clients who invest time in that process will get the most out of the engagement. We did and it is evident in what was delivered.

Please describe your company, your role, and the industry you operate in.

Catalonia Digital SL is a mid-size Healthcare business in Barcelona, Spain. I joined as Head of Digital Products two years ago specifically to modernise how we build and buy technology. This engagement was part of that programme.

What specific problem or business challenge led you to hire this company?

Our previous vendor had left us with three years of accumulated technical debt. Delivery velocity had dropped to maybe a third of what it should have been. We needed new engineering eyes and a structured plan to dig out.

What services did the company provide for your project?

End-to-end Quality Assurance & Testing delivery with particular focus on the data migration and integration workstreams, which carried the highest project risk. A dedicated QA resource was embedded throughout development and they left us with a proper operations runbook at handover.

Why did you choose this company over other providers you considered?

The questions they asked during the briefing were the first signal. Vendors who ask precise questions in the sales process tend to apply the same discipline during delivery. The technical proposal was detailed, the team was senior, and the pricing was transparent. All three were factors.

How clearly did the company understand your requirements and business goals?

Extremely well — partly because they had enough Healthcare context to ask the right questions without us having to explain the basics. The functional spec translated our business requirements into technical language with a precision that meant the development phase had almost no clarification cycles.

How was your overall experience with their communication and project management?

Communication was proactive and well-calibrated. Technical detail for the engineering audience, executive summaries for the steering group, and risks raised with proposed mitigations rather than just problem statements. The fortnightly sprint reviews kept our stakeholders informed without pulling them into every working session.

Did the company deliver the project on time and within your expected budget?

Yes. I had privately planned for a contingency given the integration complexity involved. None of it was needed. Final invoice came in within rounding of the approved budget and we launched on the agreed date. That outcome is less common than vendors would have you believe.

What tangible results or business impact have you seen since the project was completed?

Five months post-launch: zero P1 incidents, Core Web Vitals in the green, and two enterprise clients who had been citing platform limitations in renewal conversations have since renewed without raising the issue. The system is doing what we needed it to do.

What did you like most about working with this company?

Honestly, the quality of the questions they asked. It sounds simple but good questions at the start of a project make everything easier. Their discovery process was better than any briefing our internal team would have run independently.

Would you recommend this company to others, and would you work with them again?

Yes. The value starts in the discovery phase — clients who invest time in that process will get the most out of the engagement. We did and it is evident in what was delivered.

Please describe your company, your role, and the industry you operate in.

I am the Head of Digital Products at Arc-en-Ciel Digital SAS, a Insurance company headquartered in Bordeaux, France. My role covers product, platform, and the vendor partnerships that support them. We had reached a point where our internal team could not execute our roadmap fast enough without outside help.

What specific problem or business challenge led you to hire this company?

A competitor move accelerated our timeline by six months. A CMS Development investment that had been planned for next year suddenly needed to happen now. Internal build was not viable — we needed to find the right external team quickly.

What services did the company provide for your project?

The core engagement was CMS Development delivery. During discovery they also provided technical consultancy that materially improved our requirements — things we would not have caught until development if they had not raised them. They also took ownership of the third-party integrations that had caused problems in previous projects.

Why did you choose this company over other providers you considered?

We shortlisted five vendors. Two were eliminated immediately based on the technical proposals. Of the remaining three, this team's CMS Development approach was the most specific and evidenced — actual Insurance reference cases, not generic slides. The reference calls confirmed what the proposal described.

How clearly did the company understand your requirements and business goals?

Very well. The discovery process was more thorough than anything we had experienced before. They challenged requirements that were vague, proposed better alternatives where our thinking was limiting, and produced a spec that our stakeholders agreed was the clearest articulation of the product they had ever seen written down.

How was your overall experience with their communication and project management?

I used to chase status updates weekly on vendor engagements. This was the first time I did not have to. Updates came consistently, problems surfaced early, and the shared project board always reflected reality rather than optimism.

Did the company deliver the project on time and within your expected budget?

Delivered on time. We had one week of unplanned delay due to an external API issue that neither party controlled. They communicated it early, proposed a workaround, and the launch date stayed the same. That is how delays should be managed.

What tangible results or business impact have you seen since the project was completed?

We went live six weeks ago so it is early. The launch was clean, adoption is tracking ahead of plan, and the first client demo of the new platform generated a positive reaction we had not seen for the previous version. Ask me again in six months and I will have better numbers.

What did you like most about working with this company?

The fact that problems surfaced upward before they became crises. I have worked on enough vendor engagements to know that the ability to manage upward — to raise bad news early rather than bury it — is genuinely rare. This team did it consistently.

Would you recommend this company to others, and would you work with them again?

Yes, without reservation. I have already referred two peers in the Insurance sector who were facing similar CMS Development challenges. I gave those referrals confidently because I know the experience I described was not a one-off — it reflects how they work.