A SaaS Strategy That Keeps Growth From Becoming Waste

Growth should increase what the business can do, not simply what it pays Salesforce. A useful SaaS strategy makes that distinction before new licences, products and contract commitments are approved. It connects spending to demand that has an owner, a delivery date and a credible purpose.

For CFOs, CIOs and procurement leaders, the challenge is not to stop expansion. It is to support the right expansion without making every forecast permanent. That requires a shared way to decide what to buy now, what to defer and what would justify the next commitment.

What a growth-ready SaaS strategy needs to decide

A budget sets a spending limit. A strategy explains which capabilities deserve funding and how the business will know they are working.

Start with the business change, not the product request. A larger sales team may need more access to an existing Salesforce setup. A new service operation may need different functionality. A proposed product launch may need a limited pilot before it needs a wider licence commitment. These are different commercial decisions, even when they arrive in the same budget submission.

Each request should answer three questions: what work will change, who will use the capability and when those users will be ready. If the answers are vague, the purchase is probably ahead of the operating plan.

A SaaS strategy becomes useful when it distinguishes a supported business requirement from a forecast that still needs testing. Approving the direction does not have to mean approving the entire licence volume or contract term immediately.

Separate confirmed demand from possible demand

Growth forecasts contain different levels of certainty. An approved hire with a start date is not equivalent to a proposed team expansion awaiting funding. Yet both can find their way into the same licence estimate.

Use a simple demand classification before discussing quantities with Salesforce. The following is a planning framework, not a rule about what any supplier will agree to.

Demand category	Evidence to require	Purchasing approach
Confirmed	Approved users or workload, an accountable owner and a delivery date	Establish the required entitlement and purchase timing
Likely	A supported business plan with unresolved hiring or deployment dependencies	Seek pricing visibility and assess staged purchasing options
Exploratory	A possible use case without an approved rollout	Test the requirement before making a wider commitment

Keep these categories visible in the forecast rather than collapsing them into one number. Finance can then distinguish the cost of approved growth from the cost of buying ahead of it.

This is where a SaaS strategy earns its place in planning: it preserves the ambition of the growth forecast without treating every assumption as a purchase instruction.

Put a date on the requirement

Demand should have a readiness date as well as a quantity. Hiring, configuration, security review and training can all affect when paid access becomes useful.

Ask the business owner for the earliest realistic deployment date and the dependencies that could move it. Procurement can then explore purchase timing against that evidence. If a supplier offers better pricing for an earlier or larger commitment, assess the whole financial effect, including the period before the capability will be used.

Make expansion a staged decision

A request for additional licences should be checked against usable capacity already held. That does not mean treating every inactive account as spare. Some access supports infrequent but necessary work, while some licences cannot serve the proposed role.

Salesforce’s guidance on licence types helps explain why entitlement matters. A licence count alone does not establish whether a new user can perform the required work.

A hypothetical growth decision

Suppose a team holds 100 licences, has 80 verified users and expects 30 new starters. Assume the remaining 20 licences are genuinely available, suitable for those roles and assignable under the applicable terms.

Ten starters have confirmed dates. The other 20 depend on hiring approval. Buying 30 more licences immediately would ignore existing capacity and the uncertainty in the forecast.

The first ten can use available capacity. If all remaining hires proceed, total demand would reach 110, creating a requirement for ten additional licences rather than 30. Procurement would still need to confirm availability, price and purchase timing for that later addition.

A SaaS strategy should make this demand reconciliation routine, not a one-off saving exercise. The licence audit before renewal provides a useful evidence base, but the growth decision must also account for future roles and deployment dates.

Give each commitment a clear owner

Shared accountability works only when individual decisions have named owners. Otherwise, finance approves the budget, IT enables access and procurement signs terms, while nobody owns whether the purchase becomes useful.

The business sponsor should own the requirement and adoption plan. IT should validate the technical fit, entitlement requirements and readiness to deploy. Finance should test affordability and the assumptions behind the business case. Procurement should assess the commercial commitment, available alternatives and consequences of changing the plan.

These are decision responsibilities, not four separate approval queues. Teams can agree them in a short purchasing brief rather than creating another committee.

That brief should record the capability being funded, expected users or workload, purchase timing, full committed cost and the next review point. For a substantial expansion, it should also explain what happens if adoption is late or demand is lower than expected.

