playbooks

home / skills / gtmagents / gtm-agents / joint-solution-blueprint

joint-solution-blueprint skill

/plugins/partnership-development/skills/joint-solution-blueprint

This skill helps teams document and launch co-built solutions with architecture, value storytelling, and GTM playbooks to accelerate partner-enabled deals.

npx playbooks add skill gtmagents/gtm-agents --skill joint-solution-blueprint

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
name: joint-solution-blueprint
description: Template for documenting co-built solutions, integrations, and GTM motions
  with partners.
---

# Joint Solution Blueprint Skill

## When to Use
- Launching or refreshing a co-built integration or packaged service.
- Equipping field teams with architecture, value props, and proof points.
- Coordinating enablement across product, marketing, and partner teams.

## Framework
1. **Use Case Definition** – target persona, pain point, and success metrics.
2. **Architecture Overview** – system diagram, data flows, dependencies, security notes.
3. **Value Narrative** – customer outcomes, ROI proof, competitive differentiation.
4. **Go-To-Market Plays** – positioning, pricing principles, launch checklist, asset library.
5. **Support & Lifecycle** – roles, escalation paths, roadmap commitments.

## Templates
- One-page solution brief with messaging + CTA.
- Architecture diagram checklist.
- Launch plan with tasks, owners, and deadlines.

## Tips
- Keep diagrams simple enough for sales decks, with appendix for technical deep dives.
- Include customer stories or beta insights to increase credibility.
- Pair with `build-co-sell-playbook` so reps know how to pitch + progress deals.

---

Overview

This skill provides a repeatable template for documenting co-built solutions, integrations, and joint go-to-market motions with partners. It organizes use cases, architecture, value narrative, GTM plays, and support lifecycle into a production-ready blueprint. The goal is to accelerate launches, align field teams, and ensure consistent messaging and enablement across product, marketing, and partner stakeholders.

How this skill works

The skill guides authors through a compact framework: define the target persona and success metrics, map the system architecture and data flows, and craft the customer value narrative and ROI proof points. It then captures GTM plays including positioning, pricing principles, launch tasks and assets, plus support roles and escalation paths. Templates include a one-page solution brief, an architecture checklist, and a launch plan with owners and deadlines.

When to use it

  • Preparing to launch or refresh a co-built integration or packaged service with a partner
  • Equipping sales, marketing, and customer success teams with unified architecture, messaging, and proof points
  • Coordinating enablement and launch tasks across product, partner, and field operations
  • Documenting responsibilities, support flows, and roadmap commitments for shared solutions

Best practices

  • Keep diagrams simple for sales decks and provide technical appendices for engineers
  • Focus the use case on a single target persona with clear success metrics and measurable outcomes
  • Include customer stories, beta insights, or pilot results to validate claims
  • Standardize launch tasks with owners, deadlines, and required assets to avoid gaps
  • Pair the blueprint with co-sell playbooks so reps know how to pitch and progress deals

Example use cases

  • Create a one-page brief and architecture checklist to support a joint integration launch
  • Build a GTM playbook that defines positioning, pricing guardrails, and channel motions
  • Document support and escalation paths before a commercial rollout to prevent handoff issues
  • Equip field reps with messaging, ROI proof points, and asset libraries for partner-led campaigns

FAQ

How detailed should the architecture diagram be?

Keep the main diagram high-level for sales materials and include a technical appendix with data flows, dependencies, and security notes for engineering teams.

What metrics should be included in the use case definition?

Include persona-specific success metrics such as time saved, cost reduction, revenue uplift, or adoption KPIs that can be tracked post-launch.