Digital Now 2026 is scheduled for December 9–11 in Casablanca, bringing government officials, executives and startup founders together around digital transformation, cybersecurity and emerging technologies. For Moroccan leaders, its value will not lie in the number of tools on display. It will lie in whether they leave with a shorter list of measurable priorities for revenue, productivity, resilience and data control.

Key Takeaways

  • Treat Digital Now 2026 as a portfolio-review meeting, not a technology showcase.
  • Start from business bottlenecks and baselines before approving AI projects.
  • Test AI readiness across strategy, data, technology, people and governance.
  • Make cybersecurity and data control conditions of deployment, not afterthoughts.

Why the Casablanca congress matters now

Morocco’s Digital Morocco 2030 strategy aims to make the country a regional digital hub. Its published objectives include 240,000 direct jobs, MAD 100 billion in GDP contribution by 2030, better online public services and a stronger role as a producer of digital solutions. Talent, cloud and connectivity are named as accelerators, with AI treated as a cross-cutting priority.

More recent policy reporting describes targets to train 200,000 graduates in AI skills, create 50,000 AI-related jobs, expand sovereign data-centre and cloud capacity, and generate a potential MAD 100 billion GDP contribution from AI by 2030. These are ambitions, not achieved outcomes. They still set a demanding test: investment must produce operational results, not isolated pilots.

Cybersecurity adds urgency. One analysis citing SAMENA Council figures reports 12.6 million attempted cyberattacks against Morocco in 2024, a 40% increase from the previous year, with banking, telecommunications and public-cloud environments among the most targeted sectors. Separate reporting based on Moroccan police data says the DGSN handled 13,643 cybercrime cases in 2025. The figures measure different things—attempted attacks and investigated cases—but together they argue for linking AI programmes to security controls from the start. See Morocco’s cybersecurity crisis guide.

Start with business constraints, not AI tools

Before approving a generative-AI or automation project, leaders should name the bottleneck it is meant to remove: slow customer response, high processing costs, fraud, downtime, regulatory exposure, poor forecasting, manual back-office work or fragmented operational data. Each use case needs a baseline, a responsible owner, a target metric and a review date. Useful measures include processing time, cost per transaction, error rates, revenue per employee, conversion, retention, fraud losses and service availability.

A simple prioritisation rule is expected business value multiplied by feasibility, divided by risk and implementation effort. It does not replace judgement, but it discourages fashionable projects and forces teams to estimate integration, data preparation, training, security and monitoring costs before committing budget.

Assess AI readiness across five layers

Executives can use the congress to benchmark their organisation against five practical dimensions:

  • Strategy: Is there a documented problem that AI is expected to solve?
  • Data: Are data complete, accurate, accessible, classified and legally usable?
  • Technology: Can existing cloud, network, identity and application systems support deployment?
  • People: Do employees have the skills to validate, operate and improve AI systems?
  • Governance: Are privacy, accountability, security, procurement and model-monitoring responsibilities defined?

The weakest layer usually limits the whole programme. A sophisticated model cannot compensate for unreliable data, unclear ownership or workflows employees cannot adopt. Startups comparing providers should test fit with local languages, payment systems and support capacity; see choosing the right AI model for Moroccan startups.

Treat data strategy as operating infrastructure

AI readiness is primarily a data-management question. Organisations should map critical data assets, establish ownership, define retention rules and create quality indicators for completeness, accuracy, timeliness and duplication. They should also decide which workloads can use public cloud services, which require private or sovereign environments, and which data must remain within controlled national or organisational infrastructure.

A credible data strategy should answer five questions: Where is sensitive data stored? Who can access it, and why? Can data be audited and deleted when required? How are third-party AI providers prevented from reusing confidential information? Can the organisation migrate between providers without losing control? Morocco’s cloud and sovereignty priorities should become procurement criteria, not conference language.

Make cybersecurity a condition of AI deployment

AI expands the attack surface through models, APIs, data pipelines, plugins, employee prompts and automated agents. Security teams should evaluate identity and privileged-access controls, encryption and secrets management, prompt injection and data-exfiltration risks, model and software supply chains, vendor incident reporting, logging, monitoring, human override, and recovery procedures for corrupted data or unavailable systems.

The objective is not to eliminate all risk. It is to ensure that each deployment has a defined risk owner, tested safeguards and an acceptable failure mode. That discipline matters more than a generic “secure by design” claim.

Build a 90-day execution plan

The most useful outcome from Digital Now should be a short implementation roadmap:

  • Days 1–30: Select one high-value use case, establish the baseline, inventory required data, and complete a security and legal review.
  • Days 31–60: Run a controlled pilot with representative users, measure quality and productivity, and document failures.
  • Days 61–90: Decide whether to stop, redesign or scale; calculate total cost; assign operational ownership; and define ongoing monitoring.

This separates experimentation from production deployment and gives boards evidence before larger budgets are committed.

Questions leaders should ask at the congress

  • What measurable results has the technology delivered in organisations of comparable size?
  • What is the full cost, including integration, data preparation, training, security and monitoring?
  • Where are customer and business data processed, and what happens when the model is wrong?
  • Can the solution integrate with Moroccan payment, identity, telecom, public-sector or enterprise systems?
  • Which skills must be developed internally, and how will success be reported to investors, employees, customers and regulators?

Payment integration deserves attention as Moroccan commerce moves toward more digital channels; the opportunities and constraints are explored in Morocco’s digital payments shift. Leaders should also consider how Casablanca fits into a wider national innovation map, covered in navigating Morocco’s three-city innovation corridor.

What the event can and cannot tell you

Available event information confirms the dates, location, broad themes, organisers and participant profile, but not a complete official agenda, speaker list, ticketing details or published performance evidence for individual exhibitors. Secondary event listings have also reported different December dates, including December 16–18, so verify the final schedule with the organiser before publication or travel planning.

Morocco’s strategic targets are ambitions, not achieved outcomes. Reporting also indicates that the country does not yet have a comprehensive binding AI-specific governance framework, although AI is incorporated into Digital Morocco 2030 and responsibilities sit partly with the Ministry of Digital Transition and the Digital Development Agency. Businesses should not assume that strategic intent resolves questions of accountability, privacy, procurement or liability.

Turn Casablanca conversations into a portfolio review

Digital Now 2026 should be used as a portfolio-review meeting, not merely a technology conference. The practical test is whether each conversation produces a named use case, a baseline, a data owner, a security review, a budget range and a decision date. Organisations that connect AI use cases to reliable data, cybersecurity controls, accountable teams and measurable outcomes will be better positioned to turn Morocco’s digital ambitions into durable business results.