Whatfix

Volume I: three accounts

Three target accounts · buyer personas · email, LinkedIn, and Cold Call Script

Voya Financial

Buyer map

21 business days, four people - multithreading

Personas_full sequence, day by day

Matt Lehmann - VP, HR Operations & Chief of Staff to the CHRO

Atlanta > End user / influencer

subject: fifteen modules, two releases

Hi Matt - you're on the steering committee for the workday southeast user group. three events a year, a hundred plus workday users in the room each time.

that's a lot of unpaid work, and nobody does that unless they actually like the problem. which is why i wanted to ask you rather than anyone else.

in those rooms, is adoption still mostly a training conversation, or has that shifted?

harshit

LINKEDIN · Day 2 · Connection note

matt — came across your work while looking at how large workday estates handle release adoption. fifteen modules with vndly and extend in the mix is an unusually deep footprint. following along.

CALL / VOICEMAIL · Day 5 · First live attempt — opener + discovery + ask

OPENER: "matt, [your name] calling from whatfix. you don't know me — but i think you can help me for a moment, can i have thirty seconds and you can decide if it's worth the rest?" [pause. wait for the yes.]

"i'm calling because voya has an open req for a director of workday people systems, and the description puts release readiness, change management and adoption in one job. that's three jobs at fifteen modules."

"can i ask — until that seat is filled, who's actually carrying the adoption half?"

DISCOVERY (ask in order): 1) When a Workday feature release changes a business process, what actually happens between the release notes arriving and an employee doing the new thing correctly? 2) Who writes the end-user content for that, and how long does a cycle take from release notes to published? 3) Where do the questions land when someone is stuck mid-task — HR case queue, the offshore team, a colleague, or nowhere? 4) How much of your HR case volume is "how do I" rather than a genuine exception, and is anyone counting that split? 5) When does the Director of People Systems role get filled, who would own tooling decisions in the meantime, and who else would be in the room when you look at this?

THE ASK: "here's what i'd suggest. twenty minutes with [ae name], who does this for workday estates at your scale all day. no deck — they'll take your actual module list and your release cycle and show you where the rebuild cost sits." "would tuesday morning or thursday afternoon work better?"

Note: Question 5 both gets a timing anchor and surfaces the rest of the buying committee without asking "who's the decision maker" directly. Question 4 is the one most likely to produce a quotable line for the AE.

CALL / VOICEMAIL · Day 5 · Voicemail (under 20 seconds)

"matt, [your name] from whatfix. calling about the director of workday people systems req you've got open — specifically the line about release adoption. sending an email now with what i mean."

EMAIL · Day 21 · Break-up

subject: closing this out

Worth a quick yes/no?

Note: In the source file this entire break-up email is a handwritten-note-style image (shown above), addressed to "Jeff" even though the sequence table lists Matt as the day-21 recipient — flagging that inconsistency rather than resolving it silently.

Erika LaRosa — Director, Learning & Development

Windsor, CT · Champion — owns the content cost

EMAIL · Day 3 · Wedge A, content angle

subject: articulate, twice a year

Erika — you wrote in march that modernising training isn't about chasing tools. agreed, which is why i'm asking about a cost rather than a tool.

voya runs workday across fifteen modules and takes two feature releases a year. your team authors in [articulate / captivate].

so twice a year, content that took weeks to build is partly wrong and somebody rebuilds it by hand.

how many weeks does that cycle actually take you?

Note: Send a LinkedIn connection request alongside this email — referenced in the original draft but written here as a separate step, not folded into the email body.

LINKEDIN · Day 11 · DM

curious about one thing, Erika — when a workday release changes a business process, does your team rebuild the course, or patch the job aid and hope people find it?

asking because the answer differs a lot between companies your size and i'm trying to get a real picture rather than a vendor one.

Sudarsan Nagiri — IT Director, Corporate Applications

Minneapolis · Technical buyer — a gate, not a champion

EMAIL · Day 6 · Wedge B, deployment and governance

subject: how this deploys, before anything else

Hi Sudarsan — you're asset custodian for 90+ corporate applications including workday and oracle erp, so i'll lead with the part you'd ask about anyway.

whatfix deploys either as a js snippet or as an it-managed browser extension. no workday tenant change, no configuration change, no vendor dependency. soc 2, iso 27001 and 27701, hipaa, gdpr. customer data isn't used for model training.

worth fifteen minutes on the deployment model, or should i send the architecture doc?

Note: Sudarsan is a gate, and gates open when you arrive with the answer rather than the request. Nothing here asks him to care about HR outcomes — that isn't his metric.

CALL / VOICEMAIL · Day 13 · Double tap — voicemail

"sudarsan, [your name] again. one question and i'll leave it — of the indirect spend still going off-process, do you know how much of it is people who cannot find the right path versus people choosing not to take it? emailing now."

EMAIL · Day 13 · Double tap — email (inside 10 minutes of the call)

subject: the question from the voicemail, in writing

cannot find it, or will not use it — of the spend still going around the new process, how much is people who cannot find the right path versus people who found it and went around it anyway?

the first one is solvable on the screen. the second one is a policy problem and i would tell you so.

Rajat Kalia — SVP & CTO, Workplace Solutions Technology

Greater Hartford · Economic buyer — customer-facing estate only

EMAIL · Day 10 · Wedge C — participant side only

subject: myvoyage, the first ninety seconds

rajat — voya published that myvoyage reached about 89,600 eligible employees across a full year. against the eligible population that's a participation number with a lot of headroom, and you'd know better than me where it's lost.

my read is that it isn't awareness. it's the first ninety seconds inside the product.

sentry insurance runs in-app guidance on both their internal workday and their customer and agent portals. is the participant side something your team is looking at this year, or is it further down the roadmap?

Note: Rajat only ever hears about the customer-facing estate. He owns what Voya sells, not what Voya runs internally — writing to him about internal Workday adoption is the wrong estate and he'll spot it in one line.

Jeff Armbrister — bonus contact

IT Manager, HR Program Portfolio, Quality Assurance and Release Management (Atlanta) — not one of the original four, added because he personally owns the twice-yearly Workday release-readiness cycle. Opened later, day 17, as a fresh angle.

EMAIL · Day 17 · New angle

subject: release readiness, qa side

jeff — you run qa and release management for voya's hr program portfolio, which means the workday feature releases land on your desk twice a year before they land on anyone else's.

genuine question: how much of that cycle is regression testing, and how much is rewriting what end users are told?

asking because the second half is the part most teams can't measure.

Joint / account-level email

Sent to Matt, Erika, and Sudarsan together, day 15, one thread.

EMAIL · Day 15 · Account email

subject: who owns adoption at voya

matt, erika, sudarsan — putting you on one thread rather than guessing.

voya has an open req for an avp director of workday people systems. the description names supervising semi-annual release readiness, testing, change management and adoption across fifteen modules — which means that work exists today and is currently spread across the three of you.

which of you owns that decision until the seat is filled? twenty minutes with whoever it is.

US Foods Holding Corp. (NYSE: USFD)

Ticker / scale: ~30,000 associates

Wedge: Maverick spend and last-mile process adoption — the gap between deploying a new indirect-procurement system (Ariba) and employees actually following it instead of working around it.

Buyer map

21 business days, four people, four channels

Personas — full sequence, day by day

Jason Ricketts — Senior Director, IT — Shared Business Systems & Finance

Simpsonville, KY · Technical buyer — the anchor

EMAIL · Day 1 · Anchor opener

subject: the 20 to 75 gap

