Dear SaaStr: Why is Marc Benioff Complaining About Worker Productivity?

Dear SaaStr: Marc Benioff (Salesforce CEO) keeps popping up in headlines for grumbling about “productivity.” Is this just another remote-work rant… or is something else going on?

Signed,
A Founder Who Would Like Their Team to Be Productive and Not Miserable

The short answer: he said the quiet part out loud

If you’re a SaaS operator, you’ve probably felt this vibe at least once since 2022: growth slowed, budgets tightened, and suddenly every extra headcount
feels like a line item with a pulse.

Benioff’s “productivity” complaints landed because they weren’t abstract. The gist was: performance isn’t where it used to be, and a chunk of newer hires
(many hired during the pandemic surge) aren’t producing like the pre-2020 baseline.

That’s the headline. The real story is a mix of (1) post-pandemic overhiring, (2) uneven onboarding and coaching, (3) selling getting harder, and (4) the
age-old problem of measuring knowledge work without turning your company into a hall monitor with a spreadsheet addiction.

What exactly was he reacting to?

Around late 2022 into early 2023, Salesforcelike a lot of techwas staring at the end of the “everything goes up” era. Salesforce announced major layoffs,
and leadership messaging sharpened around efficiency, performance, and doing more with less.

In that environment, “productivity” becomes the CEO’s all-purpose flashlight: you shine it into orgs, teams, and roles to find what’s working, what’s
bloated, and what’s quietly broken. Sometimes the flashlight also becomes a megaphone. That’s where the controversy tends to start.

Why the productivity conversation explodes in SaaS (especially after 2020)

1) The 2020–2022 hiring sugar rush (and the crash afterward)

Here’s the part that’s painfully relatable: many companies dramatically increased hiring from mid-2020 through early 2022. In plenty of cases, the hiring bar
slipped (because hiring fast becomes the goal), and comp jumped (because that’s what happens when every company tries to hire the same “top 10%” at once).

Then 2023 arrived like a cold shower. Growth didn’t vanish, but it normalized. And suddenly, it felt like the org had 50% more people than the plan actually
requiredoften at higher cost per employee.

When that happens, leaders don’t talk about “vibes.” They talk about “productivity.” Because “we overhired” is honest, but “we need higher productivity” is
a way to push change without admitting you bought too much headcount on margin.

2) Sales got harder, and that makes “productivity” look worse than it is

In SaaS, revenue doesn’t care how many standups you held. Sales productivity shows up in a few brutal numbers: pipeline coverage, win rate, cycle length,
quota attainment, retention, and expansion.

When the macro environment gets tougher, the bottom half of the sales org tends to show it first. Newer AEs often struggle most because they don’t have the
same internal networks, product intuition, or “I’ve seen this deal movie before” instincts that tenured reps rely on.

So you end up with a dynamic that looks like a productivity crisis: the top performers keep carrying results, while newer hires stall.
That might be “performance,” not “effort.” But CEOs often label the whole thing “productivity” because it’s the umbrella term everyone recognizes.

3) Remote and hybrid work didn’t create the issuebut it changed the failure modes

The biggest myth is that remote work automatically means lower productivity. Research and real-world experiments often show that well-designed hybrid can
preserve performance while improving retention and satisfaction.

The more realistic problem is this: remote work makes weak management more visible, and weak onboarding more expensive.
If a manager relied on “walk-by coaching,” osmosis learning, or informal peer pressure, those tools don’t work the same way on Zoom.
You need explicit systemsclear goals, feedback loops, documentation, coaching time, and measurable outcomes.

In other words: remote work doesn’t magically make people lazy. It punishes companies that never built operating discipline in the first place.

4) Knowledge work productivity is notoriously hard to measure

For many roles in SaaSproduct, engineering, marketing, partnershipsinputs and outputs aren’t as neatly measurable as “units produced.”
And when outputs are fuzzy, leaders fall back on proxies: online time, messages sent, meetings attended, tickets closed, dashboards updated.

But proxies can be deceptive. You can “look productive” while doing the wrong work. You can also do highly valuable work that looks quiet: deep thinking,
fixing a subtle reliability issue, rewriting positioning, or removing a workflow bottleneck that saves 200 hours next quarter.

