Skip to main content
Tretanz Infotech

Agency Partnership

20 questions for a white label discovery call

This is a call script, not a diligence manual. Twenty questions to run a first white label discovery conversation: delivery and branding, process and QA, commercial terms, legal and overlap. Use it live. Save the scorecard and references for after.

Agency team discussing white label discovery call questions

A discovery call is not an audit. You are not scoring a vendor to three decimal places. You are deciding whether a second conversation is worth anyone’s calendar. Bring twenty questions, a clock, and permission to end early.

This is a script for the first live conversation with a possible white label development partner for agencies. It is not a rewrite of how to vet a white label partner. Vetting is homework: references, a scorecard, a pilot, legal review. Discovery is spoken. If you try to run the full diligence checklist on a Zoom, you will get a capabilities deck and no signal.

Use these questions in order unless the partner’s answer already closed a topic. Listen for process, not adjectives. “We are agile and passionate” is not an answer. “We confirm scope in writing before a repo is opened” is an answer.

If you still need the model defined, read white label development explained before you book the call. If you already know you want branded delivery, run this script, then decide whether to start diligence.

Discovery is a conversation with a job

The job is fit, not flattery. You leave the call with a yes/no on whether they have done invisible delivery for agencies like yours, whether their operating rhythm matches yours, and whether commercial terms are even in the same universe. You do not leave with a signed MSA. You do not leave having “vetted QA.” You leave knowing whether to invest in vetting.

Discovery call vs diligence

Discovery call (this script)Diligence (different article)
GoalDecide if a second cycle is worth itDecide if they can touch a client
Time45–60 minutesDays to weeks
EvidenceHow they answer live; who is in the roomArtifacts, references, pilot, paper
Failure modeYou pitch each otherYou skip it because the call “felt good”

The partner you can reach when a launch date moves is worth more than the partner with the lowest rate card.

— Agency partnership principle

Who should be on the call and how long it runs

Your side: someone who owns client delivery (founder, CD, or delivery lead) and, if they exist, the person who will write briefs. Do not send only a salesperson. Their side: someone who owns delivery, not only a closer. If they cannot put a delivery lead on a first call, assume you will never meet delivery until something is on fire.

  1. 01

    0–5 minutes: context, not a pitch

    You state your typical project types, stacks, and whether the partner must stay invisible. They do not present 20 slides.

  2. 02

    5–35 minutes: the twenty questions

    Work the list. Skip a question only if they already answered it in a complete sentence.

  3. 03

    35–42 minutes: commercial sketch

    Model (fixed, retainer, pod), minimums, how they quote. No haggling. You are mapping, not procuring.

  4. 04

    42–45 minutes: next step or a polite stop

    If you continue: NDA, a sample brief, or a follow-up with a PM. If you stop: say so. Do not invent a “we’ll circle back” to be kind.

Open with your constraints, then ask the twenty

Do not start with “tell us about yourselves.” Start with three facts: your common project types, your white-label rule (invisible vs named), and whether you need overlap hours for launches. Then run the questions. Partners who ignore your constraints and restart their deck are showing you the relationship.

The 20 discovery questions (use live)

  1. Which agencies have you delivered for as an invisible partner in the last 12 months—and what did you actually build?
  2. If a client asks “who is building this,” what do you do unless we have authorized you to speak?
  3. Walk me through a kickoff: what do you need from us before a developer opens a repo?
  4. Where does work live during the build—our org, yours—and who owns staging credentials?
  5. How do you confirm scope in writing, and what happens if the brief is incomplete?
  6. What does your QA look like before we see staging? Name artifacts, not adjectives.
  7. How many revision rounds are in a typical marketing-site SOW, and what counts as a round?
  8. How do you price work that is clearly not in the brief—same week, not after launch?
  9. Who is the single point of contact for our agency, and what is their backup when they are out?
  10. What hours of real-time overlap can you guarantee for our account team, and what is async-by-default?
  11. How do you send status when we cannot put you on client Slack—written, Loom, ticket, all three?
  12. What project types or stacks do you decline, even if we ask nicely?
  13. How do you handle a date slip or a blocker—same day, and to whom?
  14. What does post-launch support look like in the first two weeks, and what is billed as new work?
  15. Are you signing a mutual NDA before we share client names, and will custom work be assigned to our agency on payment?
  16. Do you use subcontractors who are not on your payroll, and will you disclose them?
  17. Which commercial model do you prefer for a first project versus a third—fixed, T&M cap, retainer, pod?
  18. What is the smallest engagement you will run as a real process (not a “quick favor”), and what is your current start date?
  19. Can you share an agency reference we can call—not an end-client testimonial?
  20. If we ran a bounded pilot, what would you want in the retro that most agencies forget to measure?

Read them as a script, not a survey

Follow-ups that matter: “show me,” “who does that,” “what happens when that fails.” If they answer question 1 with logos and no project types, do not let questions 2–20 become a brochure. Take notes against the numbers, not against a vibe. After the call you should be able to quote their definition of a revision round and their overlap window without rewatching the recording.

