Search creators⌘K
  1. Home
  2. Creators
  3. Tamie Green

Tamie Green

Tamie Green works in B2B customer success, with a focus on enterprise accounts. Their posts explain how customer success teams can connect product use to business value, support renewals and expansion, and use AI to prepare for executive conversations.

3.3K followersCustomer successAI in customer successCustomer experienceBased on 18 posts · latest Oct 2026

At a glance

Most useful for reaching customer success teams with practical renewal, executive review, and AI preparation guidance.

Best for

Sponsored post or co-hosted working session with a B2B SaaS vendor selling to customer success teams.

Not for

An automation pitch about doing customer success with fewer people, or a mass-reach buy.

Key takeaways

  • Ask 'so what' of every metric: what does it protect, prevent, or unlock?
  • AI can flag what changed, but the CSM must understand why it matters.
  • The bigger barrier to CS driving revenue is structural, not a talent gap.

Check first: Confirm rates, partnership terms, availability, competing commitments, and design support.

Main ideas
Customer success must translate product metrics into executive outcomes · AI is a briefing discipline, not a content machine · AI cannot replace the human work of influence and judgment
Audience
3,272 LinkedIn followers
Read first
5 AI moves before an executive business review
Sources for this section

What they are known for

Tamie Green writes about enterprise Customer Success as a role in proving and protecting customer value—not just maintaining relationships or reporting activity.

  • Their posts show how CSMs can connect product use to business outcomes, prepare for executive conversations, and use AI to make that work more focused.
  • Follow for practical guidance on customer renewals, revenue advising, and the judgment that technology cannot replace.

Green turns the shift from support work to commercial value into concrete practices.

  • In a post on data literacy, they suggest asking “so what” of every metric: what does it protect, prevent, or unlock?
  • A related piece on translating product data for executives shows why the framing matters: adoption figures mean little to a CFO unless they connect to outcomes such as time recovered or costs avoided.
  • They apply the same principle to renewals: relationships open the door, but measurable value helps keep it open (renewals and AI adoption).

The advice is practical and specific.

  • Their five-step QBR preparation uses call transcripts to surface concerns, customer research to add context, and AI to test an executive narrative.
  • A prompt-writing example makes the method portable: brief the AI on who is in the room, what matters to them, what is at stake, and how the answer should sound (a better brief for AI).
  • But they do not present AI as a substitute for expertise: it may flag a change, while the CSM still has to understand why it matters (what AI can and cannot tell you).

They also question whether organizations give Customer Success the capacity, tools, and compensation needed to meet expectations of revenue ownership (the structural barriers to CS as a revenue driver). That broader view complements the hands-on coaching: the work is not only about better individual practice, but also about how companies define and resource the function.

Sources for this section

Ideas and priorities

Tamie Green argues that enterprise customer success has become a value-translation job: product metrics matter only when rewritten as hours, cost, or revenue a CFO will act on.

Read more

AI is useful mainly as a briefing discipline—better prompts and pre-review preparation—but judgment, trust, and product expertise remain human work. A related priority is the structural gap between what CS teams are asked to deliver and how they are resourced.

Customer success must translate product metrics into executive outcomes

Across posts, Tamie Green returns to the same problem: adoption rates, ticket trends, and health scores are not persuasive on their own.

Read more

The work is to connect a number to what it protects, prevents, or unlocks—in one sentence. Renewal conversations have become ROI audits: relationships open doors, but measurable value keeps them open.

A 92% adoption rate means little to a CFO; saying the customer's team recovered 340 hours and translating that into labor cost gets attention. Another post describes a CSM saving a $2M account by rebuilding the ROI narrative three weeks before renewal.

Read original · Original 2 · Original 3 · Original 4 · Original 5

AI is a briefing discipline, not a content machine

Tamie Green argues most CSMs are not bad at AI; they are bad at giving instructions.

Read more

