Peter Van Schaack shares practical advice on operations and RevOps for B2B firms, including improving CRM setup, reducing unused software, fixing handoffs between marketing, sales, and delivery, and fitting AI to documented processes. His posts also identify him with fractional COO work.
Peter Van Schaack writes practical advice about operations and RevOps for B2B firms.
His posts focus on fixing the systems and handoffs behind growth: CRM workarounds, software sprawl, the movement of information between marketing, sales, and delivery, and AI projects built on undocumented processes.
A separate post introduces a plain-language guide to choosing an AI assistant for a specific task.
The available work makes these themes clear, but does not establish whether he has signature books, shows, businesses, or earlier work that also explains searches for his name.
Van Schaack turns broad operational problems into specific causes and next steps.
On RevOps, he traces the work across team handoffs rather than treating it as sales forecasting alone; on CRM, he points to configuration as a source of spreadsheets, Slack workarounds, and manual labor.
He applies the same process-first reasoning to AI, arguing that new tools can scale a poorly documented workflow rather than fix it.
His posts also offer practical starting actions, such as a two-hour software inventory audit, and use benchmarks to make problems tangible.
The range is useful to readers comparing operations topics, though the six posts do not establish how representative these examples are of his full body of work.
The announced LLM guide suggests a decision-based teaching style, but its full contents were not included in the reviewed material.
Across these posts, Peter Van Schaack returns to a practical rule: look for the process or system causing operational friction before blaming people or buying another tool.
Read more
He applies that rule to CRM setup, cross-team handoffs, software spending, and AI, while also teaching readers how to choose an AI assistant for a specific task.
Fix the system behind the workaround
Van Schaack treats recurring manual work as evidence to investigate the system, not as proof that a team is simply slow.
Read more
In his framing, patches can hide the underlying problem and keep costing time. The same diagnostic instinct appears in his advice to document a process before adding AI to it.
In a CRM post, he calls spreadsheets, extra Slack channels, and manual handoffs around a misconfigured CRM technical debt.
He says the workarounds in firms he audits add up to more than 20 hours a week, and argues for fixing the configuration upstream.
In a separate AI post, he describes platform selection followed by attaching AI to an undocumented workflow as a route to “pilot purgatory.”
Van Schaack argues that RevOps is not just sales managing its pipeline.
Read more
It is the work of aligning what marketing, sales, and delivery pass to one another. His test is whether the work addresses those cross-team seams or merely adds steps to a sales process.
He describes marketing passing context, sales passing commitments, and delivery passing signal back. He asks readers to locate the first broken handoff: lead to deal, or deal to delivery.
Treat operational waste as something you can inspect and act on
Rather than leave inefficiency as a broad complaint, Van Schaack points to a bounded diagnostic action.
Read more
His examples focus on finding the source of avoidable time or spending, then making a specific change.
For SaaS sprawl, he recommends a two-hour audit: list every tool, map it by function, check usage, then decide what to cut. For lead follow-up, he cites a 2025 Chili Piper benchmark in which 30% of qualified form fills became booked meetings, compared with 66.7% with instant scheduling, and locates the leak in the delay after the form.
Van Schaack distinguishes choosing an AI assistant from choosing a process to automate.
Read more
For model selection, he says the useful question is what the task requires, rather than which assistant is generally best. His field-guide post presents a decision aid rather than a single universal winner.
He says his guide compares ChatGPT, Claude, Gemini, and Grok in plain language, explains why a context window matters when working with a 40-page contract, and includes a decision tree based on whether a job needs words or action.
This is the clearest statement of the reader brief's central problem: RevOps handoffs.
Read more
Start here to see how Van Schaack frames the work before any tool or process recommendation.
Van Schaack argues that RevOps is not pipeline management with a better title.
The post defines it as the discipline that aligns handoffs between marketing, sales, and delivery: marketing passes context, sales passes commitments, and delivery passes signal back.
The work lives in those seams, not inside any one team.
The post then asks a diagnostic question: if RevOps is just sales reviewing the forecast, it is a sales process with extra steps.
It closes by asking readers where the handoff breaks first—lead to deal or deal to delivery.
For brands planning a campaign
For the stated fractional COO brief, this post supplies the problem definition and the seams to investigate. A campaign can use it to position an engagement around handoff design rather than forecast hygiene.
Answers a first diagnostic question: when is slow operations a team problem versus a system problem?
Read more
It shows Van Schaack's operating instinct to look at configuration before performance.
The post shifts blame from team speed to CRM configuration.
It says every workaround built around a misconfigured CRM—Excel sheets, Slack channels, manual handoffs—is technical debt.
In the consulting firms Van Schaack audits, those workarounds add up to more than 20 hours a week of team time, paid weekly and compounding monthly.
The recommended action is upstream: fix the configuration, not the workarounds.
For brands planning a campaign
Useful as a discovery hook for a RevOps or fractional COO campaign: it gives a measurable symptom (20+ hours a week) and a specific first move (audit CRM config).
Explains why AI pilots stall and gives the priority order Van Schaack uses: document and fix the process before choosing a platform.
Read more
A newcomer gets the leadership-failure framing in one short post.
Van Schaack cites a RAND survey of 65 AI practitioners: more than 80% of B2B AI projects fail to deliver value, and 84% of those failures are leadership decisions rather than technology problems.
The pattern described is platform selection, model training, then bolting AI onto a workflow nobody documented, which leads to pilot purgatory.
The post applies an older CRM rule—process before platform—to AI and concludes that AI scales whatever process already exists.
For brands planning a campaign
A campaign targeting AI strategy or digital transformation can use this as the core argument for an advisory-led engagement rather than a tool purchase.
Shows how Van Schaack uses third-party benchmarks to make an operational argument.
Read more
It answers where a funnel leak might sit and gives a specific, sourced number to test.
Van Schaack cites Chili Piper's 2025 benchmark study of 4 million form submissions: only 30% of qualified form fills convert to a booked meeting, and instant scheduling raises that to 66.7%.
The gap is framed as timing—whether a prospect can book before they get distracted—not as a sales-pitch problem.
The post names marketing, sales, and the prospect as parties already in motion, then locates the leak at the booking step.
For brands planning a campaign
A demand gen or RevOps campaign can use the 30% versus 66.7% contrast as a quantified hook, especially if paired with a scheduling or routing tool.
In a post about CRM and Zoho One, Peter Van Schaack argues that the workarounds a team builds — spreadsheets, extra Slack channels, manual handoffs — are technical debt created by a misconfigured CRM, not evidence that the team is slow.
Read more
He estimates the accumulated work adds up to more than 20 hours a week in the consulting firms he audits, and says the repair belongs upstream at the configuration rather than at the workaround.
Reframes a people problem as a system problem, then points the fix at the upstream cause.
For brands planning a campaign
A firm that already suspects its CRM is the bottleneck can engage him on configuration review rather than team performance coaching; expect the first deliverable to be a diagnosis of where the system forces manual work.
Peter Van Schaack frames an oversized tool stack as a purchasing and inventory problem rather than a tool problem.
Read more
He cites figures for firms with 20 to 200 employees — 25 to 44 SaaS tools, 49% of licenses unused, 7.6 overlapping subscriptions — and notes that firms skip the cleanup because nothing is on fire until renewal time, at which point the spend compounds.
A two-hour audit sequence: list every tool, map by function, check usage, then decide and cut.
For brands planning a campaign
For a firm with unclear software spend this is a bounded, low-commitment starting engagement with a defined output; the savings case depends on usage and cost data the firm has to supply.
He argues that most firms run RevOps as a sales function, and that this is the mistake.
Read more
In his framing, RevOps aligns the handoffs between marketing, sales, and delivery — marketing passes context, sales passes commitments, delivery passes signal back — and the work lives in the seams between teams. If the forecast review is the only RevOps activity, he says, that is a sales process with extra steps.
A diagnostic question he puts to readers: where does the handoff break first, lead to deal or deal to delivery?
For brands planning a campaign
This speaks directly to a firm trying to fix RevOps handoffs, because he defines the scope of the problem as cross-functional seams and gives a test for whether a given problem is a RevOps problem at all.
Peter Van Schaack argues that failed AI projects are usually process failures.
Read more
He cites a RAND survey of 65 AI practitioners reporting that more than 80% of B2B AI projects fail to deliver value and that 84% of those failures are leadership decisions rather than technology problems. The pattern he describes is picking a platform, training a model, and bolting it onto a workflow nobody documented, which ends in pilot purgatory.
For brands planning a campaign
A firm weighing an AI pilot should expect him to start with process documentation, so any engagement should be scoped to include the workflow work before a tooling decision is made.
He published a plain-English field guide comparing the four major AI assistants — ChatGPT, Claude, Gemini, and Grok — organized around whether a task needs words or action rather than which brand is best.
Read more
It explains terms such as context window in relation to handing a tool a 40-page contract, and includes an interactive decision tree that points to a model based on the actual job.
Explainer plus a decision tree that routes a specific task to a model.
This is a longer-form teaching asset rather than a short diagnostic post, and it addresses tool selection where most of his other posts address process and operations.
For brands planning a campaign
Useful when a firm wants practical AI literacy for staff who are choosing tools without a vendor-led evaluation; it shows he produces teaching material, not only commentary.
He points to a Chili Piper 2025 benchmark study of 4 million form submissions in which only 30% of qualified form fills converted to a booked meeting, rising to 66.7% with instant scheduling.
Read more
His reading is that the leak sits in the delay and friction after the form, not in the sales pitch.
It focuses on a marketing and demand-generation metric, where most of his other posts stay inside internal operations and systems.
For brands planning a campaign
This is a client-facing revenue leak rather than a back-office one, and it shows he will examine demand-generation and scheduling mechanics alongside CRM and operations work.
Peter Van Schaack's reviewed posts do not document a sponsorship, affiliate arrangement, or client engagement with any named company.
Read more
The brands that appear are either topics he writes about or third-party research he cites to support an argument. The only business relationship the posts gesture at is generic consulting work — he refers to "the consulting firms we audit" — without naming the firm or stating his role in it.
Zoho One
Mention
Van Schaack tags a post about misconfigured CRMs with ZohoOne while arguing that workarounds teams build around a bad CRM configuration are "technical debt."
Read more
The post uses Zoho One as a topical tag; it does not state a commercial relationship.
Van Schaack cites Chili Piper's 2025 benchmark study of 4 million form submissions to argue that instant scheduling lifts form-fill-to-meeting conversion from 30% to 66.7%.
Read more
The company is a cited source, not a stated partner or client.
Van Schaack cites a RAND survey of 65 AI practitioners to support his claim that most B2B AI failures are leadership decisions rather than technology problems.
Read more
The post cites RAND as research, not as a client or partner.
Peter Van Schaack's retained posts are short, practical field notes on operational drag: a CRM that forces workarounds, a tool stack nobody audits, a handoff that drops context, an AI project bolted onto an undocumented process.
Read more
The through-line is a habit of tracing friction to its source and proposing a bounded next step — a configuration fix, a two-hour tool audit, a handoff question, a process document written before a platform is chosen. For a reader exploring the work, the posts are the fastest entry point; the LLM field guide is the one longer teaching asset, and it shows the same preference for matching a tool to a task rather than to a brand.
Kim makes the same move Van Schaack does: he treats a revenue problem as a system problem rather than a funnel problem.
Read more
In “Sales Isn’t a Funnel. It’s a System.” he argues that more leads will not fix onboarding, qualification, messaging, or coaching, which echoes Van Schaack’s claim that fixing workarounds misses the misconfigured system underneath.
Kim’s examples come from healthcare SaaS sales organisations and focus on the selling system itself — messaging, qualification, rep coaching. Van Schaack ranges wider across back-office and operating systems: CRM configuration, unused SaaS licences, RevOps handoffs, and AI adoption across marketing, sales, and delivery.
Lewis diagnoses the same class of problem under a different name.
Read more
His “growth debt” post argues that spiky results, attribution chaos, and unpredictable revenue come from chasing short-term wins without long-term infrastructure, and his post on the customer journey says the journey is not broken but disconnected across marketing, sales, and product — close to Van Schaack’s framing of RevOps living in the seams between teams.
Lewis writes from a growth-agency perspective, selling systems design and assessment-led engagements (his posts carry a free revenue-engine assessment and an agency hashtag). Van Schaack writes as an operator looking at the inside of a firm — auditing tool stacks, reconfiguring a CRM, documenting a process before buying AI — with less emphasis on brand, content, and outreach as parts of the system.
Walder writes about AI inside B2B go-to-market workflows and keeps returning to handoffs — the AE-to-CSM handoff and deal qualification — the same territory as Van Schaack’s lead-to-deal and deal-to-delivery framing.
Read more
Both treat context that fails to travel between teams as the real problem, and both see AI as changing how that work gets done rather than as a standalone tool purchase.
Walder writes as an operator inside an AI-native company, describing workflows he has watched colleagues build: context pulled from Gong, email, CRM, and enrichment into a generated handoff, and a Slack-submitted deal scored against a qualification rubric. Van Schaack writes from outside as a fractional COO, arguing process-before-platform and supporting the case with cited figures such as the RAND survey on failed AI projects.
No audience-composition or performance data was supplied for Peter Van Schaack.
Read more
The packet holds six LinkedIn posts published between 26 May and 8 June 2026 (one post carries no date) plus the follower count on his LinkedIn profile: 5,221, observed 8 October 2026.
There is no per-post reach, like, comment or share figure, no follower-growth history and no demographic breakdown, so the evidence supports a judgment about what these posts are written to help with — not a measured picture of who reads them.
The subject matter is consistent and narrow: CRM configuration and the workarounds teams build around a misconfigured system, unused SaaS licences and overlapping tools, the marketing–sales–delivery handoffs that Peter defines as the real RevOps work, AI model selection explained for non-specialists, the gap between form fills and booked meetings, and fitting AI to a documented process rather than bolting it onto an undocumented one.
The reader these posts are aimed at is someone accountable for revenue operations, CRM or technology decisions inside a B2B firm — names firms of roughly 20–200 employees — but that is an inference from the topics, hashtags and how the arguments are framed, not a measured audience property.
Follower count is the only quantitative audience figure available, and it says nothing about who those followers are or how they respond.
For a fractional COO brief, the decision turns on whether the people who follow and engage with Peter are the operations and revenue leaders the firm needs to reach.
The supplied material cannot answer that.
Two concrete requests would: recent results for posts closest to the brief — the RevOps handoff post and the CRM-configuration post — covering impressions and engagement, and, if the brief depends on job function or seniority rather than topic, whether Peter has audience survey results or another documented source.
Platform audience data does not verify employer, occupation or job seniority; those attributes need a survey or equivalent document.
No partnership or sponsorship offer is documented in the material reviewed for Peter Van Schaack.
Read more
The reviewed posts do not describe sponsored placements, branded-content formats, rates, or an inquiry route, so nothing here should be read as an offer Peter Van Schaack makes or declines.
They read as practitioner commentary on CRM configuration, SaaS licence waste, RevOps handoffs, and fitting AI to documented processes, not as commercial inventory.
If Peter Van Schaack publishes a media kit, rate card, or sponsorship policy, that document would need to be collected and reviewed before any format could be described.
Buyers planning paid work should treat the format list below as empty rather than assume a standard LinkedIn arrangement.
A B2B consulting or professional-services firm of roughly 20–200 employees whose RevOps handoffs keep stalling — leads arrive, deals slow down between sales and delivery, and no single team owns the seams — wants a fractional COO for a defined diagnostic and repair engagement.
Read more
This is the brief Peter Van Schaack's own writing addresses most directly.
In the RevOps post, the work is defined as aligning the handoffs between marketing, sales, and delivery: marketing passes context, sales passes commitments, delivery passes signal back, and the job lives in those seams rather than inside one team.
The post supplies a usable diagnostic question — where does the handoff break first, lead to deal or deal to delivery — and a test for whether a firm has RevOps at all: if the only activity is sales reviewing the forecast, it is a sales process with extra steps.
Two supporting posts extend the fit.
The CRM post argues that the workarounds a team builds around a misconfigured CRM — spreadsheets, extra Slack channels, manual handoffs — are technical debt, not a slow team, and puts the accumulated cost at more than 20 hours a week in the consulting firms they audit, which is exactly the kind of quantified symptom a consulting firm can test against its own numbers.
The SaaS post offers a bounded first exercise: list every tool, map by function, check usage, decide and cut, in about two hours.
If AI is part of the brief, the AI post gives the priority order — document the process before choosing a platform.
What the evidence supports is a diagnosis-and-plan engagement scoped to handoff design, CRM configuration, and software spend.
What it does not support is a claim about Peter Van Schaack's track record: no case studies, client outcomes, references, rates, or availability appear in the reviewed material, so those should come from the firm's own diligence before signing.
When to choose a specialist
A consumer or direct-to-consumer brand, or a software vendor, that wants to buy a paid social content package — short-form video plus sponsored posts aimed at a broad audience, with named formats, rates, and reach targets — is a poor fit on the evidence available.
Read more
No sponsorship or partnership offer is documented: the reviewed posts do not describe sponsored placements, branded-content formats, rates, or an inquiry route, so there is nothing to price or schedule.
The audience evidence is equally thin for a reach-driven brief.
The only quantitative audience figure is a follower count of 5,221 observed on 8 October 2026, with no impressions, engagement, or demographic data for any post, so there is no way to judge whether an audience of that size would respond to a consumer campaign.
The material itself points away from the brief: the posts are practitioner commentary on internal operations — CRM configuration, unused SaaS licences, marketing-to-delivery handoffs, AI project failure — written as written analysis rather than as performance content, and no video or visual assets were part of the reviewed evidence beyond a text post announcing an external guide.
A second poor-fit brief worth naming is a B2B brand that wants a tooling recommendation or a vendor-led AI pilot led by this person: the AI post argues that more than 80% of B2B AI projects fail to deliver value and that 84% of those failures are leadership decisions, so an engagement framed around picking a platform rather than documenting the process runs against the stated position.
In both cases the obstacle is missing evidence and a mismatch of purpose, not a judgment about what Peter Van Schaack would accept elsewhere.
A worked campaign example
Worked angle for the fractional COO brief: a scoped handoff diagnosis with a written repair plan.
Phase one, roughly two weeks, maps the seams rather than the org chart — short interviews with marketing, sales, and delivery to record what context marketing actually passes, what commitments sales makes, and what signal delivery returns.
The output is a one-page handoff map and a first answer to the diagnostic question Peter Van Schaack poses: does the chain break first between lead and deal, or between deal and delivery.
Phase two audits CRM configuration and quantifies the workarounds.
The test is concrete: count the spreadsheets, side channels, and manual handoffs that exist because the system cannot do the job, and convert them to hours per week.
The 20-plus hours a week figure from the CRM post is a benchmark to compare against, not an assumption to assert.
Phase three runs the two-hour tool inventory — list every tool, map it by function, check usage, then decide and cut — with the same discipline: the 25–44 tools, 49% unused licences, and 7.6 overlapping subscriptions figures are hypotheses to check against the firm's own spend, and the deliverable is a cut list with owners and renewal dates.
Phase four applies only if AI is on the table: document the workflow before selecting a platform, on the stated finding that most failures are leadership and process decisions, not technology ones.
The engagement closes with a prioritized repair list — each item with an owner, a cost or hours estimate, and an observable retest so the firm can confirm the fix held.
Two limits belong in the proposal.
First, the evidence reviewed shows a method and a set of diagnostics, not a delivery record, so the commercial terms, references, and availability need separate diligence.
Second, the angle fails if leadership wants a tool purchase rather than process documentation; in that case this scope is the wrong one to buy, and the mismatch is worth surfacing before work starts.
Kim over Peter Van Schaack when the stall sits inside sales execution rather than in the seams between teams.
The post "Sales Isn't a Funnel.
It's a System." describes the pattern: more leads, tools, and headcount hitting a process where there is no consistent messaging, no qualification framework, and no coaching cadence, so reps freelance their way through deals that should have been disqualified in week one.
That is the same buyer task — a B2B firm trying to work out why revenue is not moving — but the diagnosis points at the sales system under the funnel, not at marketing-to-delivery handoffs.
Kim also publishes a free AI Readiness Assessment for sales teams and sales leadership, a roughly ten-minute diagnostic covering where AI could move the needle, where the data, process, and adoption gaps are, and what to prioritize first.
Pick that route when the firm wants a low-commitment sales-team diagnostic, works in healthcare SaaS, or suspects the real failure is onboarding and deal coaching rather than CRM or tooling.
The tradeoff is scope and form.
Neither reviewed post touches CRM configuration, workaround debt, unused licences, or the marketing-to-delivery handoff that the fractional COO brief centers on; the focus is sales system design and AI readiness.
The assessment is a self-serve diagnostic rather than a written repair plan with owners, cost estimates, and observable retests, so the firm would still need someone to do the handoff mapping and the tool cut list.
The reviewed evidence is two posts dated July 2026 with no case studies, client outcomes, rates, or availability.
Choose Scott Lewis when the symptom is growth that does not compound rather than one broken handoff.
Read more
The "growth debt" post names the pattern a buyer would recognize — spiky results, burnt-out teams, attribution chaos, revenue that is hard to predict — and argues sustainable growth comes from systems that compound across brand, outreach, tech, and content.
The customer-journey post makes the same case at the touchpoint level: marketing says one thing, sales promises another, product delivers something else, buyers feel the seams and leave.
For a firm whose problem shows up as inconsistent promises across the buying journey, or that wants revenue-engine design treated as a growth-system project, this framing is closer to the brief than a pure CRM or handoff audit.
The tradeoff is depth and posture.
The posts stop at diagnosis and framing; there is no method for mapping the marketing, sales, and delivery handoffs, no CRM configuration work, no tool or licence inventory, and no hours or spend benchmarks to test against the firm's own numbers.
The growth-debt post is written as an agency pitch — it is tagged #TheLuckyAgency and describes what "we design" — so it reads as a growth-system offer rather than an operator-led repair plan.
The two reviewed posts are dated November and December 2025, and no engagement scope, rates, or references appear.
Choose Greg Walder when the handoff problem is specifically context loss and the firm wants to see what an AI-native version of the workflow looks like before deciding how much to automate.
Read more
The first post describes, from a first-day meeting, a fully AI-native handoff process that pulls context across sales calls, emails, CRM data, enrichment systems, and internal notes, assembles a structured customer handoff, recommends which customer-success person should take the account, routes everything through approval, and generates branded kickoff material.
The second describes a deal-qualification workflow where an account executive submits a deal from Slack, email, or the website, and the system scores it against a rubric, compares it with past deals, flags missing information, and explains the reasoning rather than just issuing a number.
Both posts treat operational problems historically framed as people or process problems as context-orchestration problems.
That is the most direct evidence in this comparison set that AI-assisted qualification and handoff can be built at all, and it is useful if the brief includes an automation phase rather than only process documentation.
The tradeoff is that this is an operating example, not a service.
The evidence is firsthand observation inside one company building its own internal tools, so the workflows depend on engineering capacity and an already-integrated stack spanning call recording, CRM, and enrichment data — a 20–200 person firm may not be able to copy them directly.
Nothing here covers CRM configuration debt, software licence and overlap audits, or the tool cut list the fractional COO brief calls for, and no rates, availability, or fractional engagement evidence appears.
This page is built from the full text of six LinkedIn posts published by Peter Van Schaack, plus the follower count on the linked account.
The posts cover CRM configuration and the workarounds teams build around it, SaaS licence and overlap audits, RevOps handoffs between marketing, sales, and delivery, B2B AI project failure, choosing an LLM for a task, and form-to-meeting conversion.
Five posts carry dates between 26 May and 8 June 2026; one was supplied without a date, so no order of development over time is claimed.
The follower count of 5,221 was observed on 8 October 2026.
Three similar creators (Yong S.
Kim, Scott Lewis, and Greg Walder) were compared using two retained posts each, dated 10 and 18 July 2026, 11 November and 9 December 2025, and 12 and 19 May 2026 respectively.
What this evidence does not establish: no engagement or reach figures, audience demographics, case studies, client outcomes, references, rates, or availability; no sponsorship, partnership, or client relationship with any named brand; and no signature books, shows, or owned businesses.
A longer LLM field guide linked from one post was outside the reviewed material, and no full posting history was available.
Those gaps are recorded as open research items rather than filled in.
