Land Your Offer – Anatomy of Revenue Generating Partner Offer – Part 4 – Cowork

This article series has traced the journey of Copilot, starting with its initial trial (Part 1), progressing through its funded development (Part 2), and culminating in its comprehensive launch (Part 3). In Part 4, we’re focusing on the latest phase: encouraging users to fully embrace Copilot Cowork for their intricate, multi-step tasks.

This phase marks a shift from the earlier ones. There’s no need to log engagement hours or select T-shirt sizes anymore. Everything hinges on a single metric: the increase in Cowork participants over the next three months. Boost that number, and everything else will follow suit. Microsoft has also announced that usage-based billing will automatically apply to new Microsoft 365 Copilot Business licenses purchased through CSP starting 1 December 2026, simplifying the process for customers embarking on their first Cowork task. By focusing on outcomes instead of effort, you can implement a fixed routine that is repeatable with every client.

The activation process initiates with a consistent conversation. Customers now have four distinct ways to engage with Copilot, and the first step is determining which method aligns best with their needs.

Cowork is perfect for tasks that involve multiple steps, span across different applications, and culminate in actions such as updates, approvals, or routed requests. Tasks that are purely informational should remain within Chat.

Guiding customers to transition this type of work to Cowork is quite consistent across different tenants, which makes this initiative valuable. Design a standard process once, and you can replicate it with every new client:

• Consistent lead-in: Checking readiness, licensing, and billing can take around four weeks and follows a single checklist.
• Uniform assessment: Each pilot user runs the same prompt to assess their recent work and determine if Cowork is a suitable fit.
• Standardised sixty scenarios: Ten proven scenarios for each of the six business functions, implemented in the same order over a three-week period.
• Identical milestones: Achieving 50 active users and $2,500 in monthly Cowork usage by the end of Month 1, maintaining this through Month 3.
• Compounding reuse: Successful scenarios evolve into shared Cowork skills, allowing each new client to benefit from previous work.

This consistency contributes to the predictability of the motion. The twelve-week activation does not involve a customer fee, as Microsoft’s partner programs reward the growth generated, and your revenue increases as clients onboard more users. Following this, the monthly service creates additional value long after the activation period ends. You can package and market it through any of the channels your customers already use—whether directly, via your distributor, as a private offer, or through Microsoft Marketplace listings. Once the processes are identical, packaging becomes straightforward.

The most easily reusable components are the scenario library: ten scenarios for each function across all six, implemented during Month 1. Each scenario comprises actual delegated work, not just a single prompt.

The sixty scenarios provide a proven launchpad. The Cowork Investment Advisor, the engine behind the Cowork Investment Assessment outlined in this guide, identifies the specific work relevant to each individual. It analyses their Work IQ indicators (emails, meetings, documents, chats, and collaboration habits) and returns:

• Persona: identifies the user’s work style, helping determine which of the six functions to select scenarios from.
• Top three workflows: highlights the tasks that are eligible for Cowork, categorised as Light, Medium, or Heavy.
• Cost and return: provides estimates for credits, pay-as-you-go expenses, and pre-purchase costs, alongside potential returns.
• Outcome: Yes (two or more qualifying workflows across different teams), Yes with a pilot (one workflow), or Not yet (none).

A workflow qualifies only if it entails multiple steps, transfers data between several applications, culminates in a business action, incorporates decision points, and tracks its own progress. Purely informative tasks should be directed to Copilot Chat, Copilot Pages, or scheduled prompts instead.

Select the format that best aligns with the individual executing it: whether it’s a prompt any Copilot user can input into Copilot Chat, an agent version that can be shared by a team leader, or a pre-configured agent that IT can launch across the entire organisation. Make sure to run this alongside the rollout of scenarios, not beforehand, and integrate its output into the Customer Cowork Estimator to assess credit expenses.

The scenarios and assessments drive usage, governed by a brief set of guidelines that define when this usage counts.

