More partner
less vendor

Who you get

We're a small team of senior engineers in Morocco, started by Issam Zoli, a software engineer who spent years consulting in big companies before building this one around his core ideas.

Most of our clients reach out at a tipping point: their SaaS stack has become a patchwork, workarounds are slowing growth, and too much of the business depends on people keeping everything together.

We design workflows from scratch, fix and optimize existing ones, and use AI to reduce the amount of human effort they rely on. The result: less friction, less manual work, and a business that runs better.

Senior engineering, minus the bloat

We've worked inside the traditional agency model. The people there are mostly good. The structure is the problem: a project moves from whoever sold it to whoever builds it, and by then half the reasoning behind the scope has gone missing.

So we took the middle tier out. There's no account executive, and no junior subcontractor doing the build at a markup. The engineer who scopes your project is the one who writes it, and the one who gets the alert when a third-party API changes shape without telling anybody.

That has a cost, and it's ours to say out loud: we can only run a handful of builds at a time. If we're full, you'll hear it on the first call, rather than after three weeks of being moved along a pipeline.

Why Morocco 🇲🇦

Morocco puts our working day almost entirely on top of London's, with half an afternoon still left when New York comes online. You're not waiting overnight for an answer to a question you asked at 9am.

The rate difference is structural. Our costs aren't tied to San Francisco rent or London rent, so our prices aren't either.

Nobody's subsidizing you, and there's no junior quietly doing the build to make the number add up. That's the whole explanation. We'd rather say it plainly than leave you wondering where the catch is.

How we work

Three commitments, and they're the same question answered three ways: when this goes wrong, who pays for it? An arrangement where the honest answer is "you" will go wrong eventually, and you'll be the last to hear about it.

• Tight, objective scopes. We write down what the job includes and what it doesn't. The second list is the one that saves you money.
• Fixed pricing. You know the cost before we write a line of code. If we estimate badly, that's ours to absorb.
• All of it is engineering. Your money buys build hours. You're not funding a pitch deck, or an office in a city you'll never visit.

Partners, not vendors

A vendor's job ends at handover. Integrations don't sit still, though: an API changes, your volume doubles, and six months on, many business rules have changed.

So the work afterward goes past error monitoring and updates. We come back with the next thing worth building, because the system tells us where your time is going, and because we've worked in many industries. The failures rhyme. When we tell you what's likely to break next, it's because we've watched it break. When we tell you something's worth building, it's because we've watched it work.

Whether you want any of that is up to you. Support is a separate decision from the build, there's no minimum term, and a quiet month is a fine reason to cancel it. We'd rather be here in year three because you keep asking us back, not because leaving costs you something.

If you'd rather see the work before you speak to anyone, that's what the case studies are for. The constraints we hit are in there, and so are the numbers.