Case studies by Ola Wallin

Case studies by Ola Wallin

Zebra BI

Zebra BI

Case

About Zebra BI

About Zebra BI

Zebra BI creates Power BI visualization tools for financial reporting with IBCS compliance, serving B2B customers through dual go-to-market motions—sales-led for managed accounts and product-led growth for self-service.

The challenge

The challenge

When I joined Zebra BI as VP of Marketing, the company faced a perfect storm of growth challenges. Conversion rates were declining across the entire funnel—from website sessions to MQLs, MQLs to trials, and trials to paying customers. Worse, organic traffic was dropping, cutting off the top of the funnel and compounding the conversion problems below.

The root causes ran deep. The marketing team operated in functional silos—SEO worked in one corner, content in another, demand generation somewhere else—with no unified strategy, no cross-functional campaigns, and no collaboration. There was no clear SEO process to stem the traffic decline, no systematic approach to demand generation, no product marketing foundation, no brand strategy, no content framework, and no CRO process.

Marketing didn’t work as a unified team running integrated campaigns. Instead, everyone optimized their individual channels in isolation. Marketing, Sales, Product, and RevOps worked in parallel rather than together, each optimizing their own piece without seeing the full customer journey or working toward shared goals.

The company had ambitious targets—€11M ARR and 65+ new customer logos monthlybut lacked the marketing foundation to get there. With dual go-to-market motions (sales-led for managed accounts and product-led growth for self-service), the complexity was high and the stakes were higher.

The solution

The solution

I started with diagnosis before prescription. Using the AARRR framework as a diagnostic lens, I mapped the entire customer journey to identify where growth was breaking down—from organic traffic decline through every conversion point to paying customer. The data revealed bottlenecks at multiple stages, but more importantly, it showed that siloed teams were optimizing pieces without understanding the whole.

The first move was restructuring the team around the customer journey. I created three specialized teams: Demand Generation (driving traffic and conversion), Product & Content Marketing (positioning and education), and Lifecycle Marketing (nurturing). But here’s what made it work: I organized them into two cross-functional working groups using AARRR—one focused on Acquisition and Activation (the AA team), another on Revenue, Retention, and Referral (the RRR team). This dual structure meant everyone had functional depth but worked together on integrated campaigns. The groups met bi-weekly for performance review and planning, ensuring continuous alignment and rapid problem-solving.

Next came strategic foundation. I developed a comprehensive Marketing Strategy 2026-2029 with five pillars—Product Marketing & Go-to-Market, Brand Building & External Presence, Customer Acquisition & Growth, Customer Marketing & Advocacy, and Marketing Operations & Analytics. This became the operating system that was going to align marketing with sales and product around shared revenue goals.

For the organic traffic problem, I established a systematic SEO and Content process connecting keywords to buyer intent and AARRR stages. But I tackled content strategy holistically. I implemented the STDC framework (See, See+, Think, Do, Care) as the foundation—mapping our content library to identify customer journey gaps and creating a systematic approach to filling them. The strategy was set and ready for execution: owned channels (website, email) for lead capture and relationship building, shared channels (YouTube, LinkedIn, paid) for audience growth with clear paths back to owned platforms. Each channel had defined purpose mapped to STDC stages—LinkedIn for thought leadership in See+ and Think stages, YouTube for education in Think and Do stages, paid for amplifying high-performing content.

For positioning, I started to shift Zebra BI from product features to thought leadership using STDC. The goal: own the category of standards-based BI and actionable reporting rather than compete as another Power BI visual vendor. The thought leadership strategy was in place and beginning to reshape how the market saw Zebra BI.

On paid performance, we identified massive investment potential. As we systematically improved landing pages, messaging, and targeting, CPL costs dropped month over month. I built the business case for aggressive paid scaling based on improving unit economics.