That’s why “productivity” debates tend to feel like two people arguing over the best pizza topping… while standing in different restaurants.

5) Post-pandemic organizations have coordination tax (hello, meeting bloat)

Hybrid can be great, but it introduces coordination complexity: which days are “together” days, which work is async, how decisions get made, and how new
hires learn what “good” looks like.

If your company solves that by adding meetings, you get the modern SaaS nightmare: calendars packed, Slack buzzing, and nobody has time for the work that
actually moves the customer needle.

When leaders see that, they call it “low productivity.” Employees call it “my calendar is eating my job.”
Both are correct. Neither is helpful without a fix.

So… is Benioff blaming workers, or diagnosing a business reality?

A little of both, probably. CEOs are humans. Humans get frustrated. And “why isn’t this team performing?” is a normal question when budgets tighten.

But for SaaS operators, the more useful lens is: productivity messaging is often a symptom of a company transitioning from “grow at all costs” to
“grow efficiently.” When that transition happens, what used to be tolerated becomes a target:

• Underperforming reps with long ramp times
• Teams that expanded faster than revenue did
• Managers without coaching cadence
• Unclear goals and too many priorities
• Remote/hybrid policies that exist, but aren’t operationalized

If you’re a founder, don’t copy the complaintcopy the operating improvements

1) Define productivity by outcomes, not activity

Want a productivity upgrade that doesn’t require surveillance software? Define outcomes that matter per role and make them visible.
Examples (adjust for your stage and motion):

• Sales: quota attainment, pipeline coverage, stage conversion, forecast accuracy, renewal/expansion contribution
• SDRs: qualified meetings that progress, not just meetings booked
• Customer success: retention, expansion, health score movement, time-to-value
• Support: time to resolution, deflection with satisfaction intact, CSAT, reopened rate
• Engineering: cycle time, reliability, incident rate, customer-impacting delivery, quality metrics
• Marketing: pipeline influenced, CAC payback trends, conversion rates, not “we posted a lot”

2) Treat onboarding like a revenue system, not a welcome email

If newer hires are underperforming, assume the system is guilty until proven innocent. Great onboarding is not “Day 1 swag.”
It’s a 30/60/90 plan, role-based enablement, shadowing, weekly coaching, and clear definitions of “ramped.”

In hybrid environments, new hires need extra structure: office days that are designed for coaching, and remote days designed for focus.
Otherwise you get the worst combo: isolated learning plus constant meetings.

3) Make hybrid purposeful (not random)

Hybrid works best when office time has a job: coaching, deal reviews, pairing sessions, whiteboarding, customer workshops, team bonding, and fast decisions.
Remote time has a job too: deep work, execution, writing, building.

“Come in three days a week because… vibes” is rarely motivating. “Come in Tuesday–Thursday because we coach, review deals, and build together” is a plan.

4) Fix performance issues fastand with respect

If someone’s not performing, dragging it out doesn’t help them or the team. But “performance management” doesn’t have to mean public shaming or broad
statements that accidentally insult high performers.

Do this instead:

• Set clear expectations
• Give specific feedback tied to outcomes
• Offer coaching and resources
• Time-box improvement plans
• Make fair decisions quickly

5) Cut meeting bloat like it’s a cost center (because it is)

Every recurring meeting should have a purpose, an owner, a decision type (inform, decide, brainstorm), and a default length.
If the meeting doesn’t produce decisions or remove blockers, it’s entertainmentand your company is not Netflix.

The Salesforce twist: “RTO doesn’t work” and “productivity is down” can both be true

Benioff has, at different times, pushed back on rigid return-to-office mandates and also emphasized performance concerns tied to newer employees and
in-office collaboration for some roles.

That sounds contradictory until you separate policy from execution:

• Policy: Flexible work can be a competitive advantage for hiring and retention.
• Execution: If onboarding, coaching, and goals are weak, productivity problems show upespecially for new hires.

In practice, many companies are converging on a pragmatic middle: hybrid policies plus tighter performance expectations plus better instrumentation around
outcomes. The workplace debate is loud, but the operational fixes are usually quiet.

