Client group
Can you name the organizations, user range, tenants, and locations that would enter scope?
Bring a high-level profile; do not send private client data.
Ready?N/A
Service readiness guide
Make the operating decisions visible.
Review each decision area before a partner conversation. “Ready” means the question can be discussed; it does not mean every answer is final.
Retail promise
Can you explain what those clients believe your practice provides?
Bring the client-facing service description and known exclusions.
Ready?N/A
Capacity constraint
Can you identify the recurring work creating pressure?
Bring examples by category, not credentials or sensitive records.
Ready?N/A
Ownership
Is one person accountable for relationship-sensitive decisions?
Bring the role or owner who can approve change.
Ready?N/A
Intake channel
Do you know how requests should enter and whose identity appears?
Bring the desired front door and escalation path.
Ready?N/A
Technology boundary
Are tools, tenant conditions, endpoints, and specialist systems understood?
Bring constraints and dependencies at a high level.
Ready?N/A
Coverage expectations
Are business hours, on-site needs, after-hours expectations, and priority language explicit?
Bring requirements; do not assume they are included.
Ready?N/A
Reading the result
Unclear answers are useful when they are visible.
Several ready areas suggest the briefing can focus on fit and lane design. Several unclear areas suggest discovery should precede any commercial assumption. A non-negotiable coverage or technology requirement may materially change fit.
This page does not calculate a score or certify readiness. Its job is to improve the first operating conversation.
Turn the answers into a copyable brief