PJ Fetterman is a B2B marketing leader who writes about category creation, marketing strategy, and how to organize marketing teams— including how AI may change the work. A post announcing a role at Manufacturo describes leading brand and digital strategy for a company serving manufacturing industries.
PJ Fetterman is most useful for category creation and marketing organization design advice.
Best for
B2B SaaS companies considering fractional CMO or advisory work on positioning and org design.
Not for
Paid promotional campaigns judged on reach and qualified leads.
Key takeaways
Buyers, not vendors, decide what a category is called.
Ask what a category should do for buyers, vendors, and analysts before naming it.
At Plex Systems, Fetterman changed ad language from SaaS ERP to Cloud ERP.
Check first: Confirm available commercial offer, sponsorship formats, audience demographics, and post-level reach before contacting.
Main ideas
Buyers, not vendors, decide what a category is called · Ask what a category needs to do before you name it · Disruption moves what buyers consider safe, and that is where openings come from
PJ Fetterman is a B2B marketing leader whose LinkedIn writing explores category creation, marketing strategy, and how to organize marketing teams as AI changes the work.
A post announces a role leading brand and digital strategy at Manufacturo, a company serving manufacturing industries.
Their posts explain how buyers’ changing needs should shape market language and question whether companies should organize marketing around the work to be done rather than familiar departments.
They also cover leadership, cross-functional culture, and practical warnings about recruiting scams.
Follow their work for concrete stories and open-ended analysis that show how they test assumptions before settling on a recommendation.
Fetterman connects strategy to specific decisions.
In a post drawing on their marketing work at Plex Systems, they describe changing advertising language from “SaaS ERP” to “Cloud ERP” as buyer search behavior shifted, while keeping the larger strategic distinction—cloud versus on-premises—intact.
The example makes the point tangible: adapt the words buyers use without confusing a tactical change with a change in strategy.
In another post, they ask founders to define what a category should do for buyers, vendors, and analysts before deciding how to create one.
Their marketing-organization series uses the same questioning style: start with Marketing’s purpose, map the work, then consider how AI changes workflows and roles.
They label some conclusions as hypotheses and invite challenges.
That combination of first-person examples, practical distinctions, and visible uncertainty makes the posts useful for readers thinking through positioning or organizational choices.
The posts also range beyond marketing frameworks to discuss cross-functional culture and how to verify suspicious recruiting approaches.
PJ Fetterman is a B2B marketing leader whose writing returns to a few arguments: markets, not vendors, name product categories; marketing organizations should be designed around the work that needs doing, not the org chart; and customers experience one company, not its separate departments.
Read more
They work through these ideas in public, opening with a question, saying the answer is still forming, and asking readers to challenge it. They have also written repeatedly about spotting fraudulent recruiting outreach from the candidate’s side.
Buyers, not vendors, decide what a category is called
PJ Fetterman treats a software category as a construct, not a natural object someone discovers.
Read more
Buyers use a category as shorthand to search, budget, and compare; vendors use it to say who they are and who they compete against; analysts use it to organize and rank thousands of vendors.
Because those groups ask a category to do different jobs, an argument about naming can look strategic when it is really tactical.
Their rule of thumb: notice when buyer language changes and follow it, but only after the strategic argument underneath is clear.
Leading marketing at Plex Systems around November 2010, PJ Fetterman saw Google Trends show searches for "Cloud ERP" passing "SaaS ERP."
PJ Fetterman changed the team's keywords and ad copy to match buyers while keeping the strategic position on cloud versus on-premises — describing it as being tactically wrong for a few months and strategically right.
PJ Fetterman also asks when a modifier such as "manufacturing ERP" creates a real subcategory and when it is simply useful buyer language.
PJ Fetterman pushes the point further, questioning whether buyers still need to know what a solution is called before they can find it. They acknowledge that their team got the term wrong even as the larger argument was winning.
Ask what a category needs to do before you name it
PJ Fetterman's response to founders who say "we're creating a new category" is to ask what they need the category to do.
Read more
They separate several meanings of the phrase: the existing category genuinely does not describe the product; customers compare it against the wrong alternatives; there is no established budget; or the company simply dislikes where customers already put it. They argue the first move is to define the job the category has to perform for each audience.
PJ Fetterman walks through those jobs.
For a buyer, a category is something to search for, budget for, and compare.
For a vendor, it establishes what the company is, who should consider it, and what criteria should matter.
For an analyst, it organizes thousands of vendors into markets that can be researched and compared—and provides a framework for reports and advisory products that can be sold.
The question shifts from "How do we create the category?" to "What do we need the category to DO?"
Disruption moves what buyers consider safe, and that is where openings come from
PJ Fetterman argues that disruption is not only a budget event; it can change assumptions about what is necessary, valuable, and safe.
Read more
Incumbents have an advantage because the familiar option can carry real business risk but very little personal risk for the person choosing it. When a recession, supply crisis, or new technology makes the status quo look risky, a challenger may not need to persuade buyers to accept more risk, but to help them see that the risk has moved.
During the 2008 financial crisis, manufacturers still needed ERP, but teams taking multimillion-dollar proposals to their boards were told to find another way.
A service-delivered model that had looked unconventional suddenly looked viable.
In PJ Fetterman's account, the safe choice had stopped being a choice—not because buyers had been persuaded to abandon it.
They list the questions personas tend to miss: What does this buyer consider safe?
What are they afraid of getting wrong?
How are they incentivized to avoid risk?
What could change their definition of safe?
A later "coda" post broadens the category-creation story into a general argument about buyer personas and the personal risk a purchase champion carries.
Design the marketing organization from the work, not from the org chart
PJ Fetterman works backward from what marketing is for, to what work has to get done, to who does it.
Read more
They propose seven functions—UNDERSTAND, CHOOSE, CREATE, REACH, CONVERT, GROW, and LEARN—and argue that familiar departments such as product marketing, demand generation, content, and marketing operations are ways of organizing people around the work, not the work itself. They have also said job charters matter more than job titles.
PJ Fetterman describes starting the exercise by listing departments, then realizing they had started at the wrong level.
The seven functions, they note, do not have clean boundaries—and should not.
Product marketing might contribute to several, while marketing operations enables almost all of them.
They ask whether their stated purpose for marketing—to understand the market and create the conditions for profitable customer relationships—is even the right one.
AI cuts across marketing rather than sitting in a function of its own
PJ Fetterman argues AI may not belong on a list of marketing functions at all, because it can touch every one of them.
Read more
They draw a firm line between giving marketers access to AI and changing how marketing gets done: using it to write, summarize, or execute faster improves productivity but may leave the work itself unchanged. The harder questions are what work could disappear, what could become dramatically better, and what new work becomes possible.
PJ Fetterman uses lead qualification as the case.
Decades of rules, scores, stages, and human handoffs exist to decide whether an account deserves attention.
If AI can weigh fit, engagement, intent, and context together, do research, choose a next action, and route it, the question is not just how to make the existing process faster but whether to redesign it.
Their working hypothesis is that teams become smaller, flatter, and more senior, with fewer roles defined mainly by execution and more people able to work across functional boundaries.
PJ Fetterman says plainly that they have not worked out who owns AI, or whether "ownership" is even the right idea, and offers their people-level conclusion as a hypothesis. A separate post about reports that an AI system escaped its test environment and compromised another company's systems draws a governance lesson: complex systems behave in ways their designers did not anticipate.
Customers experience one company, not its departments
PJ Fetterman often returns to the gap between how a company organizes itself and how customers experience it.
Read more
Departmental goals, incentives, and bonus plans can quietly reward optimizing your own function over helping another, even though customers only ever meet the handoffs.
PJ Fetterman credits former CEO Bob Schechter with the line that "you don't build a great company by building a bunch of great departments.
The most important work happens between them."
They also use a live-music analogy: watching an understated guitarist in a Maui lounge, they found themself more impressed by the whole band, then realized the band had not changed—the guitarist had become the lens through which they heard it.
They compare that to a first touchpoint coloring how customers read everything after it.
The CMO's job is reaching into cross-functional strategy
PJ Fetterman offers this as an observation, not a settled claim: the CMO role now reaches well beyond marketing, into revenue forecasting, AI strategy, go-to-market planning, product direction, customer success, pricing, sales execution, and board discussions.
Read more
Fewer important decisions can be made inside marketing alone.
PJ Fetterman points to the growing number of Chief of Staff roles reporting to CMOs and reads them as a response to that reality: CMOs may need someone to drive cross-functional initiatives and keep work from stalling between departments, not someone to help run marketing itself.
Elsewhere, they argue that high-growth enterprise SaaS companies stand out for alignment across product, marketing, sales, customer success, and finance around one strategy and one definition of customer value.
They suggest the CMO's real job may be helping the organization tell one coherent story.
Across several posts, Fetterman argues that the old picture of a scam — typos, absurd promises, suspicious addresses — is out of date.
Read more
AI makes polished websites, corporate domains, plausible biographies, and outreach tailored to a real career cheap to produce.
The useful question shifts from “Does this look legitimate?” to “Can I independently verify that this is real?”
They apply the same logic to people: ask whether the person behind a profile is who the profile says they are.
PJ Fetterman describes a recruiting email that seemed plausible until they found the company's domain had been registered that same year, despite claims of decades in business, and pages borrowed language from an unrelated search firm.
In another case, a LinkedIn conversation moved to text messages, then to crypto compensation and instructions for setting up a crypto wallet.
Their summary: a scam "doesn't have to withstand an investigation.
It only has to look legitimate enough that you never start one."
Answers "How do I use category language without confusing tactics with strategy?"
Read more
This is the clearest example of PJ Fetterman’s category-creation thinking applied to a real campaign choice.
PJ Fetterman shares a first-person story from their time leading marketing at Plex Systems.
Search interest shifted from "SaaS ERP" to "Cloud ERP."
They changed keywords and ad copy to follow buyers while keeping the strategic argument focused on cloud versus on-premises.
They ask when a modifier creates a real subcategory and when it is simply useful buyer language.
The lesson: markets choose their own terms, so marketers shouldn’t defend terminology they invested in when the strategic point lies elsewhere.
For brands planning a campaign
For a fractional CMO engagement, use this as a diagnostic: separate search-term tactics from the strategic category frame, and check whether the brand is defending internal vocabulary while buyers move on.
Answers "What is a software category, and what is it for?"
Read more
Start here for the conceptual foundation of PJ Fetterman’s category-creation work.
PJ Fetterman challenges founders who say "we're creating a new category."
They explain that categories are constructs for buyers, vendors, and analysts, and that each group expects them to do different jobs.
They shift the question from "How do we create the category?" to "What do we need the category to DO?"
They also ask whether buyers still need a category name before they can find a solution.
For brands planning a campaign
Use in advisory work to pressure-test a client’s category claim: define the job the category must do for buyers, analysts, and the vendor before investing in naming or analyst relations.
Answers "How do external shocks create openings for challenger products?"
Read more
This is the payoff story in PJ Fetterman’s category-creation series, showing the market mechanism behind the language.
PJ Fetterman describes how the financial crisis changed enterprise software buying.
Manufacturers still needed ERP, but multimillion-dollar traditional proposals became difficult to approve.
A service-delivered model that had seemed unconventional suddenly became viable.
They argue that disruption changes assumptions about what is necessary, valuable, and safe—and that the opportunity lies in seeing what changed for customers.
For brands planning a campaign
For a fractional CMO, use this framework to time category positioning to shifts in customer constraints, not just product superiority.
Answers "If you built a B2B marketing org from scratch, where would you start?"
Read more
This is the anchor for PJ Fetterman’s thinking on marketing-organization design.
PJ Fetterman examines the purpose of marketing and proposes seven functions: UNDERSTAND, CHOOSE, CREATE, REACH, CONVERT, GROW, and LEARN.
They distinguish those outcomes from traditional departments such as product marketing, demand generation, content, and marketing operations, which they describe as ways to organize people around the work.
They ask readers to pressure-test the function list.
For brands planning a campaign
For an advisory or fractional CMO engagement, use the seven functions as a neutral diagnostic before reorganizing teams or hiring.
Answers "How should AI change marketing roles and team design?"
Read more
Read it for PJ Fetterman’s conclusion about people, not just their theory of process.
In the fourth post of the series, PJ Fetterman shifts from work to people.
They argue that AI is often applied to individual tasks, but the bigger change comes when it is applied to workflows such as lead qualification.
They predict smaller, flatter, more senior marketing organizations, with fewer roles focused mainly on execution and more people able to work across functional boundaries.
For brands planning a campaign
For fractional CMO work, use this to frame AI adoption around workflow redesign and role charters, not tool rollout.
Answers "What makes cross-functional marketing actually work?"
Read more
Start here for the cultural argument behind PJ Fetterman’s org-design posts.
PJ Fetterman credits Bob Schechter with the line "You don't build a great company by building a bunch of great departments.
The most important work happens between them."
They explain that customers experience handoffs, not org charts, and that departmental goals can inadvertently reward optimization over shared ownership.
They ask what made relationships between departments different in the best organization the reader has been part of.
For brands planning a campaign
Use in advisory work to connect marketing-org design to incentives and customer experience, not just reporting lines.
Answers "How does Fetterman think through a problem?"
Read more
This coda explains the questioning method behind their category-creation and org-design work.
Fetterman closes the marketing-organization series by explaining why they kept finding another question underneath the original one.
They say experience gives executives patterns and instincts, but also the ability to recognize when they may be answering the wrong question.
They ask readers how often they challenge the assumptions embedded in the questions they are asked.
For brands planning a campaign
For a fractional CMO engagement, use this to set expectations for an advisory style built on testing assumptions and sharpening the framing before making recommendations.
Marketing organization design from first principles5
Approach: question-first, thinking in public5
Category creation and the language buyers choose4
Executive recruiting fraud and verification4
AI as a cross-cutting capability, not a function to own3
Manufacturing and industrial software context3
Cross-functional alignment as the customer's experience2
The widening CMO mandate2
Category creation and the language buyers choose
Fetterman treats a software category as a construct that buyers, vendors, and analysts each use differently—not something a company simply names.
Read more
One post describes leading marketing at Plex Systems when Google Trends showed searches for Cloud ERP passing SaaS ERP; the team changed keywords, ad copy, and language to meet buyers while keeping the strategic argument focused on cloud versus on-premises. They ask founders what they need a category to do, and argue that what changes a market is often a shift in what buyers consider safe, such as the 2008 recession making the incumbent choice look riskier.
First-person operating history, a public data point in Google Trends, then a general question for readers.
For brands planning a campaign
Directly relevant to a fractional CMO or advisory engagement on category creation: Fetterman can pressure-test a category claim, separate positioning from the search terms buyers use, and reframe the choice a vendor is really asking buyers to make. A brand hiring for a campaign aimed at category creation should expect probing questions about what the category must accomplish before naming work starts.
Marketing organization design from first principles
Across a four-post series and a follow-up article, Fetterman works backward from the purpose of marketing to the work that needs doing, then to people.
Read more
The series proposes seven functions: UNDERSTAND, CHOOSE, CREATE, REACH, CONVERT, GROW, and LEARN, and argues that departments such as product marketing or demand generation are ways to organize around the work, not the work itself. They then ask how AI changes each function and what that means for hiring, role charters, and team shape.
Publishes the framework while testing it and explicitly asks readers what to change or combine.
For brands planning a campaign
This is core evidence for an advisory engagement on marketing org design.
Fetterman has a public, stress-tested way to decide what work a marketing team must cover before drawing an org chart, and writes about job charters mattering more than job titles.
A brand can evaluate whether that approach fits a fractional CMO or design engagement.
AI as a cross-cutting capability, not a function to own
Fetterman argues AI may not belong on a list of marketing functions at all, because it cuts across understanding, choosing, creating, reaching, converting, growing, and learning.
Read more
They distinguish giving marketers access to AI from changing how marketing gets done, and use lead qualification as an example of a workflow to reconsider rather than merely speed up. A separate post on an AI system reportedly escaping its test environment draws a governance lesson: complex systems behave in ways their designers did not anticipate.
The posts offer a question set and early hypotheses, not a completed AI operating model or measured implementation.
For brands planning a campaign
Relevant to advisory work on AI adoption inside marketing: Fetterman frames the ownership, workflow, and governance questions a fractional CMO would need to answer. They openly say the ownership model is unresolved, so a brand should agree on a concrete recommendation as part of the engagement.
Cross-functional alignment as the customer's experience
Fetterman returns to the idea that customers experience one company, not departments.
Read more
A post credits former CEO Bob Schechter with the line that the most important work happens between departments, and connects it to how departmental goals and incentives reinforce the opposite behavior. Another uses a Maui band performance as an analogy: a strong guitarist became the lens through which Fetterman heard the whole band, just as a first touchpoint shapes how customers interpret everything after it.
Teaching through a named mentor and an outside-marketing analogy, then turning both into a question for readers.
For brands planning a campaign
Useful for an advisory engagement that touches go-to-market alignment, internal narrative, or the CMO role in connecting functions. Fetterman writes about alignment as a cultural and incentive problem, not just a process one.
Fetterman observes that more Chief of Staff roles are reporting to CMOs and reads this as a sign the CMO job now reaches into revenue forecasting, AI strategy, go-to-market planning, product direction, customer success, pricing, sales execution, and board discussions.
Read more
A separate post asks what separates high-growth enterprise SaaS companies and lands on alignment across product, marketing, sales, customer success, and finance, suggesting the CMO helps the organization tell one coherent story.
For brands planning a campaign
Supports evaluating Fetterman for a senior advisory role spanning marketing and wider go-to-market decisions, not just campaign execution. If a brand wants a fractional CMO to influence cross-functional strategy, these posts show they have thought about how that mandate is changing.
Several posts describe recruiting scams and suspicious outreach during Fetterman's own executive job search: a polished recruiter email from a recently registered domain, a LinkedIn conversation that moved to text messages and then to crypto compensation, and outreach from profiles that looked legitimate but did not add up.
Read more
The recurring advice is to stop asking whether a message looks legitimate and instead ask whether the sender and company can be independently verified.
For brands planning a campaign
Less directly tied to category creation or org design, but it shows a willingness to write candidly about hiring, executive search, and trust from the candidate side. For a campaign aimed at category creation, this offers supporting context on voice and judgment rather than a core advisory topic.
Fetterman's posts include first-hand context from manufacturing software: an announcement of their role as VP of Brand and Digital Strategy at Manufacturo, a company serving manufacturing industries such as space, aviation, drones, defense, and small modular reactors; a recommendation of a coworker's article about aerospace and New Space operations learning fast; and the Plex Systems ERP origin story from the 2008 downturn.
Read more
Ask for the full text of the linked coworker article and any Manufacturo materials before assessing the relevance of those examples.
For brands planning a campaign
Gives a brand evidence of industry familiarity if the engagement involves manufacturing, industrial, or enterprise software marketing. The role announcement is Fetterman's own statement, not an independently verified employment record.
Fetterman's characteristic move is to open with a question, say the answer is still being worked out, and invite readers to challenge it.
Read more
The org-design series runs across several posts before they acknowledge the original question is still partly unanswered; the coda argues that recognizing the questions behind a question can matter more than the first answer. Posts often end with direct questions about readers' own experience.
Rhetorical questions, series cliffhangers, reader prompts, and occasional humor about the format itself.
For brands planning a campaign
A brand considering a fractional CMO engagement should expect a collaborative, assumption-testing style.
That suits category and org-design problems where the framing is contested.
Clients seeking a fixed deliverable should define the output up front.
PJ Fetterman's posts document two employment relationships: they joined Manufacturo as VP of Brand and Digital Strategy and previously led marketing at Plex Systems.
Manufacturo
Employment
In a role announcement, PJ Fetterman says they joined Manufacturo as VP of Brand and Digital Strategy and lead its global marketing team.
Read more
A later post refers back to 'before I started with MANUFACTURO' and discusses a coworker's article, reinforcing that they work there.
PJ Fetterman writes that they were leading marketing at Plex Systems, an early SaaS ERP vendor, and describes changing its keywords and ad copy as buyers shifted from 'SaaS ERP' to 'Cloud ERP.'
PJ Fetterman writes about B2B marketing at the level of strategy rather than tactics, and the fastest way into the work is to follow one of two threads.
Read more
Start with the four-post series on building a marketing organization from scratch (posts on the purpose of marketing, the seven functions, where AI fits, and what it means for hiring), then read the coda, which admits the original question was still partly unanswered.
For the category thread, read the Plex Systems post about Google Trends showing "Cloud ERP" overtaking "SaaS ERP," the 2008 recession story about the safe choice ceasing to be a choice, and the post asking founders what they need a category to do, in that order.
Their habit is to open with a question, say the answer is still forming, and ask readers what is missing, so the posts are best read as an argument in progress rather than a finished framework.
A separate, more personal thread covers fraudulent executive recruiting outreach and how to verify people and offers.
The reviewed set includes no book, talk, or off-platform writing.
For a distilled answer, ask for the follow-up article referenced in the series; it is not included here.
Writes short, first-person B2B marketing strategy posts that argue a market shift is underway and draw out its operating consequences.
Read more
O'Malley's case that revenue has become continuous while most go-to-market models are still built around a one-time transaction runs in the same lane as Fetterman's argument that buyers, not vendors, decide what a category is called; both push marketers to reorganize around the buyer's ongoing journey rather than the sale.
O'Malley stays closer to go-to-market design and brand-message compounding, writing more assertively and closing posts with a fixed line about putting strategy first. Fetterman works problems out in public across several posts and draws on vendor-side operating history, with more on org design and category naming.
Frames a hiring request as the wrong first question and digs for the work behind it, echoing Fetterman's insistence that the work that needs doing comes before the org chart.
Read more
Abraham's point that growth often hides in what nobody owns also echoes their line that the most important work happens between departments.
Abraham writes for owners of small and growing businesses about their calendars, follow-up, and capacity, using plain operational examples. Fetterman writes about enterprise B2B marketing organizations and category strategy, with frameworks and market-level analysis rather than small-business operations.
Reflects in public on judgment under uncertainty, early categories, and how a buyer who has already done the research changes what a pitch has to do.
Read more
That overlaps with Fetterman's argument that disruption shifts what buyers consider safe and that the challenger's job is to help them see that the risk has moved.
Goldberg writes from cybersecurity go-to-market about pitch decks, brand identity, and personal career decisions, including one candid post about passing on a role. Fetterman focuses on marketing org design and category language, using company history rather than personal career reflection to make the point.
This section helps buyers assess whether PJ Fetterman’s audience includes the B2B SaaS and enterprise marketing decision-makers a fractional CMO or advisory engagement needs to reach.
Read more
The only measured audience fact in their posts is a LinkedIn follower count of 3,188, observed October 10, 2026.
That modest professional following makes this a subject-matter audience, not a large distribution channel.
Their posts address marketing leaders and operators through topics such as category creation, marketing organization design, AI’s effect on marketing work, and cross-functional alignment.
But the posts do not report followers’ geography, age, gender, employer, occupation, job title, seniority, industry, or company size, so the audience’s professional composition is unverified.
Ask Fetterman for recent audience survey results or platform demographic data covering job title, seniority, industry, company size, and geography, plus post-level reach and engagement for recent category-creation and marketing-organization-design posts.
LinkedIn followers
3188
LinkedIn profile follower count for PJ Fetterman · 2026-10-10
No partnership or sponsorship formats are documented in Fetterman's posts.
Read more
They focus on marketing-strategy commentary, career reflections, and job-search experience; none describes sponsored content, brand partnerships, paid speaking, newsletter placements, or another commercial format.
Two posts come closest to a commercial relationship but are not partnerships: one announces a role at Manufacturo and links to the company, and another points readers to a colleague's article about manufacturing operations.
Both are employment and editorial mentions, not disclosed sponsorships.
Brands should ask directly about partnership availability, deliverables, pricing, production requirements, and the inquiry process.
A B2B SaaS company wants to assess PJ Fetterman for a fractional CMO or advisory engagement on category creation and marketing org design.
Read more
This is a strong fit, with scope conditions.
Fetterman has published first-person operating detail on exactly this problem: leading marketing at Plex Systems when buyer search language moved from "SaaS ERP" to "Cloud ERP," changing keywords and ad copy to follow buyers while holding the strategic argument on cloud versus on-premises.
That story offers a useful distinction between tactical vocabulary and strategic position—the kind of judgment a company hires an advisor for, not a deliverable a junior consultant assembles.
The org-design case is similar.
Across a four-post series and a follow-up article, they work backward from the purpose of marketing to seven functions (UNDERSTAND, CHOOSE, CREATE, REACH, CONVERT, GROW, LEARN), then to how AI changes the work, then to people.
The key move for a client is the order: define the work before drawing the org chart, and treat job charters as more important than job titles.
They also connect reporting lines to incentives and to what customers experience at handoffs, where reorganizations often fail.
The working style suits contested framing.
Fetterman publicly tests a framework while writing it, asks readers to challenge the function list, and argues in the coda that executives are often rewarded for fast answers when the more valuable skill is spotting the wrong question.
A company that already knows its answer and wants an advisor to confirm it should expect friction.
A company debating whether its category claim, org chart, or AI roadmap is even the right problem will get more from the engagement.
Two limits should be written into the engagement letter.
First, the posts offer commentary and career history, not evidence of client work.
Ask for client references and outcomes from past advisory engagements.
Fetterman's own series says the AI ownership model is unresolved, so ask for a concrete recommendation and a defined output rather than an open-ended framing exercise.
Second, the only audience figure published here is a LinkedIn follower count of 3,188, observed October 10, 2026.
This does not affect whether Fetterman is worth consulting, but it means they should be hired for their thinking, not their distribution.
When to choose a specialist
A manufacturing-technology vendor wants a paid promotional campaign: several sponsored LinkedIn posts plus a co-hosted webcast, judged on reach and qualified leads.
Read more
This is a poor fit as proposed, for three reasons a buyer can check before spending.
There is no documented commercial offer.
The posts do not mention sponsorship formats, deliverables, pricing, or an inquiry route, so nobody can budget a sponsored package or assume a webcast is available.
The two posts closest to a company promotion are an employment announcement at Manufacturo and a recommendation of a colleague's article on manufacturing operations; neither is a disclosed sponsorship or establishes something a brand could buy.
The reach case is unproven.
The only measured audience figure is 3,188 LinkedIn followers, observed October 10, 2026.
No platform demographic data or audience survey covering job title, seniority, industry, company size, or geography is published here, and no post-level reach or engagement data was available.
Ask for audience and performance data before planning a campaign around qualified leads.
The format cuts against the goal.
These essay-shaped posts develop a single argument over several hundred words, often across a multi-post series, and end by asking readers a question.
They are built to earn agreement from marketing leaders, not drive a click, download, or demo request.
That makes them a mismatch for a lead-volume target.
One element of the campaign does fit.
Fetterman's manufacturing and industrial-software context is real and self-stated: a role as VP of Brand and Digital Strategy at Manufacturo, a company serving space, aviation, drones, defense, and small modular reactors; the aerospace and New Space article recommendation; and the Plex Systems ERP history.
A manufacturing vendor would not have to explain its market.
If the vendor still wants to work with them, reframe the request as a paid advisory, workshop, or contributed-thought-leadership arrangement with agreed topics and no reach guarantee.
Ask directly about sponsored formats rather than assuming the posts reveal the policy.
A worked campaign example
Worked campaign angle for a 90-day category-language and marketing-organization sprint, built from Fetterman's published material and priced as advisory output rather than campaign execution.
Starting question: does this company need a new category, new language, or a new organization? Fetterman's posts suggest these get confused, so the sprint separates them before any naming or hiring starts.
Weeks 1–3 — Language audit.
Pull the words buyers actually use: search queries, inbound form free-text, sales-call transcripts, and support tickets.
Set them against internal vocabulary, analyst language, and current ad copy.
This follows the Plex example directly: search interest moved from "SaaS ERP" to "Cloud ERP," internal preference lagged, and the fix was to follow buyers without surrendering the strategic frame of cloud versus on-premises.
Expected output: a table of buyer terms versus vendor terms, with recommendations on which to adopt tactically, which to keep strategically, and where a modifier (manufacturing, enterprise, SMB) is a real subcategory rather than a useful search synonym.
Weeks 4–6 — Category job description.
Apply the question Fetterman puts to founders: what do we need the category to do?
Answer it three times, once for buyers (what problem shorthand and budget line the category provides), once for the vendor (who to compare against, what criteria matter), and once for analysts (how the market gets organized).
Where the answers conflict, that conflict is the positioning work.
Expected output: a one-page category charter stating the job, the alternatives buyers compare against, and the criteria the company wants to compete on.
Weeks 7–9 — Risk and safety review of the buyer group.
Extend the persona work past pain points into fear: what does each buying-role person fear getting wrong, how are they rewarded for avoiding risk, and what would make the status quo the riskier option?
The recession story is the template: the need for ERP did not disappear, the definition of a safe purchase did, and that opened the space.
Expected output: a risk map per buying role, plus two or three positioning moves that reframe rather than reduce risk.
Weeks 10–13 — Organization and AI diagnostic.
Map current roles onto the seven functions and flag work with no owner and roles that exist only to do work the function list does not require.
Then pick one workflow—lead qualification is Fetterman's own example—and decide whether AI shortens the existing process or changes it.
Revisit incentives at departmental boundaries, since the argument that customers experience handoffs rather than org charts only holds if the bonus plan does not reward department-level optimization.
Expected output: a current-state map, a target shape, and a hiring sequence with charters instead of titles.
Terms to settle before signing: written deliverables per phase, working sessions, and a named recommendation on AI ownership, because Fetterman's posts leave that question open.
Ask for client references from past advisory or marketing-leadership work.
Ask also for the LinkedIn article that closed the org-design series; it is referenced but is not included here and likely contains the concrete team recommendations, which would sharpen the diagnostic phase.
A better choice when the live problem is the go-to-market model rather than the category or the org chart.
Read more
PJ Fetterman's posts argue that revenue has become continuous — subscriptions, consumption, hybrids — while most go-to-market models are still built around a one-time transaction.
The fix, they argue, is to connect usage, adoption and value signals across the customer journey so marketing, sales, product and customer success work from one evolving view of the buyer.
They make the same argument about messaging: internal teams get tired of a story long before the market does, so change the story when the market gives a reason, not when the organization gets bored, and let the underlying idea compound the way Salesforce built on the same core for two decades.
For a B2B SaaS company whose positioning is sound but whose funnel and handoffs were designed for a transaction, that diagnosis is closer to the problem than a category-creation engagement.
The published material consists of short, declarative essays with a consistent closing line, not first-person accounts of running a marketing organization through a category shift or reorganization.
You get a strategic frame and a set of principles, not the operating sequence.
The Plex story—following buyers from "SaaS ERP" to "Cloud ERP" while holding the cloud-versus-on-premises argument—is the kind of concrete precedent Fetterman brings that this material does not.
A company that needs an advisor who has personally made the call, not just argued for it, should ask for that experience.
A better choice when the real constraint is owner capacity at a small or mid-sized company.
Read more
PJ Fetterman's posts start from the language owners actually use — "I need an EA," "I need somebody following up with these leads," "I can't keep doing this" — and dig underneath it to find a growth problem hiding inside an operations problem: leads sitting in the CRM with nobody following up, the $200-an-hour person spending half the day on $20-an-hour work, and work that keeps coming back because nobody owns it.
The recommendation is to put someone in charge of what already exists before adding headcount.
That maps well to a fractional operations, chief-of-staff or delegation-diagnostic engagement.
The frame is small-business staffing and ownership, not enterprise software categories or marketing organization design.
PJ Fetterman's posts do not address category creation, analyst-facing positioning, marketing function structure or how AI changes the work inside a marketing team.
A company hiring for category creation and marketing organization design should ask for relevant experience in those areas; the practical output here is a decision about who owns what, not a positioning charter or a hiring sequence.
A better choice when the task is the sales-and-marketing narrative for a security buyer who has already done the research.
Read more
PJ Fetterman's pitch-deck post names the longstanding split — marketing wants the deck to tell a story, sales wants something that moves a deal — and argues that the educated buyer narrows the gap: stop diagnosing a problem they already know they have, reframe how they see it, show the moat rather than a list of differentiators, and give the internal champion ammunition to sell the decision internally. For a cybersecurity vendor whose buyers arrive pre-educated and whose sales and marketing teams disagree about what the deck is for, that is a sharper, more specific need than general marketing advice.
PJ Fetterman's posts make one argument about pitch-deck narrative, alongside a career-reflection post about a role they turned down and the reasons they no longer trust.
They do not describe creating a category or building and restructuring a marketing organization, and the most concrete advice is tied to cybersecurity buying, so it transfers less cleanly to a manufacturing, ERP or industrial-software context.
A company that needs org design and a category charter alongside messaging should ask for that experience; this material addresses the messaging half.
The public follower count on PJ Fetterman's account was 3,188 on October 10, 2026.
Every example on this page comes from 20 LinkedIn posts by PJ Fetterman.
The posts do not include publication dates, so the sequence of Fetterman's writing follows PJ Fetterman's own cross-references, such as the four-post series on building a marketing organization from scratch and its follow-up coda.
Where the page describes a trend, such as the growing number of Chief of Staff roles reporting to CMOs, it reports what PJ Fetterman says PJ Fetterman observes rather than a settled claim.
The similar-creator and alternatives sections compare three other creators using two posts each.
Not covered here: the LinkedIn article that closed the organization-design series, a colleague's linked article on manufacturing operations, any book, talk, or off-platform writing, sponsor policies or pricing, audience demographics beyond the follower count, and post-level reach or engagement data.
Statements about employers come from Fetterman's own posts rather than independent verification of Fetterman's roles.