Portfolio Story: How Cryptss Raised $2M in the Gulf

Cryptss raised a $2M round in the Gulf — and the story is worth telling less for the figure than for how the round came together. Cryptss is a Gulf Web3 loyalty startup: it turns customer loyalty into tokenised rewards that merchants can issue and redeem without the friction of traditional card-based programmes. This is the honest version of the journey, misses included. We cover what investors actually asked, how the studio supported the raise and the lessons any Web3 founder can apply to their own round. The narrative stays qualitative throughout, because the lessons live in the process, not the metrics.

Cryptss: a Gulf Web3 loyalty startup

Loyalty and Web3 look like an odd couple on paper: loyalty is a mass-market habit, while Web3 still carries jargon and baggage. In practice the fit is stronger than it seems. Tokenised rewards give merchants a programmable retention layer — points that can be issued, redeemed and exchanged without card-network fees — and give customers rewards that feel like real value rather than an expiry date. The broader Web3 movement has matured considerably, and infrastructure such as Ethereum now supports reward systems that a shopper can use without ever touching a wallet.

The Gulf is a natural proving ground: dense retail, a strong loyalty culture and a young population comfortable with digital assets. We first told the Cryptss story here; this piece goes deeper into the $2M round itself and what happened around it.

It is worth being precise about what Cryptss is not. It is not a trading platform, not a marketplace for speculative tokens and not a project that needed a glossary to be understood. The product behaves like a familiar loyalty app: a customer earns rewards with a merchant, collects them in one place and redeems them transparently. The Web3 layer is the plumbing — shared, verifiable records across partner merchants — not the pitch. That positioning decision, made early, made every later conversation easier, from retail operators to regulators.

The Cryptss journey, told honestly

The journey looked nothing like a pitch deck. Cryptss started in a shared room with a whiteboard, like hundreds of other GCC startups. The first version of the product was over-engineered — too many features, too few conversations with merchants. Early customer conversations were polite but sceptical: retail operators already had loyalty platforms, and nobody was asking for tokens, at least not at first.

What changed was a series of quiet pivots rather than a single breakthrough. The team stripped the product to fewer features, sharpened the merchant pitch and found a small number of believers who became design partners. There were long stretches of little visible progress, and the round was fought for meeting by meeting. The honest summary: nothing in the Cryptss journey looked inevitable in real time, and the founders treated every early rejection as data.

One detail from that period is worth holding onto. The design partners did not come from pitch events or accelerator showcases; they came from conversations the team had with merchants who complained about their existing loyalty programmes — unused points, expensive card schemes, customers who never came back. Listening to those complaints reshaped the roadmap more than any market report did. The lesson the team draws from it is unfashionable but consistent: the product earned the right to raise by spending months doing unglamorous customer work first.

Why Cryptss chose a studio route

Cryptss chose to build with a studio rather than going it alone, and the choice shaped the raise. The studio provided shared operations — legal, finance and hiring support that a small Web3 team rarely has in-house — and a team that had already navigated the Gulf’s company-formation and banking maze more than once. Practical infrastructure such as a Gulf business bank account was sorted before investors ever asked about it.

Just as important was compliance. Token design conversations started before the fundraise, not after, and the studio’s regulatory work tracked the fast-moving Gulf crypto regulation landscape from day one. When investors raised compliance questions, the answer was already written. A studio route is not right for every team — it works when the infrastructure gap is real and the partnership is genuine.

The division of labour mattered as much as the resources. Founders owned the product and the merchant relationships; the studio owned everything a raise depends on but a founder resents doing — legal structure, cap table hygiene, banking, contracts and the discipline of keeping records that an investor’s lawyers can actually review. That separation is why the team could keep shipping during the round instead of disappearing into spreadsheet work for three months. It is a model that suits teams raising for the first time, where the cost of a badly prepared process is not just a slow round but a lower one.

What investors asked Cryptss

The same questions came up in almost every investor conversation, and they are worth writing down because they are predictable:

• Why tokens, and why not ordinary points? The token design needed a clear answer that survived technical scrutiny.
• What is the regulatory posture of the project in the Gulf? Investors here ask early, and they expect a considered answer, not a shrug.
• How do both sides win? The two-sided incentive design — what merchants gain and what customers feel — was tested repeatedly.
• What is the retention story? Investors wanted mechanics that keep customers engaged, not a growth narrative without a base.
• What is the round for? The size had to connect to a specific milestone, which kept every conversation disciplined.

Notably, the strongest questions were about design, governance and regulatory posture — the areas where Web3 teams are most often thin. The questions that start at pre-seed in the GCC sharpen quickly once tokens are involved.

How the team answered mattered as much as what it answered. Every investor conversation was preceded by a briefing: who was in the room, what they cared about and which questions they were likely to ask. The answers were consistent across meetings — same narrative, same numbers, same caveats — because a story that changes with each audience tells investors the team is improvising. The discipline felt bureaucratic in week one and obvious by week twelve; by the end, the founders could run the full conversation in their sleep, which is exactly when conversations start going well.

How the studio supported the Cryptss raise

The studio’s role in the raise was to keep the process boring. The investor pipeline was built the same way we describe in our guide to your first thirty investors: a long, organised list, warm introductions, methodical follow-ups and a running record of every conversation. One narrative was prepared rather than a custom deck per audience, and the data room was ready early, so nothing ever blocked a meeting.

Logistics that rarely get mentioned mattered too: scheduling, room bookings, preparing founders for each conversation and honest counsel at the table about when to push and when to let a silence sit. The goal was to keep the founders building while the process ran, because a good raise should not feel like a second job. The round closed at $2M, but the mechanics of the raise were unglamorous on purpose.

Lessons for Web3 founders

Several lessons from the Cryptss round apply beyond one company. Fundraise to a milestone, not a wish. Get regulatory clarity before you ask for money. Lead with retention mechanics, not raw growth. Keep the investor process disciplined from the first coffee. Our analysis of which Web3 teams survived 2026 reached the same conclusions from a different direction.

What happens next for Cryptss

The $2M round is a beginning, not proof. Cryptss is now working to deploy the capital toward product depth, merchant partnerships and GCC-first expansion, and it remains close to the studio model that shaped the raise. The honest caveat is that rounds do not make startups; execution after the cheque does.

What we are watching is straightforward: whether the loyalty mechanics hold up with real merchants, whether the token design stays compliant as Gulf regulation evolves, and whether the team keeps the same discipline in spending that it showed in raising. The sector around projects like Cryptss moves quickly — daily market coverage in Cointelegraph shows how fast — and the founders’ habit of answering the hard questions early is the best indicator we have for the next chapter.

The final lesson of the Cryptss round is the least glamorous one. There is no version of this story where a single magic meeting, a viral moment or a famous name on the term sheet did the work. The round was the product of a long list of unremarkable actions done well: clear answers written down before they were asked, follow-up emails sent the same day, a data room that opened instantly, and a narrative that stayed true from the first coffee to the final signature. For founders preparing their own raise, that is both the bad news and the good news — none of it is secret, and all of it is doable.