Questions 1–6: branding, kickoff, and proof they have done this

White label is a behavior. Question 1 asks for recent agency-side work, not a career retrospective. Question 2 tests whether they understand they are not the brand. If they say “we like to get close to the end user,” they are telling you they will wander into your client relationship.

Questions 3–5 map to how white label development works. You want a brief, a written scope confirm, and environments you control. If kickoff is “send Figma and we’ll figure it out,” your account team will become unpaid PMs. Question 6 is where QA either exists or is a slogan. Ask for a checklist or a staging habit. “We test everything” is not a checklist.

Questions 7–14: revisions, communication, and honesty about fit

Revision and change-order answers predict margin. If they cannot define a round, you will live in Slack. Pair this with how you intend to run revision rounds. If your client packages say “unlimited” and their SOW says “two rounds,” someone is lying to someone. Better to find that on the call.

Questions 9–11 are operations. A named owner with a backup is a company. A rotating “the team” is a Discord. Overlap hours should be a number, not “we are flexible.” Async status should be a cadence you could show an account manager on day one.

Question 12—what they decline—is a quality signal. Partners who take everything will learn on your client’s dime. Question 13 is escalation. You want a path that does not require you to shout. Question 14 is whether launch is an exit. If support is “open a new quote,” price that into the first SOW or walk.

Pros

  • + They name stacks they will not take
  • + They describe consolidated feedback, not infinite Slack pixels
  • + They already have a written status format for agencies that keep them off client channels
  • + They talk about first-week bugs as a planned window

Cons

  • − “Unlimited tweaks, we want you happy”
  • − “Just add us to Slack, it’s easier” as the only communication design
  • − No backup to the one star developer
  • − They have never declined a project type you sell every week

Questions 15–20: paper, model, capacity, and the retro

Question 15 is a filter, not a contract negotiation. You are listening for willingness to NDA and to assign custom work on payment. The actual clauses live in MSA, NDA, and IP for agencies. If they bristle at the topic, diligence is already over.

Question 16 (subcontractors) should get a policy, not a speech. Question 17 should match pricing models: a first project is usually a fixed SOW; a retainer is something you earn. If they push a 12-month pod on call one, they are filling a bench, not fitting your pipeline.

Question 18 is calendar truth. A partner who can start Monday on a complex build is either empty or lying. Question 19 is the agency reference. End-client quotes hide handoff pain. Question 20 tests whether they think like operators. A good retro measures on-time, first-staging quality, revision count, and AM hours—not “how did we feel.”

How to score the call without turning it into diligence

Immediately after hanging up, mark each question yes, partial, or no. You are not filling the 20-point vetting checklist. You are deciding: schedule diligence, request a written follow-up, or stop. Three or more hard nos on branding, QA, IP, or references is a stop.

Call outcome rubric

Pattern on the callNext stepDo not do
Clear process, delivery lead present, honest declinesNDA + sample brief + scorecardSkip the pilot because you liked them
Strong talk, no delivery person, vague QAOne written follow-up; if still vague, stopIntroduce them to a client “to see”
Price-first, no questions about your briefsStopAsk for a discount to “trial” chaos
Good fit but no capacity for 8 weeksPark with a date; do not force a crash startPut them on your most political launch

When you do move to diligence, use the vetting article and the brief template. Do not paste this script into an RFP and call it homework. Spoken answers and written artifacts are different evidence.

What you should send before and after

Before the call

  • Three bullets: project types, stacks, invisible-or-not
  • Whether you need overlap for US or UK account hours
  • Who on your side will attend (names, roles)

After a “continue” call

  • Mutual NDA if client names are next
  • A sanitized sample brief from a real recent job
  • Your revision and QA expectations in one page
  • A request for an agency reference and a start-date window

Do not send a 40-page RFP after a good conversation unless you are a procurement department. You will get a 40-page fiction. Send a real brief. How they estimate it is the second discovery call, and it should be written.

Questions not to waste the hour on

Hourly rate in minute five, “are you cheaper than our last freelancer,” culture-fit small talk, and a tour of every internal tool. Rate without scope is theater. Culture is not a substitute for a named backup. Tools are negotiable; process is not.

Also skip a live coding quiz. This is not a staff-aug interview. You are buying a delivery system. If you need engineers in your standups every morning, you may want a different model—see when white label is the wrong fit—not a harsher discovery call.

Use the script, then go to process or walk away

If the twenty answers hang together, look at how we run delivery and whether that rhythm matches what you heard. If you want to see finished work in the same genre as yours, use work samples as a conversation starter—not as a substitute for an agency reference.

Ready to run this script with Tretanz? Book a partnership discovery call and send the three bullets in advance. We would rather answer the twenty questions than perform a capabilities hour that teaches you nothing.

FAQ

Frequently asked questions

Straight answers for agency owners evaluating white label development partnerships.

Continue

Related pages

Services, solutions, and next steps connected to this topic.

Continue reading

More from the blog