Progressive Monthly Discounts
product design
app design

Bringing hidden value online and reducing operational waste

Company

Localiza&Co

role

Product Designer

Type

In-house

year

2025 - ongoing

Overview & Outcomes

For years, Localiza offered progressive monthly rental discounts exclusively through phone and in-person channels, leaving online customers without access to significant savings and operational value on the table. When the initiative to bring this capability digital stalled mid-development, I was brought in to diagnose the problem, reframe the approach from "inform users" to "let users explore and apply," and coordinate delivery across five squads before a hard seasonal freeze deadline.

Problem statement

Progressive monthly discounts existed only through phone or in-person counter bookings. Users couldn't see or benefit from these incentives online, leaving revenue on the table and cars idle in yards.

The solution

in-flow re-quotation calculator

I designed an in-flow re-quotation calculator that updates the live quote as customers extend rental months, making the discount structure transparent and the value proposition immediate.

Key Outcomes

Up to 19% conversion rate

Users actively exploring and extending rentals

Signficative per day per reservation

Average increase in protection/optional uptake.

Reduced operational costs

And migrated users from fragmented bookings to single, longer contracts

Delivered on time

Across five squads before high-season freeze

Context

The Business Directive

Progressive monthly discounts had been offered at every Localiza branch for years — but only in person or over the phone. Leadership directed the product organization to bring this capability online as part of a strategic push to scale monthly rentals through digital channels.

The Timing Constraint

We had a hard deadline: ship before high season began. Localiza freezes all new feature releases during peak booking periods to avoid disruption during the most revenue-critical months. Missing this window meant waiting an entire season.

A Stalled Initiative

When I returned from vacation, the project had been in progress for weeks with minimal design involvement. The pricing squad had nearly completed their engine and expected design to figure out how to "explain" the discounts to users through better copy and layout.

The timeline:
  • 1.5–2 months until feature freeze
  • 3 weeks available for design work
  • All squads needed to complete development before the deadline

I was brought in to unblock the initiative and get it across the finish line.

The Organizational Complexity

This wasn't a single-squad effort. The internal structure required coordination across:

  • Pricing squad: owned discount logic and calculation rules
  • Data & bookings squad: processed reservations from all channels
  • App squad: my primary responsibility, accounting for 70%+ of all digital bookings
  • Site squad: web experience
  • Chatbot squad: conversational booking flow

Each channel talks to the backend squads (pricing and bookings) independently, meaning any change required synchronized updates across five teams.

My Position

As the designer for the app — the dominant digital channel — I led the design strategy across all digital surfaces. The app's volume made it the primary success metric, but site and chatbot needed the same solution to maintain experience consistency.

Why This Mattered

Offline, agents could explain progressive discounts in real-time, adjusting offers based on customer questions. Online, customers had no visibility into these incentives, no way to explore scenarios, and no confidence in how monthly pricing actually worked. The friction forced users to either call in (operational cost) or book shorter periods (missed revenue).

V1 timeline

Problem & Research

Problem space

The Business Problem

The business offered progressive discounts for longer rentals — but only through human-assisted channels. Online customers had no visibility into these savings, forcing them to either:

  • Book shorter periods and re-book multiple times (operational waste)
  • Call the counter to manually negotiate (poor experience)
  • Miss the discount entirely (lost revenue)
The user Problem

For users, the problem extended beyond missing discounts:

  • Monthly vs. daily mental models didn't align with how pricing was displayed
  • Security deposits and mileage allowances were buried or unclear
  • No way to explore "what if" scenarios before committing
The business need

The company needed to bring this pricing flexibility online before the high season, requiring tight coordination across pricing systems, reservation flows, mobile, and web — all while avoiding a feature freeze.

What I learned from research

The Business Problem

I analyzed phone and counter booking patterns, operational data, and cross-channel performance to understand:

1. Users think monthly, not daily

Long-term renters mentally budget per month. Showing "R$X per day × 90 days" created cognitive friction.

2. Discount visibility drives duration

When phone agents explained month-by-month savings, customers consistently extended rentals. Online users never saw this value proposition.

3. Mileage allowance was a showstopper

Many users abandoned or called after realizing total mileage limits weren't clear upfront.

4. The deposit question appeared in every support channel

Many users abandoned or called after realizing total mileage limits weren't clear upfront.

My Role & Strategy

Design Strategy

Reframed the brief from "inform users about discounts" to "let users explore and apply discounts in-flow." I made the case that an announcement wouldn't change behavior — we needed a calculator, not a tooltip.

ross-Squad Orchestration

Established shared delivery principles across app, web, pricing engine, and reservations teams through sync meetings and shared documentation. Created a unified decision framework so each squad could move independently without waiting for design review on every component.

Scope & Sequencing

