The 12-Point Checklist
1. Communication Speed and Quality
What to evaluate: How quickly do they respond to messages? Are responses clear, proactive, and actionable? Do they ask clarifying questions or make assumptions?
How to test: During the evaluation phase, send a detailed technical question by email. Measure response time and quality. A partner who takes 48 hours to respond during the sales phase will take longer once you are a signed client.
Green flag: Responses within 4 hours during overlap time. Proactive updates without being asked. Clear written English.
Red flag: Responses take 24+ hours. Answers are vague or require follow-up to understand. No questions asked about ambiguous requirements.
Weight: Critical — This is the #1 predictor of success.
2. NDA and IP Protection
What to evaluate: Will they sign your NDA? Do they have a standard IP assignment clause? Is your client's code and data protected?
How to test: Send your NDA before the first technical conversation. A serious partner signs it within 24–48 hours without extensive negotiation.
Green flag: Signs NDA before first call. Clear IP assignment language. Data handling policies documented.
Red flag: Hesitates on NDA. Wants to use their own contract only. No clear IP assignment process.
Weight: Critical — Non-negotiable for white-label work.
3. Timezone Overlap
What to evaluate: How many hours per day do your teams overlap? Can you have real-time conversations when needed?
How to test: Ask what their working hours are. Calculate overlap with your team and your clients.
Green flag: 4+ hours overlap. Flexible on adjusting hours for important meetings. Async communication is strong.
Red flag: Less than 2 hours overlap. Insist on working their hours only. No accommodation for urgent issues.
Weight: High — You need real-time collaboration for client-facing work.
4. Trial Period Availability
What to evaluate: Do they offer a paid trial period? What does the trial include? Is there a money-back or replacement guarantee?
How to test: Ask directly. A confident partner offers trials because they know they will perform well.
Green flag: 2-week paid trial standard. Defined deliverables for the trial. Free replacement if trial does not go well.
Red flag: No trial available. Requires 3+ month commitment upfront. No replacement guarantee.
Weight: High — Never commit long-term without testing.
5. Code Quality Standards
What to evaluate: Do they write tests? Follow consistent coding standards? Use code reviews? Document their code?
How to test: Request a code sample from a recent project (with client details removed). Review for: consistent naming, proper error handling, test coverage, documentation, clean architecture.
Green flag: 70%+ test coverage. Consistent code style (ESLint/Prettier configured). Pull request reviews standard. Clean separation of concerns.
Red flag: No tests. Inconsistent formatting. No review process. Monolithic functions with no documentation.
Weight: High — Bad code costs you in maintenance and client satisfaction.
6. Team Stability
What to evaluate: Will the same developers work on your projects long-term? What is their developer retention rate? What happens if someone leaves?
How to test: Ask about their team tenure. Request specific developers for your trial and confirm they will remain assigned.
Green flag: Average developer tenure 2+ years. Named developers assigned to your account. Replacement policy documented (e.g., free replacement within 2 weeks).
Red flag: High turnover ("we will assign whoever is available"). Cannot guarantee specific developers. No replacement process.
Weight: High — Developer turnover destroys productivity and client confidence.
7. Process Transparency
What to evaluate: Can you see their work in progress? Do they use sprint methodology? Are estimates transparent?
How to test: Ask to see their project management setup. How do they track time, progress, and blockers?
Green flag: You get full access to project boards. Daily standups or async updates. Sprint planning with clear velocity tracking. Time tracking visible.
Red flag: "Trust us, we will deliver by the deadline." No visibility into daily progress. Estimates given without breakdown.
Weight: Medium-High — You cannot manage what you cannot see.
8. Technical Breadth
What to evaluate: Does their team cover the tech stacks your clients need? Can they handle frontend, backend, mobile, and DevOps?
How to test: Map your last 5 client projects to their team's skills. Identify gaps.
Green flag: Strong in 2–3 core stacks that match your demand. Senior developers (5+ years) in primary technologies. Can recommend architecture approaches.
Red flag: Claims expertise in everything. Junior-heavy team. Cannot explain technical tradeoffs clearly.
Weight: Medium — Technical fit matters, but a strong team in one stack is better than a weak team claiming to do everything.
9. Client References (Agency-Specific)
What to evaluate: Have they worked with other agencies in a white-label capacity? Can those agencies share their experience?
How to test: Ask for 2–3 agency references specifically (not just end-client references). Call them. Ask about communication, reliability, and quality.
Questions for references:
- How long have you worked together?
- Have they ever missed a deadline? What happened?
- How is their communication when things go wrong?
- Would you recommend them without reservation?
Green flag: Multiple long-term agency partnerships (12+ months). References speak enthusiastically. Specific examples of problem-solving.
Red flag: No agency references. All partnerships are short-term. References are vague or qualified.
Weight: Medium-High — Agency white-label work is different from direct client work. Experience matters.
10. Pricing Transparency
What to evaluate: Are rates clear and predictable? Are there hidden costs? How do they handle scope changes?
How to test: Request a detailed proposal for a sample project. Look for: hourly/monthly rates, what is included vs. extra, change request process.
Green flag: Clear monthly rates per developer. No setup fees. Scope change process documented. No surprise invoices.
Red flag: Vague pricing ("depends on the project"). Hidden fees for project management, communication, or tools. No process for handling scope changes.
Weight: Medium — Predictable costs protect your margins.
11. Security Practices
What to evaluate: How do they handle client data? Code access? Credentials? Do they follow security best practices?
How to test: Ask about their security policies. How do developers access production environments? How is code stored?
Green flag: Code in your repositories (not theirs). No production access without your approval. VPN or secure access for sensitive projects. Security awareness training documented.
Red flag: Code stored on their servers. Developers have unrestricted access. No security policies documented. Share credentials in plain text.
Weight: Medium — Especially important for financial, healthcare, or enterprise clients.
12. Scalability and Bench
What to evaluate: Can they add developers quickly if your demand grows? Do they have available capacity, or will they need to recruit?
How to test: Ask how quickly they can add a developer to your team. Ask about their current bench (developers available now vs. need to hire).
Green flag: Can add a developer within 1–2 weeks. Existing bench of available talent. Proven track record of scaling partnerships.
Red flag: Need 4–6 weeks to find additional developers. No bench — everything is recruit-to-order. Cannot guarantee scaling timeline.
Weight: Medium — Important if your agency is growing fast.
Scoring Your Candidates
Rate each candidate 1–5 on all 12 points. Weight the critical factors (1, 2) by 3x, high factors (3, 4, 5, 6, 7) by 2x, and medium factors (8–12) by 1x.
Maximum score: 150. A partner scoring below 100 has significant gaps. Below 80, walk away.
The One Non-Negotiable
If you take nothing else from this checklist: run a paid trial before committing.
Two weeks. One real project. Defined deliverables. This single step prevents 90% of bad partnership outcomes. If a potential partner refuses a trial, that tells you everything you need to know.
How Kwiqwork Scores on This Checklist
We designed our agency partnership model around these exact factors:
- Communication: 4-hour response guarantee during overlap hours
- NDA: Signed before first call
- Timezone: 4+ hours overlap with EU/US (IST, flexible hours)
- Trial: 2-week paid trial, free replacement if not satisfied
- Code quality: PR reviews mandatory, automated testing standard
- Team stability: 12+ month average developer tenure, named assignments
- Process: Full Jira/Linear access, daily standups, weekly demos
- Pricing: $1,600–$2,500/month per developer, no hidden fees
Request a trial with a specific project in mind. Two weeks of real work tells you more than any checklist.