Yashi Tech India Reviews

Infrastructure-as-code that our SRE team treats as a reference example

Reuben Loh / CTO - Marina Bay Ventures Pte Ltd

Verified
May 21, 2026

Project summary: Matter management had become a significant overhead for our fee earners. Every hour spent on administration was an hour not spent on billable advisory work — the business case was straightforward.

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

Quality

4.5

Schedule

4.5

Cost

4.5

Communication

Project TypeCloud Services

IndustryLegal Services

Project Cost$50,000 to $149,999

DurationAug 2025 – Feb 2026

Questions & Answers

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

As CTO at Marina Bay Ventures Pte Ltd I oversee technology investment and delivery across our Legal Services operations in Singapore. 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 Legal Services market but lacked the engineering depth internally to execute it. The Cloud Services 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 Cloud 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?

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?

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

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.

Publishing workflow that took our time-to-live from days to under an hour

Marcus Holloway / SVP of Engineering - Vertex Cloud Dynamics

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

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

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

CONS

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

IndustryInformation Technology

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.

Vertex Cloud Dynamics is an established Information Technology organisation headquartered in Austin, USA. My role as SVP 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 Information Technology 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 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?

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

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

Project execution that matched the proposal in every dimension that mattered

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

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

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

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

Cost

4.0

Communication

Project TypeIndustry-Specific Solutions

IndustryEvents & Event Management

Project Cost$10,000 to $49,999

DurationOct 2025 – Feb 2026

Questions & Answers

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

As Head of Product Engineering at Scandia Digital AB I oversee technology investment and delivery across our Events & Event Management operations in Gothenburg, Sweden. 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 Events & Event Management market but lacked the engineering depth internally to execute it. The Industry-Specific Solutions 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 Industry-Specific Solutions 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?

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

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

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

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

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

What did you like most about working with this company?

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

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

Yes, without reservation. I have already made two direct referrals within my Events & Event Management network — in both cases to peers facing Industry-Specific Solutions 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.

Test automation that our developers adopted as a genuine aid rather than a compliance exercise

Théo Beaumont / VP of Innovation - Laurentian Tech Partners

Verified
Feb 01, 2026

Project summary: Our trading platform had been extended incrementally for seven years. Latency was degrading, technical debt was compounding, and a clean rebuild was no longer optional.

The technical quality of the final deliverable is the easiest thing to point to. The automated test coverage is thorough, the deployment pipeline is reliable, the documentation is genuinely useful rather than ceremonially produced. But the metric I keep returning to is the number of post-launch conversations we have not had to have. No incident calls at two in the morning. No emergency patches. No retrospective discussions about what went wrong. The absence of those events is the evidence I would show to someone considering this vendor.

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

5.0

Cost

4.0

Communication

Project TypeQuality Assurance & Testing

IndustryFinancial Services

Project Cost$150,000 to $499,999

DurationMar 2025 – Dec 2025

Questions & Answers

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

I lead technology at Laurentian Tech Partners, a growth-stage Financial Services business based in Montreal, Canada. As VP of Innovation my remit spans product engineering, platform operations, and strategic vendor partnerships. We had reached an inflection point where our internal capacity was not sufficient to execute our roadmap at the pace our market required.

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

Regulatory requirements in our Financial Services segment had changed and the compliance timeline was set by our regulator, not by us. The Quality Assurance & Testing 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 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.

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.