Wave Reviews

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

Zofia Kamińska / CTO - Odra Tech Studio

Verified
Jun 10, 2026

Project summary: Grid modernisation funding required us to demonstrate demand-response capability. The machine learning models existed on paper; we needed an engineering partner to build and productionise them.

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

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 quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism

4.0

Overall

4.0

Quality

3.5

Schedule

4.0

Cost

4.0

Communication

Project TypeMobile App Development

IndustryEnergy & Utilities

Project Cost$500,000+

DurationNov 2025 – May 2026

Questions & Answers

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

Odra Tech Studio operates in the Energy & Utilities sector with headquarters in Wrocław, Poland. 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?

Regulatory requirements in our Energy & Utilities 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?

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 Mobile App Development approach and the evidence base they provided — reference projects in Energy & Utilities 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?

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

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

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

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

Yes 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 Energy & Utilities network — in both cases to peers facing Mobile App 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.

Cloud architecture that reduced our monthly infrastructure spend by over a third

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

Verified
Jun 03, 2026

Project summary: Our field service management system had not been updated significantly in six years. Rising technician count and increasing job complexity had exposed every one of its limitations.

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

Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism

CONS

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

4.0

Quality

4.5

Schedule

4.5

Cost

4.5

Communication

Project TypeCloud Services

IndustryEnergy & Utilities

Project Cost$50,000 to $149,999

DurationSep 2025 – May 2026

Questions & Answers

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

I lead technology at Scandia Digital AB, a growth-stage Energy & Utilities business based in Gothenburg, Sweden. As Head of Product 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?

A competitive threat had accelerated our roadmap. We had planned a significant Cloud Services investment for the following year. External pressure moved that timeline forward by six months and required us to find an external partner rather than attempting to build internally in the time available.

What services did the company provide for your project?

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

A trusted peer in the Energy & Utilities sector had used them for a comparable Cloud Services engagement and their recommendation was unequivocal. Our own due diligence confirmed the pattern they described. The combination of domain knowledge, Cloud Services depth, and demonstrated delivery discipline was the deciding factor.

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?

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?

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.

Design work that measurably improved every conversion metric on our platform

Sebastian Lapointe / CTO - Boreal Systems Inc

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

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

Overall

4.5

Quality

4.0

Schedule

4.0

Cost

4.0

Communication

Project TypeUI/UX Design

IndustryHealthcare

Project CostLess than $10,000

DurationOct 2025 – Feb 2026

Questions & Answers

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

Boreal Systems Inc operates in the Healthcare 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?

A competitive threat had accelerated our roadmap. We had planned a significant UI/UX Design investment for the following year. External pressure moved that timeline forward by six months and required us to find an external partner rather than attempting to build internally in the time available.

What services did the company provide for your project?

The core engagement was UI/UX Design 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?

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?

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

Business system that replaced seven legacy tools and consolidated our data model entirely

Imogen Tanner / Head of Engineering - Outback Data Solutions

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

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

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

Quality

4.5

Schedule

4.5

Cost

4.5

Communication

Project TypeERP Development

IndustryEvents & Event Management

Project CostLess than $10,000

DurationMar 2025 – Jan 2026

Questions & Answers

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

Outback Data Solutions is an established Events & Event Management 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 Events & Event Management segment had changed and the compliance timeline was set by our regulator, not by us. The ERP 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 ERP 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?

Comprehensively. The discovery phase they ran was more thorough than anything we had experienced with previous vendors. They challenged requirements that were vague or contradictory, proposed alternatives where our initial thinking was limiting, and produced a functional specification that our internal stakeholders agreed was the clearest articulation of the product they had seen written down.

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

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

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

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

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 Events & Event Management sector looking for ERP Development expertise combined with genuine delivery discipline, I would put this team at the top of the evaluation list.

Content platform our editorial team adopted without a single escalated support request

Flynn Buchanan / GM of Technology - Pacific Rim Commerce Group

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

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

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

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

4.5

Schedule

4.5

Cost

4.5

Communication

Project TypeCMS Development

IndustryInsurance

Project Cost$50,000 to $149,999

DurationJun 2025 – Mar 2026

Questions & Answers

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

I lead technology at Pacific Rim Commerce Group, a growth-stage Insurance business based in Perth, Australia. As GM of Technology 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?

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?

End-to-end CMS 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.