How to choose and scope an AI studio in Morocco

Write the current workflow as a sequence of steps. For each step, identify the person responsible, the tool used, the input required and the possible exceptions. A provider should be able to explain this map back to you before proposing a build. If the current process is unclear, automation may only make the confusion move faster.

Separate repetitive rules from judgement. Copying an approved customer record into another system may be suitable for automation. Approving a refund, publishing a sensitive message or deciding whether a prospect is genuinely qualified may require human oversight. The boundary should be visible in the brief, not discovered after launch.

Include uncommon cases. Missing fields, duplicate records, expired credentials, rejected payments and unavailable APIs are part of real operations. Ask how the workflow pauses, retries, alerts a person and records what happened. Error handling is a deliverable, not an invisible technical detail.

Different constraints need different forms of work. Process automation is useful when clear rules are executed manually. An integration is useful when information must move reliably between existing tools. A custom CRM is relevant when the sales process, permissions and reporting do not fit the current setup. Website or application work is appropriate when customers or teams need a dedicated interface.

AI video has a different production logic. The brief should define approved source images, brand constraints, advertising formats, review stages and where the final assets will be used. It should not promise media performance that the creative alone cannot guarantee. The provider should distinguish the asset it can deliver from the campaign result you will measure later.

The simplest credible intervention is often the best first phase. A narrow integration may solve the immediate problem without replacing an entire system. A short creative test may answer a visual question before a large production commitment. Ask every provider to explain what it intentionally excluded and why.

List the data the project will read, create, change or send elsewhere. Mark personal data, confidential commercial information and credentials separately. For each category, identify the source, the people who should have access, the necessary retention period and the action required when access must be removed.

Moroccan organizations should assess personal-data processing against the applicable requirements and their own obligations. The CNDP publishes the text of Morocco’s Law 09-08 and supporting material. A studio can help design technical safeguards, but your organization should confirm its legal responsibilities with appropriate counsel when the project handles personal information.

Do not email production passwords or share a permanent administrator account as a shortcut. Ask for a documented access plan using the least privilege needed for the phase. The proposal should say how secrets are stored, which third parties receive data, what logs are retained and how access is transferred or revoked at handoff.

• Systems and data fields involved in the first phase
• Named owners for approvals, credentials and incident decisions
• Third-party services, hosting regions and retention expectations

An automated action still needs an owner. Decide who reviews exceptions, who can change a rule and who can stop the workflow. For generated content, define who approves facts, claims, brand use and publication. For a sales or support system, define when a person takes over and what context must be preserved.

The NIST AI Risk Management Framework is a useful reference for thinking about governance, measurement and risk. You do not need a large compliance programme to apply the underlying discipline: document the intended use, test realistic cases, assign responsibility and monitor whether the system behaves within the agreed boundaries.

Ask how changes will be controlled after launch. A small adjustment to a prompt, field mapping or approval rule can affect downstream outcomes. The project should include a place to record versions, decisions and incidents so that the team can understand why the current behaviour exists.

Two proposals can describe very different projects even when their total cost looks similar. Compare the discovery work, number of workflows or screens, integrations, migration effort, testing, training, documentation and post-launch support. Ask which usage fees, platform subscriptions, hosting costs and model charges remain outside the quoted budget.

A responsible proposal states its assumptions. It should explain what data quality it expects, which APIs must be available, how many review rounds are included and what happens when a dependency changes. Those assumptions let you estimate the real investment and reduce arguments about work that was never included.

Avoid choosing on a promised result that no provider can control alone. A studio can deliver a working system, a documented process or campaign-ready assets. Revenue, adoption and advertising performance also depend on your offer, team, traffic, training and operational follow-through. Agree on the evidence that will show whether the delivered work is functioning as specified.

List each deliverable in plain language. This can include a workflow map, configured environments, source code, design files, prompts, field definitions, dashboards, tests, operating instructions and training. If an item matters to your team after the provider leaves, it belongs in the scope.

Clarify ownership and licences before work begins. Identify which assets you own, which third-party services remain licensed separately and which reusable provider components may be included. Confirm who controls the domain, hosting, repositories, automation accounts and billing relationships. Access should not depend on a former supplier answering a message months later.

Documentation should help a new team member operate the result. Ask for setup instructions, common failure modes, recovery steps, named responsibilities and a record of important decisions. A live handoff session is useful, but it should complement written material rather than replace it.

Score providers against the same questions instead of comparing polished presentations. Look for evidence that they understand the workflow, can explain risks without drama and are willing to reduce scope when a simpler solution is sufficient. A good answer should reveal trade-offs, not hide them behind technical vocabulary.

Ask for a proposed first milestone that produces something inspectable: a validated process map, a working integration in a test environment, a CRM prototype with sample data or a small set of creative directions. Define the acceptance decision in advance. You should know what will make you continue, revise or stop.

Finally, evaluate communication fit. For a Moroccan team that works across Arabic, French and English, language can affect discovery, training and adoption. Confirm who will run workshops, who makes technical decisions and how often progress, risks and decisions will be documented.