Testing SaaS Scalability Before Investing

SaaS scalability due diligence starts with a question investors cannot afford to overlook: can the software platform support the growth promised in the business plan? A SaaS company may have established customers, recurring revenue and an ambitious expansion strategy, but that does not prove its technology can handle substantially more demand.

A platform that works well today may need considerable engineering work to support tomorrow’s customers, transactions, integrations and product features. Those requirements can affect operating costs, delivery schedules and the investment needed after acquisition.

The objective is not to find technically perfect software. It is to establish whether the technology and engineering team can support the proposed growth at a commercially acceptable cost and level of risk.

Takeaways

  • SaaS growth forecasts need technical evidence, not just customer and revenue projections.
  • Assess real usage patterns, performance limits and engineering capacity together.
  • Examine future infrastructure costs and the investment needed to support growth.
  • Distinguish manageable platform improvements from major redevelopment risks.
  • Use independent due diligence when technology uncertainty could materially affect the investment.

Table Of Content

Why SaaS Growth Plans Need Technical Evidence

The value of a SaaS business is often closely linked to expectations about future growth.

An investor may be considering a company with rising recurring revenue, a growing customer base and plans to enter new markets. The investment case may assume that additional customers can be supported without a comparable increase in technology expenditure.

That assumption needs testing.

Technology systems do not necessarily become more expensive in a predictable, straight-line relationship with customer numbers. Some costs may remain relatively stable as usage grows. Others may increase sharply when the platform reaches a capacity limit or requires a substantial change.

For example, a SaaS business may need to redesign part of its database, improve how background processing works or introduce new infrastructure to manage increasing demand.

The cost is not limited to cloud hosting. The engineering team must design, implement, test and maintain those changes while supporting existing customers.

EY Australia’s analysis of software technology due diligence identifies scalability constraints, technical debt and engineering capability as factors that can affect the value of software investments.

For an investor, the important question is not whether the company claims its platform is scalable. It is what evidence supports that claim.

Customer Growth Is Not System Demand

A common mistake is assuming that four times as many customers means four times as much work for the platform.

The relationship may be very different.

One customer might have ten employees using the system occasionally. Another could have hundreds of employees processing transactions continuously.

Customers may also consume different amounts of storage, reporting, processing capacity and third-party services.

A platform serving 500 small businesses might experience more demand from a single large enterprise customer than from dozens of smaller customers.

That is why scalability needs to be assessed against actual usage patterns, not simply projected customer numbers.

Growth Can Change the Product

The SaaS business may also plan to introduce features that change how the platform operates.

Examples include advanced reporting, customer integrations, automation, artificial intelligence or support for additional countries.

A new reporting feature could create demanding database queries. An integration with an external system might introduce processing delays or additional costs. Expanding into another market may create new data handling and operational requirements.

These changes can alter the technical demands placed on the platform, even if customer numbers remain relatively stable.

The growth plan therefore needs to consider both increasing usage and the technology required to deliver the future product.

Investor and technology adviser comparing SaaS growth forecasts with platform capacity information.
Reviewing SaaS Growth Projections

What Evidence Should Investors Request?

The first step is to compare the business growth forecast with what is known about the platform’s existing performance and capacity.

I would begin by requesting evidence in five areas: current demand, technical architecture, historical performance, future capacity planning and engineering capability.

The level of detail should reflect the size and maturity of the business being assessed.

A smaller SaaS company may not have extensive documentation or sophisticated monitoring. That does not automatically make it a poor investment. It does, however, affect how much confidence can be placed in its growth assumptions.

Current Usage and Demand

Ask for historical information showing how the platform is actually being used.

Useful evidence includes:

  • Active customers, users and transactions over time.
  • Peak concurrent usage and busy processing periods.
  • API requests and background processing volumes.
  • Data storage growth and database size.
  • Usage differences between customer types.
  • Application response times and error rates.
  • Performance changes during customer onboarding or major releases.

Not every metric will be relevant to every SaaS product.

For a document management platform, storage and document-processing volumes may be important. For a payment platform, transaction throughput, latency and reliability could be more material.

The aim is to identify the activities that drive demand and understand how those activities are expected to change.

