Devlogiq

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

Salam Digital Solutions operates in the Government & Public Sector sector out of Jeddah, Saudi Arabia. In my role as VP of Engineering 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?

Low-Code / No-Code Development design and build, plus the performance testing that revealed an architecture concern we needed to address before launch. The testing investment paid for itself. They also handled the deployment pipeline and monitoring configuration, which our internal team had not budgeted time for.

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 Low-Code / No-Code Development approach was the most specific and evidenced — actual Government & Public Sector reference cases, not generic slides. The reference calls confirmed what the proposal described.

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?

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. 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?

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?

The post-launch engagement. Some vendors treat go-live as the end of their obligation. This team treated it as a transition to a different kind of engagement. Hypercare was substantive, documentation was genuinely useful, and they checked in proactively at thirty and ninety days.

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.

Seoul Digital Corp operates in the Financial Services sector out of Seoul, South Korea. In my role as VP of Engineering 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 Digital Marketing capability had become the bottleneck for everything. Feature requests, client requirements, internal initiatives — all of them were queuing behind a platform we had patched past its design limits. We needed a proper rebuild.

What services did the company provide for your project?

Full Digital Marketing 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?

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?

Very strong on the async side, which mattered given the time difference between Seoul, South Korea and the delivery team. Written updates were specific and consistent, decisions got responses the same day, and nothing was dropped across a five-month engagement. That discipline is harder than it looks.

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?

Biggest impact: our internal team is no longer spending three days a week maintaining a platform they hated working with. That productivity is now going into building. The platform change was as much about our engineering team's quality of life as it was about the end user.

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?

Yes, without reservation. I have already referred two peers in the Financial Services sector who were facing similar Digital Marketing 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.

Arc-en-Ciel Digital SAS is a Agriculture business based in Bordeaux, France. As Head of Digital Products, I own the technology strategy and vendor relationships. Every spending decision gets evaluated against a concrete business case — we do not invest in technology for its own sake.

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

Compliance requirements in our Agriculture space changed and the deadline was set by our regulator, not by us. The Data & Analytics work required was specialist enough that pulling our internal team off the product roadmap to do it was not an option.

What services did the company provide for your project?

Data & Analytics design and build, plus the performance testing that revealed an architecture concern we needed to address before launch. The testing investment paid for itself. They also handled the deployment pipeline and monitoring configuration, which our internal team had not budgeted time for.

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?

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?

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?

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?

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. 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 SVP of Engineering at Vertex Cloud Dynamics, a Automotive company headquartered in Austin, TX, 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?

Our Web Development capability had become the bottleneck for everything. Feature requests, client requirements, internal initiatives — all of them were queuing behind a platform we had patched past its design limits. We needed a proper rebuild.

What services did the company provide for your project?

End-to-end Web Development 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?

We had a fixed budget and a non-negotiable timeline. Several vendors told us it could not be done. These were the ones who said it could and explained clearly why. They turned out to be right.

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

Extremely well — partly because they had enough Automotive 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?

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. 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?

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?

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.

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

As VP of Engineering at Adriatic Tech Srl, a Financial Services organisation in Milan, Italy, I manage technology investment and delivery outcomes. We make commercial decisions about technology — every project needs a credible case before it gets approved.

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?

Low-Code / No-Code Development design and build, plus the performance testing that revealed an architecture concern we needed to address before launch. The testing investment paid for itself. They also handled the deployment pipeline and monitoring configuration, which our internal team had not budgeted time for.

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

We had a fixed budget and a non-negotiable timeline. Several vendors told us it could not be done. These were the ones who said it could and explained clearly why. They turned out to be right.

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?

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?

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?

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 Financial Services sector who were facing similar Low-Code / No-Code Development challenges. I gave those referrals confidently because I know the experience I described was not a one-off — it reflects how they work.