Yusuf Umar

Yusuf Umar

Managing Director & Chief Executive
#97510952 followers23 following
>10,000All time
0 KP

About

With over 13 years of experience, I specialize in business strategy, financial modeling, and risk management within the oil & gas, renewable energy, and infrastructure sectors. My career has been dedicated to delivering strategic solutions and fostering sustainable growth in these critical industries. As Managing Director and Chief Executive Officer at RIPLE since April 2024, I lead initiatives focused on advancing renewable energy development and infrastructure projects. Collaborating with stakeholders, my mission is to create value and address complex challenges while driving impactful outcomes in the energy and infrastructure domains.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Forums

Banquish — Make the web your workspacep/banquish-make-the-web-your-workspace•

13d ago

Is there a feature you'd like to see in Banquish?

Followings are coming soon!

  • panel customization

  • mobile element capture

  • Device syncing

Tell me any features you'd like to see in Banquish!

•

19d ago

What was harder to explain than to build?

I launched a product today, and one of the biggest lessons came before the launch:

Building individual features was relatively straightforward. Explaining why they all belonged in the same product was much harder.

The moment the product became easier to explain, a lot of other decisions became easier too: what to remove, what to emphasize, and who it was really for.

Have you ever built something that worked well, but was surprisingly difficult to explain clearly?

•

20d ago

What ate the most time building your marketplace?

Across the last few home-services marketplace builds I've been part of (cleaning, repairs, salon-at-home type booking flows), the same three things kept eating more time than expected, in this order:

  1. Provider trust/verification document checks, ratings, and dispute handling needed to be right from day one. Bolting it on after a few bad-actor incidents was way more expensive than building it in up front.

  2. Payment splits and payout timing getting the wallet logic right between customer and provider (holds, refunds, payout schedule) caused more support tickets early on than any missing feature did.

  3. Scheduling conflicts double-bookings and no-shows quietly killed early retention more than discovery or search ever did.

What surprised me is that none of these three were the thing founders originally worried about most going in most people spend their early planning time on discovery/search UX, and the actual pain shows up somewhere else entirely once real bookings start happening.

Curious if others building in this space saw the same pattern, or if something else entirely turned out to be the real bottleneck for you onboarding the supply side, pricing/commission structure, something else?

View more