Architecture and Infrastructure

Ask how the software is structured and where its major dependencies sit.

An architecture diagram can help explain how the application, databases, background jobs, storage, integrations and supporting services work together.

However, a diagram is not evidence that the architecture performs well.

I would also want to understand deployment arrangements, infrastructure configuration, operational monitoring and how the system responds when demand increases.

Important questions include whether the platform can add processing capacity, whether its database can support growing workloads and whether individual components create limits that affect the complete system.

A platform does not need to use the latest technologies or a complicated architecture to be suitable for growth.

Sometimes a relatively simple design is easier to maintain, more reliable and entirely adequate for the company’s plans.

The decision should be based on what the architecture can do, not how fashionable it looks.

Historical Performance

Review incidents, performance problems and service disruptions.

Has the platform become slower as customer numbers have increased? Have major releases caused outages? Have database problems or background processing delays affected customers?

Look for evidence of how the engineering team investigated and addressed these issues.

A system that has experienced problems is not necessarily a poor investment. Software businesses encounter technical difficulties as they grow.

What matters is whether the problems are understood, whether the team can resolve them and whether the same weaknesses are likely to become more serious under future demand.

Capacity Planning

Capacity planning connects expected workload with the resources needed to deliver acceptable performance.

The Microsoft Azure Well-Architected guidance on capacity planning recommends using historical demand, workload patterns and anticipated growth to estimate future requirements.

For an investor, I would want to see whether the company has converted its commercial forecast into measurable technical assumptions.

If management expects substantially more transactions, what additional processing and data capacity will be required?

If the business plans to sign larger customers, how will their usage differ from existing customers?

If those questions cannot be answered, the capacity forecast may be little more than an educated guess.

How Do You Test SaaS Scalability?

A credible scalability assessment combines current operating evidence with targeted technical investigation and testing.

It should not rely solely on management assurances or a supplier’s statement that the system is hosted in the cloud.

Cloud infrastructure can provide flexible resources, but the application must be designed and operated in a way that can use them effectively.

Understand the Performance Limits

The engineering team should be able to identify the components most likely to constrain growth.

These could include:

  • Application processing capacity.
  • Database queries, storage and connections.
  • Background jobs and processing queues.
  • External APIs and service limits.
  • Network performance.
  • Reporting and data processing.
  • Shared resources used by multiple customers.

The appropriate investigation depends on the architecture.

For example, adding application servers may improve capacity for some workloads but have limited benefit when the database is already the main bottleneck.

Similarly, upgrading the database may not address inefficient application behaviour or slow external integrations.

I would want to understand which components limit throughput, what evidence supports that conclusion and how the company proposes to address those limitations.

Review Load-Testing Evidence

Load testing examines how a system performs under defined levels of demand.

A useful test should model realistic user activity and transaction patterns rather than simply generating large numbers of artificial requests.

The results may include response times, transaction throughput, error rates and resource utilisation.

Microsoft’s performance testing guidance distinguishes between testing expected workloads, testing the system’s limits, assessing sudden demand spikes and examining performance over longer periods.

For investors, the important questions are straightforward.

What was tested? How closely did it represent actual customer usage? What happened when demand increased? Where did performance begin to deteriorate? What would need to change to support the forecast workload?

A test conducted several years ago, on a different version of the application or against a much smaller environment, may provide limited assurance about current capacity.

Examine the Database and Data Growth

Databases deserve particular attention because they often sit at the centre of a SaaS platform.

Increasing numbers of customers can mean more records, larger queries, additional concurrent connections and growing reporting workloads.

The company should understand how data volume and transaction activity affect database performance.

Questions worth asking include whether slow queries are monitored, whether database maintenance is managed and whether the data model supports the planned growth.

Also consider backup, recovery and data retention arrangements.

A database may have enough capacity to process today’s workload while becoming increasingly difficult or expensive to maintain as data accumulates.

Test Dependencies Beyond the Application

A SaaS product may depend on payment processors, identity providers, messaging services, external databases, APIs or specialised third-party software.

Even if its own infrastructure can scale, these dependencies may create limits.

