Skip to content
Partner Enablement Hub
Partner Enablement Hub
Accredidations
Delivery Enablement
Sales Enablement
Superhuman Internal Enablement
Database
Scratch Pad
Archive
Share
Explore

Go Services & PM Enablement – Top Near-Term Needs

Lauren’s stated top priority: Services enablement for Go by April (v1)
Focus areas from Go OS:
Partner revenue opportunities
Services opportunities
Custom agent development
Industry solutions

Recognized realities:
For Go, partners cannot realistically sell without a services/agent-build motion
The team is “building and flying the plane” simultaneously; must support both grassroots deals and long-term framework

Concrete near-term Go deliverables (over next ~month, 3/20/26-4/20/26):


1. PM-facing training: How to talk to Go beta customers

Deliverables
Training
Guide?
Purpose:
To get PMs to start taking the lead
⁠
To get partners to
⁠
:
completing enablement and technical onboarding
beginning to explore agent development opportunities
initial partner-led opportunities identified
Topics to Cover
⁠
Launch Goals
⁠
(Do PMs already know this?)
The goal of the entire partner launch is to convert early excitement around Go into real partner-led customer activity. In the first phase of launch, the partner ecosystem should begin to demonstrate:
active partner engagement with Go
partners pursuing new opportunities
services offerings emerging around the platform
early customer deployments
Our focus is to activate a small number of strategic partners who are ready to build solutions, pursue opportunities, and deliver customer value quickly.
PM discovery structure (business overview, goals, gaps, key vendors)
Elevator Pitch: For many organizations, the challenge is not access to AI - it is turning fragmented AI tools into measurable enterprise value. Go solves the “last mile of AI” problem by delivering a single AI layer that spans the entire workplace.
Discovery
What are the biggest gaps that your key product lacks? (HubSpot, Jira, JSM, etc)
Overview of agents
What are the agent capability levels
Level
Type
Description
Example
L0
Connector Agents
Basic integrations that move data between systems
​
L1
Solution Agents
Agents that automate specific tasks across multiple systems
​
L2
Workflow Agents
Advanced agents that orchestrate complex workflows end-to-end
​
There are no rows in this table
⁠
Use Hector’s Claude-based ideation tool: Feed partner focus into the “What Agent to Build” agent→ generates 3 agent ideas
Walk through how to do this
Prompt 1
Prompt 2
Prompt 3
Prompt 4
Suggested Agent- who needs to sanity check this? Partner and SH?
Workshop ideas with customer, define next steps/goals for beta
What are the next steps we want?
Output: simple, tactical guide for training for PMs
Results:


2. Partner-facing “How to Get Going with Go” guide

Very high-level, fast-start resource, not an Accred:
Base overview / pitch (can reference existing CRO training)
How to build first agent(s)
Where to find SDK docs
Services/implementation entry points and next steps

3. Go Webinar (partner-focused)

Topic candidates:
How to support customers with Go services
How to support your first Go opportunity
How to identify right-fit customers & use cases
“You’re in beta—what next?” for Go
Include Hector and Eric as technical experts (SDK, agent creation)
Desired outcome: each attendee leaves with at least one specific customer/action to pursue (optionally with a SPIFF)

Additional suggested enablement workstreams:
AE-facing resource (v1): partner resource guide on:
Which partners are in Go beta
How to connect AEs with the right partners
Basic guidance on when to involve partners for Go opportunities
Ongoing “PM Go Tip of the Week”:
Short, tactical prompts for PMs on what to talk about with partners
Helps PMs sustain proactive conversations with beta partners
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.