For lifecycle marketing, I developed dual-track programs matching our hybrid GTM motion—one nurture path for self-service PLG users, another for sales-assisted accounts. Critical to this was defining Product Qualified Lead (PQL) criteria to identify which trial users showed genuine buying intent. This PQL definition was designed to transform our trial-to-customer nurturing, allowing lifecycle marketing to focus resources on high-intent users while automating light-touch nurture for others.

For conversion optimization, I built systematic CRO processes—bi-weekly analysis, hypothesis-driven experiments, rapid testing across the full funnel. We treated the website as a product requiring continuous iteration.

Finally, I established cross-functional collaboration frameworks connecting Marketing, Sales, Product, and RevOps. Shared dashboards tracking session to revenue. Unified success metrics where everyone optimized for pipeline and revenue, not departmental vanity metrics. Marketing became a revenue driver.

The transformation took months of systematic work—restructuring teams, building processes, establishing measurement, running experiments, creating alignment—but the foundation was built to scale and sustain growth long-term.

“Ola was a true partner on the leadership team. He rebuilt marketing into a high-performing function by focusing on team, process, and outcome, not just tactics. The collaboration between marketing and sales became genuinely productive, with shared goals and clear accountability. He made marketing a strategic contributor again.”

Jerome Johansen
VP of Sales, Zebra BI

20%

Accelerating MQL growth MoM last quarter

20%

Session→Trials up MoM last quarter

€300k

CRO Compound (in 4 months) - 75k monthly sessions

26%

Black Friday New ARR above expectations

21%

Final 2 months, great PLG New ARR uplift

38%

Final 2 months, showed great PLG Logos uplift

Raketech

Raketech

Case

About Raketech

About Raketech

Raketech is a leading iGaming affiliate company connecting sports bettors and casino players to operators through performance-based marketing websites across global markets.

The challenge

The challenge

When I joined Raketech as VP of Product for Affiliation Marketing with P&L responsibility for the portfolio, the company faced a critical problem: traffic and conversion rates were declining across their iGaming affiliate sites in Europe and Asia. The causes were multiple—competitors and operators ranking above them, potential algorithm penalties, weak technical SEO—but the deeper issue was organizational.

Despite having a 70-person product organization with dedicated PMs, SEO specialists, and a CRO team, the company was completely SEO and content driven with no product maturity. Revenue generation relied solely on SEO and outclicks to operators. Websites weren’t treated as products requiring continuous optimization and user-centric development. Instead, the focus was narrow: rank for a few SEO keywords, add content, measure outclicks. There was no balance between short-term and long-term traffic strategy—just immediate outclicks today. There was no AARRR framework, no buyer journey understanding, no focus on user engagement, aha moments, or retention—just traffic in, outclicks out.

The CRO team existed but wasn’t integrated into product development. Sports and Casino product teams worked in silos, disconnected from the central Product Experience and CRO teams. Product and Tech teams didn’t collaborate on problem-solving; instead, PMs wrote feature tickets and passed them to development. The organization didn’t focus on problems → solutions; they focused on features → implementation. Decision-making was largely HiPPO-driven rather than data-driven, and the company operated on rigid 12-month feature roadmaps that were detailed, feature-focused, and disconnected from business outcomes.

With direct reports managing Product, UX, UI, Data Analytics, CRO, SEO, and Content functions, my challenge was clear: transform how the organization thought about product development, establish cross-functional collaboration, shift from SEO-only dependency to full-funnel optimization, and move focus from outputs (features, content) to outcomes (user value, business results).

The solution

The solution

I started by changing how we looked at the problem. I introduced the AARRR framework to shift focus from SEO traffic and outclicks to the entire user journey—Acquisition, Activation, Retention, Revenue, and Referral. This reframed the conversation: it wasn’t just about getting more traffic, but about what happened after users arrived. Were they finding value? Reaching their aha moment? Coming back? Converting?

Next, I tackled the planning process. I replaced the 12-month feature roadmaps with lean, problem-focused roadmaps that prioritized outcomes over outputs. Instead of “build feature X by Q3,” we asked “how do we improve user engagement by 20%?” I connected these lean roadmaps to OKRs, creating clear alignment between product work and measurable business objectives. This shift established a lean and agile mindset where teams learned to iterate quickly based on evidence rather than execute detailed year-long plans.

