Workshops — Product, AI & engineering

Six workshops. Each ends with something you use next week.

Hands-on, 4 to 8 hours, for founders, leaders and technical teams. Worked on your own product, data and code.

Your work, not case studiesBuilt to change behaviourEnglish or Arabic · in person or remote

Move across to scan

Six workshops — pick one to see the details

01Building Products That Scale Founders · 4h

AI changed how you build and ship. It did not change how you decide what is worth building.

For
Founders
Total
4 hours
Format
1 half-day, in person
Group
8–15 founders
Ask about this workshop

The day

  • SaaS in the LLM era: which layer are you on?
  • Your best customer segment, and a roadmap cut to serve it
  • Why deals really stall
  • Custom work, packaging and pricing
  • Build live with AI, then evaluate what you built
  • Retention and the metrics that matter

You leave with

  • A named target segment and a re-cut roadmap
  • A written rule for custom requests
  • A pricing metric decision
  • An eval set for one AI feature
  • Actions to start next week, with no extra budget

Before the day

  • Paying customers
  • A 15-minute diagnostic completed in advance
  • Your roadmap, last 5 won and 5 lost deals, pricing and retention numbers
  • A laptop
02Ship It This Week Founders · 8h over 5 days

A feature that takes three months to build can now be tested with customers in three days. Most teams still build first and ask later.

For
Founders & product teams
Total
8 hours over 5 days
Format
4h Monday · 3 × 20 min check-ins · 3h Friday
Group
6–12 participants
Ask about this workshop

The day

  • Mon, 4h: sharpen the problem, write a one-page brief and a kill condition, build a first version with AI, book 3 customer sessions
  • Tue–Thu, 3 × 20 min: build, test with customers, daily check-in
  • Fri, 3h: present the evidence, peer challenge, decide keep, kill or change

You leave with

  • A working prototype tested by 3 real customers
  • A keep-or-kill decision backed by evidence, not opinion
  • A method for testing any feature in a week

Before the day

  • One product idea or backlog feature you are unsure about
  • Access to 3 real customers or prospects
  • A laptop; no coding required
03AI Foundations Teams · 4h

Your people are already using AI, often in tools you have not approved and with data that should not leave the company.

For
Teams
Total
4 hours
Format
1 half-day, repeatable per team
Group
Up to 25
Ask about this workshop

The day

  • How AI actually works, shown through three live failures: made-up answers, tokens and context, and why it does not know your company
  • Hands-on: one real task from your job
  • The leak test: which data can go where, and prompt injection
  • Ethics in practice: where AI should not decide

You leave with

  • One real task done with AI, and the prompts to repeat it
  • A clear rule on what data goes where
  • Knowing when to trust AI output and when to check it
  • A documented AI-literacy measure for the organisation

Before the day

  • No technical background needed
  • Access to the company's approved AI tool
  • One repetitive task from your own job
  • A 5-minute anonymous survey beforehand

EU clients: supports the AI-literacy duty in Article 4 of the EU AI Act, as amended by the Digital Omnibus in July 2026.

04AI Adoption Playbook Leaders · 8h

Most AI rollouts stall after the licences are bought: either people use it with no rules, or there are rules and nobody uses it.

For
Leaders
Total
8 hours
Format
4h morning, everyone · 4h afternoon, leaders & champions
Group
Up to 25, then up to 15
Ask about this workshop

The day

  • Morning, everyone: the AI Foundations session, condensed
  • Afternoon, leaders and champions: map use cases, scored on time saved, data sensitivity and harm if wrong
  • Design 3 workflows per department, each with a human checkpoint
  • A one-page AI use policy and a list of red-lane uses
  • How to measure adoption, and 30-day commitments

You leave with

  • 3 pilot workflows per department, with before-and-after time estimates
  • A draft AI use policy and data guide
  • A named AI champion in each team
  • A 30-day plan for measuring adoption

Before the day

  • An executive sponsor present for the close
  • Department heads, plus one nominated AI champion per team
  • Each department's most repetitive tasks
  • An anonymous AI-use survey completed beforehand
05Building Production AI Agents Engineers · 8h

Getting an agent to demo is easy. The real job is making it reliable, affordable and safe in production.

For
Engineers
Total
8 hours
Format
1 full day, hands-on
Group
8–16 engineers
Ask about this workshop

The day

  • Agent or workflow: choosing the right architecture
  • RAG that works: chunking, hybrid search, re-ranking
  • Tools, function calling and MCP
  • Multi-agent orchestration, and when not to use it
  • Evals: test sets, grading, catching regressions
  • Cost, latency, guardrails, monitoring

You leave with

  • A working agent with retrieval and tools, built on your own documents
  • An eval set and a baseline score
  • A production-readiness checklist covering cost, security and monitoring

Before the day

  • Comfortable in Python or JavaScript
  • A laptop with a working dev environment
  • Familiarity with REST APIs
  • A use case and sample documents (API keys can be provided)
06AI-Native Engineering Teams Engineering leaders · 6h

AI coding tools make each developer faster. Without shared practices, the team just produces code nobody can review or maintain, faster.

For
Engineering leaders & teams
Total
6 hours
Format
1 day, hands-on
Group
6–15, with their tech lead
Ask about this workshop

The day

  • Where AI speeds engineering up, and where it slows it down
  • Write the spec before the prompt
  • Tests as the contract with the agent
  • AI-assisted code review, and its limits
  • Agents in CI/CD: permissions, guardrails, security

You leave with

  • One real backlog item shipped using the workflow
  • A team agreement for AI-assisted development
  • A CI/CD guardrails checklist
  • Metrics to track the impact: cycle time, rework, defects

Before the day

  • Working engineers
  • A real repo, or a sandbox copy
  • Claude Code, Cursor or similar installed
  • Company approval to use AI tools on the codebase

Delivered by Bassel Jalaleddine

10+ years building SaaS, AI and cloud products. Director of Engineering at EDT&Partners, leading AI adoption and enablement. Entrepreneur in Residence for Scale Now (Qatar MCIT). Founder of eFlow, acquired by EDT&Partners.

Hours are total contact time, including breaks. Every workshop can be tailored in scope, sector and length.