Six questions to ask before you choose a delivery partner

Choosing a delivery partner is one of those decisions that feels routine until it goes wrong. A weak partner does not usually fail loudly. It fails through small things: a status report that arrives late, a question answered slowly, a ServiceNow configuration that meets the letter of the requirement but not its purpose. By the time the pattern is visible, the customer has noticed too.

These six questions will not guarantee a good outcome, but they will surface most problems early, while they are still cheap to deal with.

1. Who owns what, in writing? Ask how the partner documents roles and responsibilities. A good answer describes a short document naming the owner of each workstream, such as the service portal, the CMDB or an integration, which both sides review before starting. A weak answer is a general reassurance that “we will figure it out as we go.”

2. How do you report bad news? Every partner will tell you how they report progress. Ask instead how they report problems, and ask for an example of a time they flagged an issue that was their own fault. Partners who can describe that honestly tend to raise issues early.

3. Will you follow our standards? Your templates, tools and review steps exist for reasons, some of which are not obvious to an outsider. A good partner asks to see your best work and matches it. The difference shows up in the first deliverable.

4. Who is our single point of contact? Managing several individuals on the partner’s side, each with a different understanding of the priorities, defeats the purpose of using a partner. Look for a named lead who attends your meetings and can speak for their team.

5. What happens when we disagree? Disagreements are inevitable. Ask about escalation paths and time limits. A partner who has thought about this before the first disagreement is far more likely to handle it well.

6. What are your limits? Every partner has them. Ask which kinds of projects they would decline, which skills they would need to bring in and how much notice they need to add capacity. If your project includes AI, ask specifically how they would decide what a human must review. Honest answers here are a sign of a partner who plans rather than promises.

Using the questions

You do not need to ask all six in one meeting. Spread them across early conversations and pay attention to how the answers feel. Precise, specific answers, with examples, are usually a good sign.

The best partnerships we have seen began with a candid conversation about how things could go wrong. That conversation is uncomfortable for about ten minutes and saves months of frustration afterwards.