Diimtech Reviews

The first content management system we have deployed that editors genuinely prefer

Nathan Prescott / VP of Technology - Ironclad Insurance Group

Verified
May 05, 2026

Project summary: Our internal product thinking was strong but our execution capability in this specific technology domain was limited. We needed depth, not generalism.

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

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

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

5.0

Overall

5.0

Quality

5.0

Schedule

5.0

Cost

5.0

Communication

Project TypeCMS Development

IndustryHuman Resources

Project Cost$10,000 to $49,999

DurationJun 2025 – Apr 2026

Questions & Answers

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

As VP of Technology at Ironclad Insurance Group I oversee technology investment and delivery across our Human Resources operations in New York, USA. 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 Human Resources segment had changed and the compliance timeline was set by our regulator, not by us. The CMS 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 core engagement was CMS 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?

A trusted peer in the Human Resources 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 Human Resources 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. 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 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 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?

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 CMS Development programme in the Human Resources space and will deliver against a serious brief, this is the team.

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

Sabrina Vollmer / Chief Innovation Officer - Rheintal Digital AG

Verified
Apr 23, 2026

Project summary: Lean manufacturing initiatives required real-time OEE data at the line level. Our existing systems could not provide it without significant manual aggregation.

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

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

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

5.0

Cost

4.5

Communication

Project TypeLow-Code / No-Code Development

IndustryManufacturing

Project CostLess than $10,000

DurationOct 2025 – Feb 2026

Questions & Answers

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

I lead technology at Rheintal Digital AG, a growth-stage Manufacturing business based in Düsseldorf, Germany. As Chief Innovation 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?

The immediate problem was that our Low-Code / No-Code 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 Low-Code / No-Code 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?

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?

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?

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?

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?

Quantifying the impact precisely is complicated by other variables in our business, but the metrics we can attribute directly to the Low-Code / No-Code Development 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?

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 Manufacturing sector looking for Low-Code / No-Code Development expertise combined with genuine delivery discipline, I would put this team at the top of the evaluation list.

Tokenisation project that went from whitepaper to mainnet without a single major incident

Imogen Tanner / Head of Engineering - Outback Data Solutions

Verified
Apr 15, 2026

Project summary: B2B customer churn was concentrated among accounts that had complained about portal usability. We needed a complete redesign of the self-service experience before the next contract renewal cycle.

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

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

Communication

Project TypeBlockchain Development

IndustryTelecommunications

Project Cost$500,000+

DurationNov 2025 – Feb 2026

Questions & Answers

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

As Head of Engineering at Outback Data Solutions I oversee technology investment and delivery across our Telecommunications operations in Melbourne, Australia. 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?

A competitive threat had accelerated our roadmap. We had planned a significant Blockchain 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 Blockchain 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 Blockchain Development approach and the evidence base they provided — reference projects in Telecommunications 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 Melbourne, Australia 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 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?

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 Blockchain Development programme in the Telecommunications space and will deliver against a serious brief, this is the team.

An app our customers return to daily — the engagement numbers speak for themselves

Kelsey Drummond / Director of Digital Health - Crestline Health Partners

Verified
Apr 01, 2026

Project summary: As a technology business ourselves we apply the same scrutiny to our vendor selection that our clients apply to us. We needed a delivery partner who could meet a standard we would be comfortable being measured against.

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

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

Their insistence on a detailed functional specification before development began felt like friction at the time. In retrospect, it was the reason the development phase ran without the ambiguity that has derailed similar projects for us previously

4.5

Overall

5.0

Quality

5.0

Schedule

4.0

Cost

4.0

Communication

Project TypeMobile App Development

IndustryInformation Technology

Project Cost$150,000 to $499,999

DurationOct 2025 – Jan 2026

Questions & Answers

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

I lead technology at Crestline Health Partners, a growth-stage Information Technology business based in Houston, USA. As Director of Digital Health 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?

We had a defined product vision for our next phase of growth in the Information Technology market but lacked the engineering depth internally to execute it. The Mobile App Development requirements in particular required specialist experience that we could not realistically recruit for on the timeline our business plan required.

What services did the company provide for your project?

The core engagement was Mobile App 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?

A trusted peer in the Information Technology 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?

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?

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?

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 Mobile App Development 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.

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

Liselotte Bakker / Head of Platform Engineering - Harbour Digital BV

Verified
Feb 07, 2026

Project summary: Our campaign management workflow had grown to involve twelve different tools and significant manual reconciliation. The inefficiency was affecting both speed and accuracy.

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

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

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

5.0

Quality

4.0

Schedule

4.5

Cost

4.5

Communication

Project TypeMobile App Development

IndustryAdvertising & Marketing

Project Cost$150,000 to $499,999

DurationSep 2025 – Jan 2026

Questions & Answers

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

Harbour Digital BV is an established Advertising & Marketing organisation headquartered in Utrecht, Netherlands. My role as Head of Platform Engineering 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?

We had a defined product vision for our next phase of growth in the Advertising & Marketing market but lacked the engineering depth internally to execute it. The Mobile App Development requirements in particular required specialist experience that we could not realistically recruit for on the timeline our business plan required.

What services did the company provide for your project?

The scope covered the full Mobile App 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 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.