The fix is a brief that names the audience, stakes, context, and output constraints. Their AI posts focus on preparation: mining call transcripts, researching the customer's earnings calls, translating usage data, reusing a QBR template, and having AI role-play a skeptical CFO.

The provided prompt prepares AI for a 20-minute review with a CFO and COO, supplies adoption and contract renewal details, and asks for three talking points under 40 words that connect product impact to business outcomes.

Read original · Original 2 · Original 3

AI cannot replace the human work of influence and judgment

Tamie Green draws a boundary: AI can automate tasks and flag changes, but it cannot get a skeptical CFO to agree.

Read more

Influencing without authority requires speaking to executives in terms of outcomes, building stakeholder trust before problems arise, and knowing the product deeply. At the team level, the hardest part of AI-enabled customer experience is often not technology but disconnected signals, unclear ownership, and competing definitions of customer health.

One post states it plainly: AI can tell you something changed, but a strong CSM still has to understand why.

The AI argument starts with what AI can do in preparation, then sharpens into a limit: AI can flag a change, but the CSM still owns the interpretation.

Read original · Original 2 · Original 3

The bigger barrier to CS driving revenue is structural, not a talent gap

Tamie Green argues CS teams are told to act as value managers while still measured on NPS and QBR timing and resourced like a cost center.

Read more

An event poll at Customer Success Festival in New York listed bandwidth, compensation, skill set, lack of internal coordination, and missing tools as the biggest barriers; Green sees none of them as talent problems.

The audience word cloud showed bandwidth and compensation as the largest concerns. Another post says CSMs get blamed for churn caused by a departing champion, budget cuts, or product changes.

Read original · Original 2 · Original 3

A preference for building the customer success playbook from scratch

Tamie Green's career-search post says they prefer founding or first-CS-hire roles over inheriting an existing playbook.

Read more

It lists self-reported results and target sectors; an event recap also shows their continued investment in the field through volunteering.

Managed 25 strategic enterprise accounts ($12M ARR), delivered 116% NRR and 99% GRR in 2025, generated $2M expansion revenue, saved a $1.5M at-risk account, built a 30-person CS team, and cut time to adoption from 45 to 29 days. These figures come from Tamie Green's job-search post; ask for supporting documentation before relying on them.

Read original · Original 2

From broad workplace thought leadership to customer success specifics

One post is a generic remote-work and outsourcing piece with dense emoji and stacked hashtags, and no customer-success specifics.

Read more

The others focus tightly on enterprise CS, renewals, data literacy, and AI-assisted executive preparation. The difference suggests a change in register and subject focus; ask for the posts' dates to establish when that shift occurred.

The earlier post asks whether remote is the new word for outsourcing and lists collaboration, cost, entrepreneurship, productivity, and the digital future. Later posts open with a CSM scenario, a renewal problem, or a customer-success claim.

The posts show a clear shift from broad workplace commentary to a specific enterprise customer-success argument.

Read original · Original 2 · Original 3 · Original 4

Sources for this section

Start with their work

5 AI moves before an executive business review

This post answers 'How does Green actually use AI in customer success?' and gives newcomers a quick look at their practical, step-by-step approach.

Read more

Start here for Green's most detailed public example of turning AI into a repeatable approach for CSMs.

Tamie Green lays out a specific AI-assisted sequence for preparing for quarterly business reviews.

  • The post describes five steps: pull call transcripts to find repeated concerns and renewal objections; research the customer's business; translate usage data into CFO language like time recovered or cost avoided; build a reusable QBR template; and ask an AI to role-play a skeptical CFO to stress-test the narrative.
  • The advice focuses on using AI to improve the story rather than just produce more data.

For brands planning a campaign

For a vendor selling AI tools to customer success teams, this post is a natural fit for co-marketing or sponsored content: it demonstrates a specific use case a CS leader could adopt. It could also serve as a proof point in a campaign about AI adoption in CS.

Data literacy: turning numbers into stories a CFO acts on

