ZedStack Reviews

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

Reuben Loh / CTO - Marina Bay Ventures Pte Ltd

Verified
May 28, 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.

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

Production system that has performed as specified since go-live without remediation work, documentation thorough enough to support internal maintenance, knowledge transfer that left our team genuinely capable

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

5.0

Schedule

5.0

Cost

4.5

Communication

Project TypeCMS Development

IndustryEvents & Event Management

Project Cost$500,000+

DurationNov 2025 – Apr 2026

Questions & Answers

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

Marina Bay Ventures Pte Ltd operates in the Events & Event Management sector with headquarters in Singapore. In my role as CTO 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?

A competitive threat had accelerated our roadmap. We had planned a significant CMS Development investment for the following year. External pressure moved that timeline forward by six months and required us to find an external partner rather than attempting to build internally in the time available.

What services did the company provide for your project?

The scope covered the full CMS Development lifecycle: discovery and requirements definition, solution architecture, iterative development across twelve sprints, integration testing, performance validation, production deployment, and a structured four-week hypercare period. They also provided system documentation and a knowledge transfer programme for our internal team.

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

A trusted peer in the Events & Event Management 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 Events & Event Management 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?

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

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?

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.

IT partner embedded deeply enough to understand our business, not just our ticket queue

Erik Lindqvist / Chief Technology Officer - Nordic Cloud AB

Verified
Apr 05, 2026

Project summary: The project had a board-facing delivery date tied to a strategic initiative. We needed a partner who would treat that date as their own, not ours.

Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.

PROS

Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism

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

5.0

Schedule

4.5

Cost

5.0

Communication

Project TypeIT Managed Services

IndustryEnvironmental Services

Project Cost$150,000 to $499,999

DurationAug 2025 – Feb 2026

Questions & Answers

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

I lead technology at Nordic Cloud AB, a growth-stage Environmental Services business based in Stockholm, Sweden. As Chief Technology Officer 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?

Our platform had been maintained by a previous vendor for three years and the accumulated technical debt had reached a point where delivery velocity had dropped to a fraction of what it should have been. We needed fresh engineering expertise and a structured plan to address the underlying issues.

What services did the company provide for your project?

The scope covered the full IT Managed Services lifecycle: discovery and requirements definition, solution architecture, iterative development across twelve sprints, integration testing, performance validation, production deployment, and a structured four-week hypercare period. They also provided system documentation and a knowledge transfer programme for our internal team.

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?

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?

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

The continuity of the team. The engineers who participated in the discovery sessions were the engineers who built the system. That consistency of institutional knowledge across a six-month project has a value that is difficult to quantify but easy to notice when it is absent. Every conversation built on the previous ones.

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 Environmental Services sector looking for IT Managed Services expertise combined with genuine delivery discipline, I would put this team at the top of the evaluation list.

Technically rigorous, commercially grounded, and a genuine pleasure to work with

Hyun-Su Lim / Director of Platform - Hanam Tech Solutions

Verified
Mar 19, 2026

Project summary: The transition to EV had created demand for dealer network management capabilities our existing system was not designed to support. A targeted rebuild was the agreed path forward.

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

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

Quality

4.0

Schedule

5.0

Cost

4.0

Communication

Project TypeIndustry-Specific Solutions

IndustryAutomotive

Project Cost$150,000 to $499,999

DurationJul 2025 – Feb 2026

Questions & Answers

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

I lead technology at Hanam Tech Solutions, a growth-stage Automotive business based in Incheon, South Korea. As Director of Platform 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?

Our platform had been maintained by a previous vendor for three years and the accumulated technical debt had reached a point where delivery velocity had dropped to a fraction of what it should have been. We needed fresh engineering expertise and a structured plan to address the underlying issues.

What services did the company provide for your project?

The core engagement was Industry-Specific Solutions 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?

The quality of the questions they asked during the briefing process was the first indicator. Vendors who ask precise questions in the sales phase tend to apply the same rigour during delivery. That hypothesis proved accurate. The technical proposal was substantive, the team structure was senior throughout, and the pricing was transparent.

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

Extremely well, in part because they had relevant Automotive 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 Incheon, South Korea 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?

Quantifying the impact precisely is complicated by other variables in our business, but the metrics we can attribute directly to the Industry-Specific Solutions work are meaningful: session duration up, conversion rate up, error rate down, and our NPS for the digital touchpoint has improved by eleven points. Our account managers report that the new capability is coming up positively in client conversations.

What did you like most about working with this company?

The post-launch behaviour. Some vendors consider go-live to be the end of their professional obligation. This team treated it as the transition to a different kind of engagement. The hypercare period was substantive, the documentation was thorough and genuinely useful, and they checked in proactively at the thirty-day and ninety-day marks to review production metrics with us.

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

Siobhan Gallagher / Chief Technology Officer - Northumbria FinTech Ltd

