Lansa Inc. Reviews

CI/CD pipeline that transformed how our engineering team thinks about release risk

Flynn Buchanan / GM of Technology - Pacific Rim Commerce Group

Verified
Jun 11, 2026

Project summary: First notice of loss processing was taking three days on average. Market benchmarks were under four hours. Automation of the intake and triage workflow was the agreed priority.

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

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

Overall

4.0

Quality

4.5

Schedule

4.0

Cost

4.0

Communication

Project TypeDevOps Services

IndustryInsurance

Project Cost$10,000 to $49,999

DurationSep 2025 – Mar 2026

Questions & Answers

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

Pacific Rim Commerce Group is an established Insurance organisation headquartered in Perth, Australia. My role as GM of Technology 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 Insurance market but lacked the engineering depth internally to execute it. The DevOps 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?

Primarily DevOps Services, 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?

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 DevOps Services approach and the evidence base they provided — reference projects in Insurance 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?

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?

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

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.

Multi-region setup that has delivered 99.97 percent uptime since go-live

Beatriz Cavalcanti / Chief Digital Officer - Cerrado Tech SA

Verified
Jun 10, 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.

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

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

3.5

Quality

4.0

Schedule

4.0

Cost

4.0

Communication

Project TypeCloud Services

IndustryMining & Metals

Project Cost$10,000 to $49,999

DurationAug 2025 – Apr 2026

Questions & Answers

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

As Chief Digital Officer at Cerrado Tech SA I oversee technology investment and delivery across our Mining & Metals operations in Brasília, Brazil. 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?

The immediate problem was that our Cloud 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?

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?

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?

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

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

Zara Hussain / Head of Technology - Ravi Digital Agency

Verified
Apr 30, 2026

Project summary: First notice of loss processing was taking three days on average. Market benchmarks were under four hours. Automation of the intake and triage workflow was the agreed priority.

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

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

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

Quality

3.5

Schedule

3.5

Cost

4.0

Communication

Project TypePOS System Development

IndustryInsurance

Project Cost$50,000 to $149,999

DurationSep 2025 – Mar 2026

Questions & Answers

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

Ravi Digital Agency is an established Insurance organisation headquartered in Lahore, Pakistan. My role as Head of Technology 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?

A competitive threat had accelerated our roadmap. We had planned a significant POS System 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?

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

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?

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

Analytics infrastructure that made our data science team genuinely productive for the first time

Imogen Tanner / Head of Engineering - Outback Data Solutions

Verified
Apr 05, 2026

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

We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.

PROS

Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes

CONS

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

Cost

4.0

Communication

Project TypeData & Analytics

IndustryNonprofit & NGO

Project Cost$10,000 to $49,999

DurationJul 2025 – Jan 2026

Questions & Answers

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

Outback Data Solutions is an established Nonprofit & NGO organisation headquartered in Melbourne, Australia. My role as Head 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 Nonprofit & NGO segment had changed and the compliance timeline was set by our regulator, not by us. The Data & Analytics changes required were significant enough to justify engaging a specialist partner rather than diverting our internal team from the product roadmap.

What services did the company provide for your project?

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

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

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?

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

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

Eoghan Fitzgerald / VP of Engineering - Shannon Tech Solutions Ltd

Verified
Feb 27, 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

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

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

Schedule

4.5

Cost

3.5

Communication

Project TypeMobile App Development

IndustryAutomotive

Project Cost$150,000 to $499,999

DurationSep 2025 – Dec 2025

Questions & Answers

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

I lead technology at Shannon Tech Solutions Ltd, a growth-stage Automotive business based in Dublin, Ireland. As VP of Engineering 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 Automotive 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?

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

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

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

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

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

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

Yuki Hashimoto / Head of Product Development - East Asia Commerce KK

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

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

Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes

CONS

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

4.0

Overall

3.5

Quality

4.0

Schedule

4.5

Cost

4.0

Communication

Project TypeMobile App Development

IndustryInformation Technology

Project CostLess than $10,000

DurationMar 2025 – Oct 2025

Questions & Answers

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

As Head of Product Development at East Asia Commerce KK I oversee technology investment and delivery across our Information Technology operations in Osaka, Japan. 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 Information Technology 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?

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

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

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

Outstanding. The discipline around asynchronous communication was particularly effective given the time zones involved between Osaka, Japan 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. 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 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 Mobile App Development programme in the Information Technology space and will deliver against a serious brief, this is the team.

Lansa Inc.

About Lansa Inc.

Where We Specialize

Industry Expertise

Typical Project Size