Insights

Jam3ya FinTech: Our Cooperate Venture Builder Approach in Practice

Salim Akil · · 4 min read

When I talk about our Cooperate Venture Builder approach at BE Venture Partners, I mean collaborate and build. The founder does not receive a set of recommendations and then disappear to work through them alone. We work alongside them as an operational partner.

Jam3ya is a useful example of that approach. It is a FinTech platform built around modernizing traditional savings circles, known as ROSCAs, for the UAE.

In this account, I am describing the work and progress reported in April 2025. The distinction matters: a development plan, an introduction, and a completed outcome are not the same thing.

Begin with a familiar savings behavior

Many UAE residents use informal savings circles. The underlying behavior already exists, but informal arrangements can struggle with transparency, security, and the ability to grow.

The opportunity with Jam3ya was to bring that practice into a digital-first platform. BE Venture Partners teamed up with founder Manei Alyammahi to work on a solution intended to improve transparency, automate transactions, and broaden access to savings tools for underserved communities.

This was not about introducing technology for its own sake. It was about taking an existing way of saving and working through what a more structured digital version required.

Work like a co-founder

Our model is hands-on. We work with first-time entrepreneurs who need a path from idea to market, early-stage founders who need an experienced operational partner, and established SMEs looking to digitize and innovate.

In Dubai, that work sits with BE Venture Partners. In the original account, I also described our partner organization Beyond 360 Ventures delivering venture-building work in Riyadh and Istanbul.

The common thread is practical involvement: defining objectives, validating a market, refining the product, and building a business model. Advice is part of it, but execution is the point.

Make the work concrete

The activities behind that approach span the venture-building journey:

  • Market research and customer discovery to test an idea against real needs.
  • Business planning, including the competitive landscape, financial projections, and milestones.
  • Business and product roadmaps that connect priorities with development work.
  • Alpha and beta releases that can be tested and improved.
  • Go-to-market planning for the right audience and early traction.
  • Fundraising preparation through decks, financial models, and relevant introductions.
  • Operational support with team building, strategy, and performance monitoring.

Those activities need to connect. A product roadmap cannot be separated from what the market needs, and a fundraising story cannot replace a plan for launching and operating the business.

Build the technology partnership

For Jam3ya, one important piece was a convertible note arrangement with a UK-based technology firm. That firm also took on the CTO role.

The structure helped address development costs while putting technical leadership alongside the product work. My original account described it as a way to save costs and support development quality; it did not provide a quantified saving.

That is a practical example of venture building. The question was not simply which features to recommend. It was how to put the capability in place to build them.

Connect development with launch and access

Our work also included securing a place in the Emirates NBD Incubator and developing and deploying an alpha version with a focused go-to-market strategy.

We facilitated investor meetings and feedback. At the time of the April 2025 article, a fundraising round was slated for May 2025. That was a plan, not a completed raise I am claiming here.

On the regulatory side, the account reported that operations had been established in the DIFC and that Jam3ya had progressed into a regulatory sandbox, with an announcement expected from a major regulator. I did not name the regulator in that article, and that progress should not be read as a claim of a particular license or approval.

Keep outcomes separate from the ambition

The original case study described positive reception for the mobile app, progress toward financial inclusion through modernized savings, and recognition for the venture's FinTech work.

Those were qualitative statements. The article did not provide an app-rating figure, a user total, or a measured financial-inclusion result. I would not turn them into numbers the source did not establish.

What the case does show is the breadth of work involved: technology, operational support, launch, institutional access, investor conversations, and regulatory setup all had to move together.

Bottom Line

A Cooperate Venture Builder approach means staying involved in the work, not stopping at the advice. Jam3ya illustrates how we bring structure, relationships, and operational support alongside a founder—while keeping plans, progress, and proven outcomes distinct.

Related reading

Put this into practice with Venture OS. Venture OS is BE Venture Partners' step-by-step platform for taking an idea from a problem to a validated business, with AI-powered tools, expert and mentor insight, and real customer testing. Start in Venture OS.

Salim Akil — Venture Building Consultant, BE Venture Partners · Host, B Model Podcast. LinkedIn