Strategic Solutions NW
Overall Review Rating
4.8 (7 Ratings)
Services
- DevOps & Cloud
- MVP Development
- Platform Development
- MySQL
- Mobile App Development
- Business Analysis & Consulting
- Cross Platform Development
- AngularJS Development
- Web Development
- Android App Development
- Drupal
- iOS App Development
Industries Served
Strategic Solutions NW Reviews
Have a look at these client reviews on previously delivered projects.
Maja Söderström
Head of Product Engineering - Scandia Digital ABReal-time dashboards that finance and operations both agree on. That alone was worth it.
We handed them an aggressive deadline, a complex scope, and a client-side team that was stretched and not always available when they needed us. They handled that gracefully. They were precise about what they needed and when they needed it. Where they could proceed independently they did. The delivery landed on time in spite of the constraints we added. I regard that as strong evidence of genuine professional maturity — not just capability.
Project summary
Our mobile app sat at 2.9 stars. Every negative review mentioned the same two things — speed and checkout complexity. Both were fixable with the right engineering approach.
Yuki Hashimoto
Head of Product Development - East Asia Commerce KKPlatform that our fulfilment team, finance team, and customers all rate highly
The part of this project I had been most worried about was the integration work. Our system landscape is complex, some of the upstream APIs were barely documented, and one of our third-party vendors was notoriously slow to respond. This team documented what the upstream vendors could not, built resilience into the architecture where third-party reliability was uncertain, and delivered integrations that have worked exactly as specified since day one. I genuinely could not have asked for more.
Project summary
Multi-touch attribution across our full media mix was the most consistently requested capability by every client in our book. We could not deliver it without rebuilding the data foundation.
Sarah Kimball
Product Manager - Clearpath Health SolutionsCloud architecture built properly the first time. We did not have to go back and fix it.
The technical quality is the obvious thing to highlight. The automated test suite is comprehensive, the deployment pipeline is solid, and the documentation is actually useful rather than written to satisfy a checklist. But the metric I keep coming back to is what has NOT happened since go-live. No 2am incident calls. No emergency patches. No post-launch retrospectives about what went wrong. For a system of this complexity, that outcome is exactly what we paid for.
Project summary
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Niamh O'Sullivan
Director of Product - Munster Digital LtdOur support ticket volume dropped 20% after the UX overhaul. Proof is in the numbers.
I have been through several technology implementations in my career. The pattern I am used to is: detailed proposal, optimistic timeline, scope creep, overrun, excuses at the end. This engagement broke that pattern at every stage. The timeline was realistic from the start. Changes were managed through process. The final delivery matched what was agreed. Simple, but uncommon.
Project summary
OTA update orchestration for our software-defined vehicles needed to be bulletproof. The liability implications of getting it wrong were significant enough to justify specialist development.
Kenji Watanabe
Senior Engineering Manager - Fuji Software CorpOur engineering team reviewed the handover codebase and was impressed. That rarely happens.
Looking back, what strikes me most is how little drama there was. Real technology projects have problems. This one had them too — but every problem was flagged before it became a crisis, every scope change was handled through a proper process, and every risk was managed rather than buried. Our project manager said it was the smoothest vendor engagement he had been involved in. Given how complex the technical requirements were, I think that reflects genuine delivery maturity.
Project summary
Seven years of incremental changes had left our trading platform fragile. Latency was worsening, technical debt was growing, and the rebuild conversation had been postponed long enough.