What you ask before handing over the work

Yes. Every project starts with a written contract naming the scope, the price, the delivery date and the payment terms. Nothing begins on a verbal agreement — not to protect me, but so you know exactly what you are buying.

Payment is staged, not paid up front. The work is divided into stages and each payment follows the delivery of its stage. In the worst case, you have only ever paid for what you already received.

Revisions happen on the design, before anything is built, because that is where change is cheap. If we cannot get there at the design stage, the work stops and the unpaid stages are simply not paid.

It depends on the scope, and any number given before hearing the problem is meaningless. Each service page carries an indicative range so you know the neighbourhood; the exact figure is fixed and comes after the first conversation.

Each service page carries its own range, and the exact delivery date goes into the contract. Delivering on time is one of this brand's five stated values — if I name a date, I keep it.

Payment is staged, and the method depends on whether you are inside Iran or elsewhere. The first conversation settles which route is simplest for you.

You do. The code, the domain, the hosting and every credential are registered in your name and handed over at the end. If you ever want to continue with someone else, nothing stays hostage with me.

Yes — 30 days after handover, at no cost, for anything that came from my work. After that you are welcome back for new changes, but there is no compulsory monthly retainer.

Yes. The work is fully remote and the client can be anywhere. We can talk in Persian or English, whichever suits you.

You talk to the person doing the work, not to an account manager. That means faster answers and nothing lost in the handoff between people. In exchange, it means I take a limited number of projects at a time.

Looking at what you actually do every day and finding where a tool can free up time or cost — and, just as important, saying where it cannot. The output is a plan you can act on, not a list of fashionable tools.

I use these tools where they make the work faster and more precise, but the design, the decisions and the final review are mine — and so is the responsibility for them. What you receive is code that has been read and tested.