Euda Reviews

Headless CMS that finally allowed our designers and developers to work in parallel

Takashi Morimoto / Director of IT Strategy - Sakura Digital KK

Verified
May 31, 2026

Project summary: A previous engagement had delivered something that worked in staging and struggled in production. We approached this project with greater rigour in vendor selection as a result.

The thing that retrospectively seems most significant is how little drama there was. Complex technology projects tend to accumulate incidents, escalations, and tense conversations. This one did not. Problems were surfaced before they became incidents. Scope changes were handled with process rather than conflict. Risks were managed rather than avoided. That level of maturity is rare in my experience and it made the delivery feel almost effortless from our side, which I know it was not from theirs.

PROS

Senior-level engineering presence throughout the entire project, not just during the pitch, honest and commercially fair handling of scope changes, codebase that our internal team praised on review

CONS

Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project

4.5

Overall

4.0

Quality

4.5

Schedule

4.5

Cost

4.5

Communication

Project TypeCMS Development

IndustryConstruction

Project Cost$150,000 to $499,999

DurationDec 2025 – May 2026

Questions & Answers

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

Sakura Digital KK is an established Construction organisation headquartered in Tokyo, Japan. My role as Director of IT Strategy covers both strategic planning and operational technology delivery. We maintain high standards for our vendors because our clients hold us to high standards — a bar we expect our partners to meet.

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

The immediate problem was that our CMS Development capability had become the bottleneck limiting our ability to grow. Every feature request, every new client requirement, every internal initiative was delayed by a platform that had been extended beyond its original design. We needed a rebuild, not a patch.

What services did the company provide for your project?

End-to-end CMS Development delivery with particular depth in the integration and data migration components, which were the highest-risk elements of the programme. They supplemented this with a dedicated QA resource throughout development and a documented runbook for our operations team at handover.

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

A trusted peer in the Construction sector had used them for a comparable CMS Development engagement and their recommendation was unequivocal. Our own due diligence confirmed the pattern they described. The combination of domain knowledge, CMS Development depth, and demonstrated delivery discipline was the deciding factor.

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

Extremely well, in part because they had relevant Construction experience that reduced the context-setting overhead significantly. They understood the domain vocabulary, asked the right questions, and translated business requirements into technical specifications with a fidelity that meant the development phase had very few clarification cycles.

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

Outstanding. The discipline around asynchronous communication was particularly effective given the time zones involved between Tokyo, Japan and the delivery team. Written updates were specific and consistent, response times were same-day for anything that required a decision, and nothing fell through the cracks across a six-month engagement.

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

Yes to both. There was a single sprint where a dependency on a third-party API introduced a one-week delay. The team identified it three weeks in advance, presented two mitigation options, and we agreed on an approach that recovered the schedule within the same sprint cycle. That level of foresight is what separates good project management from reactive problem management.

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

The ROI case we presented to our board was conservative by design. Current performance against the financial model suggests we will hit the projected payback point in under twelve months against an eighteen-month target. The operational efficiency gains in particular have exceeded the model, in part because the quality of the data the new platform generates supports decisions that the previous system could not.

What did you like most about working with this company?

The willingness to be direct. When our requirements were unclear they said so. When our priorities were contradictory they explained why. When a technical approach we had assumed was the right one turned out to have significant downsides, they told us before we had committed to it. That kind of intellectual honesty is what I look for in a long-term technology partner.

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

Unreservedly. We are in active scoping conversations for a second engagement and I expect this to develop into a multi-year partnership. For any organisation in the Construction sector looking for CMS Development expertise combined with genuine delivery discipline, I would put this team at the top of the evaluation list.

A partnership that began with a single project and earned a place on our preferred vendor list

Bram de Vries / Chief Technology Officer - Windmill Tech BV

Verified
Apr 26, 2026

Project summary: Our actuarial models had outgrown the reporting infrastructure feeding them. Data latency was introducing risk into pricing decisions that the business had decided it could no longer accept.

Six months after go-live our platform is processing three times the transaction volume we specified in the original brief. The architecture choices made during discovery accommodated that growth without remediation work. That is the difference between a team that designs for what you tell them and a team that designs for what you are likely to need. We are in conversation about a Phase 2 engagement and I expect to be using this partnership for several years.

PROS

Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes

CONS

Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project

4.5

Overall

4.0

Quality

4.5

Schedule

4.5

Cost

5.0

Communication

Project TypePOS System Development

IndustryInsurance

Project Cost$500,000+

