Zack Greenfield advises middle-market companies on putting AI to work, with a focus on fitting tools and training to real workflows and helping organizations move from pilots to wider adoption.
Zack Greenfield advises middle-market companies on putting AI to work.
In the posts here, they focus less on what AI tools can do than on whether people can use them in real jobs and whether organizations can move from a promising pilot to wider adoption.
Their examples range from training floor supervisors around their daily tasks to planning who must approve a rollout.
Follow their work for practical arguments about the people, workflows, and decisions that shape AI implementation—not just the technology.
Greenfield connects AI adoption to specific operating problems.
In one post, they argue that feature-focused training missed the factory supervisors who stood to benefit, and propose starting with the decisions they make, the time they lose, and the work they hand off.
In another, they describe testing an AI-assisted intake process inside their own business, including failures with unusual contracts and overlapping timelines, before bringing a version to a client.
They also point to a different obstacle: a successful pilot can still stall when the departments responsible for scaling it were not involved early.
Together, these examples help readers understand why AI initiatives falter after the demo—and what workflow design, hands-on testing, and decision ownership have to do with it.
Zack Greenfield writes about why AI programs in middle-market companies stall and what to do instead, as well as how consultants should position and test their own work.
Read more
Across the posts, the argument is that adoption fails for organizational reasons, not because the technology is unready: training focuses on software features rather than people's daily decisions, and rollout plans leave most departments out of the original conversation. Greenfield pairs each argument with a numbered case from a company or client and ends with a prescription: start from the job, decide who owns deployment before the pilot, narrow what you claim to specialize in, and test the solution inside your own business before selling it.
Teach the job, not the software
Greenfield argues that AI rollout training fails when it covers product features instead of the decisions people actually make at work.
Read more
Curriculums are built before anyone talks to the people who will use the tool, leaving those closest to the work watching demonstrations designed for someone else's job before returning to their old process.
Greenfield's prescription: ask what decisions people make repeatedly, where they lose time, and what output they hand to someone else, then build training around that.
The approach takes longer upfront, Greenfield says, but the rush to show a return on the platform cost keeps adoption low.
The conclusion is blunt: education is the implementation, and there is no shortcut around it.
Greenfield recounts a manufacturing vice president's account: the company spent $80,000 on an enterprise AI platform, but six months later adoption stood at 11%.
Training ran for two days and covered features; nobody spent an hour mapping which daily tasks the tool was meant to improve.
Floor supervisors who stood to gain the most watched demos built for a different workflow.
The vendor blamed change resistance, and the internal team blamed the interface.
Greenfield traces the problem to the missing workflow mapping.
The account comes from the executive, as relayed by Greenfield.
Adoption stalls in the approval chain, not in the model
Greenfield argues that AI projects can prove real savings and still never ship when rollout requires sign-off from departments left out of the original test.
Read more
Those departments have questions but no context.
Greenfield calls the accumulated result organizational debt, which can make model improvements irrelevant.
Companies that scale AI, they say, restructure who owns deployment decisions before pilots begin, treating deployment authority as a design problem rather than an afterthought.
The practical test: does an initiative have a path to full deployment, or only to an expensive proof of concept?
At a regional logistics company, an AI routing pilot cut fuel costs by 11% across a 40-truck test fleet, producing documented savings and pleasing the operations director.
Eighteen months later, it still had not been deployed at scale: company-wide rollout needed approval from six departments that were not part of the original conversation.
Greenfield says none of them acted badly; each had legitimate questions but no context, so they slowed the rollout.
Greenfield gives the savings figure and fleet size from their own account.
Pick one problem and refuse work that does not fit
Greenfield describes narrowing a consulting practice from generalist to specialist, and frames positioning as a decision rather than a marketing exercise.
Read more
A reputation for being useful to everyone can become a ceiling: clients are satisfied and referrals keep coming, but the market cannot describe what the person is for, so they are not recommended for larger engagements.
Greenfield argues that a personal brand is not your own story but the story other people tell about you when you are not in the room.
It is built through consistent choices over time, including what to stop doing.
Greenfield also describes the cost of the change: the first six months after narrowing felt, in their words, like walking off a cliff.
Better-fit clients later arrived with larger problems and longer engagements.
After years of taking any problem — scoping a CRM migration on Monday and redesigning an operations workflow on Friday — Greenfield says a CFO they respected told them plainly that she did not know what they specialized in and therefore could not recommend them for the big work.
The fix was not a rebrand, a new headshot, or a conference slot, Greenfield says, but turning down work that did not fit until the market associated their surname with one problem: helping middle-market companies cut through AI hype and build systems that work.
Greenfield recounts the exchange as their own account of what a client-side executive told them.
The post describes a shift from taking any consulting engagement to focusing on middle-market AI implementation, with a financially uncomfortable transition of roughly six months.
Greenfield says every tool, workflow, and automation their firm brings to a client has already been tested inside its own operations, under real deadlines and cash-flow conditions rather than in a sandbox or demo environment.
Read more
They present this as a rarely discussed part of AI consulting, contrasting it with firms that turn vendor promises into slide decks without operating the product at the scale they sell.
The trade-off, Greenfield says, is slower timelines and no deployment of unvalidated solutions, which frustrates executives seeking fast answers.
The benefit: whatever reaches a client's organization has already failed once on the consulting firm's own budget.
A six-week internal rebuild of the firm's client intake process used AI-assisted document parsing and automated follow-up sequencing.
It failed twice: parsing misfired on contracts with non-standard formatting, and follow-up logic triggered out of order when timelines overlapped.
Greenfield says the team fixed the problems, documented what broke and why, and rebuilt until the process held.
Only then did they bring a version to a mid-size professional services firm with the same bottleneck.
Greenfield's post identifies the company as ZGC and gives the project details.
Answers the practical question newcomers have about Zack Greenfield: do they teach AI implementation as an operating problem or repeat vendor talking points?
Read more
This is their most concrete case study and clearest statement of method.
Greenfield describes a recurring pattern: leadership approves an AI initiative, IT and sometimes power users get trained, and the rollout quietly dies in departments left out of planning.
The example is a manufacturing VP whose company spent $80,000 on an enterprise AI platform and reached 11% adoption six months later.
The vendor blamed change resistance; the team blamed the interface.
Greenfield's diagnosis: two days of training covered features, but nobody spent an hour mapping which daily tasks the tool was meant to improve.
Floor supervisors sat through demos built for someone else's workflow, then went back to spreadsheets.
The prescription is to start with the job, not the software: what decisions does this person make repeatedly, where do they lose time, and what output do they hand off?
Greenfield acknowledges this takes more time upfront and requires talking to people before building a curriculum.
Avoiding that work, they argue, is exactly why adoption numbers stay low.
For brands planning a campaign
A natural anchor piece for a collaboration on AI adoption and implementation training.
Its structure — diagnostic question, specific failure case, corrective method — could work as a co-created training series or workshop, while the workflow-first framing gives a brand a defensible editorial angle.
The $80,000 and 11% figures are Zack Greenfield's own claims; re-verify them before presenting them as fact.
Shows the operating claim behind Greenfield's consulting: recommendations have already been run inside the business.
Read more
Start here for hands-on build work rather than advisory commentary.
Greenfield writes that before ZGC recommends anything to a client, the firm has already broken it internally.
They describe every tool, workflow, and automation as stress-tested in the real conditions of running a company, not a sandbox or demo.
The concrete example is a six-week rebuild of internal client intake using AI-assisted document parsing and automated follow-up sequencing.
It failed twice: parsing misfired on contracts with non-standard formatting, and follow-up logic triggered out of order when timelines overlapped.
They fixed it, documented what broke and why, and rebuilt until it held.
Only then did they bring a version to a mid-size professional services firm with the same bottleneck.
Greenfield also names the cost: slower timelines, a refusal to deploy unvalidated solutions, and frustration from executives who want fast answers.
For brands planning a campaign
Supports a behind-the-scenes format built on documented internal rebuilds — what broke, why, and what changed — as an alternative to vendor-promise content.
The tension over slower timelines could resonate with executives skeptical of fast AI promises.
ZGC and the described builds appear only in the creator's post; ask for documentation of the company and project details before using them as proof points.
The best entry point to Greenfield's argument about deployment authority: why pilots that prove ROI still fail to ship.
Read more
Useful for readers focused on organizational barriers rather than tooling.
Greenfield argues that AI adoption stalls because of the org chart, not the technology.
The example is a regional logistics company whose AI routing pilot cut fuel costs by 11% across a 40-truck test fleet.
Eighteen months later, it still had not been deployed at scale because company-wide rollout required sign-off from six departments left out of the original conversation.
Each had legitimate questions but lacked context, so they did what cautious people do and slowed it down.
Greenfield calls this organizational debt and says companies scaling AI restructured who owns deployment decisions before pilots started, treating deployment authority as a design problem rather than an afterthought.
Ask for independent documentation of the 11% saving and 40-truck scope before citing them.
For brands planning a campaign
Best suited to a campaign about governance and change management rather than tools.
The arithmetic — proven pilot, documented savings, eighteen months of nothing — is a strong hook for operations and finance audiences.
It also pairs naturally with implementation training, where the same approval-path problem is a practical obstacle.
Answers the name-search question: what does Greenfield say they specialize in, and why?
Read more
This is their clearest first-person statement of focus in the posts here, and it explains the phrase middle-market companies keep encountering alongside their name.
Greenfield describes spending three years building a reputation as an all-purpose consultant who would scope a CRM migration on Monday and redesign an ops workflow on Friday.
Clients were happy, referrals steady, revenue fine on paper.
A CFO Greenfield respected told them, "Zack, I genuinely don't know what you specialize in.
And because of that, I can't recommend you for the big stuff."
Greenfield says the fix was not a rebrand but a decision to turn down work that did not fit, until the market associated the name with helping middle-market companies cut through AI hype and build systems that actually work.
The first six months, they write, felt like walking off a cliff.
Then better clients arrived with bigger problems and longer engagements.
Their conclusion: a personal brand is built through consistent decisions over time, including what to stop doing.
For brands planning a campaign
Relevant for a collaboration about the creator's own authority-building narrative or a founder-facing content series; less directly useful for practical AI implementation material. This is a first-person account of market positioning, not a client outcome.
Firm-as-lab: validate internally before recommending2
Decision ownership and approval paths as the real adoption blocker1
AI training built around the job, not the tool
Zack Greenfield argues that AI rollouts fail when training covers software features instead of the decisions people make every day.
Read more
In a post shared on LinkedIn and Instagram, they describe a manufacturing VP whose company spent $80,000 on an enterprise AI platform and reached 11% adoption six months later.
The company gave two days of feature training, never mapped which daily tasks the tool was meant to improve, and put floor supervisors through demos built for someone else's workflow.
Greenfield's method starts with the job — what decisions a person makes repeatedly, where they lose time, and what they hand off — then builds the curriculum around it, accepting a slower start to avoid low adoption.
Interview the people doing the work before designing a curriculum; make education part of implementation, not a follow-on step.
For brands planning a campaign
Frame collaborations around workflow-specific adoption training, not product walkthroughs. A vendor or consultancy offering an AI tool should co-produce content that maps it to named daily tasks and decisions for a specific role.
Decision ownership and approval paths as the real adoption blocker
A second recurring thread locates failure in the org chart, not model capability.
Read more
Greenfield describes an AI routing pilot at a regional logistics company that cut fuel costs by 11% across a 40-truck test fleet, then stalled for eighteen months because company-wide rollout required sign-off from six departments that had not been part of the original conversation. Their argument: companies that scale AI restructure ownership of deployment decisions before pilots start; the rest build expensive proofs of concept.
For brands planning a campaign
Content collaboration on change management and governance suits campaigns focused on organizational rollout decisions better than pure model-capability messaging. Expect Greenfield to steer the conversation toward who signs off, how many approvals a rollout needs, and how deployment authority is designed.
Greenfield writes about deliberately narrowing a consulting practice.
Read more
After years of taking any client problem, a CFO told them they could not name a specialty and therefore could not be recommended for large work.
Greenfield describes the fix as a decision, not a rebrand: refusing work that did not fit until the market associated the name with one problem — helping middle-market companies cut through AI hype and build systems that work.
They describe the first six months after narrowing as financially uncomfortable.
For brands planning a campaign
Partnership proposals should fit that narrow claim. Broad 'AI everything' campaigns are likely to conflict with Greenfield's public positioning, while middle-market implementation and adoption work aligns with it.
Firm-as-lab: validate internally before recommending
Greenfield says the consulting firm stress-tests every tool, workflow, and automation inside its own business before bringing it to a client.
Read more
One example: a six-week internal rebuild of client intake using AI-assisted document parsing and automated follow-up sequencing failed twice — parsing misfired on non-standard contract formats, and follow-up logic triggered out of order — before it held.
Only then did they offer a version to a client.
Greenfield names slower timelines and less tolerance for fast answers as the cost of that stance.
For brands planning a campaign
Partnerships that allow hands-on testing fit this posture; campaigns promising instant deployment or relying on unvalidated vendor claims do not. Be prepared for slower timelines and for Greenfield to test the tooling in their own operations first.
The posts follow a consistent structure: a one-line claim, a concrete first-person or observed business anecdote with numbers and roles, an explicit argument about what the failure actually was, a prescriptive method, and a closing question inviting readers to describe their own situations.
Read more
Posts run long for social media and use topic hashtags such as #AIImplementation, #MiddleMarket, #OperationalExcellence, #AIAdoption, #Founders, and #PersonalBrand. The same text appears on LinkedIn and Instagram, making the approach channel-adapted rather than channel-specific.
Lead with a specific observed situation, state the argument plainly, then ask the audience a direct question about their experience.
For brands planning a campaign
Contributions should be narrative, example-led, and end with a question that invites replies. Slogans, product features, and short promotional captions would be out of step with this account.
The posts here cover a small and recent window: seven copies of posts representing four distinct posts published on Instagram and LinkedIn, all from October 2026.
Read more
They contain no video or audio and no transcripts.
They show no sponsorship, vendor-partnership, or paid-placement formats, and the recent window means no conclusions can be drawn about how these themes developed over a longer period.
Any planning that depends on partnership history, earlier positioning, or format range beyond long-form text posts needs more information before it is treated as settled.
An absence of sponsorship posts in this sample is not evidence that Greenfield does or does not accept sponsorships.
For brands planning a campaign
A brief can focus on AI implementation, adoption training, and organizational decision-making. Before committing, ask Greenfield about sponsorship formats and the themes they have covered beyond this recent sample.
The posts name one business: ZGC, presented as the consulting firm behind the AI implementation work.
Read more
They don’t mention sponsorship, affiliate, client or investment relationships. Several unnamed companies appear as examples — a manufacturing VP's employer, a regional logistics company and a mid-size professional services firm — but not as brand relationships.
ZGC
Disclosed partnership
Posts written in the first-person plural describe ZGC testing AI tools and workflows inside its own business before bringing them to clients, including a six-week rebuild of its internal client intake process that failed twice before it held.
Read more
The writing presents the author as part of the firm ("at ZGC, the firm is the lab"), but doesn’t specify whether Greenfield owns or works for ZGC. Ask about their relationship to the firm.
Zack Greenfield's published work is a short set of long-form posts, mostly on LinkedIn, with the same texts also on Instagram.
Read more
The format repeats: a specific business scene with numbers and roles, a plain claim about why the outcome happened, and a direct question to the reader.
Read them as case notes rather than tips: each argument usually turns on the organizational side of a rollout, not the technology.
The most developed threads are AI adoption and implementation training, ownership of deployment decisions, and how a consultant narrows and tests their own offer.
Both write about software implementation and adoption as people and process problems, building their arguments from first-person business scenes rather than frameworks.
Read more
Nanney describes years as an enterprise implementation consultant at large companies and concludes that shipping software and solving the problem are not the same thing.
They argue that AI has sped up the front end of product work while roles, ownership and tooling fragment unless teams standardize how they work.
Greenfield makes the same case for AI rollouts: training and the approval path determine the outcome, not the tool.
Readers interested in why implementation fails despite working technology will recognize the argument.
Nanney's vantage is inside software, from enterprise ERP installations to product management, with tension arising between teams and product organizations. Greenfield's is external AI consulting for middle-market companies, where tension comes from department sign-off and testing tools inside the consulting firm before recommending them to clients.
Both advise mid-market leaders to choose a small number of high-impact moves and pair a practical framework with an explicit offer.
Read more
Hunshikatti argues that a fractional leader's value includes knowing which specialist to bring in and when, and uses an effort-versus-impact lens to identify the handful of initiatives worth pursuing next. Greenfield's posts end with a comparable prescription and a direct question, appealing to the same operating-leadership audience.
Hunshikatti's domain is marketing and growth leadership — fractional CMO work, demand generation, lifecycle and content specialists — while Greenfield's is AI implementation and adoption inside mid-market operations. Hunshikatti's posts also promote services more directly, including a named workshop, than Greenfield's case narratives.
Holley makes the same core move as Greenfield, locating operational failure in leadership alignment and decision ownership rather than tools or frontline execution.
Read more
Holley describes a plant where sales, finance and operations each protected a different priority while the plant manager served three masters.
In another example, a predictive number went ignored for two months because it was not on anyone's scorecard.
Both teach through a specific observed scene and close with a question to the reader.
Holley's setting is lean manufacturing and plant-floor metrics — takt time, WIP, OEE and weekly ops reviews.
Greenfield's is AI platform rollouts and consulting practice decisions in mid-market companies.
Holley stays closer to the shop floor and review room, while Greenfield focuses on executive decisions about who owns deployment.
Zack Greenfield's Instagram and LinkedIn posts support a topic-level placement decision, but they do not say who is in that audience.
Read more
The two accounts show the only measured audience numbers: 23,728 Instagram followers (observed 12 October 2026) and 3,603 LinkedIn followers (observed 11 October 2026).
Everything else is post content, not audience data.
The posts show what Greenfield publishes to those followers — AI rollout failures, adoption training built around daily tasks rather than software features, and middle-market decision bottlenecks — which is useful for judging whether the topics fit a campaign on AI adoption and implementation training.
They do not show that the followers are operations leaders, plant managers, or buyers with budget.
Zack Greenfield's posts do not include a demographic data, audience survey, or employer/occupation data.
Follower counts on two channels also say nothing about engagement rates, which vary widely and matter more for a sponsored placement than raw reach.
Concrete next step for the buyer: ask Greenfield for (1) reach and engagement results for recent posts on AI adoption or implementation training, covering the last 90 days, and (2) any audience survey or platform demographic data showing geography, age, and job seniority, so the composition question can be answered with data instead of inference.
Until then, treat this as a reasonable topic match with unverified audience composition.
Zack Greenfield's posts describe ZGC's consulting work but do not set out sponsorship packages, rates, deliverables, or a partnership contact.
Read more
Operationally, ZGC says it stress-tests every tool and workflow inside its own business before recommending it.
The firm describes a six-week internal rebuild of its client intake process that failed twice before it held.
That practice comes at the cost of speed: ZGC will not deploy a solution it has not already tested, and says executives seeking fast answers find the slower timeline frustrating.
The same approach shapes its training work, which starts with the tasks a person repeats daily rather than a software's feature list.
That takes longer upfront because it requires talking to staff before building anything.
Ask Greenfield directly whether they accept creator-side sponsorships or media partnerships, and how to inquire.
A mid-market operations consultancy selling AI adoption and enablement work wants a co-produced collaboration on implementation training: long-form pieces and a practical workshop to help operations leaders get a tool into daily use.
Read more
This is the strongest fit based on Greenfield’s posts, for four reasons.
First, the subject matter lines up almost exactly: their recurring argument is that rollouts fail when training covers software features instead of the decisions people make daily.
Second, the format matches.
They publish long, example-led pieces that open with a one-line claim, give a concrete business anecdote with numbers and roles, explain the real failure, prescribe a method, and close with a direct question.
Narrative case content, rather than slogans or product captions, fits how they already communicate.
Third, the positioning is compatible.
They write about deliberately narrowing a practice to helping middle-market companies cut through AI hype and build systems that work—the same buyer a mid-market operations consultancy is chasing.
Fourth, they offer a usable operating claim: tools are stress-tested inside their own firm before being recommended to clients, with slower timelines as the cost.
For a consultancy selling adoption work, a partner who publicly accepts slower, validated rollouts over fast, unvalidated ones is a credible voice, not a liability.
Two points need settling before a campaign.
The two social profiles show 23,728 Instagram followers (observed 12 October 2026) and 3,603 LinkedIn followers (observed 11 October 2026), but no demographic or engagement data is published.
Ask for audience and performance data before promising reach among operations leaders.
No sponsorship format, rate, or partnership contact appears in the posts, so settle the commercial terms directly.
When to choose a specialist
An enterprise AI platform vendor wants a fast, feature-led product launch: short promotional captions, a demo-first walkthrough of new capabilities, and reach measured mainly by follower counts and posting cadence.
Read more
This campaign conflicts with Greenfield’s posts on content, tone, and pace.
On content, it inverts the method they state most clearly: the tool should answer a problem the audience already feels, not be a capability they are told to get excited about.
They explicitly frame feature-focused training as the reason a company reached 11% adoption after spending $80,000.
A launch built around capability announcements would contradict their published diagnosis.
On tone, the account runs on long, first-person or observed business stories with specific numbers and roles, ending in a question that invites readers to describe their own experience.
Short promotional captions do not match that pattern and would read as out of place on the profile.
The posts do not show a documented sponsorship or paid-placement format, so ask whether they offer vendor-led launches and on what terms.
Audience composition is also unverified: follower counts on two channels do not show whether followers are operations leaders with budget, and engagement rates are not available.
Ask for those metrics before making reach the campaign’s main measure.
Pace is another mismatch.
They say unvalidated solutions are not deployed and executives wanting fast answers find the slower timeline frustrating, which sits poorly with a launch calendar driven by a release date.
A narrower version could work if rebuilt around a named operational problem the tool solves, with enough lead time for testing and a story-led format.
As written, it asks for the opposite of what their posts support.
A worked campaign example
A worked angle for an implementation-training collaboration with a mid-market operations consultancy, built on the strongest material in Greenfield’s posts.
Anchor piece: a co-created long-form article titled around the factory-floor failure—why AI rollout training dies where the work actually happens.
The spine is their case: leadership approves an initiative, IT and sometimes power users get trained, and the rollout stalls in every department that was not in the room.
The specific example is a manufacturing VP whose company spent $80,000 on an enterprise AI platform and reached 11% adoption six months later, with two days of training covering features and nobody mapping which daily tasks the tool was meant to improve.
The corrective method is the useful half: start with the job by listing the decisions a person makes repeatedly, where they lose time, and what they hand off; then build the curriculum around that.
The $80,000 and 11% figures are their own account, so re-verify them or present them as a case they reported rather than established results.
Second deliverable: a 90-minute working session or recorded workshop that applies the method live to one role at the partner consultancy’s client—map the repeated decisions first, then show where the tool fits, so the audience sees the sequence rather than just the conclusion.
Third deliverable: a one-page worksheet readers can complete without the article, capturing repeated decisions, time losses, and handoffs for a named role.
This mirrors the prescriptive, resource-style output readers ask for and gives the partner something to hand to a client.
Distribution and voice: keep the long, example-led structure of their posts, open with the failure rather than the tool, and close by asking readers what their own rollout training actually covered—features or workflows.
Reuse the topic hashtags they already use on these posts.
Campaign angle in one line: education is the implementation, so the collaboration sells a method for mapping work before software, not a platform.
Before committing, ask for reach and engagement on recent AI adoption or implementation-training posts over the last 90 days, and for any audience survey or platform demographic data covering geography, age, and job seniority.
Also settle directly whether they accept this kind of sponsorship and on what terms, since no format, rate, or inquiry route appears in the posts.
A better choice when the collaboration's most credible voice belongs to someone who has sat on the receiving end of a software rollout that went wrong and now builds the product.
Read more
Nanney's account describes years as an implementation consultant driving installs and training at large enterprises — Compaq Computers, Phillips Petroleum, Union Carbide — for rigid ERP systems.
In their telling, the people who built the software never asked the people who had to use it what they needed, so some processes came out slower and clunkier and delivered on time but wrong.
Nanney describes becoming the person customers vented to, then moving into product management with that experience and carrying the rule that shipping software and solving the problem are not the same thing.
A second post names the current version of the same shift: AI has compressed the research, requirements, and business-case front end of product work; the bottleneck has moved into how teams operate; and the real risk is fragmentation when every team runs its own tools instead of one standard system.
For a consultancy whose campaign angle is why adoption dies after go-live, Nanney can speak to the builder-vendor side of the same failure, not just the buyer side.
The subject is product-team workflow and the software vendor's own choices, not operations-leader rollout training.
Nanney's posts do not cover curriculum design, mapping a role's daily decisions, or the executive-decision problem, so the practical how-to half of Greenfield's angle would need another voice.
Two short LinkedIn posts dated May and June 2026 do not show depth across formats and time.
Ask for partnership and commercial details before proceeding.
A better choice when the buyer wants a partner whose promise is prioritization and assembling the right specialists rather than AI implementation itself.
Read more
Hunshikatti writes from a fractional-CMO frame and argues that the value of fractional leadership is not only the person hired but who they already know how to bring in, naming demand generation and platform scaling, content strategy and case-study storytelling, lifecycle marketing and program management, and modern go-to-market automation as separate crafts.
A second post lays out the sorting method directly: run every initiative through effort versus impact and split the list into quick wins, foundational must-dos, roadmap items that need real resourcing, and bets made only after the first three, with most of what sits on a leadership whiteboard falling into that last bucket.
Hunshikatti also publishes a workshop offer — CMO for a Day — that puts the CEO, sales leadership, operations, and the tech lead in one room to agree on five priorities for the next 90 days.
That maps closely onto an operations consultancy's sales motion, where the first deliverable is usually helping a client decide what to do rather than building it.
The method is about choosing what to work on, not getting a tool into daily use.
Nanney's posts contain no AI rollout material or implementation-training content, so a collaboration framed around adoption and training would be a topic stretch.
Nanney already sells a workshop with a direct-message call to action, which complicates a co-produced offer.
Two LinkedIn posts dated September and October 2026 do not publish rates, formats, or partnership terms.
A better choice when the audience is plant and manufacturing leadership and the argument should land above the shop floor.
Read more
Holley's posts place the failure in the executive room rather than on the line.
In one, a strategy review for a portfolio company had sales chasing new SKUs and finance cutting working capital while operations was already stretched.
Nobody in the room disagreed with lean principles, but three different definitions of priority walked out; six weeks later, the plant manager was serving three masters with one crew.
In the other, a weekly operations review ran forty-five minutes over twelve slides, with one line yellow for eleven straight weeks that nobody asked about because the metric did not roll up to corporate and was therefore not on anyone's scorecard.
Holley's conclusion is that reviewing metrics is a decision about what matters enough to interrupt your week, and that the metric nobody official asks about is usually the one worth attention.
That is the same organizational-ownership diagnosis Greenfield applies to AI scaling, translated into manufacturing operations language and grounded in observed reviews.
Manufacturing-specific and not about AI adoption or training.
Holley's posts cover lean, continuous improvement, and metrics discipline, so an AI implementation collaboration would need to be reframed around those themes rather than used as-is.
The fit for an operations consultancy would depend on the quality of that reframing, not on AI subject-matter depth in the posts.
Two LinkedIn posts dated September 2026 are cited here.
Ask for commercial and partnership details before proceeding.
Seven posts by Zack Greenfield on LinkedIn and Instagram were observed in October 2026.
The seven resolve to four distinct texts because the same wording appears on both channels.
Instagram listed 23,728 followers (observed 12 October 2026), and LinkedIn listed 3,603 followers (observed 11 October 2026).
The posts themselves carry no publication dates.
The posts here include no video, audio, transcripts, long-form articles, or older posts, so they do not show how Greenfield's positions changed over a longer period or how they come across in spoken or long-form formats.
Figures in the posts, including an $80,000 platform spend, 11% adoption, 11% fuel savings, and a 40-truck pilot fleet, are Greenfield's own account and were not independently verified.
The posts here do not mention a sponsorship format, rate, partnership contact, or audience demographic data; those remain open questions rather than settled facts.
