Rebuilding a booking flow: 11 steps to 3

When we started working with Deem in 2018, their enterprise travel platform required 11 steps to complete a booking. Average booking time was 425 seconds. NPS sat at 19. For a platform serving over 300 enterprise clients, including Fortune 500 companies, these numbers represented a real problem.

Seven years later, the booking flow takes 3 steps. Average time is 127 seconds. NPS is 54. Adoption increased 47% in the first quarter after the redesigned platform launched. The work won over 20 industry awards.

This is how we got there.

Understanding the real problem

The surface problem was obvious: too many screens, too many clicks, too much friction. But enterprise travel is not consumer travel. A corporate booking involves policy enforcement, approval chains, expense integration, travel preferences, loyalty programs, and accessibility requirements. You can't just remove screens. You have to figure out which decisions can be automated, which can be deferred, and which genuinely require the traveler's input.

We spent the first three months observing. Not redesigning. Watching real users book real trips. The patterns were clear: most travelers book the same routes repeatedly. Most policy decisions have one correct answer. Most approval workflows are rubber stamps. The 11 steps existed because the system treated every booking like a novel event. It wasn't.

The design decisions

We collapsed the flow by identifying what could be pre-filled, what could be inferred, and what genuinely required a choice. Recent searches became the default starting point. Policy compliance checks moved to the background. Approval routing happened automatically based on rules rather than manual selection. The traveler only saw screens where their input changed the outcome.

The 3-step flow that emerged: search (with smart defaults), select (with policy-compliant options highlighted), and confirm. Everything else happens in the background.

Accessibility as architecture

Deem serves travelers with vision, hearing, motor, and cognitive impairments. Accessibility was not a compliance checkbox. It was an architectural decision. Every component in the design system was built with WCAG AA+ compliance from the start. When Apple later required specific accessibility standards for a custom deployment, our existing architecture met their requirements without a rebuild. That only happens when accessibility is structural, not decorative.

The outcome

425 seconds to 127. NPS 19 to 54. 47% adoption increase in the first quarter. 22 industry awards. But the metric that matters most to us: the engagement lasted 7 years. That kind of continuity means the team knows the product well enough to make good decisions fast. It means the client trusts the team enough to let them make those decisions.

The distance between wanting a flight and having a booking got shorter. That's what rendering of intent looks like in practice.