Exato Software Reviews

Monetisation system integrated in a way that players accepted rather than resented

Marcus Holloway / SVP of Engineering - Vertex Cloud Dynamics

Verified
Apr 15, 2026

Project summary: Unplanned downtime had become our single largest cost driver and our data showed that predictive maintenance could address the majority of it — if we had the right infrastructure to act on it.

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

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

4.5

Quality

4.5

Schedule

4.5

Cost

4.0

Communication

Project TypeGame Development

IndustryManufacturing

Project Cost$150,000 to $499,999

DurationOct 2025 – Mar 2026

Questions & Answers

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

As SVP of Engineering at Vertex Cloud Dynamics I oversee technology investment and delivery across our Manufacturing operations in Austin, 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?

We had a defined product vision for our next phase of growth in the Manufacturing market but lacked the engineering depth internally to execute it. The Game 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?

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

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?

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?

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 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, without reservation. I have already made two direct referrals within my Manufacturing network — in both cases to peers facing Game 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.

Mixed reality build that landed exactly where the brief pointed and then went further

Declan Hartley / Chief Digital Officer - Southern Cross Technology

Verified
Apr 02, 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.

The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.

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

Quality

4.5

Schedule

4.0

Cost

5.0

Communication

Project TypeAR/VR Development

IndustryNonprofit & NGO

Project Cost$500,000+

DurationJun 2025 – Mar 2026

Questions & Answers

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

I lead technology at Southern Cross Technology, a growth-stage Nonprofit & NGO business based in Sydney, Australia. As Chief Digital 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?

We had a defined product vision for our next phase of growth in the Nonprofit & NGO market but lacked the engineering depth internally to execute it. The AR/VR 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?

End-to-end AR/VR 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?

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?

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?

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 Nonprofit & NGO network — in both cases to peers facing AR/VR 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.

Security posture transformed from a known liability to a competitive differentiator

Lars Pfeiffer / VP of Technology - NordTech Logistik GmbH

Verified
Apr 02, 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.

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

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

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

Schedule

5.0

Cost

5.0

Communication

Project TypeCybersecurity

IndustryNonprofit & NGO

Project Cost$50,000 to $149,999

DurationOct 2025 – Feb 2026

Questions & Answers

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

As VP of Technology at NordTech Logistik GmbH I oversee technology investment and delivery across our Nonprofit & NGO operations in Hamburg, Germany. 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?

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?

Primarily Cybersecurity, 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?

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?

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 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. 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 Cybersecurity programme in the Nonprofit & NGO space and will deliver against a serious brief, this is the team.

Project execution that matched the proposal in every dimension that mattered

Sebastian Lapointe / CTO - Boreal Systems Inc

Verified
Mar 26, 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.

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

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

4.5

Cost

4.5

Communication

Project TypeLow-Code / No-Code Development

IndustryEnvironmental Services

Project Cost$50,000 to $149,999

DurationJul 2025 – Dec 2025

Questions & Answers

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

Boreal Systems Inc operates in the Environmental Services sector with headquarters in Toronto, Canada. 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?

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?

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?

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?

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 Low-Code / No-Code Development programme in the Environmental Services space and will deliver against a serious brief, this is the team.

Observability stack that caught three production issues before any user reported them

Matthieu Renard / Directeur Technique - Lumière Technologies SAS

Verified
Mar 24, 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.

The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.

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

The engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk

4.5

Overall

5.0

Quality

4.5

Schedule

4.5

Cost

4.5

Communication

Project TypeDevOps Services

IndustryAutomotive

Project CostLess than $10,000

DurationAug 2025 – Dec 2025

Questions & Answers

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

Lumière Technologies SAS operates in the Automotive 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?

Regulatory requirements in our Automotive segment had changed and the compliance timeline was set by our regulator, not by us. The DevOps Services 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 DevOps Services 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 Automotive sector had used them for a comparable DevOps Services engagement and their recommendation was unequivocal. Our own due diligence confirmed the pattern they described. The combination of domain knowledge, DevOps Services 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?

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

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 Automotive network — in both cases to peers facing DevOps Services 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.

A QA partner who treated our product quality as a personal responsibility

Zofia Kamińska / CTO - Odra Tech Studio

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

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

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

4.5

Schedule

4.5

Cost

4.0

Communication

Project TypeQuality Assurance & Testing

IndustryMining & Metals

Project Cost$500,000+

DurationFeb 2025 – Nov 2025

Questions & Answers

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

Odra Tech Studio is an established Mining & Metals organisation headquartered in Wrocław, Poland. My role as 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?

We had a defined product vision for our next phase of growth in the Mining & Metals market but lacked the engineering depth internally to execute it. The Quality Assurance & Testing 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 Quality Assurance & Testing 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.