• Which customers qualify: By August 2026, customers should have Microsoft 365 Copilot with Cowork enabled, fewer than 50 monthly active Cowork users, and under $2,500 in monthly consumption. At least half of their Copilot licenses and Cowork use must come through CSP. Strategic 500 clients are excluded.
• When the clock starts: The first month a customer hits a minimum of 50 monthly active Cowork users and at least $2,500 in monthly consumption becomes Month 1 of a three-month evaluation window.
• How payments are determined: Both criteria must be met in Month 3. Month 2 does not count but contributes to the usage measured in Month 3.
• Payment details: $50 for each eligible new user. Qualified new users are determined by the lesser of two amounts: the cumulative Month 3 users minus August users, or additional monthly consumption divided by $50. The payment range is a minimum of $200 up to $12,500 per tenant, equating to 250 new users.
• Timing: Payments are processed 45 days after the conclusion of the window, made as a rebate. This is in addition to your CSP consumption profits.
• Frequency: The window can be claimed once for each customer tenant throughout the incentive’s duration. If Month 3 results fall short, a new window can commence the next month when both thresholds are met. The final window can start in June 2027.
• Eligibility to claim: Partners with a Solutions Partner designation in areas like Modern Work, Business Applications, Infrastructure, Data & AI, or Digital & App Innovation, plus trailing revenues of $1M (for direct billing) or $25K (for indirect resellers). Indirect resellers can qualify with 25 capability points without needing a designation. Copilot specialization is not required.
• Attribution criteria: The same partner must be the recorded transacting partner for both the Copilot licenses and the Azure subscription that includes the Cowork consumption.
• Term details: Valid from 1 September 2026 to 30 June 2027.

These guidelines form a four-stage process: Qualify, Activate, Sustain, and Reward.

• Qualify (four weeks before Month 1): Ensure you meet the partner requirements and complete your setup in Partner Center. Locate customers who meet the August baseline. Designate yourself as the transacting partner for licenses and consumption. Move Cowork billing onto a CSP Azure plan with Owner or Contributor access, allowing Partner Earned Credit to apply, and enable the default spending policy.
• Activate (Month 1): Run two independent processes simultaneously; the assessment can begin in the lead-in, with neither waiting for the other.
  • Assess the work: Prompt each pilot user to complete the Cowork Investment Assessment, either as an agent or by entering its prompt in Copilot Chat. The assessment reviews their work over the past three to six months and indicates if Cowork will provide the most value.
  • Implement the scenarios: Roll out the six functions weekly: Executives and Sales in the first week, Marketing and Customer Service in the second, followed by Finance and Operations and Legal in the third.
  • Facilitate uninterrupted usage: Allocate around $50 per user each month (approximately 5,000 credits) and establish a Cowork spending limit of at least 250,000 credits per month, including alerts, to ensure usage reaches the Week 4 milestone without hitting a cap.
• Sustain (Months 2 and 3): Preserve successful scenarios as shared Cowork skills for any selected team to reuse, and incorporate additional pilot users to maintain active users above 50. Regularly check users, credits, and attribution in Cost management in the Microsoft 365 admin centre. Ensure prompt credit approvals and address any declines before Month 3.
• Reward (after Month 3): Calculate qualified new users, anticipate payment around six weeks after the window closes, and transition the customer to monthly managed services. The tenant can only receive payment once, so activation payments for subsequent tenants will follow.

Each phase can be broken down into actionable steps, allowing the same strategy to work for any eligible tenant. The timing suggested is for pacing, not a strict requirement. Week 1 refers to the first week of Month 1, while negative weeks denote the lead-in period.

Executing these steps for one tenant can yield three forms of returns within the evaluation window. Here’s an overview of how it all adds up for a customer starting from zero Cowork usage.

† Illustrative. Assumes $50 of monthly Cowork usage per new user, equating to $2,500 a month at 50 users and $12,500 a month at 250. The CSP incentive is distributed as 60% rebate and 40% co-op. The 13% Partner Earned Credit rate is for planning purposes; the actual rate is listed in the Partner Center price guide. Always verify figures against the latest Microsoft Commercial Partner Incentives Guide.

When the Partner Earned Credit applies: All of the following conditions must be satisfied:

• You must possess a current Microsoft AI Cloud Partner Program contract and invoice the customer’s Azure plan through CSP.
• The Cowork consumption must be billed on a pay-as-you-go basis through that Azure plan. Reservations, savings plans, Spot virtual machines, and Marketplace or third-party entries are excluded.
• You should hold administrative access to the subscription through an eligible Azure role: through default admin on behalf of (AOBO) access, Azure Lighthouse, or user/service-principal accounts linked with Partner Admin Link. This role must be linked to the subscription, resource group, or management group level, since root scope alone is insufficient.
• If you are an indirect vendor, your indirect provider must grant you that role on the customer’s subscription.
• This access must be sustained. If the customer removes it or the subscription shifts to a new partner who doesn’t configure it again, the credit is ceased.

