SaaS prices are rising 4x faster than inflation. So if you’re not negotiating, you’re watching your costs climb year after year as auto-renewals lock in those increases.
This guide gives you the step-by-step tactics for securing multi-year price locks, escalation caps, and 15-30% discounts on your SaaS contracts.
Price escalation caps, auto-renewal clauses, service level agreements, exit clauses, and payment terms. That’s your list. Get those right and you’ll avoid the worst of vendor lock-in and runaway costs.
Price escalation caps stop vendors from hitting you with 7-10% uplifts at renewal or worse—resetting your pricing to current list rates. That discount you negotiated last year? It vanishes without a cap.
Your contract should spell it out: “Annual price increases shall not exceed 3-5% or the percentage increase in the Consumer Price Index, whichever is lower.”
Auto-renewal clauses are vendor lock-in tools. Vendors often comply with requests to remove them during negotiations, but only if you ask. The standard 30-day notice window isn’t enough. Push for 90-120 days.
Service level agreements need to include uptime expectations, response times, and what happens when things go wrong. If the vendor misses their SLA, what do you get? Fee reductions? Service credits? Right to terminate? Get specific numbers in writing.
Exit clauses determine how painful it will be to leave when the time comes. Data portability provisions should specify standardised formats that minimise downtime when you’re moving your data elsewhere.
Payment terms affect cash flow. Annual payments typically secure 10-15% discounts compared to monthly billing. You can also negotiate Net 60 or Net 90 terms instead of the standard Net 30.
Multi-year contracts usually get you 15-25% discounts compared to annual agreements. You’re locking in current pricing before vendors implement next year’s price increases. The trade-off? Reduced flexibility if your business needs change. The sweet spot is 2-3 year commitments with escalation caps—not 5+ year locks.
A 1-year contract is your baseline. A 2-year commitment gets you 10-15% off. A 3-year commitment pushes that to 15-25%. Five-year deals might offer 20-30%, but that locks you in for too long.
Here’s why this matters: SaaS inflation is running at 11.4% year-over-year compared to 2.7% general inflation. By locking in today’s pricing, you’re protecting yourself against those increases. For a comprehensive look at why SaaS prices are rising and the broader market forces driving this trend, see our full analysis.
Thing is, vendors are dialling back multi-year discount incentives, so you’ll need to push harder and insist on escalation caps as part of the deal.
Also worth doing: include performance review clauses in your multi-year contracts. These let you renegotiate if service quality tanks, the vendor gets acquired, or there’s a major change of control.
Usage data, competitive alternatives, timing, and multi-year commitment offers. That’s your leverage.
Usage data is your most effective weapon. If you can show that 45.7% of your licences go unused—and that’s the average across all companies—you’ve got an immediate argument for right-sizing your contract. Pull login data and identify seats unused for 90+ days.
Competitive alternatives work even if you have no intention to switch. When AWS sees Azure offered aggressive incentives, it often sharpens their pencil. Get actual quotes from 2-3 alternatives. Then tell them: “We prefer AWS, but our board is considering all options.” That creates real leverage.
Understanding what Salesforce and Microsoft are doing with their pricing strategies helps you anticipate vendor-specific tactics and prepare your counter-arguments.
Quarter-end timing is tactical. The last two weeks of a quarter are when sales teams are most motivated to close deals and hit their targets.
Multi-year commitment offers revenue certainty that vendors value. Use this: “We’re prepared to commit for three years if you lock our pricing and cap increases at 3% annually.”
Benchmark using SaaS management platforms, request competitive quotes, analyse cost per active user, and check for shelfware that’s killing your value per dollar spent.
Average SaaS price increases run 8-12% annually, with aggressive movers at 15-25%. If your increases are higher, you’re likely overpaying.
Cost-per-active-user is the metric that matters. Divide your total contract value by monthly active users, not provisioned licences. If you’re paying for 100 seats but only 55 people logged in last month, your real cost per user is nearly double what you think it is.
CloudEagle provides vendor price benchmarking by comparing data from similar companies in your industry. Or just request quotes from 2-3 alternative vendors yourself and see how they stack up.
Watch for hidden fees while you’re at it. Implementation charges, premium support, API overages, data storage, integration fees, and training charges all add up fast. Vendors use AI bundling and credit multipliers to mask price hikes—a service that used to cost 10 credits can jump to 20 credits overnight, and they call it a “feature enhancement.”
Here’s a telling stat: 55% of vendors lack transparent pricing, which means there’s plenty of room to negotiate.
A price escalation cap limits annual price increases to a fixed percentage—typically 3-5%. You negotiate caps as part of multi-year agreements to protect yourself against unlimited increases. Tie caps to recognised inflation indices like CPI rather than leaving it to vendor discretion. Without caps, vendors can increase prices 20-30% annually and there’s nothing you can do about it.
3% is aggressive but achievable. 5% is reasonable. CPI-linked caps protect against inflation. No cap at all? That’s risky.
Locking down renewal terms is just as important as negotiating the upfront price. Do it at the initial deal or push for caps when renewal time comes around.
Your contract should state something like: “Annual price increases shall not exceed 5% or the percentage increase in the Consumer Price Index, whichever is lower.” Make sure it applies to all fees—base subscription, support, and add-ons.
Avoid vague wording like “mutually agreed pricing” or “prevailing rates at renewal.” That’s just code for “we’ll charge whatever we want.”
Price holds are even better than caps. The price doesn’t go up at all: “The renewal price per user will remain $100” or “All current discount percentages will apply to renewal.”
Negotiate exit clauses with reasonable notice periods, ensure data portability rights, avoid contracts longer than 3 years unless the business case is rock solid, and include performance review clauses that let you renegotiate if service degrades.
Exit clauses need to cover notice periods, termination fees, and pro-rata refund terms. Push to eliminate termination fees entirely. If the vendor insists on them, negotiate them down below 25% of remaining contract value.
Data portability is critical. Many SaaS platforms store data in proprietary formats not easily exportable, which makes leaving painful. Your contract needs to specify export rights in standardised formats, clear timelines for getting your data out, and migration assistance from the vendor.
Contract length matters more than most people realise. One-year contracts give you flexibility. Two to three years balance savings with flexibility. Five-plus years is risky—too much can change in that time.
Performance escape hatches let you exit if things change. Include clauses for material breach of contract, SLA violations, and vendor acquisition scenarios where control changes hands.
Begin renegotiations 90-120 days before renewal date to avoid auto-renewal traps. Align with vendor fiscal quarter-ends—the last 2 weeks of the quarter—for maximum leverage. Start competitive research 6 months before renewal to build credible alternatives. Never wait until the auto-renewal notice deadline.
83% of successful renewal negotiations start at least 120 days before renewal. That’s your window.
Here’s how to structure it:
6 months out: Start your research. Identify which contracts are coming up for renewal and what alternatives exist.
4 months out: Obtain competitive quotes from 2-3 alternative vendors to establish what market pricing looks like.
3 months out: Begin negotiations with your current vendor. Present your research, usage data, and competitive alternatives.
120 days out: This is your deadline to avoid auto-renewal traps that lock you in.
1 month before renewal: Have everything signed and put to bed.
Also worth knowing: AWS’s fiscal year-end and quarter-ends make reps more flexible as they’re trying to hit targets. Microsoft’s fiscal year ends June 30. The last two weeks of any quarter are when sales teams are most motivated to close deals.
Audit active users monthly to identify unused licences, calculate cost-per-active-user to demonstrate overprovisioning, present usage analytics showing feature adoption to negotiate tiered pricing, and document usage trends to forecast accurate future needs for multi-year commitments.
45.7% of all SaaS licences go unused. If you’re average, nearly half your SaaS spend is waste.
Track usage through built-in vendor analytics, SSO login data, or SaaS management platforms. Look at active versus provisioned users and last login dates for each seat.
Identify shelfware by finding seats unused for 90+ days. Inventory every software tool tracking actual usage against purchased licences and you’ll find the waste quickly.
Right-size your contract based on what you find. If you’re paying for 100 seats but only 60 are active, negotiate down to 70 seats. Show the vendor the login analytics—hard data beats hand-waving.
Calculate cost-per-active-user by dividing total contract cost by monthly active users, not provisioned licences. Use this metric for vendor comparisons and to demonstrate where you’re getting poor value.
Quarterly true-up clauses let you adjust licence counts quarterly based on actual usage, which is much better than being locked into an annual count.
What are the price increase limits for renewals? What is the auto-renewal notice period and can we extend it to 90 days? What are the SLA guarantees and financial remedies for breaches? What are the data export and termination terms? Are there volume discounts for multi-year commitments?
Pricing: What are the escalation caps? Multi-year discounts? Volume tiers? Payment terms? Hidden fees that’ll show up later?
Contract terms: Auto-renewal window—can we extend it to 90 days or more? Termination clauses and notice periods?
Service levels: What uptime do you guarantee? Support response times? Financial remedies for SLA breaches—actual penalties, not just hand-waving?
Security: Where does our data physically reside? What certifications do you have—SOC 2, ISO 27001, GDPR, CCPA? Do we have audit rights?
Integration: What API access and rate limits apply? Data export capabilities and what formats can we get our data in?
Negotiability: Which terms are negotiable versus standard boilerplate? This often reveals how much vendor flexibility exists.
Poorly structured agreements lead to cost overruns and vendor lock-ins that take years to unwind.
Yes, mid-contract renegotiations are possible during vendor price increase announcements, when you’re adding significant new users, or if service quality degrades. Material changes to service terms may also trigger renegotiation rights. Document all issues and approach the vendor with a data-driven business case for changes.
Waiting until the auto-renewal deadline removes all your leverage. Accepting the first offer without a counter-proposal wastes opportunity. Failing to research competitive alternatives leaves you blind to market pricing. Not using usage data means you’re overpaying. Agreeing to contracts without escalation caps exposes you to unlimited price increases down the track.
Focus on data-driven arguments rather than threats. Acknowledge vendor value while presenting competitive research as market context. Frame negotiations as seeking fair market pricing, not exploiting the vendor. Microsoft expects large enterprise clients to negotiate hard—it’s standard practice in their world. Involve procurement or finance rather than making it personal with your account manager.
For 10+ SaaS contracts or contracts exceeding £100K annually, procurement platforms like Vendr, Vertice, or Tropic provide benchmarking data and expertise worth their 10-20% fees. CloudEagle’s negotiation experts work as extension of procurement team and bring vendor relationship intelligence you don’t have. For smaller portfolios, direct negotiation is usually sufficient.
New customers typically achieve 10-20% discounts off list pricing. Renewals see 5-15%. Multi-year commitments secure 15-25%. Quarter-end timing adds another 5-10%. Volume consolidation across multiple products can push discounts to 30-40% for enterprise deals.
Walk away when the vendor refuses reasonable escalation caps on multi-year deals, demands termination fees exceeding 25% of remaining contract value, won’t commit to acceptable SLA terms with real remedies, requires proprietary data formats that lock you in, or when alternatives offer 30%+ better value for comparable features.
Usage data showing actual adoption versus paid licences provides right-sizing leverage. Competitive alternatives demonstrate you’re monitoring the market even if switching is painful. Multi-year commitment offers revenue certainty vendors value in exchange for concessions. Expansion into additional products from the same vendor creates bundle opportunities. Customer reference participation and case studies have value vendors may trade for pricing concessions.
Implement contract lifecycle management immediately, tracking all renewal dates, notice periods, and key terms in one place. Set alerts for 6 months (begin research), 4 months (obtain competitive quotes), 3 months (begin negotiations), and 120 days (latest start to avoid auto-renewal) before each renewal date so nothing catches you by surprise.
Request: “Annual price increases shall not exceed 3-5% or the percentage increase in the Consumer Price Index (CPI), whichever is lower.” Avoid vague terms like “reasonable increases” or “market rates”—they mean nothing and give the vendor complete discretion. Make the cap explicit and ensure it applies to all fees—base subscription, support charges, and add-ons.
Request extended payment terms like Net 60 or Net 90 versus the standard Net 30. Explore annual payment discounts, which typically run 10-15% versus monthly billing. Propose quarterly payments as a middle ground compromise. For large implementations, negotiate milestone-based payments tied to delivery rather than upfront payment.
Implementation and onboarding fees. Premium support charges beyond basic support. API usage overages when you exceed rate limits. Data storage fees as your usage grows. Integration fees for connecting to other systems. Training charges for getting your team up to speed. User tier upgrade fees when someone needs more access. Vendors use AI bundling and credit multipliers to mask price hikes—a service costing 10 credits can rise to 20 credits overnight and they’ll call it an enhancement.
Leverage your technical background for data-driven negotiation using usage analytics and performance metrics. Quantify ROI and cost-per-user in ways procurement might miss. Evaluate technical alternatives credibly—you understand the switching costs and integration complexity better than anyone. Understand what’s genuinely hard to migrate versus vendor lock-in tactics. Bring in finance or legal for business terms and contract language. Use technical requirements like API limits, security certifications, and compliance needs as non-price negotiation points vendors can often accommodate more easily than price cuts.
How to Audit and Reduce SaaS Spending Through Software RationalisationThe average organisation is managing 275 SaaS applications in 2025 and wasting 30% of their software spending on unused or underutilised licences. Shadow IT makes it worse—3.8% of total spend is going to unauthorised applications your IT department doesn’t even know exists.
Adobe cut their application count from 2,600 down to 400 and saved $60 million in the process. This guide is part of our comprehensive analysis on why SaaS prices are rising 4x faster than inflation and what you can do about it, where we explore the full scope of the rising software costs crisis and practical strategies to manage it.
In this article we’re going to walk you through discovering every application in your organisation, reclaiming unused licences, and setting up governance to prevent this mess from happening again. Let’s get into it.
There’s no single source that gives you complete visibility. You need four complementary discovery methods to find everything.
Financial records review is where you dig through credit card statements, expense reports, and procurement records. Check all corporate cards, departmental purchasing accounts, and employee reimbursements for recurring software charges. This finds your paid subscriptions but misses free-tier tools and trial accounts people have spun up.
Network scanning tools monitor traffic patterns to detect applications actually in use, including shadow IT that bypassed your approval processes entirely. SaaS management platforms like Zylo, Productiv, Torii, Vertice, CloudEagle.ai, and Josys automate this discovery for you.
SSO data analysis uses your single sign-on authentication logs to track which applications employees are actually accessing. If you’re using Okta, Azure AD, or Google Workspace, you’ve already got this data—you just need to pull the authentication logs.
Employee surveys capture the free accounts, browser extensions, trial subscriptions, and departmental purchases that technical scanning misses. People are using tools IT doesn’t know about. Ask them.
Most organisations discover 25-40% more applications than they initially estimated. Adobe thought they had 1,800. They found 2,600.
Deploy all four methods. Financial records find your paid subscriptions. Network scanning finds active usage. SSO logs show authentication patterns. Surveys capture tribal knowledge. You need all of it.
Once you’ve identified all your applications, you need to gather six categories of information to determine which to keep, consolidate, or eliminate.
Application inventory: This is your complete list with vendor names, subscription tiers, and cost per licence. Document every application with product name, vendor company, subscription plan level, and per-user pricing. This becomes your single source of truth.
Usage metrics: Login frequency, active users versus provisioned licences, feature adoption rates, and last access dates. Track how many users actually log in weekly or monthly compared to the licences you’ve purchased. Identify power users leveraging advanced features versus casual users who could function with basic tiers. If an application hasn’t had a login in 60+ days, it’s an elimination candidate.
Contract information: Renewal dates, contract terms, cancellation policies, and notice requirements. Record when each subscription renews so you can identify upcoming negotiation opportunities. Note contractual obligations—minimum commitment periods, cancellation notice requirements (often 30-90 days), penalties for early termination. This timing is going to drive your implementation roadmap.
Cost data: Total cost of ownership including licences, hosting, integration expenses, support, and training. Direct licence fees are only part of your true costs. You need to factor in API usage fees, premium support contracts, custom integration development, employee training time, and IT administration hours. Hidden costs often exceed base licence fees by 40-60%.
Business value: Which departments use each tool, which processes it supports, and what stakeholders actually think of it. Interview department heads to understand why they selected specific tools and what business outcomes those tools enable. You need to distinguish between “nice to have” applications and tools supporting revenue-generating processes or regulatory compliance.
Compliance requirements: Data residency needs, regulatory obligations (GDPR, CCPA, SOC 2, ISO 27001), and audit trail capabilities. Document whether applications process sensitive customer data, store information in specific geographic regions, or support compliance frameworks. These requirements often override cost considerations.
Where you find each type varies. Usage metrics come from SaaS management platforms or individual application dashboards. Contract information lives in procurement systems or email archives. Cost data requires aggregating from finance systems, expense reports, and vendor invoices.
Organise your findings in a spreadsheet or dedicated SaaS management platform. Key columns: application name, vendor, cost, licence count, active users, renewal dates, business owner, and rationalisation decision.
Apply the Gartner TIME Model. Categorise each application as Tolerate, Invest, Migrate, or Eliminate.
Tolerate: Applications that work adequately but aren’t strategic. Keep them as-is with minimal changes. Think departmental tools with satisfied users but limited expansion potential.
Invest: Strategic applications worth enhancing. Your core collaboration platforms, development tools, business-critical applications. These deserve additional licences, advanced features, or custom integrations.
Migrate: Applications to replace with better alternatives. Legacy tools with modern competitors, overpriced solutions, applications with poor vendor support. But only if the migration benefits exceed the transition costs.
Eliminate: Redundant, unused, or low-value applications. Zero usage in 90+ days, complete redundancy with retained tools, failed adoption despite training, abandoned pilot projects.
Start with eliminations where the data shows zero usage or obvious redundancy. Quick wins build momentum. Then tackle consolidation where you’ve got multiple tools providing overlapping functionality. Finally review the borderline cases with stakeholders.
Red flags for elimination: redundant functionality, less than 10% licence usage, annual costs exceeding value delivered. Green flags for retention: supports critical business processes, high engagement, unique capabilities.
Your rationalisation decisions should align with your broader response to rising SaaS costs—focusing your spend on tools that deliver measurable value while eliminating waste.
Licence reclamation is recovering unused or underutilised software licences. 53% of licences go unused according to 2025 data. This is your fastest path to savings without eliminating any applications.
There are three categories of reclaimable licences:
Inactive users: Departed employees whose licences remain active and billable. Set up automated offboarding workflows that flag all software access during employee exits.
Overprovisioned accounts: Premium licences for users who only need basic features. Users with premium Zoom licences who never host webinars can downgrade to basic licences. They keep their access, you reduce your per-seat costs.
Dormant licences: Purchased but never activated, or abandoned after onboarding. Pure waste.
Frame downgrade communications as optimisation, not cuts. Users retain access to features they actually use. The organisation redirects savings to tools that deliver broader value. Simple.
Most organisations reclaim 20-30% of licence costs within 30 days. Modernizing Medicine reclaimed 2,800 unused licences for $1.4 million in savings. No application elimination required.
Online training platforms average 14.2 applications per organisation. Project management averages 9.9. Team collaboration averages 9.5. This redundancy is wasting your money and fragmenting workflows.
You’ve got a choice: suite platforms like Microsoft 365 that bundle everything under unified licensing, or best-of-breed approaches with specialised tools for each function. Suite consolidation reduces vendor overhead but might sacrifice specialised capabilities. Best-of-breed maintains superior functionality but increases complexity.
Vendor consolidation gives you negotiating leverage during renewals. Fewer vendor relationships means less administrative overhead for contracts, security reviews, and integration maintenance. Once you’ve completed your audit and rationalisation, you can negotiate from a position of strength with concrete usage data and clear alternatives.
Change management determines success or failure here. Engage stakeholders early. Identify application champions who can advocate for transitions. Document migration requirements—data export, workflow replication, integration dependencies.
Start with a pilot department of willing early adopters. Gather feedback. Refine your processes, training, and support. Use pilot success to build confidence before you roll out more broadly.
Keep both old and new tools active during migration so users can reference historical data and revert if workflows break. Establish rollback procedures. Provide dedicated support during transitions.
Without governance, departments will independently purchase tools that recreate the redundancy and waste your audit just fixed.
Set up tiered approval based on cost and scope. Purchases under $100 monthly might need only manager approval. Department-wide tools or subscriptions over $1,000 monthly require IT and Finance review.
Maintain a single source of truth for all subscriptions—ownership, contracts, costs, renewal dates. A spreadsheet works for smaller organisations, a dedicated platform for scale.
Schedule quarterly usage reviews examining active users, licence utilisation, spending trends. Annual comprehensive audits to find new optimisation opportunities. Trigger evaluation 90 days before each renewal to consider downgrades, eliminations, or renegotiations.
SaaS management platforms provide continuous visibility through automated detection of new applications, usage tracking, spending monitoring, and optimisation alerts.
Designate application owners for each tool who manage access, monitor usage, and drive renewal decisions. Establish IT and Finance collaboration. Define decision authority to prevent bottlenecks.
The goal is preventing waste without creating rigid bureaucracy that drives employees toward unapproved shadow purchases.
Spreadsheets work for initial audits in smaller organisations under 50 applications. They’re sufficient for simple environments but unsustainable at scale.
SaaS management platforms provide automated discovery, real-time usage monitoring, renewal tracking with 90-day alerts, optimisation recommendations, and workflow automation. Platforms like Zylo, Productiv, Torii, and Vertice offer end-to-end capabilities. 70% of IT teams prefer all-in-one platforms over point solutions.
Match platforms to organisational needs. 50-100 employees: single-framework solutions. 100-300 employees: multi-framework platforms. 300-500 employees: hybrid approaches.
Start with a spreadsheet audit to understand the scope before committing to platform costs. Validate that optimisation opportunities exist, then invest in platforms for ongoing management.
Typical platform costs run $15,000 to $50,000 annually for mid-sized organisations. Most organisations achieve 5-10x ROI in the first year through sustained waste reduction.
Cost savings: Total spend reduction, cost per employee, eliminated subscriptions, reclaimed licences. Track hard savings from eliminations and soft savings from negotiated discounts.
Efficiency metrics: Application count reduction, vendor count reduction, administrative time saved and redirected to strategic work.
Usage optimisation: Active licence percentage (target 80%+), average utilisation per application, adoption rates for consolidated tools.
Governance metrics: Shadow IT as percentage of total spend (target under 2%), approval cycle time, process compliance.
Business impact: Employee satisfaction, productivity metrics, security posture improvement.
Document your baseline before optimisation: application count, total spend, cost per employee, waste percentage, shadow IT spend, licence utilisation rates. Compare to post-optimisation metrics.
Modernizing Medicine reclaimed 2,800 licences ($1.4M) and cancelled 122 applications ($1.6M). These measurable outcomes justify the effort.
Annual audits with quarterly usage reviews. If you’re growing fast or doing M&A, audit every six months. SaaS management platforms reduce the need for disruptive periodic audits through continuous monitoring.
Shadow IT is software purchased or used without IT approval. It’s 3.8% of total spend, creates security vulnerabilities through unvetted vendors, causes redundant spending, and prevents accurate forecasting. It emerges from slow approval processes or employees finding better tools than the sanctioned alternatives.
Discovery takes 2-4 weeks. Analysis takes 3-4 weeks. Implementation takes 8-12 weeks. Total: 3-5 months. SaaS management platforms can reduce discovery to days through automated scanning.
Joint ownership works best. IT provides technical expertise on usage patterns and alternatives. Finance contributes cost analysis and contract management. Appoint cross-functional teams with executive sponsorship from both departments.
53% remain unused according to 2025 data. Organisations waste approximately 30% of software spending. Audits typically discover 25% waste, concentrated in collaboration tools, project management, and marketing technology where departments independently purchase overlapping solutions.
Engage early before announcing decisions. Focus on usage data, not opinions. Propose trials of replacement tools. Identify champions to lead the change. Provide training. Maintain parallel access during migrations. Data showing low usage or high cost strengthens objective decision-making.
Audit is discovery and analysis—identifying applications, gathering usage data, assessing costs. Rationalisation is execution—implementing consolidation, migration, or elimination decisions. Audit provides the data. Rationalisation delivers the savings.
Spreadsheets work for initial audits under 50 applications. Platforms become essential at 100+ applications, for ongoing monitoring, and when automation delivers significant time savings.
Include licence costs, implementation and integration expenses, training, support and maintenance, data storage, premium features, and allocated IT administration time. Hidden costs often exceed base licence fees by 40-60%.
Approval workflows with spending thresholds. Evaluation criteria: business justification, existing alternatives, security review, cost-benefit analysis. Ownership assignment. Contract terms requirements: cancellation policies, data export capabilities. Usage monitoring with quarterly reviews and annual audits. Offboarding procedures for licence reclamation.
Eliminate when you’ve got zero usage, complete redundancy, failed adoption, or vendor concerns. Consolidate when overlapping functionality serves different users, migration complexity exceeds savings, or specialised features aren’t available in your standard tools.
Network scanning for SaaS traffic patterns. SSO authentication logs for unauthorised applications. DNS queries for SaaS vendor domains. Employee expense reports. Credit card statements for recurring charges. Employee surveys. SaaS management platforms automate discovery through continuous monitoring.
Auditing and rationalising your SaaS portfolio is your most direct path to regaining control over software costs. The data shows that most organisations waste 30% of their software spend on unused licences, redundant applications, and unmanaged shadow IT. You’ve now got the framework to find that waste, reclaim those costs, and prevent them from recurring.
Start with the quick wins—licence reclamation delivers results in 30 days. Build momentum with eliminations where usage data is clear. Then tackle consolidation where it reduces vendor overhead and increases negotiating power. Finally, implement governance to ensure the mess doesn’t recreate itself.
For a complete overview of the software inflation crisis and additional strategies to protect your budget, see our comprehensive guide on why SaaS prices are rising 4x faster than inflation and what you can do about it.
How Salesforce Microsoft Google and Atlassian Are Raising Prices in 2025Your SaaS bills are about to jump. We’re not talking small bumps here. Microsoft is pushing increases of 5-40% across its products. Google bumped Workspace pricing 16.7% and made AI features mandatory. Salesforce slipped in another 6% increase after they hit you with 9% in 2023.
The numbers tell a rough story. SaaS inflation is running at 11.4% year-over-year while general inflation sits at 2.7%. Your software costs are climbing four times faster than everything else. This SaaS price crisis affects all software spending, not just these four vendors.
This article breaks down what Salesforce, Microsoft, Google, and Atlassian are doing with pricing in 2025. You’ll see the exact percentage increases, when they kick in, and the hidden costs they’re sneaking in.
When you’re ready to push back, check the tactics that work best in renewal discussions.
Microsoft leads with Power BI Pro up 40% from $9.99 to $14 per user per month. Adobe sits between 17-50%. Atlassian is around 7.5% for cloud but they’re forcing Data Center customers to migrate by cranking on-premise pricing up 15-40%. Salesforce is hitting 6-9% direct increases plus bundling AI you might not want.
It’s a pattern. Average SaaS price increases are running at 8-12% annually.
73% of SaaS vendors hiked prices in 2023 and they’re at it again in 2025. Businesses spend an average of $9,100 per employee on SaaS now, up 27% year-over-year. If you’re dropping $1M annually on software, you’re looking at an extra $114,000 for the exact same stack.
Why are vendors doing this? Because they can. Joel Windels at Vertice put it plainly: “Software vendors are hiding behind the idea that inflation is high, so therefore they can charge more. Tech companies’ revenue growth is not as good as it was. Increasing prices is a relatively simple way of trying to squeeze more dollars out of their customers.”
60% of vendors mask their price increases. Another 57% hide pricing from public view entirely. You have to get on a sales call just to see what things cost.
Salesforce is raising prices 6% for Enterprise and Unlimited Editions across Sales Cloud, Service Cloud, Field Service, and select Industry Clouds starting August 1, 2025. This comes after their 9% increase in 2023.
Here’s what matters: In 2025, price increases are contributing approximately 6.3 percentage points of 8.7% total growth. That’s 72% of growth. They’re pulling more money from existing customers rather than growing the user base.
Top-tier pricing now hits $500 per seat per month for Sales Cloud Unlimited, up from $250 five years ago. That’s doubled.
Salesforce is also pushing AI through bundling. Agentforce add-ons are priced at $125 per user per month. Whether you use these capabilities or not, you’re paying for them if you want premium tiers.
Start renewal talks 120-180 days before your contract expires to give yourself maximum leverage.
Power BI Pro increased 40% from $9.99 to $14 per user per month on April 1, 2025. Power BI Premium Per User went up 20% from $20 to $24. Teams Phone Standard jumped 25% from $8 to $10.
Microsoft’s new commerce experience slaps a 20% surcharge on monthly billing compared to annual prepayment. For a 100-user M365 E3 deployment, this adds approximately $3,000 annually.
Dynamics 365 isn’t escaping either. Business Central Essentials increased from $70 to $80 per user per month (14% jump) on October 1, 2025. Business Central Premium went from $100 to $110 per user per month.
SQL Server received 10% price increases across Standard and Enterprise editions starting January 1, 2025. SharePoint, Exchange, and Skype for Business Server all got 10% increases on July 1, 2025.
Regional pricing varies wildly. Brazil customers face 12% increases. UK customers got -5% to -6% adjustments.
Microsoft is bundling Copilot AI across all products. Whether you want AI help or not, you’re getting it and paying for it. This tacks on $20-30 per user per month if you move to tiers that include Copilot.
The message is clear: annual billing gets you the best deal, monthly billing penalises you, and AI features are becoming mandatory.
Google Workspace Business Standard increased from $12 to $14 per user per month for annual plans. That’s 16.7%. Business Starter went from $6 to $7 per user per month. Business Plus jumped from $18 to $22 per user per month (22.2%).
Price bumps hit new customers on January 16, 2025. Existing customers won’t see increases until at least March 17, 2025.
The bigger change is AI bundling. Gemini AI features are now included in all Workspace Business and Enterprise plans by default. Gemini used to cost $20-30 per user per month as an add-on.
Google killed the standalone Gemini add-on. AI is mandatory in all business tiers now. You can’t opt out.
A Google Cloud spokesperson justified this by saying “AI is foundational to the future of work.” The problem is if you’re not using AI features, you’re paying for development that benefits other customers. One partner said a customer called “in a panic saying, ‘We’re not ready for this AI. Why is it on? And when do I have to start paying more for something I don’t want?'”
Atlassian increased Jira Standard plans by 5%, Premium by 7.5%, and Enterprise by 7.5-10% on October 15, 2025. Confluence got the same percentage bumps. Jira Service Management took 5% for Standard and 7.5% for Premium and Enterprise.
Bitbucket got hit with 10% for both Standard and Premium.
The real squeeze comes from Data Center edition increases. Jira Software Data Center saw 15% increases for 1-1,000 users, 20% for 1,001-5,000 users, 25% for 5,001+ users, and 30% for legacy advantage pricing.
This is intentional. Atlassian is using pricing as a weapon to force Data Center customers to cloud. Stay on-premise if you need to, but you’ll pay heavily for it.
A 2,000-user Jira Cloud Premium plan at list price saw bills rise from $189,000 to $203,175. That’s $14,175 more per year for identical functionality.
Valiantys recommends renewing within 90 days of October 15 at current tier pricing to lock in rates.
Shrinkflation affects 28% of SaaS contracts. Same price, reduced features or tighter usage limits.
Four tactics show up most: feature bundling, feature unbundling, non-cumulative pricing, and reduced discounting.
Feature bundling forces you to purchase unwanted functionality. AI features that used to be optional add-ons now appear as mandatory inclusions, adding $20-30 per user per month.
Feature unbundling is the opposite. Previously bundled features now show up as separate line items. Zendesk split what used to be in their core Support product into separate charges for chat, voice, and analytics. What you got in one subscription now needs three.
Non-cumulative pricing shifts usage-based pricing from cumulative credits to fixed monthly models. Zoom cut the rollover window for meeting minutes from unlimited to monthly allocations. Don’t use your monthly allocation? You lose it.
Reduced discounting means salespeople have less pricing flexibility than before. HubSpot tightened discount approval levels in 2024. The discounts you negotiated three years ago might not be available at renewal.
A service costing 10 credits can rise to 20 credits overnight, doubling your costs without changing the nominal price.
55% of SaaS vendors obscure pricing. 33% include price uplift clauses varying by industry.
Consumption overages create the nastiest surprises. API calls, storage, and compute usage beyond included limits generate unpredictable bills. Consumption-based pricing creates bills that can spike 50-200% above baseline.
User tier jumps trigger massive cost bumps. Going from 50 to 51 users can trigger a 40% price increase because you’ve crossed into the next tier bracket.
Migration fees are appearing more frequently. Vendors charge 5-15% “migration-related” increases. You’re paying them to move you to their new platform.
HubSpot shows how consumption traps work. They auto-upgrade users whose AI usage passes the credit limit, automatically buying additional credit packs without asking.
45.7% of all SaaS licences go unused, up 7% in 12 months. You’re paying for seats that provide zero value.
Implement monitoring alerts at 75% of budget thresholds for consumption pricing. Negotiate consumption caps in contracts to control unpredictable bills.
Multi-year discounts typically offer 5-15% off list price for 3-year commitments. The real benefit is price cap protection. Lock in 2-3% annual increase limits versus the 10-15% annual increases vendors are implementing.
Multi-year contracts now account for 40% of SaaS agreements, up from just 14% in 2022. More businesses are locking in rates to avoid inflation.
Early renewal leverage works. Vendors offer 10-20% discounts to lock in revenue before contract expiry. Starting negotiations 120-180 days before renewal gives you maximum leverage.
Without renewal caps, you face list-price resets or automatic 7-10% uplifts at renewal. A 30% discount negotiated upfront could vanish at renewal without price protection clauses.
Use language like “The renewal price per user will remain $100” or “All current discount percentages will apply to renewal.” Avoid vague wording like “mutually agreed pricing” or “prevailing rates at renewal.”
83% of successful renewal negotiations start at least 120 days before the renewal date. Starting less than 60 days before expiry weakens your position significantly.
Expect 6-9% list price increases plus potential tier upgrades if they push AI features on you. Your actual increase might hit 15-25% when you factor in Einstein Copilot bundling and data storage overages. Start negotiations 120 days early and use competitive quotes from HubSpot or Dynamics 365 as leverage.
Yes. Microsoft’s new commerce experience adds a 20% surcharge for monthly billing compared to annual prepayment. For a 100-user M365 E3 deployment, this adds roughly $3,000 annually. Annual billing with auto-renewal gets you the best pricing now.
Yes, especially 90-120 days before contract expiry. Tactics include cutting seat count through usage audit (20-40% reductions are common), requesting multi-year price caps, leveraging competitive alternatives, and using buying consortiums. The US federal government negotiated a 90% discount on Slack through aggregated demand.
AI bundling forces AI features like Copilot, Gemini, and Einstein into standard subscriptions regardless of customer need or usage. Google’s Gemini adds $30 per user per month in equivalent value. Microsoft’s Copilot adds $20-30 per user per month. If you’re not using AI features, you’re subsidising development for other customers.
Use SSO login analytics to find users who haven’t accessed software in 60-90 days. SaaS management platforms like Zylo, Productiv, and Torii automate this discovery. Average organisations find 30-40% of licences are unused or underutilised. That’s immediate cost reduction.
Consider open source when vendor lock-in is low, internal technical capability is high, and total cost of ownership (including hosting, support, maintenance) is genuinely lower. Examples include Jira to Linear or Plane, Confluence to Outline or BookStack. Calculate TCO including implementation effort and opportunity cost.
Consumption pricing creates bills that jump around significantly. Three out of five SaaS companies now use usage-based pricing models. Salesforce Data Cloud, Azure services, and Snowflake run on consumption models where costs can spike 50-200% above your baseline. Set monitoring alerts at 75% of budget thresholds and negotiate consumption caps.
Software now represents 14-21% of IT budgets, up from 13% five years ago. Average SaaS cost per employee ranges from $7,900 to $9,100. Benchmark against industry: technology companies spend 25-30%, manufacturing 10-15%, professional services 15-20%.
Calculate current software waste: 30-40% unused licences, 20% redundant applications, 10-15% savings from better negotiations. SaaS management platform ROI typically hits 5-10x in year one. Example: $2M software spend, $80K platform cost, $400K identified savings equals 5x ROI. Include cost avoidance from preventing shadow IT.
Price increases are legal if your contract terms allow them. Most enterprise SaaS contracts include clauses permitting annual increases of 3-8%. Review your contract for price protection clauses, required notice period (typically 30-90 days), and termination rights. If increases exceed contractual limits, you have grounds to negotiate or exit without penalty.
Zylo leads for enterprise renewal management and price tracking. Productiv excels at usage analytics and shadow AI discovery. Torii offers strong workflow automation. Vertice combines spend management with procurement negotiation services and publishes the SaaS Inflation Index. Choose based on company size: SMB (Torii), mid-market (Productiv), enterprise (Zylo).
Begin 120-180 days before contract expiry for maximum leverage. This timeline allows: 60 days for usage audit and seat reduction, 30 days for competitive alternative evaluation, 30-60 days for vendor negotiation rounds, and a 30-day buffer for legal review and approval. Starting less than 60 days before expiry weakens your negotiating position significantly.
These vendor price increases are part of a broader pattern where SaaS prices are rising at 4x the rate of general inflation. Understanding what Salesforce, Microsoft, Google, and Atlassian are doing with pricing helps you prepare for renewal conversations and build the business case for better cost controls.
Why SaaS Prices Are Rising 4x Faster Than Inflation and What You Can Do About ItYour software budget faces unprecedented pressure. SaaS prices increased 12.2% in 2024 while general inflation ran at 2.7% — a 4.5x gap that’s reshaping how you allocate technology spend. Software now consumes 21% of IT budgets, up from 13% just five years ago, and the average organisation spends over $9,000 per employee annually on SaaS subscriptions.
SaaS inflation has persisted for three consecutive years at 11-12% annually. Vendors like Salesforce, Microsoft, Google, and Atlassian are raising prices 6-40% across their product lines, using AI bundling as justification and relying on customer switching costs to prevent departures. Meanwhile, shrinkflation—discussed below—compounds these overt increases.
This guide provides the comprehensive overview you need to understand what’s happening and clear paths to tactical responses. You’ll find detailed analysis on specific vendor tactics, frameworks for auditing and reducing spend, negotiation playbooks for securing better contracts, tool comparisons for spend management platforms, and governance strategies for long-term cost control.
What you’ll find in this resource hub:
SaaS inflation is the year-over-year rate of price increases in Software-as-a-Service subscriptions, currently running at 12.2% according to the Vertice SaaS Inflation Index — 4.5 times higher than general inflation in G7 countries at 2.7%. This gap represents systematic vendor pricing power that’s outpacing economic fundamentals, turning software budgets into a pressure point for technology leadership.
The Vertice SaaS Inflation Index measures actual contract renewal price changes across thousands of SaaS vendors, providing the most authoritative benchmark for tracking software cost increases. In 2024, the index recorded its highest-ever annual increase at 12.2%, while general consumer price inflation stabilised around 2-3% in developed economies. SaaS inflation has consistently outpaced general inflation for three consecutive years, with an average rate of 11-12% annually.
For IT budgets, this means software is consuming a growing share of total spend. BCG research shows software’s share of IT budgets grew from 13% to 21% over five years — a 50% increase driven primarily by per-seat price increases rather than expanded usage. For the first time ever, software spending has surpassed employer contributions to healthcare coverage.
The gap between SaaS inflation and general inflation matters because it reveals vendor pricing behaviour disconnected from underlying cost pressures. While SaaS companies operate with 80%+ gross margins, they’re raising prices at rates that suggest scarcity rather than abundance. Joel Windels from Vertice observes that “software vendors are hiding behind the idea that inflation is high, so therefore they can charge more” — even as their actual cost increases remain modest.
Deep dive: How Salesforce Microsoft Google and Atlassian Are Raising Prices in 2025 provides vendor-by-vendor analysis of specific price increase tactics.
SaaS vendors possess significant pricing power due to high customer switching costs, vendor consolidation reducing competition, and AI bundling that justifies premium pricing. Unlike commodity markets where inflation tracks production costs, SaaS operates with 80%+ gross margins, allowing vendors to raise prices based on customer captivity rather than cost pressures.
Vendor consolidation has fundamentally reduced competitive pressure. In CRM, marketing automation, and collaboration software, 2-3 vendors now dominate each category. Major vendors now derive the majority of their revenue growth from price increases rather than new customer acquisition — a clear signal of pricing power over market expansion. When you’re locked into Salesforce, Microsoft, or Google’s ecosystem, the competitive alternatives that once disciplined pricing have largely disappeared through acquisition or market exit.
Customer switching costs create vendor lock-in that enables sustained pricing increases. Migrating from Salesforce to HubSpot or Microsoft to Google Workspace involves data migration, workflow reconfiguration, user retraining, and integration rebuilding — costs that often exceed 18-24 months of the price increase being avoided. Vendors understand this math and price accordingly. As long as the annual 10-15% increase costs less than migration, they know you’ll stay.
AI feature bundling has become the newest justification mechanism. Microsoft forces Copilot into M365 subscriptions, Google bundles Gemini into Workspace, and Salesforce packages Einstein AI whether customers use it or not. This adds 10-20% to renewal costs while claiming “enhanced value” from features many organisations don’t adopt. The AI tax appears across platforms as vendors shift from optional AI add-ons to mandatory AI inclusion in base tiers, regardless of actual customer usage or ROI. Our detailed vendor analysis examines how each major platform implements this tactic.
The combination creates a pricing environment where vendors can extract maximum value. They’ve consolidated markets to reduce alternatives, built switching costs that trap customers, and layered AI features that justify price increases. The result is inflation running 4x general rates with limited competitive pressure to moderate increases.
Deep dive: How Salesforce Microsoft Google and Atlassian Are Raising Prices in 2025 breaks down specific vendor tactics and percentage increases.
Response strategy: How to Build a SaaS Governance Framework That Prevents Cost Blowouts provides long-term controls to limit vendor pricing power.
The average organisation spends $9,100 per employee annually on SaaS subscriptions, according to Vertice’s 2025 research. This represents a year-over-year increase of 15% from the previous $7,900 benchmark, and the figure continues climbing as vendors layer AI features and premium tiers onto existing contracts.
This per-employee cost compounds dramatically as organisations scale. A 200-person company faces an annual SaaS bill of $1.82 million; scaling to 500 employees pushes costs above $4.5 million. These figures exclude implementation costs, training, integration development, and the hidden expenses of tool sprawl where teams adopt redundant solutions. Companies now manage an average of 275 SaaS applications, creating coordination complexity alongside direct costs.
Cost-per-employee varies significantly by industry and company maturity. Technology companies with developer-heavy workforces average $12,000-15,000 per employee due to development tools, infrastructure platforms, and collaboration software. Professional services firms typically run $7,000-9,000 per employee, while retail and manufacturing average $5,000-7,000. Healthcare leads all sectors at $10,150 per employee, driven by specialised clinical applications like Epic and compliance tools such as HIPAA-certified communication platforms.
The growth trajectory concerns leadership teams across functions. Software’s share of total IT budgets has expanded from 13% to 21% over five years, and with SaaS inflation running at 12% annually versus 2-3% general IT cost inflation, this budget pressure will intensify without active cost management interventions. The question isn’t whether to act but how quickly you can implement controls before renewals lock in higher baseline costs.
Cost reduction: How to Audit and Reduce SaaS Spending Through Software Rationalisation provides a framework for identifying waste and optimising licences.
Tool selection: Comparing Zylo Productiv Torii and Vertice for SaaS Spend Management helps you choose platforms that track per-employee costs automatically.
Industry benchmarks suggest software should represent 15-21% of total IT budgets, though this varies by company size, industry, and technology maturity. The critical consideration isn’t hitting a specific percentage but rather ensuring software spending delivers measurable value and aligns with strategic priorities versus accumulating through unmanaged sprawl.
Software’s share of IT budgets has grown from 13% to 21% over five years — a 50% relative increase driven primarily by SaaS subscription growth and price increases. This shift represents software consuming budget that historically funded infrastructure, personnel, or innovation projects. IT budgets for third-party services grew by about 6% annually from 2019 through 2024, but software costs increased by 50% as a share of total tech budget during that period.
The “right” software percentage depends on your operating model. SaaS-first organisations leveraging platforms like Salesforce, Workday, and ServiceNow might appropriately run 25-30% software spend if this replaces custom development and infrastructure costs. Conversely, product companies with significant internal development may run 12-15% software spend while investing heavily in engineering salaries. The percentage itself matters less than the efficiency of spending.
What matters more than the percentage is spending efficiency. Research shows 20-30% of SaaS licences go unused, 40% of organisations pay for redundant applications, and shadow IT accounts for an additional 30-50% of managed software spend. A 20% software budget where 30% is waste is worse than a 15% budget fully optimised. The goal isn’t hitting a benchmark percentage but eliminating waste and ensuring every dollar delivers value.
Optimisation framework: How to Audit and Reduce SaaS Spending Through Software Rationalisation shows how to identify waste and improve efficiency.
Governance approach: How to Build a SaaS Governance Framework That Prevents Cost Blowouts establishes controls for sustainable spending.
Salesforce leads major vendor increases at 6-9% annually with 72% of growth from price hikes rather than new customers. Microsoft implemented 10-40% increases across products, Adobe raised Creative Cloud prices 17-50%, Atlassian increased Jira and Confluence approximately 7.5%, and Google embedded Gemini AI into Workspace for effective 15-20% cost increases through bundling.
Price increase justification falls into three categories. AI bundling drives vendor tactics at Microsoft (Copilot), Google (Gemini), and Salesforce (Einstein). Tier elimination forces upgrades at Adobe Creative Cloud and Microsoft M365. Direct percentage hikes appear across IBM (6-24%), Oracle (8%), SAP (5%), and most major platforms. Power BI Pro jumped from $9.99 to $14 (a 40% increase), while Google Workspace Business Plus went from $18 to $22 per user (22% increase).
The AI bundling pattern described earlier—Copilot, Gemini, Einstein—delivers 10-20% cost increases disguised as “enhanced value.” Vendors price AI features at premium tiers regardless of customer adoption, knowing switching costs deter migration. The AI tax applies whether you use the features or not, as vendors shift from optional AI add-ons to mandatory AI inclusion in base tiers, regardless of actual customer usage or ROI.
Shrinkflation affects 28% of SaaS contracts according to CFO Dive research. Vendors reduce features, eliminate lower-priced tiers, impose usage limits, or add surcharges (Microsoft’s 5% monthly billing fee) while maintaining or increasing headline prices. This hidden pricing pressure compounds overt increases. A 7% renewal price increase combined with feature reduction or usage caps can deliver effective cost increases of 15-25% when organisations must purchase add-ons to maintain previous functionality.
Vendor analysis: How Salesforce Microsoft Google and Atlassian Are Raising Prices in 2025 provides detailed breakdown of specific vendor tactics and price changes.
SaaS shrinkflation occurs when vendors reduce features, eliminate pricing tiers, impose usage limits, or add surcharges while maintaining or increasing subscription prices — effectively reducing value-per-dollar. CFO Dive research shows 28% of SaaS contracts experienced shrinkflation in 2024, making it as significant as direct price increases for total cost impact.
Shrinkflation manifests in multiple forms that are harder to detect than headline price increases. Microsoft’s elimination of lower-tier M365 plans forces customers to higher-priced SKUs. Salesforce’s introduction of usage-based consumption charges on previously unlimited features. Adobe’s reduction of cloud storage in Creative Cloud packages. Atlassian’s Data Center price increases designed to force cloud migration. Each tactic reduces what you receive for the same or higher price. Understanding these patterns helps you negotiate better terms when renewing contracts.
Vendors layer shrinkflation onto price increases, compounding budget impact. More than half (57%) of SaaS vendors hide their pricing from public view, and 60% deliberately mask their rising prices, making cost clarity difficult. When tier eliminations combine with annual price increases and feature reductions, the effective cost increase can reach 15-25% even when the vendor announces only a 7% price adjustment. These compound effects rarely appear in vendor communications.
Detecting shrinkflation requires comparing contract terms year-over-year: seat minimums, included features, usage limits, support levels, SLA terms, and pricing tier availability. Usage analytics become critical — if licence costs increase while available features decrease, you’re experiencing shrinkflation regardless of vendor messaging about “enhanced value.” The challenge is that vendors make pricing complicated and difficult to understand by design, as they charge the same price for reduced functionality while looking to increase revenues.
Vendor tactics: How Salesforce Microsoft Google and Atlassian Are Raising Prices in 2025 identifies specific shrinkflation patterns.
Negotiation response: How to Negotiate Better SaaS Contracts and Lock In Lower Prices shows how to push back on shrinkflation.
Understanding the scale of price increases raises an immediate question: how much are you actually spending? Start with SSO integration logs to identify all applications receiving authentication, cross-reference with expense reports and credit card statements to capture shadow IT, then analyse usage patterns via login frequency and feature adoption to classify tools as essential, underused, or redundant. This three-step discovery reveals the true scope before optimisation decisions.
Comprehensive SaaS audits typically uncover 30-40% more applications than IT teams initially estimate. Shadow IT accounts for this gap — departments purchasing directly via credit card, free tier applications that escalated to paid, legacy tools that continue auto-renewing, and acquisitions that brought duplicate software stacks. IT is responsible for just 26% of SaaS spending, leaving the majority in business unit hands where visibility is limited.
Usage analytics distinguish purchased licences from active users. SSO login data shows which employees actually authenticate monthly, while application-specific analytics reveal feature adoption depth. As noted earlier, 20-30% of paid licences typically remain unused, presenting immediate optimisation opportunities without functionality loss — you can eliminate unused seats without impacting operations.
The audit should quantify overlap and redundancy. Many organisations run 3-5 tools covering the same use case — separate project management platforms, multiple communication tools, overlapping analytics solutions — because different teams made isolated buying decisions. Identifying these duplications enables consolidation conversations. The goal is creating a comprehensive inventory with owner, department, renewal dates, usage metrics, and cost allocation before making optimisation decisions.
Complete framework: How to Audit and Reduce SaaS Spending Through Software Rationalisation provides the step-by-step audit process with optimisation strategies.
Supporting tools: Comparing Zylo Productiv Torii and Vertice for SaaS Spend Management evaluates platforms that automate the discovery and audit process.
Begin negotiations 120+ days before contract expiry with usage audit data showing licence right-sizing opportunities, use competitive alternatives as leverage for discounts, insist on multi-year price cap language with 2-3% annual increases maximum, and leverage vendor end-of-quarter urgency to secure 15-30% discounts from list prices.
Timing determines negotiation leverage. Vendors discount more aggressively in the final weeks of their fiscal quarters, and procurement teams who engage 90-120 days before renewal can pressure vendors to discount early rather than risk missing quarterly targets. Last-minute renewals surrender this timing advantage. Align your negotiations with vendor fiscal calendars to maximise leverage when sales representatives need deals to hit quotas.
Licence right-sizing creates immediate negotiation power. Reducing seat counts by 20-40% based on actual usage data from your software audit establishes credible departure risk that vendors must address with pricing concessions. This works even without competitive alternatives because vendors prefer discounted renewals to customer losses. Usage data gives you the evidence to push back on vendor assumptions about your needs.
Multi-year agreements with price caps protect against future inflation. Contract language specifying “2% annual increase maximum” or “CPI-indexed pricing” locks in predictability. While extreme examples exist (the U.S. federal government achieved 90% off Slack through volume consolidation and public sector leverage), most organisations achieve 15-30% off list with prepared negotiation. The vendor gross margins support these discounts; the question is whether you have the leverage and preparation to extract them.
Negotiation playbook: How to Negotiate Better SaaS Contracts and Lock In Lower Prices provides tactical scripts, timing strategies, and contract language templates.
Preparation: How to Audit and Reduce SaaS Spending Through Software Rationalisation gives you the audit data needed for negotiation leverage.
Manual tracking can’t deliver the visibility needed for effective negotiation. This is where specialised platforms become essential. Enterprise-focused platforms include Zylo for renewal management and cost optimisation, Productiv for usage analytics and shadow AI visibility, Torii for workflow automation, and Vertice for spend management with market intelligence. These tools automate discovery, track usage, predict renewals, and provide benchmark data that manual tracking cannot deliver at scale.
SaaS spend management platforms solve the visibility problem that enables cost creep. By integrating with SSO systems, expense tools, and vendor APIs, they automatically discover applications, track usage, allocate costs to departments, and alert on upcoming renewals — functionality impossible to replicate with spreadsheets as software portfolios exceed 50-100 applications. With companies managing an average of 275 SaaS applications, manual tracking becomes impractical.
Platform selection depends on organisational priorities. Zylo excels at renewal management and vendor negotiation preparation, with customers ranking reduced software costs as the number one outcome. Productiv provides deepest usage analytics for optimisation decisions. Torii offers strongest workflow automation for approval processes. Vertice combines spend management with competitive market intelligence from their inflation index research, giving you benchmarking context for negotiations.
ROI from these platforms typically achieves payback in 6-12 months through licence optimisation and negotiation improvements. Identifying 30 unused licences at $100/month each saves $36,000 annually; negotiating 15% better renewal terms on a $500,000 contract saves $75,000 — both common outcomes that exceed platform costs. The platforms enable optimisations that manual processes can’t scale to deliver, making them essential complements to your governance framework.
Platform comparison: Comparing Zylo Productiv Torii and Vertice for SaaS Spend Management provides detailed feature analysis and selection guidance.
Establish a software governance office with procurement policy authority, mandate SSO integration for all applications to ensure visibility, implement approval workflows requiring CTO/CFO sign-off for purchases above defined thresholds, and create vendor evaluation criteria that assess total cost of ownership including switching costs and lock-in risk.
Governance frameworks prevent the shadow IT and uncontrolled renewals that enable SaaS cost spirals. Without central oversight, departments make isolated buying decisions optimising for immediate functionality rather than portfolio efficiency, leading to redundant tools, incompatible systems, and fragmented vendor relationships that dilute negotiation leverage. Without these controls, marketing might purchase HubSpot while sales uses Salesforce, creating $120,000 in redundant CRM spend that audit discovery reveals.
Effective governance balances control with agility. Overly restrictive policies drive underground procurement and slow legitimate business needs; overly permissive approaches enable chaos. The framework should define clear approval tiers — for instance, auto-approve under $1,000/year, require manager approval for $1,000-10,000, and mandate governance committee review above $10,000 — with fast-track processes for pre-approved vendors. Acme Corp requires SSO integration for all tools serving more than 50 users, automatically flagging non-compliant purchases for review within their procurement workflow. This prevents governance from becoming a bottleneck while maintaining control.
Policy enforcement requires technical controls, not just documentation. Mandating SSO integration makes governance enforceable — applications that can’t integrate don’t get approved, immediately creating visibility into usage and preventing shadow IT. Blocking corporate credit cards from software vendor charges except through approved procurement channels reinforces this control. Technical enforcement works where policy documentation alone fails.
Framework implementation: How to Build a SaaS Governance Framework That Prevents Cost Blowouts provides policy templates, maturity model, and cultural change strategies.
Supporting tools: Comparing Zylo Productiv Torii and Vertice for SaaS Spend Management covers platforms that enforce governance workflows.
How Salesforce Microsoft Google and Atlassian Are Raising Prices in 2025
Vendor-by-vendor breakdown of specific price increase tactics, AI bundling strategies, and shrinkflation patterns affecting enterprise renewals. Essential reading for understanding what drives the 12.2% inflation rate and what to expect at your next renewal.
How to Audit and Reduce SaaS Spending Through Software Rationalisation
Complete framework for discovering shadow IT, analysing usage patterns, eliminating redundancy, and optimising licence counts before renewals. Includes audit checklists, usage metrics thresholds, and consolidation decision criteria.
How to Negotiate Better SaaS Contracts and Lock In Lower Prices
Negotiation playbook covering optimal timing, leverage tactics, contract language for price caps, and scripts for securing 15-30% discounts. Includes vendor fiscal calendar alignment and multi-year agreement trade-offs.
Comparing Zylo Productiv Torii and Vertice for SaaS Spend Management
Fair comparison of leading spend management platforms with feature matrices, pricing models, and guidance for matching tools to organisational needs. Covers Zylo’s renewal management, Productiv’s usage analytics, Torii’s workflow automation, and Vertice’s market intelligence.
How to Build a SaaS Governance Framework That Prevents Cost Blowouts
Strategic guide to establishing procurement policies, controlling shadow IT, assessing vendor lock-in, and evaluating open-source alternatives. Includes governance office structure, approval tier definitions, and maturity progression path.
The Vertice SaaS Inflation Index provides the most comprehensive benchmark, tracking actual contract renewal price changes across thousands of vendors. Published annually, the index measures year-over-year SaaS price increases and compares them to general inflation. Additionally, CFO Dive, SaaStr, and AnglePoint regularly publish enterprise software pricing research based on contract data and renewal tracking.
Beyond headline per-seat pricing, watch for consumption-based charges (API calls, storage, compute), mandatory support fees added at renewal, professional services requirements for upgrades, integration costs for ecosystem lock-in, monthly billing surcharges (Microsoft adds 5%), seat minimums that exceed your needs, and auto-renewal clauses that trigger without explicit approval. Read the full analysis in How Salesforce Microsoft Google and Atlassian Are Raising Prices in 2025.
Vendors bundle AI capabilities (Copilot, Gemini, Einstein) into standard subscriptions and use this as justification for 10-20% price increases, regardless of whether organisations actually use AI features. This AI tax appears across Microsoft M365, Google Workspace, Salesforce, and other platforms as vendors shift from optional AI add-ons to mandatory AI inclusion in base tiers. Our vendor pricing analysis details exactly how each platform implements this strategy.
The decision depends on integration complexity, negotiation leverage, and total cost of ownership. Vendor suites (Microsoft M365, Google Workspace, Salesforce Platform) offer bundled pricing, unified support, and pre-built integrations but create vendor lock-in and may include unused features. Best-of-breed tools provide optimal functionality but require custom integration, multiple vendor relationships, and potentially higher total costs.
Consider the cost comparison for a 200-person company: M365 suite might run approximately $2,400 per user annually for full functionality. Best-of-breed alternatives combining Slack, Notion, Zoom, and Dropbox can reach $3,200 per user annually when integration development, multi-vendor management overhead, and ongoing maintenance costs are factored in. The suite delivers 25% cost savings but creates deeper vendor lock-in. Evaluate total cost of ownership including switching costs and migration flexibility. Learn the complete framework in How to Audit and Reduce SaaS Spending Through Software Rationalisation.
Vendors raise prices at renewal for multiple reasons: scheduled annual increases (5-9% typical), tier eliminations forcing upgrades, AI feature bundling, transition from promotional to standard pricing, usage-based charges replacing unlimited plans, and general vendor pricing power where customer switching costs exceed price increase pain. Understanding these triggers helps with negotiation timing. See tactical responses in How to Negotiate Better SaaS Contracts and Lock In Lower Prices.
Analyse SSO login data to identify licences with zero authentication in the past 90 days, cross-reference application-specific usage analytics for feature adoption patterns, survey licence holders about actual tool necessity, and review expense data for recurring charges without assigned owners. Typical organisations find 20-30% of licences are unused and can be immediately eliminated. Full audit process detailed in How to Audit and Reduce SaaS Spending Through Software Rationalisation.
Evaluate open-source alternatives when vendor lock-in risk outweighs convenience, when self-hosting total cost (infrastructure, maintenance, support) falls below SaaS subscription costs at scale, when data sovereignty or security requirements mandate on-premises deployment, or when vendor pricing becomes predatory with limited alternatives. Factor in opportunity cost of internal maintenance and security patching responsibilities. Framework provided in How to Build a SaaS Governance Framework That Prevents Cost Blowouts.
Implement SSO integration requirements making applications visible through authentication logs, mandate procurement approval workflows for software purchases, block corporate credit cards from direct vendor charges except through approved channels, provide easy-to-access approved alternatives so teams don’t circumvent policies, and create fast-track approval processes (24-48 hours) for legitimate urgent needs. Technical controls work better than policy documentation alone. Implementation guide in How to Build a SaaS Governance Framework That Prevents Cost Blowouts.
SaaS inflation running at 12.2% versus 2.7% general inflation represents vendor pricing power disconnected from underlying costs. With software consuming 21% of IT budgets and climbing, the pressure on your technology spending will intensify through 2025 and beyond. Vendors have consolidated markets, built switching costs that trap customers, and layered AI features that justify price increases — creating an environment where they can extract maximum value from your renewals.
The response requires both immediate action and long-term strategy. Start with a comprehensive audit to understand your true software spend and usage patterns. Use that data to negotiate better contract terms at renewal, securing price caps and eliminating unused licences. Implement spend management tools to maintain visibility as your portfolio scales. Build governance frameworks that prevent shadow IT and uncontrolled renewals from recreating the waste you’ve eliminated.
The five cluster articles in this hub provide the tactical guidance you need. Each focuses on a specific aspect of the response — from understanding vendor tactics to implementing governance controls — giving you actionable frameworks rather than abstract strategy. Your next renewal is coming. The question is whether you’ll face it prepared with data, leverage, and alternative options, or whether you’ll accept vendor pricing as inevitable.
Start with the audit. Everything else builds from there.
Implementing Fair RTO Policies Without Destroying Team MoraleReturn-to-office mandates are decimating trust and talent retention. 80% of companies have already lost employees because of RTO policies. High performers are 16% more likely to leave when forced back.
This guide is part of our comprehensive analysis of return-to-office trends in 2025, where we explore what’s driving these mandates and their broader implications for technical teams.
Here’s the tension. Executives hand down RTO mandates while you’re protecting team morale and keeping your best engineers from walking.
When RTO goes wrong, you get surveillance culture. 34% of companies track badge swipes. 25% of executives admit they’re hoping for voluntary departures—using RTO as passive layoffs. Everyone plays productivity theatre instead of working.
It doesn’t have to play out that way. Fair implementation uses decision frameworks, trust-based communication instead of surveillance, phased rollouts, and transparent exception handling.
The difference is team-determined schedules versus top-down enforcement. When teams decide their in-office days, you get 91% fairness. When employers dictate the schedule, that drops to 73%. The gap is the difference between retaining high performers and losing them.
Evaluate three dimensions: business impact, talent risk, and cultural alignment.
Business impact means actual revenue consequences. If in-office presence genuinely improves collaboration for your specific work, that’s different from a blanket mandate with no clear benefit.
Talent risk needs hard data. Identify your top 20% by impact. If three or more signal they’ll leave over RTO, escalate with retention cost projections. Recruiting fees average 20-30% of salary, onboarding takes 3-6 months, and knowledge loss stalls projects.
Cultural alignment asks whether the mandate respects how your team works. Team-determined schedules get 91% fairness ratings because teams coordinate around actual collaboration needs.
Comply when: The mandate allows teams to choose their own days, provides reasonable timelines, and shows genuine collaboration benefits.
Push back when: The mandate requires surveillance enforcement like badge tracking, threatens retention of engineers with unique expertise, or contradicts your productivity data.
Gather evidence. Run retention risk assessments. Compare productivity metrics from remote versus office periods—delivery velocity, code quality, stakeholder satisfaction.
If three or more high performers plan to leave, build your business case. Present alternatives like team-led hybrid schedules or trial periods with measurable success criteria.
Choose your battles. Push back on surveillance and rigidity. Comply on reasonable hybrid—like three days—if you can negotiate team control over which days.
Transparency beats spin. If this is an executive mandate, say so. If the goal is collaboration, detail what specific activities you expect to improve. Never claim productivity benefits if your data doesn’t support it.
37% of employees forced back reported being unhappy, and 29% threatened resignation. That’s not because of office work—it’s because of broken communication.
Announce with three months lead time. People need time to adjust childcare, commutes, and work patterns.
Involve teams in schedule design. The difference between 91% fairness (team-determined) and 73% fairness (employer-dictated) comes down to autonomy. Let teams decide their in-office days based on when they actually need to collaborate.
Create real feedback channels. Anonymous surveys, 1-on-1s, team retrospectives. Then actually respond—acknowledge concerns publicly and share what you can and can’t change.
Avoid trust-destroyers: Surprise enforcement. Badge-tracking surveillance. Tying performance reviews to attendance before communicating expectations.
Equip managers with consistent talking points. Provide a clear decision framework for exceptions.
Acknowledge trade-offs honestly. RTO costs commute time and disrupts work-life balance. Explain what you expect to gain and admit you’re experimenting.
Commit publicly to fairness. Publish your exception process. Enforce policies consistently—no executive exemptions without documented business reasons. Show willingness to adjust based on outcomes.
Start with one day per week for two months. Increase to two days for two months. Reach your target—typically three days—by month six.
This gives teams time to adapt. Amazon’s hasty rollout led to desk shortages and plummeting morale without measurable productivity gains.
Consider piloting with volunteer teams first. Gather data on desk availability and collaboration effectiveness before rolling out company-wide.
Let teams synchronise their days collectively. Backend picks Monday-Wednesday, frontend takes Tuesday-Thursday. This ensures the colleagues they need are actually there.
Verify infrastructure readiness. Check desk availability. Set up meeting room booking systems. Confirm parking logistics.
Build in feedback checkpoints. Monthly surveys on what’s working. Track utilisation metrics. Monitor productivity and retention. Be willing to adjust if data shows problems.
Set adjustment triggers in advance. If high-performer departures spike, pause and investigate. If desk shortages create frustration, add space or reduce requirements. If collaboration metrics don’t improve, question whether more days are needed.
Hold at each phase for 6-8 weeks minimum. Don’t change policies mid-quarter during critical delivery periods.
Coffee badging—people badge in and leave—happens when your policy lacks genuine collaboration value. It’s a symptom of performative compliance rather than meaningful work.
Fix: Shift to team-determined days. Create valuable in-office activities like architecture reviews or sprint planning.
High-performer departure clusters—multiple key engineers resigning within weeks—means you’re losing talent.
Fix: Urgent retention conversations. Offer exceptions for roles where remote work succeeds. Pause the rollout and gather feedback.
Surveillance culture—managers obsessing over badge data, tying performance to attendance—damages trust. 88% of remote workers already feel pressure to prove productivity.
Fix: Remove badge data from performance systems. Train managers on outcome-based evaluation—measure delivery, impact, code quality, not office visibility.
Productivity drops—delivery velocity decreases, deep work suffers—indicates commute fatigue or office distractions outweigh collaboration benefits.
Fix: Allow focus-work-from-home days. Ensure quiet spaces exist. Reconsider how many mandatory days you need.
Equity issues—senior leaders exempted, parents penalised, disability accommodations ignored—create resentment and legal risk.
Fix: Transparent exception process with clear criteria. Ensure leadership models in-office presence.
Logistics breakdowns—desk shortages, parking chaos, meeting room unavailability—frustrate people daily.
Fix: Pause mandates until infrastructure is ready. Implement booking systems.
Formalise exception categories: medical and disability accommodations, caregiver responsibilities, extreme commutes, and role-based remote suitability.
Remote work is now the most-requested accommodation under the ADA. Courts recognise COVID proved remote work is viable.
Publish your exception process clearly. Define the decision timeline—respond within two weeks. Provide an appeal mechanism.
Use a decision matrix, not manager discretion. Can the role be performed effectively remotely? What’s the business impact? Document your rationale.
Disability accommodations require working with HR and legal. Recognise mental health conditions as valid needs. Don’t demand extensive medical disclosure. 63% of workers with disabilities prefer remote work, and 42% would consider leaving if forced back.
75% of caregivers say flexibility helps them manage work and home. Childcare and eldercare constraints disproportionately affect women. Offer phased schedules or specific-day flexibility.
For extreme commutes—two hours or more, or employees who relocated during remote periods—consider permanent remote status for high performers.
Role-based exceptions recognise some work is genuinely more effective remotely. Security engineers, infrastructure on-call, deep focus roles—evaluate based on outcomes and past performance, not optics.
Avoid favouritism. Don’t grant exceptions based solely on seniority. Ensure leadership follows the rules. Communicate aggregate exception rates so teams see consistent application.
Even rigid mandates have negotiation space. Who chooses the specific days? Whether days must be consecutive? Temporary exceptions during critical delivery periods?
Frame requests around business outcomes. Position flexibility as retention tool for key talent or recruiting competitive advantage based on delivery metrics.
Present productivity evidence from remote periods. Show delivery velocity, code quality, stakeholder satisfaction. Compare against office periods.
If three-day mandates are non-negotiable, negotiate which three days. Propose team-determined schedules around actual collaboration needs.
Suggest pilots with defined success metrics. Three-month trial with agreed measures: retention rates, delivery velocity, team satisfaction. Pilots reduce risk—easier to approve experiments than permanent changes.
Build coalitions with peer leaders facing similar challenges. Present unified proposals.
Understand your leverage. 70% of companies with fewer than 500 employees offer location flexibility, compared to just 14% of large enterprises. If you’re competing for talent against smaller, flexible companies, that’s leverage.
Badge tracking signals compliance matters more than outcomes, creating distrust. As we discuss in our overview of RTO mandates in 2025, enforcement methods reveal leadership’s true priorities.
When teams determine schedules, 91% see the policy as fair. When employers dictate schedules, fairness drops to 73%. That 18-point gap shows why enforcement method matters.
Surveillance damages culture. High performers resent it. They’re 16% more likely to leave when autonomy disappears.
Outcome-based accountability works better. Focus on delivery velocity, impact, code quality. Evaluate based on results, not location. Set clear quarterly goals. Measure actual output. Remove location from performance conversations.
Team-determined schedules let teams choose in-office days based on collaboration needs. Autonomy increases buy-in. Peer accountability replaces surveillance. Teams coordinate for collaboration-intensive activities and choose specific days that maximise in-person value.
Voluntary in-office programming creates compelling reasons to come in. Run architecture weeks, team-building events, learning sessions. Survey teams on what activities they find valuable. If people come voluntarily, you’ve succeeded.
Flexible core hours require overlap time for collaboration but allow location choice. Define core hours—say 10am-3pm for meetings. Outside that window, people choose location based on work type.
If you’ve already implemented surveillance, rebuild trust by publicly committing to remove it. Apologise for the signal it sent. Transition to outcome-based evaluation over six months.
54% of managers strongly agree they trust their teams to be productive remotely. If half of managers don’t trust remote teams, the problem isn’t the teams. It’s manager capability.
Fair RTO implementation comes down to balancing executive mandates with team needs—using frameworks that prioritise outcomes over surveillance, communication that builds trust rather than breaking it, and enforcement that treats people as professionals. For a complete overview of the broader RTO landscape and how these implementation practices fit into the wider context, see our comprehensive guide to return-to-office mandates in 2025.
Yes, but it requires early communication with at least three months’ notice, team-determined schedules instead of employer-dictated days, clear exception processes for accommodations, and genuine collaboration value when people are in the office. Monitor high-performer sentiment weekly and prepare retention packages if needed. The 16% higher departure risk for high performers means proactive mitigation is necessary, not optional.
Only 27% of companies plan full in-person work by end of 2025. 67% maintain hybrid arrangements, and 22% stay fully remote. Headlines focus on Amazon, JPMorgan, and Dell because their 5-day mandates are newsworthy exceptions. SMBs—67% of companies under 500 employees—remain remote, using flexibility as competitive advantage for talent.
Track delivery velocity, features shipped, code quality metrics, stakeholder satisfaction, and time-to-market before and after RTO. Compare against the same team’s remote periods, not different teams. Gartner found no measurable productivity gains among companies that enforced RTO. Beware proximity bias—measure objectively, not based on manager perception of who they see in the office.
Teams collectively decide which days to co-locate based on their actual collaboration needs—sprint planning days, architecture discussions, pair programming sessions. It gets a 91% fairness rating versus 73% for employer-dictated schedules. Works because it respects autonomy, creates peer accountability, and ensures the people who need to work together are actually there on the same days.
Yes. It signals you don’t trust people to do their jobs, which breeds coffee badging—people badge in then leave. High performers particularly resent surveillance because they value autonomy. Focus on delivery, impact, and outcomes instead of location monitoring. 88% of remote workers already feel pressure to prove productivity, and badge tracking amplifies that pressure without improving results.
Minimum six months: one day per week for two months, two days for two months, target—typically three days—by month six. Include feedback checkpoints at each phase, verify infrastructure readiness, and build willingness to pause if retention or productivity metrics decline. Rushed rollouts cause infrastructure problems and morale issues—phased approaches prevent this.
Medical and disability accommodations including mental health conditions, caregiver responsibilities for childcare or eldercare, extreme commutes over two hours or geographic relocation during remote period, and role-based remote suitability demonstrated by strong remote performance metrics. Document your case, use the formal exception process, and involve HR if needed. Remote work is the most-requested ADA accommodation.
Warning signs: No genuine collaboration justification, rigid enforcement without flexibility, lack of office infrastructure investment, surprise announcements with short timelines, and refusal to discuss retention concerns. 25% of executives admit hoping for voluntary departures. If you suspect this, document your performance and consider alternatives.
Be transparent: “This is a company decision I’m required to implement. I’ll advocate for maximum flexibility within the constraints and ensure we implement it fairly. Let’s discuss what would make this work better for you.” Don’t pretend to support it if you don’t, but commit to fair implementation and protecting your team within the boundaries you’re given.
Focus on asynchronous collaboration infrastructure—documentation, recorded meetings, clear decision trails. Designate core overlap hours for synchronous work, not full days. Use in-office time for same-location team members while including remote members virtually in important discussions. Measure inclusion and outcomes. Don’t penalise people for geographic distribution outside their control.
47% of companies with 5-day mandates plan termination for non-compliance. Google threatened this explicitly. Unless you have a documented exception for medical accommodation or other protected category, refusal risks your job. Better approach: request a formal exception with documentation, or begin a job search for remote-friendly employers if the mandate is unacceptable.
Train managers on outcome-based evaluation using delivery metrics, impact, stakeholder feedback, and code quality instead of office visibility. Remove badge data from performance systems. Ensure 1-on-1s are equally frequent for remote and in-office workers. Document achievements regardless of location. Audit promotion and raise data for location bias patterns. Active mitigation is required because proximity bias is nearly universal among managers.
Managing Engineering Teams in Hybrid Work Environments – Building Trust and ProductivityHybrid work is the new standard for engineering teams. Some people work from home, others are in the office, and everyone’s trying to figure out how to make it all work. As part of the broader return-to-office landscape in 2025, technical leaders face unique challenges in keeping distributed development teams productive and aligned.
The challenge is real. How do you keep productivity up when your team is scattered? How do you make sure remote engineers don’t get passed over for promotions just because they’re not visible? How do you avoid burning everyone out with constant video calls?
Here’s the good news. Research shows that specific practices can increase trust by 30% and achieve 91% fairness ratings in hybrid teams. These aren’t generic “have more meetings” suggestions. They’re engineering-specific practices that address code reviews, pair programming, async communication, and making your limited office time actually count.
In this article we’ll walk through what you need to know: team-determined schedules that prevent proximity bias, trust-building systems that work for distributed teams, and the documentation and communication practices that make hybrid engineering teams productive.
Proximity bias is when you unconsciously favour the people who are physically present in the office. It creates inequitable recognition and advancement opportunities, even when the quality of work is identical. This is one of the key challenges in navigating the office return context that many technical leaders face today.
96% of executives report noticing in-office contributions more than remote work. Think about what that means. You’ve got an engineer who ships solid features, writes clean code, and mentors juniors through thoughtful pull request reviews. But they work remotely. Meanwhile, someone else is in the office, visible at lunch conversations, present when architectural decisions get discussed informally. Guess who gets remembered at performance review time?
For engineering teams, proximity bias shows up predictably. Architectural decisions get made during office lunch conversations, excluding remote engineers. Technical leadership opportunities go to whoever was in the room. Code contributions from remote engineers get less attention during performance reviews.
The damage compounds. Initial bias in visibility leads to fewer opportunities, which reduces future visibility, creating a self-reinforcing loop. Not great.
The solution is implementing outcome-based evaluation and team-determined schedules. These approaches shift focus from physical presence to actual results.
Team-determined schedules mean your team collectively decides when members come to the office. Not individuals choosing for themselves. Not managers mandating attendance. The team decides together.
Research from Gallup shows this approach achieves a 91% fairness rating compared to just 73% when managers determine the schedule.
When the team decides together, no one gets penalised for location choices they didn’t control individually. The consistency in attendance patterns makes remote members’ schedules predictable, eliminating coordination headaches. And when everyone agreed to the schedule, you can’t claim someone is “not committed” for working remotely on agreed remote days.
Here’s how to implement it. Convene a team discussion about hybrid needs and preferences. Identify what collaborative work genuinely requires in-office time. Establish a trial schedule for 4-6 weeks. Review and iterate based on what you learn.
Self-determined schedules come with trade-offs. Employees with self-determined schedules are 76% more likely to report burnout as their greatest challenge and 57% more likely to report reduced work-life balance. Individual autonomy sounds great until coordination breaks down and everyone’s stressed.
Asynchronous communication is any method that doesn’t require simultaneous participation. Written code reviews. Design documents. Recorded demos. Slack messages that don’t expect immediate replies.
Shopify Engineering describes it as the glue holding distributed workforces together. It’s inclusive across time zones, creates an audit trail, and gives everyone the same window into what’s happening.
In physical offices, context gets gathered through osmosis. You overhear conversations. You see what people are working on. That doesn’t happen remotely. Async communication replaces osmosis with explicit, documented information sharing.
The shift to async means a shift to permanence. Conversations leave searchable records. Decisions get documented instead of lost. Future team members can understand why choices were made because the reasoning is written down. That’s a good thing.
For engineering workflows, async is a natural fit. Code review comments, pull request discussions, and technical RFC documents produce better outcomes than verbal approvals. The written format forces clarity.
GitLab’s approach is instructive. Optimise for high synchronous collaboration within teams and asynchronous communication between teams. Engineers on the same team should have overlap hours for discussions and pair programming. But communication with other teams can be async by default.
Common async tools include Slack for threaded discussions, GitHub or GitLab for code review, Notion or Confluence for documentation. The key is establishing team norms around response time expectations and where information lives.
Gallup research identifies four practices that together increase employee trust by nearly 30 percentage points.
Transparency in decision-making. Document why decisions were made, not just what was decided. Share decision criteria before decisions happen. Explain trade-offs considered, especially for architecture and technical direction.
Consistent communication cadence. Regular written updates at predictable intervals. No information surprises where remote team members find out about changes after the fact. The same information available to everyone regardless of location.
Equitable treatment. Outcome-based evaluation, not face-time assessment. Rotate tasks fairly across the team. Ensure remote members get the same opportunities for conference attendance, leadership roles, and high-visibility projects. When employees receive the same opportunities whether they’re remote or on-site, they feel more trusted.
Follow-through on commitments. Do what you say you’ll do. Respond to messages within stated timeframes. Implement agreed policies. Deliver promised resources. Broken commitments erode trust faster than any other factor.
All four together create a foundation of psychological safety. Run regular anonymous surveys asking about fairness perceptions, decision transparency, and manager reliability. If scores decline, you’ve got an early warning that trust is eroding.
Office time is limited in hybrid models. Use it for high-bandwidth collaborative activities that genuinely benefit from physical presence.
High-value in-office activities: architecture planning sessions that need whiteboarding, pair programming for complex problems, onboarding new engineers with hands-on mentoring, resolving complex technical conflicts.
Poor uses of office time: individual coding (better at home without interruptions), routine status meetings (more efficient async), administrative tasks.
When your team determines the schedule, explicitly identify what collaborative work happens on office days. Don’t just say “everyone in on Tuesday.” Say “Tuesday is for architecture planning and pair programming sessions.”
Avoid forced attendance without purpose. If you mandate office time but there’s no genuine collaborative value planned, you undermine trust. That breeds cynicism. For more guidance on implementing fair RTO policies that maintain team morale, consider how schedule decisions align with your broader workplace policy.
Research suggests 2-3 days per week provides balance for most hybrid teams. Prioritise quality over quantity.
Even on office days, accommodate remote members. Record whiteboard sessions. Document decisions in writing.
Code review is naturally an async activity. Embrace it.
The foundation is rich context in pull requests. Write detailed PR descriptions explaining why you made the changes, not just what changed. Include visual aids like screenshots and architecture diagrams. Give reviewers everything they need to understand the change without having to ask you questions.
Code reviews are valuable for spreading knowledge across the team. When one developer reviews another’s code, they learn about that feature area.
Set clear expectations. Define response time SLAs, like first response within 24 hours. Establish review thoroughness standards. Make these norms explicit so everyone knows what’s expected.
Distribute review load to avoid bottlenecks. Use GitHub or GitLab features for automatic reviewer assignment.
Keep review guidelines lightweight. Focus on design and logic issues, not nitpicking formatting. The goal is collaborative improvement, not gatekeeping.
You need five core categories. An async communication platform like Slack or Microsoft Teams. Code collaboration via GitHub or GitLab. A documentation wiki using Notion or Confluence. Video conferencing with Zoom. Project tracking through Linear or Jira.
For engineering teams specifically, you need code integration so Slack connects to GitHub. Search functionality for retrieving past discussions. Threading for technical conversations. High-quality screen sharing for pair programming.
Integration matters more than individual tool features. Notifications from GitHub appearing in Slack. Project updates linked to documentation. When tools work together, workflows are seamless.
Common mistakes: using too many tools, creating fragmented communication. Poor adoption because tools are too complex. Missing integrations that force manual work.
GitLab’s principle is instructive. Choose a single system for communicating project progress. If it’s not in an epic, issue, or merge request, it doesn’t exist.
Focus on outcomes, not activity. Features shipped, bugs resolved, incidents prevented. Results matter. Presence doesn’t.
Avoid surveillance entirely. No keystroke logging. No screen monitoring. No time tracking. These tools erode trust faster than any metric improves performance.
The DORA framework provides validated metrics: deployment frequency, lead time for changes, change failure rate, and mean time to recovery. These measure team effectiveness without individual surveillance.
The DX Core 4 consolidates DORA, SPACE, and DevEx frameworks into four balanced dimensions: speed, effectiveness, quality, and impact. Companies like Booking.com quantified a 16% productivity lift from AI adoption using these metrics.
Don’t measure lines of code or raw ticket counts. These are easily gamed. An engineer who refactors a complex module might delete more lines than they add while creating significant value.
Teams that feel trusted are more productive. Measurement should inform improvement, not create fear.
You can’t rely on over-shoulder learning in hybrid teams. Documentation and structure become critical.
Start with comprehensive documentation covering architecture, development setup, deployment processes, and team norms.
Assign an explicit buddy. Make one person responsible for daily check-ins, code review learning, and answering questions.
Schedule overlap time for the first 2-4 weeks. Early-career engineers especially struggle with fully remote onboarding. They need synchronous time to ask questions and get immediate feedback.
Use progressive integration. Start with well-scoped starter tasks that let new hires contribute without needing to understand the entire system.
Have new hires document the setup process as they go through it. They’ll identify gaps in your documentation that you’ve become blind to.
Knowledge transfer should be ongoing, not a one-time dump. The smoother your process, the faster new hires become productive.
Architecture Decision Records (ADRs) are the foundation. An ADR documents why technical decisions were made, the context at the time, and alternatives considered. This replaces verbal tribal knowledge that disappears when people leave.
Each ADR should include: title, status, context, decision, and consequences. Store ADRs with the codebase or in a searchable wiki.
Runbooks and playbooks document operational procedures, incident response, and deployment processes. These enable self-service without asking teammates who might be asleep in a different time zone.
Every meeting should produce documented outcomes, decisions, and action items. No verbal-only decisions. GitLab’s rule is strict. Any side conversation gets documented in the agenda, and useful elements get ported to relevant issues or merge requests.
Code comments and README files provide context in the repository itself. Document team norms and processes. Make implicit expectations explicit.
Organise your knowledge base with searchable structure. Prune outdated content regularly. Outdated docs are worse than no docs because they mislead people.
The effort-value balance matters. Not everything needs documentation. But anything architecturally significant should be documented. Ask yourself: will someone six months from now need to understand why we made this choice? If yes, document it.
Set clear work-hour boundaries. No expectation of 24/7 availability. Async-first communication reduces pressure to respond immediately.
Model work-life balance by not sending messages outside work hours. If you’re working late, schedule messages to send during business hours so you’re not creating pressure for your team.
Monitor workload distribution. Watch for overwork signals like late-night commits and weekend work. Address it in 1:1s before burnout happens.
Return to team-determined schedule principles. Identify what collaborative work genuinely requires in-office time.
Find overlapping days that work for the majority. Respect genuine conflicts like childcare and long commutes.
Trial the schedule for 4-6 weeks then iterate. Treat it as an experiment, not a permanent decree.
Generally 2-3 days per week provides balance. Some teams succeed with 1 day weekly.
Prioritise quality over quantity. One well-planned office day beats three days of people working individually at desks.
Yes. You need proper tools and practices, but remote pairing works.
High-quality screen sharing with low latency is necessary. IDE plugins for collaborative editing like VS Code Live Share help.
Rotate pairs to spread knowledge. Some pairs find remote pairing more focused than in-office because there are fewer distractions.
Document all decisions in writing. No verbal-only decisions.
Use threaded Slack or Teams conversations for team-relevant discussions instead of DMs.
Record meetings and share notes. Use explicit @mentions for important updates. Centralise reference information in a wiki so people can find it when they need it.
Self-determined: individuals choose their own office days. This maximises personal flexibility but creates coordination challenges.
Team-determined: the team collectively decides the schedule. This achieves 91% fairness ratings versus 73% for manager-determined schedules.
Self-determined schedules are 76% more likely to report burnout as the greatest challenge and 57% more likely to report reduced work-life balance.
Async-first communication reduces real-time dependency. Distributed teams rely heavily on detailed design documents and recorded meetings.
Identify overlap hours for time-sensitive discussions. Use those hours strategically.
Rotate meeting times to share inconvenience fairly. Use recorded demos instead of live presentations.
Establish response time expectations of 24-48 hours rather than immediate replies.
Thriving signals: consistent deployment frequency, low change failure rate, improving cycle times, high code review engagement, positive retrospective feedback.
Struggling signals: increasing deployment intervals, quality issues rising, missed deadlines, low pull request activity, declining attendance, turnover increasing, fairness scores dropping.
Track DORA metrics at the team level: deployment frequency, lead time, change failure rate, and mean time to recovery.
Start with a team discussion of hybrid vision and concerns.
Audit and improve documentation. Co-located teams often have poor documentation because they rely on verbal communication.
Establish a team-determined schedule through collaborative planning. Select async communication tools.
Run a trial period of 8-12 weeks with regular retrospectives. Resist reverting to office-first habits like verbal decisions.
Generally yes, especially aligning with team-determined office days.
Asymmetric schedules create proximity bias risk. If you’re more accessible to office workers than remote workers, remote team members are at a disadvantage.
Communicate your schedule explicitly. Ensure remote accessibility during your remote days.
Plan intentional social time during office days. Team lunches, coffee breaks.
Virtual social activities for remote days, but make them optional. Forced fun creates resentment.
Celebrate wins in public channels. Set up social channels to spotlight interests and talents. The stronger the community, the stronger the collaboration.
Team retrospectives build trust through process improvement.
Team-determined schedule framework and process. Communication response time SLAs. Meeting guidelines: video on, recordings shared, notes documented.
Outcome-based evaluation criteria making it clear you assess results, not presence. Documentation requirements for decisions.
Work-hour boundaries and availability expectations. Office space booking process if needed. Expense policies for home office equipment.
Trial period and review process for policy iteration. Create clear expectations for remote work quality. For comprehensive guidance on fair enforcement and communication strategies, ensure your policy addresses both technical requirements and team morale considerations.
How RTO Mandates Affect Employee Retention and Why Top Performers Leave FirstReturn to office mandates have created a talent retention crisis, and the numbers aren’t pretty. 80% of companies that implemented RTO policies experienced employee departures.
Here’s what’s really happening: High performers are 16% more likely to have low intent to stay when you force them back to the office. You’re losing your best people—the ones you can’t afford to lose. And there’s this massive preference gap nobody seems to want to talk about: 64% of employees want flexibility whilst only 27% prefer full-time office work. Yet executives keep mandating returns anyway.
The costs? They’re quantifiable and brutal. Each departure costs you 50-200% of annual salary. Your hiring timelines stretch out by 23%. And you’re fishing in a talent pool that’s 60% smaller than your competitors who offer flexibility. Meanwhile, smaller companies with flexible policies are going head-to-head against larger competitors with deeper pockets—and they’re winning.
This analysis is part of our comprehensive look at RTO mandates in 2025, exploring how these policies reshape workforce dynamics and competitive landscapes.
80% of companies that implemented RTO mandates experienced talent loss. Let that sink in. Four out of five companies that forced people back saw employees walk out the door.
It gets worse when you look at who’s leaving. Companies are seeing 17% higher departure rates among senior employees specifically—the people with institutional knowledge, client relationships, and mentorship capacity.
And this isn’t just people quietly updating their LinkedIn profiles. 76% of workers state they would actively job hunt if their remote work arrangements were removed. That’s three-quarters of your workforce ready to bail. 27% personally know someone who quit specifically because of an RTO mandate.
Look at what happened to the big players. SpaceX saw a 15 percentage point decline in senior workforce share after their RTO push. Microsoft and Apple experienced 4-5 percentage point declines in senior employees. At Amazon, 91% of employees were dissatisfied with the RTO mandate.
The pattern is consistent across industries: the more restrictive your mandate, the higher your talent loss. Amazon’s sixth policy revision—each one more restrictive than the last—shows you what happens when companies double down on failing strategies.
Gartner research documents that high performers have a 16% higher likelihood of low intent to stay under RTO mandates. Stanford economist Nicholas Bloom doesn’t mince words: “You’re going to get negative selection. The ones who leave are the ones that can pull an outside offer, who are the better employees”.
It’s simple economics. Top performers have options. They’re the least captive audience for unwelcome policy changes. Here’s a telling stat: Remote job listings represent only 15-20% of available positions but attract 60% of all applications. Your best people know they can find remote work elsewhere.
Autonomy and trust matter to high achievers. An RTO mandate signals you don’t trust them. 76% of high performers report improved work-life balance with remote work, and 61% experience less burnout. They proved their productivity during the pandemic. Forcing them back to the office feels like micromanagement, because it is.
Geographic arbitrage appeals most to high earners. A $150K Silicon Valley salary provides equivalent buying power to $200K+ in Austin or Nashville. And remote-first companies actively recruit these departing top performers, positioning flexibility as their key competitive advantage.
There’s a leadership pipeline problem brewing too. Companies enforcing strict RTO are struggling to fill management roles because the next generation of leaders actively seeks hybrid and remote-friendly organisations. You’re not just losing talent now—you’re losing your future leadership bench.
Turnover costs range from 50-200% of an employee’s annual salary. For a mid-level developer earning $120,000, you’re looking at replacement costs running $60,000-$240,000.
Recruiting expenses alone increase by $5,000-$15,000 per hire for RTO-mandating companies. Your time-to-hire extends by 23% compared to remote-friendly competitors. That’s nearly a quarter longer to fill critical roles.
Lost productivity compounds over 6-12 months. You’ve got notice periods, handover time, vacancy periods, and new hire ramp-up. Institutional knowledge from senior departures carries hidden costs—tribal knowledge about systems, client relationships, mentorship capacity. You can’t easily replace that.
Do the maths. If RTO causes 10 departures from a 100-person team, your total impact hits $600,000-$2.4 million.
Meanwhile, companies offering flexibility experience turnover reduction of 25-35%. That translates directly to cost savings you can measure.
64% of US employees would prefer remote or hybrid roles. Only 27% prefer full-time office work. That’s a 37 percentage point gap between what most workers want and what RTO mandates require.
Now look at the executive perspective. 83% of CEOs expect employees to be back in the office full-time within the next three years. Only 10% of Fortune 500 companies have actually achieved this. That 73-percentage-point gap between CEO predictions and current reality tells you something: executive preferences don’t align with market forces.
Here’s the disconnect in a nutshell: 64% of companies cite improved productivity as their reason for RTO, yet Stanford research shows hybrid work has zero negative productivity impact. The gap reflects different priorities. Executives value collaboration and culture. Employees prioritise flexibility and work-life balance.
And it gets dodgier. 25% of executives and 18% of HR professionals admit hoping employees would voluntarily leave due to RTO. That’s quiet firing, plain and simple.
67% of companies under 500 employees offer full remote work compared to only 10% of Fortune 500 firms. That 57 percentage point difference is a genuine competitive weapon for smaller companies with tighter budgets.
SMBs can now access top talent departing from Amazon, Google, Meta, and other RTO-mandating giants. Former Meta senior engineers now lead product development at 50-person fintech startups. Ex-Amazon principal architects have joined healthcare AI companies as CTOs.
One startup CEO nailed it: “We can’t compete with Google’s salary packages, but we can compete with Google’s flexibility. And right now, flexibility is winning”.
The numbers back this up. Among Fortune 100 companies, 54% now require full-time office presence—up from just 5% in 2023. Small companies can recruit from anywhere whilst large competitors restrict themselves to expensive local markets.
Senior employees carry 5-15 years of tribal knowledge about your systems, customers, and organisational history. High performers typically mentor 3-5 junior team members each. When they leave, you’re multiplying the impact of their departure across the organisation.
Team morale takes a quantifiable hit. Remaining employees watch top performers exit. They question their own future. They start passive job searches. Teams experiencing high cognitive load show 76% correlation with burnout rates and 68% correlation with turnover intention.
Then you get cascading departures. Initial exits trigger further turnover as teams fragment and projects lose momentum. It’s a domino effect you can’t easily stop.
Stanford research shows that hybrid work—2-3 days remote per week—produces zero negative productivity impact and reduces turnover by 33% compared to full-time office requirements.
Currently, 67% of companies offer some form of hybrid flexibility. 75% of small and mid-sized business leaders have a hybrid workforce, 18% are fully in the office, and 7% are fully remote.
Results speak louder than mandates. Spotify’s structured hybrid model reduced attrition by 50%.
Employee satisfaction with hybrid depends heavily on implementation. There’s a difference between mandatory fixed days versus flexible team-determined schedules. Here’s the friction point: Most workers prefer 2-3 office days per week, but companies typically require 3-4 days.
Best-practice hybrid maintains outcome-based performance management rather than badge tracking or presence monitoring. For detailed guidance on retaining engineers through effective hybrid management, building trust and avoiding proximity bias prove essential.
University of Pittsburgh researchers tracked 3 million LinkedIn profiles and found firms implementing RTO mandates take 23% longer to fill open positions. Geographic talent pool restrictions eliminate 50-60% of potential candidates before you even start.
The application volume tells the story. Remote job postings receive 60% of all applications despite representing only 15-20% of job listings. 46% of qualified candidates won’t even apply to jobs requiring full-time office presence.
For specialised technical roles, location requirements can reduce your candidate pool by 80%+ in smaller markets.
Each additional day a role remains unfilled costs companies 0.3% of the position’s annual salary. The quality gap compounds the time gap. Your best candidates have multiple offers and they’re choosing remote-friendly employers.
If you’re implementing new work location policies, understanding how to implement RTO policies fairly can minimise talent loss and preserve team trust throughout transitions.
Millennials show the strongest resistance to RTO with 41% extremely likely to leave if forced back to office full-time. Gen Z presents more nuanced preferences with 65% favouring hybrid models that offer some office interaction alongside flexibility. The generational divide reflects different life stages—Millennials often juggle families and caregiving responsibilities whilst Gen Z values collaboration opportunities for career development. Both generations prioritise work-life balance significantly more than previous cohorts did.
The productivity data is genuinely mixed, not the clear-cut story either side wants. Stanford research shows zero negative productivity impact for hybrid arrangements (2-3 days remote). 56% of employees who prefer remote work feel they are more productive working from home. But 39% of workers accomplish less in the office because of socialising with coworkers. The real variable appears to be management quality and outcome-based evaluation rather than work location itself. Funny thing is, 64% of companies cite improved productivity as their reason for RTO—they’re often conflating visibility with actual output.
Hybrid policies offering 2-3 days remote per week represent the most common alternative, adopted by 67% of companies offering flexibility. Team-determined flexible schedules—where groups coordinate their own office days—perform better than mandatory fixed-day requirements. Outcome-based performance management eliminates presence monitoring in favour of deliverable-focused evaluation. Office-optional models where workspace is available but not required provide maximum flexibility. Seasonal or project-based office requirements give you collaboration benefits without daily mandate burdens.
BambooHR research reveals 25% of executives and 18% of HR professionals admit hoping employees would voluntarily leave due to RTO policies. This suggests quiet firing is more widespread than companies publicly acknowledge—it’s not just a few bad actors. This stealth layoff strategy avoids severance costs and legal risks of formal redundancies. The tactic backfires spectacularly by losing the most marketable employees (high performers with options) whilst retaining those with fewer alternatives.
34% of businesses have implemented attendance monitoring systems using employee ID card swipes to track office presence. Badge tracking creates resentment by signalling you don’t trust your people. You’re treating employees as children requiring supervision rather than professionals accountable for outcomes. The approach measures compliance rather than productivity, creating perverse incentives where employees optimise for swipe times rather than actual work quality. 88% of remote workers and 79% of in-office workers feel they need to prove they’re being productive. That’s not healthy.
High performers with 5+ years experience show the highest flight risk (16% more likely to have low intent to stay). Millennials aged 32-42 with family responsibilities demonstrate 41% extremely likely to leave ratings. Employees who relocated during the pandemic to lower-cost areas face impossible choices between job loss and expensive moves back to urban centres. Those with specialised skills in high demand have the most labour market options and least tolerance for unwelcome mandates.
Meta, Google, and Apple reduce salaries for employees relocating to lower-cost areas. This diminishes but doesn’t eliminate the financial advantage—a $130,000 Nashville salary still provides better purchasing power than $150,000 in San Francisco after cost-of-living adjustment. Location-agnostic pay offered by some SMBs and remote-first companies becomes a competitive differentiator. The policy creates resentment when employees perform identical work for different pay based solely on location.
Hybrid team management requires async communication proficiency—documentation, recorded meetings, clear written updates. You need outcome-based performance evaluation skills to replace presence-based management instincts. Equity maintenance across distributed team members prevents office workers gaining visibility advantages over remote colleagues. Trust-building without physical proximity demands intentional relationship investment. Meeting facilitation needs adapting for hybrid contexts to prevent conference room participants dominating over video participants.
19.6% of departing tech workers move to professional services firms, 8.6% to financial services. Many join SMBs and startups offering full remote work (67% of sub-500 employee companies). Remote-first competitors actively recruit from RTO-mandating firms, positioning flexibility as their key differentiator. Geographic relocation patterns show movement from expensive tech hubs to mid-tier cities that offer remote opportunities.
Turnover rate comparison with 50-200% salary replacement cost calculations. Time-to-hire measurements for remote-friendly versus location-restricted positions. Quality-of-hire assessments comparing candidate pools with geographic restrictions versus open access. Real estate cost savings from reduced office space requirements (San Francisco: $87/sq ft annually). Productivity metrics focused on deliverables and outcomes rather than presence indicators. Employee engagement scores and retention rates specifically among high performers.
San Francisco shows 28.8% office vacancy rate, Bay Area overall 26.4%, Seattle 26.3%, Denver 24.7% despite aggressive RTO mandates from major employers. These elevated vacancy rates suggest companies are maintaining expensive real estate whilst employees resist full-time returns. The sunk cost of office leases creates political pressure for RTO mandates to justify the expense rather than genuine productivity requirements.
Disparate impact claims emerge when RTO policies disproportionately affect protected classes—parents, disabled workers, older employees with caregiving responsibilities. Constructive dismissal lawsuits arise when policy changes create intolerable working conditions forcing resignations. Disability discrimination claims from employees with mobility challenges or immune compromises. Gender discrimination patterns where RTO disproportionately impacts women with caregiving responsibilities (74% of HR professionals report leadership conflicts over policies). Documentation of executive quiet firing admissions creates legal liability evidence.
For comprehensive coverage of office return policies, including executive motivations, productivity evidence, and implementation strategies, explore our complete guide to navigating the RTO landscape in 2025.
Remote Work vs Office Productivity – What Research Actually Shows About Where Work Gets DoneYou’ve heard the arguments. CEOs want everyone back in the office. Staff threaten to quit if forced back. Every day brings a new headline contradicting yesterday’s. Everyone’s got an opinion based on whatever anecdote fits their view.
But as you’re deciding on work arrangements for your engineering team, opinions aren’t going to cut it. You need data.
The good news? There’s comprehensive research from Stanford, Gallup, and the Bureau of Labor Statistics that actually gives us some clarity. The findings are more nuanced than the shouty debate suggests, but there’s a pattern—trust, not location, drives productivity.
As part of the broader return-to-office landscape in 2025, the productivity debate has become central to decisions about where and how teams work. Let’s get into what the research actually says.
Stanford found hybrid workers are just as productive as office workers, with 33% lower turnover. That’s significant. When you factor in the cost of recruiting and onboarding replacements, that’s real money.
Nicholas Bloom’s multi-year study tracked the same workers over time instead of taking snapshots. The result? No productivity drop when remote work has the right support—the right tools, clear accountability, and outcome-based measurement.
76% of remote and hybrid workers report improved work-life balance according to Gallup. Three-quarters of your team getting tangible benefits. That’s not nothing.
Organisations that invested in collaboration tools and outcome-based performance metrics are seeing 40% productivity gains in remote settings. The companies struggling? Still managing by looking over shoulders and counting hours.
What makes the difference? Three things: trust between managers and teams, outcome-based measurement instead of time-based surveillance, and intentional communication frameworks. Miss any of those and your remote arrangement will struggle.
Here’s the problem: only 54% of managers trust remote teams to be productive according to Gallup.
Nearly half of all managers don’t believe their team is working unless they can see them. That’s a management problem, not a remote work problem. This trust gap drives many of the return-to-office mandates we’re seeing across the industry.
The data backs this up. 88% of remote workers feel pressure to prove productivity. 64% keep their chat status green even when not working. Low trust creates performative availability instead of actual output.
High-trust environments enable outcome-based measurement. You focus on deliverables, sprint velocity, code quality, project milestones. Low-trust environments drive surveillance and micromanagement. You get monitoring software, excessive check-ins, and people optimising for looking busy instead of being productive.
Companies that build high-trust cultures drive substantial business impact with remote work. Companies that can’t build trust struggle no matter where people sit.
Building trust takes time. You need to shift from evaluating hours worked to evaluating output delivered. You need clear accountability frameworks. You need consistent results that demonstrate remote teams deliver.
Many managers struggle because they’re used to visual oversight. Walking past someone’s desk and seeing them at their computer feels like confirmation they’re working. It isn’t, but it feels that way. Outcome-based evaluation requires actually looking at results. Managing engineering teams in hybrid work environments requires intentional frameworks that build trust through transparency rather than surveillance.
If you don’t trust your team to work without constant supervision, you’ve got a staffing or management issue. Changing physical location won’t fix it.
The data on hybrid work shows stability. Gallup’s Q2 2025 research shows 51% of remote-capable employees work hybrid. That number has held steady since 2022. It’s a new baseline, not a temporary adjustment.
Hybrid workers now spend 46% of their workweek in the office—about 2.3 days. That’s up slightly from 42% in 2022, but the pattern holds: most people split their time.
The productivity comparison is interesting. Hybrid workers match office workers on output but show 33% lower turnover. Office workers? 39% say they accomplish less in the office because of socialising.
Schedule autonomy matters. The percentage of employees who say their hybrid schedule is “entirely up to me” declined from 37% in 2024 to 34% in 2025. More companies are mandating specific office days instead of letting teams self-organise.
Self-determined schedules outperform employer-mandated schedules on both satisfaction and retention. When you tell people exactly which days to come in, you’re optimising for management comfort instead of team effectiveness.
Most workers prefer 2-3 office days per week, but companies typically require 3-4 days. This gap creates friction.
The optimal split appears to be 2-3 office days for most tech teams. More important than the exact number is who decides. Teams that choose their own office days outperform teams following arbitrary mandates.
The shift is from time-based metrics—hours worked, attendance, time at desk—to output-based metrics—what got shipped, quality of work, project milestones hit.
For engineering teams, track sprint velocity, deployment frequency, code quality metrics, pull request throughput, and project completion rates. These are the DORA metrics high-performing teams already use: deployment frequency, lead time for changes, change failure rate, and mean time to recovery.
The predictable mistake: companies that can’t trust remote teams turn to surveillance software. This correlates with lower trust and negative outcomes. Monitoring activity isn’t measuring productivity—it’s signalling distrust.
Companies using workforce analytics tools had 20% higher productivity rates than those relying on traditional management methods according to Gartner. The difference? Analytics tools measure outcomes and identify inefficiencies. Traditional methods measure presence and assume correlation with productivity.
Avoid basic measures like lines of code or raw ticket counts. These create perverse incentives.
Establish a baseline. Track your team’s productivity metrics in the original environment, then measure the same metrics after implementing remote or hybrid work.
Track leading indicators alongside lagging ones. Engagement scores, collaboration frequency, and knowledge sharing predict future productivity. If those are trending down, you’ll see it in deliverables later.
Pick metrics that align with your business goals, make them transparent, and evaluate everyone using the same standards regardless of location.
76% of remote and hybrid workers experience improved work-life balance. 61% experience less burnout or fatigue.
The mechanism is straightforward. Most people commute at least an hour daily. Remote work gives that time back. They sleep better, exercise more, spend more time with family, and have more control over their day.
Better wellbeing drives higher engagement. Higher engagement drives better retention. Companies offering flexibility see 25-35% turnover reduction.
But remote work can create burnout if you implement it poorly. Without clear boundaries, remote work becomes always-on work. Without the physical separation of office and home, some people struggle to disconnect.
The difference is autonomy and boundaries. When people control their work hours and have clear expectations about availability, burnout decreases. When remote work means being available 24/7 because you’re “always home anyway,” burnout increases.
75% of caregivers say flexibility helps them manage work and home. Caregivers are a substantial portion of your team—people dealing with childcare, elder care, or other responsibilities that don’t fit 9-to-5 office schedules.
The data on workers with disabilities is particularly stark. 63% prefer working remotely. 42% would consider leaving if forced back to office. For many people, remote work makes employment viable.
The wellbeing benefits translate to performance. When people control their time, they produce better work.
84% of remote workers report feeling more productive, but nearly half run into collaboration challenges. Individual productivity often goes up while collaborative friction sometimes goes up too.
The office provided spontaneous interactions. You’d overhear a conversation, jump in with a solution. Remote work requires being more intentional. You need documentation culture and structured collaboration time.
The key is optimising your mix of synchronous and asynchronous work.
Optimise for synchronous communication inside teams, asynchronous communication outside teams. Engineers within a team should have overlapping hours for real-time collaboration. Communication between teams should default to asynchronous—detailed documentation, recorded meetings, written updates.
Hybrid models can optimise for both. Use remote days for concentrated work. Use office days for workshops, planning sessions, architecture discussions.
Over 40% of hybrid employees feel disconnected from fully remote teammates. This requires active management. Proximity bias can develop where office workers get more context and remote workers get left out. Building trust and productivity in hybrid teams means deliberately counteracting these patterns.
Strong documentation drives down the number of meetings needed between teams. Innovation depends more on team practices than physical proximity. Psychological safety and experimentation culture drive innovation more than location.
The business case for flexibility is compelling.
67% of companies under 500 employees offer full remote work versus only 10% of Fortune 500 firms. Small companies worked out they could recruit from anywhere, not just their local metro. This gives them access to talent that would never relocate.
Companies enforcing return-to-office mandates face 23% longer hiring timelines, pay $5,000-$15,000 more per hire, and access only 40% of the available talent pool.
Remote job postings are 15-20% of available positions but attract 60% of all applications.
Workers with hybrid schedules were 33% less likely to resign than full-time office workers. 76% of companies experience greater retention by allowing remote work.
The cost of replacing someone ranges from 50-200% of their annual salary. A third fewer departures is substantial money saved.
RTO mandates correlate with talent loss. 80% of companies reported losing talent because of RTO mandates. High-performing employees are 16% more likely to have low intent to stay if they face an RTO mandate.
High performers leave first because they have the most options. Tech companies with RTO mandates lose 15 percentage points of senior workforce share.
Remote-first companies save $10,000-$15,000 per employee annually on office space, utilities, and facilities. Even hybrid arrangements let you right-size office space, typically reducing space needs by 50-70%.
Only 10% of Fortune 500 companies have achieved full return-to-office despite 83% of CEOs predicting this outcome. The gap between executive expectations and actual outcomes reflects current RTO trends and talent market dynamics.
It depends on how you implement it, not just location. Stanford’s hybrid study found equal productivity with 33% better retention. Success requires trust, proper measurement, and intentional collaboration frameworks. 56% of employees who prefer remote work report being more productive at home.
Focus on output-based metrics instead of surveillance. Track deliverables, sprint velocity, code quality, and project milestones. Surveillance tools correlate with lower trust and negative outcomes, while outcome-based measurement drives better performance.
Gallup research identifies this trust gap as the main barrier. Managers accustomed to visual oversight struggle with outcome-based evaluation. Building trust requires shifting from time-based to output-based metrics, establishing clear accountability, and demonstrating consistent results over time.
Research suggests 2-3 office days per week optimises collaboration benefits while maintaining flexibility. More importantly, self-determined schedules outperform employer-mandated schedules significantly. Give teams autonomy in choosing their office days based on collaboration needs.
Yes. RTO mandates correlate with increased talent loss, especially high performers with in-demand skills. 80% of companies reported losing talent because of RTO mandates. High-performing employees are 16% more likely to have low intent to stay if they face RTO mandates.
Less burned out. 76% report improved work-life balance in remote/hybrid arrangements. 61% experience less burnout or fatigue. Burnout risk decreases with autonomy, clear boundaries, and right-to-disconnect policies. It increases when remote work means always-on expectations without boundaries.
Collaboration changes rather than necessarily declining. Spontaneous collaboration decreases, but planned collaboration can improve with intentional frameworks. Hybrid models optimise both: deep focused work remotely, collaborative sessions in office. Documentation culture becomes critical.
Bureau of Labor Statistics data shows no systematic productivity decline with properly implemented remote work. Stanford research found productivity parity for hybrid arrangements. Organisations with collaboration tools and outcome-based metrics see 40% productivity gains in remote settings.
Shift from time-based metrics (hours worked) to output-based metrics (deliverables completed). Use sprint velocity, code quality, deployment frequency, project milestone completion, and customer satisfaction. Track engagement and collaboration as leading indicators of future productivity.
67% of companies under 500 employees offer full remote work versus only 10% of Fortune 500 firms. Remote-first companies save $10,000-$15,000 per employee annually. Companies offering flexibility see 25-35% turnover reduction. Workers with hybrid schedules were 33% less likely to resign.
Positive impacts include eliminated commute stress (1+ hour daily returned), better sleep, more family time, and improved physical health. Negative risks occur without boundaries or with always-on expectations. 76% of remote/hybrid workers report improved work-life balance. 61% experience less burnout.
Innovation depends more on team practices than physical proximity. Intentional collaboration frameworks, psychological safety, and documentation culture drive innovation. 84% of remote workers report feeling more productive, but nearly half face collaboration challenges requiring deliberate solutions.
The productivity debate around remote work isn’t simple, but the research points to a clear pattern: outcomes depend more on trust and management practices than physical location. As the return-to-office landscape continues to evolve, the evidence suggests that flexible work arrangements can deliver strong productivity when implemented with outcome-based measurement, intentional collaboration, and high-trust cultures.
Why Companies Are Forcing Return to Office – The Real Reasons Behind RTO MandatesReturn-to-office mandates are reshaping workplaces in 2025. Amazon, JPMorgan, and Google are requiring employees back in offices. Ask the executives why and they’ll tell you it’s about collaboration (68%), productivity (64%), and company culture (61%).
But here’s the thing. Research from KPMG found 25% of executives admitted they hoped RTO would trigger voluntary departures. Gartner research shows no measurable productivity gains from RTO mandates, whilst Gallup reports employee engagement at 10-year lows.
The stated reasons don’t match the actual outcomes. So what’s really going on? This article examines the motivations behind RTO mandates as part of our comprehensive guide to the return-to-office landscape in 2025, digging into both the official justifications and the hidden economic pressures driving these decisions.
68% of executives cite collaboration as the primary reason for RTO. 64% say productivity. 61% claim communication. Those are the talking points. But when you look at what the research actually says, you get a different picture.
25% of executives explicitly hoped RTO would cause voluntary departures. Another 18% of HR workers admitted the same thing. This is the passive layoff strategy in action—cutting headcount without paying severance or dealing with the bad publicity that comes with actual redundancies.
Then there’s commercial real estate. Office utilisation remains at 50-65% of pre-2019 levels despite 80% of companies having RTO policies. Companies are paying for space nobody’s using.
Here’s an interesting data point. S&P 500 companies were more likely to roll out RTO mandates after stock prices dropped. That’s cost cutting, just through the back door.
And of course there’s management preferences. Some executives simply want visibility and control despite evidence that remote teams can be measured objectively. They’re choosing what makes them comfortable over what actually works.
The numbers tell the story. 90% of large employers now have RTO policies. 83% of CEOs expect employees back in offices full-time within three years. As we explore in our overview of return-to-office trends, these mandates are rolling out for reasons that have very little to do with the official explanations.
One in four. 25% explicitly acknowledged hoping for voluntary attrition through RTO mandates. That’s executives admitting out loud what the strategy really is.
This is how the passive layoff works. You implement an unpopular policy. You wait for people to quit. You avoid severance packages, WARN Act notifications, and the bad press that comes with actual layoffs.
And it works because remote work is valued as equivalent to 8% of salary on average. For tech workers, that figure reaches 25%. When you force people back to offices you’re effectively cutting their compensation. Some will leave rather than accept the pay cut.
The strategy shifts the “choice” to employees, which reduces company liability. They’re not laying people off—people are choosing to leave. Legally and optically, that’s cleaner.
But here’s the problem with this strategy. It loses your best people. High-performing employees are 16% more likely to have low intent to stay when facing an RTO mandate. They have options. They can find remote positions elsewhere. And they do.
That 25% admission rate is probably understated. That’s just executives willing to say it out loud.
And the cost? Replacing an employee costs six to nine months of their salary. When you lose senior technical talent, you’re also losing institutional knowledge and team velocity. The passive layoff strategy might cut immediate costs, but it damages long-term capability.
Studies show inconclusive evidence that five-day office policies improve business performance. That’s research-speak for “it doesn’t work.”
Gartner found companies using workforce analytics tools had 20% higher productivity rates than those relying on traditional management methods. Notice what drives that difference—it’s about measurement approach, not location.
Stanford research on hybrid work (2-3 days remote) shows zero negative effect on performance metrics. Employee resignations dropped 33%. That’s hybrid work improving both productivity and retention.
Now, fully remote work can get complicated. Studies show 10-20% productivity decline compared to office work, primarily from communication challenges. But here’s where it gets interesting. Well-managed remote arrangements achieve 13-47% productivity increases through improved focus and reduced distractions.
The difference between those two outcomes? Management quality, not location. Companies with strong remote work infrastructure see productivity gains. Those with poor remote management see declines.
Look at what actually works. Microsoft and Dropbox redesigned workforce models to prioritise deep work and strategic collaboration rather than tracking hours. Atlassian measures productivity through structured goal setting and data-driven accountability—not attendance. Spotify’s flexible hybrid model saw 50% reduction in attrition.
The companies improving performance aren’t forcing employees into offices. They’re optimising how work actually gets done.
It’s pretty straightforward. Companies implement unpopular policies expecting employees will resign rather than comply. And it works. Research shows 20-30% attrition rates following strict RTO announcements.
This avoids all the costs of formal layoffs. No severance payments. No WARN Act compliance. No unemployment insurance increases. It’s economically attractive, even if ethically questionable.
Here’s how companies enforce it. 47% of companies requiring five-day schedules plan to terminate or discipline non-compliant employees. 34% implemented badge tracking and attendance monitoring. 32% factor in-office attendance into performance evaluations. 29% consider office presence for promotions and pay increases.
What this creates is selective enforcement. Companies can use policy compliance as de facto performance management. Don’t like someone’s work? Enforce badge compliance strictly. Want to keep a high performer? Be flexible about their schedule.
But the strategy has a problem. It disproportionately affects high performers because they have better employment options and more remote work alternatives. Rigid mandates drive away the best employees, which is the opposite of what you want during a workforce reduction.
The trend is accelerating too. 37% of companies are enforcing office attendance in 2025, up from 17% in 2024. More companies are choosing this strategy despite the risks.
Big numbers here. US office vacancy rates peaked at 19.8% by end-2024, up from 12% pre-pandemic. San Francisco hit 28.8%. Bay Area: 26.4%. Seattle: 26.3%. That’s a lot of empty, expensive space.
Companies hold long-term lease obligations. They’re paying for space nobody’s using.
Manhattan office space averages $87 per square foot annually. For 1,000 employees at 150 square feet per person, that’s $13 million annually. That’s real money showing up on balance sheets.
Now compare that to attrition costs. Replacement costs run 50-200% of annual salary. Lose 200 employees averaging $150,000 salary? That’s $15-60 million in replacement costs.
The maths doesn’t support RTO mandates. But corporate real estate shows up as an asset on balance sheets. Underutilisation affects valuations. That creates pressure that has nothing to do with productivity.
And the mandates aren’t even working. National office vacancy rates remain at 19.7% as of March 2025, unchanged despite all these RTO policies. The mandates aren’t filling offices. They’re just losing employees.
Here’s the opportunity cost. Allowing remote work could save $10,000-15,000 per employee annually in office space, $2,000-5,000 in utilities, and $1,000-3,000 in parking and amenities. That’s $13,000-23,000 per employee per year in savings.
But economic pressure to justify real estate commitments outweighs productivity and retention data. That’s what’s really driving these decisions.
The attrition numbers are significant. 20-30% of employees are willing to quit rather than comply with strict RTO mandates. And high performers disproportionately leave.
80% of companies reported losing talent because of RTO mandates. At Amazon specifically, 91% of employees were dissatisfied with the RTO mandate. 73% indicated they would consider leaving if forced into office full-time. Those are terrible retention numbers.
Companies with strict RTO had 13% higher turnover—169% versus 149%. They were twice as likely to say turnover increased. The correlation is clear.
The talent market tells the same story. Remote job listings made up only 15% of openings but attracted 50% of applications. That’s massive demand concentration. McKinsey reports the most in-demand professionals—engineers, analysts, senior executives—actively seek remote-first or hybrid environments.
The demographic breakdown matters too. Gallup found engagement levels dropped most among employees under 40—the exact demographic companies rely on for leadership succession. You’re losing future leaders.
And it’s affecting wellbeing. Remote and hybrid workers report 20% higher happiness levels compared to office-only workers. 85% report improved work-life balance. Engagement rates are 54% higher among employees with remote options.
Companies that offer flexibility see 25-35% turnover reduction. That’s the flip side—flexibility as a retention tool.
Companies implementing RTO are losing competitive advantage in talent markets where flexibility is becoming standard. The long-term retention damage outweighs any short-term headcount reduction benefits.
Executives say collaboration (68%), productivity (64%), and company culture (61%). Those are the official talking points.
But research contradicts these claims. No productivity gains. Collaboration works remotely. Culture data shows decline in employee satisfaction after RTO, not improvement.
The hidden motivations? Passive layoffs (25% admission rate), real estate pressure, management control preferences. Those are the actual drivers.
Here’s the disconnect. 76% of leaders say face-to-face work boosts engagement. 71% say it strengthens culture. 63% say it improves productivity. Yet there’s no solid proof five-day office policies improve business performance. Belief versus evidence.
74% of HR professionals said RTO mandates led to leadership conflicts. That’s internal acknowledgement of the disconnect. When HR and executives are fighting about policy, you know the justifications don’t hold up.
Glassdoor reviews show companies that issued RTO mandates saw meaningful decreases in employee satisfaction scores. The transparency gap creates employee distrust and damages organisational culture more than remote work ever did.
Many companies are using outdated management methods that prioritise visibility over actual performance. It’s micromanagement by attendance—measuring success by desk time instead of work completed.
If you’re evaluating workplace policies for your own organisation, look at actual data from your teams. Compare stated productivity concerns against measured outcomes. The gap between rhetoric and reality tells you what’s really going on.
You need to shift from presence-based evaluation to output-based measurement. Track what people deliver, not where they sit when they do it.
The DX Core 4 framework provides a comprehensive view across four dimensions: speed, effectiveness, quality, and impact. Leading companies use DORA metrics—deployment frequency, lead time, change failure rate, MTTR. These measure actual software delivery performance.
Developer velocity metrics matter. Sprint velocity, deployment frequency, pull request quality, code review thoroughness. Track focus time (uninterrupted blocks for deep work). Monitor context switching frequency. Analyse code quality metrics through automated tools.
Real companies are doing this. Dropbox uses Core 4 to align teams around measurable outcomes. Booking.com quantified a 16% productivity lift from AI adoption using these metrics. Adyen achieved measurable improvements across half its teams in three months using data-driven approaches.
OKR/KPI frameworks focused on business outcomes work better than activity monitoring. Performance analytics platforms can track contribution patterns regardless of location.
Async communication patterns provide visibility without surveillance. Documentation quality and response times show team effectiveness without badge tracking.
Organisations that rigorously track productivity gain competitive advantage by identifying bottlenecks, eliminating waste, and making smarter investment decisions.
The key is trust-based management with clear success criteria and regular feedback loops. When you have objective measurement, you remove the subjective justifications for RTO and enable evidence-based decisions instead.
Yes. Research found 25% of executives explicitly admitted hoping RTO mandates would trigger voluntary departures. This is the passive layoff strategy in action. It avoids severance costs and negative publicity associated with formal redundancies, though it risks losing top talent who have the most employment options.
This depends on your circumstances, career stage, and market options. Think about your role’s remote work viability, your company’s enforcement approach, your financial situation, and what alternative opportunities exist. High performers often have leverage to negotiate exceptions. Don’t make the decision in a vacuum.
Research shows 20-30% attrition rates following strict RTO announcements. This varies by industry and role type, of course. At Amazon specifically, 73% of Amazon employees indicated they would consider leaving if forced into office full-time. Those are significant numbers.
Research shows no measurable improvement in collaboration from RTO mandates. Collaboration can be equally effective remotely with proper tools and practices. In many cases, offices actually increased distractions, which reduced focused work time. The stated benefit doesn’t show up in the data.
Look for these indicators. Sudden mandates after years of successful remote work. Office space utilisation problems. Mandate timing that correlates with lease renewals. Or leadership that openly acknowledges “empty office” concerns. Office utilisation remains at 50-65% of pre-2019 levels despite RTO policies. That’s a lot of expensive empty space creating pressure.
This varies by organisation, but “hybrid creep” is a documented pattern where required office days gradually increase over time. Evaluate whether the hybrid policy has clear written commitments, flexibility in scheduling, and what leadership’s stated long-term intentions actually are. The trend data suggests executives want full-time office presence eventually.
Legal considerations include your employment contract terms, constructive dismissal claims, disability accommodation requirements, and geographic relocation expectations. Employees hired explicitly as remote may have stronger legal positions, but employment law varies significantly by jurisdiction. Talk to an employment lawyer if your contract specified remote work.
The surveillance is widespread. 34% of businesses implemented badge tracking and attendance monitoring. 32% factor in-office attendance into performance evaluations. 29% consider office presence for promotions and pay increases. This creates a compliance-based performance management system.
Replacement costs run 50-200% of annual salary for departing employees. Add decreased productivity from distractions and commute fatigue, reduced employee engagement, ongoing office space expenses, and competitive disadvantage in talent markets. The total cost often exceeds the savings companies hope to achieve.
Multiple factors drive this. Genuine belief in collaboration benefits despite contradictory evidence. Pressure from real estate commitments. Preference for visibility and control. The passive layoff strategy we discussed. And difficulty measuring productivity objectively. 83% of CEOs expect employees back full-time within three years, regardless of what the research says.
Yes, absolutely. Research shows culture can be built effectively in distributed teams through intentional practices: async-first communication, documentation focus, regular video interactions, clear values communication, and trust-based management. Remote and hybrid workers report 54% higher engagement rates. Culture isn’t about location—it’s about practices.
Present objective data. Show your team’s actual output metrics—velocity, deployables, business outcomes. Share research showing productivity maintenance or gains from well-managed remote work. Run a cost analysis showing retention and real estate savings. Provide competitive talent market data. And offer trial periods with clear success metrics. Make it about evidence, not preference.
Understanding the real motivations behind RTO mandates helps you make informed decisions about your own workplace policies. For a complete overview of the RTO landscape, including productivity research, retention impacts, and implementation strategies, see our comprehensive resource on return-to-office mandates in 2025.