Purpose
The source announces that IDC brought IDC Quanta, its AI-powered technology intelligence platform, into
Claude as an MCP connector, and that IDC adopted Claude across its own business. Customers describe the
market, strategy, or purchase they are working on, and Claude returns finished analysis built on IDC's
forecasts, market data, and research. This skill turns the post's scenarios into repeatable request
patterns. Anything beyond what the post states is left to IDC's documentation (see the original).
When to use
- You need a competitor brief, a vendor shortlist, a market size, or a benchmark and have IDC Quanta access.
- You want to compare your own numbers (for example next year's IT budget) to IDC's forecast.
- You need to assess what a competitor's acquisition means for your business.
- You lead a research or data company and want a blueprint for adopting Claude across teams.
Instructions
- Connect. IDC Quanta customers add the IDC Quanta connector from within Claude. Others contact IDC or
book a demo (link in the post). It works wherever the customer already uses Claude: the desktop and mobile
app, Cowork, and the Microsoft Office add-ins.
- Describe the job, not the report. State the role, the market or purchase, and the decision you face.
Pick a request pattern from templates/request-prompts.md.
- Add your context. For a shortlist, include your existing architecture and business requirements.
For a benchmark, upload your own figures; the post says uploaded data stays private to the customer.
- Ask for a usable format. Request the deliverable you will act on, such as an Excel scorecard for an
evaluation team or an executive-ready brief.
- Check citations. Each answer should cite the IDC document or dataset it came from. Because Claude uses
the same data and definitions as an IDC analyst, market share and growth figures should match what IDC
would publish; flag anything uncited.
- Review before you decide. Treat the output as a fast first analysis that people review before acting.
- Rolling Claude out internally? Follow IDC's sequence in
references/internal-adoption.md: start with engineering, then extend
to product, planning, sales, and marketing.
Examples
Competitive brief
A corporate strategy lead asks for a brief on a competitor. Claude returns positioning, market share,
product capabilities, and recent acquisitions, cited to IDC research - minutes instead of a day.
Vendor shortlist
A CIO describes the current architecture and requirements for procurement software. Claude returns the top
three vendors based on IDC's procurement database and MarketScape research as an Excel scorecard.
Budget versus forecast
A CFO uploads next year's IT budget and asks how it compares to IDC's forecast. Claude shows where and by
how much the two differ.
More role-based scenarios: examples/role-scenarios.md.
1---2name: idc-quanta-research-workflows3description: Answer market and technology questions in Claude through the IDC Quanta MCP connector, following the October 2026 IDC announcement - competitive briefs, vendor shortlists delivered as Excel scorecards, comparing your own budget to IDC forecasts, and acquisition-impact analysis, each cited to the IDC document or dataset it came from. Also covers how IDC rolled Claude out internally (Claude Code for prototypes, parallel tests, and reviews; Cowork for plan drafts; CRM-export deal triage; a marketing content assistant). Use when a customer with IDC Quanta wants finished analysis instead of reading long reports, or when a research firm plans a company-wide Claude rollout.4metadata:5 source: https://skillmd.com/skills/uygnoey/idc-quanta-research-workflows6---78## Purpose9The source announces that IDC brought IDC Quanta, its AI-powered technology intelligence platform, into10Claude as an MCP connector, and that IDC adopted Claude across its own business. Customers describe the11market, strategy, or purchase they are working on, and Claude returns finished analysis built on IDC's12forecasts, market data, and research. This skill turns the post's scenarios into repeatable request13patterns. Anything beyond what the post states is left to IDC's documentation (see the original).1415## When to use16- You need a competitor brief, a vendor shortlist, a market size, or a benchmark and have IDC Quanta access.17- You want to compare your own numbers (for example next year's IT budget) to IDC's forecast.18- You need to assess what a competitor's acquisition means for your business.19- You lead a research or data company and want a blueprint for adopting Claude across teams.2021## Instructions22231. **Connect.** IDC Quanta customers add the IDC Quanta connector from within Claude. Others contact IDC or24 book a demo (link in the post). It works wherever the customer already uses Claude: the desktop and mobile25 app, Cowork, and the Microsoft Office add-ins.262. **Describe the job, not the report.** State the role, the market or purchase, and the decision you face.27 Pick a request pattern from [templates/request-prompts.md](templates/request-prompts.md).283. **Add your context.** For a shortlist, include your existing architecture and business requirements.29 For a benchmark, upload your own figures; the post says uploaded data stays private to the customer.304. **Ask for a usable format.** Request the deliverable you will act on, such as an Excel scorecard for an31 evaluation team or an executive-ready brief.325. **Check citations.** Each answer should cite the IDC document or dataset it came from. Because Claude uses33 the same data and definitions as an IDC analyst, market share and growth figures should match what IDC34 would publish; flag anything uncited.356. **Review before you decide.** Treat the output as a fast first analysis that people review before acting.367. **Rolling Claude out internally?** Follow IDC's sequence in37 [references/internal-adoption.md](references/internal-adoption.md): start with engineering, then extend38 to product, planning, sales, and marketing.3940## Examples4142**Competitive brief**43> A corporate strategy lead asks for a brief on a competitor. Claude returns positioning, market share,44> product capabilities, and recent acquisitions, cited to IDC research - minutes instead of a day.4546**Vendor shortlist**47> A CIO describes the current architecture and requirements for procurement software. Claude returns the top48> three vendors based on IDC's procurement database and MarketScape research as an Excel scorecard.4950**Budget versus forecast**51> A CFO uploads next year's IT budget and asks how it compares to IDC's forecast. Claude shows where and by52> how much the two differ.5354More role-based scenarios: [examples/role-scenarios.md](examples/role-scenarios.md).