Credits are calculated daily and reflected as a reduced price on your invoice, not as a separate item. For full guidelines, refer to Partner Earned Credit for managed services.

The potential for these returns increases in two ways. Firstly, the CSP incentive and Partner Earned Credit continue beyond Month 3, recurring each month the customer relies on Cowork. Secondly, the activation payment is limited to one per tenant, meaning that true scale is achieved by implementing the same twelve weeks with multiple tenants. To identify these tenants, filter the AI Business Solutions & Security Insights (ASPX) dashboard for customers in your management purview that possess Copilot, less than 50 Cowork users, and a CSP connection. Assemble a new cohort each month. Keep in mind that the last activation window can begin in June 2027, meaning every month you delay results in one less cohort.

The visual summary below simplifies one tenant’s journey onto a single page: the twelve-week activities illustrated along the top and the returns displayed below. Observe it from left to right:

1. Lead-in (four weeks before Month 1): Confirm eligibility, attribution, Partner Earned Credit, and Default Spending policy setup, while pilot users are evaluated through the assessment.
2. Month 1 (weeks 1 to 4): Two functions are introduced each week: Executives with Sales, then Marketing with Customer Service, and finally Finance and Operations with Legal. Achieve the milestone in Week 4: 50 users and $2,500 in usage.
3. Months 2 and 3 (weeks 5 to 12): Foster champions, provide role-based training, and onboard new users continuously. Turn effective scenarios into reusable skills by Month 2. Monitor progress weekly to ensure both metrics remain above the threshold until the Month 3 evaluation.
4. Payout (around week 18): Calculate qualified users, with the ~$2.5K activation payment processed. The ~$0.98K CSP incentive and ~$0.98K Partner Earned Credit accumulate over the months, leading the window to roughly $4.5K per tenant before engaging managed services.

Ending this payout signals the close of the activation phase, not the conclusion of the partnership. Ensuring Cowork remains beneficial requires ongoing efforts each month. Therefore, consolidate services into three categories: combine Cowork adoption, support, and FinOps into one subscription after Month 3, and introduce security and scaling services as necessary based on customer requirements.

The total line reveals the economic narrative. About $55K in annual service revenue from a single tenant supplements the ~$4.5K gained during the activation period, and this repeats annually as long as the customer continues to utilise Cowork. On the customer side, the $103K in total expense is apportioned as $30K for Cowork, $18K for Copilot licenses, and $55K for services. As usage expands to 100 or more users in a year, Cowork spending escalates to around $60K, with the return also escalating towards threefold.

All value figures are illustrative. They presume a savings of 2 hours per user weekly at a rate of $50 per hour, with Copilot costs at around $30 per user monthly and a partner day rate of $1,000. Adjust these figures with the results of each customer’s Investment Assessment.

To activate the playbook, start with one tenant and implement these six steps:

1. Verify eligibility: Confirm your Solutions Partner designation and revenue threshold, then enroll in the incentive and finalize your Partner Center information.
2. Identify your tenants: In ASPX, filter for customers using Copilot, with Cowork under 50 users and a CSP relationship. Check each against the August 2026 baseline.
3. Ensure correct configurations: Attribution, the CSP Azure plan, and default spending policy must be established before Month 1. A missed setup step cannot be rectified during the window.
4. Run the assessment concurrently: Pilot users can complete the Cowork Investment Assessment anytime. This will not delay the rollout of scenarios, and the results will inform where Cowork can expand next.
5. Package it once: Approach the twelve-week activation as a worthwhile investment that generates returns as user numbers grow; layer on monthly services for adoption, FinOps, and scaling, marketed through pre-existing customer purchasing channels.
6. Schedule the Month 3 review on day one, alongside the sponsor’s first monthly business review.

Cowork marks the transition of Copilot from merely answering queries to accomplishing tangible tasks. Help each customer reach this milestone, one tenant at a time.

These resources offer guidance on the rules, tools, and the broader context surrounding Copilot in line with this playbook.