Dux Raymond Sy writes and speaks about practical AI governance, leadership, cybersecurity, and helping managed service providers prepare customers to use AI. Sy's posts discuss controlling AI agents, managing costs and data access, and turning governance into an ongoing service.
Dux Raymond Sy is most useful for practical AI governance, cybersecurity, and MSP readiness conversations.
Best for
AI governance campaigns for MSP owners and channel partners in Australia and APAC.
Not for
Developer-tools or platform campaigns needing hands-on implementation tutorials and developer sign-ups.
Key takeaways
Control matters more than how quickly an organization adopts AI.
For MSPs, AI governance can be an ongoing service rather than a one-off project.
A device-code phishing rule: if you did not start the sign-in request, do not finish it.
Check first: Confirm media kit, rate card, sponsorship terms, booking route, and audience measurement.
Main ideas
Control matters more than how quickly an organization adopts AI · For MSPs, AI governance can be an ongoing service rather than a one-off project · Teach security through the steps of a realistic scenario, not just a warning
Dux Raymond Sy writes and speaks about AI governance, cybersecurity, leadership, and the practical challenges facing managed service providers (MSPs).
Their posts focus especially on what organizations need to control before AI agents are widely used: spending, data access, security, and accountability.
Sy also appears in posts about the #shifthappens podcast and The Right of Boom CyberCall.
Follow their work for concrete examples of how AI and security decisions play out in organizations, not just product announcements.
Sy often opens with a situation readers can picture, explains the operational risk, then ends with a practical question or action.
In one post, a CFO trusts AI-generated board decks while the security team has not cleared the same tool to handle financial data; Sy uses the contrast to distinguish trust in an AI answer from trust in the system behind it.
In another, they walk through device-code phishing step by step and offer a memorable rule: if you did not start the sign-in request, do not finish it.
For MSP readers, Sy connects AI governance to repeatable work across customer tenants and an ongoing service, using market figures and event-room examples to make the business case.
Their posts also show a quieter interview style: a conversation with a former CIO becomes a reflection on the pressure to rush into a new role.
The range—from security walkthroughs and governance arguments to leadership conversations—is a reason to follow Sy's work.
Dux Raymond Sy’s posts return to a practical idea: AI adoption is not the same as being in control of AI.
Read more
They argue for deliberate governance covering data, access, agent behavior and cost, and treat that work as an ongoing responsibility, especially for managed service providers. Sy makes the case through concrete scenarios, audience questions and market examples rather than abstract predictions.
Control matters more than how quickly an organization adopts AI
Sy argues that a polished rollout or confidence in AI does not prove an organization can manage what its systems do.
Read more
They distinguish trust in an AI answer from trust in the system behind it, and urge teams to check whether trust rests on verification or convenience. The advice favors deliberate preparation over moving fastest.
Sy contrasts a CFO’s confidence in AI-drafted board decks with a security team’s unresolved review of whether the same tool should access financial data. They also recommend setting tenant-level spending limits before enabling Copilot Cowork, whose usage-based costs can vary by task.
For MSPs, AI governance can be an ongoing service rather than a one-off project
Sy frames the managed service provider opportunity as helping customers protect data, manage access and govern AI agents—not simply sell AI tools.
Read more
Customers need governance as their AI use continues, and providers can make that work repeatable across the tenants they manage.
In posts about Australian and Philippine partner events, Sy points to a reported gap between MSPs intending to invest in AI readiness and those saying they have reached that maturity. They describe repeatable governance across customer tenants as the practical challenge, and present ongoing service as an alternative to rebuilding the work for each customer.
Teach security through the steps of a realistic scenario, not just a warning
Sy makes security advice concrete by showing how an attack can succeed even when familiar safeguards appear to work.
Read more
The lesson is to question the reason for an authentication prompt, not just whether a sign-in page looks genuine.
In a device-code phishing walkthrough, an employee follows an invoice link to the real Microsoft sign-in page, enters a code and completes MFA—thereby authenticating the attacker’s session. Sy’s rule: if you did not start it, do not finish it; report unexpected codes or approval requests.
A leadership pause can be a considered choice, not a sign of being stuck
In a podcast post, Sy uses a guest’s reflection to question the pressure to have the next role lined up immediately.
Read more
The point comes through the interview; it is not the guest’s advice attributed to Sy.
Giovanni Piccirilli, described in the post as having recently stepped away from being CIO, said he wanted time to absorb and enjoy what came next. Sy contrasts that with the tendency to rush toward a new title to avoid appearing stalled.
This example offers a more personal, reflective register than the posts about AI governance and security.
Open with this post to see how Dux Raymond Sy turns a product launch into a practical decision.
Read more
It answers the question IT admins were asking and lays out the numbers behind it.
Dux Raymond Sy opens with the question Sy's phone was fielding after Copilot Cowork went generally available: should we turn it on?
Sy's answer is not yet, and the rest of the post explains why.
Cowork is not Copilot suggesting your next sentence, Sy writes, but an agent that gathers context, uses tools, generates deliverables and keeps running after you move on.
That switches the billing model to usage: $0.01 per Copilot Credit, roughly $0.50–$1.50 for a quick email summary, $5–$8 for a research report pulling from SharePoint, and $20–$35 for a multi-step research, analysis, deck and emails project.
Sy estimates one heavy daily user at $400–$700 a month on top of an existing $30 licence, and a 50-person team doing moderate complex work at $5,000–$15,000 a month, and notes that at the time of writing users could not see cost before running a task.
The single move Sy recommends before enabling anything is setting tenant-level spending limits in the M365 admin center.
For brands planning a campaign
A vendor or consultancy selling agentic AI, cost governance or Copilot deployment could build a checklist, calculator or webinar around the pre-enable controls. The price ranges make the risk concrete enough to anchor a session.
This is the clearest statement of the distinction running through Sy’s other posts, and shows how they build an argument from one story and two data points.
Read more
The post turns on a story about a CFO whose team now drafts board decks with an AI tool in minutes and who trusts it completely for that, while her security team has spent six months reviewing whether the same tool can touch financial data, with no answer.
Trusting the output completely while not trusting the system behind it, Sy writes, can both be true for the same person in the same week.
They set that against a 2026 Writer survey finding 80% of Gen Z employees trust AI more than their manager on certain tasks, and their own organisation’s State of AI 2026 report finding 88.4% of organisations had an AI agent breach in the past year despite feeling confident going in.
These are not contradictory findings, Sy argues, but answers to two different questions: whether you trust what the AI just told you, and whether you trust the system that produced it.
Confidence is not the problem; control is.
Sy closes with an assignment: pick one AI decision your team makes daily and decide whether it is trusted because it has been verified or because it is convenient.
For brands planning a campaign
The verified-versus-convenient question could anchor a webinar, assessment tool or newsletter prompt, while the breach statistic gives sponsors a defensible hook for governance content.
Different subject, same teaching method: one scenario walked through step by step, then a rule short enough to remember.
Read more
It shows how Sy speaks on stage or to a security audience.
Dux Raymond Sy describes a device-code phishing scenario from an appearance on The Right of Boom CyberCall.
An employee receives an invoice email, follows the link to the real Microsoft sign-in page, enters a code and completes MFA — and has authenticated the attacker’s session, all while every visible signal looked legitimate.
The sign-in page was real, MFA worked, and the attacker still got in.
For security leaders and managed service providers, Sy says, training needs to go beyond checking the URL.
People also need to ask why they are being prompted to sign in and whether they started the request.
Their one-line rule: if you didn’t start it, don’t finish it.
Report the unexpected code or approval request.
For brands planning a campaign
A security-awareness or identity vendor could use this scenario as the spine of a training module, phishing simulation debrief or co-branded explainer. The attack succeeds through legitimate steps, not obvious red flags.
This is Sy’s audience pitch in one post: the historical analogy, market numbers and commercial ask, all in the format they use in a live room.
Read more
The post opens with the 1851 Australian gold rush and the point that history remembers the people who built the roads, services and trust that turned a rush into an economy, not the people who chased the gold.
Dux Raymond Sy told that story in Sydney and Melbourne and says both rooms reached the same conclusion: managed service providers are in that moment with AI.
They bring market data — Australian IT spending at $172.3 billion this year, up 8.9%, with the fastest growth in categories most MSPs do not own, 94% intending to get AI governance right against 43% who have done it, and a compliance deadline on December 10 that, Sy says, almost none of their customers know about yet.
The opportunity, they argue, is not selling AI but helping customers protect data, secure access and govern the agents already running in the business — a recurring revenue relationship rather than a project.
Sy points readers to AvePoint Elements and asks which of the three conversations — data, infrastructure or agents — is easiest to start.
For brands planning a campaign
A vendor or agency targeting the Australian MSP market could build an event, deadline-driven campaign or co-branded asset around the December compliance date, using the same story-plus-numbers structure.
Where the gold rush post gives the argument, this one lays out the operating model for MSPs, built on a named study.
Read more
Read them together.
Dux Raymond Sy cites a global Omdia study of 333 MSPs: 94% say they are investing in automation to get customers AI-ready, and only 43% say they have reached that maturity.
They saw the same gap in a room with Crayon Philippines, a SoftwareOne company: the partners were not short on AI ambition but lacked a repeatable way to deliver governance across every customer tenant without rebuilding it by hand each time.
The pitch was AvePoint Elements, presented as a way to manage AI-readiness and compliance across multiple customers at once.
What made the room lean in, Sy writes, was not the tool but the model underneath: governance and compliance packaged as an ongoing service instead of a one-time project, starting the month Copilot is deployed.
Sy names five people from Crayon in the thank-you line and asks readers which side of the 94-43 split they are on.
For brands planning a campaign
The 94-versus-43 split offers a usable benchmark for channel-facing content, while the service-versus-project argument could anchor a webinar on recurring AI governance revenue.
This shows how Sy adapts the governance message for a regulated regional audience and positions an event around named speakers and customers.
Read more
The post argues that an AI rollout that looks good in a board deck remains untested until an agent does something nobody planned for — and until the organisation can show a regulator it was in control the whole time.
In Europe, Dux Raymond Sy writes, the EU AI Act already expects an answer, whether or not an organisation has worked one out.
That frames the #shifthappens executive summit EMEA, where Sy will speak alongside AvePoint colleagues Dana Simberkoff, Chief Risk, Privacy and Information Security Officer; Timothy Boettcher, SVP of GTM Strategy; and CTO John Peluso, with customer speakers from Arup and ABELLIO Greater Anglia discussing what scaling AI inside a European enterprise looks like.
Dates and cities are The Hague on 6 October, London on 8 October and Paris on 5 November.
The post closes with a registration link.
For brands planning a campaign
An event organiser or content partner could join a regional summit series or use the pairing of vendor executives with named customer speakers as a format for a governance session.
The governance posts show the practitioner; this one shows the interviewer.
Read more
It is the best available sense of what a podcast or fireside collaboration with Sy would feel like.
Dux Raymond Sy describes a moment a few minutes before recording a #shifthappens podcast interview with Giovanni Piccirilli, who had just stepped away from being a CIO.
Asked off the record what comes next, Piccirilli said he wanted the time to let things happen on him, to absorb and enjoy.
They contrast that with the usual habit of lining up a new title before the old one is closed out, mostly so nobody thinks you stalled, and note that Piccirilli is not stalled — just not in a hurry.
The post ends with a question to readers: would you actually let yourself take that kind of pause, or does the pressure to have an answer kick in too fast.
For brands planning a campaign
A good fit for a podcast, interview series or live conversation that calls for a thoughtful guest rather than a product talk. The closing-question style also offers a repeatable way to engage an audience.
Field events, executive summits, and podcast interviews as working formats5
AI governance as a recurring MSP service, not a project2
Leadership pacing: deliberate, not fast2
Control costs before turning agentic AI on1
Trust in the AI answer versus trust in the system behind it1
Identity security taught through one live attack scenario1
AI governance as a recurring MSP service, not a project
Across field-event posts, Dux Raymond Sy returns to one argument: the MSP opportunity in AI is not selling AI but making data protection, access control, and agent governance a recurring service.
Read more
The pitch comes with a gap statistic — 94% of MSPs say they are investing in automation to get customers AI-ready, while 43% say they have reached that maturity — and the claim that governance starts the month a customer deploys Copilot and does not end there. A December 10 compliance deadline that almost none of their customers know about yet supplies urgency, while a question from the room asks where liability sits once an agent goes live.
Open with an event-room anecdote, bring in a third-party study figure, draw out the commercial takeaway, then close with a question for the reader.
One post names the Omdia study of 333 MSPs, while the other uses the same 94/43 numbers without attribution. Cite the study when reusing the figures.
For brands planning a campaign
Build a webinar around the 94/43 gap: a first-90-days plan for packaging governance as a billable recurring line, with the compliance deadline as the reason to act now.
On the Copilot Cowork general-availability announcement, the answer is "not yet" until buyers understand what they are purchasing.
Read more
The post works through usage-based billing at $0.01 per Copilot Credit, with examples ranging from $0.50-$1.50 for a quick email summary to $5-$8 for a SharePoint research report and $20-$35 for a multi-step project.
It estimates $400-$700 a month for one heavy user on top of an existing $30 licence, or $5,000-$15,000 a month for a team of 50 working moderately.
Because users cannot see cost before running a task until July, the recommendation is to set tenant-level spending limits in the M365 admin center before a single user runs anything.
Start with a question the audience is already asking, answer with a flat no, then unpack the billing model with worked numbers and one pre-launch control.
For brands planning a campaign
The worked cost ranges and single pre-launch control give a webinar a ready-made demo segment on governing agent spend, for finance and admin audiences as well as technical staff.
Trust in the AI answer versus trust in the system behind it
Dux Raymond Sy separates two questions that often get blended: do you trust what the AI just told you, and do you trust the system that produced it?
Read more
A CFO anecdote carries the point: a team drafts board decks with a tool trusted completely for that task, while the same tool is six months into a security review with no answer on touching financial data.
Two studies sit side by side: a 2026 Writer survey finding 80% of Gen Z employees trust AI more than their own manager on certain tasks, and a State of AI 2026 finding that 88.4% of organizations had an AI agent breach in the past year despite feeling confident going in.
The close is a piece of homework: pick one AI decision the team makes daily and ask whether it is trusted because it has been verified or because it is convenient.
For brands planning a campaign
This framing makes a strong opening for a governance session: it shifts the discussion from adoption enthusiasm to verification and control, then ends with an activity attendees can run before the next meeting.
Identity security taught through one live attack scenario
A device-code phishing walkthrough carries the security lesson: an employee receives an invoice email, follows the link to a real Microsoft sign-in page, enters a code, and completes MFA — authenticating the attacker's session.
Read more
The takeaway for security leaders and MSPs: checking the URL is only one step; people also need to ask why they are being prompted to sign in and whether they started the request. It closes with a rule short enough to train on: if you did not start it, do not finish it, and report the unexpected code or approval request.
Walk through a scenario presented on a cyber call, then deliver a single memorable rule.
The post teaches a security point without an event, registration link, or product mention.
For brands planning a campaign
This works as a self-contained training segment in a webinar or content collaboration, turning an incident pattern into an instruction staff can repeat.
A podcast interview with Giovanni Piccirilli, recorded shortly after he stepped away from being CIO, turns on one quiet answer about giving himself time to let things happen rather than lining up the next title.
Read more
The same posture runs through the AI writing: the organizations that win with agentic AI will not move fastest; they will move most deliberately.
For brands planning a campaign
The human, non-product register suits an interview-style webinar or podcast collaboration. The argument about deliberate pacing speaks directly to CIO and CISO audiences weighing a pause against pressure to ship.
Field events, executive summits, and podcast interviews as working formats
Most posts center on live rooms: partner sessions in Sydney and Melbourne; a shifthappens executive summit EMEA running The Hague on October 6, London on October 8, and Paris on November 5; a Manila partner session with Crayon Philippines; a cyber call; and a podcast interview.
Read more
The summit post names colleagues and outside speakers and points to EU AI Act expectations as the reason the conversation matters now. Posts typically credit partners by name and close with a registration or learn-more link.
Use a recap-and-invite structure: what the room agreed on, who was there, where the next session is, and a link.
Before booking, ask whether these appearances have a sponsorship format, rate card, or audience-size claim; Dux Raymond Sy's posts do not specify.
For brands planning a campaign
A webinar or hosted conversation matches an established format and a habit of promoting it with named guests and a registration link. Expect the deliverable to be framed as a live discussion rather than a written asset.
Dux Raymond Sy's posts place Sy inside AvePoint: Sy calls AvePoint colleagues "my" colleagues, refers to "our CTO," and cites an AvePoint research report as "our own."
Read more
Microsoft Copilot and Microsoft 365 are recurring subjects with no stated commercial tie, and Sy also appears in a partner event and a security program that readers assessing Sy may want to know about. The posts contain no sponsorship or affiliate disclosures.
AvePoint
Employment
Sy refers to AvePoint staff as "my AvePoint colleagues," names "our CTO John Peluso," and cites "our own State of AI 2026 report" — language that places them inside the company.
Read more
They also promote AvePoint Elements for MSPs and take part in AvePoint's shifthappens executive summits and podcast. Ask what their job title is and what the role entails.
Copilot, Copilot Cowork, and the Microsoft 365 admin center recur in Sy's posts, including per-task pricing figures for Cowork and a device-code phishing scenario run against a genuine Microsoft sign-in page.
Read more
The coverage offers commentary and advice to MSP and IT audiences. Ask whether Sy has a sponsorship, partner, or client relationship with Microsoft.
Sy describes presenting AvePoint Elements to partners in a room credited to Crayon Philippines (a SoftwareOne company) and thanks named Crayon staff for building it.
Read more
Ask what relationship, if any, they have with Crayon or SoftwareOne beyond the event.
Sy walked through a device-code phishing scenario as a participant on this security program, using it to argue that checking a URL is not enough and that people should question why they are being asked to sign in.
Read more
Ask whether they have a commercial relationship with the program.
Dux Raymond Sy's posts track AI governance as it moves from slideware into managed service contracts.
Read more
The through-line is simple: adopting an AI tool is not the same as controlling it, and customers will pay for control.
Start with the post on Copilot Cowork's general availability for the clearest example.
It breaks down usage-based credit costs ($0.01 per Copilot Credit, with tasks priced from roughly $0.50 for an email summary to $20–$35 for a multi-step project) and argues for setting tenant-level spending limits before anyone runs a task.
Next, read the posts from Sydney and Melbourne and the Philippine partner-event posts for the MSP case: 94% of MSPs are investing in AI readiness, against 43% who say they have reached it, and governance can be packaged as a recurring service across the tenants a provider already manages.
The device-code phishing walkthrough is the shortest self-contained lesson: one scenario from start to finish, followed by a rule short enough to repeat.
The Europe summit post and the CFO anecdote draw out a distinction Sy returns to: confidence in an AI answer versus confidence in the system behind it.
For a different register, the podcast post about a CIO's deliberate pause after leaving a role sits alongside the argument running through the AI writing: organizations that win with agentic AI will move most deliberately.
Both write practitioner-level LinkedIn posts about putting Microsoft 365 and Copilot to work inside organizations.
Read more
Both argue that governance and adoption structure—not licence count—determine whether the investment pays off.
Willinger's governance material centers on a single named client case study, with a phase-by-phase AI Center of Excellence framework and measured results: proposal creation time down 28%, executive prep down 35%, and 14 workflows automated. Sy takes a market-level approach, addressing MSPs across multiple customer tenants and mixing event recaps with security teaching.
Both write for MSP owners and account teams about turning a support relationship into a strategic one.
Read more
Collins' quarterly business review framework brings security posture, roadmap progress and quantified risk into the same buyer conversation where Sy argues governance belongs.
Collins teaches account-management mechanics—a standardised QBR deck, the metrics to report and the recommendations to close on—without centring AI governance.
His other post here is a personal reflection on a sales-career rejection, rather than client-facing advice.
Sy focuses on the AI and agent governance service line itself.
Both are Microsoft-ecosystem voices writing for channel and partner audiences, covering co-sell, partner programmes and how Microsoft product shifts affect MSPs and the partners around them.
Read more
O'Donnell's posts centre on partner alliances and go-to-market moves—Dynamics 365 Activate in a heavily hashtagged partner brief, and a new role leading strategic alliances.
They read as announcements and ecosystem signposting.
Sy's posts teach governance practice through worked examples, event takeaways and questions for readers.
Placement read: Dux Raymond Sy's posts show subject-matter appeal to the MSP and channel audience an AI-governance campaign would want.
Read more
The one hard number available is a LinkedIn follower count of about 19,140, observed on 8 October 2026.
Their posts do not say how those followers break down by geography, company type, seniority, or job function, and there is no engagement rate, comment volume, or event registration data.
Treat the count as reach, not a verified audience profile.
The material addresses MSP owners and channel partners directly: a Sydney and Melbourne partner briefing, a Philippines channel session with Crayon, and a 94%-versus-43% MSP automation gap drawn from an Omdia study of 333 MSPs.
It also speaks to CIOs, CISOs, finance leaders, and security practitioners: an EMEA executive summit in The Hague, London, and Paris; a CFO whose team drafts board decks with AI while security still blocks the same tool; and a device-code phishing walkthrough on a cyber call.
Post dates run from 17 June to 29 September 2026, offering a current picture of the material rather than a long-run history of who has followed it.
For an AI-governance campaign, ask Dux or the account's representative for a LinkedIn follower breakdown (company size or industry where available) or a recent audience survey, plus results from a comparable AI-governance session, such as registrations, attendance, and which partner types turned up.
If the campaign needs verified job function, employer type, or seniority, ask for an MSP-specific registration list or survey; a platform demographic breakdown would not settle it.
Dux Raymond Sy's posts show how they work with vendors and event organisers, rather than describing a sponsorship programme.
Read more
The clearest pattern is vendor-hosted events: the shifthappens executive summit series in The Hague (6 October), London (8 October) and Paris (5 November) is an AvePoint event, with Sy listed as a speaker alongside AvePoint colleagues and customer speakers from Arup and Abellio Greater Anglia.
A Manila session with partner Crayon Philippines (a SoftwareOne company) was built around a walkthrough of AvePoint Elements for MSPs, with the commercial pitch stated plainly in the post.
A Sydney and Melbourne partner tour closes with the same product recommendation.
Two other appearances are editorial rather than commercial: a shifthappens podcast interview with a CIO who had just left the role, and a device-code phishing walkthrough on The Right of Boom CyberCall.
For a buyer, these are vendor and partner collaborations run through established relationships, not a packaged offer.
The posts include no media kit, rate card, sponsorship terms, deliverable list or booking route.
Ask Sy directly about scope, deliverables and fees.
A campaign aimed at MSP owners and channel partners in Australia and APAC: an enterprise software vendor that sells AI governance, data protection, or Microsoft 365 controls wants a named voice to front a 45-minute webinar plus one written follow-up on turning AI governance and agent readiness into a recurring billable service rather than a one-off project.
Read more
Why this fits.
The posts speak directly to this audience and decision.
The Sydney and Melbourne partner briefing and the Manila session with Crayon Philippines (a SoftwareOne company) make the same argument to MSPs: the opportunity is not selling AI, but making data protection, access control, and agent governance a recurring service from the month a customer deploys Copilot.
The narrative spine is ready-made: the 94% versus 43% Omdia gap, the market-spending figures, and the compliance deadline the post names as 10 December.
The formats are demonstrated: hosted partner sessions, a multi-city executive summit, a cyber call, and a podcast interview, all promoted with named guests and a registration link.
They also close posts with a direct question to readers, a useful way to drive webinar questions and follow-up replies.
Before booking, ask for the media kit, rate card, sponsorship terms, booking route, and audience measurement.
Agree scope, deliverables, and fees directly, and collect registration, attendance, and partner-type data in the first session to inform the next one.
When to choose a specialist
A developer-tools or platform company seeking an always-on series of hands-on implementation tutorials—code walkthroughs, repository-linked labs, benchmark comparisons, and a high volume of short-form video creative—measured on developer sign-ups and cost per acquisition.
Read more
Why this is a weak match.
The posts operate one level above implementation.
They frame decisions for IT, security, finance, and channel leaders: why Copilot Cowork pricing changes the enablement conversation, why trust in an AI answer is not trust in the system behind it, and why an AI rollout that looks good in a board deck remains untested until an agent does something nobody planned for.
The closest thing to technical instruction is a device-code phishing scenario, taught as a rule a security leader can train on—“if you didn't start it, don't finish it”—rather than as a reproducible lab.
The posts include no code, repository, environment setup, benchmark table, or step-by-step build.
The formats point the same way: live rooms, a summit, a cyber call, and a podcast interview, with a written recap and registration link.
There is no demonstrated short-form video cadence, paid creative testing, or conversion-linked asset production.
The only hard number published is a LinkedIn follower count of about 19,140; it does not establish audience fit or conversion performance.
For hands-on developer enablement at volume, the demonstrated work does not support the ask.
A stronger fit would be an executive-facing session or written decision aid.
If the buyer still wants a technical series, ask whether they produce build-level content on channels not represented in the posts before committing.
A worked campaign example
For a B2B SaaS vendor assessing Dux Raymond Sy as a speaker or advisor on AI governance for MSPs. Campaign angle: “Agents are already running — the 90-day governance line.” A 45-minute live session plus one written follow-up, co-hosted with an AI governance vendor and promoted to MSP owners and technical leads in Australia.
Why the angle works. It builds on the argument already present in the posts—governance as a recurring service, not a project—and gives it a deadline and a number. The 94% versus 43% Omdia gap sets the problem, the compliance date the posts name as 10 December supplies the reason to act now, and the three lanes they already use with partners—data, infrastructure, agents—give the session its structure.
Session shape, drawn from demonstrated methods: 1. Open with the question the audience is actually asking, using the form of the Copilot Cowork post: “We turned Copilot on — are we covered?” Answer it plainly before explaining anything. 2. Land the gap: 94% of MSPs say they are investing to get customers AI-ready, 43% say they have reached that maturity. Attribute it to the named Omdia study of 333 MSPs rather than repeating the bare figures. 3. Work the cost-control demo, because the numbers are concrete and the audience includes finance and admin staff. Take the published Copilot Cowork ranges—roughly $0.50–$1.50 for a quick email summary, $5–$8 for a SharePoint research report, $20–$35 for a multi-step project, and the estimate of $400–$700 a month for one heavy daily user—and walk through setting tenant-level spending limits in the M365 admin center before anyone runs a task. 4. Use the device-code phishing walkthrough as the security proof point: the sign-in page was real, MFA worked, and the attacker still got in. Close the segment with the rule. 5. Finish with the homework from the trust post: pick one AI decision the team makes daily and decide whether it is trusted because it has been verified or because it is convenient.
Deliverables for the buyer: the live 45-minute session; a short slide set built on the five beats above; a one-page tenant spending-limit checklist attendees can use without the vendor present; one recap post in their existing recap-and-invite style, crediting named partner speakers and carrying the registration link to the next session; and a deadline-reminder email to registrants before 10 December.
Agree fees and deliverables directly; the posts include no rate card or standard sponsorship terms, so do not assume a package. Ask for audience breakdowns and track registrations by partner type, attendance rate, checklist downloads, and how many attendees book a scoping conversation. Treat the first session as a test of whether the audience comprises MSP decision-makers, and request the follow-up numbers before committing to a series.
One campaign-specific gap remains: the posts show event appearances, webinar-style sessions, and a podcast interview, but no documented advisory engagement, retainer, or paid product work. Ask for the proposed advisory scope and any reference engagements.
Choose Jeff Willinger when the webinar needs to walk through an actual governance rollout with numbers attached, rather than make a partner-room case for why governance sells.
Read more
The case study lays out a 90-day phased AI Center of Excellence for a $1.2 billion health and life sciences organisation running 400+ Microsoft 365 Copilot licences: five enterprise use cases tied to revenue and margin, an executive AI charter and steering committee, a data security review of SharePoint and OneDrive permissions, Purview sensitivity label work, a Copilot readiness assessment, an AI usage policy with prompt governance guidelines, role-based workshops and a prompt library embedded in SharePoint, a monthly business and IT alignment cadence, and usage analytics that ended with proposal creation time down 28 percent, executive preparation time down 35 percent, and 14 internal workflows automated.
For the buyer's 45-minute session plus written follow-up, that sequence is a ready-made agenda and a measurable-results story.
It suits the same campaign when the audience is technical or operations-leaning—MSP engineers, security leads, or a customer's IT and compliance staff—and the buyer can supply the MSP service-packaging frame.
A second post shows a long Microsoft-ecosystem career across SharePoint, Microsoft 365, Dynamics, Power Platform, Copilot, cybersecurity, partner co-sell and conference speaking, supporting a broader Microsoft-ecosystem session if the governance angle proves too narrow.
The two posts are an enterprise deployment case study and a career announcement, not channel-facing or service-design content.
Dux Raymond Sy's posts do not cover recruiting MSP partners, packaging governance as a monthly service, pricing that service, or running a partner programme—the spine of a campaign aimed at MSP buyers seeking a governance service.
The case study describes one organisation's internal rollout, not a managed-service offering, so an MSP would need to translate its phased steps into a billable product.
The dense, metric-led register suits IT and finance audiences, but not the owner-operator sales pitch an MSP partner room expects.
Before booking, ask for audience figures, engagement data, session recordings, a fee card and booking terms.
Choose Roger Collins when the buyer's real objective is the recurring client relationship rather than the AI controls inside it.
Read more
The reviewed quarterly business review post gives an MSP account team a complete, reusable structure: a business update covering acquisitions, hiring and how the client is approaching AI; an executive summary with dashboards for security posture, user experience, infrastructure health, backup and recovery, and compliance readiness; a security review that tells a story with data such as 4,219 malicious emails blocked and two users who clicked phishing links where MFA prevented compromise; a service experience review focused on outcomes like average response and resolution times, CSAT and ticket trends; roadmap progress covering what is done, in progress and upcoming, including security awareness training and a cyber insurance assessment; a quantified risk review; and closing recommendations split into immediate, 90-day and 12-month actions.
The stated aim—turning a $3,000-a-month client into a $10,000-a-month strategic account—is the same commercial outcome the buyer's brief is chasing, reached through account management instead of governance tooling.
This alternative fits when the session should teach MSPs how to sell and sustain an ongoing advisory relationship, with AI governance as one agenda item among several.
The governance content is thinner than the campaign needs: AI appears in the QBR framework mainly as a question to pose to a client, not as a control set.
It does not address agent liability, tenant-level AI spend limits, prompt governance or identity attacks—the demonstrations a campaign focused on governance controls and service delivery needs.
The second post is a personal career story about a rejection email, sales performance and persistence; it would suit a sales-culture or motivational session but adds no governance credibility.
A buyer choosing this route would likely pair Roger Collins with a technical co-speaker rather than build the whole session around the QBR material.
Choose John O'Donnell when the audience is Microsoft partner and channel organisations and the decision is about co-sell motion and ecosystem positioning rather than controls.
Read more
The post on Dynamics 365 Activate explains what agentic business applications mean for messy CRM and ERP estates: AI analysing what an organisation has customised, what it actually uses and what is slowing teams down, across scenarios such as migrating from Salesforce, modernising legacy Dynamics, or starting fresh.
It speaks the partner ecosystem's language directly—ISV, SI, MSP, CSP, VAR, marketplace, AppSource, co-sell—and cites a Microsoft Finland story about a rapid ERP deployment in aerospace as a proof point.
The career post documents a move to Bell Techlogix as Director, Strategic Partnership Alliances with a mandate to grow Microsoft and other strategic partnerships, after work with ISVs, global systems integrators and startups at Microsoft and a stint on the Microsoft Copilot Connector product team.
This fits when the buyer wants a session on how a partner should position and co-sell an AI platform with Microsoft, including marketplace and partner-programme vocabulary.
Dux Raymond Sy's posts offer ecosystem context, not the governance delivery detail a campaign about a priced governance service needs: data protection, access control, AI usage policy, compliance deadlines and the recurring-service model.
One post is a job announcement; the other is product and partnership commentary wrapped in a long hashtag block.
For a session where attendees should leave with a governance checklist or priced service model, choose a different speaker.
Ask for the full speaking history and session recordings to assess their audience-facing delivery.
Dux Raymond Sy's seven complete LinkedIn posts cover AI governance, MSP services, agent costs, identity security, leadership, and a podcast interview.
The profile was observed on October 8, 2026, and includes overview, ideas, relationships, discovery, and fit sections.
Post dates are not consistently stated, so the posts do not establish a chronology or shifts over time.
The posts do not include images, videos, comment threads, podcast audio, event recordings, sponsorship terms, a rate card, a media kit, an advisory engagement, or an audience demographic breakdown; the contents of shortened links in the posts are not established here.
The posts do not establish publication dates or any signature books, shows, businesses, or earlier work beyond the events and appearances mentioned.