DurationOct 2025 – Feb 2026

Questions & Answers

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

Windmill Tech BV operates in the Insurance sector with headquarters in Amsterdam, Netherlands. In my role as Chief Technology Officer I am accountable for the full technology agenda — infrastructure, product, and vendor relationships. We are a commercially driven organisation and every technology decision is evaluated against a clear business case before it is approved.

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

The immediate problem was that our POS System Development capability had become the bottleneck limiting our ability to grow. Every feature request, every new client requirement, every internal initiative was delayed by a platform that had been extended beyond its original design. We needed a rebuild, not a patch.

What services did the company provide for your project?

The core engagement was POS System Development delivery, though their scope expanded to include technical consultancy during discovery that materially improved our requirements. They also took ownership of the third-party integration workstream that had been a coordination challenge in previous projects, removing that complexity from our internal team entirely.

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

We had a failed engagement behind us and were more rigorous in our selection process as a result. We asked detailed questions about how they managed scope change, how they handled estimation, and how they communicated problems. The answers were specific, evidenced, and consistent across the team members we spoke to. That gave us confidence that the process was real rather than rehearsed.

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

Thoroughly and precisely. The requirements document they produced was detailed enough that our QA team used it directly to write acceptance criteria. Every user story had a defined business objective attached. Nothing was left to interpretation. That discipline in the requirements phase paid dividends throughout development and testing.

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

Professional and efficient. The project manager maintained a clear view of the critical path at all times and communicated changes to it transparently. The one significant scope adjustment we made mid-project was handled through a clean change request process — fairly priced, clearly documented, and absorbed without disrupting the overall timeline.

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

The project landed on time. The budget was managed within the agreed ceiling, which included one client-driven scope addition that was quoted fairly and handled without affecting the original delivery stream. The discipline around budget transparency throughout meant there was no surprise at invoice stage.

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

The most direct measure is the performance of the system in production. In the five months since go-live we have had zero P1 incidents, our page performance scores have improved across every Core Web Vitals metric, and two enterprise clients who had cited our previous platform limitations during contract negotiations have since renewed without that objection arising.

What did you like most about working with this company?

Their instinct for keeping the business objective visible throughout technical decision-making. I have worked with technically excellent teams who lose the strategic thread as complexity increases. This team maintained a clear connection between every architectural choice and the outcome we had agreed to achieve. That orientation made the trade-off conversations significantly easier.

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

Absolutely. With a specific note that the value starts in the discovery phase — clients who approach that process with seriousness will get the most from the engagement. We invested appropriately at the front end and the returns are evident in what was delivered.

App store launch with a four-point-eight average rating in the first month

Imogen Tanner / Head of Engineering - Outback Data Solutions

Verified
Apr 17, 2026

Project summary: Regulatory submission timelines required a document management platform that could handle version control, access permissions, and audit trails at a scale our existing tools were not designed for.

What made the most difference in practice was the quality of the engineering judgment on this team. Not the ability to execute a specification — that is a baseline expectation. The ability to recognise when a specification was suboptimal, explain why, propose an alternative, and support the client in making a decision about it. That consultative dimension elevated the output beyond what the brief described and resulted in a product that is more fit for purpose than the one we had originally specified.

PROS

Clear and consistent communication adapted appropriately for both technical and non-technical stakeholders, shared tooling that gave our team real-time visibility, reliable sprint delivery throughout

CONS

The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism

4.5

Overall

4.5

Quality

4.5

Schedule

5.0

Cost

4.0

Communication

Project TypeMobile App Development

IndustryPharmaceuticals & Biotechnology

Project Cost$500,000+

DurationMay 2025 – Feb 2026

Questions & Answers

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

Outback Data Solutions operates in the Pharmaceuticals & Biotechnology sector with headquarters in Melbourne, Australia. In my role as Head of Engineering I am accountable for the full technology agenda — infrastructure, product, and vendor relationships. We are a commercially driven organisation and every technology decision is evaluated against a clear business case before it is approved.

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

The immediate problem was that our Mobile App Development capability had become the bottleneck limiting our ability to grow. Every feature request, every new client requirement, every internal initiative was delayed by a platform that had been extended beyond its original design. We needed a rebuild, not a patch.

What services did the company provide for your project?

Primarily Mobile App Development, with adjacent work in solution architecture and quality assurance. They were responsible for the full build from requirements through to go-live, including integration with four existing systems in our technology landscape. The breadth they covered without requiring additional vendors was commercially and logistically valuable.

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

