[style*="opacity:0"],[style*="opacity: 0"]{opacity:1!important}[style*="translate"]{transform:none!important}

Custom software, AI agents and automation

Your customers are messaging. Nobody is answering fast enough.

I build the system where the conversation and the order are the same thing, so a message that arrives at midnight is answered, qualified and written into your orders without anyone retyping it.

A unified inbox showing WhatsApp conversations, voice notes, customer details and a create order panel
A system I built and shipped: every channel in one inbox, with the customer and the order beside the conversation.

This is for you if

  • Most of your orders start as a message on WhatsApp, Instagram or Messenger
  • You sell on Shopify, YouCan, WooCommerce, or a store you built yourself
  • Someone on your team retypes orders from a chat into another system every day
  • You have tried a chatbot and switched it off because it could not do anything real

This is not for you if

  • You want a landing page and nothing behind it
  • You want the cheapest possible quote rather than the right scope
  • You need it live this week
  • You want to rent software rather than own it

01The cost

What the mess actually costs you

  • Messages nobody sees

    Three inboxes on three phones, and the one that matters is open on somebody's day off.

    The customer buys from whoever answered first

  • Orders retyped by hand

    The chat says one thing, the sheet says another, and the courier gets the third version.

    Every retype is a chance to get the address wrong

  • Nobody can answer about stock

    The real answer lives with one person, and everything waits until they reply.

    You promise what you do not have, or you say nothing

  • Follow up that never happens

    The lead that went quiet is still sitting there, and nobody has time to chase it.

    Demand you already paid for, left on the table

Ready made tools do not fix this

Off the shelf software makes you work the way it was designed, and the gap between that and how you actually sell is exactly where the orders get lost. The fix has to be shaped around your process, not the other way around.

02In practice

A message becomes an order

One real thread, handled start to finish without anyone typing a reply. This is the whole product in ten seconds.

New lead

WhatsApp Business

Agent active

ReplyQualifyOrderSync
  • Answers in seconds, in Darija, Arabic, French or English
  • Checks real stock and real prices before promising anything
  • Writes the order into the system, so nobody retypes it
  • Hands the conversation to a person the moment it needs one

03The difference

A chatbot is not an agent

Same customer, same question, at eleven at night. This is the whole difference.

A chatbot

Matches a keyword against a script somebody wrote months ago

Where is my order? I ordered Tuesday

Thanks for reaching out! For order enquiries please contact our support team during business hours. 🙂

The customer waits until morning, or buys somewhere else

An agent

Looks it up, in your system, right now

Where is my order? I ordered Tuesday

  • findCustomer("+212 6•• ••4 218")
  • listOrders(customerId, limit: 1)
  • getShipment(orderId)

It left the warehouse yesterday and the courier has it now. Expected at your address in Casablanca tomorrow before 6pm. Tracking is 4021 8873.

Answered in nine seconds, with nobody awake

04The boundaries

What the agent will never do without you

Before you let anything automated talk to your customers, you should know exactly where its authority ends. This is written into the system, not left to the model's judgement.

  • Reading and writing are not the same permission

    Looking up an order is free. Changing one, issuing a refund, or cancelling a shipment is gated, and each gate is a decision you make once and can change later.

  • It never invents stock or a price

    Every number it says out loud comes from a lookup against your real data. If the lookup fails, it says it will check, not a guess.

  • It hands over on its own limits

    Anger, a complaint, anything outside what it was given authority over, and the conversation goes to a person with the full history attached.

  • You can read everything it did

    Every conversation and every action it took is logged and searchable. Nothing about it is a black box you have to trust.

05Not a mockup

This is the software running

Screens from eGrow, the pocket CRM and messaging platform I built for Safe Apps. Same shape as what I build for you.

A unified inbox showing WhatsApp conversations, voice notes, customer details and a create order panel

Every conversation in one place

WhatsApp threads, voice notes and images on the left, the customer and their order on the right, and the agent working in the middle.

  • Voice notes transcribed and answered, not ignored
  • The customer record sits beside the conversation, not in another tab
  • An order gets created from inside the thread
  • Labels, assignment and agent cost per conversation, all visible
A visual automation builder showing an order confirmation flow branching into confirm, edit and cancel paths

Automation you can actually see

A real order confirmation flow: the order is created, the condition is checked, the WhatsApp template goes out, and the customer's reply branches the whole thing three ways.

  • Trigger, condition, action, built visually rather than buried in code
  • Confirm, edit and cancel each take their own path
  • Every branch updates the order stage, so the system stays true
  • You can change a delay or a message without calling me

Both screens are from a system in production. Your build is shaped around your process, not this one, but this is the level it works at.

06What you get

One system, six parts

These are not six separate services. They are pieces of the same tool, and they are worth more connected than apart.

01

Unified inbox

Every conversation in one place, next to the customer and what they bought.

What it does

  • WhatsApp, Instagram, Messenger, Telegram, live chat and email in one view
  • The same customer is one customer across every channel
  • Team assignment, roles, quick replies, templates, tags and response time tracking

What lands in your hands

  • The inbox itself, with your team already set up in it
  • Every channel you sell on, connected and tested
  • A handover guide for whoever answers messages day to day

Reads the same customer and order records as the dashboard and the agent.

02

AI agents

Agents that do the work, not chatbots that answer FAQs.

What it does

  • Look up real orders, check real stock, confirm orders, handle cancellations
  • Understand text, voice notes and images, in Darija, Arabic, French and English
  • Hand over to a person the moment they cannot handle something

