Independent software and AI engineer

Custom software, automation and AI for small businesses.

Apps, connected tools, dashboards and AI assistants, built end to end by one senior engineer. A written plan and a fixed price come first.

Tell me about your project or write to [email protected]

No obligation. I read every message myself and usually reply within one business day. A free 20-minute call often comes next.

Who you work with

Brahim El MimouniFounder and engineer, Brahimai LLC. The person you talk to is the person who does the work.

Available for new projects

Usually replies within one business day

One engineer: from the first call to the handover
1 business day: the usual time to get a reply
3 languages: English, Arabic and French
Worldwide: fully remote, registered as Brahimai LLC in Wyoming, USA

What I build

What you might ask for, in your own words.

The technology sits underneath each one, for whoever wants to check the details.

All services

AI assistants and agents

An assistant that answers from your own documents and shows its sources

An assistant that answers from your approved files, shows its sources and hands over to a person when unsure. Agents go further: they read an inquiry, check your systems and prepare the next action for your approval.

You might ask for: a support assistant, a policy question bot, AI that reads invoices and emails into your systems, an agent that drafts CRM updates.

OpenAI, Anthropic Claude, Google Gemini, Llama and Mistral, pgvector, Pinecone, Qdrant, LangGraph, Vercel AI SDK, MCP, promptfoo, LangSmith

Automation and integrations

Your tools connected, so the busywork runs on its own

A form is filled and the deal appears in the CRM with sales already notified. Orders flow into accounting. The Monday report sends itself. Each step checks its own result and tells you when something needs a person.

You might ask for: connect my CRM to invoicing, sync orders to the warehouse, stop re-typing data every week, replace an expensive Zapier setup.

n8n, Make, Zapier, Power Automate, HubSpot, Salesforce, Pipedrive, QuickBooks, Xero, Stripe, Slack, Google Workspace, Microsoft 365, Airtable, Notion, Webhooks, Python, Node.js

Data and reporting

All your numbers in one dashboard that updates itself

Sales, ads, store and CRM data pulled into one place, cleaned, with agreed definitions so everyone quotes the same figure. A live dashboard, a scheduled report, and a check that flags stale or missing data before you rely on it.

You might ask for: one dashboard for the whole business, a weekly report that sends itself, KPIs by store or rep, a forecast for stock or demand.

PostgreSQL, BigQuery, Snowflake, dbt, Airflow, Dagster, Fivetran, Airbyte, Looker Studio, Power BI, Metabase, Tableau, Python, SQL

Web apps, portals and internal tools

A web app or customer portal that replaces the spreadsheet

Logins, roles, approvals, uploads and reports for your team or your clients, built around how you actually work. From a first version to show investors to the admin panel your operations team lives in.

You might ask for: a client portal, a booking system, an MVP in weeks, a tool to approve requests, a CRM that fits how we sell.

Next.js, React, TypeScript, Node.js, FastAPI, Django, Laravel, Ruby on Rails, PostgreSQL, Supabase, Firebase, Stripe, Clerk, Auth0, Retool, Appsmith

Mobile apps

Your app in the App Store and on Google Play

iPhone and Android from one codebase, with accounts, push notifications, offline mode and the store submissions handled. For your customers, or for a field team that needs photos, signatures and a job list without signal.

You might ask for: an app for our drivers, a loyalty app, turn our website into an app, fix an app Apple rejected.

Flutter, React Native, Expo, Swift, SwiftUI, Kotlin, Jetpack Compose, Firebase, Supabase, App Store Connect, Google Play Console

Websites and online stores

A website or online store that brings in inquiries, not just compliments

A fast site your team can edit, built to rank, with analytics and a contact flow that works. Online stores set up or fixed, with checkout, subscriptions and the connection to accounting and fulfillment.

You might ask for: a site that ranks on Google, a landing page for the launch, launch my store, my Shopify theme broke, move from WooCommerce to Shopify.

Next.js, Astro, WordPress, Webflow, Framer, Shopify, WooCommerce, Sanity, Contentful, Klaviyo, Google Analytics

Backend, APIs and cloud

