Exclusive Interview with Hass Peymani: Head of iGaming at CreateFuture

The article is an interview with Hass Peymani, Head of iGaming at CreateFuture, discussing the industry's move toward "AI-native" thinking and practical AI use cases such as client hackathons, AI orchestration platforms, testing, and AI-native SDLC. It is primarily commentary on technology adoption in iGaming, with no reported financial results, guidance, or quantified business impact. Market impact appears limited and informational.

Analysis

The important signal is not that AI tools are showing up in product workflows, but that operators are trying to re-architect around them while still carrying legacy stacks and compliance burden. That favors vendors that sit one layer above raw model access: orchestration, governance, testing, observability, and integration into existing SDLC. In practice, the market is likely to reward “picks-and-shovels” software revenue before it rewards end-user productivity gains, because regulated workflows tend to adopt through control layers first and only later through margin expansion.

A second-order effect is that AI can compress implementation cycles enough to change competitive dynamics among incumbents. Smaller software providers and consultancies that can prototype quickly may steal share from slower incumbents on renewal and implementation velocity, but the biggest beneficiaries are probably not the most visible AI brands; they are the middleware and workflow-layer vendors that become embedded in enterprise change management. For traditional operators, the near-term risk is not displacement by AI itself, but the widening gap between firms that can operationalize experimentation and those stuck with long IT queues.

The timing matters: over the next 3-6 months, this is mostly a sentiment and budget-allocation story, not a clean earnings catalyst. The next leg higher likely requires evidence that AI-native workflows are reducing time-to-launch, QA costs, or regulatory review costs in measurable terms; absent that, the move can remain largely narrative-driven. The contrarian view is that expectations for immediate ROI are still too high, especially in regulated verticals, and many pilot programs will end up as cost centers unless embedded into core systems with clear KPIs.

Key Decisions for Investors

• Long MSFT / long SNOW on a 3-6 month horizon: own the orchestration and data-control layer where AI-native adoption is most likely to translate into durable spend. Favor call spreads over outright longs if implied volatility stays elevated; upside is a multi-quarter budget re-rating, not a single-quarter earnings pop.
• Long PLTR against a basket of slower legacy software vendors (or short the basket) for a 2-4 quarter relative-value trade. The thesis is that regulated enterprises will pay for governance, auditability, and model routing before they pay for frontier-model access; risk is valuation compression if deployment metrics disappoint.
• Buy opportunistic calls on META or GOOGL into weakness for a 6-12 month horizon. If AI-native experimentation is real, incumbent platforms that already own distribution and data will convert pilot activity into monetization faster than pure-play AI vendors; use defined-risk calls because market expectations are already crowded.
• Avoid chasing high-multiple “AI transformation” services names after headline spikes; instead, wait for post-event pullbacks and look for 15-20% retracements before entering. The risk/reward is better after the market proves it can’t immediately price in the productivity uplift.
• For event-driven exposure, use a pairs trade: long workflow/governance software, short generic IT services consultancies over the next 6-9 months. The market should differentiate companies that automate product delivery from those selling labor hours; the latter face margin pressure as prototype velocity rises.