What lands in your hands

  • The agent, tuned on your real products and your real replies
  • The exact list of what it may do on its own and what needs you
  • A transcript view so you can read every conversation it handled

Calls the same order and stock APIs your dashboard uses, so it cannot promise what you do not have.

03

Automation

Workflows that run without anyone touching them.

What it does

  • Order in, confirmation out, status updates, courier notified
  • Follow up fires on its own when nobody answers
  • Built visually as trigger, condition, action, wired to what you already use

What lands in your hands

  • Your workflows, built and switched on
  • A run history showing what fired, when, and what it did
  • The editor, so you can change a delay or a message yourself

Triggers on events from the inbox and the store, and writes back to both.

04

Custom tools and dashboards

The core of what I do. Everything else plugs into this.

What it does

  • CRM, back office, admin panels, order and stock management, POS, booking
  • Internal tools and reporting built around your process, not a template
  • You own the source code and can host it anywhere

What lands in your hands

  • The application, deployed and running on your own hosting
  • The source code, the accounts and the documentation
  • A walkthrough with your team, recorded so new staff can watch it

This is the system of record. The inbox, the agent and the automation all read and write here.

05

Mobile apps

Often the same system, in the owner's pocket.

What it does

  • Android and iOS from one codebase with Flutter, or native Android with Kotlin
  • Backend included, or connected to the API you already have
  • Published and maintained, not handed over half finished

What lands in your hands

  • The app, published under your own developer account
  • The store listing, screenshots and release notes
  • The signing keys, which stay yours

Talks to the same backend as the web dashboard, so the two never disagree.

06

Web and ecommerce

The storefront, and everything that happens after the order.

What it does

  • Websites, web applications and custom ecommerce built from scratch
  • Or Shopify, YouCan and WooCommerce with the ordering and messaging automated
  • Connected to the same inbox, orders and automation as everything else

What lands in your hands

  • The site or store, live on your domain
  • The admin you actually use to run it
  • Analytics wired up so you can see what happens after the click

Every order it takes lands in the same place as orders that arrive by message.

The inbox knows the order. The agent reads the real stock. The automation updates the dashboard. That only works because it is one system.

08Fits your setup

Works with what you already use

Nothing here asks you to migrate off a platform that is working.

Where customers message

  • WhatsApp
  • Instagram
  • Messenger
  • Telegram
  • Live chat
  • Email

Where orders and stock live

  • Shopify
  • WooCommerce
  • YouCan
  • Google Sheets
  • Your own admin

What runs behind it

  • Laravel
  • Spring Boot
  • Nuxt
  • Flutter
  • MySQL
  • Redis
  • Docker

If it has an API, it connects. If it does not, I build the layer that gives it one.

09How it works

How the engagement works

Fixed scope, fixed price, agreed in writing before I start.

  1. 1

    I understand the problem

    What it is costing you, in money or in hours.

  2. 2

    We agree the fix and the price

    In plain language, before I write any code.

  3. 3

    Built in stages you can see

    Working software every week, not a reveal at the end.

  4. 4

    Tested on your real data

    Real orders, real messages, real edge cases.

  5. 5

    Delivered, and yours

    The code is yours. Keep me on or do not.

You own what I build

This is the part most people are surprised by. The code is yours, not licensed to you. No lock in, no monthly fee to keep your own tool running, no black box you cannot open.

09Questions

The things people ask before they say yes

  • How long does it take?

    It depends entirely on scope, and I will not pretend otherwise on a web page. What I will do on the first call is tell you honestly whether what you want is weeks or months, and what the smallest useful first piece would be.

  • What does it cost?

    Fixed price per agreed scope, quoted in writing after we have talked. I do not publish a price list because the same sentence from two businesses means two very different jobs, and an anchor that turns out to be wrong wastes both our time.

  • Do I own it?

    Yes. The source code, the accounts and the documentation are yours. Host it anywhere, hand it to another developer, change it yourself. There is no licence and no monthly fee to keep your own tool running.

  • What if I want to stop working with you?

    Then you stop, and you keep everything. That is the point of the ownership rule. I would rather you stay because it is working than because leaving is expensive.

  • Will the agent talk to my customers in Darija?

    Yes, and in Arabic, French and English. It also understands voice notes and photos, which matters more here than most people expect.

  • What happens when the AI gets something wrong?

    It is contained by design. It can only act inside the permissions you set, it cannot invent stock or prices, and anything outside its authority goes to a person with the whole conversation attached. You can read every exchange it handled.

  • Can you work with the developer I already have?

    Yes. I have built the piece that plugs into someone else's system more than once, and I would rather do that than argue for replacing something that works.

  • Do you do the mobile app too?

    Yes, Android and iOS from one Flutter codebase, or native Android in Kotlin. Usually it is the same system in the owner's pocket rather than a separate product.

10Contact

Tell me what is breaking.

Describe the problem in your own words and I will tell you what I would build first, and roughly what it takes. I reply within one working day.

[email protected]

Best for detail and attachments

Worth putting in the first email

  • Where your customers message you: WhatsApp, Instagram, a web store, or something else
  • What is going wrong, in your own words, and what it costs you in money or hours
  • What you already use to take orders and track stock
  • Roughly how many orders a day you handle

None of it is required. A single line about the problem is enough to start.

Four apps live on Google Play, and a full product concept written up.

See what I have shipped