If yours isn't here, say so anyway. I would rather point you to someone else than take on work I'm not the best person for.
Deadlines are moving, the budget is spent, and nobody wants to announce the real date any more. I come in, look at the code, the estimates and the team, and give you an honest picture within two weeks: what is recoverable, what isn't, and costed options for what comes next. Then I run the recovery if you want me to.
Hiring, structure, onboarding, rituals, technical growth. I know the Moroccan talent pool well and I know what makes good people stay, which is the part that actually matters: a team you have to rebuild every eight months never produces anything. 95% retention on my last team, in a market where everyone gets approached.
You have an idea, a rough budget and no way of knowing whether the two are compatible. Wireframes, scope, technical trade-offs explained in business terms, costing. You walk away with a pack a development team can execute and a steering committee can approve.
Plenty of organisations don't need a full-time delivery director but suffer badly from having none at all. Two or three days a week: governance, trade-offs, client relationship, releases, and growing your own people into the role. The goal is for you to be able to do without me.
Plenty of people can run a steering committee. Far fewer can open the repository afterwards and check whether what was said in it holds up. That difference is what you're buying.
PHP, MySQL, integration, UI/UX. International clients, including a Microsoft partner and the Mohammed VI Foundation. That was also where I learned what a badly scoped quote costs, by paying for it myself.
Lead developer for international teams. Adobe Experience Manager platforms, PHP, JavaScript, REST APIs. 40% less load time across the scope I was responsible for.
Engineering team hired from zero and grown to ten. Micro-frontends, daily code review, multi-region CI/CD pipelines. 35% less deployment lead time.
An international digital portfolio end to end: commercial scoping, estimating, build, release, run. A team of more than twenty, budgets and margin, AI R&D.
years delivering enterprise digital work
multi-component platforms delivered on schedule
people managed across dev · design · QA
continents served from Casablanca
The context, the decision, what it cost and what I took from it. Including the two I got wrong. You'll know how I think before you get me on a call.
Nothing is committed until the scope is written down. That protects you as much as it protects me.
Thirty to forty-five minutes. You talk, I ask questions. At the end I tell you honestly whether I'm the right person. Free, and with no obligation to go further.
A few days looking at the code, the estimates, the team and the context. You get a document that belongs to you, readable by your leadership, with costed options.
Format, duration, rhythm, price, and above all how we'll know the engagement worked. If neither of us can describe that outcome in one sentence, the engagement isn't ready.
Weekly check-in, progress shown working rather than described, bad news delivered early. And an exit plan from the first month, so your team takes the wheel.
These aren't three options to pick between at random. They follow on from each other. We start small, you judge on evidence, and then you decide whether to go further.
If you recognise yourself in one of them, the conversation will be a short one.
Stakeholders up to executive committee level, several teams, several countries. This is my home ground: thirteen years serving member firms across Europe, the United States and Asia Pacific.
The product works, the team has doubled, and nothing ships on time any more. You need rituals, a definition of done, deployment pipelines and somebody to arbitrate.
You've won a project bigger than usual and you're missing the person who can hold the client, the scope and the margin at the same time. I've done that job from both sides of the table.
Hiring here without knowing the market is expensive and takes six months longer than planned. I know where the good people are, what they're worth and what makes them stay.
You won't find an invented glowing testimonial on this site. These four people worked with me and agreed to be contacted. I hand over their names and details before signature, not before the first call. Here is what each of them is best placed to tell you.
Ask about: holding commitments under pressure, architecture trade-offs, and what I do when a date becomes untenable.
Ask about: working with design teams and governing a design system over the long run.
Ask about: hiring in Morocco, structuring a team, and the reasons people stay.
Ask about: the day-to-day client relationship, how bad news gets delivered, and the quality of the run.
Answered in advance, including the questions that suit me less well.
One hour from Paris, and a good share of the working day overlapping with North America. I spent fifteen years delivering for Europe, the United States and Asia Pacific from here, so that question was settled a long time ago.
Remotely, I'll work with you wherever you are, as long as we understand each other in French or English. That's my default, and it's how I ran programmes for Europe, the United States and Asia Pacific for fifteen years: calls scheduled at hours that suit everyone, progress shown working rather than described, written updates that stand on their own, and decisions that don't wait for everybody to be online at once.
If the engagement needs me physically in the room, the only two cities where I can do that are Casablanca and Rabat. Better said now than in month three: promising regular travel anywhere else would be a commitment I wouldn't keep, and a broken commitment costs more than an honest no.
So: anywhere in the world remotely, on site in Casablanca and Rabat. If your need is elsewhere and genuinely requires someone in your offices every week, I'm not the right person and I'll tell you that on the first call.
I give you a number on the first exchange, as long as I know the scope: duration, rhythm, size of the team involved, who I'll be dealing with. Stretching it over three meetings only to discover at the end that we're not in the same range serves nobody.
An audit is sold as a fixed fee, an engagement on time spent. There's no secret rate card: the price follows scope and length of commitment, and it's written down before we start.
Both, and in that historical order: seven years writing production code before I ran anything, four of them as a senior lead developer and four as tech lead and architect. The detail is further up.
These days I code when it's useful, and I enjoy it. If something needs exploring, an integration needs unblocking or a release is at risk, I open the editor. Day to day I mostly read: pull requests, architecture choices, estimates. That's where I save you money.
What I don't sell is development by the ticket. If you're looking for a full-time pair of hands on code, I'm the wrong choice, and I'll tell you that on the first call.
Two at most, and never two recovery engagements in parallel. A rescue needs mental availability, not just hours in a calendar. You'll know exactly what else I'm carrying during your engagement, and I turn work down when the maths doesn't work.
The exit plan gets written in the first month, not the last. Process documentation, a named handover, and a period where your team runs things while I only watch. An engagement that leaves you dependent on me is a failed engagement, however profitable it is.
No, and I'd rather be straight about it. I spent thirteen years with the same employer, in consulting, running an international digital portfolio, after two years working for myself early on. What you're buying is that experience applied to your situation, not ten years of day-rate invoicing.
The full career is here, with contactable references.
That's part of what the first month is for. If either of us decides this isn't the right fit, we stop, you pay for what has been done and you keep the deliverables. I would rather have a short clean engagement than a long one nobody stands behind.
Describe the situation in a few lines. I reply within twenty-four hours, and I'll tell you frankly whether I'm the right person.
© Abdeljalil Hcham 2026. Written by hand, numbers verifiable.