Question 1

How quickly do you reply?

Accepted Answer

Within two working days, and it will be me writing it. If it is genuinely urgent, say so in the first line.

Question 2

Do you take small pieces of work?

Accepted Answer

Yes — a week-long review or a second opinion on an architecture is often more useful than a long engagement, and cheaper for you.

Question 3

Do you work with teams in other timezones?

Accepted Answer

Most of my work is remote across timezones. I overlap comfortably with Europe and the Middle East, and I can make US mornings work.

Question 4

What do you need from me to start?

Accepted Answer

A description of what is breaking and what you have already tried. Access and paperwork can wait until we both know it is a fit.

Question 5

Can you take over an existing codebase?

Accepted Answer

Often that is the job. Inheriting a Laravel ERP, a half-finished platform or a service nobody wants to touch is normal work — the first fortnight goes on reading it, writing down how it actually behaves, and getting a test around the risky parts before changing anything.

Question 6

How do you charge?

Accepted Answer

A fixed price for a defined scope where the scope is genuinely knowable, and a weekly rate where it is not. I will tell you which one applies before you ask, and I would rather scope a project down than pad an estimate.

Question 7

Will you sign an NDA?

Accepted Answer

Yes, and I will work under your paperwork rather than insisting on mine. Where a project cannot be described publicly it simply does not appear on this site.

Tell me what is breaking.

Before you write