Case study • Snabbrent / Strykfrit
Snabbrent: booking and scheduling software for a cleaning business
From a local service company to an online product operating in Sweden: four user roles, a custom employee-availability engine and support for local payment requirements.
9 min read
8
Weekly sprints
4
User roles
Sweden
Launch market
Creating one shared view of the process
The Strykfrit project was an online system for a Swedish home-cleaning company. Before development, the team visualised the process in Miro and Moqups, then wrote user stories for four roles: guest, client, employee and manager.
Application views were designed only after the roles and journeys were agreed. That allowed the client to give feedback on wireframes before every change also carried a production-code cost.
Employee availability required a custom solution
The first assumption was to use the existing TimeWave product. The team built a proof of concept and tested its API. The experiment showed that scheduled time could not be changed in the way the product required.
Because no available solution met the need, GMI designed a custom scheduling module limited to the critical workflows. It solved the actual client and employee problems without trying to recreate a general-purpose calendar.
- Review available products and APIs first.
- Use a proof of concept for the build-versus-buy decision.
- Build only the scheduling functions the operation needs.
Payments and invoicing designed for Sweden
The system had to support more than booking. It also needed to match local expectations around payment and invoicing, including e-invoices and charge-by-invoice flows used in the market.
The lesson was that a payment provider cannot be selected only for integration convenience. It must fit customer behaviour and country-specific operating requirements.
A live booking product for the Scandinavian market
After eight weekly sprints, the team released a web application for booking and scheduling home-cleaning services. GMI supported the client from initial process sketches through to the live product.
The project also required a pause and backlog reset when easy features began displacing the largest risks. A transparent conversation with the client and a new priority order brought the work back to the critical scope.