A trusted peer in the Pharmaceuticals & Biotechnology sector had used them for a comparable Mobile App Development engagement and their recommendation was unequivocal. Our own due diligence confirmed the pattern they described. The combination of domain knowledge, Mobile App Development depth, and demonstrated delivery discipline was the deciding factor.

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

Extremely well, in part because they had relevant Pharmaceuticals & Biotechnology experience that reduced the context-setting overhead significantly. They understood the domain vocabulary, asked the right questions, and translated business requirements into technical specifications with a fidelity that meant the development phase had very few clarification cycles.

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

Communication was proactive, timely, and appropriately calibrated. Technical updates for the engineering audience, executive summaries for the steering group, risk flags with proposed mitigations rather than just problem statements. The fortnightly sprint reviews gave our stakeholders visibility without requiring them to attend every working session.

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

On time and within the approved budget. The estimation accuracy was notable — they had broken the work down in sufficient detail during discovery that their forecast proved reliable throughout, rather than being a number that shifted with every change in scope. We received one change request and it was for scope we had introduced ourselves.

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

The ROI case we presented to our board was conservative by design. Current performance against the financial model suggests we will hit the projected payback point in under twelve months against an eighteen-month target. The operational efficiency gains in particular have exceeded the model, in part because the quality of the data the new platform generates supports decisions that the previous system could not.

What did you like most about working with this company?

Their instinct for keeping the business objective visible throughout technical decision-making. I have worked with technically excellent teams who lose the strategic thread as complexity increases. This team maintained a clear connection between every architectural choice and the outcome we had agreed to achieve. That orientation made the trade-off conversations significantly easier.

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

Yes, without reservation. I have already made two direct referrals within my Pharmaceuticals & Biotechnology network — in both cases to peers facing Mobile App Development challenges similar to ours. I gave those referrals with confidence because I knew the experience I described was reproducible, not the result of exceptional circumstances on our engagement.

Custom modules that fit our operational processes rather than forcing us to change them

Maja Söderström / Head of Product Engineering - Scandia Digital AB

Verified
Mar 27, 2026

Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.

We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.

PROS

Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes

CONS

The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism

4.5

Overall

4.5

Quality

4.5

Schedule

5.0

Cost

5.0

Communication

Project TypeERP Development

IndustryMining & Metals

Project Cost$50,000 to $149,999

DurationMar 2025 – Dec 2025

Questions & Answers

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

Scandia Digital AB operates in the Mining & Metals sector with headquarters in Gothenburg, Sweden. In my role as Head of Product Engineering I am accountable for the full technology agenda — infrastructure, product, and vendor relationships. We are a commercially driven organisation and every technology decision is evaluated against a clear business case before it is approved.

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

The immediate problem was that our ERP Development capability had become the bottleneck limiting our ability to grow. Every feature request, every new client requirement, every internal initiative was delayed by a platform that had been extended beyond its original design. We needed a rebuild, not a patch.

What services did the company provide for your project?

The core engagement was ERP Development delivery, though their scope expanded to include technical consultancy during discovery that materially improved our requirements. They also took ownership of the third-party integration workstream that had been a coordination challenge in previous projects, removing that complexity from our internal team entirely.

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

We had a failed engagement behind us and were more rigorous in our selection process as a result. We asked detailed questions about how they managed scope change, how they handled estimation, and how they communicated problems. The answers were specific, evidenced, and consistent across the team members we spoke to. That gave us confidence that the process was real rather than rehearsed.

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

Comprehensively. The discovery phase they ran was more thorough than anything we had experienced with previous vendors. They challenged requirements that were vague or contradictory, proposed alternatives where our initial thinking was limiting, and produced a functional specification that our internal stakeholders agreed was the clearest articulation of the product they had seen written down.

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

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

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

Yes to both. There was a single sprint where a dependency on a third-party API introduced a one-week delay. The team identified it three weeks in advance, presented two mitigation options, and we agreed on an approach that recovered the schedule within the same sprint cycle. That level of foresight is what separates good project management from reactive problem management.

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

The ROI case we presented to our board was conservative by design. Current performance against the financial model suggests we will hit the projected payback point in under twelve months against an eighteen-month target. The operational efficiency gains in particular have exceeded the model, in part because the quality of the data the new platform generates supports decisions that the previous system could not.

What did you like most about working with this company?

Their instinct for keeping the business objective visible throughout technical decision-making. I have worked with technically excellent teams who lose the strategic thread as complexity increases. This team maintained a clear connection between every architectural choice and the outcome we had agreed to achieve. That orientation made the trade-off conversations significantly easier.

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

