Five steps, and what each one asks of you.
The same five steps whether the work is a build, a shoot, or a review of either. Most consultancies describe their process in terms of what they do; the useful half is what it needs from you, so that is written down here too.
Engagement steps
First email
You send a paragraph: the problem, roughly when, and what is already in place. We reply within two working days, either with questions or with an honest answer that this is not our work.
One paragraph. No brief required.
Scoping call
Forty-five minutes. We want to see the constraint, not the wishlist — how things get approved, who signs off, what cannot break or slip. Most of the risk in this kind of work is organisational, not technical.
Someone who knows the work, and someone who can say yes.
Written proposal
Scope, shape, price and a finish condition, in writing, before anything starts. If the scope is uncertain we say so and price the uncertainty rather than hiding it.
Read it and push back. Ambiguity is cheaper to fix here.
Delivery
Work lands in reviewable increments inside your existing process — code through your review and release pipeline, images as work-in-progress selects. Either way you see the work itself as it happens, not a status update about it.
Review as it lands, and access to whoever knows the awkward parts.
Handover
Documentation for anything non-obvious, editable source files and full-resolution originals where the work is visual, and a walkthrough with whoever inherits it. A good engagement ends with your team able to keep going without us.
An hour, and the person who will own it next.