Land Your Offer – Anatomy of Revenue Generating Partner Offer – Part 2 – Copilot Envisioning
In Part 1, we explored the Copilot in 30, which offered a trial for small and medium-sized businesses. This time, we’re targeting larger clients, with a funded engagement instead of a complimentary one. The shift in focus also changes how we generate revenue. This announcement coincides with the recent launch of Microsoft’s new Copilot featuring Home, Code, and Autopilot functionalities. This new model operates on a usage-based billing system managed through FinOps for AI, opening the door for a richer dialogue about future enhancements.
Most companies with over 300 office seats already recognise the significance of Copilot and its agents. However, they often find themselves unclear about how to leverage AI effectively, what preparations are necessary, and how to substantiate investment before allocating resources. The Frontier Accelerate for Copilot: Envisioning & POC engagement offers a pre-sales, partner-led solution to these challenges, funded by Microsoft. The engagement can vary from a swift 10-hour readiness sprint to a comprehensive 280-hour enterprise programme. By packaging this as a Microsoft Marketplace offer, you create a consistent pathway to every Copilot, Agent 365, and Microsoft 365 E7 opportunity in your region.
Microsoft Marketplace serves as a business platform focused on partners, aimed at expanding your reach and streamlining your sales processes. By publishing an offer, you provide your practice with a visible, permanent storefront in the spaces where customers and Microsoft sellers actively seek Copilot expertise.
What’s more, an offer allows you to transform your expertise into something that can be replicated. You only need to define the engagement’s phases, activities, deliverables, and sizing once, enabling you to implement it with each qualified customer instead of having to build out a new scope each time. Professional and managed service offer types are available in Partner Center, meaning one listing can encapsulate envisioning engagements, proofs of concept (POCs), and the ongoing services that follow.
Your target clients for this offer are organisations with a minimum of 300 Office 365 or Microsoft 365 seats — from mid-tier companies to the largest enterprises. These clients stand to gain the most from adopting Copilot and agents; however, they also face significant complexities such as security and governance concerns, tenant access dependencies, change management, and a reliable method to measure the promised value.
This space, where ambition meets actionable planning, is where partners can really make their mark. For FY27, Microsoft is putting significant resources into the entire Copilot journey, from envisioning to POC, deployment, and adoption — making the envisioning stage crucial for plotting the roadmap, determining scope, and steering the commercial discussion effectively.
Microsoft 365 Copilot seamlessly integrates AI into familiar daily applications — such as Outlook, Teams, Word, Excel, and PowerPoint — so users can derive value without changing platforms. For larger organisations, this is merely the first level: complementing Copilot with Agent 365, bespoke agents crafted via Copilot Studio, and Microsoft 365 E7 enhances personal productivity and introduces automation at both role and process levels.
The new Copilot also introduces a third level. Cowork manages delegated tasks and delivers final outputs; Code enables users to develop apps, dashboards, and automations using natural language hosted on Copilot Managed Runtime; while Autopilot functions as a persistent agent with unique identity, ensuring workflow continuity without prompts. All three employ usage-based billing instead of the traditional per-user subscription model, compelling all customers to gauge which users and scenarios justify this spend and how to oversee it through FinOps for AI.
Each of these advancements raises vital questions — Which user personas should be targeted? What scenarios are most beneficial? What governance measures need to be in place? What consumption models are justified? Each question presents an opportunity for envisioning discussions, placing partners in an optimal position to navigate these conversations.
The Frontier Accelerate for Copilot: Envisioning & POC engagement provides a partner-led initiative that pinpoints user personas and use cases while constructing a solid business case for Microsoft 365 Copilot, Agent 365, Microsoft 365 E7, and/or agents, complemented by an optional proof of concept. The fundamentals include:
- Who qualifies: Organisations must have at least 300 Office 365/Microsoft 365 seats; those with 500, 1,000, 1,500, 3,000 / 5,000 and 10,000+ seats unlock larger tiers.
- How it’s sized: There are six tiers — XXS (10 hrs), XS (20 hrs), S (40 hrs), M (100 hrs), L/XL (150 hrs), and XXL (280 hrs) — with hour allocations determined by the number of seats in scope.
- What it covers: The engagement unfolds in five phases — Assess, Inspire, Design, POC, and Executive Summary — and provides a working POC with measurable outcomes from the S tier onwards.
- What Microsoft provides: Delivery guides, planning resources pre-engagement, and Microsoft Commercial Incentives (MCI) funding linked to proof of execution.
- What the customer receives: Readiness findings, a business case and value plan (incorporating usage-based billing and Copilot Credits), technical necessities, a remediation plan, an adoption roadmap, a functioning POC, and a comprehensive executive summary.
Microsoft covers the costs, but you maintain control over the scope, the client relationship, and all subsequent services.
It’s essential to understand that an envisioning engagement goes beyond a standard workshop; it guides decision-making. Your objective is to transition the customer from curiosity to a formal proposal, providing supporting evidence throughout the journey.
- Assess: Pinpoint high-impact scenarios, select appropriate assessments, define success metrics, and produce actionable readiness findings for the customer.
- Inspire: Showcase the capabilities of Copilot and its agents across different roles; make topics like security, governance, adoption, and reporting tangible to mitigate concerns.
- Design: Convert your findings into a business case and value plan (including usage-based billing), create a remediation plan, outline technical requirements, design an adoption roadmap, and establish clear POC success criteria with designated risks, responsible parties, and deadlines.
- Prove: Define which users and products are part of the POC, prepare the required environment, develop the agent or solution, train users, and measure outcomes—including Copilot Credits used.
- Summarise: Present the executive summary highlighting seat growth and consumption, then facilitate the transition from trial to paid licences along with a commercial proposal and expansion strategy.
Every phase yields tangible outputs the client retains, reinforcing your position as the partner who should lead future initiatives.
Below, you’ll find the complete activity plan for this offer, detailing hours allocated for each of the six engagement sizes. Use it as a reference for creating your own offer plans and statements of work.
| ID | Phase | Activity | XXS | XS | S | M | L/XL | XXL |
|---|---|---|---|---|---|---|---|---|
| — | Pre-req | Customer eligibility (min. O365/M365 seats) | 300+ | 500+ | 1,000+ | 1,500+ | 3,000+ / 5,000+ | 10,000+ |
| A1 | Assess | Identify high-value scenarios | 0.5 | 1 | 1.75 | 3.75 | 5.5 | 10.5 |
| A2 | Assess | Select assessment(s) | 0.5 | 0.5 | 1 | 2.25 | 3.5 | 6.25 |
| A3 | Assess | Define success | 0.5 | 0.75 | 1.5 | 3 | 4.5 | 8.5 |
| A4 | Assess | Deliver readiness assessment(s) | 1 | 1.75 | 2.75 | 6 | 9 | 16.75 |
| I1 | Inspire | Product overviews & demos across Copilot and agent capabilities | 1 | 1.5 | 2 | 4.5 | 6.75 | 12.5 |
| I2 | Inspire | Security/governance overview, incl. tenant and access dependencies | 0.5 | 1 | 1.5 | 3 | 4.5 | 8.5 |
| I3 | Inspire | Adoption/change overview | 0.5 | 0.75 | 1 | 2.25 | 3.5 | 6.25 |
| I4 | Inspire | Reporting/analytics overview | 0.5 | 0.75 | 1 | 2.25 | 3.5 | 6.25 |
| I5 | Inspire | Stories & Scenario Library | 0.5 | 1 | 1.5 | 3 | 4.25 | 8.5 |
| D1 | Design | Business case/value plan, incl. usage-based billing (UBB) | 1 | 1.75 | 2.75 | 6.25 | 9.5 | 17.5 |
| D2 | Design | Remediation plan | 0.5 | 1 | 1.75 | 3.75 | 5.5 | 10.5 |
| D3 | Design | Technical/functional requirements | 0.75 | 1.5 | 2.25 | 5 | 7.5 | 14 |
| D4 | Design | Adoption roadmap | 0.5 | 1 | 1.75 | 3.75 | 5.5 | 10.5 |
| D5 | Design | POC success criteria & environment prep | 0.5 | 1 | 1.75 | 3.75 | 5.5 | 10.5 |
| D6 | Design | Recommendations/risks/owners/dates, incl. validation and next-step owners | 0.25 | 0.75 | 0.75 | 2.5 | 4 | 7 |
| P1 | POC | Scope/users/products/features | 0 | 0.25 | 1 | 3.5 | 5.25 | 9.75 |
| P2 | POC | Confirm requirements/design | 0 | 0.25 | 1 | 3.5 | 5.25 | 9.75 |
| P3 | POC | IT access & environment prep | 0 | 0.25 | 1.75 | 5.25 | 8 | 14.75 |
| P4 | POC | Trial licenses | 0 | 0.25 | 1 | 3.5 | 5.25 | 9.75 |
| P5 | POC | Build POC agent(s)/solution(s); confirm Copilot Credits consumption | 0 | 0.5 | 3.75 | 12.25 | 18.5 | 34.25 |
| P6 | POC | Train POC users | 0 | 0.25 | 1 | 3.5 | 5.25 | 9.75 |
| P7 | POC | Measure/evaluate results, incl. usage and Copilot Credits consumed | 0 | 0.25 | 1.5 | 3.5 | 5 | 10 |
| E1 | Exec summary | Executive readout: seat growth and consumption implications | 1 | 2 | 4 | 10 | 15 | 28 |
| TOTAL | Hours | 10 | 20 | 40 | 100 | 150 | 280 |
The table below outlines the revenue dynamics of one Envisioning & POC engagement for each of the six sizes, illustrating that the funded engagement is just the first of three potential revenue streams. These build upon one another:
- MCI engagement incentive: Microsoft finances the envisioning and POC itself, ranging from $2,000 for a 10-hour XXS engagement to $100,000 for a 280-hour XXL programme, contingent on proof of execution.
- CSP incentive on subsequent licences: This is generated from the Copilot revenue that the business case paves the way for, from the transition from trial to paid (T1) through to wave 2 expansion (X1). This incentive increases as agent usage and Copilot Credits accumulate.
- Ongoing managed and professional services: This recurring connection, as discussed in After the Readout, represents the bulk of sustained revenue.
| Item | XXS | XS | S | M | L/XL | XXL |
|---|---|---|---|---|---|---|
| Minimum customer seats | 300+ | 500+ | 1,000+ | 1,500+ | 3,000+ / 5,000+ | 10,000+ |
| Engagement hours | 10 | 20 | 40 | 100 | 150 | 280 |
| Post-delivery outcomes: Copilot rev (K) | Agent consumption (K) | Agent MAU | 10 | 6 | 300 | 25 | 15 | 500 | 50 | 30 | 1,000 | 125 | 75 | 1,500 | 250/375 | 150/225 | 3,000/5,000 | 500 | 300 | 10,000 |
| MCI engagement incentive (K) | $2K | $5K | $10K | $25K | $50K / $75K | $100K |
| CSP incentive on Copilot revenue (K)† | $1.95K | $4.88K | $9.75K | $24.38K | $48.75K / $73.13K | $97.5K |
† The CSP incentive is displayed as a blended 19.5% of the Copilot revenue outcome (direct billing 2.5 + 7 + 10; indirect reseller 7 + 12.5). These are estimates from the offer plan — please confirm the current MCI payouts, CSP rates, and eligibility requirements in the Microsoft Commercial Partner Incentives Guide.
Now consider the potential scope. Everything outlined so far reflects the dynamics of a single customer. By securing the offer, you can implement it across all qualifying customers in your area — and identifying these clients needn’t be guesswork. Partner Center’s growth insights reporting, accessible via the AI Business Solutions & Security Insights (ASPX) dashboard, can provide you detailed account-level information about Copilot eligibility, seat gaps, E7 opportunities, data security maturity, MCI eligibility, and potential earnings from your existing customer base.
The engagement offer progresses through three consecutive layers:
- Sizing & value: Engagements are available in six sizes, from XXS (10 hrs) to XXL (280 hrs). Hours increase alongside the number of participants, and value is measured via the client’s own metrics.
- Five phases: The engagement unfolds into Assess (A1–A4), Inspire (I1–I5), Design (D1–D6), POC (P1–P7), and Executive Summary (E1, T1, T2, X1). Each phase yields concrete outputs visible to the client.
- Proof of execution: This includes readiness findings and assessments, a solid business case and value plan alongside usage-based billing and Copilot Credits; clear technical requirements and remediation strategy; a well-defined adoption roadmap; a functioning POC with evaluable results; and an executive summary outlining the next steps and implications for consumption — leading towards a named wave 2 expansion beyond the pilot group.
Particular activities – such as security and governance (I2), adoption and change (I3), remediation plan (D2), technical requisites (D3), adoption roadmap (D4), IT access and environment preparation (P3), POC solution development (P5), user training (P6), trial-to-paid transitions (T1), commercial proposals (T2), and the wave 2 expansion strategy (X1) – signal when the engagement transitions from a project to an ongoing collaborative relationship, necessitating managed services, continuous optimisation, and additional professional services post-engagement.
Ultimately, the executive summary marks the beginning of a true collaboration. Ensure these services are part of your offer. Each offering is detailed in partner days, allowing you to price them, and each links to a result your client’s sponsor will easily understand without the need for jargon:
| Managed service | Partner activity — what you deliver and measure | Customer business outcome — what it drives (illustrative targets, for a 1,500-seat customer) |
|---|---|---|
| Deployment and remediation delivery |
• Effort: 5–10 days per wave • Activity: Close all items outlined in the remediation plan and technical requirements (D2, D3) with assigned dates, then license and activate the users for that wave as per the roadmap timeline. • Reported as: Items completed on time; activated seats; duration from readout to go-live. |
• Wave 1 operational within 30 days of the readout, not 90 — gaining extra months of value for each seat. • ≥95% of paid seats assigned and operational; 75 inactive seats might waste approximately $27K annually. • Roll-out delivered within ±5% of the business-case budget. |
| Security and governance management |
• Effort: 2 days per month • Activity: Maintain baseline admin settings and data-protection protocols, review permissions and access dependencies, authorise plugins via the plugin registry, and implement governance controls for apps hosted on Copilot Managed Runtime, acting on every Admin Settings Recommendation. • Reported as: Enabled recommended settings; findings addressed; agents, plugins, and apps with assigned ownership. |
• Zero incidents of oversharing related to Copilot; one enterprise data breach can average over $4M. • 100% of recommended settings active; issues resolved within 30 days. • Audit evidence available in hours, not weeks — achieving Advanced-Healthy Data Security Maturity. |
| Adoption and change management |
• Effort: 3–4 days per month • Activity: Execute the adoption roadmap (D4): train champions, provide role-specific training, refresh use cases, and host monthly Copilot Analytics business reviews. • Reported as: Active user percentage of assigned seats; number of individuals trained; re-engagement of low-activity users. |
• ≥80% of designated seats actively used every month. • 2–4 hours saved per user weekly (equating to 3,000–6,000 hours across 1,500 seats). • Approximately $0.5–1M monthly of staff hours freed up, assuming a $40/hour rate. |
| Agent and solution build-out |
• Effort: 5–15 days per agent or solution, plus half a day monthly for adjustments • Activity: Transition each POC agent (P5) into production using Copilot Studio and Agent 365; rollout new Copilot Studio agents, Code-based applications, and Autopilot agents from the backlog, hosted on Copilot Managed Runtime. • Reported as: Active agents and applications; user engagement each agent; tasks completed; Copilot Credits used per concluded task. |
• 20–40% deflection of tier-1 tickets or cases driven by automated processes. • Cycle times decreased by 30–50% for each agent-run workflow; estimated monthly savings of 200–500 hours per agent. • Cost per completed task continually tracked and decreasing quarter over quarter. |
| FinOps for AI: consumption and license management |
• Effort: 1-2 days per month • Activity: Monitor usage of Copilot Credits and consumption-based billing for Cowork, Code, and Autopilot; set budgets and policies per user group; manage credit requests through the customer’s approval process; forecast expenses and synchronise seat additions, renewals, and terms with each wave. • Reported as: Variance between forecast and actuals; credits per active user; expenditure per business result; new seats added; timely renewals. |
• AI expenditure within ±10% of forecasts — avoiding unexpected overspending. • Zero inactive seats at renewal time; 100% completed renewals as scheduled. • Costs per outcome decreasing by 10–20% annually as usage matures. |
| Quarterly value reviews |
• Effort: 2 days per quarter • Activity: Update the business case (D1) using actuals, gather proof points in the client’s own language, and agree on the timeline for the next slated expansion wave with the executive sponsor. • Reported as: Realised versus projected value; documented proof points; scheduling of the next wave. |
• ROI in financial terms: approximately $125K annually for Copilot seats versus $6M+ in value from time saved. • At least three quantified proof points expressed in the sponsor’s terminology each quarter. • Each review establishes scheduling for the next wave: +100–300 seats or +1–2 agents quarterly. |
The aforementioned effort is indicative for an M-tier client (1,500+ seats) and adjusts based on the number of seats and agents involved, remaining consistent with the engagement hours above. After adding together these recurring tasks, a single M-tier customer with three active agents likely maintains around 9–10 partner days per month post-readout, excluding the time spent on subsequent wave deployments and new agent or solution developments. Each task aligns an item for which you can bill with an outcome valued by the customer, transitioning a recurring service into a long-lasting one while reinforcing your role as their partner in AI transformation as their needs evolve.
These services are not one-time projects; they represent ongoing, outcome-based offerings that position you as a continual partner in your customer’s AI transformation journey.
- Review the engagement guidelines in the Microsoft Commercial Partner Incentives Guide and download the delivery guide along with pre-engagement resources.
- Verify your qualifications for Microsoft Commercial Incentives engagements in Partner Center and ensure alignment among your delivery team regarding the five-phase framework.
- Publish your offer in Partner Center as a professional service (Envisioning & POC) together with a managed service follow-up (deployment, adoption, and optimisation).
- Select your inaugural cohort: Focus on customers with 300+ Microsoft 365 seats who may not yet have a distinct Copilot or agent roadmap, then size each according to its respective tier.
- Schedule the executive readout prior to the Assess phase: Ensuring the transition from trial to paid licenses and following up with proposals and wave 2 discussions is already arranged.
Your potential customers are already in your portfolio. Publish the offer and initiate the discussion.
Share this content:
Discover more from Qureshi
Subscribe to get the latest posts sent to your email.