The questions people
actually ask.

No, and the difference is not a word game. An agency sells your project onward and manages the people who do it. We do the work. There is nobody here whose job is to stand between you and the code.

Large enough to cover several projects at once and to have real specialists in security and infrastructure. Small enough that the person answering you knows your system. If a project needs more than we can honestly staff, we say so rather than stretch.

It would if we ran on meetings, and we do not. Decisions and updates go in writing, so nothing waits for the right person to wake up. Across the four countries somebody is working in your hours, and you get one named engineer rather than whoever happens to be online. We invoice in your local currency and sign whatever agreement your legal team needs.

Some of it. Most of what we build belongs to somebody else and stays private unless they give written permission. We can walk you through anything relevant on a call, including the parts that went wrong.

A segmentation fault is what happens when a program touches memory it has no right to touch. It is the most honest error a computer produces: something is wrong, here, exactly. That is the kind of clarity we are after.

Sometimes. Write to us through the contact page with something you built and what you would change about it now. That tells us far more than a CV.

Because quoting a rebuild or a new build without seeing the system is a guess, and a guess always becomes an extra invoice later. The free audit turns the "from" into an exact number, and that number is then fixed.

We quote the change and you decide before we build it. You will never receive an invoice containing something you have not already agreed to. If the growth came from our own underestimate, it is our cost.

Yes. Usually a deposit to start and the rest on delivery, or monthly for longer projects. Retainers are billed monthly in advance. We will fit reasonable terms, and we will say so plainly if we cannot.

Prices are shown for your region and in its currency: US dollars, euros, pounds, dirhams, or riyals. Change the region at the bottom of any page. We invoice in that same currency. Any tax that applies depends on where your business is registered and appears on the invoice, never as a surprise afterwards.

Not for asking. Taking more than one service together genuinely costs us less to deliver, so that is reflected in the quote. A discount for pressure would only mean the first number was not honest.

We would prefer it. A landing page or an audit is a cheap way for both of us to find out whether working together is a good idea, before anyone commits to something large.

Because a large part of an agency invoice pays for people who never open the code. We removed that layer, not the engineering. Compare what is actually delivered rather than the number on its own, and ask any quote you receive who exactly will write it.

The engineers on your project. You get their names at the start and they stay with you until the end. If someone has to be replaced, we tell you why before it happens.

No. The work is done by our own team. Nothing is quietly passed to a cheaper studio you never meet, which is the most common reason an agency project drifts in quality.

Then we work with them. We follow your conventions if you have them and write ours down if you do not. We are not trying to become the only people who understand your system.

One at the start, one at handover, and any others you actually want. Everything else is written down, which is faster to read than a call is to attend and easier to find again in six months.

Say so early. We would rather stop, hand over everything cleanly and part on good terms than deliver something neither of us is proud of. That has never cost us a reputation. Pretending would.

No. You get the repository and you can put it anywhere, including a free host. Our hosting exists because most people would rather not think about deploys, certificates and backups. It is an offer, not a condition.

The Complete package includes writing the copy with you. For images we will tell you honestly what is worth paying a photographer for and what can wait. We do not fill a page with stock photos of people pointing at laptops.

Small text changes, yes, and we show you where. If you want to change everything without touching code, say so before we start and we will build it that way. Retrofitting it afterwards costs more than planning it.

Small edits are covered by a support plan if you have one. Larger changes are quoted, and you always see the number before we start. We do not bill by surprise.

We give you the measured number for your page on a mid-range phone on 4G, before and after. That is a real figure from a real test, not a score from a tool run on our own fast laptop.

Because there is no account manager, no strategy deck and no reselling. The people who build it are the people you talk to.

We do. There is no account manager between you and the engineers, and nothing is passed to a cheaper team you never meet. You talk to the person who wrote the function you are asking about.

Good. That is why the handover includes a runbook and a working local setup, and why we choose ordinary tools instead of clever ones. A new developer should be productive in a day, not a month.

Yes, send yours before the first call if you prefer. We do not name clients or show work without written permission, and that stays true after the project ends.

