Questions worth answering before a call

With a thirty-minute call to understand the problem, followed by a short written scope covering deliverables, cost, timeline and the measure of success. Nothing begins until that document is agreed.

Yes — most engagements are with teams in the US, UAE and UK. Working hours cover the Gulf in full and overlap the US East Coast for a good part of the day.

Builds are usually fixed-scope projects. Anything ongoing — infrastructure, support, operations management — works better as a monthly retainer with defined response times.

Small changes are absorbed. Anything that moves the scope gets a written variation with its own cost and timeline, agreed before work continues. No surprise invoices.

You do. Repositories, credentials, documentation and hosting accounts are yours, and handover is part of every project rather than an optional extra.

Yes, before any detail about your systems is discussed.

Discovery usually within a week. Build start depends on current commitments, typically two to four weeks out.

Then I usually work alongside them on the specific systems they lack capacity or specialism for, rather than duplicating what they already do well.