Defined what ships in MVP, what moves to Next, and what goes to Later. When Pricing pushed to add comparison tables and Legal wanted expanded disclaimers, I held the MVP boundary: "We're shipping the calculator and monthly framing. Everything else waits for validation data."

Holding the Line on Core Principles

When I joined the project, the pricing squad presented their nearly-complete engine implementation in a cross-team sync. Their approach: show discount information without actually changing the quote during booking. Their reasoning was capacity — they hadn't allocated engineering time to rebuild the quotation structure and expected design to "solve it with better explanations."

I pushed back directly:
"This won't work during booking. Inform-only can happen after booking, before pickup, but not in the flow. If the quote doesn't update in-flow, design will not approve this solution. We only proceed if the quotation changes."

This wasn't negotiable. Users needed to see the discount applied in real-time, not described in a tooltip. No amount of clever copy could compensate for a quote that didn't reflect the value being offered.

The pricing squad had to reprioritize their capacity. It delayed the initial timeline by two weeks, but it was the right call — the solution worked because the calculator actually changed the quote.

Stakeholder Alignment Through Framing

Connected each design decision to business outcomes in stakeholder readouts:

  • Discount discovery → duration uplift
  • Discount discovery → duration uplift
  • Mileage visibility → fewer pickup reversals

This framing turned UX goals into commercial goals, securing buy-in from teams who initially saw this as "just a UI change."

Actual structure comprises multiple teams and dependencies

Solution & Decisions

Here's how I translated insights into a transparent, actionable experience:

How I worked

Aproach

Systems thinking was paramount for this project. One of my first steps was to understand the supermarket model, market and trends in the sector. Crossing those pieces of information with innovations around the world gave me an initial view of the system around supermarkets. It was challenging to learn about the business, its clients and technologies in such a short time. So I tried the create a more high-level view of the whole picture.

Key Design Decisions

In-flow progressive calculator

Instead of static information, I designed an interactive calculator that updates the quote as users add months, making the discount tangible immediately.

Monthly-first framing

The UI mirrors how users think: monthly payments, not daily rates multiplied by 30. This single shift eliminated the most common mental model mismatch.

Rebuilt quote summary

Redesigned the reservation summary to highlight progressive savings structure, not just a single total — giving users confidence in their decision.

Navigating Constraints & Tradeoffs

Inherited mid-flight with compressed timeline

I joined the project after it had stalled for weeks with minimal design involvement. The pricing squad had nearly finished building their engine with the assumption that design would simply "explain" the discount to users. With only 3 weeks of my availability and 1.5–2 months until freeze, I had to quickly diagnose the core issue, convince teams to rebuild their approach, and coordinate delivery across five squads.

No time for user testing

The compressed timeline didn't allow for traditional validation cycles. Design decisions relied on my expert judgment, cross-channel behavioral data, and internal expert feedback from product, engineering, and operations teams. I shaped the solution through design expertise and strategic conviction rather than prototype testing.

we had already built the wrong thing

When I joined, the pricing engine was nearly complete — but it was built around an "inform-only" model that wouldn't solve the trust problem. I had to convince the team to rebuild their approach to support in-flow quote updates, which delayed their timeline by two weeks but ensured the experience actually worked.

Five-squad coordination

App, web, pricing engine, reservations systems, and chatbot all needed synchronized changes. I established shared principles and a unified delivery cadence to keep everyone aligned without creating bottlenecks.

Impact & Learnings

Business & User Impact

Business
  • Up to 19% conversion on the in-flow calculator
  • Increased average rental duration through transparent progressive incentives
  • Fewer vehicle yard cycles — cars generate revenue faster with longer single rentals vs. consecutive short bookings
User
  • First-time visibility into progressive savings across online channels
  • "What if" exploration before committing — no need to call or re-quote
Organization
  • Proved design drives pricing outcomes — elevated UX's role in commercial execution
  • Created reusable transparency pattern for future discount structures

Next Steps

Post-MVP priorities include:
  • Refining comparison cues between per-month vs. total pricing
  • Improving legal transparency around deposit and mileage language

Each iteration will be informed by real usage data, not assumptions.

What I Learned

Design conviction under pressure is a skill

With no time for traditional validation, I relied on cross-channel behavioral evidence, expert judgment, and strategic framing to make confident decisions. The 19% conversion proved that experience-driven design can succeed when backed by strong research foundations.

"If it doesn't update the quote, it's not solving the problem."

Standing firm on core interaction principles, even when it forces technical teams to rebuild their approach, is what separates strategic design from feature factory work. The two-week delay was worth it.

Ruthless scope management ships complex projects

Protecting the MVP boundary while planning future improvements is how you deliver under pressure without sacrificing quality.

Legacy

Future Roadmap

This progressive discount calculator establishes a foundation for transparent, user-controlled pricing exploration across Localiza's rental ecosystem — a pattern that can extend to subscriptions, insurance tiers, and multi-product bundles.