A messaging provider might impose transaction limits. An external API may become slower under high request volumes. Additional usage could introduce charges that materially affect the cost of serving customers.

These dependencies should be reflected in the scalability assessment.

The question is whether the complete service can support growth, not merely whether one application server can handle more requests.

Will the Platform Remain Reliable?

Scalability is not only about handling more work. It is also about maintaining an acceptable service as demand increases.

A platform that doubles its throughput but experiences frequent outages may be unsuitable for customers who depend on it for critical operations.

Reliability requirements should reflect what the product does and how customers use it.

A scheduling application serving internal administrative teams may have different availability requirements from a platform processing financial transactions.

I would assess whether the architecture, operational procedures and support arrangements are appropriate for the business’s actual commitments.

Understand Failure and Recovery

Consider what happens when a server fails, a database becomes unavailable or an external service stops responding.

Can the application recover? Are backups maintained and restoration procedures tested? Does the team know how to respond to major incidents?

The AWS Well-Architected Framework provides a useful structure for examining reliability, performance efficiency, operational practices, security and costs.

The framework is not proof that a platform is well designed simply because it uses AWS services.

It provides questions and principles that can help assess the architecture against its business requirements.

Avoid Assuming Bigger Servers Solve Everything

One way to increase capacity is to use larger servers, often called vertical scaling.

This can be a perfectly reasonable approach for some workloads.

However, larger servers have practical limits. They may also become more expensive, and increasing their size does not automatically address poor database design, application inefficiencies or single points of failure.

Another approach is to distribute demand across additional processing resources, commonly called horizontal scaling.

That can offer flexibility, but it may require additional engineering work and introduce operational complexity.

Neither approach is automatically correct.

The key is whether the selected design can deliver the forecast capacity, reliability and cost requirements with acceptable risk.

Can SaaS Growth Remain Economically Viable?

A SaaS company may increase revenue while its technology operating costs rise even faster.

For an investor, this matters because the business plan may assume improving margins as customer numbers grow.

I would examine how technology costs have changed historically and what is expected to happen as demand increases.

Understand the Real Cost Drivers

Technology operating costs may include:

  • Cloud processing and database services.
  • Data storage and transfers.
  • Third-party APIs and transaction charges.
  • Monitoring, logging and security services.
  • Software subscriptions and licences.
  • Production support and specialist operational services.
  • Additional infrastructure needed for reliability.

The relationship between these costs and customer growth can vary considerably.

Some services charge according to usage. Others have fixed commitments, pricing tiers or capacity thresholds.

The business may also need temporary parallel environments, data migration or additional services to deliver major architectural changes.

Examine Cost Per Customer and Transaction

Total cloud spending is useful, but it can hide important trends.

I would look at appropriate unit measures such as technology cost per active customer, transaction, account or other meaningful workload.

The FinOps Foundation’s unit economics guidance recommends linking technology expenditure with the business activity or value being delivered.

This allows management to understand whether the platform is becoming more efficient as demand increases.

For example, if infrastructure costs rise while the number of transactions grows much faster, the cost per transaction may be improving.

Conversely, a platform that gains customers but experiences rapidly increasing processing and support costs may need further investigation.

These measures must be interpreted carefully.

Large enterprise customers may generate greater usage and support demands than smaller customers, so dividing total cost by customer count alone can be misleading.

Don’t Forget Engineering Expenditure

Infrastructure is only one part of the cost.

If the platform requires architectural changes, database redesign, new deployment processes or extensive performance improvements, engineering capacity becomes important.

The company must balance maintaining existing services with implementing the improvements required for growth.

That work may involve additional employees, contractors, testing, documentation or specialist expertise.

A growth forecast that includes higher recurring revenue but excludes necessary engineering investment may overstate the expected financial benefit.

Business and technology leaders reviewing SaaS customer growth and infrastructure cost forecasts.
SaaS Scalability and Operating Costs

Can the Engineering Team Deliver the Plan?

A technically capable platform can still fail to deliver the investment case if the engineering team cannot support the required work.

Investors should assess the people, processes and responsibilities behind the product, not just its source code and infrastructure.

A growth plan may involve substantial new features, customer integrations, performance improvements and operational changes.