This answers 'What does Green mean by data literacy, and why does it matter?' It introduces their core argument: CSMs must move from reporting to advising.

Read more

Tamie Green distinguishes reporting from advising.

  • The post says most CSMs can pull a metric, but data literacy means knowing that 87% adoption means the customer's team operates faster than 70% of companies at the same stage—and being able to say what that protects in dollars or hours.
  • Green encourages CSMs to ask 'so what' about every number and connect metrics to business outcomes.
  • It reframes the CSM role as a translator for executives.

For brands planning a campaign

Useful for analytics, BI, or CS platform vendors positioning their products as tools that help CSMs translate data into executive-ready narratives. A campaign could highlight this shift as a reason to adopt outcome-focused tools.

Renewal conversations became audits

This post answers 'Why does Green emphasize ROI and business value in renewals?' It sets up the business context for their other advice and offers an early read for anyone assessing their understanding of enterprise renewal dynamics.

Read more

Tamie Green describes a shift in enterprise accounts: renewal conversations changed from relationship check-ins to ROI audits.

  • Executives ask 'show me the ROI,' and champions need ammunition.
  • Green says relationships still open doors, but measurable value keeps them open.
  • The post points to procurement involvement, CFO attention, and the insufficiency of 'we have a great relationship,' then explains how AI speeds up the translation work.

For brands planning a campaign

A campaign for value-selling, ROI, or revenue intelligence tools could use this post to highlight the need for CSMs to produce quantified business cases. It also supports content about preparing champions with ROI evidence.

TSIA 2026 report calls CSMs value managers

This post answers 'Where does Green get their framing about the CSM role?' and shows how they connect their arguments to industry research and use external reports to challenge current measurement practices.

Read more

Tamie Green cites the TSIA 2026 State of Customer Success report, which calls CSMs 'value managers.' They point out that most CS teams are still measured like support reps—on NPS and QBR timing.

  • Green shares an example of a CSM saving a $2M account by reframing the ROI narrative three weeks before renewal, but says that work is often dismissed as just doing the job.
  • The post argues that organizations need to measure commercial confidence, data literacy, and outcome ownership.

For brands planning a campaign

For a vendor selling CS measurement or analytics software, this post offers a direct hook: the gap between what the role demands and how it is measured. A campaign could invite Tamie Green to discuss shifting metrics from support to value.

Open to work: Senior or Founding Customer Success role

This post answers 'What has Green actually done, and what kind of role are they seeking?' It is the clearest source on their track record and career goals, so it belongs early in any assessment.

Read more

Tamie Green says they are looking for a next role as a Senior, Strategic, or Founding Customer Success Manager.

  • The post lists concrete accomplishments: managed 25 strategic enterprise accounts worth $12M in ARR, delivered 116% net revenue retention and 99% gross revenue retention in 2025, generated $2M in expansion revenue, saved a $1.5M at-risk account that grew into a new location, and built a 30-person CS team from the ground up at a B2B SaaS company, cutting time to adoption from 45 to 29 days.
  • Green says founding roles appeal because they want to build the playbook, not just run it.

For brands planning a campaign

For a company or brand considering hiring Green or inviting them into an advisory role, this post provides numbers to evaluate fit. It also gives content marketers a concrete example of a personal brand post that blends achievements with a clear call to action.

You're not bad at AI. You're bad at giving instructions.

This post answers 'How does Green approach AI prompting?' and shows their teaching style: they use a before-and-after example to make a practical point.

Read more

Start here to see how Green turns AI advice into a repeatable skill for CSMs.

Tamie Green argues that many CSMs struggle with AI because they give generic prompts.

  • The post contrasts a vague request ('Write a follow-up email after a QBR') with a detailed brief specifying the audience (a CFO and COO), their priorities, the customer context, the risks, and the desired output format.
  • Green shows the exact prompt structure and asks readers to share tasks that AI gets wrong.
  • The piece makes the difference between a request and a brief concrete through example.

