Agree the decisions, then build the scope.

1. Show the current situation

Describe the task and the people involved. A public link or a redacted example helps us assess the starting point. Keep credentials and confidential production records out of the first message.

2. Review the dependencies

We identify source access, providers, language reviewers, data decisions and the people who approve the result. A written scope sets deliverables, commercial terms, assumptions and exclusions.

3. Inspect working examples

We arrange useful overlap with your team and written updates for decisions outside shared hours. Reviews include the ordinary task and selected exceptions. Your reviewers approve content, language and professional questions within their responsibility.

4. Hand over the change

The handover covers the agreed accounts, operating tasks, documentation and support. Production releases, external communications and paid provider commitments require their applicable explicit approval.