Please describe your company, your role, and the industry you operate in.
Tasman Commerce Group is a Retail & E-commerce business headquartered in Melbourne, Australia. As GM of Technology I'm responsible for the whole technology agenda — infrastructure, product, and how we pick vendors. Every decision we make on the technology side has to tie back to a clear business case before it gets approved.
What specific problem or business challenge led you to hire this company?
Regulation in our Retail & E-commerce segment shifted and the compliance deadline came from the regulator, not from us. The scale of the IoT Development changes required justified bringing in a specialist rather than pulling our internal team off the product roadmap to handle it.
What services did the company provide for your project?
The scope ran the full IoT Development lifecycle — discovery, requirements, architecture, development across roughly a dozen sprints, integration testing, performance validation, deployment, and a four-week hypercare window afterward. They also handed over full documentation and ran a knowledge transfer session for our internal team.
Why did you choose this company over other providers you considered?
The questions they asked during the briefing stage told us most of what we needed to know. Vendors who ask sharp questions during sales tend to bring that same rigor into delivery, and that held up. The technical proposal had real substance, the team was senior from the start, and the pricing was straightforward.
How clearly did the company understand your requirements and business goals?
Thoroughly. The requirements document was detailed enough that our own QA team used it directly to build acceptance criteria. Every user story had a clear business reason attached, and nothing was left open to interpretation. That discipline early on paid off through the rest of development and testing.
How was your overall experience with their communication and project management?
Genuinely excellent, especially given the time difference between Melbourne, Australia and the delivery team. Written updates were consistent and specific, anything needing a decision got same-day turnaround, and nothing slipped through the cracks across the whole engagement.
Did the company deliver the project on time and within your expected budget?
Both, yes. One sprint hit a one-week delay from a third-party API dependency outside anyone's control. The team flagged it three weeks ahead of time, laid out two options, and we picked an approach that clawed the schedule back within the same sprint. That's the kind of foresight that separates real project management from just reacting to problems.
What tangible results or business impact have you seen since the project was completed?
We went live about three months ago. User adoption beat the target we'd set by roughly 20 percent in the first month, and support ticket volume has dropped noticeably since. Features we'd shelved because the old architecture made them too expensive to build are now back on the roadmap.
What did you like most about working with this company?
What they did after launch. A lot of vendors treat go-live as the finish line. This team treated it as the start of a different phase — the hypercare period was substantial, the documentation held up in practice, and they checked back in at the thirty and ninety day marks to go over production metrics with us unprompted.
Would you recommend this company to others, and would you work with them again?
Absolutely, with one caveat worth mentioning: the value really starts in discovery, so clients who take that phase seriously will get the most out of it. We put real effort in upfront and it clearly paid off in what got delivered.