For brands planning a campaign

A campaign for an AI writing assistant or CS enablement tool could use this post to demonstrate the value of better prompting. It also works as a lead-in to a workshop or template resource.

Sources for this section

Topics and approach

Posts cited for each topic
Translating product data into language executives act on5
AI as a briefing discipline rather than a content machine5
Format, and a shift in register across the corpus5
Where AI stops and judgment starts4
The structural gap between what CS is asked to deliver and how it is resourced3
Building customer success from scratch, and a current job search2

Translating product data into language executives act on

Across these posts, a recurring argument is that adoption rates, ticket trends and health scores alone do not persuade a CFO.

Read more

Tamie Green describes pulling usage, health and ticket data from separate systems, then rewriting it as hours recovered, cost avoided or revenue protected before a quarterly business review.

  • One post recounts a CSM who saved a $2M account by rebuilding the ROI narrative three weeks before renewal.
  • Another argues that renewal conversations now resemble audits: procurement wants value that holds up in a spreadsheet, not relationship goodwill.
  • A 92% adoption rate lands only when mapped to labor cost.

Apply the same test to every metric: So what does this number protect, prevent or unlock? Require a one-sentence answer before using it with an executive.

For brands planning a campaign

For help translating renewal or expansion outcomes, bring live product metrics and reframe them as financial outcomes tied to a named renewal. Ask in advance what the account team should provide — usage data, executive names, contract timing — so the session produces a usable narrative rather than general advice.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

AI as a briefing discipline rather than a content machine

The AI posts focus on inputs, not tools.

Read more

One argues that most people are not bad at AI; they are bad at giving instructions.

  • It then supplies a full prompt that specifies the audience, stakes and output length before asking for talking points.
  • Another lists five pre-review moves: mine call transcripts for repeated concerns and unmet commitments; research the customer's earnings calls and leadership changes; convert usage data into CFO language; reuse one QBR template per account; and have AI play a skeptical CFO the night before.
  • A later post states the limit plainly: AI can tell you something changed, but a strong CSM still has to understand why.

Publishes the exact prompt text and an ordered sequence of pre-review steps, with attendees expected to run them against their own account numbers.

For brands planning a campaign

This works as a hands-on format: participants bring an upcoming review and leave with a written prompt brief and a tested narrative. Provide sample account data or let attendees use their own; the method depends on running prompts against real figures, not demonstrating them abstractly.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Where AI stops and judgment starts

Tamie Green consistently draws a line around automation.

Read more

One post says AI can automate tasks but cannot get a skeptical CFO to agree.

  • Influencing without authority, it argues, rests on three human skills: speaking to executives in terms of outcomes, building stakeholder trust before problems arise, and knowing the product well enough to be the expert in the room.
  • Another distinguishes reporting from advising: pulling a metric is reporting; explaining what it protects in dollars or hours is advising.
  • A third post, about an AI and customer-experience report, makes the same point at the team level: the technology is rarely the hardest part; disconnected signals, unclear ownership and competing definitions of customer health are.

For brands planning a campaign

Sets clear expectations for an AI-themed engagement: this is not an automation pitch. It suits a discussion or session on where CS headcount and judgment remain necessary, and gives a brand a credible counterweight to tool-first messaging.

Examples: Source 1 · Source 2 · Source 3 · Source 4

The structural gap between what CS is asked to deliver and how it is resourced

An event recap reports a live audience poll at the Customer Success Festival in New York on the biggest barrier to CS driving revenue.

Read more

The word cloud returned bandwidth, compensation, skill set, lack of internal coordination and missing tools.

  • Tamie Green's reading: none is a talent problem; each is structural.
  • Related posts make the same case from other angles: teams are told to act as value managers while still being measured on NPS scores and whether reviews happened on time; CSMs are held accountable for churn caused by a departing champion, a budget cut or a product that shipped differently than promised.

