Map the parties involved
Before discussing a large project, establish the legal entity that will sign the agreement, the team that will perform the work and the party that will receive payment. Ask the contact to explain any difference between a trading name, website brand and contracting entity. Keep the answer in your project record rather than relying on a chat display name.
An introduction is useful because it starts a conversation. It does not replace your own checks. Confirm important details through an agreed business channel and obtain documents directly from the party responsible for the engagement.
Check evidence against the proposed scope
Ask for examples of work similar to your requirements, with permission to discuss the relevant details. Distinguish a public logo from an active customer relationship, and a published capability from a service available to your project today. If a reference cannot be shared, ask what alternative evidence the supplier can provide.
- Contracting entity and delivery contact
- Written service scope and subcontracting arrangements
- Commercial terms, acceptance milestones and change process
- Security responsibilities and handling of shared information
Start with a bounded working relationship
Choose a pilot that produces a reviewable output and has a clear stop point. Set a schedule for updates and a process for raising unresolved issues. Avoid placing passwords, identity documents or other sensitive material into an open sourcing discussion. Use your company's approved process for confidential checks and agreements. If a material question remains unanswered, keep it visible in the decision sheet instead of treating silence as approval.
Your working checklist
- Identify the actual contracting party
- Match evidence to your project
- Use a bounded pilot
- Keep unresolved questions visible
Editorial note
Use the original publications for their current scope. These guides offer an editorial framework; they do not certify a supplier or replace business-specific checks.
