Case Study Deskcasestudydesk.com
Home-Services MarketplaceSourced

Case Study: Hipages cuts new-message launch time from four weeks to one day with Courier

Hipages Case StudySourced & dated by Case Study Desk
Key facts · TL;DR
Company
Hipages
Industry
Home-Services Marketplace
Challenge
Hipages' in-house notification system made shipping a new message type slow and error-prone as the marketplace grew.
Headline result
Hipages cut new-message launch time from four weeks to under one day and eliminated recurring deployment faults with Courier

Key results

1 day
New-message launch time
from four weeks
5-6
Deployment faults eliminated
per change, before Courier

The challenge

Hipages, an Australian home-services marketplace, had built its own notification system, but as the company grew the in-house tooling began to drag. Rolling out a new message type into the monolith took about four weeks and typically introduced five or six faults, and the team had no appetite to rebuild the fragile system again.

The solution

Hipages replaced its in-house system with Courier, moving message creation and routing onto a single platform. When it later needed to switch email providers from Mailgun to SendGrid, the team completed the migration in days.

It used to take four weeks to get a new message type into the monolith and probably about five or six faults. Post Courier, it takes less than one day, which is what you'd expect.

CB
Clayton Bell
Head of Platform, Hipages

The results, in context

With Courier, Hipages cut the time to launch a new message type from four weeks to less than one day and eliminated the critical bugs that previously accompanied each change. Messaging incidents, especially P1s and P2s, have nearly disappeared.

Products used

Courier CourierCourier Multi-channel notificationsCourier Provider integrations