If we underestimated our own work, that is our cost, not yours. If you change what you want, we quote the change and you decide. The line between those two is written down at the start so it is never an argument later.

Yes. We review together, follow your conventions if you have them, and write ours down if you do not. We are not trying to be the only people who understand your system.

Morocco, working across European and North American hours. Everything is written down, so a time difference is a scheduling detail rather than a delay.

That is the most common fear and it is a fair one. Rankings are lost when old addresses stop working. Every page that exists today gets redirected to its new home, the content stays, and the site gets faster, which search engines reward. We check the results for weeks afterwards rather than declaring victory at launch.

Yes. We can rebuild what is there, or move you off it entirely if the plugins have become the problem. The audit tells us which one saves you more, and we explain the trade-off in plain language before you decide.

Yes, and usually more easily. Tell us before we start which parts you need to change yourself. Building that in from the beginning is cheap. Adding it afterwards is not.

It should not go down at all. The new site is finished and tested on a separate address first, and the switch is a change of destination that takes minutes. Where downtime is genuinely unavoidable we tell you in advance and schedule it.

That is normal, and it is not a problem you have to solve before calling us. Working out how an undocumented system behaves is part of the job. We write down what we find as we go, and you keep that document.

Sometimes, and we will say so. If the existing site has little content and no ranking worth protecting, a fresh build can be faster and cost less. We would rather tell you that than sell you the more expensive option.

It should not, and we plan it so it does not. Load-heavy checks are agreed in advance and usually run outside your busy hours. We keep a contact on call during testing so anything unexpected is stopped in minutes, not hours.

Not necessarily. Testing without it is closer to what a real attacker sees. Testing with it finds more, faster, for the same money. We will tell you which one fits your situation and why.

Then the report says so, and that is a real result you can show a client or an investor. We do not inflate low findings to justify an invoice. Our reputation is worth more than one project.

You. We do not name clients or publish findings without written permission, and we hold nothing on our side longer than the engagement needs. If you want us to sign your NDA first, send it.

Yes, quoted separately, and you are never obliged. Some clients hand the report to their own team, and that is a good outcome too. We would rather the hole gets closed than that we get the work.

You get a letter of attestation stating the scope, the dates and the state of the findings after retest. That is what a serious client or auditor asks for. Anyone selling you a badge without a scope is selling you a picture.

For Critical plans it means a named engineer is on call at any hour, every day. For Landing and Business it means our monitoring runs around the clock and pages us, and we answer during working hours. We would rather tell you the limit than promise a number we cannot hold.

On infrastructure we rent and manage ourselves, not resold from a platform. That is why we can change kernel settings, tune the database, and give you the whole machine's behaviour instead of a support ticket.

You get the code, the database dump, the configuration and the deploy scripts, in a form another team can run. Thirty days notice, no exit fee, no held hostage data. We would rather you leave cleanly than stay unhappy.

Yes, after a free audit. The audit tells us what we are taking on. If we find something we cannot support responsibly, we say so before you pay anything.

New features, redesigns and large refactors are project work, quoted separately. Hosting covers keeping what exists running well. Small content edits are included in the hours listed on each plan.

Short spikes are absorbed. If your normal traffic grows past the plan, we tell you before the invoice changes and we show you the numbers behind it.

Yes, after a free audit. We need to know what we are taking responsibility for. If we find something we cannot support honestly, we tell you before you pay anything rather than discovering it during an outage.

They roll over for three months. We are not trying to profit from a quiet quarter, and you should not feel pushed to invent work in the last week of the month.

If something used to work and stopped, it is a fix and it is free. If it never worked that way and you want it to, it is a change and it comes out of your hours. Borderline cases go in your favour, and we would rather lose the argument than have you hesitate before writing.

Yes. Most of what matters is access, not ownership of the server. If your current host makes support genuinely difficult we will explain exactly why and let you decide.

Your engineer directly, by email or chat, whichever you prefer. Not a shared inbox, not a form. Out of hours on Priority and above there is a number that reaches a person.

Thirty days notice and we hand over everything: code, data, configuration and the notes we kept while working on it. No exit fee. A retainer should be something you keep because it is worth it.