Colonel, I'm assuming that's the right address for an Honorable Order commission.

Jokes aside, your Q2 call mentioned $20M in indirect procurement savings YTD, with $75M expected this year, right?

The thing that can quietly eat into numbers like that is maverick spend — people who never fully adopt the new process and find a way around it.

And with the new indirect procurement system only just past baseline deployment, I imagine that becomes even more relevant.

We help close that last-mile gap with guidance inside the app, without adding code to Ariba or getting in the way of the request flow.

Would you be open to 20 minutes to see if this is something you're running into at US Foods?

LINKEDIN · Day 2 · Voice note

"We help companies make sure employees actually follow the new processes instead of finding workarounds. Given the scale at US Foods and the Blue Yonder rollout, I was curious if that's something you're seeing too."

CALL / VOICEMAIL · Day 5 · Voicemail

"Jason, [your name] from Whatfix. Calling about the indirect procurement number on your Q2 call — specifically the gap between the system going live and people actually using it the way it was designed. Sending an email now with what I mean."

CALL / VOICEMAIL · Day 13 · Double tap — voicemail

"Jason, [your name] again. One question and I will leave it — of the indirect spend still going off-process, do you know how much of it is people who cannot find the right path versus people choosing not to take it? Emailing now."

EMAIL · Day 13 · Double tap — email (inside 10 minutes of the call)

subject: cannot find it, or will not use it

Of the spend still going around the new process, how much is people who cannot find the right path versus people who found it and went around it anyway?

The first one is solvable on the screen. The second one is a policy problem and I would tell you so.

Nicole Hajdrowski — Vice President, Learning & Development

Greater Chicago · Champion

EMAIL · Day 3 · Training angle

subject: aspire to lead, and the other 51 weeks

Nicole — you wrote in February about your CEO, CHRO and Chief Merchant actually sitting in the room for Aspire to Lead. That is rarer than it sounds.

The part no leadership academy reaches is the associate stuck mid-requisition in a system that changed last quarter. That moment is where process adoption is won or lost, and it does not have a classroom.

How does your team handle enablement for a system change today — new content, or a job aid people have to go find?

LINKEDIN · Day 11 · DM

One thing I keep asking L&D leaders: when a system changes, does your team rebuild the course, or patch the job aid and hope people find it?

The answer differs a lot at 30,000 people versus 3,000 and I am trying to understand where the line actually sits.

LINKEDIN · Day 12 · Meme

Pam Federick — Senior HRIS Analyst

— · End user / influencer

EMAIL · Day 6 · No ask, one question

subject: the screen everyone gets stuck on

Hi Pam, you are the senior HRIS analyst at a 30,000-person distributor, which means the "how do I" questions land on you before they land anywhere else.

Genuine question, and no ask attached: what is the one screen or process where you answer the same question over and over?

Asking because that answer is usually more accurate than anything a ticket report shows, and I am trying to get a real picture rather than a vendor one.

Note: Her LinkedIn profile displays as "Pam Rodgers" — this email deliberately opens on the problem rather than a first name, in case the name on file is wrong. Confirm identity before sending.

John Tonnison — EVP, Chief Information & Digital Officer

Tampa, FL · Economic buyer — one touch only

EMAIL · Day 10 · A number in the subject line

subject: $174m, and what gates the return on it

John — $174M of capex year to date into IT and distribution facilities, AI across forecasting, labor planning and routing, robotics scaling from one site to six.

All of it has the same gate: whether the people on the other end use it the way it was designed. That gate is not a training budget, it is the first thirty seconds inside the screen.

Is adoption something your team measures per system today, or per program?

Joint / account-level email

Sent to Jason, Nicole, and Pam together, day 15, one thread.

EMAIL · Day 15 · Account email

subject: who owns adoption at us foods

Jason, Nicole, Pam — putting you on one thread rather than guessing.

US Foods has told the market it expects more than $75M from indirect spend this year and more than $100M in 2027. Those numbers assume people use the new process.

Between IT, L&D and HRIS, which of you owns that assumption? Twenty minutes with whoever it is.

Ryder System, Inc. (NYSE: R)

Ticker / scale: Large frontline workforce (technicians, drivers, warehouse)

Wedge: Provable training evidence for a frontline workforce — the gap between a completion record and proof someone can actually do the task, surfaced through an internal champion who has already solved this manually.

Buyer map

21 business days, four people - multithreading

Personas — full sequence, day by day

Eliza Fendell — Director, Technology Change Enablement

Waltham, MA · Champion — first door

EMAIL · Day 1 · Champion opener

subject: 96% and 95%, and what they cost

Eliza — you took Workday HCM and Finance to 96% adoption across the US and Canada, then built #LearnWithRyder to a 95% activation rate against a 48% peer benchmark.

You did both with a newsletter, a Workday Wednesday series, and gift cards. That is genuinely impressive and it is also entirely dependent on you keeping it up.

When the next acquisition lands, does that whole machine have to be rebuilt by hand?

Note: Every number here is hers and is public — her LinkedIn profile, plus LinkedIn's own talent-blog write-up of #LearnWithRyder. The last line is the only one doing sales work, and it names a real risk rather than a product.

LINKEDIN · Day 2 · Connection note

Eliza — read the LinkedIn write-up of #LearnWithRyder. Driving 95% activation with change-management technique rather than mandate is the part most people skip. Following your work.

CALL / VOICEMAIL · Day 5 · Voicemail

"Eliza, [your name] from Whatfix. Calling about #LearnWithRyder — specifically what happens to it when you are not personally driving it. Sending an email now with what I mean. [number]"

EMAIL · Day 21 · Break-up

subject: closing this out

Last one from me.

If the timing is just wrong, reply with the next big system change on your roadmap and I will come back a quarter before it rather than keep guessing.

If it is not relevant at all, that is a useful answer too.

Kristen Frankovich — Director, Training and Development

Miami–Fort Lauderdale · End user / influencer

EMAIL · Day 3 · Completion vs. capability

subject: completion, and capability

Kristen — you build in Articulate for a workforce that is largely not sitting at a desk. Technicians, drivers, warehouse.

Which means a completion record proves someone clicked through a module, not that they can do the task. Those two things get treated as the same number in almost every reporting pack I see.

At Ryder, is anyone asking you for the second one yet?

LINKEDIN · Day 4 · Follow-up

Kristen - This felt relevant after our conversation, hahaha

LINKEDIN · Day 11 · DM

Curious about one thing — when leadership asks whether a team was trained on something, what do you actually hand them? A completion report, or something closer to evidence?

Asking because the answer differs a lot by industry and I am trying to get a real picture rather than a vendor one.

Rajeev Ravindran — EVP & Chief Information Officer

Miami, FL · Technical buyer

EMAIL · Day 6 · His own framing

subject: self-service, the actual blocker

Rajeev — you said a few years ago that technology was getting easier to use and Ryder needed to look at self-service to move faster. You then moved tier-one RPA out of IT and into the business that uses it.

That model only holds if the application can teach a business user in the moment. Otherwise self-service becomes a ticket with extra steps.

How are you solving that layer today — Workday native, documentation, or people?

Note: The self-service quote is from his CIO.com interview on moving IT closer to the business. He also publicly sponsored #LearnWithRyder and is quoted in LinkedIn's write-up of it, so this isn't a cold subject for him.

CALL / VOICEMAIL · Day 13 · Double tap — voicemail

"Rajeev, [your name] again. One question — across ServiceNow, Workday and the mainframe modernisation work, is adoption measured per system or per program? Emailing now."

