Partner Services Discovery & Assessment Kit

A structured framework for the partner team to run discovery, score readiness, and design services engagements

How to use this kit: Work through each section in order with your partner. Start with the Partner Readiness Scorecard, move into the Workflow Discovery Questions, then use the Service Design Worksheet to map the right engagement. The output is a recommended services path and a proof-of-value scope.

Framework Overview

This kit gives you and your partners a repeatable process for moving from first conversation → scoped services engagement.

It has four parts:

Partner Readiness Scorecard — assess where the partner is on the Services Ladder

Customer Workflow Discovery Questions — structured questions to surface AI automation opportunities

AI Readiness Assessment — evaluate the customer’s organizational readiness

Service Design Worksheet — translate findings into a recommended services path

Most successful engagements begin with a 60–90 minute discovery session using sections 2 and 3, followed by a scoped proposal using section 4.

⁠

Part 1: Partner Readiness Scorecard

Use this before designing a services engagement. It tells you which stage of the Go Services Ladder the partner is ready to operate at — and where they need enablement before moving forward.

Instructions: Score each dimension 1–4. Total score determines recommended starting stage.

Partner Readiness Scorecard

Partner Readiness Scorecard

⁠

Scorecard Interpretation

Total Score

Recommended Starting Stage

6–10

Stage 1: Implementation & Integration only — focus on platform enablement first

11–15

Stage 1–2: Implementation + Workflow Automation

16–20

Stage 2–3: Workflow Automation + Custom Agent Development

21–24

Stage 3–4: Full AI Transformation Programs — ready for strategic advisory work

There are no rows in this table

⁠

Michelle’s note for PMs: If a partner scores below 10, prioritize technical enablement and a supervised pilot before scoping a billable services engagement. Premature commitments create delivery risk.

⁠

Part 2: Customer Workflow Discovery Questions

Use these questions in your first 60-minute discovery session with the partner and their customer. The goal is to surface the workflows, pain points, and systems that are best suited for AI automation.

Organize the conversation across four areas:

Workflow Discovery Question Bank

Workflow Discovery Question Bank

Area

Discovery Question

What You're Listening For

Question Type

Partner Notes

Walk me through a workflow your team runs manually today that consumes significant time or creates coordination friction.

Volume, repetition, cross-system dependencies — all strong signals for automation

Where do your teams spend the most time searching for information or waiting on inputs from others?

Knowledge retrieval bottlenecks, approval chains, communication overhead

Which of your enterprise systems are most critical to daily operations — and how well do they talk to each other?

Integration complexity and system sprawl — flags where Go connectors create value

Have you tried to automate any workflows before? What happened?

Prior automation failures often reveal change management gaps and technical constraints

Where is AI on your executive agenda right now? Is there a named initiative or budget?

Sponsored budget and exec alignment dramatically accelerate deployment timelines

Do you have a Center of Excellence or internal team responsible for AI adoption?

Indicates governance maturity and whether a structured rollout program is needed

What's your biggest concern about deploying AI in your workflows?

Surfaces governance, security, and change management blockers early

Which teams or departments would benefit most from faster access to information and automated coordination?

Quantifies user scope and helps size the platform opportunity

If you could automate one workflow starting next quarter, what would it be and why?

Reveals the highest-priority use case and internal champion

How do you currently measure productivity or operational efficiency in these teams?

Establishes the baseline needed to demonstrate ROI post-deployment

Beyond this team, which other departments face similar challenges?

Maps the expansion path from initial deployment to enterprise rollout

Are there industry-specific workflows or compliance requirements that any solution needs to support?

Flags vertical solution opportunity and partner domain expertise needed

Have you built any agents yet? If so, what are they and who is using them? Do you know what the usage is for them?

What are the top 1-2 things that a user has to leave [key product] to go do?

What information do they copy-paste into or from [key product] on a regular basis?

There are no rows in this table

⁠

What kind of agent should be built?

About their product

What does your tool/app do, and who uses it?

What's the core workflow those users are in when they would need help? Think connection or integration with another tools.

Take one persona and list all of the tools that they use

Marketing: HubSpot, Figma

About their data

Do you have a public API or MCP server? What can it read/write?

What's the richest data they have — contacts, documents, tasks, content?

About the user

Which team or persona are we targeting first? (Sales, engineering, product, etc.)

What are they actively writing when they'd use this? (Emails, tickets, docs, Slack messages?)

About the moment

Is there a specific pain point that's obvious and demo-able in 30 seconds?

Do users need to act on something (rewrites, CRUD) or just know something (lookup, search)?

Those last two are the most important for scoping a prototype. The answers tell you whether to lean into screen annotations (writing + rewrites), the knowledge layer (rich data + search), or an MCP integration (taking action in their product).

The single most useful thing a partner can tell you: "Here's what our users are typing right now, and here's what they wish they didn't have to do manually." That's your agent.

⁠

Part 3: AI Readiness Assessment

After the discovery conversation, use this assessment to score the customer’s organizational readiness. This determines whether to recommend a proof-of-value deployment first or whether the organization is ready for a full transformation program.

Instructions: Score each dimension 1–3. Use the readiness bands below to determine the recommended engagement type.

Customer AI Readiness Assessment

Customer AI Readiness Assessment

Readiness Dimension

Score 1: Low

Score 2: Moderate

Score 3: High

Score (1–3)

Evidence / Notes

Executive Sponsorship

No named exec sponsor for AI

AI mentioned as priority but no budget or owner

Named exec sponsor with allocated budget

Internal AI Expertise

No internal AI knowledge or resources

IT or ops team exploring AI tools ad hoc

