--- title: "How a Team Ran Partner CRM and Co-Selling in One Workspace — Kylon Use Case" description: "A working system for partner contacts, shared opportunities, joint plans, documents, and human-reviewed communication." url: "https://kylon.io/use-cases/partner-crm-co-selling" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>[Outreach & pipelines](https://kylon.io/use-cases/topics/outreach-pipelines)\>How a Team Ran Partner CRM and Co-Selling in One Workspace Use Case7 min read # How a Team Ran Partner CRM and Co-Selling in One Workspace A working system for partner contacts, shared opportunities, joint plans, documents, and human-reviewed communication. [Start in Kylon](https://app.kylon.io/launch/partner-crm-co-selling) [Book a call](https://cal.com/forms/5bd983bd-70e5-4afa-afd7-098b78cde6c3) What you'll connect - Gmail - Google Drive - Outlookoptional Your agent asks for each one in the Room. Nothing is sent or written until a person approves it. Kylon TeamProduct August 6, 2026 Step by step ## From a referral to a joint plan. One card per step. The agent prepares, and a named person decides. 1. 01 ### Give each partner one record Today Partner context searched across several inboxes before every partner conversation. In Kylon One record holds the owner, contacts, focus areas, shared accounts, notes and latest communication. Who decides The relationship owner confirms the record. 2. 02 ### Connect the joint opportunity Today Each partner keeps a different version of the same account story. In Kylon Each co-sell opportunity links the partner, account, stakeholder map, mutual actions and open questions. Who decides The internal owner sets the stage and next action. 3. 03 ### Prepare the introduction Today Partner updates pieced together from memory and scattered email threads. In Kylon An update or introduction request is drafted from prior emails, account notes and the joint plan. Who decides The relationship owner confirms recipients and wording, then sends. 4. 04 ### Keep the relationship current Today A request for input disappears after the planning meeting ends. In Kylon Owners are prompted to refresh the plan after a meeting, with a review brief prepared from the evidence. Who decides The relationship owner runs the partner review. What it works with ## The tools you already use. - Connection Gmail Carries partner threads, with each update drafted for the relationship owner to send. - Connection Google Drive Keeps meeting notes, joint plans and the shared materials behind each opportunity. - Optional Outlook Carries partner email if your team works from Outlook instead. Set it up ## Start with one partner and its accounts. 1. 1\. Start in Kylon A new Room opens in your workspace with this prompt. 2. 2\. Connect what it lists Gmail, Google Drive, from the card in the Room. 3. 3\. Give it your rules Your agent asks one at a time and writes them into the Room's guideline. Set-up prompt Set up our partner CRM and co-selling in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Gmail and Google Drive first, since the first run needs them. Tell me which ones still need connecting. Outlook can wait until a step uses it. 2. Ask me which partners we co-sell with, who owns each relationship, and who on the sales team works the shared accounts. Help me invite them to this Room. 3. Build a Partner CRM App with partners (relationship owner, contacts, focus areas, what may be shared) and co-sell opportunities (partner, account, referral source, stakeholder map, proposed value, mutual actions, open questions, stage, next review). Keep confirmed customer needs apart from our joint-selling hypothesis. 4. Read recent partner threads and meeting notes, and create a record for each partner and live opportunity. Show me the records, and flag any without an owner or a next review date, before you save them. 5. For the partner I pick, draft an update or introduction request from prior emails, account notes and the joint plan, and hold it in Gmail for the relationship owner to send. Never mark it as sent until a person has sent it. 6. Copy our stages, sharing rules and what the relationship owner must confirm before a send into this Room's guideline. 7. After one clean review cycle, offer to turn post-meeting plan refreshes and partner review briefs into an Automation. Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time. [Start in Kylon](https://app.kylon.io/launch/partner-crm-co-selling) Rolling this out with a team? ## How it works in detail ## Give the relationship one home A partner record holds the relationship owner, contacts, focus areas, shared accounts, meeting notes, documents, and the most recent communication. The team does not need to search several inboxes before every partner conversation. ## Keep joint opportunities connected Each co-sell opportunity can link the partner, account, stakeholder map, proposed value, shared materials, mutual actions, and open questions. People and agents work from the same current facts. ## Prepare introductions with context An agent can assemble a partner update or introduction request using prior emails, account notes, and the joint plan. The relationship owner reviews recipients and language before confirming an external message. ## Build a shared co-sell view The app can group opportunities by partner, stage, owner, or next action. It gives sales and partnership teams a usable operating view instead of another spreadsheet without conversation history. ## Make relationship care routine A workflow can prompt owners to refresh the account plan after a meeting, create follow-up work, and prepare a partner review brief with the linked evidence. ## Coordinate partner work around a shared account picture Co-selling becomes difficult when each partner maintains a different version of the account story. A referral may begin in a partner conversation, customer feedback may change the proposed use case, and the internal go-to-market team may be planning a launch at the same time. Kylon can hold the internal operating picture in a partner relationship record. A database app can capture the partner organization, relevant contacts, account opportunity, referral source, shared hypothesis, agreed responsibilities, materials requested, current stage, and next review. It is usable as an internal record and working application, not merely a static spreadsheet. Teams can link discussion, planning documents, customer feedback, and decision notes to the same record. This helps a partnership manager see where coordination is needed without exposing information that has not been approved for sharing. The record supports a deliberate process: establish context, agree on responsibility, prepare material, review the next action, and document what the teams learn. ### Keep partner communications prepared, reviewed, and accountable Partner communication needs careful ownership because it often represents more than one organization. Kylon can help prepare a draft using relevant connected email context and the current internal account record. For example, a team may prepare a recap of an agreed joint opportunity, request feedback on a proposed customer introduction, or assemble a concise list of materials for review. Before anything is sent outside the workspace, the designated relationship owner explicitly confirms the recipient, wording, commercial statements, permissions, and timing. Workflows can remind internal owners about reviews, collect requested input, and surface unresolved decisions. They should not be treated as an unattended partner outreach mechanism. Where a campaign requires sending at scale, professional outreach platforms remain responsible for bulk deliverability and campaign controls. Kylon maintains the internal account context so campaign activity and direct relationship work do not become disconnected. - Start each co-selling record with the referral origin, shared account context, named internal owner, and a clear note about what information may be shared. - Map responsibilities by task, such as customer discovery, product validation, proposal contribution, executive sponsorship, or post-meeting follow-up. - Attach customer feedback and meeting insights as evidence, while distinguishing confirmed customer needs from an internal joint-selling hypothesis. - Use review dates and internal reminders to prevent a request for input from disappearing after a planning meeting. - Draft external partner messages from relevant connected context, then require the accountable owner’s explicit confirmation before sending. - Review outcomes at the record level, including whether the next step occurred, what feedback was received, and what should change in the partnership playbook. > ““We stopped treating a partner introduction as a loose message. The record showed the source of the opportunity, each owner’s responsibilities, and the point at which a human needed to approve the next communication.”” ## Turn partner feedback into a reusable co-selling playbook ## What the team keeps in the internal system The exact fields differ by workflow, but the system keeps the source context, current status, accountable owner, decision history, related documents, relevant email thread, next internal action, and review date together. That structure gives people and agents a reliable starting point whenever work changes hands. ## Start with one repeated workflow Teams do not need to replace every tool at once. Start with the repeated work that currently requires people to copy information between conversations, inboxes, documents, and spreadsheets. Build a shared record, connect the people who own it, and use a workflow to support the review rhythm. The system becomes more useful as its context and decisions accumulate. See how Kylon can help your team turn recurring work into a shared operating system. [Talk to Kylon](https://cal.com/forms/5bd983bd-70e5-4afa-afd7-098b78cde6c3) ## More Use Cases [View all](https://kylon.io/use-cases) [ Before: 1,000 to email today, Re: group rates?, call notes: who?, hot lead, unread, OOO reply x40. With Kylon: 12 meetings booked from one send. Scored 214 replies by intent. Workflow tools: Gmail, Outlook, Fathom. ### How a US Hospitality Firm Built an AI Sales Pipeline with Kylon Agents run 1,000-contact outreach, score replies and route leads. - ![HubSpot](https://kylon.io/v2/integrations/small/hubspot-com.webp) - ![Apollo](https://kylon.io/v2/integrations/apollo.png) - ![Cloudbeds](https://kylon.io/v2/integrations/small/cloudbeds-com.webp) - ![Fathom](https://kylon.io/v2/integrations/small/fathom-video.webp) - ![Calendly](https://kylon.io/v2/integrations/small/calendly-com.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/ai-sales-pipeline)[ Before: resume\_final2.pdf, Re: still keen?, interview: TBD, 47 unread applicants, which role is this?. With Kylon: 12 interviews booked this week. Scored 47 resumes vs roles. Workflow tools: Gmail, Outlook, Google Calendar. ### How an AI Startup Automated Talent Sourcing with Kylon Resumes parsed, candidates scored and outreach managed from one room. - ![Greenhouse](https://kylon.io/v2/integrations/small/greenhouse-io.webp) - ![LinkedIn](https://kylon.io/v2/integrations/small/linkedin-com.webp) - ![Airtable](https://kylon.io/v2/integrations/small/airtable-com.webp) - ![Google Calendar](https://kylon.io/v2/integrations/small/google-calendar.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/talent-sourcing)