The Floor or The Ceiling
The Cost of Avoiding Outcome Alignment
Construction technology companies must generate revenue from customers who cannot easily pay more.
This is the structural constraint of our industry.
This creates a choice about what to sell. Most construction technology companies choose to sell activity. This choice has institutional support. Horizontal SaaS playbooks from consumer software suggest neutrality wins. Investors pattern-match to companies like Salesforce, not to niche vertical software. The decision looks safe because it worked elsewhere. But construction is not elsewhere.
In construction, you can sell activity or you can sell outcomes.
If you sell activity, you charge for usage. Per seat. Per project. The customer pays as work is happening and the software makes that work easier to coordinate, document, or track. The software does not need to change whether the customer wins or loses. It just needs to be present when the work occurs.
The software can serve everyone. General contractors can use it. Subcontractors can use it. Owners can use it. No one is excluded by the software’s implicit assumptions about who should win or how margin should be distributed. The product is neutral.
Neutrality accelerates distribution. Uniformity and neutrality allows sales cycles to shorten as you are not asking anyone to make a structural bet on your business. You are asking them to coordinate better. Contractor objections are tactical, not strategic or structural. Adoption spreads horizontally across participants on a project. Revenue grows as long as construction activity on platform grows.
The business model is clean. Projects happen and the software gets used. You get paid because it doesn’t matter whether the contractor executing the project is profitable or not. The software is infrastructure for activity. Infrastructure gets paid simply for being there.
A durable floor. Revenue is predictable and churn is low because the software is embedded in how work gets done. The company grows with industry activity. Investors can model revenue with confidence and founders can minimize existential risk. The company becomes a utility.
The solution can’t command outcome-based pricing because success is not tied to outcomes. You can’t charge more when your customer wins a more profitable bid when your value prop is allow contractors to “document what happened on the last ten bids.” You can’t charge based on margin improvement because the software is not designed to improve contractor margin. It is designed to make activity visible and record decisions.
Pricing scales linearly. More seats = more revenue. More projects = more revenue. The relationship between customer growth and your revenue is one-to-one at best. Often it is less than one-to-one because as customers scale they want to negotiate volume discounts.
The software depends on fragmentation. Many buyers making independent purchasing decisions. The business model reinforces this—many small transactions instead of portfolio-level negotiations.
Fragmentation of software purchasing is also ending. Contractors are increasingly consolidating software spend at the enterprise level. What used to be hundreds of independent purchasing decisions across project teams is now fewer, centralized portfolio-level negotiations. Innovation, IT, software departments and operations leadership are standardizing toolsets to reduce redundant spend and improve data consistency across organizations. This software procurement consolidation accelerates pricing pressure on activity-based platforms. Volume buyers demand volume discounts while switching costs remain low. We see this in Procore's pricing concessions to Autodesk Construction Cloud users as a demonstration of this dynamic. Neutral platforms compete on price because they cannot compete on outcomes.
As the industry consolidates software spend, this business model weakens. Consolidation of purchasing within contractors means fewer buyers. Fewer buyers means fewer independent purchasing decisions. Larger customers mean portfolio-level negotiations. Portfolio-level negotiations mean pricing pressure.
In this world, customers must ask: does this software give us a structural advantage over our competitors? Does this software improve our margins, reduce our risk, accelerate our cash, or give us better control over portfolio outcomes?
If the software serves everyone, it is infrastructure. Infrastructure does not create competitive advantage for users. Infrastructure becomes table stakes. Table stakes compress pricing advantages to cost. Software that documents activity makes work more visible. It doesn't change the financial outcomes of that work, which means it can't provide structural advantage in winning, pricing, or executing.
At this point, the software loses leverage. The customer still needs it because work needs to be documented. But the customer does not value it the way they value systems that change their competitive position. The software is a cost center, not a growth driver, which means pricing compresses and strategic relevance diminishes.
The software structurally can’t participate in value capture because it’s designed to observe value, not create it. It cannot move closer to money or risk or control because it is neutral about who wins and who loses. Activity scales linearly. But when buyers consolidate their purchases, this model breaks. Optimizing for the floor forecloses the ceiling. The product decisions that maximize horizontal adoption, like neutrality, breadth, and activity metrics are the same optimizations that prevent outcome alignment. You fundamentally can’t serve everyone and make specific customers structurally better. You must choose between charging for activity and charging for outcomes. The business model that minimizes early risk maximizes late-stage exposure to a capped ceiling. Path A is capped.
To sell outcomes, you must tie your revenue to customer improvement. You can’t charge for usage. You charge for margin expansion, risk reduction, cash acceleration, or portfolio optimization. You do not get paid because work happened. You get paid because the work you delivered produced better financial results for the customer.
You can only sell to customers who can actually want to use your solution to become structurally better. This means customers who are scaling (or have ambitions to scale), who are sophisticated enough to care about financial outcomes at a portfolio level, who are willing to integrate deeply because the payoff is competitive advantage.
The addressable market is narrower. You are not serving all contractors. You are serving contractors who are trying to build durable advantages in a commodity business. Contractors that care whether their margin on the next hundred projects is three percent vs ten percent because that difference determines whether they can grow or whether they stagnate.
GTM becomes selective. You optimize for depth with specific customers who can actually use what you build. Early adoption is slower because you are asking the customer to change how they operate. You are asking them to embed the software in decisions that really matter. Pricing decisions. Staffing and overhead decisions. Risk assessment. Cash management. The software must work at a level where failure is costly and visible.
Product decisions have to become opinionated because you are trying to make specific customers better. The software must care whether the customer wins or loses. It must surface information that changes decisions. It must be designed around financial outcomes for customers, not around activity metrics.
You do not charge per seat. You charge based on value delivered. This only works if the software actually delivers real value. If it does not improve margins, if it does not reduce risk, if it does not accelerate cash, there is no fallback. You do not get paid for usage. You do not get paid for breadth and you are at risk for being exposed.
If the thesis is wrong, if the software does not make customers structurally better, the company fails. There is no durable revenue from activity. There is no wide adoption to point to. You picked specific customers. You tied your success to their financial outcomes. If they do not improve, you do not grow.
But if the software works, the ceiling is unbounded.
As the customer scales, the software's impact compounds. The absolute value delivered grows non-linearly as small per-project improvements aggregate into enterprise-level advantages. The software becomes embedded in how the company operates at a structural level because the aggregated value becomes irreplaceable.
And at the scale of contractors doing hundreds of millions in revenue to billions in revenue, this level dependency is structural. Switching costs become prohibitive. Customers cannot easily replace the software because the software is now part of how they think about risk, how they price work, how they staff, and how they manage cash across the portfolio.
Pricing power increases when value delivered increases faster than the customer’s increase in activity. You’ve earned the right to move closer to money and control. These are the only defensible positions in a commodity business.
There’s a future in which the industry consolidates, and in this world, this business model strengthens. Contractors aren’t looking for software that everyone uses. They are looking for an edge that makes them durably and structurally advantaged against their competitors.
Competitive advantage commands pricing power. Pricing power creates enterprise value. This is why Procore's ceiling exists where it does. Procore built infrastructure for a fragmented industry. It scaled to $1.3B+ in revenue by being everywhere. But its valuation multiple compressed from 25x revenue to 8x revenue as the market recognized it could not participate in the value concentration happening through consolidation. Procore documents activity for its customers. It does not make them structurally better than their competitors. That is the ceiling.
Building for outcomes instead of activity means accepting that you will not serve everyone. It means accepting an incredible amount of early friction, narrower markets, slower adoption, and higher expectations. It means accepting total exposure and failure if the thesis is wrong.
It also means participating in real value creation and real value capture instead of observing it. Customer alignment determines go-to-market, pricing, product, who you serve, who you exclude, and whether you digitize or change the industry.
Companies that choose Path A in a consolidating market face a specific failure mode: they become cost centers with compressing margins and weakening strategic relevance. They watch their largest customers demand enterprise-level advantages they cannot provide. They negotiate pricing down while switching costs continue to decrease. They remain venture-backable based on their growth patterns but they do not produce venture returns.
Companies that choose Path B face a different failure mode: total exposure if the thesis is wrong. If the software does not make customers structurally better, there is no fallback revenue. No breadth and therefore no floor.
The choice is between two types of risk. Obvious failure fast, or subtle deterioration.
Activity is a floor. Outcomes are a ceiling.
If you got value from this, the best way to support my work is to share it with one person who’d find it useful.