Absolutely. With a specific note that the value starts in the discovery phase — clients who approach that process with seriousness will get the most from the engagement. We invested appropriately at the front end and the returns are evident in what was delivered.

Custom modules that fit our operational processes rather than forcing us to change them

Niamh O'Sullivan / Director of Product - Munster Digital Ltd

Verified
Feb 27, 2026

Project summary: Several years of incremental development had left us with a platform that was technically functional but strategically limiting. A structured rebuild was the agreed path forward.

The thing that retrospectively seems most significant is how little drama there was. Complex technology projects tend to accumulate incidents, escalations, and tense conversations. This one did not. Problems were surfaced before they became incidents. Scope changes were handled with process rather than conflict. Risks were managed rather than avoided. That level of maturity is rare in my experience and it made the delivery feel almost effortless from our side, which I know it was not from theirs.

PROS

Clear and consistent communication adapted appropriately for both technical and non-technical stakeholders, shared tooling that gave our team real-time visibility, reliable sprint delivery throughout

CONS

We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs

4.5

Overall

4.5

Quality

4.5

Schedule

4.5

Cost

4.0

Communication

Project TypeERP Development

IndustryMining & Metals

Project Cost$10,000 to $49,999

DurationJul 2025 – Nov 2025

Questions & Answers

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

I lead technology at Munster Digital Ltd, a growth-stage Mining & Metals business based in Limerick, Ireland. As Director of Product my remit spans product engineering, platform operations, and strategic vendor partnerships. We had reached an inflection point where our internal capacity was not sufficient to execute our roadmap at the pace our market required.

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

Regulatory requirements in our Mining & Metals segment had changed and the compliance timeline was set by our regulator, not by us. The ERP Development changes required were significant enough to justify engaging a specialist partner rather than diverting our internal team from the product roadmap.

What services did the company provide for your project?

End-to-end ERP Development delivery with particular depth in the integration and data migration components, which were the highest-risk elements of the programme. They supplemented this with a dedicated QA resource throughout development and a documented runbook for our operations team at handover.

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

We had a failed engagement behind us and were more rigorous in our selection process as a result. We asked detailed questions about how they managed scope change, how they handled estimation, and how they communicated problems. The answers were specific, evidenced, and consistent across the team members we spoke to. That gave us confidence that the process was real rather than rehearsed.

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

Better than we managed ourselves going in. The workshops they facilitated surfaced assumptions we had not examined and exposed three requirements that were in direct conflict with each other. Resolving those before development began saved us what would certainly have been significant rework later in the project.

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

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

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

Yes. I had privately built a contingency expectation into my planning given the project complexity and the number of integrations involved. None of that contingency was needed. The delivery landed on the agreed date and the final invoice matched the approved budget to within a fraction of a percent. That outcome is rarer than the industry acknowledges.

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

The most direct measure is the performance of the system in production. In the five months since go-live we have had zero P1 incidents, our page performance scores have improved across every Core Web Vitals metric, and two enterprise clients who had cited our previous platform limitations during contract negotiations have since renewed without that objection arising.

What did you like most about working with this company?

Their instinct for keeping the business objective visible throughout technical decision-making. I have worked with technically excellent teams who lose the strategic thread as complexity increases. This team maintained a clear connection between every architectural choice and the outcome we had agreed to achieve. That orientation made the trade-off conversations significantly easier.

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

Yes, without reservation. I have already made two direct referrals within my Mining & Metals network — in both cases to peers facing ERP Development challenges similar to ours. I gave those referrals with confidence because I knew the experience I described was reproducible, not the result of exceptional circumstances on our engagement.

Multi-region setup that has delivered 99.97 percent uptime since go-live

Marcus Holloway / SVP of Engineering - Vertex Cloud Dynamics

Verified
Feb 03, 2026

Project summary: Digital-first buyer behaviour had made our property search experience a genuine competitive liability. We needed it to match the quality of the portfolio it was representing.

We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.

PROS

Delivery timeline that proved achievable rather than optimistic, estimation accuracy that reflected real analysis rather than competitive bidding, scope discipline that prevented the feature creep we had experienced before

CONS

Pipeline availability for kickoff required a few weeks of lead time — in hindsight that selection pressure means you are working with a team that is in demand for the right reasons

4.5

Overall

4.5

Quality

4.5

Schedule

4.5

Cost

4.5

Communication

