---
name: "scope-the-tech-partnership"
description: "Use when an integration or product partnership needs pre-engineering scoping: the brief, the ranked roadmap input, readiness, and the handoff."
triggers: ["integration scoping brief", "partner API review", "voice of partner for product", "integration launch readiness", "hand off an integration to engineering", "beta coordination with a partner", "technical validation gate"]
version: "1"
---
# Scope the tech partnership
Use this when an integration or product partnership needs scoping before
engineering picks it up. Start from the partner's product and API
documentation, the integration ask, our product contacts, and the roadmap
window.
This hands off to engineering. It never implements.
## Write the scoping brief
Platform and program selection first — pricing, program features, case
studies — then the application programming interfaces (APIs) and the
extensibility surface, data flows, authentication, and rate limits, then
the open questions for partner engineering.
Each unknown names who can answer it and by when. An unknown with no
owner is not scoped.
## Synthesize the voice of partner for Product
Ranked partner asks with their evidence: who asked, what deal or adoption
is attached, how often it comes up. Then what we will not build, with the
reason for each.
Product decides. This brief informs.
## Set launch readiness
Documentation, a sandbox, the support path, joint messaging, and the
early-access or beta coordination plan — who is in it, what success looks
like, and when it ends.
Pass the certification and technical-validation gate on performance,
security, and interoperability before launch. A launch with no support
path stays in beta.
## Hand off clean
The brief, one named owner on each side, and a date. Then track the
handoff and the integration success metrics — adoption, attach,
retention lift — not the build.
## What you hand back
The scoping brief, the ranked roadmap input, the readiness checklist, and
the dated handoff.
## Fallbacks
No API documentation means scoping from public material marked INFERENCE,
with the documentation request as step one. No product contact means the
introduction ask comes before any roadmap input.