You do not need a perfect process before discussing support. You do need enough clarity to explain the problem and make decisions together. A short preparation exercise can make the first conversation more productive.
Describe the requirement
Write down the bottleneck, the activities involved and what a useful output would look like. Include a sample vacancy or task, typical volumes if known and any seasonal changes. Identify the person who can clarify the brief and the people who will approve the work.
- One representative brief or task example
- Essential requirements and known exclusions
- Decision owners and likely dependencies
Check the practical foundations
List the systems involved, the access a support team might need and the information it should not handle. Identify existing templates, approved messages and status definitions. If information or documents would cross organisational or national boundaries, raise that early so appropriate arrangements can be assessed before delivery.
Plan how to learn from the start
Agree an initial sample, a review point and the questions that will determine whether to continue. Look at usefulness and rework as well as throughput. A good discovery conversation can resolve remaining details and turn this preparation into a scoped proposal. Capacity, timing, commercial terms and service targets should then be documented together.