Someone has to design, build, test, deploy and maintain all that work.

Review Development Capacity

I would begin by understanding the engineering team’s responsibilities and how its time is currently allocated.

How much effort goes into customer support and defect correction? How much is spent maintaining existing software? What capacity remains for new features and improvements?

A small team may deliver considerable value when responsibilities are clear and the software is maintainable.

However, a roadmap can become unrealistic when the same developers are expected to fix recurring defects, support customers, improve scalability and deliver major new features simultaneously.

Ask whether the planned work has been estimated and prioritised.

Also look at delivery history. Has the team consistently delivered its previous commitments, or does work routinely take longer than expected?

A confident roadmap is not a substitute for evidence of delivery capability.

Identify Key-Person Dependencies

Some platforms depend heavily on a founder, senior developer or small group of technical specialists.

That may have been manageable while the company was developing its initial product.

It can become a concern when the business grows and requires more reliable delivery, support and decision-making.

Ask who understands the architecture, database, deployment process and critical integrations.

Can other engineers maintain the platform? Is important technical knowledge documented? Can the business continue if a key person becomes unavailable?

The concern is not simply the number of developers.

It is whether knowledge, responsibility and operational capability are concentrated in a way that could affect continuity or growth.

Where the dependency is material, a Key Person Technology Risk Review may help clarify the exposure.

Examine Development Quality

A platform that is difficult to change may struggle to deliver the future product roadmap.

Useful evidence includes source code quality, automated testing, release practices, defect trends, documentation and the management of technical debt.

Technical debt refers to future work created by earlier design or implementation choices that make software harder to maintain or change.

Not all technical debt is unacceptable.

Teams often make sensible compromises to deliver features quickly or meet commercial deadlines.

I would be more concerned when the company cannot identify its important technical limitations, explain their consequences or demonstrate a practical plan for addressing them.

The investment question is whether the software can continue evolving economically, not whether every part of the codebase meets an ideal standard.

A Hypothetical Three-Year SaaS Growth Plan

Consider a hypothetical Australian SaaS company preparing for investment.

It currently serves 500 business customers and plans to increase that number to 2,000 over three years.

The management team expects to introduce new reporting features, attract larger customers and expand integrations with other business platforms.

Its investment forecast assumes that technology operating costs will grow more slowly than revenue.

These figures are illustrative, not market benchmarks or predictions.

The company may have a credible growth strategy, but several technical assumptions require testing.

Start With the Actual Workload

The first question is how today’s 500 customers use the product.

Perhaps most are small businesses that use the system for a few hours each day.

The growth strategy, however, includes larger organisations with substantially more users, higher transaction volumes and additional integrations.

Although the customer count is projected to quadruple, the technical workload might grow by a different amount.

The company needs to model that change using realistic customer segments and usage patterns.

Compare the Growth Scenarios

ScenarioWhat should be testedPotential investment consequence
Existing demandCurrent performance, operating cost and reliabilityEstablish the factual baseline
Forecast growthExpected customer mix, transactions, integrations and data volumesIdentify planned capacity and engineering expenditure
Higher-than-expected demandPeak processing loads, larger customers and sudden usage increasesIdentify limits and additional capacity requirements
Delivery delaysWhat happens if planned platform improvements take longerAssess whether commercial growth depends on unfinished technical work

The assessment should identify which assumptions are supported by evidence and which remain uncertain.

For example, the company might demonstrate that adding processing resources supports the forecast application workload.

However, load testing might reveal that database performance becomes unacceptable under heavier transaction demand.

The company may then need targeted database work before onboarding its largest planned customers.

That does not automatically make the business unattractive.

It does change the investment case if the work is expensive, uncertain or required earlier than management expected.

Examine the Delivery Schedule

The company also needs to demonstrate that its engineering team can perform the necessary improvements while continuing to deliver the commercial product roadmap.

If the business must postpone important customer features to address technical limitations, revenue growth could be affected.

If it hires additional engineers, the expected cost base may increase.

If it proceeds without resolving the limitations, service quality and customer relationships may be exposed to greater risk.

Each outcome has different commercial consequences.

This is why SaaS scalability due diligence should examine technical capability and the delivery plan together.