Project TypeCloud Services

IndustryReal Estate

Project CostLess than $10,000

DurationMay 2025 – Jan 2026

Questions & Answers

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

I lead technology at Vertex Cloud Dynamics, a growth-stage Real Estate business based in Austin, USA. As SVP of Engineering my remit spans product engineering, platform operations, and strategic vendor partnerships. We had reached an inflection point where our internal capacity was not sufficient to execute our roadmap at the pace our market required.

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

The immediate problem was that our Cloud Services capability had become the bottleneck limiting our ability to grow. Every feature request, every new client requirement, every internal initiative was delayed by a platform that had been extended beyond its original design. We needed a rebuild, not a patch.

What services did the company provide for your project?

End-to-end Cloud Services delivery with particular depth in the integration and data migration components, which were the highest-risk elements of the programme. They supplemented this with a dedicated QA resource throughout development and a documented runbook for our operations team at handover.

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

We had a failed engagement behind us and were more rigorous in our selection process as a result. We asked detailed questions about how they managed scope change, how they handled estimation, and how they communicated problems. The answers were specific, evidenced, and consistent across the team members we spoke to. That gave us confidence that the process was real rather than rehearsed.

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

Better than we managed ourselves going in. The workshops they facilitated surfaced assumptions we had not examined and exposed three requirements that were in direct conflict with each other. Resolving those before development began saved us what would certainly have been significant rework later in the project.

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

Outstanding. The discipline around asynchronous communication was particularly effective given the time zones involved between Austin, USA and the delivery team. Written updates were specific and consistent, response times were same-day for anything that required a decision, and nothing fell through the cracks across a six-month engagement.

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

The project landed on time. The budget was managed within the agreed ceiling, which included one client-driven scope addition that was quoted fairly and handled without affecting the original delivery stream. The discipline around budget transparency throughout meant there was no surprise at invoice stage.

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

The most direct measure is the performance of the system in production. In the five months since go-live we have had zero P1 incidents, our page performance scores have improved across every Core Web Vitals metric, and two enterprise clients who had cited our previous platform limitations during contract negotiations have since renewed without that objection arising.

What did you like most about working with this company?

Their instinct for keeping the business objective visible throughout technical decision-making. I have worked with technically excellent teams who lose the strategic thread as complexity increases. This team maintained a clear connection between every architectural choice and the outcome we had agreed to achieve. That orientation made the trade-off conversations significantly easier.

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

Yes. I would add the context that this is not the cheapest option in the market and they are selective about the engagements they take on. If your primary criterion is price, there are alternatives. If you want a technology partner who can be trusted with a complex Cloud Services programme in the Real Estate space and will deliver against a serious brief, this is the team.

The outcome we specified, delivered the way we needed it, by people we would hire again

Dominic Fairfax / Head of Digital Transformation - Arcadian Consulting Ltd

Verified
Jan 29, 2026

Project summary: Cross-agency data sharing had been blocked by incompatible systems for four years. A secure integration platform was the prerequisite for every transformation initiative in our roadmap.

I came into this engagement as a sceptic. We had been through a failed implementation with a previous vendor and I had high standards for what evidence of competence looked like before I would trust a partner with our core systems. This team earned that trust progressively — through the quality of the discovery documentation, the rigour of the technical proposals, the consistency of the sprint deliveries, and ultimately the stability of the production system. I no longer lead with scepticism when recommending them.

PROS

Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring

CONS

Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project

4.5

Overall

4.5

Quality

4.0

Schedule

5.0

Cost

4.5

Communication

Project TypeLow-Code / No-Code Development

IndustryGovernment & Public Sector

Project CostLess than $10,000

DurationMay 2025 – Nov 2025

Questions & Answers

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

As Head of Digital Transformation at Arcadian Consulting Ltd I oversee technology investment and delivery across our Government & Public Sector operations in London, UK. We are a commercially focused business and our technology choices are always evaluated in terms of their direct contribution to business outcomes rather than technical elegance alone.

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

Regulatory requirements in our Government & Public Sector segment had changed and the compliance timeline was set by our regulator, not by us. The Low-Code / No-Code Development changes required were significant enough to justify engaging a specialist partner rather than diverting our internal team from the product roadmap.

What services did the company provide for your project?

Primarily Low-Code / No-Code Development, with adjacent work in solution architecture and quality assurance. They were responsible for the full build from requirements through to go-live, including integration with four existing systems in our technology landscape. The breadth they covered without requiring additional vendors was commercially and logistically valuable.