createIT.com

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

I am the Co-Founder & CTO at TechLyon SAS, a Food & Beverage company headquartered in Lyon, 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?

Our internal team was good but maxed out. The CMS Development work needed for this phase of the product required a depth of experience we did not have internally, and could not build in time.

What services did the company provide for your project?

Primarily CMS Development, 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 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 Food & Beverage reference cases, not generic slides. The reference calls confirmed what the proposal described.

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

Honestly, better than we understood them ourselves going in. The workshops they ran surfaced assumptions we had not examined and caught three requirements that were in direct conflict with each other. Resolving those before development started saved us a significant amount of rework.

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?

Yes on both. There was one sprint where a third-party API dependency introduced a one-week slip. They flagged it three weeks before it became critical, presented two options, and we agreed on one that recovered the timeline within the same sprint. That kind of foresight is the difference between good and average project management.

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, without reservation. I have already referred two peers in the Food & Beverage 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.

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

Prairie Tech Solutions Inc operates in the Aerospace & Defense sector out of Calgary, Canada. In my role as Senior Engineering Manager 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?

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?

Primarily UI/UX Design, 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?

The requirements process took longer than we expected but the thoroughness showed in the development phase — we had noticeably fewer mid-sprint clarifications and no major requirement changes that required rework.

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

Good. The sprint cadence worked well for our team. Fortnightly reviews gave us the checkpoints we needed. The one friction point — time zone overlap — was resolved after the first sprint and did not reoccur.

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

Yes on both. There was one sprint where a third-party API dependency introduced a one-week slip. They flagged it three weeks before it became critical, presented two options, and we agreed on one that recovered the timeline within the same sprint. That kind of foresight is the difference between good and average project management.

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

Four months live. User adoption exceeded our first-month target by around 20%. Support volume is down. Features we had deferred for years because the old architecture made them too expensive to build are now in active development. The platform opened our roadmap.

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?

Absolutely. We are scoping a second engagement and I expect this to become a multi-year partnership. For anyone in the Aerospace & Defense space looking for serious UI/UX Design delivery, I would put them at the top of the evaluation list.

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

I am the Chief Digital Officer at BlueSky Retail Holdings, a Food & Beverage company headquartered in Chicago, IL, USA. 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 Embedded Systems 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?

Full Embedded Systems Development 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?

Professional and efficient. The PM had a clear view of the critical path at all times and was transparent when anything threatened it. We made one significant scope change mid-project. It was handled through a proper change request, fairly priced, and absorbed without disrupting the delivery timeline.

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

Yes on both. There was one sprint where a third-party API dependency introduced a one-week slip. They flagged it three weeks before it became critical, presented two options, and we agreed on one that recovered the timeline within the same sprint. That kind of foresight is the difference between good and average project management.

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?

The directness. When our requirements were unclear, they said so. When our priorities were contradictory, they explained why. When a technical approach we assumed was right had significant downsides, they told us before we committed. That kind of honesty is what I actually want from a technology partner.

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

I already have. Three people in my network have used them based on my recommendation and all three have reported positively. That is the only endorsement that matters.

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

Rheintal Digital AG operates in the Legal Services sector out of Düsseldorf, Germany. In my role as Chief Innovation Officer 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?

Honestly, we had been deferring this Cloud Services investment for eighteen months. User feedback had been consistent and our conversion data confirmed the impact. We eventually ran out of reasons to delay.

What services did the company provide for your project?

The stated scope was Cloud Services 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?

Referral from someone whose technical judgment I trust. The due diligence we ran confirmed what we had been told. The proposal stage was also notably more thorough than the alternatives — they clearly understood the Cloud Services requirements better than the other vendors we evaluated.

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?

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?

Yes on both. There was one sprint where a third-party API dependency introduced a one-week slip. They flagged it three weeks before it became critical, presented two options, and we agreed on one that recovered the timeline within the same sprint. That kind of foresight is the difference between good and average project management.

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

Four months live. User adoption exceeded our first-month target by around 20%. Support volume is down. Features we had deferred for years because the old architecture made them too expensive to build are now in active development. The platform opened our roadmap.

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?

I already have. Three people in my network have used them based on my recommendation and all three have reported positively. That is the only endorsement that matters.