Pyxl Reviews

Cloud migration completed without the chaos our previous attempt had produced

Kelsey Drummond / Director of Digital Health - Crestline Health Partners

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

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

PROS

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

Overall

4.0

Quality

3.5

Schedule

4.0

Cost

3.5

Communication

Project TypeCloud Services

IndustryConstruction

Project Cost$50,000 to $149,999

DurationApr 2025 – Feb 2026

Questions & Answers

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

Crestline Health Partners operates in the Construction sector with headquarters in Houston, USA. In my role as Director of Digital Health 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 Construction segment had changed and the compliance timeline was set by our regulator, not by us. The Cloud 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 Cloud 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?

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?

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

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

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

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

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?

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?

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

A technology investment that delivered returns ahead of the business case we approved

Zofia Kamińska / CTO - Odra Tech Studio

Verified
Apr 06, 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

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

CONS

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

Overall

4.0

Quality

4.5

Schedule

4.0

Cost

4.0

Communication

Project TypePOS System Development

IndustryMining & Metals

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.

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?

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

What services did the company provide for your project?

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

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

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

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

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

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

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

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

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

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

Aarav Mehta / Chief Data Officer - Zenith FinServ Ltd

Verified
Mar 20, 2026

Project summary: Remote care had gone from an experiment to a core service line and our technology had not kept pace. We needed a robust, compliant telehealth platform in a timeline that the market would not wait for.

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

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

Schedule

4.0

Cost

5.0

Communication

Project TypeDevOps Services

IndustryHealthcare

Project CostLess than $10,000

DurationJul 2025 – Jan 2026

Questions & Answers

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

Zenith FinServ Ltd is an established Healthcare organisation headquartered in Bangalore, India. My role as Chief Data 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?

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

What services did the company provide for your project?

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

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

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?

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

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

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

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

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?

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?

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.

Security team that communicated findings clearly to non-technical stakeholders — genuinely rare

Matthieu Renard / Directeur Technique - Lumière Technologies SAS

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

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

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

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

4.5

Overall

4.5

Quality

4.0

Schedule

5.0

Cost

4.5

Communication

Project TypeCybersecurity

IndustryFashion & Apparel

Project Cost$150,000 to $499,999

DurationMar 2025 – Jan 2026

Questions & Answers

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

I lead technology at Lumière Technologies SAS, a growth-stage Fashion & Apparel business based in Paris, France. As Directeur Technique 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 Fashion & Apparel market but lacked the engineering depth internally to execute it. The Cybersecurity 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 Cybersecurity 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?

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

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

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

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

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?

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 Fashion & Apparel network — in both cases to peers facing Cybersecurity 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.

The team understood mobile-first thinking before we finished the brief

Nisha Pillai / Director of Engineering - GrowthBridge Ventures

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

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

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

CONS

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

Overall

4.5

Quality

4.0

Schedule

4.0

Cost

3.5

Communication

Project TypeMobile App Development

IndustryHuman Resources

Project Cost$150,000 to $499,999

DurationJun 2025 – Dec 2025

Questions & Answers

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

GrowthBridge Ventures is an established Human Resources organisation headquartered in Pune, India. My role as Director of 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?

Regulatory requirements in our Human Resources segment had changed and the compliance timeline was set by our regulator, not by us. The Mobile App 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 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.

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?

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?

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

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

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

Nora Al-Otaibi / VP of Engineering - Salam Digital Solutions

Verified
Jan 19, 2026

Project summary: Our client portal had been built in 2017 and had not received meaningful investment since. Clients were contrasting it unfavourably with the portals of our competitors in pitches.

We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.

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

4.0

Schedule

4.5

Cost

4.5

Communication

Project TypeLow-Code / No-Code Development

IndustryLegal Services

Project Cost$500,000+

DurationJul 2025 – Dec 2025

Questions & Answers

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

Salam Digital Solutions is an established Legal Services organisation headquartered in Jeddah, Saudi Arabia. My role as VP of 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?

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