A technology company may have a popular product, growing revenue, and a strong sales pipeline, yet still see declining profitability each year.
This situation is more common than it appears. While product and financial success are related, they are not identical. A product may generate demand without delivering sufficient returns on the capital invested to build, sell, implement, and support it. As long as revenue grows, this gap can remain unnoticed for an extended period.
This issue is especially challenging for technology companies because costs are often separated from the revenue they generate. Acquiring a new customer requires marketing and sales resources.
Onboarding involves implementation work. Serving the account uses cloud infrastructure and support capacity. Product commitments add further development work. If you focus only on revenue, a customer may appear valuable. However, a complete economic analysis can reveal a very different picture.
Growth can hide weak unit economics
Rapid growth often drives its own narrative. As customer numbers increase, so do the needs for sales, development, infrastructure, and support. Rising costs may seem like an inevitable result of expansion.
Sometimes this is true. However, a CFO must determine whether the company’s economics improve with growth. Customer acquisition cost illustrates this point.
While companies often view CAC as marketing spend, the true figure includes all costs to acquire a customer: sales salaries, commissions, marketing, implementation, and other resources needed to convert a prospect into a paying account.
This figure is only meaningful when compared to the customer’s contribution after delivery and support costs. The same logic applies to CAC payback. A customer may be profitable over time but still create immediate cash challenges. The longer it takes to recover acquisition costs through contribution margin, the more capital is required to fund growth.
No single payback period defines a healthy technology business. Factors such as contract length, retention, customer segment, implementation needs, and access to financing all play a role. What is essential is that management understands these dynamics.
Revenue growth can be misleading if each new customer cohort requires more sales capacity, onboarding, cloud resources, and support. While revenue rises, so does the cash needed to sustain it.
For a CFO, the key question is not just, “How fast are we growing?” but, “What are the economic effects of adding the next customer?” If the company cannot answer this, growth alone does not prove a scalable business model.
When profitable products subsidize unprofitable projectsConsider an anonymized composite of an established technology company with several profitable core products. As the business grew, it also invested in new products, bespoke customer developments, and internal platform projects. Each initiative appeared reasonable on its own, while the company remained profitable overall. The problem was that engineering time, cloud usage, and support resources were not consistently attributed to individual initiatives. Some projects generated revenue but had negative contribution margins. Others continued without a defined commercial milestone. Their costs were absorbed by departmental budgets and ultimately funded by cash generated by the core products. As margins declined, the consolidated P&L showed the effect but not the cause. Project-level reporting finally made the cross-subsidies visible and allowed management to distinguish deliberate strategic investments from projects that had continued simply because their full cost had never been assembled. The lesson was not that every unprofitable project should be killed. It was that every subsidy should be visible, intentional, and time-bound. |
Project-level budgeting makes the losses visible
When profitability is assessed at the product and project level, budgeting shifts from merely controlling costs to evaluating whether the original investment case remains valid.
Each significant initiative should have a defined budget, funding period, named owner, and clear expected outcome. For mature products, this may be contribution margin or retention; for new products, it may be achieving a commercial milestone that justifies further investment. Regular plan-versus-actual analysis is essential. Overspending alone provides limited insight; the key is understanding why the project deviated from the plan.
Development may have required more work than anticipated. Hiring could have occurred earlier, while revenue was delayed. Customer adoption might have been slower, infrastructure costs underestimated, or pricing adjusted. The product may also have shifted enough from its original scope that the initial business case is no longer relevant.
These differences are important because they require different responses. A project that is delayed but still economically viable is not the same as one whose market has disappeared. Project reviews should not be limited to a choice between continuing or canceling.
Management may reduce scope, delay hiring, adjust pricing, target a new customer segment, or separate a software product from related services. Funding can also be released in stages instead of being fully committed upfront. The key change is that continued spending becomes an active decision, not an automatic extension based on previous funding.
When a startup grows before understanding the economics
The same problem appears in a more concentrated form in early-stage companies. Consider a software startup that raised its first investment round and immediately did what startups are expected to do: hired people, developed the product, and acquired customers. Revenue grew, as did the customer base. From the outside, the company appeared to be gaining momentum.
However, the founders had not calculated fully loaded CAC, contribution margin, or CAC payback, nor had they modeled the impact of hiring on cash runway. The annual budget tracked spending speed but not outcomes. Acquisition costs were not linked to customer cohorts or channels, and recurring software revenue was combined with implementation-heavy work. As a result, the company knew its burn rate but not its true economic model.
By the time finance reconstructed the economics, much of the initial funding had already been spent. The response was not just to cut headcount. The company first reduced spending on acquisition channels without acceptable returns, narrowed development scope, and separated recurring product economics from services work. The company then aligned its hiring plan with runway and commercial milestones.
The lesson is straightforward but often overlooked during rapid growth: a budget shows how much a startup plans to spend, while unit economics reveal whether that spending is justified.
Better capital allocation does not begin with layoffs
When margins decline, headcount is often the most visible cost and the first to be reduced. While this can quickly improve the P&L, it does not address the core issue: which activities should continue to receive funding?
Without clear insight into which products, customers, and projects generate acceptable returns, broad cost reductions risk cutting resources from both strong and weak initiatives. The core allocation issue persists.
Other options exist. Teams can shift from low-return projects to profitable products. Product scope can be narrowed. Hiring can be delayed until commercial milestones are met. Pricing can be adjusted when implementation or support costs make certain customers unprofitable. Cloud commitments and third-party costs can be reviewed. Separating software and services economics can also provide clarity.
The CFO’s role is not to block investment in projects that are currently unprofitable. New technology products often need years of investment before delivering returns. The CFO should clarify the trade-offs: how much capital the company will commit, what outcomes are expected, and what evidence would prompt a change in direction.
This requires treating capital allocation as an ongoing decision, not just an annual budgeting exercise.
For each significant product or project, CFOs should be able to answer a concise set of questions:
|