How to Judge SaaS Scalability Risk

I would avoid reducing the assessment to a simple claim that a platform is either scalable or not scalable.

Almost any software system can be changed with enough time, money and expertise.

The more useful question is what the business needs to do to achieve its growth plan, and whether those changes are commercially reasonable.

A practical decision framework can separate findings into three broad categories.

Growth the Platform Can Support

Evidence indicates that the existing architecture and operating arrangements can support the forecast demand within an acceptable range.

The engineering team understands the workload, has relevant monitoring and can explain how capacity will be managed.

Normal improvements and planned investment may still be necessary.

The important point is that the growth assumptions are supported by credible evidence.

Growth Requiring Manageable Investment

The platform has identifiable limitations, but the required improvements appear achievable with reasonable effort, cost and delivery risk.

Examples might include optimising database queries, improving background processing or expanding infrastructure capacity.

These findings should be reflected in the investment model and technology roadmap.

The investor needs to understand what work is required, when it must happen and how confident the company is in its estimates.

Growth Requiring Major Technology Change

The forecast depends on substantial redevelopment, architectural changes or engineering capability that the company does not currently have.

The limitations may affect critical parts of the platform or require a lengthy period of investment before the planned growth can be supported.

This does not necessarily mean the transaction should be abandoned.

However, the investor may need to reconsider valuation, funding requirements, timing, execution risk or the conditions of the investment.

The difference between these three categories is not a universal technical threshold.

It is the relationship between the platform’s capability, the proposed business plan and the investor’s tolerance for cost and risk.

Investor and technology adviser discussing SaaS scalability risks and investment options.
SaaS Investment Risk Assessment

Warning Signs Worth Investigating

There are several findings that would make me investigate a SaaS growth forecast more closely.

These are warning signs, not automatic reasons to reject an investment.

  • No reliable usage information. The company cannot explain how demand has changed or what resources its customers consume.
  • No meaningful performance evidence. Capacity claims depend on opinion rather than monitoring, testing or operational experience.
  • Unclear scaling limits. The engineering team cannot explain which components are likely to constrain growth.
  • Increasing costs without explanation. Cloud and third-party expenditure rises, but management cannot relate the increase to customer activity or business outcomes.
  • Repeated performance problems. Important incidents continue without clear investigation or corrective action.
  • A roadmap without delivery capacity. The company promises major features and technical improvements without sufficient engineering resources.
  • Excessive dependency on individuals. One developer or founder holds critical knowledge needed to maintain or expand the platform.
  • Unfunded redevelopment. Management acknowledges major architectural changes but excludes their cost and timing from the growth plan.

I would also investigate situations where the seller cannot provide reasonable technical information.

Sometimes evidence is unavailable because the business is immature or has limited documentation. In other cases, access may be restricted for legitimate confidentiality reasons.

The assessment should explain these limitations rather than assuming that missing information proves either good or bad technology.

What Should a Due Diligence Review Produce?

Technology due diligence should translate technical findings into information the investor can use.

A long report describing servers, programming languages and system diagrams has limited commercial value if it does not explain how those findings affect the investment.

I would want the assessment to address five questions:

  1. Can the existing technology reasonably support the forecast growth?
  2. What technical limitations or dependencies could prevent that growth?
  3. What investment and engineering work may be required?
  4. What operating costs and risks are likely to change?
  5. Which uncertainties remain, and how could they affect the transaction?

The findings should distinguish confirmed evidence from assumptions, estimates and matters that could not be verified.

Important risks should have a clear explanation of their potential business consequences.

Where possible, recommended actions should identify timing, dependencies and the further investigation needed before costs can be estimated reliably.

The final decision remains with the investor and their commercial, financial and legal advisers.

A technical assessment should improve that decision, not pretend to replace it.

When Independent SaaS Due Diligence Helps

An independent technology assessment may be worthwhile when the platform represents a material part of a company’s value and the investment case relies heavily on future growth.

It is particularly relevant when the investor lacks the technical experience needed to challenge management’s assumptions.

A company’s existing CTO or engineering leader may provide valuable information about architecture, capacity and delivery plans.

