I turn ideas into shipped products.
Currently migrating this site, some project are linked to Behance in the meantime
Tripsome Partner App — Enabling Partners to Operate Independently (MVP)
A partner app that helps activity providers manage bookings, payments, and daily operations on the go.
Role
Product design, UX strategy, design system, and execution.
Defined product scope and prioritization.
Cross-functional alignment.
Results
Cash bookings reached 50%+ of total revenue.
Reduced partner churn despite existing debt.
Turned two years of stalled development into a shipped, usable MVP.
Enabled expansion into link payments (Indonesia).
Tripsome started as an activity marketplace where partner operations were largely managed through support.
The lack of a self-service tool meant that even basic actions had to be routed through support.
The system was too complex for non-technical partners and didn’t solve their real problems.
Delayed payouts and debt made things worse and trust started breaking.
Initially, we explored a calendar-based layouts used by major marketplaces.
Aiming for full control over bookings and availability.
We explored a calendar-based interface giving partners control over scheduling, availability, and bookings in one place.
This made it clear that this wasn’t the product
On the surface, the initial concept appeared complete, yet it failed to address the partners' actual needs. With the primary pain points of payments and payouts still unaddressed.
The goal wasn’t to ship this. It was to align on why we shouldn’t build it, at least not yet.
By stripping the layout down to its essentials, we identified which features mattered most.
We removed everything that didn’t matter.
Kept only core actions, used simple, scalable components and designed for responsiveness.
Not more powerful. Just usable.
Working with partners revealed that they rarely use laptops and are often asked to accept cash payments
Success wouldn’t come from better tools alone, but from understanding how partners actually operate day to day.
Our support team kept reporting the same two signals.
This led us to go app-first and we prioritized accordingly.
Designing the experience
The product was reduced to a few essential actions.
This phase focused on making them clear, fast, and usable.
Giving partners clarity over their earnings
Payout summary, monthly revenue and bookings
No advanced analytics. Just clarity.
Making cash payments trackable
Partners scan a ticket and confirm whether payment was received.
Handling unscanned bookings
Tickets that aren’t scanned are flagged for review.
This removed ambiguity in cash payments and reduced disputes.
Requesting payout
No automation. No complex rules. Just clear balances and simple requests.
Allows partners to request payouts with full visibility into the amount and status.
The goal is confidence, not speed.
Adding bank info
Partners are prompted to add or update bank details before requesting a payout.
Keeping this flow simple reduces friction and support dependency.
Understand your payouts
Gives partners a clear breakdown of what’s available, what’s pending, and what’s been requested.
A simple view of where their money stands.