Hosting, APIs and deployments that do not need babysitting

The part your customers never see and always feel: an API for partners and apps, accounts and permissions, payments, automatic deployments, backups you can restore, alerts when something breaks, and a cloud bill you can explain.

You might ask for: speed up the slow app, move off the old server, set up staging, our AWS bill exploded, add single sign-on.

AWS, Google Cloud, Azure, Vercel, Cloudflare, Docker, Kubernetes, Terraform, GitHub Actions, Redis, REST, GraphQL, Sentry, Grafana

Care plans, testing and second opinions

Keep it running, or take over what someone else built

Updates and security patches, tests before each release, monitoring, small fixes every month, and a named person to call. Taking over a codebase whose developer left, upgrading an old framework, or reviewing an agency quote before you sign.

You might ask for: our developer disappeared, it keeps breaking after updates, is this quote fair, are we ready for GDPR or SOC 2, review our developer’s work.

Playwright, Cypress, pytest, Dependabot, Sentry, Uptime monitoring, Backups, OWASP reviews, Framework upgrades, GDPR and SOC 2 readiness

Technology

Any stack you already run.

You do not have to choose a technology to talk to me. I build in what your business already uses, and recommend the simplest tool that will still work in five years.

Languages

Python, TypeScript, JavaScript, SQL, Go, PHP, Java, Kotlin, Swift, Dart, Bash

Web and mobile

React, Next.js, Vue, Nuxt, Svelte, Astro, Tailwind, Flutter, React Native, Expo, SwiftUI, Jetpack Compose

Backend and APIs

Node.js, NestJS, FastAPI, Django, Laravel, Ruby on Rails, .NET, REST, GraphQL, tRPC, Stripe, Twilio, Auth0, Clerk

Databases

PostgreSQL, MySQL, SQL Server, MongoDB, Redis, SQLite, Supabase, Firebase, pgvector, Pinecone, Qdrant

Data and analytics

BigQuery, Snowflake, dbt, Airflow, Dagster, Fivetran, Airbyte, Looker Studio, Power BI, Metabase, Tableau, Google Analytics

Cloud and operations

AWS, Google Cloud, Azure, Vercel, Cloudflare, Docker, Kubernetes, Terraform, GitHub Actions, Sentry, Grafana, Playwright, Cypress

AI and automation

OpenAI, Anthropic Claude, Google Gemini, Llama and Mistral via Ollama, AWS Bedrock, LangChain, LangGraph, LlamaIndex, Vercel AI SDK, MCP, promptfoo, LangSmith, n8n, Make, Zapier, Power Automate

Platforms your team uses

Shopify, WooCommerce, WordPress, Webflow, Framer, Sanity, Contentful, HubSpot, Salesforce, Pipedrive, QuickBooks, Xero, Slack, Google Workspace, Microsoft 365, Airtable, Notion, Retool

AI agents

What an agent looks like inside your business.

An inquiry arrives. The agent reads it, checks the CRM, drafts the follow-up and stops. A person approves it before anything is sent.

Agent run with sample dataFig. 02

Choose a goal

Illustrative workflow

The request

Prepare this lead for follow-up

Allowed tools: Inbox, CRM search

AI agent

Understand
Read the inquiry
Connect
Check CRM context
Prepare
Draft the follow-up
Review
You make the call

Draft for reviewStandby

A follow-up ready to approve

Your next step, made clearer.

Run the simulation to prepare a sample draft.

Check the contact match and approve the proposed update or message before it is sent.

Ready when you are.

Illustrative workflow with fictional sample data. The same boundaries apply to every agent I build: approved tools only, every action traceable, a person in charge of anything consequential.

Build something like this

How I build agents

How it works

A written plan first. Then a build you can watch.

Four steps, the same every time. The scope sheet is what you hold in your hand before any work starts.

A 20-minute call
You describe the work that slows your team down, in plain language. I ask about the tools involved and what a good result looks like. No technical brief needed.
A written plan
Within a week you get a one-page scope sheet: what is included, what is not, the price, the timeline and the running costs. Larger builds start with a Roadmap instead. Nothing starts until you approve it.
The build, with weekly progress
You see working software every week and test it on real scenarios. If something is off, we change course early, while it is still cheap to do so.
Launch, handover, care
Monitoring, documentation and a walkthrough for your team. Everything lives in your own accounts. Then a care plan, if you want someone to call.

