Consultation · Book a time

Book a consultation

Some problems need a second pair of eyes more than another pair of hands.

Pick a time on my calendar and tell me what you are trying to fix or build. On the call I tell you honestly what I see, what I would do, and whether I am the right person for it. You leave with an answer, not a sales pitch.

Pick a time Open the booking page

Consulted for DownloadLyFaramoujZarinpalCoin-plusSarrafehTajVape

Pick a time

Choose a 45-minute slot that suits you. Times are shown in your own time zone, and the calendar invite with the Google Meet link arrives as soon as you book. Add a line about the problem when you book, so the call starts with the real question.

calendar.book · Google CalendarOpen in a new tab

No slot that works? Email its@amirhp.com or message me on Telegram with two or three times that suit you.

What people book me for

The questions I get most. None of them is one setting, and all of them are cheaper to understand before anyone writes more code.

A slow or unstable site

A store that is slow, expensive or falling over, and nobody knows why. I trace it across code, database, cache, PHP and server instead of guessing at plugin settings. On one store with 30 million monthly visitors the first finding took ten minutes.

An architecture decision

Build or buy, one plugin or three, where the data should live, what happens at ten times the orders. The trade-offs named and written down before anything is built.

WordPress and WooCommerce

Custom plugins, HPOS, checkout and order flows, invoicing, payment gateways, SMS and OTP, marketplace and ERP integrations. Eleven years of building below the theme.

A plugin someone else wrote

Send me the repository and I tell you what shape it is in, what it will cost to maintain, and what to fix first, before you commit to it.

Hosting and infrastructure

cPanel, HestiaCP, LiteSpeed, Nginx, Redis, Cloudflare. What to move, in what order, and what has to stay up while it happens.

A review before launch

Security, data handling, update safety and the things that only show up after the first thousand orders.

A brief that needs to be testable

A vague idea turned into a specification someone can build against and someone else can check. I write the spec before the code.

A product you want to ship

Plugins and apps from idea to release: WordPress.org review, readme and assets, versioning, changelogs, licensing and the support that follows. I have published and maintained them since 2015.

How it goes

Short on purpose. The point is an answer you can act on, whether or not we work together afterwards.

You book a time
Pick a slot above and add a line about the problem. If there is a site, a repository or a brief, send the link; I read it before we talk.
The call
You describe the problem, I ask the questions that usually matter, and I tell you what I see and what I would do. If I am not the right person, I say so and, where I can, who is.
Written notes
After the call you get the findings and next steps in writing, so your team can act on them with or without me.
If there is work, a written scope
For a deeper investigation or a build: a document that says what will be done, what will not, how long it takes and what it costs. Fixed price for scoped work, a daily rate for open-ended work. I quote after the call, never from a form.
Investigation or build
A few days inside the code, logs, database and server, ending in a report ordered by cost; or milestones on a staging site, where nothing lands on production without your sign-off.
Handover, and I stay reachable
Documentation and everything in your repository, not mine. Maintenance afterwards is optional and separate, and I am still answering support threads for code I shipped in 2020.

To get the most from the call

None of this is required. Each item saves ten minutes of the call.

Useful to send

The site or product URL, and what "working" should look like.
What you have already tried, and what changed when you tried it.
The stack as far as you know it: hosting, plugins, custom code.
Any deadline, and who on your side will do the work.

Access, only if needed

Read-only access is usually enough for a first look.
Never send passwords in the booking form; we agree a safe way on the call.
I sign NDAs. Some of my work is under one and does not appear on this site.

Is it the right call?

Most of my week belongs to Pigment Dev, so I would rather say early if it is not a fit.

A good fit when

You have a specific technical problem and need a clear answer, not a retainer.
Your team has developers but nobody who owns the technical picture.
You are an agency that needs a senior second opinion or white-label development.

Not a fit when

You need someone to do implementation full time.
You need design or a theme customised. For that, Pigment Agency is where I would send you.
It has to ship next week, or the budget assumes a template.

Questions

Which time zone are the slots in?

Yours. The calendar converts them automatically. I am at UTC+3:30, which overlaps the whole working day in Europe and the Gulf and the first half of the North American day.

What does it cost?

If a call type is paid, the booking page says so before you confirm. Anything deeper is quoted in writing after the call, once I know what it actually is: a fixed price for scoped work, a daily rate for open-ended work.

Can we talk in Persian?

Yes. English or Persian, whichever your team works in. Written reports can be in either.

Do you sign NDAs?

Yes. Some of my past work is under one and does not appear on this site.

I need to reschedule.

Use the link in your calendar invite, or reply to it. If none of the slots work, email its@amirhp.com with a few times that suit you.

Can you take over the work after the call?

Sometimes. Pigment Dev has first claim on my week, so I take a small number of projects a year. If it fits, you get a written scope; if not, I tell you who I would send you to.