Technical Readiness Checklist
Verify customer technical prerequisites before project kickoff
Ensure all technical requirements are in place to prevent 'we thought they were ready' disasters
How This Works
Use this checklist after contract signing but before project kickoff to verify customer readiness. Generate an email template to request evidence from the customer IT team, then track responses.
Select your solution tier and customize checklist items
Generate email template requesting evidence from customer IT
Mark items verified as you receive responses and evidence
Pro Tips for Maximum Value
🎯 When to Use This Tool
Use this immediately after contract signing but at least 2-3 weeks before kickoff. Waiting until the week before kickoff gives customer no time to address blockers, forcing you to delay the project or proceed without critical prerequisites.
✅ Best Practices
- •Set a response deadline - Give customer 1 week to respond, then follow up. Vague deadlines = no responses.
- •Request evidence, not promises - "We have API docs" is not verification. Request actual API docs, screenshots, or test credentials.
- •Save progress frequently - Use the Save Progress button after each customer response to track over multiple weeks
- •Escalate blockers early - If status = "Blocked", escalate to executive sponsor immediately. Don't wait.
- •Share checklist with customer PM - Print/PDF the checklist and give it to customer project manager so they can track internally
🚨 Critical Warning Signs
- ✗Customer doesn't respond within 1 week (signals low commitment or internal dysfunction)
- ✗Multiple "Blocked" items with no resolution plan (project will fail - delay kickoff)
- ✗Customer says "we'll figure it out later" for critical items (they won't - require resolution before kickoff)
🔗 Combine with Other Tools
Use Architecture Visualizer to show customer what infrastructure is needed → Use this checklist to verify that infrastructure exists → After verification complete, proceed to project kickoff.