AI Maturity Assessment
See how your engineering teams compare with peers on AI adoption and implementation.
Get a step-by-step playbook to help your team advance.
Assessment Access
Tools Matrix Access
AI Tools Matrix
AI Hackathon Playbook
A comprehensive guide to running successful AI hackathons that drive innovation and adoption
Table of Contents
Introduction
Executive Summary
This guide distills the experience of organizations that have run transformative AI hackathons achieving 15-20% productivity improvements and fundamentally changing their AI adoption culture. A well-structured hackathon serves as a cultural accelerator for AI adoption, breaking down barriers and creating lasting organizational change.
Why Run an AI Hackathon?
The AI Adoption Challenge
Many organizations face a common problem: despite significant investment in AI tools like GitHub Copilot and Microsoft 365 Copilot, they struggle to achieve the promised productivity gains. Common barriers include:
- Legacy codebases that seem incompatible with AI tools
- Poor documentation that limits AI effectiveness
- Skepticism that AI only works for greenfield projects
- Lack of hands-on experience with AI capabilities
- "AI envy" - seeing headlines about competitors' success without knowing how to replicate it
The Hackathon Solution
A hackathon can serve as a cultural accelerator that:
- Breaks down psychological barriers to AI adoption
- Creates hands-on experience with AI tools
- Generates concrete proof points for AI value
- Identifies AI champions who can spread knowledge
- Develops organizational AI literacy rapidly
Key Success Metric
Organizations can realistically expect 15-20% overall productivity improvements with proper hackathon execution and follow-through, based on real-world implementations.
Pre-Hackathon Planning
1. Secure Leadership Buy-In
Leadership support is the single most critical factor for hackathon success. Without genuine executive buy-in, teams will face resource constraints, approval bottlenecks, and lack of follow-through that kills innovation momentum. The key is positioning the hackathon not as a costly experiment, but as a strategic investment in organizational capability building.
Executives are often skeptical of hackathons because they've seen them fail to deliver business value. Address this by emphasizing measurable outcomes, time-bounded commitment, and clear learning objectives. Remember: you're not asking for a massive budget—you're asking for permission to remove constraints and prove what's possible.
Building the Business Case
- Present concrete metrics: Reference Microsoft/Accenture study showing 26% developer productivity gains
- Frame as limited-time experiment: Minimal risk, maximum learning potential
- Emphasize learning objectives: Focus on capability building alongside deliverables
- Secure executive sponsorship: C-level participation demonstrates commitment
2. Call for Volunteers
The volunteer selection process is critical for hackathon success:
- Send clear vision memo: Outline hackathon objectives and expectations
- Allow self-selection: You want AI-curious participants who are motivated
- Don't limit team size artificially: If 35 people volunteer, use them all
- Target 15-20% of development organization: Critical mass for cultural change
- Include diverse skills: Developers, designers, product managers, domain experts
Participation Strategy
Broad participation creates network effects. More participants mean more learning, more champions, and greater organizational impact. Quality emerges from quantity when properly structured.
3. Define Strategic Focus Areas
Select 4-6 strategic areas that matter to your business. Successful organizations have chosen:
Adjacent Business Opportunities
New product lines, service extensions, market expansions enabled by AI
Customer-Facing Features
Portals, personalization, chatbots, recommendation systems
Technical Capabilities
AI-powered imaging, OCR, automation, API frameworks
Platform Evolution
Marketplaces, integration platforms, developer tools
Process Improvement
AI SDLC, governance frameworks, workflow automation
Data Intelligence
Analytics, insights generation, predictive capabilities
4. Remove All Constraints
Critical for Success
This is the most important success factor - create true innovation freedom:
- Allow any tools, frameworks, or cloud services
- Permit greenfield development
- Remove architectural restrictions
- Suspend normal approval processes
- Make it clear there are "no sacred cows"
The goal is to discover what's possible when traditional constraints are removed.
Execution: 5-Day Sprint Structure
Day 1: Ideation & Team Formation
- Problem statement presentations
- Idea pitching sessions
- Team formation (4-6 members)
- Initial project scoping
Days 2-3: Development Sprint
- Intensive development and prototyping
- Regular mentor check-ins
- Technical workshops and support
- Progress reviews and pivoting
Day 4: Refinement & Preparation
- Solution refinement and testing
- Presentation preparation
- Demo rehearsals
- Business case development
Day 5: Presentations & Judging
- Final presentations (10 minutes each)
- Live demonstrations
- Judging and deliberation
- Awards ceremony and next steps
Success Factors
🎯 Clear Objectives
Well-defined problem statements with measurable outcomes
🛠️ Tool Access
Pre-configured environments with AI/ML tools and datasets
👥 Expert Support
Available mentors and technical assistance
⚡ Rapid Iteration
Focus on working prototypes over perfect solutions
Evaluation Framework
Judging Criteria
Business Impact (30%)
- Potential ROI and value creation
- Alignment with strategic objectives
- Market opportunity size
Technical Innovation (25%)
- Novel use of AI/ML techniques
- Technical complexity and sophistication
- Scalability and performance
Feasibility (25%)
- Implementation complexity
- Resource requirements
- Time to market
Presentation (20%)
- Clarity of communication
- Demo effectiveness
- Team collaboration
Evaluation Process
- Initial Screening: Technical feasibility review
- Business Review: Strategic alignment assessment
- Final Judging: Comprehensive evaluation by panel
- Audience Choice: Peer voting for innovation award
Post-Hackathon Actions
Immediate Actions (Week 1)
- Document all solutions and learnings
- Conduct team retrospectives
- Prioritize winning solutions for development
- Assign project owners and resources
- Communicate results organization-wide
Medium-Term Actions (Months 1-3)
- Develop detailed implementation roadmaps
- Secure funding and resources for selected projects
- Form dedicated development teams
- Begin pilot implementations
- Plan follow-up hackathons
Success Metric
Aim for at least 30% of hackathon solutions to progress to pilot or production within 6 months.
Measurement & KPIs
Event Metrics
Participation
- Number of participants
- Cross-functional representation
- Engagement scores
Innovation
- Number of viable solutions
- Technical complexity achieved
- Novel use cases identified
Business Value
- Projected ROI of solutions
- Strategic alignment score
- Market opportunity size
Long-term Impact
AI Adoption Performance Index
Track progress across key dimensions:
- Solution Deployment: % of hackathon solutions in production
- Skill Development: AI competency growth across teams
- Cultural Change: Innovation mindset adoption
- Business Impact: Revenue/cost benefits realized
Tools & Technologies
Development Tools
Based on our Tools Matrix analysis, here are the most popular AI development tools:
Most Popular Tools
- GitHub Copilot
- Cursor
- Claude Code
- Visual Studio IntelliCode
AI Development Tools
- JetBrains AI
- OpenAI Codex
- Kiro
- Sourcegraph
Emerging Tools
- Lovable
- GitLab Duo
- CodeWhisperer
- Xcode AI
Pre-configured Environments
Setup Requirements
Prepare standardized development environments with pre-installed libraries, sample datasets, and API access to minimize setup time during the hackathon.
Common Pitfalls
❌ Overly Complex Problems
Issue: Choosing problems too complex for a 5-day sprint
Solution: Focus on well-scoped, achievable objectives with clear success criteria
❌ Insufficient Data Access
Issue: Teams spending time on data acquisition instead of solution development
Solution: Pre-curate and clean datasets, ensure proper access permissions
❌ Lack of Business Context
Issue: Technical solutions without clear business value
Solution: Include business stakeholders as mentors and judges
❌ No Follow-through
Issue: Great ideas die after the event ends
Solution: Establish clear post-hackathon development pathways
The Path Forward: From 20% to 200%
After achieving initial success with 15-20% productivity improvements, set ambitious targets for transformational change. The hackathon is not the destination—it's the catalyst that accelerates your journey to becoming an AI-first organization.
Advanced AI Integration Areas
1. Semantic Search for Legacy Codebases
Transform how developers navigate and understand existing code through AI-powered semantic search and documentation generation.
2. AI Code Review Automation
Implement intelligent code review systems that understand context, patterns, and business logic beyond simple static analysis.
3. Workflow Automation Beyond Coding
Extend AI capabilities to project management, deployment pipelines, and business process automation.
4. AI-Augmented Product Management
Use AI for market research, user story generation, competitive analysis, and product roadmap optimization.
5. Domain-Specific AI Agents
Develop specialized AI agents that understand your business domain, compliance requirements, and industry-specific workflows.
6. AI-Powered DevOps and CI/CD
Intelligent monitoring, automated incident response, predictive scaling, and self-healing infrastructure.
Building AI-Native Workflows
Moving beyond tool adoption to true AI-native operations requires fundamental changes in how your organization approaches every aspect of software development and business processes. This isn't about adding AI as a layer on top of existing workflows—it's about reimagining those workflows from the ground up with AI as a core assumption.
Organizations that achieve 200%+ productivity improvements don't just use AI tools more effectively; they restructure their entire development lifecycle around AI capabilities. This means rethinking everything from how requirements are gathered to how code is reviewed, deployed, and maintained. The goal is to create seamless human-AI collaboration where AI amplifies human capabilities rather than simply automating tasks.
Systematic Transformation
- Develop processes for moving from AI prototypes to production systems
- Create design system integration for AI-generated components and interfaces
- Build feedback loops for continuous improvement and learning
- Establish centers of excellence to spread best practices and maintain standards
- Create AI governance frameworks that scale with adoption
The Ultimate Goal
The goal isn't just to use AI tools; it's to fundamentally transform how your organization thinks about and approaches problem-solving in the age of AI. A hackathon provides the perfect laboratory for this transformation.
Remember: The "afterglow" of a successful hackathon can power months of continued innovation and productivity gains. Sustain that momentum through systematic follow-up and ambitious vision.
Conclusion
A well-executed AI hackathon can transform your organization's relationship with AI, moving from skepticism to enthusiasm, from potential to proven value. The key is to:
- Remove all barriers during the hackathon
- Measure everything to prove value
- Share knowledge aggressively
- Sustain momentum through systematic follow-up
- Scale successes into production quickly
With Thanks
We extend our sincere gratitude to Iarfhlaith Kelly, CTO at Ocuco, and his exceptional engineering team for their valuable insights and real-world experiences that helped shape this comprehensive hackathon playbook.
Their proven track record of successful AI adoption and innovative approach to team development has been instrumental in creating a guide that delivers practical, actionable results for organizations embarking on their AI transformation journey.
AI Skunkworks Playbook
A comprehensive guide to launching successful AI Skunkworks that deliver breakthrough results
Table of Contents
What is a Skunkworks Project?
A skunkworks project is an autonomous innovation initiative where a small, cross-functional team operates outside standard corporate processes to achieve breakthrough results rapidly. Core characteristics include isolated operation from bureaucracy, 4-12 elite team members, high autonomy, specific ambitious goals, rapid iteration, and tight deadlines (30-90 days for initial results).
Why Skunkworks for AI Adoption?
Traditional AI adoption faces predictable barriers that skunkworks projects uniquely overcome. Organizations invest heavily in tools like GitHub Copilot and Microsoft 365 Copilot but struggle to achieve promised productivity gains. Common obstacles include:
- Skepticism that AI only works for greenfield projects
- Legacy codebases that seem incompatible with AI tools
- Lack of hands-on experience with AI capabilities
Skunkworks projects serve as cultural accelerators that break these psychological barriers through direct experience. Unlike traditional pilots that move cautiously, skunkworks initiatives embrace calculated risk-taking and rapid iteration. They create concrete proof points that demonstrate AI's value in your specific context, not just in vendor demos or competitor press releases.
Start Here: Your 90-Day Roadmap
Successful AI skunkworks projects solve specific business problems with measurable impact, operate with significant autonomy, and maintain direct executive sponsorship. Most failures occur when teams lack clear success metrics or proper data infrastructure. The roadmap deliberately compresses timelines to force creative solutions and prevent overthinking.
Days 1-30: Foundation and Team Assembly
- Secure executive sponsorship with defined success metrics
- Issue open call for volunteers (target 15-20% of engineering organization)
- Define 4-6 strategic focus areas aligned with business priorities
- Remove ALL constraints: tools, frameworks, architectural restrictions
- Establish baseline metrics across speed, value, quality, and predictability dimensions
Days 31-60: Sprint Execution
- Run 5-week development sprint with daily cross-team knowledge sharing
- Maintain regular business operations (limit to 2 days per person on skunkworks)
- Create working prototypes, not just concepts or presentations
- Document both successes AND failures as equally valuable learning
- Hold weekly steering committee reviews for alignment without bureaucracy
Days 61-90: Scale and Integrate
- Select 2-3 prototypes for immediate productionization
- Conduct weekly demos to entire organization (the "afterglow" effect)
- Establish AI governance and SDLC frameworks
- Expand tool licenses based on proven success
- Create formal rollout plan for broader adoption
Real-World Validation
These approaches have been battle-tested in production environments with remarkable results:
Basware's Project Tsunami
4 team members delivered 22 major features in 12 working days, generating 286,000+ lines of code. Their revolutionary insight: traditional product management must shift from defining "what" applications do to understanding "how" database interactions and business rules work. This fundamental reframing enabled their AI to operate effectively within architectural constraints.
Duett
Compressed a two-month timeline into four weeks, achieving a working solution after just one week with only 3 developers, 1 QA, and 1 tech lead. They succeeded without dedicated product or design support by pairing AI generation with rigorous human review and implementing domain-first prompting strategies.
Pre-Project Planning
1. Secure Executive Sponsorship
Executive commitment is the single most critical factor for skunkworks success. Unlike hackathons, skunkworks projects require sustained support over 90+ days, making genuine leadership buy-in essential. Without it, teams face resource constraints, approval bottlenecks, and organizational resistance that kills innovation momentum.
Position the skunkworks not as a risky experiment, but as a strategic capability-building initiative with measurable outcomes. Executives are often skeptical because they've seen innovation projects fail to deliver business value. Address this by emphasizing concrete deliverables, time-bounded commitment, and clear success metrics.
Building the Executive Case
- Present concrete metrics: Reference proven 15-20% productivity improvements from similar initiatives
- Frame as capability investment: Building long-term organizational AI competency
- Define clear success criteria: Specific, measurable outcomes tied to business objectives
- Secure active sponsorship: C-level participation in weekly reviews and decision-making
- Guarantee learning documentation: Value creation even if project doesn't reach production
2. Recruit Motivated Volunteers
Team selection determines project trajectory more than any other factor. Unlike traditional assignments, skunkworks requires self-motivated participants willing to work outside standard processes:
- Issue clear vision memo: Outline project objectives, expectations, and time commitment
- Allow self-selection: Volunteers bring intrinsic motivation essential for breakthrough work
- Target 4-8 core members: Small enough for speed, large enough for diverse expertise
- Include strategic skeptics: Ensure groundedness and credibility with broader organization
- Mix experience levels: Senior architects for decisions, junior developers for energy and fresh perspective
The Volunteer Advantage
Self-selected teams consistently outperform assigned teams by 2-3x in innovation contexts. Volunteers have personal investment in success and willingness to work through ambiguity that mandated participants often lack.
3. Define Strategic Focus
Select 1-2 strategic areas maximum for focused execution. Unlike hackathons with multiple parallel tracks, skunkworks succeeds through deep focus on specific problems with clear business impact:
Core Product Enhancement
AI-powered features that differentiate your primary offering and drive user engagement
Operational Efficiency
Process automation and workflow optimization with measurable productivity gains
Customer Experience Innovation
New interaction paradigms that fundamentally improve user experience and satisfaction
Adjacent Market Opportunity
AI-enabled expansion into new customer segments or use cases
4. Eliminate Organizational Constraints
Essential for Breakthrough Results
The most important success factor - create genuine innovation freedom by removing typical corporate limitations:
- Technology freedom: Any tools, frameworks, or cloud services needed
- Architectural autonomy: Permission to build greenfield solutions
- Process suspension: Bypass normal approval workflows for speed
- Budget flexibility: Pre-approved spending authority for tools and services
- Communication direct lines: Direct access to executives and domain experts
- "Sacred cow" immunity: Permission to challenge existing systems and assumptions
The goal is discovering what's possible when traditional corporate constraints are temporarily removed. This freedom is what enables breakthrough innovation.
5. Establish Success Metrics
Define specific, measurable outcomes that justify the investment and guide decision-making throughout the project:
Business Impact Metrics
- Revenue attribution from AI features
- Cost reduction from process automation
- Customer satisfaction improvements
- Market differentiation achievements
Technical Achievement Metrics
- Development velocity improvements
- Code quality maintenance or improvement
- Architecture scalability demonstrations
- Integration success with existing systems
Organizational Learning Metrics
- Team AI competency development
- Knowledge transfer to broader organization
- Cultural change indicators
- Future project readiness assessment
Team Composition and Dynamics
Core Team Structure (4-8 members)
The optimal team size balances diverse expertise with communication efficiency. Smaller teams move faster but may lack critical skills; larger teams bring more capabilities but suffer from coordination overhead.
Technical Lead (1)
Bridges architecture and implementation, makes rapid technical decisions, coordinates with stakeholders
Developers (2-3)
Must understand both "what" requirements mean and "how" to constrain AI implementation
UX Designer (1)
Focuses on human-AI interaction patterns, ensures consistency across AI-generated interfaces
Product Manager (0.5-1)
Drives rapid customer iteration, maintains business alignment, documents learnings
Why These Specific Roles Matter
The technical lead prevents architectural drift that AI can introduce. Developers must think like architects, not junior programmers—as Basware learned, "any developer can prompt AI to generate code, but the valuable ones know how to constrain it." The UX designer addresses the common problem of "messy UI generation" that both Duett and Basware encountered. The product manager ensures business value remains central when technical possibilities explode.
The 5-Week Sprint Structure
Based on proven implementations from Duett, Basware, and Ocuco, this sprint structure balances speed with quality:
Week 0: Planning and Preparation
- Define MVP scope with clear success criteria
- Conduct AI tool training for all participants
- Set up development environments and repositories
- Establish daily standup and weekly review schedules
- Create evaluation framework with weighted criteria
Week 1: Rapid Prototyping
The goal is a working demo by week's end, even if rough. This creates momentum and makes the project tangible for stakeholders.
- Start with clickable prototype or wireframe
- Experiment with multiple AI tools and approaches
- Daily check-ins to share tool discoveries
- Document what doesn't work (equally valuable as successes)
- First demo to stakeholders by Friday
Week 2: Architecture Validation
Ensure the foundation is solid before building features. This prevents the technical debt that rapid AI development can create.
- Verify data flows and system integration points
- Establish architectural constraints for AI
- Refine based on Week 1 learnings
- Mid-sprint demo to wider audience
- Begin customer validation if applicable
Week 3: Feature Development
Focus on building the core value proposition with enough polish to demonstrate viability.
- Implement main features with AI assistance
- Address code quality issues from earlier sprints
- Enforce smaller PRs with clear ownership
- Introduce UX checkpoints for consistency
- Continue daily knowledge sharing
Week 4: Polish and Handoff
Prepare for either productionization or knowledge transfer, depending on project success.
- Final demo preparation with full functionality
- Document architecture and key decisions
- Create knowledge transfer materials
- Conduct retrospective capturing learnings
- Develop scale-up plan if moving forward
Week 5: Momentum Maintenance
The "afterglow" period where successful projects gain organizational support.
- Present to entire organization
- Begin productionization planning
- Expand tool access based on proven value
- Identify next sprint opportunities
- Transfer knowledge to non-participants
Risk Management and Mitigation
Code Quality Challenges and Solutions
Real implementations revealed specific challenges requiring targeted solutions:
Challenge: Oversized PRs Overwhelming Review
Solution:
- Enforce maximum 200 lines changed per PR
- Implement "PR splitting" practice for large features
- Use feature flags for incremental deployment
Challenge: Messy UI Generation
Solution:
- Create design system components AI must use
- Pair AI generation with designer review for all UI
- Maintain component library with clear usage guidelines
Challenge: Context Loss in AI-Generated Code
Solution:
- Implement domain-first prompting strategies
- Include architectural context in every prompt
- Use retrieval-augmented generation (RAG) for codebase knowledge
Challenge: Ownership Ambiguity
Solution:
- Assign feature leads responsible for AI output
- Implement traceability from requirements to code
- Maintain clear documentation of AI-generated sections
Organizational Resistance Patterns
Address the human side of AI adoption with targeted strategies:
The Skeptic Contingent (40-50% of organization)
- Include skeptics in skunkworks teams for credibility
- Focus on measurable improvements, not hype
- Share failures openly to build trust
The Fearful (concerned about job displacement)
- Emphasize augmentation, not replacement
- Provide reskilling opportunities
- Celebrate how AI eliminates mundane work
The Overwhelmed (struggling with pace of change)
- Implement gradual rollout with support
- Create AI literacy programs at multiple levels
- Pair early adopters with those needing help
Critical Success Factors
Executive Commitment Beyond Sponsorship
True executive support means more than approval and budget. It requires active participation in demos, public celebration of failures as learning, protection from organizational antibodies, and willingness to change processes based on findings. The executive sponsor should spend 2-4 hours weekly engaged with the skunkworks team.
Data Readiness as Foundation
AI without data is like a race car without fuel. Before launching, audit your data quality and accessibility, implement basic governance if lacking, ensure compliance with privacy regulations, and create data pipelines for model training. Poor data quality causes 60-70% of AI project failures.
Cultural Readiness Indicators
Look for these signs your organization is ready:
- Previous successful innovation initiatives
- Comfort with experimentation and failure
- Cross-functional collaboration patterns
- Investment in employee development
- Customer-centric decision making
Organizations lacking these indicators need cultural work before AI initiatives.
Integration Planning from Day One
Successful experiments that can't scale create frustration. Plan the path from prototype to production before starting, including technical architecture alignment, operational handoff procedures, training and documentation requirements, and support model definition. The best skunkworks projects seamlessly transition to business-as-usual.
The Path Forward
Success in AI skunkworks requires balancing seemingly contradictory forces. You need speed without sacrificing quality, autonomy while maintaining alignment, innovation that can integrate with existing systems, and risk-taking within responsible boundaries.
Start small but think big. Your first skunkworks project proves the model works; subsequent initiatives transform your organization. View AI not as a project but as a fundamental capability requiring continuous investment and evolution.
Most importantly, remember that skunkworks projects are about people, not technology. They succeed when talented individuals receive trust, resources, and clear objectives. The AI tools are powerful, but human creativity and judgment remain irreplaceable.
Next Steps by Role
For Executives
- Identify your highest-impact business problem solvable with AI
- Allocate budget and resources for 90-day initiative
- Select executive sponsor with weekly time commitment
- Define success metrics tied to business objectives
- Prepare organization for rapid change
For Technical Leaders
- Assess current architecture for AI readiness
- Identify technical champions for skunkworks team
- Evaluate and provision AI development tools
- Establish governance framework for AI code
- Plan knowledge transfer mechanisms
For Product Managers
- Map customer problems to AI solution potential
- Define MVP scope achievable in 5-week sprint
- Establish customer validation approach
- Create measurement framework for value
- Prepare scaling plan for successful experiments
For Developers
- Experiment with AI tools on personal projects
- Learn prompt engineering fundamentals
- Understand architectural patterns for AI
- Practice code review of AI-generated code
- Document patterns and anti-patterns discovered
The journey to AI-native development starts with a single sprint. Whether through skunkworks projects or hackathons, the key is starting now, learning rapidly, and scaling what works. The organizations succeeding with AI aren't waiting for perfect conditions—they're creating them through experimentation and iteration.
With Thanks
We extend our heartfelt appreciation to the engineering leaders who shared their real-world skunkworks experiences and insights that shaped this comprehensive playbook:
- Kartik Sharma, Vice President, Product Development at Basware
- Antti Stenvall, Senior Manager at Basware
- Øyvind Bauer, CTO at Duett
- Piotr Musial, Director of Engineering at Duett
- Piotr Walczuk, Tech Lead at Duett
Their proven track record of delivering breakthrough results through AI-powered skunkworks initiatives has been instrumental in creating a guide that provides practical, actionable strategies for organizations ready to accelerate their AI transformation journey.
About the Assessment
Comprehensive Analysis
Our assessment evaluates your AI maturity across key dimensions of the Software Development Life Cycle (SDLC).
Industry Benchmarking
Compare your results against industry peers and see where you stand in the AI maturity landscape.
Actionable Insights
Receive personalized recommendations to advance your AI capabilities and drive business value.
Join the Conversation
Connect with AI professionals across AKKR's portfolio companies and explore the latest tools, insights, and best practices shaping the future of AI adoption.
Discover how leading organizations are implementing AI, share your experiences, and get answers from practitioners who have successfully navigated the AI transformation journey.
About the Team
Built by engineering and product leaders who understand the challenges of AI adoption in real-world organizations.
Advisors & Partners
With Thanks
We extend our heartfelt appreciation to the engineering leaders who shared their real-world experiences and insights that shaped our comprehensive AI playbooks:
Basware
- Kartik Sharma, Vice President, Product Development
- Antti Stenvall, Senior Manager
Duett
- Øyvind Bauer, CTO
- Piotr Musial, Director of Engineering
- Piotr Walczuk, Tech Lead
Lemontech
- Ezequiel Rabinovich, CTO
Ocuco
- Iarfhlaith Kelly, CTO
Their proven track record of delivering breakthrough results through AI initiatives has been instrumental in creating practical, actionable guidance for organizations ready to accelerate their AI transformation journey.