Combines field observation with a poll at one event. The resourcing argument is based on experience, not data in these posts.

The word-cloud evidence comes from one event recap, and the poll is not broken down by segment; treat the ranking as directional.

For brands planning a campaign

For a brand selling CS tools or services, messaging that starts with mindset will read as out of touch here.

  • Capacity, compensation and explicit ownership are more credible entry points.
  • A candid session or sponsorship on resourcing would fit the material better than a productivity pitch.

Examples: Source 1 · Source 2 · Source 3

Building customer success from scratch, and a current job search

One post announces an active search for a senior or founding customer success role and lists self-reported results: 25 strategic enterprise accounts and $12M ARR, 116% NRR and 99% GRR in 2025, $2M in expansion revenue, a $1.5M at-risk account saved and later grown, and a 30-person CS team built with playbooks and training that cut time to adoption from 45 to 29 days.

Read more

They prefer founding or first-CS-hire work over inheriting an existing playbook, and target B2B SaaS and tech plus healthcare, life sciences and ingredient or CPG companies, hybrid in New Jersey or New York or remote. A second post describes volunteering at a customer success event in New York to find something that changes how they operate the next day.

The performance figures appear in a job-search post and are not confirmed elsewhere; verify them in conversation.

For brands planning a campaign

This is the most directly relevant material for a hiring or advisory brief on renewal and expansion outcomes.

  • A concrete next step is a paid interview or working session on the brand's own renewal, testing the approach against real accounts.
  • The search is active, so confirm availability, timing and any competing commitments directly.

Examples: Source 1 · Source 2

Format, and a shift in register across the corpus

Most posts follow a consistent pattern: a short hook, a numbered or arrowed list, a one-sentence conclusion and a closing question inviting replies.

Read more

Prompts and templates appear verbatim, and one post is built around a carousel.

  • A post on remote work and outsourcing takes a different tack: broad thought leadership, dense emoji and stacked hashtags, with no customer-success specifics.
  • Individual post dates are not stated, so the sequence here reflects subject matter and voice rather than timestamps.

Hook, list, conclusion and closing question, inviting readers to share their own case in the replies.

No visual or carousel assets are included, and no engagement or reach data is available; performance by format is unknown.

For brands planning a campaign

Text-first posts are easy to quote and excerpt, and a sponsored post could follow the existing structure without extra production overhead. Ask whether design support or carousel production is available.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Sources for this section

Brands and businesses

The saved posts document no sponsor, affiliate program, owned business, employer, client, investment, or disclosed commercial partnership with a named business.

Read more

Brands appear as tools or cited reports: Claude in an AI QBR prompt, Slido in an event poll, and McKinsey and TSIA reports.

  • The posts state no relationship with those brands.
  • No post dates or date range are provided; ask for dated examples.
Sources for this section

Topics and similar creators

Tamie Green writes about enterprise customer success as a value-translation job: adoption and usage numbers must be translated into hours recovered, cost avoided, or revenue protected before a renewal conversation reaches a CFO.

Read more

Read the AI posts alongside the value posts: AI can help prepare for a review by mining call transcripts, researching the customer's own earnings calls, or rehearsing a skeptical CFO, but it cannot decide what the account needs.

  • A second thread covers the gap between what customer success teams are asked to deliver and how they are staffed, measured, and paid.
  • The short LinkedIn text posts follow a familiar format: a hook, a numbered or arrowed list, a one-line close, and a question to readers.
  • Several include copyable prompts and a named pre-review sequence, the most directly reusable material.
  • For something to use today, start with the prompt posts; for the commercial argument, start with the renewal posts.
Customer success Enterprise customer success AI in customer success Translating metrics into business outcomes QBR preparation Renewal and retention Customer success leadership Customer experience Prompt templates LinkedIn text posts Customer success managers B2B SaaS

Chris Patin

Both write practical enterprise customer success advice as structured LinkedIn posts, treating renewal as something to prove continuously rather than address when the contract date arrives.