The practical test of a SaaS strategy is whether anyone can explain why a commitment was made and what evidence would justify expanding it. A discount is part of that explanation, not a substitute for it.

Measure value without penalising useful growth

Total Salesforce spend can rise for good reasons. A business adding productive users or adopting a capability it genuinely needs should not be judged only on whether its invoice fell.

Use measures that separate growth from waste. Depending on the capability, these might include:

• Cost per verified active user: Use a defined activity window and role-specific criteria, not login frequency alone.
• Cost per supported business activity: Use a relevant measure such as cases handled, with a clearly defined cost scope.
• Time from purchase to productive use: Track how long paid capacity waits for deployment and meaningful adoption.
• Capacity awaiting an approved use: Distinguish an agreed operational buffer from licences with no current purpose or owner.

These measures need interpretation. Cost per user can increase when the business adds necessary functionality. A falling unit cost can still conceal a larger unused commitment. Neither movement proves success or failure by itself.

Compare each measure with the assumptions recorded at approval. If a rollout was expected to reach a defined group by a certain date, check whether that happened and why. The response may be better training, a revised rollout or a different future purchase, rather than an immediate licence reduction.

A SaaS strategy should therefore track both commercial exposure and business use. That gives finance a clearer account of spending and gives IT space to explain what adoption actually requires.

Protect the ability to change the plan

Growth plans change. Hiring can slow, deployment can slip and an approved use case can turn out to need a different product. The commercial question is how much of the original plan has already become an obligation.

Before approving an expansion, establish what the applicable documents say about additional purchases, renewal, quantity changes, pricing and notice requirements. Check whether a new purchase changes dates or introduces dependencies elsewhere in the agreement. Do not assume that a lower future requirement automatically creates a right to reduce fees during the term.

Salesforce publishes its standard agreements and related legal documents, but the signed order forms and incorporated terms applicable to your organisation need their own review. A current public document should not be assumed to replace the terms already agreed.

A SaaS strategy needs to treat flexibility as something to evaluate alongside price. A larger discount may not compensate for a commitment that outlasts the business requirement. Equally, a longer term may be reasonable for stable, well-understood demand.

Compare realistic scenarios rather than discount percentages alone: expected demand, delayed deployment and lower adoption. For each, identify the cost the organisation would remain committed to and the decisions it could still change. That makes the trade-off visible before signature.

Review growth before the next purchase, not just at renewal

Renewal is an important commercial checkpoint, but it is too late to be the only point at which growth assumptions are challenged.

Keep the approved demand forecast alongside actual deployment and upcoming purchase requests. Before each material addition, check whether earlier capacity has been used, whether the new requirement remains confirmed and whether the proposed purchase changes the existing commercial position.

A short recurring review can focus on exceptions: delayed rollouts, purchases arriving earlier than expected and demand that has changed materially. The frequency should reflect the pace of hiring and deployment, not an arbitrary reporting calendar.

A SaaS strategy stays useful when the forecast is revised as evidence changes. It should not preserve last quarter’s assumptions simply because they supported an approved budget.

As renewal approaches, bring that evidence into the Salesforce renewal process. Procurement can then work from a defensible future requirement rather than treating the current contract quantity as the default. Finance and IT also enter discussions with the same account of what the business needs.

Frequently asked questions

Does a SaaS strategy have to reduce total spending? No. It should improve the relationship between spending, business requirements and contractual exposure. Total cost may rise with useful growth. The concern is spending that gets ahead of confirmed demand, remains unused or creates obligations the business no longer needs.

How far ahead should Salesforce demand be planned? Plan across the relevant contract and business-planning horizons, but show uncertainty explicitly. Near-term deployment requirements deserve different treatment from growth that depends on future approvals. Extend the forecast far enough to understand commitments without presenting distant estimates as confirmed purchases.

Can unused Salesforce licences support new growth? Sometimes. First confirm that the licences are genuinely available, appropriate for the required roles and assignable under the applicable terms. Existing capacity can reduce the need for additional purchases, but it does not automatically create a refund or a right to reduce a current commitment.

Make the next growth decision easier to defend

Before approving the next Salesforce expansion, ask for confirmed demand, usable existing capacity, deployment timing and the full commercial commitment. Those four pieces of evidence will do more for the decision than a discount viewed in isolation.

SaaSed supports Salesforce contract and SKU reviews, usage audits and renewal preparation. If you want to test whether your current commitments support the next stage of growth, book a complimentary Salesforce audit conversation.