Scope sheet, example

Project: Inbox to CRM lead routing
For: Your company
Included: Read new inquiries from the shared inbox
Match or create the contact in HubSpot
Draft a reply and a CRM note for approval
Notify sales in Slack with the summary
Not included: Changes to the HubSpot pipeline. Outbound email sequences.
Approval points: Every reply, before it is sent. Every new contact, before it is saved.
Price: Fixed, stated here
Half at the start, half when it works as agreed here.
Timeline: Three weeks from approval, with a working version to test after week one.
Running costs: Model usage and hosting, estimated per month in this sheet and billed to your own accounts.
Approved by: You, in writing, before anything starts.

Ways to work together

Start small. Scale what works.

Every engagement begins with the free call. After that, three ways to work, each with a fixed price agreed in writing.

One to two weeks

Roadmap

Flat fee, agreed before it starts.

For larger builds: a map of the workflow or product, the simplest build that will work, and a fixed quote for it. You keep the plan whoever builds it.

Written scope, price and timeline
Running-cost estimate for models and hosting
Credited in full if we go on to build

Two to four weeks

Starter build

Fixed price, set in the scope sheet.

A good first project: one agent, automation, dashboard or app feature, built on your own tools and live in weeks. Larger builds are quoted after a Roadmap.

Half at the start, half when it works as agreed
Working progress to test every week
Documentation, a walkthrough and your own accounts

Monthly, cancel any time

Care plan

Flat monthly fee, sized to your system.

Monitoring, updates, small fixes and a named person to call when something needs attention. For what I built, or what someone else did.

A reply within one business day
Updates, security patches and backups checked
Hours each month for small improvements

Tell me about your project

Not sure which one fits? Start with the call and I will tell you.

About

The person you talk to is the person who does the work.

I am Brahim El Mimouni, the engineer behind Brahim AI. I work across AI, backend development and data, and I build the whole thing myself: the app, the integrations, the data behind it and the hosting it runs on. No agency layer, no hand-off to a team you never meet.

I start with the problem, not the technology. Sometimes the answer is an AI assistant; often a straightforward integration does the job. Either way you get readable code in your own accounts, documented decisions and a walkthrough, so the system is yours to keep.

More about me Code on GitHub

What you can expectEvery project

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

Company: Brahimai LLC, registered in Sheridan, Wyoming
Working from: Anywhere. Fully remote, across time zones.
Languages: English, Arabic and French
Not a fit: Games, blockchain, or a developer hired by the hour inside your team

Questions

What people ask before we start.

If yours is not here, it is a good reason to send a message.

How much does a project cost?

Every project gets a fixed price in writing before it starts: a flat fee for a Roadmap, a fixed quote for a Starter build once the scope sheet is agreed, and a quote after a Roadmap for larger apps and portals. Model usage and hosting run in your own accounts and are estimated in the plan, so you see the full cost.

How fast can you start, and how long does it take?

The availability line at the top of this page is kept current. A Starter build is usually live in two to four weeks. An app or a portal usually takes six to ten. The written plan gives you a date before anything starts.

Do we need to change the tools we already use?

Usually not. The goal is to connect what you have. I check the APIs, permissions and integration options of your tools before proposing anything. If a tool cannot support what you need, you hear about the limits and the alternatives before you commit.

Will we own the code?

Yes. Everything is delivered into your own repositories and accounts, with documentation and a walkthrough. If you later work with someone else, they can pick it up.

What if the AI makes mistakes?

We agree what data it can access and which actions need a person to approve. Outputs are tested against real examples from your business before launch, with monitoring and a fallback afterwards. Where an error would matter, review is built in rather than hoped for.

What happens after launch?

You get documentation and a walkthrough so your team understands the system. If you want someone to call, the Care plan covers monitoring, updates and small fixes each month. If you would rather run it yourselves, that is fine too.

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.