However, investors may still want an independent perspective on whether that evidence adequately supports the investment thesis.

The purpose is not to criticise the engineering team or demand unnecessary redevelopment.

It is to understand what the business has built, what it can realistically support and what additional investment may be needed.

At White Internet Consulting, my Technology Due Diligence service focuses on assessing material technology risks and capabilities before important commercial commitments.

A properly scoped review can consider software architecture, infrastructure, technical debt, engineering capability, operational dependencies and the assumptions behind future growth.

The depth of assessment should match the investment and the evidence available.

A smaller transaction may justify a focused review of the most important risks. A major software acquisition may require more detailed technical investigation involving specialist expertise.

What Happens After the Investment?

Scalability findings should also inform the company’s priorities after the transaction.

If the platform has manageable limitations, the business may need a clear plan for improvements before launching new features or onboarding larger customers.

If engineering capability is constrained, management may need to reconsider delivery priorities, staffing or supplier arrangements.

A practical Technology Strategy can connect these findings to investment priorities and a realistic roadmap.

The important point is that technical improvements should be linked to business outcomes.

There is little value in replacing a working platform simply because newer technology exists.

Likewise, postponing necessary improvements indefinitely may expose the business to more expensive disruption later.

My guiding principle is people before technology.

For SaaS businesses, that means considering the engineers who maintain the platform, the customers who depend on it, and the leaders responsible for turning an investment plan into sustainable results.

The best technology decision is the one that helps those people deliver the business objectives with acceptable cost and risk.

Frequently Asked Questions

What Is SaaS Scalability Due Diligence?

SaaS scalability due diligence assesses whether a software platform, infrastructure and engineering team can support anticipated growth. It examines current performance, technical limitations, future capacity, operating costs and the investment required to deliver the growth plan.

Can SaaS Scalability Be Proven?

Testing and operating evidence can provide confidence about defined workloads, but they cannot prove that every future growth scenario will succeed. A credible assessment identifies supported assumptions, known limits and remaining uncertainties.

Do Investors Need Source Code Access?

Not every initial assessment requires direct source code access. Architecture documentation, operational records, testing results and engineering interviews can provide useful evidence, although restricted access may limit conclusions about implementation quality and maintainability.

Is Cloud Hosting Enough for Scalability?

No. Cloud services can make additional capacity available, but the application, database, integrations and operating arrangements must be capable of using it effectively. A poorly designed workload may remain constrained even when more infrastructure is added.

When Should Due Diligence Begin?

Start early enough for material findings to influence valuation, investment requirements, transaction conditions and post-acquisition plans. If the growth forecast depends on unproven technical assumptions, investigate them before committing capital.

Make SaaS Growth Assumptions Investable

A strong SaaS investment case needs more than attractive revenue projections. It needs credible evidence that the platform and engineering team can support the proposed growth at a commercially sensible cost.

If you are considering an investment or acquisition involving a SaaS business, I can help assess the technical assumptions, identify material risks and clarify what additional work may be required. Book a free technology consultation to discuss the transaction and whether an independent assessment would be worthwhile before you commit.

The goal of SaaS scalability due diligence is to understand whether the technology can support the business you expect to build.

Share This Post

Need Technology Due Diligence support?

Major technology decisions can involve significant cost, risk and long-term commitments. An independent review can help you understand what you are really committing to before you proceed.

If you need an independent assessment of a software platform, technology investment, development partner or proposed solution, take a look at my Technology Due Diligence service or Contact Us to start the conversation.

Iain White Technology Due Diligence Adviser

Technology decisions can look straightforward on paper. The risks often become clearer once you look beneath the surface.

As a Technology Due Diligence Adviser, Iain White helps business leaders independently assess technology before making significant investments, acquisitions or commitments.

Drawing on more than 35 years in technology, Iain reviews areas such as software architecture, delivery capability, technical debt, security, scalability, costs, team dependencies and technology risk.

His focus is not simply on identifying problems. It is about giving decision-makers a clear view of what they are buying, what risks they are taking on, and what may need to change.

Through White Internet Consulting, Iain provides independent technology due diligence without being tied to a software vendor, development agency or particular technology solution.