Private page. Shared directly, not listed on the site. Please do not forward.
Concierge Plus · Property software

The software still worked like the binder.

A property management platform had digitised the front desk binder without questioning any of it. Residents took two minutes to book a room and often failed late in the flow.

80%Faster bookingAbout 2:00 down to 0:24
30%Fewer support ticketsClient reported
7→1Screens to complete a bookingWith every option on, which was rare
RoleLead product designer
Team1 design, engineering partners
UsersResidents, security, property managers, board
ShippediOS, Android and web
The diagnosis

Every project turns on one question: is the obvious explanation the right one?

What everyone assumed

The flow is too long. Cut steps and completion will improve.

What was actually wrong

Length was a symptom. The real failure was that availability was checked late, only after a room was chosen and the details were in. With every option switched on, a booking could run to seven screens before the resident found out the slot was taken. Cutting steps without moving that check would have produced a faster way to fail.

I read the support tickets. Many asked staff to book for them, or asked whether a booking had gone through.

The calls I made

Show availability first

The booking opens on a visual time strip with taken slots already greyed out.A conflict discovered at the end is a wasted trip. A conflict shown at the start is just information.

Fill in what the system already knows

Unit, resident and deposit come pre-filled from the account.Four of the seven original screens asked for data the system already held. That is not a user problem.

Say when approval is not needed

The screen states plainly that a free slot needs no approval.Many tickets asked whether a booking had gone through. The answer belonged on the screen.

What shipped
One booking flow, same peopleSeven screens

Seven screenswalking the old flow

1234567 · ConflictOne screen · availability firsttakentakentakenBookedcalled the desk instead

Before, up to seven screens with the conflict surfacing late. After, one screen with conflicts visible up front.

The argument redrawn: a playhead runs down the fields and hits the conflict late, then the check itself moves to the front and the same run clears in one pass.

Seven fieldsFilling

Seven fieldstyped one by one

Unitfrom accountResidentfrom accountDepositfrom accountAvailability checked hereFirst, not lastSame form. Different order.
Nate reimagined and designed an updated interface for our product and worked with our developer team to ensure everything ended up pixel perfect.

Peter Pietrzkiewicz · Founder, Concierge Plus

If this sounds familiar

Before you shorten a flow, find the step where people quit. Shortening a flow that fails at the end just gets users to the failure faster.

Have a problem like this one?

Send a link and a sentence. If I can help, I will record a teardown. If I cannot, I will say so.

Start a conversation