Amirhossein Hosseinpouramirhp
CV
Service · Short engagements

Technical consulting

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

For teams that have developers but nobody who owns the technical picture. A few days of investigation, a written report you can act on without me, and a conversation to walk through it.

Tell me what you are trying to fix How it goes
Done for DownloadLyFaramoujZarinpalCoin-plusSarrafehTajVape

What it usually looks like

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

A store that is slow, and nobody knows why

I trace it across code, database, cache, PHP and server instead of guessing at plugin settings.

An architecture decision with consequences

Build or buy, one plugin or three, where the data should live. Written down with the trade-offs named.

A plugin someone else wrote

Send me the repository and I will tell you what shape it is in before you commit to maintaining it.

A hosting or infrastructure move

What to move, in what order, and what has to stay up while it happens.

A code review before launch

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

A roadmap that needs to be testable

A vague brief turned into a specification someone can build against and someone else can check.

What you get

Short on purpose. The point is an answer you can act on, not a retainer.

  1. Investigation

    A few days inside the code, the logs, the database and the server, with whatever access you can give. I work from evidence, and I say what I could not see.

  2. A written report

    Every finding, in order of cost, with what to change, what not to touch, and why. Written so your team can act on it without me.

  3. A walkthrough

    One call to go through it with whoever will do the work, and to answer the questions the report raises.

An example

A download store was returning 503s most of every business day. The first finding took ten minutes: OPcache was not loaded at all, so every request compiled WordPress from source. Account CPU went from a pinned 100/100 to about 15/100 within minutes. The client received a full written report in Persian documenting every change. Read the full case.

A good fit when

You have a specific technical problem and need a clear answer, not a retainer.

Not a fit when

You need someone to do the implementation full time.

The final price did not change, even though the project turned out larger than we had estimated.
Eng. RahmatizadehManager, DownloadLy. About the Pepro Dev team. Translated from Persian.
branch main 6 active projects ↑ 113 releases services/technical-consulting.md Sari --:-- UTC+3:30 its@amirhp.com