The biggest transformation was cultural. I established cross-functional collaboration between Product, Tech, central Product Experience, and CRO teams. Instead of writing feature tickets and passing them to development, teams worked together solving defined problems. Sports and Casino product teams no longer operated in isolation—they partnered with Product Experience and CRO to optimize the full user experience from landing to conversion.

I introduced continuous discovery frameworks using a data → insights → actions approach. We implemented systematic methods for gathering both qualitative and quantitative insights: user surveys, on-site popups, data analysis, A/B testing, Hotjar for behavior tracking. The goal: make decisions based on evidence, not opinions. We focused on understanding and optimizing the aha moment, user engagement, retention, and conversions—not just traffic volume. This established an experimental culture where teams continuously tested hypotheses and learned from results.

To reinforce the shift, I established bi-weekly AARRR outcome reporting sessions where teams reviewed performance across the full funnel. We tracked compound ARR impact from CRO work, showing how small improvements multiplied across the portfolio. This created accountability and visibility: everyone could see how their work connected to business results.

The transformation took months of systematic work—changing processes, building new collaboration patterns, establishing data-driven practices, coaching teams on discovery methods, fostering lean and agile mindsets, creating experimental culture—but the way of working fundamentally changed. Teams shifted from ticket-takers to problem-solvers, from output-focused to outcome-oriented, from siloed functions to cross-functional collaboration, from SEO-only dependency to full-funnel optimization.

“In just a few months, Ola Wallin made a lasting impact on the product team. He showed us how to plan for outcomes (business/product results) rather than just outputs (features), guiding us to iterate effectively. Though he was no longer with us throughout Q1, the frameworks he introduced, coached, and trained us on were fully adopted allowing the team to stay aligned and successfully achieve the planned outcomes by the end of the quarter.”

Antonella Foti
Head of Product Experience, Raketech

“Ola’s implementation of cross-functional teams and lean roadmaps revolutionized how product and engineering collaborate. By shifting from feature requests to problem-solving, he created alignment between our technical capabilities and business objectives. His data-driven approach ensured we built solutions that actually moved the needle on performance metrics.”

Andrea Candian
CTO, Raketech

LeoVegas

LeoVegas

Case (as an employee)

About LeoVegas

About LeoVegas

LeoVegas is a leading mobile-first gaming operator serving casino and sports betting customers across multiple regulated markets. Founded with the vision “leading the way into the mobile future,” LeoVegas holds a strong market position in mobile gaming and was publicly listed on Nasdaq Stockholm. The company was later acquired by MGM Resorts International in 2022.

The challenge

The challenge

When I joined LeoVegas as Lead Product Manager in late 2015, the company was a casino-only gaming operator with a clear mobile-first vision. The strategic decision came early: launch a sportsbook from zero. What started as a casino product role quickly transformed into leading the company’s first-ever sports betting vertical—becoming fully responsible for the entire sportsbook product. The company hired a Head of Sportsbook to handle operational aspects (odds, risk management with Kambi), while I owned the product.

The challenge was substantial. LeoVegas had no sportsbook experience, no sports team, and no product. We were starting from absolute zero against established players like Unibet and Expekt with years of market presence. The company’s DNA was pure casino—a product that operates like a machine with predictable patterns. Sports betting was entirely different, with massive volatility dependent on match results. When Boxing Day arrived and all favorites won, the internal reaction exposed the cultural gap between casino certainty and sports unpredictability—the learning curve was steep.

But the biggest product decision shaped everything that followed. Kambi offered a white-label sportsbook—a turnkey solution used by multiple operators that all looked the same. Instead, our team made a critical strategic call: build a custom frontend using only Kambi’s APIs. This meant significantly more complexity—integrating Kambi’s backend (odds, risk management) with our own frontend, adding Sportradar for streaming and stats, building everything mobile-first (though supporting desktop) aligned with LeoVegas’ vision of “leading the way into the mobile future.”

