Skip to content
Brahim AI

An engineer who likes connecting the dots.

I work at the intersection of software, data and AI. My focus is turning what is possible, agentic AI included, into useful software people can actually work with.

Tell me about your project
  • Software and apps
  • Automation and data
  • AI agents

Founder and engineer

Portrait of Brahim El Mimouni
Brahim El MimouniBuilding Brahim AI. Exploring how agents, tools and good engineering fit together.

Available for new projects

The whole system, beyond the prompt.

I’m interested in what happens when an AI model becomes part of real software: the tools it can use, the context it needs and the way a team stays in control.

  1. Agent orchestration

    Turning a goal into a sequence of tool calls, decisions and review steps.

  2. Knowledge & retrieval

    Connecting models to useful information, with sources and access boundaries.

  3. Evaluation & reliability

    Testing behavior, understanding failures and making systems easier to operate.

How I think about the work

I'm Brahim El Mimouni, the engineer behind Brahim AI. I work across AI, backend development and data engineering. I’m drawn to the point where those disciplines meet: a system that understands a task, connects to the right information and helps someone get useful work done.

That means thinking beyond a model’s answer. The API needs to handle failure. The data needs to be trustworthy. The person using the system needs to know what it can do and when to step in. Those details are part of the product.

Why agentic AI interests me

Agents bring reasoning and action into the same workflow. A system can retrieve context, choose a tool, inspect the result and decide whether it has enough information to continue. That opens up useful possibilities in support, research, operations and reporting.

My approach is to keep the scope clear. I define the goal, the tools available to the agent and the conditions for stopping or asking for help. Retrieval gives it relevant knowledge; state keeps track of the work; evaluation helps reveal where its behavior needs to improve. When a task needs several stages, I make the handoffs explicit before adding more agents.

For me, a useful agent should be inspectable. You should be able to see which sources it used, what actions it proposed and which decisions still belong to a person.

A direct line from idea to implementation

Brahim AI is how I put that approach into practice. You work directly with me to understand the workflow, make a plan and build the system. There is one accountable point of contact from the first conversation to handover.

We start with a practical problem and a clear definition of success. Sometimes that calls for an AI assistant. Sometimes a straightforward integration is enough. The solution follows the business need.

What you can expect

  • A clear scope. Milestones, price and running costs agreed before the build begins.
  • Working progress. Short iterations and real scenarios you can review along the way.
  • People in control. Permissions, human review and a recovery path appropriate to the workflow.
  • A useful handover. Documentation and a walkthrough so your team understands what it owns.

Working together

Engagements are a Roadmap, a Starter build or a Care plan, each with a fixed price agreed in writing. A first conversation helps us understand the opportunity and whether Brahim AI is the right fit. You do not need a technical brief; a description of the work that slows your team down is a good place to start.

Find me elsewhere

A closer look at the code.

You can find my public repositories and follow what I’m building on GitHub.

Visit my GitHub profile

Start here

Tell me about the work that slows your team down.

A 20-minute call, no obligation. You leave with a written next step whether or not we work together. Plain language is fine; you do not need a technical brief.

Tell me about your project

Prefer to write? [email protected]

I read every message myself and usually reply within one business day.