Verified
Feb 12, 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.

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

Their discovery process is more rigorous than we were accustomed to and required more preparation from our side than we had initially allocated — but the quality of what followed justified every hour of it

4.5

Overall

4.5

Quality

4.0

Schedule

4.0

Cost

4.5

Communication

Project TypeERP Development

IndustryFashion & Apparel

Project Cost$500,000+

DurationFeb 2025 – Nov 2025

Questions & Answers

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

Northumbria FinTech Ltd is an established Fashion & Apparel organisation headquartered in Edinburgh, UK. My role as Chief Technology Officer 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?

Regulatory requirements in our Fashion & Apparel 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?

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

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?

Outstanding. The discipline around asynchronous communication was particularly effective given the time zones involved between Edinburgh, UK 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?

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

The post-launch behaviour. Some vendors consider go-live to be the end of their professional obligation. This team treated it as the transition to a different kind of engagement. The hypercare period was substantive, the documentation was thorough and genuinely useful, and they checked in proactively at the thirty-day and ninety-day marks to review production metrics with us.

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 Fashion & Apparel sector looking for ERP Development expertise combined with genuine delivery discipline, I would put this team at the top of the evaluation list.

Real-time dashboards that our executives now open before any other application

Matthieu Renard / Directeur Technique - Lumière Technologies SAS

Verified
Feb 05, 2026

Project summary: Rapid growth had created a skills gap on the platform engineering side of our business. We needed an experienced partner to close that gap while our internal team scaled, without compromising quality or timeline.

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

Production system that has performed as specified since go-live without remediation work, documentation thorough enough to support internal maintenance, knowledge transfer that left our team genuinely capable

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

Schedule

5.0

Cost

4.5

Communication

Project TypeData & Analytics

IndustryInformation Technology

Project CostLess than $10,000

DurationFeb 2025 – Dec 2025

Questions & Answers

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

Lumière Technologies SAS operates in the Information Technology sector with headquarters in Paris, France. In my role as Directeur Technique 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?

Our platform had been maintained by a previous vendor for three years and the accumulated technical debt had reached a point where delivery velocity had dropped to a fraction of what it should have been. We needed fresh engineering expertise and a structured plan to address the underlying issues.

What services did the company provide for your project?

End-to-end Data & Analytics 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 Information Technology sector had used them for a comparable Data & Analytics engagement and their recommendation was unequivocal. Our own due diligence confirmed the pattern they described. The combination of domain knowledge, Data & Analytics depth, and demonstrated delivery discipline was the deciding factor.

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?

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?

The continuity of the team. The engineers who participated in the discovery sessions were the engineers who built the system. That consistency of institutional knowledge across a six-month project has a value that is difficult to quantify but easy to notice when it is absent. Every conversation built on the previous ones.

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 Information Technology sector looking for Data & Analytics expertise combined with genuine delivery discipline, I would put this team at the top of the evaluation list.

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

Bilal Chaudhry / Co-Founder & CTO - Indus Software House

Verified
Jan 21, 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.

Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.

PROS

Architectural decisions designed for longevity rather than just the current brief, thorough automated test coverage, post-launch stability that validated every technical choice made during discovery

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

5.0

Quality

4.5

Schedule

4.0

Cost

5.0

Communication

Project TypeLow-Code / No-Code Development

IndustryConstruction

Project Cost$10,000 to $49,999

DurationJan 2025 – Nov 2025

Questions & Answers

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

Indus Software House is an established Construction organisation headquartered in Islamabad, Pakistan. My role as Co-Founder & CTO 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?

Regulatory requirements in our Construction 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?

The scope covered the full Low-Code / No-Code Development lifecycle: discovery and requirements definition, solution architecture, iterative development across twelve sprints, integration testing, performance validation, production deployment, and a structured four-week hypercare period. They also provided system documentation and a knowledge transfer programme for our internal team.

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

We ran a structured shortlisting process across five vendors. The technical evaluation eliminated two immediately. Of the remaining three, this team's proposal was differentiated by the specificity of their Low-Code / No-Code Development approach and the evidence base they provided — reference projects in Construction contexts, not generic case studies. The reference calls confirmed a track record that the proposal had described accurately.

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 Islamabad, Pakistan 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?

We went live four months ago. User adoption exceeded the target we had set by 23 percent in the first month. Support ticket volume has dropped measurably. The features we had deferred because the previous architecture made them prohibitively expensive to build are now in development. The platform they built has opened our roadmap.

What did you like most about working with this company?

The continuity of the team. The engineers who participated in the discovery sessions were the engineers who built the system. That consistency of institutional knowledge across a six-month project has a value that is difficult to quantify but easy to notice when it is 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 made two direct referrals within my Construction network — in both cases to peers facing Low-Code / No-Code 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.

ZedStack

About ZedStack

Where We Specialize

Industry Expertise

Typical Project Size