Mike Coutts writes about improving commercial operations at manufacturers, especially the CRM, ERP, pricing, quoting, and data processes that affect revenue and post-acquisition integration.
Most useful for operational questions about CRM, ERP, pricing, quoting, and post-acquisition commercial integration.
Best for
A manufacturing-focused private equity firm wanting a post-deal commercial operations assessment.
Not for
A CRM or AI platform vendor seeking paid LinkedIn sponsorship with guaranteed reach.
Key takeaways
Manual Tax is their term for costs of work left to spreadsheets and manual processes.
Before ERP or CRM cutover, settle price-book rules, discount approvals, and source of leadership metrics.
CRM trust starts with one disputed number, tracing inputs, and useful returns for data entry.
Check first: Ask for basis behind the 50 to 300 basis points EBITDA estimate and LinkedIn post analytics.
Main ideas
Manual work in commercial operations carries a cost · Settle commercial decisions early in an acquisition · CRM data depends on trust and useful returns for the people entering it
Mike Coutts writes about the commercial operations behind manufacturing businesses: how quoting, pricing, customer data, CRM and ERP systems affect revenue, especially after an acquisition.
The posts reviewed are known for “Manual Tax,” their term for the cost of work left to spreadsheets and manual processes.
They offer practical explanations of why these problems persist and what to examine first.
For example, Coutts suggests settling price-book rules, discount approvals and the source of leadership’s weekly metrics before an ERP or CRM cutover.
The posts also connect AI plans to the underlying work: an agent placed over a manual process may automate it without removing its costs.
Coutts turns broad claims about digital transformation into operational questions.
In a post about acquisitions, they ask not just whether systems will be integrated, but how overlapping customer accounts will be priced, who can approve discounts and where leadership’s numbers come from.
In a post about CRM trust, they propose starting with one number leaders dispute: trace its inputs, give employees a useful return for entering data, then see whether the number changes and earns trust.
They also push back on AI-first plans, arguing that messy data, administrative work and weak change management can undermine them.
The posts are strongest as a way to frame an assessment and identify questions.
The cited estimate that the Manual Tax costs 50–300 basis points of EBITDA is presented without a calculation; ask for the basis behind it before treating it as a demonstrated result.
Mike Coutts argues that manufacturers should fix the commercial processes and incentives beneath their systems before adding more technology.
Read more
Across their posts, they connect manual work to a measurable cost, treat trust as essential to usable CRM data, and favor small, practical steps over broad AI mandates.
Manual work in commercial operations carries a cost
Coutts uses “Manual Tax” for the gap between commercial work and the systems meant to support it.
Read more
Spreadsheets and workarounds can leave quoting, pricing, and rebates disconnected from the CRM. They argue that putting AI on top of those processes does not remove the underlying work; it can automate it.
Coutts describes manufacturers running quote-to-cash across an ERP, a CRM salespeople work around, and about 40 spreadsheets.
In another post, they estimate the gap at 50–300 basis points of EBITDA in their work.
Settle commercial decisions early in an acquisition
Coutts says acquisition integration often gets a plan for plant operations but only a deadline for commercial systems.
Read more
If teams move existing pricing, customer records, and approval habits into a new system without deciding how they should work, the new system preserves old problems.
Coutts says that six months after a deal, finding out which customers are profitable can take three people and a week of spreadsheets. Before a cutover, they recommend deciding which price book applies to overlapping customers, who approves discounts, and what number leadership will review each Monday.
CRM data depends on trust and useful returns for the people entering it
Coutts describes a loop: managers distrust the numbers and rely on gut; the CRM becomes optional; thin data then gives managers more reason to distrust it.
Read more
Their proposed first step is to follow one disputed number back to its inputs and make sure the people entering data get something useful in return.
Coutts says one commenter, Mike Mulligan, put it this way: reps enter data when they get something back, while most CRMs only take. They add that AI may clean data quickly, but keeping it clean months later is a people problem, not just a technology problem.
Measure the cost of waiting, not just the cost of investment
Coutts argues that businesses scrutinize purchase and operating costs but often leave delay out of the model.
Read more
Its effects can surface as slower quoting, forecasts people do not trust, or deals that stop closing—and become harder to address when they appear during diligence or a value-creation review.
Coutts sketches a manufacturer whose quote-to-cash process spans an ERP, a workaround-heavy CRM, and roughly 40 spreadsheets, then urges leaders planning for 2027 to put a number on another year of waiting. If they cannot size the delay, they say, that is the first problem to solve.
Start AI adoption with a small, measurable use case
Coutts reports that teams facing AI mandates are tired, while familiar problems such as messy data, administrative work, and weak change management remain.
Read more
They argue that the first use case should be small and measurable, rather than the ambitious example on a presentation slide.
After attending Dreamforce for roughly the tenth time, Coutts writes that the hallway conversations felt thin despite the event’s prominent AI displays. They say many companies still lack a practiced process for basic work such as lead management or case handling, and warn that an agent placed on top of a manual process automates it rather than eliminating its cost.
If you have five minutes and want to know whether Coutts's writing is relevant to you, start here: this is the thesis their longer posts expand.
Read more
Coutts's shortest post is also the clearest statement of what they look for.
Manufacturers, they write, still run quoting, rebates and contract pricing on spreadsheets, while the CRM holds contact records and little else.
They put the gap at 50 to 300 basis points of EBITDA and say they will be at Dreamforce on September 15 to 17, where they hope to meet people working on this at a portfolio company.
The post names a range and an audience but offers no example, calculation or company behind the number.
For brands planning a campaign
A private equity firm can lift this framing almost directly into a post-close conversation, but the 50 to 300 basis point range is Coutts's working estimate. Rebuild it from a specific portfolio company's quoting, pricing and rebate data before putting it in a board pack.
This is where the Manual Tax idea becomes a method.
Read more
It answers the question a newcomer may have after reading a short post: what would Coutts actually do in the first weeks after a deal closes?
Coutts notes that acquisition announcements describe integration on the plant side — equipment, safety, purchasing, an ERP cutover date — while the commercial side gets only a deadline.
Price lists, customer records, quoting habits and discount approvals move into the new system as they worked before, because nobody had time to decide how they should work.
Six months later, a new sales leader asks which customers are profitable, and the answer takes three people and a week of spreadsheets.
The post ends with three questions to settle before cutover: when two acquired companies sell to the same customer, which price book wins; who approves a discount, and does the system know; what will leadership look at every Monday, and where will that number come from?
For brands planning a campaign
For a post-acquisition brief, these three questions can set the agenda for a commercial operations assessment. Coutts argues that most of the cost is set in the first 90 days after close, making the case for running the assessment early rather than as part of a later systems project.
This shows how Coutts argues, not just what they conclude.
Read more
They respond to named disagreement, concede a point and turn it into a concrete first-quarter sequence — useful for judging whether their thinking holds up under scrutiny.
After a post about Dreamforce, Coutts reports that the word appearing most in the comments was not AI but trust.
They quote three commenters by name — Mike Mulligan on reps entering data only when they get something back, Meredith Tawney on workarounds becoming another layer of admin, and Spencer Lowe on AI cleaning data in days rather than months — and agree with Lowe while arguing that keeping data clean six months later is the hard part, a people problem wearing a technology costume.
They describe a loop they say they have watched for 15 years: nobody trusts the number, the manager goes back to gut, gut makes the CRM optional, optional systems produce thin data, and thin data is why nobody trusts the number.
The post closes with a four-step sequence for anyone handed an AI mandate this quarter, built around one number leadership already argues about: find where it comes from, decide what the rep gets back this week, and check whether the number moved.
For brands planning a campaign
The four-step sequence is a scoped, low-cost first phase for an AI or CRM mandate: pick one contested number, trace its inputs, give reps something back within the week, then measure whether anyone believes it. It could serve as a deliverable for an assessment engagement and a way to test Coutts's judgement before committing to a larger programme.
This answers the question a buyer asks before any technical discussion: why act now instead of next year?
Read more
It is also Coutts's clearest example of connecting an abstract cost to specific operational symptoms.
Coutts argues that businesses can price almost everything except delay.
Upfront cost, maintenance, labour, interest and headcount all get debated, while the cost of waiting stays out of the model because it does not appear anywhere you can point to.
It surfaces later, they write, in quote turnaround, in a forecast nobody trusts enough to plan production against, and in deals that quietly stop closing.
The example is a manufacturer running quote-to-cash across an ERP, a CRM the sales team works around, and about 40 spreadsheets.
The bill comes due at the worst moment, usually in diligence or a value creation review, when there is no runway left to fix it properly.
The post turns to 2027 planning with an invitation: put a number on another year of waiting; if you cannot size it, that is the first problem.
For brands planning a campaign
This post gives a sponsor the opening argument for commissioning an assessment before diligence rather than after it.
Coutts's symptoms — quote turnaround, forecast credibility, deals that stop closing — are concrete enough for an initial diagnostic checklist.
If the cost is not yet sized, report that finding to the investment committee.
This post supplies context for Coutts's other themes: the Manual Tax, scepticism about AI mandates and the small-first-use-case rule.
Read more
It also draws on first-hand observation of a large industry event, evidence that helps readers assess a practitioner's general claims.
Coutts describes their tenth or so Dreamforce as thin, while separating that from the production: AIforce, Claudeforce, Slackforce and Agentforce were everywhere, and Salesforce says 30,000 customers are live on Agentforce.
The thinness was in the hallway conversations.
Enterprises have had about twelve months to live with the AI mandate, they say, and the people carrying it are tired.
Four themes recur: data is still messy and now has an AI layer that will be confidently wrong about it; reps still spend too much time on administration, an argument they say they were having in 2014; change management is the line item most often cut, and gets harder when users rather than workflows decide what to ask; and the pace of change means nobody masters a craft that is redesigned every quarter.
The line they kept hearing behind closed doors was 'we can taste it, but we haven't captured it.' Their conclusion: first use cases have to be small and measurable, usually not the one on the slide, and an agent placed on top of a manual process automates the tax rather than removing it.
For brands planning a campaign
For a brief with an AI-first mandate, this post sets expectations: the first use case should be small and measurable, the underlying data is likely to be the real constraint, and change management needs a budget. An agent deployed over existing spreadsheets will not, on its own, close the gap.
How Coutts works: field observation and audience follow-up3
Post-acquisition commercial integration2
CRM trust and the data-quality loop2
AI adoption inside industrial commercial teams2
Cost of delay1
The Manual Tax in commercial operations
Coutts calls the cost of running quoting, rebates, contract pricing, and order handling on spreadsheets and workarounds while the CRM holds little beyond contact records the “Manual Tax.”
Read more
In their work, that gap costs manufacturers between 50 and 300 basis points of EBITDA.
They describe a common setup: quote-to-cash spread across an ERP, a CRM the sales team works around, and roughly 40 spreadsheets.
Adding an AI agent does not remove the tax; it automates it.
Field observations across client manufacturers, paired with an estimated range rather than a published benchmark.
Coutts presents the 50–300 bps range as an observation from their work, not a universal industry minimum.
For brands planning a campaign
A brand selling a commercial-operations assessment or CRM/ERP integration offer can use this framing to quantify inaction and justify a diagnostic before any software purchase.
Coutts argues that after an acquisition, the plant side gets a plan—equipment, safety, purchasing, an ERP cutover date—while the commercial side gets only a deadline.
Read more
Price lists, customer records, quoting habits, and discount approvals move into the new system as they worked before because nobody had time to decide how they should work.
Six months later, answering which customers are profitable can take three people and a week of spreadsheets.
They say most of the Manual Tax is set in the first 90 days after close and identify questions to settle before cutover: when two acquired companies sell to the same customer, which price book wins; who approves a discount, and does the system know; and what leadership will look at every Monday, and where that number comes from.
For brands planning a campaign
A manufacturing-focused private equity firm can lead with a 90-day commercial operating assessment to settle pricing, discount, and reporting decisions before ERP or CRM work begins.
Coutts reports that the most common word in comments on their Dreamforce post was not AI but trust.
Read more
Reps enter data when they get something back; most CRMs only take.
When people stop trusting the system, they build workarounds, which become another layer of admin.
AI can clean data in days, but keeping it clean six months later is a people problem.
They describe a repeating loop: nobody trusts the number, so the manager goes back to gut; gut makes the CRM optional; optional systems produce thin data; thin data is why nobody trusts the number.
Putting an agent on top of that loop does not break it.
Review and synthesis of comments on Coutts's post, including named practitioners' counterpoints.
For brands planning a campaign
An AI or CRM consultancy should address rep incentives and processes before pitching data cleanup or automation, or the same trust failure will return.
Coutts argues that upfront costs, maintenance, labor, and headcount get debated line by line, but cost of delay never enters the model because it is not visible in a specific measure.
Read more
It shows up later in quote turnaround, forecasts nobody trusts enough to plan production against, and deals that quietly stop closing.
The bill usually comes due in diligence or a value-creation review, when there is no runway left to fix things properly.
They suggest putting an actual number on another year of waiting before deferring commercial-operations investment again.
Coutts says that if there is no way to size the delay, that is probably the first problem to solve.
For brands planning a campaign
A short diagnostic that sizes the cost of delay can open the door to a larger commercial transformation engagement.
After roughly twelve months of AI mandates, Coutts reports tired teams and four recurring themes from a large conference: data is still messy, and AI adds a layer that can be confidently wrong about it; reps still spend too much time on administration; change management is the line item most often cut even as systems shift from structured to unstructured; and the pace of change means no one masters a craft redesigned every quarter.
Read more
Their working rule: the first use case has to be small and measurable, and it is usually not the one on the slide. Many companies still lack a conditioned muscle around lead management or case handling.
For brands planning a campaign
Brands selling AI enablement into manufacturing should lead with small, measurable use cases and adoption support, not platform breadth or big-bang rollouts.
How Coutts works: field observation and audience follow-up
Coutts draws on roundtables, customer conversations, and conferences—a tenth Dreamforce is mentioned—rather than published market research.
Read more
Their short-form LinkedIn posts use numbered themes or questions and pair a named operating concept with a concrete example, such as 40 spreadsheets or a week-long customer profitability exercise. Posts often close with a direct question to readers; at least one explored the comments on a prior post and quoted named practitioners.
For brands planning a campaign
A campaign seeking operator-level field perspective should expect first-person observations and direct practitioner quotes, not analyst-style data studies. An interview or event-based format suits this style.
The available posts do not document a sponsor, affiliate, owned business, employment, client, disclosed partnership, or investment relationship.
Read more
The clearest named commercial-platform connection is Mike Coutts writing about Salesforce’s Dreamforce event and Agentforce adoption; the posts present this as commentary and observation, not a disclosed commercial relationship. Ask directly about any commercial ties if they matter to a campaign.
Salesforce
Mention
Writes about attending Dreamforce and Salesforce’s Agentforce adoption claims in a post on AI fatigue, messy data, and commercial operations.
Read more
The post does not disclose sponsorship, employment, client work, or another commercial relationship with Salesforce; ask directly if that matters to a campaign.
Mike Coutts writes short, example-led LinkedIn posts about the commercial side of manufacturing: how quoting, pricing, rebates, and customer data run on spreadsheets and workarounds, and what that costs.
Read more
Start with the Manual Tax posts, then the acquisition integration piece, the CRM trust follow-up, and the cost-of-delay argument.
Read the Dreamforce post for their view on AI adoption.
The tags below group those threads so readers can follow one subject at a time, and the similar creators offer adjacent voices on Salesforce, revenue operations, and AI adoption.
Commercial operationsManufacturingPost-acquisition integrationCRM adoption and data qualityCost of delayAI adoption in commercial teamsQuote-to-cash processesShort-form LinkedIn postsField observation and conference notesPrivate equity operating partnersRevOps and sales operations leaders
Both write about enterprise software ecosystems and what happens when AI meets messy, governed data.
Read more
Keenan analyses Salesforce orgs, dependencies, and the metadata layer AI agents need; Coutts covers commercial systems, CRM trust, and the gap between the data a company has and the data it can act on.
Keenan works at the platform and DevOps level, writing longer analytical pieces about Salesforce architecture, vendor moves, and agent governance. Coutts focuses on industrial commercial operations, using EBITDA estimates, post-acquisition decisions, and on-the-ground examples such as quote-to-cash spreadsheets.
Both are skeptical of AI hype and argue that adoption, clean data, and measurable ROI matter more than a keynote demo.
Read more
They write about why promised productivity gains have not fully arrived and what would actually deliver value.
Markman writes broadly about AI, productivity, and Revenue Operations ROI, often in a provocative style. Coutts focuses on manufacturing commercial operations, acquisition integration, and a specific EBITDA framing of manual work.
Both write for revenue operations audiences and treat spreadsheet assumptions as a source of operational risk: Aleman on hiring math and capacity plans, Coutts on quote-to-cash and the Manual Tax.
Read more
They also argue that systems fail when leaders rely on lagging or untrusted signals.
Aleman works inside sales team planning and forecasting, covering ramp curves, territories, quota capacity, and CRM risk signals. Coutts covers the manufacturing commercial stack, post-acquisition pricing and discount decisions, and the cost of running those processes on spreadsheets.
Mike Coutts reaches a small, tightly targeted LinkedIn audience.
Read more
The account has 1,485 followers, and the five posts here address people who run or improve commercial operations at manufacturers: CRM data trust, quote-to-cash spreadsheets, pricing and discount approval during acquisition integration, and AI mandates landing on messy systems.
For a manufacturing-focused private equity firm, that suggests a narrow but well-matched group of operators and commercial leaders—not a mass channel.
The key question is whether the portfolio-company people a campaign targets are among them.
The posts don’t identify the followers’ geography, job titles, seniority or employers, and show no engagement counts.
Before agreeing to a placement aimed at portfolio-company CFOs or commercial leaders, ask for recent LinkedIn post analytics—including impressions, reactions, comments and follower demographics such as geography and seniority—and any audience survey, subscriber list or testimonials covering the operators, sales leaders and finance people reached.
Evidence that portfolio-company CFOs or commercial leaders read a specific post would be more useful than the follower total.
Mike Coutts's posts do not mention sponsorship, advertising, or paid-partnership formats.
Read more
The only commercial contact is an open invitation: in a post about spreadsheet-heavy commercial operations, they say they will attend Dreamforce on September 15–17 and invite people working on this problem at a portfolio company to meet for a conversation.
It is an offer to talk shop with operators and investors, not a purchasable package: the posts provide no rate card, sponsored-placement example, audience specification, disclosure of a paid brand deal, or partnership inquiry route.
For a paid engagement, confirm terms directly through LinkedIn; no official partnership or media-kit page is present, so ask for available formats and terms.
A good fit for an expert-led engagement or co-authored diagnostic piece. This is the brief Coutts’s writing is built for, provided the buyer wants judgment applied to a specific portfolio company rather than a paid promotional placement.
Read more
Brief
A manufacturing-focused private equity firm, shortly after signing a deal, wants a commercial operations assessment in the first 90 days that quantifies the Manual Tax and sequences CRM and ERP integration decisions before cutover.
Reasons
The scope matches what Coutts describes doing. The acquisition post sets out three questions to settle before an ERP or CRM cutover: when two acquired companies sell to the same customer, which price book wins; who approves a discount, and does the system know; and what leadership looks at every Monday, and where that number comes from. Those are the brief’s deliverables, not adjacent topics.
The timing argument is already made in the material. Coutts writes that most of the Manual Tax is set in the first 90 days after close, and that the cost of delay shows up later in quote turnaround, forecasts nobody trusts, and deals that quietly stop closing. These problems usually surface in diligence or a value creation review, when there is no runway left. That is a sponsor-ready case for acting early.
The audience is narrow but aimed at exactly these people. The five posts are written for operators and commercial leaders fixing quote-to-cash, pricing, and CRM data trust at manufacturers. The account carries 1,485 followers, making it a targeted pocket of operators rather than a mass channel. Ask for follower demographics to confirm whether portfolio-company CFOs are among them.
The 50 to 300 basis points of EBITDA figure is Coutts’s own working estimate from past client work, stated without a supporting calculation. Rebuild it from the portfolio company’s quoting, pricing, and rebate data before it goes near a board pack.
When to choose a specialist
Poor fit based on what the posts say. The mismatch is not subject knowledge; it is the sponsorship product, audience scale, performance data, and message alignment, none of which the posts describe.
Read more
Brief
A CRM or AI platform vendor wants a disclosed paid LinkedIn sponsorship series to launch an AI agent product to a broad business audience, with guaranteed impressions, reach targets, and a mass-market product message.
Reasons
The posts describe no sponsorship product, rate card, format, pricing, disclosed paid partnership, or inquiry route. The only commercial contact is an open invitation to meet people working on this at a portfolio company during Dreamforce. Ask for the sponsorship terms before planning a paid series.
Reach cannot be underwritten. The account has 1,485 followers, and the posts carry no visible engagement counts, impressions, or audience breakdown by geography, job title, or seniority. Ask for performance and audience data before considering a guarantee-based impressions buy.
The message runs against the writer’s own public position. Coutts argues that the first AI use case has to be small and measurable, and is usually not the one on the slide; that change management is the line item most often cut; and that an agent placed on top of a manual process automates the tax rather than removing it. A broad AI-launch narrative would ask them to contradict what this audience has already read.
The posts publish no response or reach data, leaving vendors without a basis for forecasting placement performance.
A worked campaign example
Angle
Size the cost of delay, then decide the system. Lead with what waiting is costing, resolve the commercial decisions the ERP cutover would otherwise lock in by default, and prove one number before automating anything.
Brief
Manufacturing-focused private equity firm, in the first 90 days after close, wants the Manual Tax quantified and CRM/ERP integration decisions prioritized.
Caveats
The 50 to 300 basis points of EBITDA range is Coutts’s own practice estimate and would need to be rebuilt from the company’s quoting, pricing, and rebate data before use. The posts are five short LinkedIn posts and publish no engagement or reach data; ask for performance data before forecasting response to a placement or co-authored piece.
Deliverable
An expert-authored diagnostic, a working session with the portfolio commercial team, and a short written readout to the investment committee covering the sized cost of delay, the three cutover decisions, and the results of the one-number test.
Sequence
Put a number on another year of waiting. Walk the portfolio company’s quote-to-cash path and estimate the cost of delay in quote turnaround, forecast credibility, and deals that stop closing. If no number can be produced, report that inability as the first finding—a step Coutts names directly.
Run the 90-day commercial operating assessment. Settle three cutover questions: which price book wins when two acquired companies sell to the same customer; who approves a discount, and whether the system knows; and what leadership looks at every Monday, and where that number comes from. Make these decisions before the ERP or CRM work, not after it.
Prove one number. Pick a single metric leadership already argues about, such as pipeline coverage or lead response time. Trace which records feed it and who types them in; give the reps something back that same week; then check whether the number moved and whether anyone now believes it. Only then automate.
Choose Keenan over Coutts when the 90-day assessment is really a Salesforce estate question: whether an acquisition's CRM org can be governed, released, and safely changed by AI agents, and what a platform asset is worth.
Read more
Keenan's posts analyse ServiceNow's acquisition of Sweep as a move to see inside Salesforce estates and govern agents working there without moving CRM data.
They frame a metadata graph as giving agents a dependency-resolved model of the org they are about to change, and call the reported price a strategic valuation signal for a category the Salesforce DevOps ecosystem undersold.
That is the better lens if the portfolio company's risk sits in release automation, permissions, code dependencies, platform control, or platform strategy rather than pricing habits and commercial operating cadence.
Keenan does not work the manufacturing commercial path Coutts does.
Their posts focus on ecosystem strategy and delivery tooling, not quote turnaround, price books, discount approvals, rebates, or a Monday number leadership trusts.
A sponsor wanting the Manual Tax sized in EBITDA terms and CRM/ERP decisions sequenced for a plant-based business would need to translate Keenan's platform analysis into that operating context.
Ask for that translation before relying on their work for those decisions.
Choose Markman over Coutts when the assessment needs a skeptical technology-adoption voice and an ROI test.
Read more
Markman's posts argue that AI replacing the UI is a keynote line, while adoption and production proof are the real barriers.
They warn that putting an unproven surface on production CRM costs more than a refund: a year of cleanup and a trust hit with the business.
Markman also argues that the hardest problems yield to clean data, governance, and systems that earn user trust, and writes about wanting to deliver ROI from revenue operations.
For a PE firm deciding whether to fund an AI or interface change during the first 90 days, that challenge forces the buyer to ask what will actually be adopted and measured.
The posts are less specific to manufacturing commercial operations and post-close integration.
Markman writes about RevOps ROI, AI productivity, and software delivery in broad terms, not price-book conflicts, discount approval, ERP cutover, quote-to-cash, or the operating mechanics Coutts lays out.
A buyer would get a strong adoption filter, not a commercial operations assessment built around quote-to-cash.
Choose Aleman over Coutts when the post-close problem is sales capacity and forecast credibility rather than manufacturing quote-to-cash.
Read more
Aleman's posts work through the arithmetic of hiring 10 reps against a $10M target, ramp versus sales cycle, pipeline slicing, territory damage to existing producers, and the risk that the CRM is the last place a rep admits a deal is dying.
They also argue that RevOps owns the absence of surprise, and that boards can plan around a miss they saw coming in week three but not one they discover the same day.
If the investment committee's first worry is missing the number because the capacity plan is mathematically impossible or late-stage risk is invisible, Aleman addresses that directly.
Aleman's posts sit in B2B sales operations and forecast risk, not industrial commercial operations.
They do not cover price books, rebates, contract pricing, ERP-CRM integration, or the 50 to 300 basis points of EBITDA leakage that define the manufacturing commercial operations needs Coutts addresses.
A sponsor could pair the two: Aleman on capacity and risk signals, Coutts on the commercial stack.
Ask Aleman for a manufacturing-specific view before relying on their work to resolve those decisions.
Mike Coutts's own LinkedIn posts cover the subjects here, rather than headlines or summaries.
Five posts are discussed: the Dreamforce write-up on AI adoption and messy data, the acquisition integration post, the CRM trust follow-up, the cost-of-delay argument, and the short post on spreadsheets in commercial operations.
Together these carry the arguments, examples and phrasing used across the page, including the "Manual Tax" term, the 50–300 basis points of EBITDA estimate, the three cutover questions, and the one-number trust test.
Posts by Vernon Keenan, Felix Markman and Jose Aleman provide comparisons with adjacent voices on Salesforce, revenue operations and AI adoption.
The Coutts posts here carry no publication dates, so the ideas are presented by subject rather than as a dated timeline, and the follower figure is not stated in the posts.
No long-form writing, book, talk, newsletter or other channel is mentioned in the posts here, and no engagement, impression or audience-demographic data is presented.
Those gaps are stated where they affect a decision rather than treated as settled.