William Wacker writes about mainframe modernization, including vendor pricing pressure, shrinking technical talent pools, and how organizations can sequence change without disrupting critical systems.
Most useful for mainframe modernization thought leadership on vendor pricing, talent gaps, and safe sequencing.
Best for
Mainframe advisory firms selling assessments and delivery restructuring to CIOs, CTOs, and procurement leads.
Not for
Sales enablement software seeking recurring short-form video for sales development reps.
Key takeaways
Mainframe talent trouble is a strategy failure, not a shortage to endure.
Vendor pricing has become an architecture decision, not a negotiation.
Sequencing beats speed, because production has to keep running.
Check first: Confirm whether Composer is part of their mainframe work and ask for audience data.
Main ideas
Mainframe talent trouble is a strategy failure, not a shortage to endure · Vendor pricing has become an architecture decision, not a negotiation · Read the tells: job ads and filings reveal buying decisions before they are announced
William Wacker writes about mainframe modernization and enterprise IT.
Their posts examine how vendor pricing pressure, shrinking technical talent pools, and operational demands can force decisions about mainframe systems.
They also discuss delivery models that preserve expertise and reduce dependence on a few key people.
A separate post introduces Composer, a browser-based tool for pausing and thinking through high-pressure work situations.
Ask whether Composer is part of their mainframe work.
Wacker connects practical signals to organizational decisions.
They point to hiring patterns and vendor disputes as signs that modernization is moving from discussion to execution, then ask whether pricing is a negotiation issue or an architecture issue.
In another post, they use job listings at five insurers to argue that talent gaps reflect years of underinvestment, not just a short-term shortage.
Their advice gets specific about sequencing: senior specialists should handle architecture and risk, while teams execute within clear guardrails and transfer knowledge.
Readers interested in the business and operating choices behind mainframe change can follow how they link these pressures to delivery.
William Wacker writes about mainframe and enterprise IT for a business audience, mostly CIOs, CFOs, and procurement leads.
Read more
Three habits run through their posts: reframing common complaints (cost, talent, vendor pricing) as strategy or delivery-model failures rather than shortages to endure; treating lawsuits and job ads as leading indicators of what enterprises will buy next; and insisting that modernization is a sequencing problem, not a speed problem.
Their posts are short, argument-first, and usually end with a question aimed at peers.
One post sits outside that work entirely and introduces a separate sales-coaching tool.
Mainframe talent trouble is a strategy failure, not a shortage to endure
Organizations losing mainframe staff are not victims of a thin market, Wacker argues.
Read more
A decade of treating mainframe maintenance as a cost center and starving it of investment created the scarcity.
Now the bill comes as executive-level salaries for outside hires and dependence on a handful of key people.
Organizations either build internal capability deliberately or rent it expensively later—and renting does not fix the underlying exposure.
Over a 90-day window, Wacker tracked mainframe-related job postings at MetLife, Lincoln National, Nationwide, Prudential, and New York Life.
The roles covered modernization leadership, security and compliance, and product work for active middleware estates.
They read each opening as evidence that the organization could not find the talent internally.
The post asks what organizations plan to do about talent walking out the door—and what the mainframe community intends to do about it.
Vendor pricing has become an architecture decision, not a negotiation
Wacker says Broadcom's post-acquisition pricing of CA mainframe software has crossed a threshold where legal action replaces bargaining.
Read more
When a company the size of UnitedHealth Group sues a mainframe software vendor instead of renegotiating, peer procurement teams do not wait for the outcome; they start modeling their own exposure. That turns a pricing dispute into a tooling and architecture review.
Across several posts, Wacker counts three active mainframe software legal disputes in enterprise accounts and calls them a market inflection point, not a coincidence.
They name the UnitedHealth Group suit as the most visible case and point to pressure in healthcare, banking, and insurance.
The question for peers: are clients still treating Broadcom pricing as a negotiation problem, or have they started treating it as an architecture problem?
Read the tells: job ads and filings reveal buying decisions before they are announced
Wacker infers intent from observable signals rather than waiting for public strategy.
Read more
Hiring patterns show whether a modernization program is still being planned or already executed; litigation shows how far pricing pressure has gone. The useful question, they argue, is not how many signals appear but which ones mark a decision already made.
A QA automation role appearing alongside COBOL modernization work signals execution-stage hiring, not planning.
Likewise, DB2/zOS teams hiring for automation plus 24x7 on-call coverage suggest modernization is funded while the mainframe remains load-bearing and tooling decisions are moving forward.
Wacker also describes healthcare as a case where litigation, a multi-role staffing spike anchored by a principal migration engineer, and a parent-subsidiary signal arrived in one intelligence cycle.
They point to a 90-day buying window through early August 2026 for mainframe tooling displacement.
Sequencing beats speed, because production has to keep running
Wacker's recurring recommendation: modernization succeeds or fails on ordering, not pace.
Read more
Vendor conflict, workforce cuts, compliance obligations, and government timelines arrive at once, each pressing on the same production estate.
The task is to decide what moves first so the business keeps running through change.
They also argue against waiting for perfect clarity: organizations that wait usually get none and lose the ability to set their own terms.
One post lists five recurring patterns in enterprise estates: vendor pressure turning into sequencing pressure while production must stay stable; bridge roles pairing COBOL with modern-stack skills as a phase-one sign that inventory work is done; workforce reductions forcing vendor rationalization; fraud- and audit-critical workflows turning legacy cost into operational risk; and government modernization timelines acting as external clocks beyond IT's control. Wacker's prescription is to move early, not perfectly, and define minimal viable governance steps rather than a full plan.
The focus shifts from diagnosis to method: earlier material lays out converging pressures; later posts argue for acting early with incomplete information and separating fear from facts.
Change how delivery is structured instead of renegotiating rates
Rising mainframe costs are a delivery-model issue, not a pricing issue, Wacker argues.
Read more
Rate negotiations or staffing cuts in mission-critical environments simply shift risk.
Their proposed structure assigns senior specialists to architecture, risk, and decisions; mid-level teams to execution within clear guardrails; and systematic mentoring and supervised delivery to replace ad hoc knowledge transfer.
The mentoring layer reduces key-person dependency so organizations stop rehiring the same capability.
Wacker frames the outcome for CFOs and procurement leaders as lower cost while maintaining quality and reducing risk. They call it a cost-control and risk-management lever, not a staffing problem, and invite anyone facing cost pressure or talent risk to compare notes.
Executive ownership of the mainframe relationship, decided before negotiations start
Wacker frames control of the mainframe relationship as a governance problem, not a disruption project.
Read more
Leverage shifts during renewal, so the useful work happens earlier: name an executive owner, plan commercial scenarios, and get an independent assessment before talks begin. They also call for reducing talent concentration and shortening delivery cycles for non-critical functions, turning renewal pressure into predictable outcomes instead of last-minute forced decisions.
One post lays out the sequence: explicit executive ownership, disciplined commercial scenario planning, independent insight before negotiations begin, and deliberate reductions in talent concentration and delivery cycle times for non-critical functions. The aim is to turn renewal pressure into predictable outcomes.
AI budgets are pulling mainframe tooling spend into review
Wacker connects the boardroom AI agenda to mainframe budgets.
Read more
Infrastructure cost rationalization has to fund AI investment, they argue, and it lands hardest on the CA tooling layer, which they describe as the highest-cost, lowest-visibility line item in most mainframe budgets.
AI modernization talk does not displace anything on its own; downstream tooling and workflow decisions appear when initiatives move from narrative to production.
Funded AI programs cannot show returns until the mainframe bottleneck is resolved, they add.
Wacker says AI transformation mandates are forcing mainframe budget reviews and that rationalization is landing on the CA tooling layer. Three forces—vendor pricing, talent attrition, and AI mandates—are arriving simultaneously across banking, healthcare, insurance, and transport, not in sequence.
A separate venture: a tool for decisions under sales pressure
One post leaves the mainframe subject entirely.
Read more
Wacker introduces Composer, a browser tool designed to create a moment of space before a high-stakes email, meeting, or sales call, drawing on a background in enterprise technology and cybersecurity sales. Training rarely appears when judgment is tested, they argue, so a short intervention just before the decision is more useful than a course taken weeks earlier.
Wacker describes the target moments: just before sending an email, the four minutes before walking into a room, the silence on a sales call when you feel yourself about to promise too much, and the drive home after a hard meeting. They frame the product as a tool for better decisions under pressure and link to composercoach.ai.
This post departs from mainframe and enterprise IT commentary to cover a personal product venture, not a shift in Wacker's mainframe positions.
This post shows their signature move: reading market inflection points from litigation and hiring data.
Read more
A newcomer can start here to see how they connect vendor pricing pressure to architecture decisions rather than treating it as a simple negotiation.
Wacker argues that three simultaneous mainframe software legal disputes mark a market inflection point.
When large organizations sue over CA software costs, peer procurement teams begin modeling their own exposure, creating a buying motion across healthcare, banking, and insurance.
They also point to COBOL talent attrition forcing modernization on someone else’s timeline, citing QA automation roles appearing alongside COBOL modernization projects as a tell of execution-stage hiring.
The piece asks whether clients treat Broadcom pricing as a negotiation problem or an architecture problem.
For brands planning a campaign
For a thought-leadership engagement, this piece can anchor a webinar on responding to vendor pricing pressure when litigation changes the negotiation landscape. It shows how they frame the issue as an architecture problem—a strong hook for a co-hosted enterprise webinar.
This post turns talent attrition into a board-level strategy argument, using named insurers and a specific time window.
Read more
It’s a clear entry point for understanding why they treat mainframe talent as a forcing function for modernization.
Wacker tracked mainframe-related job postings at MetLife, Lincoln National, Nationwide, Prudential, and New York Life over 90 days.
They argue the common driver is not a generic talent shortage but a strategy failure: organizations that treated mainframe maintenance as a cost center now pay executive-level salaries for external capability.
They warn that the cost of not investing in internal talent exceeds the cost of the systems themselves, and ask CIOs and CTOs whether they will act before or after a forcing function arrives.
For brands planning a campaign
This content can support a webinar segment on the business case for early action on talent, using concrete hiring examples to show why waiting creates executive-level costs. It also fits a thought-leadership piece on reframing mainframe maintenance from cost center to strategic capability.
This is a concise map of their recurring arguments about sequencing and operating model decisions.
Read more
A newcomer can use it to see how they organize multiple pressures into a practical modernization checklist.
Wacker lists five recurring patterns: vendor pressure becoming sequencing pressure; bridge roles as phase-one tells when COBOL is paired with modern stack skills; workforce reductions forcing vendor rationalization; compliance workflows turning legacy cost into operational risk; and government mandates creating external clocks IT does not control. Their conclusion: modernization is about sequencing correctly so the business is not broken while changing it.
For brands planning a campaign
This list is a natural outline for a co-hosted webinar on sequencing mainframe modernization, with each pattern as a discussion point. It also shows how they synthesize complex pressures into teachable operational guidance.
This post demonstrates how they combine litigation, hiring, and executive mandates into a single market view.
Read more
It helps readers understand how they use multiple signals together to predict procurement and tooling decisions.
Wacker uses healthcare to illustrate signal quality: in a single intelligence cycle they saw active litigation over mainframe software pricing, a multi-role staffing spike anchored by a principal migration engineer, and a parent-subsidiary compound signal.
The post identifies structural trends: Broadcom pricing reaching litigation threshold, UnitedHealth Group’s lawsuit as a pattern for enterprises running CA tooling, and senior talent attrition accelerating the consulting window.
They also note that AI modernization narratives have not yet driven displacement, but downstream tooling and operational decisions appear once initiatives move to production.
For brands planning a campaign
This content can frame a webinar around early warning indicators and signal quality, using healthcare as a concrete sector example. It also supports a thought-leadership piece on why AI modernization narratives alone do not trigger displacement until production workflows change.
This post states their core consulting recommendation: change how delivery is structured rather than simply negotiating rates.
Read more
It helps a newcomer see the practical advice behind their market analysis.
Wacker argues that rising mainframe costs and scarce talent are a delivery model issue, not a pricing issue.
They propose structuring delivery so senior specialists focus on architecture, risk, and decisions; mid-level teams handle execution within clear guardrails; and expertise is embedded through real mentoring and supervised delivery to reduce key-person dependency.
They frame this for CFOs and procurement leaders as a cost control and risk management lever, not a staffing problem.
For brands planning a campaign
This content can anchor a thought-leadership piece on alternative delivery models, positioning the consultancy as a partner for restructuring mainframe work. It also fits a webinar segment on cost control and knowledge transfer as risk management.
Reading the tells that precede toolchain decisions6
Mainframe talent attrition and key-person dependency5
Vendor pricing pressure at the litigation threshold4
Sequencing modernization so production stays stable3
AI mandates pulling mainframe budgets into review3
Executive governance and procurement strategy2
Restructuring the delivery model as a cost and risk lever1
Beyond mainframe commentary: a personal product venture1
Vendor pricing pressure at the litigation threshold
Wacker tracks Broadcom's post-acquisition pricing of CA mainframe software and argues it has crossed a litigation threshold, pointing to UnitedHealth Group's lawsuit as the most visible case while peer procurement teams model their own exposure.
Read more
They frame the pressure across healthcare, banking, and insurance, and ask whether organizations still treat it as a negotiation problem or have started treating it as an architecture problem.
Name a pattern, cite one concrete trigger, then close with a direct question to peers.
For brands planning a campaign
A sharp, current hook for a webinar or thought-leadership piece aimed at CIO, procurement, and finance audiences weighing a mainframe vendor renewal. It positions an independent consultancy in the vendor-economics conversation, not around a product.
Mainframe talent attrition and key-person dependency
Wacker argues that the COBOL, CICS, and z/OS talent pool is shrinking faster than it can be replaced, leaving organizations dependent on a handful of key people.
Read more
They point to executive-level mainframe roles posted at large insurers, banks, and carriers because organizations cannot find internal talent, and argue that the real failure was starving maintenance of talent investment for a decade.
Reframe a staffing gap as a strategy and investment failure, then ask what the community will do about it.
For brands planning a campaign
Supports a content collaboration on workforce risk and knowledge transfer. Wacker frames this as a strategy story, not a talent-shortage story, giving a co-hosted discussion a clear, arguable position rather than a generic skills warning.
Sequencing modernization so production stays stable
Wacker argues modernization is not about moving fast but about sequencing correctly so the business does not break during change.
Read more
Under the line 'move early not perfect,' they contend that organizations waiting for perfect clarity get none, and that vendor conflict creates sequencing pressure while production must stay stable during the decision.
For brands planning a campaign
Fits a practical playbook, workshop, or assessment. The sequencing angle gives enterprise audiences evaluating modernization timelines and risk a concrete, non-promotional perspective.
Reading the tells that precede toolchain decisions
Wacker uses pattern-recognition framing—a tell, a 90-day buying window, an intelligence cycle—to point to hiring signals, litigation, and post-acquisition integration as precursors to toolchain decisions.
Read more
Examples include automation plus 24x7 on-call roles appearing alongside DB2/zOS work, and QA automation roles appearing alongside COBOL modernization projects, evidence that execution has already started.
Signal analysis: identify the observable hiring or legal tell, then infer the buying motion behind it.
For brands planning a campaign
A distinctive methodological angle for a data-driven webinar or market report, positioning the collaboration around mainframe market intelligence rather than vendor claims.
Restructuring the delivery model as a cost and risk lever
Wacker argues rising mainframe costs are a delivery-model issue, not a pricing issue, and that rate negotiation or staffing tactics raise risk in mission-critical environments.
Read more
The proposed structure puts senior specialists on architecture, risk, and decisions; mid-level teams on execution within guardrails; and systematic knowledge transfer to reduce key-person dependency. The message targets CFOs and procurement leaders.
Name a desired business outcome—lower cost, maintained quality, reduced risk—and explain the mechanism: placement of expertise.
For brands planning a campaign
Suits executive-facing content that frames mainframe cost as a cost-control and risk-management lever. The delivery-model argument supports sponsorship copy that does not depend on a single vendor or tool.
Wacker frames executive control of the mainframe relationship as clarity, not disruption: explicit executive ownership, disciplined commercial scenario planning, independent insight before negotiations begin, and deliberate work to reduce talent concentration and shorten delivery cycles for non-critical functions.
Read more
For brands planning a campaign
A natural scaffold for a CIO/CTO-facing webinar or independent-assessment offer. The governance-before-negotiation angle leads into a co-hosted session on renewal and procurement strategy.
Wacker argues that AI transformation mandates are forcing mainframe budget reviews, and that infrastructure cost rationalization lands hardest on the CA tooling layer, which they describe as the highest-cost, lowest-visibility line item in most mainframe budgets.
Read more
The argument ties mainframe bottlenecks to whether funded AI programs can show returns.
For brands planning a campaign
Connects the mainframe conversation to the boardroom AI agenda, making it useful for a joint piece on how AI investment collides with infrastructure spend.
Beyond mainframe commentary: a personal product venture
One post departs entirely from mainframe analysis, introducing Composer, a browser tool for creating space to think in the moments before a high-stakes sales call, meeting, or email.
Read more
Wacker draws on a background in enterprise technology and cybersecurity sales, framing the product around better decisions under pressure.
The topic, product, and audience differ from the rest of the posts, so treat this as a separate venture rather than a mainframe content theme.
For brands planning a campaign
Shows a wider range than mainframe-only commentary. Scope a co-hosted effort deliberately: focus on mainframe and enterprise IT to match the bulk of the work, or on sales and decision-making coaching if that angle is the goal.
The posts show two named commercial connections: CPT Global, which Wacker promotes in three posts about mainframe cost and governance, and Composer, a coaching tool they say they built.
Read more
The posts do not state Wacker's title or ownership stake in either, or whether they work with CPT under contract; ask for those details before assessing the commercial relationship.
Broadcom appears often as the vendor whose pricing and litigation Wacker tracks, with no disclosed commercial relationship.
MetLife, Lincoln National, Nationwide, Prudential, and New York Life are named only as employers with mainframe job postings, not as brand relationships.
CPT Global
Disclosed partnership
Three posts speak for CPT and point readers to cptglobal.com.
Read more
One closes with "Break the Mainframe Tax, with CPT"; another says "At CPT, we have been doing this a long time" while describing how modernization should be sequenced; a third says CPT provides "the independent assessment and execution playbook executives need" for mainframe renewal and governance.
The posts do not state Wacker's title or the nature of their relationship with CPT.
Ask whether they are employed by CPT, own a stake, or work with the company under contract.
Original disclosure
At CPT, we have been doing this a long time.
Modernization isn't about moving fast.
It's about sequencing correctly so you don't break the business while you change it.
Wacker says "I built Composer for a very small window of time" and describes it as a browser tool for the minutes before a pressured moment — sending an email, walking into a room, a sales call — drawing on their enterprise technology and cybersecurity sales background.
Read more
They ask readers to try it at composercoach.ai. The post says they built the product but does not state their current role or whether they own a stake in it.
Original disclosure
I built Composer for a very small window of time. ... Try Composer: https://composercoach.ai
Broadcom is a recurring subject, with no disclosed commercial relationship.
Read more
Wacker writes that Broadcom's post-acquisition pricing of CA mainframe software "has crossed the litigation threshold," that peer procurement teams are modeling their own exposure, and that the question for peers is whether clients still treat Broadcom pricing as a negotiation problem or an architecture problem. The posts state no sponsorship, client work, or partnership with Broadcom.
Follow William Wacker to think about enterprise mainframe estates from a buyer's perspective.
Read more
Start with the argument-first posts on vendor pricing and talent, then move to those on how to order a modernization program.
They work from observable signals rather than vendor roadmaps: job ads, lawsuits, staffing spikes, and compliance obligations serve as evidence of decisions already made inside large organizations in banking, healthcare, insurance, and transport.
Most posts are short, take a clear position, and end with a question for peers; reading several in sequence shows recurring themes and how Wacker tests ideas against other practitioners.
One post steps outside this material to introduce Composer, a browser tool for pausing before a high-pressure email, meeting, or sales call, drawing on a background in enterprise technology and cybersecurity sales.
If mainframe strategy is not your subject, Composer is the post that overlaps with sales and decision-making coaching instead.
Mainframe modernizationMainframe talent and workforce riskVendor pricing and procurement strategyEnterprise IT governanceAI mandates and infrastructure budgetsCOBOLIBM Z and z/OSEnterprise technology salesLinkedIn postsCIOs and CTOsCFOs and procurement leaders
Michael Belkin JD, MSHA, FACHE, CMPE
Belkin writes about clinician supply as Wacker writes about mainframe staff: both treat a persistent talent gap as a planning and investment failure, not a market condition to wait out.
Read more
They argue that organizations reacting only after a shortage becomes urgent pay more and carry more risk. Each works on staffing and workforce issues in their industry and draws on long client histories to make the case.
The subject matter differs: healthcare delivery and physician workforce strategy rather than mainframe and enterprise IT. Belkin anchors arguments in burnout and specialty-level attrition data, while Wacker grounds theirs in hiring posts, vendor litigation, and platform economics.
Lancellotti reasons about how AI changes enterprise systems as Wacker does about mainframe estates: both look beneath transformation narratives and argue that durable work lies in data, architecture, and the layer where decisions are made.
Read more
Both write for transformation leaders and are willing to revise a long-held position when new evidence changes their view.
Lancellotti focuses on ERP and CRM consolidation, customer data platforms, and AI-generated workflows, largely from a delivery and customer-success vantage point. Wacker stays closer to mainframe tooling, vendor conflict, and procurement and governance decisions around renewals.
Kumar covers niche enterprise application talent, Oracle Cloud, PeopleSoft, SAP, and Workday, making a case similar to Wacker's mainframe argument: scarce specialists rarely apply through job boards, and relationship-based, AI-assisted sourcing beats reactive hiring.
Read more
Both write short posts that name a market shift and close with an offer to compare notes.
Kumar, a recruiting founder, describes how to find and place ERP consultants across sectors, with the sourcing model as the product. Wacker is narrower and more analytical, reading job ads and legal filings as buying signals and tying them to mainframe tooling and cost decisions.
On October 8, 2026, William Wacker’s LinkedIn profile showed about 10,155 followers.
Read more
Their writing addresses an enterprise-IT audience — people who run or buy mainframe services — through commentary on Broadcom and CA-era software pricing, COBOL and z/OS talent attrition, and the sequencing risk of modernizing systems that are still load-bearing.
Posts typically close with a direct question inviting peers to compare experience, suggesting the audience is expected to answer from inside enterprise programs rather than observe from outside.
For a placement decision, the follower base and subject matter are consistent with a relevant professional audience for a mainframe modernization consultancy selling to CIOs, CTOs, procurement leads, and mainframe engineering managers.
This is an inference from what they write and whom the writing addresses.
Their posts do not report the followers’ geography, age, gender, employer, occupation, or seniority, and publish no per-post engagement counts (likes, comments, reshares), so individual posts’ reach and response levels cannot be compared.
Before committing to a co-hosted webinar, ask for recent results on comparable content — posts on vendor pricing, talent attrition, or sequencing, with impressions and engagement — and any audience survey reporting job title, seniority, or geography.
These would help establish whether the following concentrates in enterprise mainframe decision roles and how comparable posts perform.
LinkedIn followers
10,155
Follower count shown on the LinkedIn profile linked in the identity section · 2026-10-08
Wacker's posts focus on mainframe modernization and do not document a sponsorship program, rate card, disclosure policy, or partnership inquiry route.
Read more
Several reference CPT, a mainframe consultancy; one says CPT provides independent assessment and an execution playbook.
Another promotes Composer, a browser-based decision tool at composercoach.ai that they say they built.
These are business and product mentions, not confirmed creator sponsorship offers.
Brands considering a thought-leadership engagement or co-hosted webinar should ask Wacker or CPT directly whether sponsorship or co-marketing is available and on what terms.
Strong fit for the written series and webinar; commercial terms remain unconfirmed, and audience composition is unmeasured.
Read more
Brief
An independent mainframe advisory firm selling assessments and delivery restructuring to CIOs, CTOs, and procurement leads at insurers, banks, and carriers wants William Wacker for a thought-leadership engagement: a 60-minute co-hosted webinar and a four-part written series timed to clients' 2026 software renewals. The brief covers vendor pricing pressure, mainframe talent attrition, and modernization sequencing.
Reasons
The campaign targets advisory firm clients facing renewals—a subject Wacker writes about repeatedly and in depth. Across the posts, they track Broadcom's post-acquisition pricing of CA mainframe software, argue it has crossed a litigation threshold, cite UnitedHealth Group's lawsuit as the most visible case, and describe peer procurement teams at other enterprises modeling their own exposure. That is the conversation an advisory firm wants to join as its clients approach renewals.
The framing suits an advisory seller better than a product seller. Wacker's closing question—whether clients still treat Broadcom pricing as a negotiation problem or have started treating it as an architecture problem—shifts the conversation from rate haggling to structural decisions. A firm selling independent assessment and execution planning can build a webinar around that distinction without turning it into a product pitch.
A concrete, board-level hook is available. Wacker tracked mainframe job postings at MetLife, Lincoln National, Nationwide, Prudential, and New York Life within a single 90-day window, arguing that a decade of under-investment in internal capability—not a generic skills shortage—was the common driver. Named companies and a defined time window give the co-hosted session a specific opening, rather than a general warning about retiring COBOL staff.
Wacker's stated advisory position aligns with a consultancy's offer. Their delivery-model argument—senior specialists handling architecture, risk, and decisions; mid-level teams executing within guardrails; and expertise transferred through supervised delivery to reduce key-person dependency—is a straightforward cost-control and risk-management case for CFOs and procurement leaders. An advisory firm can co-present that structure instead of re-arguing the diagnosis.
Wacker's usual format works for a co-hosted session. The posts are analytical and medium-length, and end with direct questions inviting peers to compare experiences—a natural fit for a webinar with audience discussion. They have also framed the current period as a concentrated buying window, giving the series a reason to run now.
The main open items are commercial and audience-related. Wacker's posts do not mention a sponsorship program, rate card, or partnership inquiry route, and several refer to their business context, including CPT. Ask Wacker or CPT directly whether co-marketing or sponsorship arrangements are available and on what terms. The posts do not report the job title, seniority, employer, or geography mix of the roughly 10,155 LinkedIn followers, nor do they publish per-post impressions or engagement figures. Request audience and performance data before assessing reach or response.
When to choose a specialist
Poor fit for this brief as written.
Read more
Brief
A sales-enablement software company wants Wacker as a recurring short-form video creator, producing weekly 60-second vertical clips and reactive posts for frontline sales development representatives. The campaign would build on their personal product post about a browser tool for pausing before high-stakes calls and meetings.
Reasons
The premise rests on one post out of ten. The post introducing a decision-making tool for the moments before a sales call, meeting, or email is the only one that departs from mainframe and enterprise-IT analysis. It documents a personal product venture, not a body of sales-coaching content; the other nine posts offer no basis for predicting a steady supply of SDR-focused material.
The audience evidence points the other way. The writing addresses people who run or buy mainframe services—CIOs, CTOs, procurement leads, and engineering managers dealing with COBOL, CICS, z/OS, and vendor renewals. Frontline sales development representatives are a different audience. The available material does not measure who follows or engages, so audience overlap cannot be assumed.
Wacker's posts show no short-form video work. They are written LinkedIn posts, with no video, transcript, or visual assets to help a buyer assess whether they can deliver a weekly vertical-video format or how the clips might perform.
Wacker's posts describe no commercial format for any category. There is no sponsorship program, rate card, disclosure practice, or inquiry route. A recurring paid creator arrangement would need to start from scratch; ask for terms and evidence of sponsored-work performance before proceeding.
The subject-matter transfer is weak. The sales-pressure angle rests on Wacker's stated earlier career in enterprise technology and cybersecurity sales. That makes the product's origin credible, but does not establish a following among sales representatives or reach into sales-team training budgets.
A worked campaign example
Angle
Build the campaign around the argument that mainframe software pricing conflicts have shifted from procurement negotiations to architecture and sequencing decisions—and that organizations acting before a renewal date secure better terms than those reacting to one. The advisory firm supplies the independent-assessment framing; Wacker brings the market reading and the peer question that closes each piece.
Format
Run one 60-minute co-hosted webinar with a named host from the advisory firm and Wacker as guest, supported by four written installments of roughly 600 to 900 words published over six weeks. End each installment with a question inviting reader responses. Distribute through LinkedIn and the firm's own channels.
Running order
Installment one: what changed. Wacker's view that litigation over CA-era software pricing has become a pattern rather than an isolated dispute, and what peer procurement teams do when they see one. Close by asking readers where friction is worst: procurement, operations, or vendor lock-in.
Installment two: the talent clock. Cover the 90-day window of executive-level mainframe roles at large insurers and carriers, and the argument that under-investment in internal capability—not a generic skills shortage—created the openings. Close by asking what readers' organizations are doing about departing staff.
Installment three: sequencing, not speed. Cover five recurring patterns in mainframe estates: vendor pressure becoming sequencing pressure; bridge roles signaling phase one; workforce cuts forcing vendor rationalization; compliance workflows turning legacy cost into operational risk; and external modernization timelines that IT does not control. Close by asking readers which pressure they feel first.
Webinar: the renewals conversation. Wacker opens with the market read; the advisory firm presents its assessment and delivery-restructuring method. Close on governance: executive ownership, commercial scenario planning, and independent insight gathered before negotiations begin, rather than after leverage shifts.
Installment four: what good looks like. Recap the webinar discussion, the delivery model the firm recommends, and what to confirm before a renewal.
Follow-up handoff: offer a short assessment with a defined scope and a next-step conversation, so the series ends with an action rather than a summary.
Title
The Renewal Clock: a co-hosted webinar and four-part series on pricing disputes that have become architecture decisions
What to confirm
Ask Wacker or CPT whether sponsorship or co-marketing is available, what it costs, and how the arrangement would be disclosed.
Recent results for comparable posts — impressions and engagement on pricing, attrition, or sequencing topics — plus audience data reporting job title, seniority, employer, or geography, so the firm can test whether this content reaches enterprise mainframe decision roles before committing budget.
Ask whether Wacker is willing to appear on camera or in a live session; their posts are written only, so live and video capability is untested.
Schedule against the firm's clients' renewal dates, since the urgency argument depends on a defined window rather than an open-ended invitation to act.
Why it works
Every claim in the series is grounded in something Wacker has already published: pricing litigation as a market signal, named hiring examples in insurance and banking, the sequencing argument, and the governance framing. The advisory firm's offer answers the question the content raises instead of interrupting it.
For a thought-leadership engagement on enterprise change, workforce pressure, and operational risk, Belkin is the better choice when the buyer's audience is healthcare delivery organizations and the subject is clinician supply, physician burnout, or workforce planning.
Read more
Their posts address patient access, continuity of care, revenue stability, and staffing gaps directly.
They cite specific figures, such as roughly 50% of physicians reporting burnout in 2024 to 2025, and name the highest-burnout specialties: emergency medicine, OBGYN, oncology, anesthesia, and radiology.
They connect burnout to turnover and argue that flexible workforce models such as locums, PRN, rapid-response teams, and fractional roles should be structural, not optional.
Belkin is a stronger match than Wacker if the campaign promises help for healthcare recruiters, service-line leaders, or clinical workforce strategists.
Belkin's posts do not cover Broadcom or CA software pricing, mainframe litigation, COBOL, CICS, z/OS, or modernization sequencing.
A buyer choosing Belkin for a mainframe renewal-themed campaign would miss Wacker's named hiring signals at large insurers and carriers, the litigation-threshold argument, and the advisory framing around procurement, operations, and vendor lock-in.
Belkin's evidence points to a healthcare staffing and clinical operations audience, not the CIO, CTO, procurement, and engineering leaders Wacker addresses.
For a thought-leadership engagement on enterprise technology pressure and transformation, Lancellotti is the better choice when the campaign is about AI-driven ERP consolidation, agentic AI replacing the workflow layer, or using AI to serve long-tail customer accounts.
Read more
Their posts make specific architecture claims: AI is not replacing ERP systems but replacing the workflow layer built on top of them; ERP becomes the system of record, not the system of work; and organizations should keep consolidating financials, procurement, HR, and supply chain while stopping workflow construction inside the ERP.
A second post describes a digital account manager workflow that joins customer data platform, service delivery, contract lifecycle, and finance data to reach customers who rarely hear from a human sales agent.
Lancellotti is a sharper fit than Wacker if the buyer wants an enterprise AI and ERP architecture voice rather than a mainframe-specific voice.
Lancellotti's posts do not discuss Broadcom, CA tooling, UnitedHealth Group's lawsuit, COBOL talent attrition, or mainframe sequencing.
A buyer choosing Lancellotti for a renewals-themed campaign would get AI and ERP transformation arguments, but miss Wacker's read on litigation as a market signal, the 90-day window of mainframe leadership hires, and the argument that organizations cannot hire their way out of mainframe dependency.
Lancellotti's audience evidence points to ERP, customer success, and enterprise AI readers, not mainframe CIOs, CTOs, or procurement leads.
For a thought-leadership engagement about enterprise technology talent and delivery, Kumar is the better choice when the campaign centers on ERP and enterprise application recruiting, niche consultant sourcing, or hiring strategy for Oracle Cloud, PeopleSoft, SAP, Workday, and similar programs.
Read more
Kumar's posts describe a sourcing model built on long-term relationships, repeat project engagements, referrals, a passive consultant network, an active ERP and IT talent database, and AI-driven sourcing tools.
They list specific skill areas, including Oracle Cloud PPM, Oracle Revenue Management Cloud, Oracle Subscription Management, Oracle Recruiting Cloud, PeopleSoft FSCM and HCM, Oracle OIC integrations, SAP S/4HANA finance and supply chain, and Workday HCM and payroll.
Kumar is more useful than Wacker if the buyer's promise is finding specialized ERP talent rather than advising on mainframe modernization.
Kumar's material does not address the mainframe buyer task: vendor pricing pressure, software litigation, COBOL or z/OS talent attrition, or modernization sequencing.
A buyer choosing Kumar for a mainframe renewal-themed campaign would miss the specific market signals that make Wacker relevant to an independent mainframe advisory offer.
Kumar's audience and offer also focus on recruiting and ERP program delivery, shifting the discussion from architecture and procurement decisions to hiring pipelines and consultant availability.
This profile covers the full text of ten LinkedIn posts written by William Wacker, plus two posts each from three creators used for comparison: Michael Belkin, Tino Lancellotti, and Amresh Kumar.
Wacker's posts carry no publication dates, so they map recurring arguments and priorities rather than a chronology; one post refers to sixteen years observing the IBM z ecosystem.
Nine posts cover mainframe vendor pricing, mainframe talent and key-person risk, modernization sequencing, executive governance, and pressure on mainframe budgets from AI investment; one post introduces Composer, a separate sales-coaching tool, and is flagged as falling outside that work.
The profile lists roughly 10,155 followers on 8 October 2026.
The comparison posts were published between December 2025 and May 2026.
Gaps that affect what this page can claim: William Wacker's posts do not mention books, shows, talks, or other signature work, so earlier career history and the wider name-search footprint are unconfirmed; no video, transcripts, or visual assets appear in the posts here; no audience demographics or per-post engagement figures appear in the posts here; and no sponsorship program, rate card, or partnership inquiry route appears in the posts here, so commercial terms remain open questions.
The brand connections to CPT Global and Composer are described only as far as the post text goes, which does not state a title, ownership stake, or contract.
