Describe the job before naming a product
Start with the business outcome and the work your team needs a partner to perform. A request such as ‘need an India partner’ leaves the reader to guess the service, customer and delivery model. Write one sentence explaining who you serve, the market you plan to reach and the specific gap you want to close.
Separate essential requirements from preferences. A local support window might be essential; a particular dashboard design might be optional. This lets a supplier explain an alternative rather than simply saying yes to every line.
Give every supplier the same questions
State your current stage, expected start date, decision owner and the information you can share. If commercial figures are confidential, offer a range or request an initial capability discussion. Ask for evidence relevant to the proposed scope rather than a general company presentation.
- Which parts are delivered directly, and which involve another company?
- What must our team provide before a pilot can begin?
- What is excluded from the quotation, and how are changes priced?
- What would make this project unsuitable for your service?
Make the next step small and specific
Request a written response followed by a focused call. Compare replies in a single sheet using scope, assumptions, evidence and unresolved questions. A polished profile is a starting point for a conversation, not proof that a supplier can deliver your project. HUIDU can help you discover profiles and discuss introductions; your team should confirm the final scope and agreement with the provider.
Your working checklist
- One business outcome
- Essential requirements clearly marked
- The same questions for every supplier
- A named next step and decision owner
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.
