THE REVENUE PROBLEM 💵

“Gotham’s Repair-Rescue: Cracking the Payment Code”

Gotham has been a dark place lately, with your average everyday people coming down to streets damaging, wrecking and burning vehicles freely to support Joker’s movement and Chaos. Even the Wayne Enterprises is facing a recession and decline in it’s revenue with cash burn increasing rapidly despite the services being provided to Gotham citizens.

<aside> 🔻

WayneTech Repair-Rescue needs a new infrastructre in payments.

</aside>

Looking at the current scenario of Gotham, even the Dark Knight knows the value of reliable service when the Batmobile breaks down. Citizens of Gotham are using WayneTech Repair-Rescue, Gotham’s premier app for connecting citizens with skilled mechanics.

But the app is facing a dire challenge—users are bypassing the app’s payment infrastructre, and directly paying mechanics locally via cash or UPI sidestepping the app. This loophole leaves WayneTech unable to generate revenue through convenience fees from the app.

The challenge lies in the inability to pre-estimate repair costs, as prices vary based on on-site evaluations, vehicle type, level of damage and unforeseen repair needs. While pre-estimation isn’t always feasible, the true mission is to design UI/UX solutions that encourage seamless in-app payments and minimize transactions happening locally.

MISSION BRIEF 📜

Innovate the app’s design and user experience to:

<aside> 📌

1. Build trust and convenience, ensuring mechanics and users prefer the app for payments. </aside>

<aside> 📌

1. Address challenges like service price ambiguity and offline payment exploitation through strategic features. </aside>

<aside> 📌

1. Deliver a robust system that maximizes in-app payment usage, creating a sustainable revenue stream for WayneTech. </aside>

WAYNE ENTERPRISES GUIDELINES 📋

… DELIVERABLES

1. User should should keep a Design Approach in mind.