How we work, and how we price

Three ways to work with us

The shape is chosen by how clear the problem is, not by how large the invoice would be.

1. 01

   Discovery

   Usually one week

   We read your existing system if there is one, talk to the people who use it daily, and write the constraints down as they are. You leave with a scoped brief, a decision log and an estimate built on something real. Those outputs are yours to keep whether or not we build it together.

   Right when you know the problem but not yet the shape of the answer.

2. 02

   Fixed scope

   Agreed after discovery

   A written scope, an agreed price, and payments tied to deliverables you can open and try. Any change to scope is priced before it is built rather than after, and you see it in writing before we start on it.

   Right when the work is clear and bounded, and you need a number to plan against.

3. 03

   Monthly retainer

   Renewed monthly

   Reserved capacity each month on a product that keeps moving: development, maintenance, and response to whatever surfaces. The month’s priorities are agreed at the start of it, and the work is visible to you week by week rather than summarised in a monthly report.

   Right when you have a live product that changes continuously.

What determines an estimate

These are the factors that actually move the number. If you have answers to most of them, we are close to a serious estimate.

• How many surfaces

  One customer-facing screen is one thing. A customer app plus an admin console plus an operator view plus a mobile app is an entirely different piece of work — each surface carries its own design, its own states and its own tests.

• What it has to talk to

  Connecting to something that already exists — accounting, payments, stock, a government service — is usually the largest unknown in a project, because how well it is documented is not within our control.

• Whether both languages ship

  Arabic and English together is not a translation pass. It is a layout decision that touches every screen and doubles review and testing. We will tell you plainly what it costs, and sometimes we will tell you that you do not need it yet.

• Whether a system already exists

  Building new is easier to estimate than taking over something written by someone else. The second is possible and we do it, but it always starts with an assessment before we commit to any number.

• Who runs it afterwards

  If you have a team taking it over, part of the work is handover and training. If you do not, the system has to be built to run with as little intervention as possible. Either one changes the cost.

What happens after you send

Nothing automated, and no sequence of marketing emails. Your message is read by someone who works on the projects.

Within one working day

A reply from a person, not an autoresponder.

The first call

Half an hour to understand what you want, and to tell you honestly whether we are the right people. Sometimes we are not, and we say so early.

After the call

A written summary of what we understood, what we would suggest, and what we still need to know before pricing it.

The estimate

It follows the scope becoming clear, and it arrives in writing with what it includes and what it excludes.

Before any of that

We sign an NDA on request, before you send us any detail about your business.

Remote projects

Working hours, contracting and data-residency requirements are agreed per project.

• Agreed working hours

  Working hours and response windows are written into the project agreement.

• Contracting and invoicing

  The signed agreement identifies the contracting and invoicing arrangement before work begins.

• Data residency

  Data-location requirements are recorded in the project scope before infrastructure is selected.