Skip to content

Technology consultancy · Dubai

The diagnosis first. The build only if you actually need one.

We built websites, then kept finding the website was rarely the problem. The investigation became the product.

Free, 45 minutes, no deposit. No proposal unless you ask for one.

The origin story

What kept happening, and what we changed.

  1. Then

    Shape Shifters started out building websites, and it built them properly.

    Custom code, no templates, the kind of site a business grows into rather than replaces in two years. We still do that work and it still holds up.

  2. What kept happening

    The website was rarely where it was going wrong.

    What kept happening was the same conversation. A company would come to us because enquiries were going cold, or because one person rebuilt the same report by hand every month, and they would describe it as a website problem. Then we would go and look. The website was rarely where it was going wrong. It was going wrong in the four days between an enquiry arriving and somebody answering it. In a second system holding the same customer under a slightly different name. In a CRM bought at full price and switched on at a fraction of what it could do.

  3. When the thinking is free

    We could have built the website anyway.

    That is what happens when the thinking is free: the advice gets given away to win the build, so the advice has to arrive at a build, because otherwise nobody is paid for the thinking. We were doing that, and it had started to feel like selling rather than work.

  4. What we changed

    So we changed what we sell.

    The investigation became the product — paid work in its own right, ending in a written recommendation that belongs to you and can be handed to anybody. That single change is what makes it possible for the honest answer to be change how this is done, or switch on what you already own, or yes, this genuinely has to be built.

    See how an engagement works →

  5. The clearest example

    Fixing it took no new code at all.

    The clearest example is a Dubai brokerage that came to us for a website. Phase one was not a website. It was time spent inside the CRM they were already paying full price for — no action plans, no automations, plain-text email going out of a product that ships branded templates as standard. Fixing it took no new code at all.

  6. Still engineers

    We are still engineers, and most engagements do end in code.

    For The Dubai Islands, a concierge agent and a mortgage calculator carrying real UAE lending rules, built into a property platform. For Mizanna Studio, an interior design studio, a tool that takes DWG floor plans and elevations in and returns 3D with every wall rendered. For ROI'ALL Real Estate, a system that reads an agent's existing history with a lead and drafts the next follow-up. What changed is that by the time we write any of it, we can tell you exactly why it exists.

Our principles

What we believe

  1. Advice you pay for is the only advice that can say no

    Free thinking gets recovered somewhere, and where it gets recovered is the build. Charging for the investigation is what makes it possible for the honest conclusion to be that you should not build anything.

  2. The cheapest fix that works is the right fix

    Change a process, switch on what you already pay for, then build. In that order, because the first two are usually faster and cheaper — and because they usually make the third list a great deal shorter.

  3. Nobody should have to buy the whole plan

    Work should be phased so that every phase is live, in use, and worth having on its own. A phase you decide against is a phase you never pay for, and the plan is a plan rather than a contract for all of it.

  4. You should own what you paid for

    Repository, infrastructure, data — yours from the first commit. Not licensed back to you, not held on our hosting. Being able to leave is what makes staying a decision instead of a dependency.

  5. The system should bend to the business

    Off-the-shelf software asks a company to reshape itself around the tool, and then the workaround quietly becomes the process. Real code goes around how you already work and the systems you already run.

  6. The diagnosis comes from the people doing the job

    Not from the org chart and not from a management summary. You find out where the week goes by following one real job from first enquiry to invoice and asking everyone who touches it on the way.

What it means for you

How we're different

  1. Both halves, done by the same people

    A management consultancy hands over a diagnosis and leaves before anything is implemented.

    An agency starts building before anyone has looked. We do both, so nothing is lost in the handover between whoever worked out the answer and whoever writes the code.

  2. Small, senior, and nobody in between

    The person you brief is the person inside your systems.

    No junior tier beneath us and no account manager in front of us, which is why the questions on the first call are specific and the answer comes on the call. It also means we run few engagements at a time — and if we cannot start when you need us to, we say so rather than put you in a queue.

  3. The bus-factor question, answered before you ask it

    Anyone buying a system their operations depend on daily should ask what happens if we stop answering the phone.

    So we build for that answer: you hold the repository and the infrastructure, the stack is conventional enough for any competent developer to pick up, and documentation ships as part of the work. The test we hold ourselves to is whether another team could take it over without calling us.

  4. The recommendation is not a sales document

    It is written down, ordered cheapest first, and yours to take to another firm to build.

    An engagement that ends at change this process and configure what you already own is a finished piece of paid work, not a lost sale.

  5. Custom code, so it fits what you already run

    We are not reselling a platform, so there is nothing we need you to standardise onto.

    What we build goes around the CRM, the portal feeds, the accounting and the spreadsheets that already exist, instead of asking your team to abandon tools that work.

  6. Proof at both ends of the range

    At one end, work that ends in configuration, with no new code written at all.

    At the other, a multi-tenant platform running several brands in multiple languages including RTL, with role-based access and a page builder that publishes without a deploy.

The team

Meet the team

  • Alireza Chamanrouy

    Lead Designer & Project Manager

    Turns business problems into digital systems

  • Behnam Khorsandian

    Solution Architect & AI Specialist

    Makes machines understand what humans need

  • Farzin Firoozi

    Full-Stack Developer

    Builds the engines behind every platform

  • Alireza Farasat

    Tech Lead & System Architecture

    Architects systems that scale and survive

  • Maral Emdadian

    UX / Copywriter

    Shapes the words and flows users love

Tell us the part of the week that keeps going wrong.

Free, 45 minutes, no deposit. No proposal unless you ask for one.