Tech Integration Proposal AI Prompt

Propose a technology integration partnership with this AI prompt. API scope, joint value, and go-to-market plan. With fill-in variables and real examples.

The prompt

ROLE: You are a product partnerships manager who ships integrations that drive adoption.

CONTEXT: My product: [MY_PRODUCT] with [MY_API]. Partner product: [PARTNER_PRODUCT]. Integration idea: [INTEGRATION_IDEA]. Shared customers: [SHARED_CUSTOMERS]. Technical effort: [EFFORT].

TASK: Write a technology integration partnership proposal.

FORMAT: 1. Integration Vision (what users can do, described as a user story). 2. Joint Value (for shared customers, for each company: adoption, retention, revenue angles). 3. Technical Scope (MVP integration: endpoints, data flow, auth, effort estimate per side). 4. Build Plan (phases, owners, timeline). 5. Go-to-Market (joint announcement, docs, marketplace listing, co-marketing). 6. Support Model (who supports what, SLAs). 7. Commercial Terms (any revenue share, costs). End with 3 integration partnership failure modes and preventions.

CONSTRAINTS: MVP scope must be shippable in 6-8 weeks; grand integrations die in planning. Each side's effort must be roughly balanced or explicitly compensated. Include a sunset clause discussion point.
If any variable is unclear or missing, ask up to 3 targeted clarifying questions before producing the output, and clearly mark every assumption you make with [ASSUMPTION].

Variables to fill in

Replace each [variable] in the prompt with your own details:

[MY_PRODUCT] [MY_API] [PARTNER_PRODUCT] [INTEGRATION_IDEA] [SHARED_CUSTOMERS] [EFFORT]

Example input

MY_PRODUCT=HelpdeskPro, MY_API=REST + webhooks; PARTNER_PRODUCT=ChatFlow chatbot; INTEGRATION_IDEA=bot escalates to human agents with full context; SHARED_CUSTOMERS=200 overlapping; EFFORT=3 eng-weeks per side

How to use this prompt

Validate with 5 shared customers first, scope the MVP tightly, and get engineering leads from both sides in the room before proposing timelines.

Tips for the best results

Ship the MVP integration before the press release; announced vaporware burns both brands.
Shared customers are your leverage and your QA; involve them early.
Document the support split clearly; integrations break at 2am and someone must own the pager.