Separate the roles, connect the booking
Customers get a focused public booking page; providers get availability and appointment controls. The same booking model connects both experiences.
Back to all projects
Shipfire Product · Service booking platform
okDuo
From a broad platform idea to a focused path for making and managing a booking.
Project focus
- Booking
- MVP scope
- UX architecture
The product we set out to build.
okDuo started with two connected needs: customers wanted an easy way to book, and independent providers needed to manage their availability. The product could quickly grow into a much larger platform.
We defined the first milestone around a confirmed appointment. The work connected service setup, available times, public booking and provider management, giving the first release a clear boundary.
The constraints that shaped the work.
The boundaries that mattered
- Let customers complete a booking before creating an account
- Make provider setup fast enough for a solo operator
- Avoid premature payments, team management and marketplace features
- Use one availability model across public and provider-facing experiences
The decisions behind the product.
Resolve the rules before the screens
We defined how service length, working hours and blocked time determine available slots. The interface could then reflect a consistent set of rules.
Give the first version a stopping point
Payments, teams and advanced reporting stayed outside the initial scope. We concentrated on the path from finding a provider to confirming a time.
One booking. Two connected experiences.
- Create a provider profile and define services
- Set recurring availability and block unavailable time
- Share a public booking page
- Select a service, date and available appointment
- Review, confirm and manage upcoming bookings
Next project / 04Pitchforge