Read more

Patin argues that quick wins in the first 30 days build lasting retention, and that renewals should start months ahead with data, stories, and outcomes. Green makes the same case through the numbers: relationships open the door, and measurable value keeps it open.

Patin's posts are tactical playbooks: numbered onboarding or renewal series with steps and a single client example. Green focuses instead on how executives should measure the work, offering AI prompts and a preparation sequence rather than a step-by-step customer success playbook.

Read original · Original 2 · Original 3 · Original 4

Priyadarshini Ravichandran

Both describe customer success as guiding customers through change and influencing people who do not report to you.

Read more

Ravichandran notes that CSMs work across departments without direct control, making influence and empathy their main tools; adoption alone is not the goal, sustained value is. Green makes a similar argument, saying AI can automate tasks but cannot get a skeptical CFO to agree.

Ravichandran writes about change management and adoption inside the customer's organisation, citing Gartner's estimate that most digital transformation initiatives miss expectations because of change management rather than technology. Green focuses on translating product metrics into financial language for executives and using AI to prepare for those conversations.

Read original · Original 2 · Original 3 · Original 4

Mason Moyer

Both advocate proactive customer success: spot adoption trends before they become renewal risks, understand why the customer bought beyond usage numbers, and own the whole journey rather than one part of it.

Read more

Green's version is that AI can tell you something changed, but the CSM still has to work out why.

Moyer's posts are short, question-led reflections on mindset and ownership, without metrics or prompts. Green pairs that mindset with explicit financial framing — hours recovered, cost avoided, revenue protected — along with copyable AI prompts and a pre-review checklist.

Read original · Original 2 · Original 3 · Original 4

Sources for this section

Audience

Tamie Green’s LinkedIn posts address people in B2B software customer success: CSMs, CS managers, and CS leaders carrying renewal and expansion targets.

Read more

They cover issues that matter to the role: protecting renewals when procurement gets involved, executive business reviews, translating adoption numbers into time-recovered and cost-avoided language, prompting AI with a real brief instead of a vague request, and the mismatch between role demands and how teams are measured.

  • The only measured audience figure is a LinkedIn follower count of 3,272, recorded on 9 October 2026.
  • For a B2B SaaS company hiring a customer success leader for renewal and expansion outcomes, the topics warrant a closer look, but the audience data is thin.
  • Ask Tamie for LinkedIn follower analytics or a recent audience survey covering seniority, job function, and geography, plus engagement examples showing CS leaders or CS directors responding to the renewal, QBR, and value-translation posts.

LinkedIn followers

3,272

LinkedIn profile for Tamie Green · 2026-10-09

Sources for this section

Partnership options

Tamie Green's LinkedIn posts focus on customer success rather than brand partnerships.

Read more

They discuss enterprise CS topics — renewal narratives, executive reviews, data literacy and AI-assisted preparation — without promoting a product or naming a commercial partner.

  • A job-search post asks for introductions to Senior, Strategic or Founding Customer Success roles and lists recent results, including 25 strategic enterprise accounts, $12M ARR, 116% NRR and a 30-person CS team built from scratch.
  • For partnership inquiries, contact them through the LinkedIn profile linked in the identity section; no dedicated partnership or media inquiry page is linked there.
Sources for this section

Campaign fit

A campaign to shortlist

A sponsored post or co-hosted working session with a B2B SaaS vendor selling to customer success teams — AI enablement, CS analytics, review tooling or value-selling software.

Read more

