Partners, accounts, and activities

A partner is an alliance organization you work with — for example Accenture, Microsoft, or Snowflake. Each partner record holds motion types (GSI, Hyperscaler, ISV, OEM, tech alliance), a primary motion for default views, contacts on both sides, pipeline linked through partner–opportunity links, and delivery projects (implementations).

The partner page is your operational home for one relationship: Relationship signal, Co-sell pipeline, Execution health, recent activities, and skills like Brief Me and Partnership Scorecard.

An account is the end customer both you and the partner care about — Caterpillar, Bank of America, etc. Accounts belong to your organization. Activities attach to accounts through contexts: a single meeting can touch multiple accounts if the conversation spanned them.

Account-level relationship signals roll up to the partner's Relationship column (Cooling, Stable, Warming). Import accounts before capture if you want decompose to match names automatically.

An activity is a captured interaction: type, date, narrative, structured notes, participants, and linked contexts (account, opportunity, project). Next steps hang off contexts and can be bilateral — owned by your team or the partner.

The activity feed across Triad is filterable by partner, motion, and activity type. It is the audit trail behind pipeline and relationship scores, not a generic CRM task list.

Opportunities are deals on an account, often imported from Salesforce via CSV. Partner credit links attribute pipeline dollars to the partner that influenced or sourced the deal.

Projects (implementations) are post-sale delivery engagements — phase, target go-live, and your independent health status (On Track, Watch, At Risk, Escalated). Activities can link to open opportunities and active projects so Co-sell and Execution stay tied to conversation history.

Triad organizes partnership work into Relationship, Co-sell, and Execution. Partners list all three in one row. Accounts carry relationship signal. Opportunities feed Co-sell. Projects feed Execution.

When you capture against a partner and link an account context, you are wiring evidence into all three layers at once — which is why the data model rewards consistent linking during decompose review.