The technical complexity was immense. A sportsbook isn’t just displaying odds—it’s real-time data synchronization, bet placement flows, regulatory requirements varying by market, payment optimization, streaming integration, and conversion optimization. We had tight timelines (months, not years) to launch ahead of the 2016 European Championships, needed to build cross-functional teams from scratch, establish product processes in a casino-focused organization, and deliver a differentiated product that could compete with decade-old brands.

The solution

The solution

I started by introducing lean startup methodology and systematic product processes to the newly formed sportsbook team. Inspired by Marty Cagan’s product thinking, I focused on three dimensions: product (what to build), process (how to build it), and people (building the team and culture). We adopted an opportunity → discovery → delivery mindset—identifying opportunities through lightweight research, moving promising ideas into discovery where I supported our UX lead with product and business expertise as we researched and collaborated, then pushing viable concepts into delivery.

The custom frontend decision proved transformative. By securing full API access from Kambi—we became the first operator to get this level of access—we could build a truly differentiated mobile-first sportsbook rather than another generic white-label product. This wasn’t just technical; it was strategic product differentiation.

I built and led three cross-functional teams totaling 25-30 people across product, UX, development, analytics, QA, and UI. We worked as a lean, startup-style team within a larger organization—given autonomy to operate with agile methodologies. Starting with Scrum, transitioning to Kanban, releasing weekly or more frequently. The team culture was critical—we had fun while working, built genuine collaboration, and established an experimental mindset from day one.

Mobile-first wasn’t just a slogan; it was product strategy perfectly aligned with LeoVegas’ vision. Every decision started with mobile, though we supported desktop. Our product motto became “relevant wherever the user is”—ensuring users had the information they needed exactly when they needed it. We obsessed over conversion optimization: streamlining deposits and payment flows, perfecting bet placement, optimizing odds presentation. We ran continuous experiments across event lists, event pages, and betslips, working closely with BI and analytics teams using data-driven approaches to validate every decision.

We collaborated closely with casino teams to create seamless cross-selling—converting sports betting players to casino and vice versa to increase lifetime value (LTV). The platform needed to move users smoothly between verticals, and we built product features specifically to drive this behavior.

Regulatory complexity required close collaboration across multiple markets—Sweden (launch market), Denmark, UK, Italy—each with different requirements. We successfully navigated compliance challenges while maintaining product quality. As we approached World Cup 2018, we scaled the team by adding an extra development group, expanded our live streaming offering to 10,000+ events, and systematically improved the product for the tournament.

The strategy worked. Within a year of launch, we won two industry awards: “Rising Star in Sports Betting” (1st place) and “2nd Mobile Sportsbook of the Year” at the SBC Awards 2017, competing against all operators including decade-old established brands. Sports betting grew rapidly, contributing significantly to company revenue and becoming a key revenue driver for LeoVegas—transforming from zero to a meaningful percentage of total business within 18 months.

Throughout, I worked side-by-side with the Head of Sportsbook Operations in Malta—clear ownership made it work: I owned product, discovery, development, and user experience; he owned operations, odds, and risk management with Kambi.

The transformation took months of systematic work—building teams, establishing product culture, making strategic calls like custom frontend over white-label, scaling for major events—but we built a differentiated product that stood out in a crowded market and earned industry recognition.

2 Industry Awards

Rising Star (1st) and Mobile Sportsbook (2nd) at SBC Awards 2017

Operator of the Year

EGR Nordics 2018 award for best-in-class sportsbook experience

4 Markets

Launched in Sweden, Denmark, UK, and Italy with full regulatory compliance

65%

€41m to €68m revenue growth Q4 2016-2017, with sportsbook as new key driver

Let’s connect!

Let’s connect!

Explore how my executive leadership or advisory services can address your specific challenges.

No pitch, no pressure—just honest conversation about what you need.

Contact Me
Ola Wallin
+39 348 843 9295
hello@olawallin.com
LinkedIn

CONTACT ME