The fit is both audience and method.

  • Tamie Green's readers are CSMs, CS managers and CS leaders with renewal and expansion targets: the same people such a vendor wants to reach.
  • The posts offer material a sponsor can build on: a full prompt naming the audience, stakes and output length; a five-step sequence to run before an executive business review, from mining call transcripts for repeated concerns and unmet commitments to having a model play a skeptical CFO the night before; and a recurring test for every metric — what does this number protect, prevent or unlock?
  • A sponsored post can follow the familiar format of a short hook, numbered list and closing question while offering standalone value, because the advice concerns the inputs to the work rather than a product demo.
  • The examples distinguish them from a general AI commentator: they address specific account situations (a renewal three weeks out, a CFO in the room, procurement asking for ROI) and leave readers with something reusable.
  • Before scheduling, ask about rates, partnership terms and availability.
  • No rate card, media kit or partnership terms appear in the posts, and the September 2026 job-search post makes availability and competing commitments worth confirming.
  • No visual or carousel assets appear, so ask whether design support is available.

When to choose a specialist

An automation pitch built around doing customer success with fewer people, or a mass-reach buy that needs a large general audience.

Read more

On headcount, an event recap reports an audience poll on the biggest barrier to CS driving revenue.

  • The word cloud returned bandwidth, compensation, skill set, lack of internal coordination and missing tools; Green's reading is that none is a talent problem and each is structural.
  • The same argument runs through the writing about teams told to act as value managers while still measured on NPS scores and whether reviews happened on time.
  • The boundary around automation is just as firm: AI can automate tasks, but it cannot get a skeptical CFO to agree.
  • The work that moves a renewal depends on executive alignment, stakeholder trust and product knowledge deep enough to make someone the expert voice in the room.
  • An audience drawn to judgment as the scarce resource is a poor fit for a 'do more with fewer CSMs' message.
  • Reach is another concern: the only published audience figure is a LinkedIn follower count of 3,272, with no seniority, job function or geography breakdown and no post-level engagement, reach or conversion data.
  • Ask for audience and performance data before considering a broad-awareness campaign or forecasting responses, even among CS leaders.
  • A future-of-work or outsourcing thought-leadership campaign is a weaker fit for the same reason.
  • The one remote-work post in the earlier part of the record stands apart in register, with stacked hashtags and dense emoji but no customer-success specifics; it does not show that the current audience arrives for that style of content.
A worked campaign example

Working angle: bring a renewal you are worried about.

  • A sponsoring CS platform runs one sponsored post and a small working session based on Green's published method.
  • The post opens with a moment readers recognise — a renewal that looks safe until procurement asks for ROI — then lays out five moves from the pre-review sequence: mine the last two call transcripts for repeated concerns and unmet commitments; research the customer's own earnings call and leadership changes; convert the adoption number into hours recovered or cost avoided rather than a percentage; reuse one review template per account; and have a model play a skeptical CFO the night before to find weak spots first.
  • It closes with the question their posts use, asking readers to name one metric they have never connected to a business outcome, and invites them to bring that account to the session.
  • The follow-up session does the work rather than describing it.
  • Attendees bring one live account, its usage figures and an upcoming review date, and leave with a written prompt in the published format — who is in the room, what they care about, what is at stake and how long the output should be — plus a narrative that has already survived skeptical-CFO pushback.
  • The sponsor supplies sample or anonymised account data for anyone who will not use their own, along with a blank worksheet so the method keeps working after the session.
  • Before proceeding, ask for measurement data, production support and availability and terms: no public engagement, reach or conversion figures or visual and carousel assets appear in the posts, and the September 2026 post is a job search, not a sponsorship offer.
  • If the goal is hiring rather than a campaign, Green's stated record offers a starting point for an interview — 25 strategic enterprise accounts and $12M ARR, 116% net revenue retention and 99% gross revenue retention in 2025, $2M in expansion revenue, a $1.5M at-risk account saved, and a 30-person CS team built from scratch with time to adoption cut from 45 to 29 days.
  • These are Green's own figures, not confirmed by another source.
Sources for this section

Who else to consider

Chris Patin, MBA, CCSM, CSM

Consider Chris Patin when the campaign needs a series format a CS team can follow across the customer lifecycle.

Read more