Seven takeaways for SaaS leaders (without becoming the Productivity Police)

1. Assume you hired too fast in 2020–2022 and audit roles against today’s revenue reality.
2. Diagnose by cohort: tenured vs. new hires often have different blockers.
3. Measure outputs (customer and revenue outcomes), not “online vibes.”
4. Rebuild onboarding and coaching like they are mission-critical systems.
5. Make hybrid purposeful: office time for collaboration, remote time for execution.
6. Reduce meeting load so real work can happen.
7. Be candid, but precise: broad productivity complaints can demoralize your best people.

Experience notes: what “productivity problems” look like in real SaaS teams

Below are a few composite, real-world patterns SaaS operators commonly describe when they say “productivity is down.” None of these are about people being
inherently unmotivated; they’re about systems that quietly stopped working as the world changed.

Story #1: The new AE who “works hard” but can’t close

The AE is busy all daycalls, follow-ups, Slack, internal questionsyet pipeline doesn’t progress. The root cause is usually not effort. It’s enablement and
deal quality. When selling gets harder, “activity” isn’t a substitute for good pipeline. The fix often looks like: tighter ICP enforcement, better discovery
coaching, win/loss reviews, and pairing newer reps with top performers for deal strategy. In other words, make the reps better and the leads better.
“More hustle” is not a strategy.

Story #2: The engineering team with a full sprint… and nothing ships

This is the classic “everything is in progress” problem. Work is fragmented, priorities shift, and nobody has uninterrupted time. The team looks busy in Jira
but customers don’t feel progress. The fix is boring but powerful: fewer priorities, smaller work items, explicit decision owners, and a culture of finishing.
Many teams also benefit from a meeting dietreplacing status meetings with written updates and reserving live time for decisions and debugging.

Story #3: The hybrid schedule that accidentally becomes “always on”

The team has flexible work… but no shared rules. Some people come in Monday, some Thursday, and collaboration happens across time zones and calendar chaos.
The result is constant pings and “just a quick call” requests. Productivity dips because everyone is context-switching. Teams that recover usually pick
“together days” for high-collaboration work (planning, coaching, design reviews) and protect deep-work blocks on remote days. The office stops being a
surveillance symbol and becomes a collaboration tool.

Story #4: The manager who used to coach by proximity

Before 2020, coaching happened naturally: overheard calls, hallway questions, quick desk check-ins. In a remote/hybrid world, that “ambient coaching”
disappears. Some managers replace it with more meetings, which makes everything worse. The better fix is intentional coaching: scheduled 1:1s, structured
feedback, shadowing sessions, and clear expectations. The manager’s job becomes less “watch” and more “teach.” When that shift happens, productivity rises
without anyone feeling policed.

Story #5: The company that confuses speed with thrash

Leaders want faster execution, so they add urgency. Urgency turns into re-prioritization. Re-prioritization turns into half-finished work. Half-finished work
turns into low morale. The company concludes: “People aren’t productive.” The actual fix is clarity: fewer top priorities, stable roadmaps for long enough to
ship, and decision discipline. Speed comes from focus, not from yelling “faster” into the void.

Story #6: The AI era productivity comparison trap

As AI tools improve, leadership expectations often jump: “If an agent can draft this in 30 seconds, why did it take you two days?” Sometimes that’s fair.
Sometimes it ignores the human parts: judgment, nuance, customer context, compliance, and integration. The best teams set a new standard: AI handles the
repetitive parts, humans handle the decisions, and productivity means “more customer impact per hour,” not “never take a breath again.”

Conclusion

Benioff’s productivity complaints aren’t just a CEO mood swingthey’re a signal of a broader shift in SaaS: the industry moved from “growth at all costs” to
“efficient growth,” and that transition forces companies to rebuild hiring standards, onboarding, coaching, measurement, and meeting culture.

If you take one lesson from the whole debate, make it this: don’t argue about productivity in the abstract. Define outcomes, fix systems, coach people, and
make hybrid work purposeful. You’ll get higher performance and you won’t have to become the boss who thinks “productivity” is spelled
M-I-C-R-O-M-A-N-A-G-E.