- Binding Constraint
- Customer acquisition cost must be amortized across a long-lived installed base protected by switching costs. Acquiring a customer requires substantial upfront investment in sales, onboarding, and integration. This investment is only recovered if the customer remains for multiple renewal cycles. The switching costs that protect the installed base are structural — data migration complexity, workflow integration depth, retraining burden, and ecosystem dependencies — not merely contractual. The entire economic structure depends on retention being high enough and long enough to justify acquisition spending.
- Capital Dynamics
- Capital is deployed in two distinct phases. First, heavy upfront investment in product development creates the software or service that will be sold repeatedly at near-zero marginal cost. Second, customer acquisition spending — sales teams, marketing, free trials, implementation support — is front-loaded against each customer cohort and recouped over multi-year subscription periods. Returns compound as the installed base grows because existing customers generate revenue with minimal incremental cost while new acquisition spending adds to the base. The capital-light balance sheet belies the capital-intensive customer acquisition cycle.
- Revenue Mechanism
- Revenue is formed through recurring subscription or contractual payments from an installed customer base. The structural mechanism is that customers pay periodically — monthly or annually — for continued access to software or services that are embedded in their operations. Revenue is predictable and cumulative: each retained customer adds to a growing base of recurring payments. Growth comes from expanding the installed base (new customers), increasing revenue per customer (upselling, price increases), and maintaining high retention. The revenue model produces high gross margins because the marginal cost of serving an additional subscriber is extremely low once the product exists.
- Cost Structure Rigidity
- The cost structure splits into two layers. Product development (engineering, infrastructure, security) is a high fixed cost that exists regardless of customer count and must continue to prevent competitive displacement. Customer acquisition cost (sales, marketing, onboarding) is technically variable but behaves as a fixed commitment because stopping acquisition means the installed base begins to shrink through natural churn. Cloud infrastructure costs are semi-variable, scaling with usage but with substantial baseline commitments. The dominant cost tension is between investing in product development to maintain switching costs and investing in acquisition to grow the base — both are structurally necessary and neither can be easily reduced without damaging the business.