EMAIL · Day 13 · Double tap — email (inside 10 minutes of the call)

subject: per system, or per program

The question from the voicemail, in writing.

Eliza's team has driven adoption on ServiceNow, Workday VNDLY, Mural, Asana and the Azure mainframe work. That is a lot of separate change efforts.

Is adoption measured per system, or is there one number your leadership team looks at?

Frank Lopez — EVP & Chief Human Resources Officer

Miami, FL · Economic buyer — one touch, no product word

EMAIL · Day 8 · Video email

subject: 90 seconds, on screen

Frank, made a short video rather than writing a longer email — it shows what guidance sitting inside a Workday process actually looks like to the person doing it, and what it records on the way through.

[video link — e.g. https://www.loom.com/share/...]

If this belongs to someone other than you, tell me who and I will stop.

EMAIL · Day 10 · The anchor, evidence framing

subject: trained, or provably trained

Frank, something I keep running into with large frontline workforces, and Ryder is a pretty clear example.

When a process goes wrong, most orgs ask, "Was the person trained?"

The better question is, "Can you actually show what they were trained on, and when?"

With 40K+ employees and labor relations in your remit, I'd imagine that second question comes up more often at Ryder than at most companies.

Is that something you run into?

Joint / account-level email

Sent to Eliza, Kristen, and Rajeev together, day 15, one thread.

EMAIL · Day 15 · Account email

subject: who owns the evidence

Eliza, Kristen, Rajeev — putting you on one thread rather than guessing.

Ryder has a strong record of driving adoption. What I have not been able to work out from the outside is who owns the proof — the record of what a given employee was shown, in which system, on what date.

Change enablement, L&D, or IT? Twenty minutes with whoever it is.

Loom Link - https://www.loom.com/share/873daf3759bf4b28a065b7a91096ab40

Volume II: territory, tiering and the buying committee

Whatfix — Outbound Capstone, Volume II

Territory model, account tiering, and an expanded buying committee

Companion to the three-account outbound document (Voya Financial, US Foods, Ryder System). Nothing written in that document is changed, removed or re-worded here. The existing 21-business-day sequences are retained in full and become Wave 1 of a longer enterprise motion. Everything in this volume is additive.

1. What the feedback asked for, and what changed

The one thing worth flagging before the numbers

Nine named accounts cannot produce $1M. Even at a 100% win rate, nine accounts at $60k–$100k is $540k–$900k. So the nine named accounts are not the plan — they are the Tier 1 layer that sits on top of a 1,780-account territory. That is the reason the tiering exists, and it is the answer to the obvious panel question: why 1,500–2,000 accounts and nine named accounts in the same document.

2. The number, worked backwards

Target: $1,000,000 in new ARR in twelve months. Everything below is derived from that figure and from three inputs that were given, not assumed: a 5–7% reply rate, a 1,500–2,000 account universe, and a $60k–$100k ACV band.

2.1 The full funnel

Two checks the panel will run

• Blended reply rate lands at 5.9%, inside the 5–7% that was given. It is not flat across the territory — Tier 1 is modelled at 10% because it is hand-researched and multithreaded twelve ways; Tier 3 at 4% because it is templated. A flat 6% across 11,960 contacts would be the less honest version of this model.
• Pipeline coverage is 55 SQOs at $85k blended, or $4.68M against a $1M quota. That is 4.7x. Enterprise new-logo coverage is typically modelled at 3–5x, so this sits at the top of the band rather than being optimistic about it.

2.2 Timing, given a five-month cycle

Enterprise DAP deals involving multiple applications, a security review and procurement run roughly four to six months. At a five-month average, anything expected to close inside the year must be sourced by month seven. That front-loads Tier 1.

Q1 produces no revenue and that is the plan, not a shortfall. If Tier 1 is not fully loaded by the end of month two, the year does not close — that is the single most important dependency in this model.

2.3 The capacity constraint, stated honestly

11,960 contacts over 240 working days is roughly 50 new contacts entered per day. Across the full sequence that is about 47,000 individual touches, or roughly 195 a day: approximately 120 emails through a sequencer, 40 LinkedIn actions, and 35 dials.

The binding constraint is not volume. It is Tier 1 research. 2,160 deeply researched contacts across 48 weeks is 45 contacts a week, or roughly four new Tier 1 accounts a week at twelve personas each. At fifteen minutes of research per contact that is about eleven hours a week of pure research before a single email is written. Tier 2 and Tier 3 exist precisely because that ceiling is real — they are what the remaining hours can actually support.

3. Territory: 1,780 accounts in three tiers

3.1 The firmographic floor

The $60k–$100k ACV band is not the average Whatfix deal. Third-party contract data puts the standard band nearer $32k; $60k–$100k is the multi-application Enterprise tier. That single fact sets the ICP, because it means the target must have several enterprise applications in scope, not one.

• US-headquartered, 5,000+ employees, with the sweet spot at 20,000–150,000.
• Three or more enterprise applications in the estate: Workday, SAP, Oracle, Salesforce, ServiceNow, Epic, Guidewire, Ariba, Blue Yonder.
• An active or recently completed transformation, migration, consolidation or restructure.
• A named change enablement, L&D, HRIS or transformation office function — someone whose job title already contains the problem.
• Bonus multiplier: a large external user population (agents, franchisees, contractors, dealers). External users cannot be put through a training programme, which removes the main alternative to in-app guidance.

3.2 The three tiers

Tiers are defined by trigger proximity, not by company size. A 200,000-person company with no change event is Tier 3. A 15,000-person company two months from an ERP cutover is Tier 1.

3.3 Promotion and demotion rules

Tiering is only worth doing if accounts move. The rules below run weekly and are what turn a static list into a territory.

• Tier 3 → Tier 2 when any fit signal strengthens: a relevant req is posted, an SI partner is named, or an executive in the buying committee changes.
• Tier 2 → Tier 1 when a dated event appears: a go-live is announced, a program is named on an earnings call, or a change-enablement role is opened.
• Any tier → Tier 1 immediately on a positive reply, a referral, or a competitor-displacement signal, regardless of what the account looked like the week before.
• Tier 1 → Tier 2 after 40 business days with no engagement from any of the twelve contacts. The account goes to nurture with its trigger logged as a re-entry condition.
• Hard cap of 180 live Tier 1 accounts. If a new account earns promotion and the tier is full, the coldest one demotes. This is what keeps research quality from degrading as the year fills up.

3.4 Where the nine named accounts sit

Six of the nine are Tier 1 and three are Tier 2. That ratio is deliberate — a list where every account is hot is a list that has not been qualified.

4. The buying committee: four seats to twelve

The original four seats are correct and unchanged. What they miss is that in an enterprise DAP deal the people who kill the deal are rarely the people who want it. Procurement, security and enterprise architecture do not appear in a four-persona map, and they are three of the most common reasons a signed-in-principle deal slips two quarters.

Seats 1–4 open the account. Seats 5–8 build the business case. Seats 9–12 are the ones that stop it closing, and they get worked early precisely so they do not.

Seats 1–4 — unchanged, these open the account

Seats 5–8 — added, these build the business case

Seats 9–12 — added, these decide whether it closes on time

Thirteenth seat, external

On any account with a named SI partner (Deloitte, Accenture, IBM, Infosys), the partner's engagement lead is worked as a coach rather than a buyer. They have no budget and every reason to want the adoption problem solved before it becomes their problem at go-live.

5. Multithreading: eleven channels, sequenced not stacked

Multithreading fails when it looks like volume. Twelve people at one company receiving a similar email in the same week does not read as coverage, it reads as a list purchase. The sequencing below and the rules underneath it are what make the difference.

Rules of engagement

• One channel per contact per day. Maximum two contacts at the same account on the same day.
• No contact is mentioned to another contact before day 15. Before that, every thread has to stand on its own.
• Every persona gets its own wedge. The same email never goes to two people at one account — that is the fastest way to have it forwarded and laughed at.
• The joint account-level thread only fires after at least four individual touches have landed. It is a consolidation move, not an opener.
• A negative reply from anyone pauses the whole account for five business days, and the wedge changes before it restarts.
• 'Not me, talk to X' is a win, not a rejection. Stop every other thread and run X.
• Security and procurement are touched before anyone asks for them. That is the entire point of working them early.

5.5 The proof library — which customer, to which seat

Eight named Whatfix customers with published results. Every figure below is from a public Whatfix case study or press coverage, listed in §

11. Nothing here is estimated, rounded up, or invented — a fabricated metric in a cold email is the one mistake that cannot be recovered from once a prospect checks it.

5.55 Length discipline

Every email and LinkedIn message in this volume sits between 50 and 70 words, averaging 63. That is deliberate and it is checked, not estimated.

• Under 50 words and the proof point has nowhere to sit without the email reading as a one-liner from an automated tool.
• Over 70 and it stops being a message and starts being a pitch. A director scrolling on a phone sees the paragraph count before they read a word, and that is the moment the decision gets made.
• The proof point costs roughly 15 to 20 words. That is a fifth of the email, which is why the rule is one per message. Adding a second means cutting the observation or the question, and both are load-bearing.
• Contractions throughout. Lowercase where the account's voice is lowercase. The test is whether it reads like something a person typed rather than something a team approved.

5.6 Optional proof inserts for Wave 1

Wave 1 is not rewritten. What follows is a single line per email that can be dropped in if wanted, and an explicit list of the emails where proof should not go. The second list matters more than the first.

One caution before inserting anything

Each insert costs 15 to 20 words. If the Wave 1 email is already near 70, the insert has to replace something rather than be added to it — usually the weakest of the middle lines, never the opening observation or the closing question. An email that grows to 90 words to accommodate a customer logo has traded the thing that was working for the thing that sounds impressive.

Where proof should not go, and why

• Voya — Matt Lehmann, Day 1. The email is a pure question built on his user-group role. A customer metric turns a genuine question into a pitch and loses the only thing that email has going for it.
• Ryder — Eliza Fendell, Day 1. The email compliments her numbers and then names a risk. Following her 96% and 95% with somebody else's figures reads as a comparison she did not ask for.
• Ryder — Frank Lopez, Day 10. Risk and evidence framing. A savings metric cheapens a legal question.
• Every security and GRC email in Waves 2 and 3. That seat wants certifications and a deployment model, not customer outcomes.
• Every LinkedIn connection note, on every account, without exception.

5.7 LinkedIn DM copy carrying proof

Connection notes stay product-free. From the DM onward, one proof point is allowed and works harder on LinkedIn than in email, because the reader can check the logo in two clicks.

LINKEDIN DM · L&D or learning technology seat

something i keep asking l&d folks — when a release changes a process, does your team rebuild the course, or patch the job aid and hope people find it?

sentry found a third way. they author across eight apps and cut content creation time by 40%.

no ask here. just trying to get a real picture rather than a vendor one.

LINKEDIN DM · IT service desk seat

do you split 'how do i' from genuinely broken, or does it all land as one number?

renewable energy group split theirs and took 83% off daily app-related tickets, just by solving the first group on the screen.

mostly wondering if that split even exists as data at your scale.

LINKEDIN DM · Application owner or HRIS seat

you're the one rebuilding documentation every release, which is work nobody outside your team ever sees.

semler gruppen put a full successfactors interface change through with no support tickets, because the guidance moved with the release instead of being rebuilt behind it.

is the rebuild still manual at your end, or has something shifted?

6. Tier 1 cadence: 40 business days, three waves

The existing 21-business-day sequence is Wave 1 and is not modified. Wave 2 and Wave 3 extend it to match an enterprise cycle.

Wave 2 and Wave 3 skeleton

7. Wave 2 and 3 applied to the three existing accounts

Names left in brackets are the seats to fill from Sales Navigator. The existing document's credibility comes from every name in it being a real, verified person, so nothing is invented here.

7.0 Creative assets from Wave 1, and where they extend

Four visual assets already exist in the original document. They are reproduced here unchanged, with the Wave 2 and Wave 3 seats where the same asset works a second time. Nothing about their original placement changes.

Asset 1 — the handwritten break-up note

Original placement: Voya Financial, Day 21 break-up. Unchanged.

Original use: the Voya day-21 break-up. Extends to the Wave 3 close on every Tier 1 account — CommonSpirit, Albertsons and Parker Hannifin all end on a day-40 break-up, and this is the format for all three. Written by hand, photographed, attached rather than pasted.

Carry-forward note: the version in the original file is addressed to Jeff while the sequence table lists Matt as the day-21 recipient. That discrepancy is flagged in the original document and is still open.

Asset 2 — 'The system just changed'

Original placement: US Foods, Nicole Hajdrowski, Day 12 LinkedIn. Unchanged.

Original use: the US Foods day-12 LinkedIn touch to Nicole Hajdrowski. Extends directly to the L&D and learning-technology seats on the new accounts — CommonSpirit's Director of Learning & Organisational Development and Albertsons' Director of Retail Training are the same buyer with the same problem. Also works on Ryder seat 6 (LMS administration).

Asset 3 — 'Timing is just wrong?'

Original placement: break-up / nurture touch. Unchanged.

Original use: the timing objection at break-up. Extends to the day-41 nurture entry on every account that demotes from Tier 1 to Tier 2 — it is the asset that makes a re-entry ninety days later feel like a continuation rather than a fresh cold touch.

Asset 4 — 'Completion ≠ Capability'

Original placement: Ryder System, Kristen Frankovich, Day 4 LinkedIn. Unchanged.

Original use: the Ryder day-4 LinkedIn follow-up to Kristen Frankovich. This is the strongest of the four because it states the wedge rather than just making the joke. Extends to Ryder seat 5 (VP Safety & Compliance) and to Cardinal Health's Director of Quality & Compliance Training, where the same distinction is a regulatory one rather than an operational one.

7.1 Voya Financial — seats 5 to 12

EMAIL · Day 24 · Seat 7 — Director, IT Service Desk

subject: the how-do-i split

[name] — most hr case queues have two things in them counted as one number. real exceptions, and people who just can't find the screen.

fifteen workday modules and two releases a year means that second number moves twice a year, whether anyone's watching or not.

renewable energy group split theirs and took 83% off daily app-related tickets.

do you split those two, or is it one figure?

Note: Written to produce a number, not a meeting. A service desk director who answers this has given the AE the business case in one line.

EMAIL · Day 27 · Seat 5 — Director, Enterprise Change Management

subject: the number after go-live

[name] — change management gets measured up to go-live. adoption gets measured six months later, usually by someone else.

with two releases a year, that gap reopens twice a year rather than once per programme.

semler gruppen ran a full successfactors change and generated no support tickets from it.

when leadership asks how adoption's tracking, what do you actually hand them?

EMAIL · Day 36 · Seat 9 — Director, Third-Party Risk / InfoSec GRC

subject: answers before the questionnaire

[name] — sending this before anyone asks, because the questionnaire is usually what slows this category down.

js snippet or an it-managed browser extension. no workday tenant change, no config change. soc 2 type ii, iso 27001 and 27701, hipaa, gdpr. customer data isn't used for model training.

if a review's already open here, worth ten minutes so it isn't run twice?

Note: The only email in the sequence that leads with product detail, and deliberately so. To this seat, the product detail is the value.

7.2 US Foods — seats 5 to 12

EMAIL · Day 23 · Seat 6 — Manager, Procurement Operations

subject: the requisition nobody finishes

[name] — you sit closer to the Ariba requisition flow than anyone on the exec team does.

No ask attached: of the requisitions started in a month, how many get abandoned and become a card purchase or an email to a supplier?

That's usually the honest version of the maverick spend number. OMRON cut expense rejections 25% in Concur by moving the rule onto the screen.

EMAIL · Day 29 · Seat 8 — Senior Director, FP&A

subject: the $75m assumption

[name] — US Foods has told the market it expects $75M+ from indirect procurement this year and $100M+ in 2027.

Those forecasts assume a compliance rate on the new process. Somebody picked that rate.

Bakersfield halved rejected invoices in Oracle ERP without touching the process, just by enforcing it at entry.

Is yours modelled, or is it the number the programme committed to?

Note: The second line is the WDYM line. An FP&A director who knows the answer will reply to correct you, and an FP&A director who does not will reply to find out.

EMAIL · Day 27 · Seat 5 — Director, Organisational Change Management

subject: after the hypercare window

[name] — most OCM plans run to hypercare, then the team gets redeployed to the next programme.

With Ariba just past baseline and Blue Yonder behind it, the first curve is flattening right as your people stand up the second one.

Renewable Energy Group moved enablement into the apps and cut time-to-proficiency by about half.

Who owns that curve once the team's moved on?

7.3 Ryder System — seats 5 to 12

EMAIL · Day 24 · Seat 5 — VP, Safety & Compliance

subject: trained, and provable

[name] — when an incident review asks whether a technician was trained on a procedure, what actually gets produced?

A completion record shows a module was clicked through. It doesn't show what the person was shown inside the system at the moment they did the task.

With labour relations and DOT compliance both in your remit, does that distinction ever come up?

Note: This is the highest-value seat added to Ryder. It converts the existing 'trained versus provably trained' wedge from a productivity argument into a risk argument, which reaches a different budget. Deliberately carries no customer proof point — a savings metric underneath a legal question cheapens it, and this seat is the one place on the account where that trade is not worth making.

EMAIL · Day 27 · Seat 7 — Director, IT Service Desk

subject: the same five tickets

[name] — across ServiceNow, Workday, VNDLY and the Azure work, I'd bet a handful of screens generate most of your ticket volume.

Renewable Energy Group found theirs, fixed them in-app, and took 83% off daily application tickets.

Do you know which five? And is anyone solving them on the screen rather than in the queue?

EMAIL · Day 30 · Seat 6 — Manager, Learning Technology / LMS

subject: what the lms cannot see

[name] — the LMS knows who completed a course. It doesn't know who got stuck in the actual system three weeks later and quietly gave up.

Sentry captures that second half across eight apps, and cut content creation time 40% on the way.

Does that data exist at Ryder, or is completion still the only number?

Note: This is the one Wave 2 email that references another contact by name, and only because Eliza's adoption record is public rather than something learned from her.

8. New accounts — full build

8.1 CommonSpirit Health

Scale: 137 hospitals, approximately 175,000 employees, one of the largest health systems in the United States.

Tier: 1 (BOFU). Modelled ACV: $100,000+ — multi-application across Epic non-clinical workflows, Workday HCM and Finance, and ServiceNow.

Wedge: two simultaneous multi-year platform migrations, and the second one is structured in eight waves.

CommonSpirit is 65% live on Epic with two of eight implementation waves complete, having reduced its EHR portfolio from 19 platforms to 11 under the OneEHR initiative, and is running roughly two years ahead of the original schedule. Running alongside it, a Workday ERP implementation is expected to retire 12 disparate ERP systems and 20 software platforms, with completion targeted for mid-2027 to early fiscal 2028.

The wedge is the wave structure. Eight waves is not one change event, it is eight. If the enablement content is rebuilt per wave, that is a cost that recurs eight times, and nobody costed it that way at business-case stage. Second wedge: a consolidation's savings depend on retiring the legacy systems, and a system is only retired when the last person stops using it.

Buyer map

Sequence — 40 business days

Copy

EMAIL · Day 3 · Seat 2 — Director, Learning & Organisational Development

subject: 137 hospitals, eight waves

[name] — you're building enablement for 175,000 people across 137 hospitals, in waves, on two platforms at once.

the thing i'd want to know in your seat is how much of wave two was genuinely reusable from wave one.

sentry authors across eight apps and cut content creation time 40% by building once instead of per-site.

was yours reusable, or did each site need its own?

EMAIL · Day 6 · Seat 3 — VP, Enterprise Applications

subject: the parallel run

[name] — retiring twelve erps means a long stretch where some sites are on the new system and some aren't.

whatfix is a js snippet or managed extension. no tenant change, no config change, and it can show different guidance to different sites on the same screen. soc 2 type ii, iso 27001, hipaa.

worth fifteen minutes on the deployment model, or shall i send the architecture doc?

Note: Follows the Sudarsan pattern from the original document: arrive with the answer, ask nothing about business outcomes.

EMAIL · Day 10 · Seat 4 — Economic buyer

subject: what gates legacy retirement

[name] — the consolidation case rests on retiring twelve systems. a system is only retired when the last person stops using it.

in most consolidations that tail isn't technical. it's a few thousand people who kept a workaround alive.

renewable energy group cut time-to-proficiency roughly in half, which is the same tail from the other end.

is that tail measured per wave, or found at cutover?

EMAIL · Day 24 · Seat 7 — Director, IT Service Desk

subject: eight go-lives of tickets

[name] — eight epic waves and a workday erp means eight ticket spikes. the spike isn't the problem though. the plateau after is.

of your post-go-live volume, do you know what share is 'how do i' versus something actually broken?

renewable energy group took 83% off daily app tickets once they had that split.

EMAIL · Day 36 · Seat 9 — Director, Information Security

subject: hipaa answers, unasked

[name] — sending the security answer before anyone asks, since it's usually what slows this category down.

js snippet or it-managed extension. no phi captured by default, and it sits outside the epic and workday tenants. soc 2 type ii, iso 27001, 27701, hipaa, gdpr. customer data isn't used for model training.

if a review's already open here, ten minutes so it isn't run twice?

8.2 Albertsons Companies (NYSE: ACI)

Scale: approximately 285,000 employees across roughly 2,200 stores.

Tier: 1 (BOFU). Modelled ACV: $100,000+ — corporate and store-facing applications, very large user population.

Wedge: a structural reorganisation that changes the process under a quarter of a million mostly-frontline, high-turnover people.

Albertsons is executing ACI Edge, a transition from 11 divisions to 4 regions with centralised merchandising. Transition costs are approximately $50M across fiscal 2026 and 2027, against roughly $200M of incremental annual run-rate benefit expected to land mostly in fiscal 2027. Separately, the company has guided to $2.0–2.2B of fiscal 2026 capital expenditure driven substantially by its technology agenda, with four named structural initiatives: digital customer experience, merchandising intelligence, labour optimisation and supply chain optimisation.

The wedge is the gap between the two dates. The cost lands in FY26, the benefit is expected in FY27, and the thing that bridges them is whether roughly 285,000 people work the new way. Second wedge: labour optimisation only produces the saving if store leaders run the generated schedule rather than overriding it, and the override rate is almost never measured.

Buyer map

Sequence — 40 business days

Copy

EMAIL · Day 3 · Seat 2 — Director, Retail Training

subject: 285,000, and turnover

[name] — retail training at your scale has a problem no leadership programme solves. the person doing the task is mid-shift on a store floor and won't go find a course.

then aci edge changes the process, and turnover changes the audience anyway.

sentry does a version of this across eight apps for employees and several hundred external agents.

how does a process change actually reach a store associate today?

EMAIL · Day 6 · Seat 3 — VP, Enterprise Applications

subject: how this deploys

[name] — leading with the part you'd ask about anyway.

js snippet or an it-managed browser extension. no change to the underlying app, no config change, and the same content runs across corporate and store-facing apps. soc 2 type ii, iso 27001 and 27701, gdpr.

worth fifteen minutes on the deployment model, or shall i send the architecture doc?

EMAIL · Day 10 · Seat 4 — Chief Information & Digital Officer

subject: $200m, and who has to change

[name] — aci edge is modelled at roughly $200m of run-rate benefit, mostly in fiscal 2027, against about $50m of transition cost.

the gap between those dates is the adoption window. benefit arrives when people work the new way, not when the structure changes.

sophos measured their version at 342% roi and around 12,000 tickets that stopped being raised.

is adoption tracked as a programme metric, or per system?

Note: Economic buyer, one touch, a number in the subject line. No product word anywhere in the body.

EMAIL · Day 24 · Seat 8 — VP, Labour / Workforce Management

subject: labour optimisation, the last mile

[name] — labour optimisation is one of the four big bets, and the tooling only produces the saving if store leaders run the schedule the way the model intends.

in my experience the model's rarely the problem. the override is.

omron cut improper submissions in concur by putting the rule on the screen at the point of entry.

does anyone measure how often a schedule gets overridden at store level?

Note: This is the sharpest wedge on the account. It names a specific failure mode inside a publicly committed initiative, and the answer is either a number or an admission that there isn't one.

EMAIL · Day 27 · Seat 7 — Director, Store Support

subject: the store support queue

[name] — with the regional restructure and the ai rollouts landing together, i'd expect your queue to be carrying a lot of 'how do i' rather than genuine breaks.

renewable energy group took 83% off daily app-related tickets after solving the first group in-app.

do you split those two, and has it trended down or stayed flat since aci edge started?

9. New accounts — compressed build

Buyer map, sequence skeleton and three anchor emails each. These four are built to the depth that matches their tier; Parker Hannifin is Tier 1 and would be extended to the full twelve-seat map before working it.

9.1 Parker Hannifin (NYSE: PH)

Scale: approximately 61,000 employees, around $19.9B revenue. Tier 1 (BOFU). Modelled ACV: $95,000.

Wedge: divisional autonomy meeting a standard process, in a company that grew by acquisition.

Parker Hannifin selected SAP S/4HANA Cloud and has an implementation underway with IBM supporting it. Separately, there is an open requisition for a Global SAP Supply Chain Transformation Lead whose remit includes developing standard processes across supply chain pillars and supervising a Supply Chain Change Process Team. Historically Parker's aerospace group alone ran six ERP systems and over 180 engineering tools, and the company continues to acquire.

The trigger structure here is identical to the Voya play that already works: an open requisition that puts the change half of a transformation into one person's job description, which means the work exists today and is currently being carried by someone who also has a day job.

EMAIL · Day 3 · Director, Technical Training

subject: divisions, and one process

[name] — parker's model has always rewarded divisional autonomy, and s/4hana asks divisions to run one standard process instead.

so your team has to teach one process to people who've each done it their own way for years.

renewable energy group cut erp and crm time-to-proficiency by about half building it centrally and delivering it in-app.

is yours built centrally and pushed down, or built per division?

EMAIL · Day 6 · VP, Enterprise Applications

subject: clean core, before anything else

[name] — leading with the deployment answer, since it's the first thing you'd ask.

whatfix sits on s/4hana fiori as a js snippet or an it-managed extension. no abap, no clean-core violation, no config change, and it survives the next release. soc 2 type ii, iso 27001 and 27701.

worth fifteen minutes on the model, or shall i send the architecture doc?

Note: 'Clean core' is the phrase that proves you have talked to an SAP estate before. It is the expert observation for this account.

9.2 Duke Energy (NYSE: DUK)

Scale: serves roughly 7–8 million electric customers across seven states, with a large field workforce. Tier 2 (MOFU). Modelled ACV: $75,000.

Wedge: the first wave is done, which sets the price of the second.

Duke deployed the next generation of SAP S/4HANA IS-U while adopting RISE with SAP for its customer information and billing system, completing the transition in just over fifteen months, as part of the broader Customer Connect programme. That is a fast CIS cutover by utility standards.

Two openings. First, a CIS cutover puts contact centre handle time and error rate under pressure for the two quarters that follow, and that recovery curve is rarely forecast. Second, the field estate — enterprise asset management and work management on a tablet in a truck — is a different adoption problem entirely, because there is no colleague to ask and no time to ask them.

EMAIL · Day 3 · Manager, Field Work Management

subject: the tablet in the truck

[name] — a work screen in a truck is a different problem to one on a desk. no colleague to ask, no time, and a job to close out.

sentry runs guidance across eight apps for employees and several hundred external agents, most of them not at a desk either.

when a work order process changes, how does that reach the field — bulletin, toolbox talk, or in the app?

EMAIL · Day 6 · VP, Enterprise Applications

subject: the next wave

[name] — the cis work's done. what i'd want to know in your seat is what the next s/4hana wave costs in enablement, now the first one set an expectation.

whatfix is a js snippet or it-managed extension over fiori. no config change, and the same content serves the desk and the field apps.

worth fifteen minutes on the model, or shall i send the architecture doc?

9.3 Erie Insurance (NASDAQ: ERIE)

Scale: a mid-sized carrier distributing entirely through an independent agency network. Tier 2 (MOFU). Modelled ACV: $70,000.

Wedge: the external agent estate — the closest structural match to Whatfix's own Sentry Insurance reference.

Erie runs Guidewire and continues to hire Guidewire engineers. Guidewire is retiring support for its on-premise versions, which means existing customers face a cloud migration involving change management and technical debt whether or not it was on the roadmap.

The reason this account matters out of proportion to its size: Erie distributes through independent agents. You can ask an independent agent to use a system; you cannot put them through a training programme. That removes the main alternative to in-app guidance and is precisely the shape of the Sentry deployment — eight applications supporting employees, several hundred external agents and customer service representatives, and a large customer base. It is the single most quotable comparable in the Whatfix reference library for this account.

EMAIL · Day 3 · Director, Claims Training

subject: guidewire, and the muscle memory

[name] — a guidewire cloud migration changes screens adjusters have used for years. the system gets better and the first quarter gets slower.

sentry's numbers after theirs were 91% self-help search success and 94% engagement — the dip absorbed in-app rather than in the queue.

is anyone forecasting that dip, or does it get written off as project cost?

EMAIL · Day 6 · VP, Enterprise Applications

subject: on-prem to cloud, the user side

[name] — guidewire is retiring on-prem support, so this migration is happening whether or not it was on the roadmap.

whatfix sits on top of guidewire as a js snippet or an it-managed extension, and the same content serves employees and external agents. no core change.

worth fifteen minutes on the deployment model, or shall i send the architecture doc?

9.4 Cardinal Health (NYSE: CAH)

Scale: approximately 48,000 employees. Tier 2 (MOFU). Modelled ACV: $80,000.

Wedge: regulatory process change, where doing it wrong is a compliance event rather than a productivity one.

Cardinal Health is running a Pharma NDC Transformation Program supporting enterprise blueprinting and regulatory modernisation tied to the FDA's NDC transition, with DSCSA and serialisation already in the environment. Separately, the OptiFreight business is described as being in the final phase of modernising its technology ecosystem, moving from a legacy .

NET and Java microservices landscape to SAP BRIM, Salesforce, Java portal solutions and Google Cloud analytics. The company has also historically consolidated multiple ERP instances onto S/4HANA after growth by acquisition.

Two wedges. First, regulatory: when a field is mis-keyed in a serialisation workflow, that is not a productivity loss, it is an audit finding, and enforcement at the point of entry beats training after the fact. Second, the seam: a user crossing SAP BRIM, Salesforce and a portal to finish one task cannot be helped by guidance that lives inside a single application.

EMAIL · Day 3 · Director, Quality & Compliance Training

subject: trained, and provable

[name] — in a regulated environment, 'was the person trained' and 'can you show what they were shown, and when' are different questions. only one survives an audit.

baltimore resolved 98% of support issues in-app on oracle unifier and cut training time 63%, and the compliance argument there was the same.

does cardinal capture the second one, or is completion still the record?

Note: Same wedge as Ryder, different consequence. At Ryder it is labour relations; here it is the FDA.

EMAIL · Day 6 · VP, Enterprise Applications

subject: brim, salesforce, and the seam

[name] — the optifreight modernisation puts sap brim, salesforce and gcp in one workflow, so a user crosses systems to finish one task.

guidance inside a single app doesn't help at the seam. whatfix runs across applications as a snippet or managed extension, no core change.

cardinal health canada already runs whatfix self-help on the customer ordering portal, so the model isn't new to your organisation.

fifteen minutes?

10 · Assumptions, stated explicitly

10.1 Inputs given, not assumed

• Target of $1,000,000 new ARR in twelve months.
• ACV band of $60,000–$100,000.
• Average reply rate of 5–7%.
• Account universe of 1,500–2,000 per year.

10.2 Assumptions I made, and why

10.3 What still needs verification before sending

• Every bracketed name in sections 7, 8 and 9 is a seat, not a person. These need a Sales Navigator pass. The existing document's credibility rests on every name in it being real and verified, and nothing here breaks that rule by inventing one.
• Employee counts and programme dates are drawn from public filings, earnings calls and press coverage as listed in §11. Anything more than two quarters old should be re-checked before it appears in an email — a stale number in a cold email costs more than no number.
• Whatfix pricing figures are third-party contract data, not official Whatfix quotes. They are used here to set the firmographic floor for the ICP, not to quote a customer.
• Cardinal Health Canada's status as a live Whatfix customer must be confirmed with the account team before any outreach. A published case study is evidence of a past deployment, not proof of a current contract, and referencing a lapsed relationship as a live one is worse than not referencing it at all.
• Every metric in the proof library (§5.5) should be re-checked against the current Whatfix case study page before it goes into a send. Published figures get restated and occasionally withdrawn, and a number a prospect cannot find is worse than no number.
• The Pam Federick / Pam Rodgers name discrepancy and the Jeff-versus-Matt addressing in the day-21 break-up image are both already flagged in the original document and are carried forward here unresolved.

11 · Sources

Whatfix contract value and pricing tiers: Vendr third-party contract data as reported by Userpilot (userpilot.com/blog/whatfix-pricing), Guidde and Tandem, August 2026.

Forrester digital adoption loss estimate and Sentry Insurance deployment scope: whatfix.com/digital-adoption/, May 2026.

SAP ECC end-of-maintenance and S/4HANA migration state: ASUG and Precisely, Transforming SAP Processes Through Automation — 2026 Trends and Challenges; SAPinsider ERP Migration and Transformation 2026 Benchmark.

CommonSpirit Health — Epic OneEHR wave progress, EHR portfolio reduction, and Workday ERP scope and timeline: Becker's Hospital Review, 8 June 2026; investor call remarks of 29 May 2026.

Albertsons — ACI Edge division-to-region restructure, transition cost, run-rate benefit, capital expenditure and the four structural initiatives: Q1 FY2026 earnings call transcript, 23 July 2026; Q4 FY2026 earnings call transcript, April 2026; CIO Dive, 16 April 2026.

Parker Hannifin — SAP S/4HANA Cloud selection and IBM implementation support: Apps Run The World customer database, February 2026. Global SAP Supply Chain Transformation Lead requisition: Parker Hannifin careers listing.

Duke Energy — S/4HANA IS-U on RISE with SAP, fifteen-month transition, Customer Connect programme: ASUG SAP Utility Excellence Award coverage; SAPinsider case study, June 2026.

Erie Insurance — Guidewire claims platform selection and ongoing Guidewire engineering hiring: Guidewire investor relations; Erie Insurance careers listing. Guidewire on-premise support retirement: ISG Provider Lens, Guidewire Services Ecosystem, 2025.

Whatfix customer proof points — Sentry Insurance, Renewable Energy Group, Sophos, Old Mutual, City of Baltimore, City of Bakersfield and OMRON: Whatfix published case studies as aggregated by Cuspera (cuspera.com) and whatfix.com/digital-adoption/, 2026; Whatfix digital transformation case study collection, January 2026.

Semler Gruppen SAP SuccessFactors rollout: Whatfix company post as reported by TipRanks, 1 July 2026.

Cardinal Health Canada as a Whatfix customer: whatfix.com/resources/case-studies/, accessed 2026.

Cardinal Health — Pharma NDC Transformation Program and DSCSA scope; OptiFreight modernisation to SAP BRIM, Salesforce and GCP; historical multi-ERP consolidation onto S/4HANA: Cardinal Health careers listings, July 2026; Google Cloud customer blog.

The GTM motion strategy

No budget line,

so it has to be sold.

The full menu of go-to-market motions available to Whatfix, scored against this company at this stage — the case for outbound as the primary wedge, the motion missing from the menu, and how the rest layer in over twelve months.

Company figures are drawn from Whatfix press releases, Series E coverage in Bloomberg and Economic Times, published analyst recognitions and the company's own site, each labelled by confidence. Where I have extrapolated — notably current ARR — I say so. Nothing here is internal data, which is the honest limit of a strategy written from outside.

01 · The starting position

H1Six facts that constrain the answer before I make it

Motion selection is not a preference. It falls out of where the company is, what the category is, and who the buyer is. Six things about Whatfix in August 2026 do most of the deciding.

ARR was around $75M at the Series E with the CEO stating $100M was a couple of quarters away. Two years on, a reasonable outside estimate is meaningfully past $100M, but I have no current figure and will not invent one. Every allocation in Section 07 is expressed as a proportion for that reason.

02 · The full menu

H1Eight motions, scored honestly against this company

Scored 1 to 5 on four dimensions: how well the motion fits a category with latent demand, how fast it produces pipeline, how efficiently it scales, and how defensible it is against SAP putting WalkMe into every S/4HANA conversation. The point of scoring is to make the trade-offs visible, not to pretend it is arithmetic.

Why product-led is the wrong answer, specifically

PLG is the fashionable answer and it is wrong for this product, for three structural reasons rather than one philosophical one.

• The buyer is not the user. The person who benefits from a Flow is an employee in Workday; the person who signs is a CIO, a VP of L&D or a transformation lead. Self-serve adoption by the beneficiary never reaches the signer.
• It cannot be installed without IT. Deployment is a JavaScript embed or an IT-managed browser extension pushed by Group Policy or Jamf. There is no credit-card path into a Fortune 500 tenant, and there should not be.
• The value only appears at scale. A single Flow in a trial proves nothing. The ROI claim is portfolio-wide — ticket deflection, content rebuild cost, time-to-proficiency across many applications — and none of it is visible in a fourteen-day sandbox.

There is one exception worth building: Mirror. A simulation product is demonstrable in a way a guidance overlay is not, and a guided self-serve trial of Mirror is the closest thing to a genuine PLG surface Whatfix has. I would treat it as a lead-generation experiment in month nine, not as a motion.

03 · The call

H1Why outbound is the right primary wedge

Five arguments, in the order I would defend them.

One · Latent demand cannot be captured, only created

Inbound works when someone is already searching. The whole premise of digital adoption is that the buyer does not know the problem has a category — they think they have a training problem, or a support-ticket problem, or a change-management problem, and they have already budgeted for those separately. A CIO whose ERP rollout is underperforming is searching for consultants, not for a DAP. Outbound is the only motion that reaches that person before they have named their own problem, and naming it for them is most of the sale.

Two · The buying committee does not know it is one

The pain is distributed across four people who rarely meet: L&D feels content rebuild cost, IT feels ticket volume, the CIO feels unrealised ROI on a platform investment, and the process owner feels the errors. No single one of them owns the problem, which is exactly why it persists. Only a multithreaded outbound motion can assemble that committee, because it is the only motion that talks to four people at once about four different symptoms of one cause.

Three · The triggers are unusually observable

This matters more than it sounds, because outbound only scales when the "why now" is findable. Whatfix's buying triggers are dated, public and repeatable.

Four · The WalkMe window is open and it will close

SAP will do the obvious thing: bundle WalkMe into SAP deals and prioritise the SAP roadmap. That is good for WalkMe inside SAP estates and bad for WalkMe everywhere else, and the customers who feel it are Workday, Oracle and Salesforce-primary enterprises now sitting on a multi-year contract with a vendor whose incentives just changed. That is a finite, nameable list working through renewals over roughly the next two years. You cannot content-market your way onto it. You build the list and you work it.

Five · Pre-IPO demands forecastability

This is the argument a GTM head makes and a demand-gen lead often does not. Approaching an IPO, the quality of pipeline matters as much as the quantity: attributable, repeatable, and controllable quarter to quarter. Outbound is the only motion where I can change the input on Monday and see the output move. Inbound, community and partnerships are all lagging systems with six-to-eighteen-month latencies — excellent to own, impossible to steer inside a quarter.

Outbound is not the best motion in the abstract. It is the correct primary wedge for a category with no budget line, a committee that does not self-identify, dated public triggers, a competitor in transition, and a company that needs its numbers to be predictable. Change any one of those and I would answer differently.

Where outbound is genuinely weak, stated plainly

• It is the most expensive pipeline per dollar on the list, and it stays expensive — it does not compound the way content does.
• It does not build the category. Every outbound conversation pays the full cost of explaining what a DAP is, because nobody else has explained it first.
• It does not defend against distribution. SAP does not have to out-sell Whatfix; it can out-distribute it. Only partnerships answer that.
• It is people-limited. Scaling outbound means hiring, ramping and managing, and ramp time is a hard floor on growth.

Which is precisely why outbound is the wedge and not the strategy. The sequence in Section 06 exists to fix all four of those weaknesses with the motions that layer in behind it.

04 · What outbound must not be

H1The failure mode, and the shape that avoids it

The way this decision goes wrong is not choosing outbound. It is choosing outbound and then building the wrong kind — high-volume, contact-based, sequence-per-persona, measured in dials. At Fortune 1000 ACVs that motion produces meetings that do not convert and burns the domain reputation that every other motion depends on.

This is why ABM does not appear as a separate motion in my sequencing. At this ACV, ABM is not something you layer on top of outbound — it is what outbound has to be from day one. Running them as two programmes produces two teams writing to the same person.

05 · The motion missing from the menu

H1Installed-base expansion, and why I would fund it first

The standard menu — outbound, inbound, product-led, partnerships, events, referrals — describes ways to acquire logos. For a DAP it omits the motion with the best economics in the entire business, because that motion is not acquisition. It is the second, third and eighth application inside a customer you already won.

The strategic point: every enterprise Whatfix sells has an internal estate and a customer-facing estate, and the first deal almost always lands in one application inside one of them. The second deal has no security review, no procurement cycle, no category education and a live reference sitting in the same building. It is the cheapest revenue in the company and it is usually owned by whoever has time.

If I had one hire and had to choose between another outbound SDR and an expansion-focused role working the installed base against a mapped application inventory, I would take the second and expect to be right. Outbound is the wedge because it is how you get in. Expansion is how the company actually gets to the next number.

06 · The sequence

H1Twelve months, four phases

Each phase adds a motion that repairs a specific weakness in the one before it. Nothing is added because it is best practice.

The sequencing logic in one paragraph

Outbound first because it is the only motion that pays this quarter and the only one that reaches a buyer who has not named their problem. Expansion alongside it because it is the same quarter and cheaper. Partnerships next because they take three quarters to produce and they are the only structural answer to SAP owning distribution — starting them in month nine means benefiting in month eighteen, which is too late. Content after outbound rather than before, because outbound tells you what to write. Community and events last, because they need a body of work to convene around.

07 · Where the money goes

H1Proportions rather than numbers

I have no visibility into Whatfix's actual GTM budget, so this is expressed as a share of pipeline-generating spend and headcount, and as a direction of travel rather than a plan.

08 · How I would know I am wrong

H1

A strategy without falsification criteria is an opinion. Here is what would tell me to change the answer, and what I would change it to.

Assumptions this rests on

• That the DAP category still has no dedicated budget line at most enterprises. If procurement has started treating it as a standard category, the inbound argument strengthens considerably.
• That current ARR is meaningfully past $100M and the IPO window is roughly live. Both are outside inference from 2024 statements.
• That net revenue retention has room to improve. I cannot see it, and if it is already excellent, Section 05 is redundant.
• That the WalkMe installed base at non-SAP accounts is large enough to justify a named displacement programme. I would size this properly in week one rather than assume it.
• That US and Western Europe behave similarly enough to run one motion mix. They may not — Europe is more SI-led and may want partnerships earlier than month three.

What I would ask in week one

• Current pipeline mix by source, and win rate and cycle length by source. This single table would confirm or destroy most of the argument above.
• Net revenue retention, and how much of last year's new ARR came from existing logos.
• Whether expansion has an owner and a target, or whether it is absorbed into account management.
• The size and renewal timing of the WalkMe base at Workday, Oracle and Salesforce-primary accounts.
• What partner-sourced revenue looks like today, and what the Icertis relationship actually produced — because it is the proof point for the entire partnerships thesis.
• Which verticals close fastest, because that should override my trigger ranking if the data disagrees.

The part of this I would most want challenged: I have ranked partnerships third by urgency and second by strategic importance, which is an uncomfortable place for anything to sit. If SAP moves faster than I expect at putting WalkMe in front of every enterprise it already sells to, then partnerships stops being a month 3–6 build and becomes the thing that should have started before outbound. That is the single judgement in this document I would most want to be argued out of.