The two posts reviewed use that format: one numbered post on quick wins in the first 30 days of onboarding and one on renewals.

  • Each ends with a question to the reader, giving a sponsor a format to reuse campaign beat by campaign beat.
  • The advice on early adoption is concrete: find a use case that solves an immediate pain, prioritise a feature that is easy to adopt but visible, and publicise the win with dashboards, shoutouts and an executive summary.
  • The account story is specific: a client with low engagement after onboarding moved to a single reporting feature that saved their team ten hours a week, and adoption rose.
  • Choose this writer for campaigns aimed at practitioners who need something to apply this week on onboarding and renewal timing, and when the sponsor's product supports that kind of early, visible win.

For a campaign that needs a buyer-inspectable account narrative or a working-session asset a sponsor can hand out, Tamie Green's posts offer no prompt-level material or executive-room framing—no CFO, procurement or business review workflow—and describe one quantified account outcome rather than several.

  • Chris Patin's posts stop earlier on this need.
  • A sponsor would need to build the account narrative or working-session asset separately for Chris Patin; Green's published method already provides its shape.

Examples: Source 1 · Source 2

Priyadarshini Ravichandran

Consider Priyadarshini Ravichandran when the campaign focuses on change management and technology adoption rather than the mechanics of a renewal.

Read more

The two posts reviewed take a leadership view: a CSM guiding transformation, translating features into real-world impact, navigating internal resistance and treating value realisation—not usage—as the goal.

  • One post backs the argument with outside authority, citing a Gartner figure that over 70% of digital transformation initiatives miss expectations because of change management rather than the technology itself.
  • Choose this writer when the sponsor sells into transformation budgets, the audience is CS leaders deciding how to move an organisation, and an analyst figure strengthens the case more than a how-to sequence would.

The difference is evidence of practice.

  • These posts frame and argue; they do not walk through a numbered procedure, publish a reusable prompt or give account-level numbers or named situations.
  • A sponsor who wants attendees to leave a session with a written asset would need to design that exercise from scratch.
  • Buyers comparing writers on renewal and expansion outcomes have less to inspect here than in Tamie Green's step-level posts or Chris Patin's onboarding example.

Examples: Source 1 · Source 2

Mason Moyer

Consider Mason Moyer when the campaign calls for a plain, steady voice on CS fundamentals rather than an operational playbook.

Read more

The two posts reviewed define the role with two words: proactive and ownership.

  • The proactive post lists what that looks like in daily work: noticing adoption trends before they become renewal risks, understanding the customer's reasons beyond product usage, building touchpoints not driven by urgency, aligning internally and reaching out before the customer realises they need help.
  • The ownership post covers taking responsibility for the whole journey, agreeing on goals and success metrics early, following through on commitments and leading when the situation is ambiguous.
  • The register is low-key, short and discussion-led.
  • Choose this writer when the sponsor wants a softer editorial tone, the product supports proactive health monitoring or accountability workflows, and the topic is the mindset behind retention rather than a specific tactic.

Across the two posts, there are no account examples, metrics or named situations, so readers cannot see how the advice played out or what it protected.

  • For a campaign that needs to show the audience a practice produced renewals or expansion, this is the lighter option of the three.
  • The sponsor would need to supply a concrete example and usable asset.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Concept: prepare for the renewal conversation

Sources for this section

Research methodology

  • This page summarizes examples and arguments from the full text of 12 saved LinkedIn posts from Tamie Green's linked account, and includes the account profile's follower count.
  • The posts cover enterprise customer success, renewals, business value, AI-assisted preparation, data literacy, event observations, a job-search post, and an earlier remote-work and outsourcing piece.
  • Exact post dates are not stated consistently.
  • The posts do not state engagement, reach, seniority, geography, sponsorship terms, a rate card, or a media kit, and no independent employer-side sources are included here.
  • Career metrics in the job-search post are self-reported and are not confirmed by other sources.
  • The posts do not document sponsorship, affiliate, ownership, employment, client, investment, or disclosed partnership with a named business.

Brands they talk about