Dedicated AI team or Center of Excellence

Data & Systems Access

Siloed systems with no API access or governance

Some systems accessible; inconsistent data quality

Clean data, API access, and documented workflows

Workflow Documentation

No documented workflows; largely tribal knowledge

Some processes documented; gaps remain

Well-documented workflows with defined owners

Change Management Capability

No change management process or history

Some training programs exist; adoption uneven

Structured adoption programs with tracking

Prior Automation Experience

No prior automation; all manual

Some tools in use (Zapier, basic RPA); limited impact

Successful automation deployments with measurable results

Procurement & Security

Lengthy procurement; unknown security posture

Standard procurement with moderate security review

Fast-track procurement; clear security frameworks

There are no rows in this table

⁠

Readiness Bands

Total Score

Readiness Level

Recommended Engagement Type

7–11

Early Stage

Proof-of-value deployment only — pick 1 workflow, limited scope

12–16

Emerging

Implementation + 1–2 workflow automation engagements

17–19

Ready

Full Go implementation + custom agents + rollout program

20–21

Advanced

AI Transformation Program — enterprise-wide, multi-department

There are no rows in this table

⁠

PM Guidance: Customers scoring 7–11 are not ready for a transformation program yet — and partners who over-sell at this stage risk failed deployments. Recommend a scoped proof-of-value focused on a single high-visibility workflow. Success there creates the internal momentum needed to expand.

⁠

Part 4: Service Design Worksheet

Use the outputs of Parts 1–3 to design the recommended services engagement. Fill this out with the partner before writing a proposal or SOW.

This worksheet produces: a recommended services path, a proof-of-value scope, and the metrics that will define success.

Service Design Worksheet

Service Design Worksheet

Design Element

Guidance

Partner Input

Examples

Target Workflow

Identify the single highest-priority workflow to automate in the proof-of-value phase

Sales pipeline review automation | Support ticket triage | Engineering release coordination

Go Services Stage

Based on Part 1 scorecard, which stage of the Services Ladder will this engagement operate at?

Stage 1: Implementation | Stage 2: Workflow Automation | Stage 3: Custom Agent | Stage 4: Transformation

Recommended Service Type

Select the primary service type based on partner capability and customer readiness

AI Workflow Assessment | Go Implementation | Enterprise Rollout | Custom Agent Development

Systems to Integrate

List the enterprise systems Go will connect to in this engagement

Salesforce, Jira, Confluence, ServiceNow, Slack, Teams

Primary Buyer

Who is the economic buyer and executive sponsor at the customer?

CIO, VP of Operations, Chief Digital Officer, VP Engineering

Success Metrics

Define 2–3 measurable outcomes the customer will see in the first 90 days

Hours saved per week, reduction in escalations, improvement in pipeline visibility

Expansion Path

Which additional teams or workflows will be targeted in Phase 2?

From sales ops to marketing ops | From engineering to customer success

Estimated Engagement Duration

How long will the initial engagement run?

4–6 weeks (POV) | 3 months (Implementation) | 6+ months (Transformation)

Partner Deliverables

What will the partner produce as part of this engagement?

Assessment report, deployment configuration, workflow documentation, agent library, rollout plan

Superhuman Support Needed

What does the partner need from Superhuman to execute this engagement?

Technical sandbox, co-sell support, partner solution architect, reference customer intro

There are no rows in this table

⁠

Recommended Engagement Paths

Based on the combination of partner readiness and customer AI readiness, use this matrix to recommend the right starting engagement.

Partner Stage → Customer Readiness ↓

Stage 1 Partner

Stage 2 Partner

Stage 3–4 Partner

Early (7–11)

4-week POV: 1 workflow, Go config only

POV + Workflow Design Sprint

POV + Custom Agent Prototype

Emerging (12–16)

Implementation + basic workflow setup

Implementation + Workflow Automation package

Implementation + Agent Library

Ready (17–19)

Implementation + partner upskill plan

Full workflow automation practice

Full transformation program

Advanced (20–21)

Refer to Stage 2–3 partner

Multi-department automation

Enterprise AI Transformation Program

There are no rows in this table

⁠

How to Use This Kit: Recommended Flow

Before the partner meeting — complete Part 1 (Partner Readiness Scorecard) using what you already know about the partner

During the first discovery session — run through Part 2 questions with the partner and their customer contact

After the session — score Part 3 (Customer AI Readiness Assessment) based on what you heard

In the follow-up call — complete Part 4 (Service Design Worksheet) with the partner to scope the engagement

Output — use the Recommended Engagement Paths matrix above to confirm the services path, then hand off to the partner to build the proposal

Tip for PM: Run this process with your top 3–5 partners first to build reusable case examples. Each completed kit becomes a reference template you can share across the partner team.

Next Steps: Once an engagement is scoped, connect the partner with Technical Enablement (Implementation Blueprint) and ensure they have access to the Agent Builder documentation. For Stage 3–4 engagements, loop in a Superhuman Solution Architect for co-delivery support.

Agent Identifier Workflow

List the persona and the top X apps/tools they use for what purpose

Marketing Stack Examples

CRM & Marketing Automation

SEO & Competitive Intelligence

Email Marketing

Marketing Eyecandy

Paid Advertising

Content Optimization

Marketing Planning & Collaboration

Workflow Automation

Web Analytics

HubSpot

Salesforce

Semrush

Hootsuite

Buffer

Outreach

HubSpot

Mailchimp

Klaviyo

Canva

Figma

Google Ads

Meta Ads Manager

Surfer SEO

Notion

Zapier

Google Analytics 4

There are no rows in this table

⁠

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.