Most CX problems enterprises invest in solving are not unique. The authentication friction banks face, the appointment scheduling complexity in healthcare, or the journey orchestration gaps in retail are industry-wide challenges. When a company spends hundreds of thousands building a solution, it is often creating something many others would pay to use.
The traditional procurement model captures none of that value. Organizations fund the development, vendors deliver the system, and ROI is measured only through internal improvements like reduced costs or higher customer satisfaction.
According to Gartner, 18–25% of enterprise development budgets go toward solutions that could be commercialized across an industry but never are, simply because procurement models are not designed to treat software as a revenue-generating asset.
Co-build equity partnerships change that equation. Instead of funding technology purely as an expense, organizations share development costs, retain equity in the solution, and turn CX innovation into both an operational improvement and a potential revenue stream.
Strip away the venture capital terminology and the startup jargon, and co-build partnerships are straightforward. Instead of hiring a vendor to build something you'll own and use internally, you partner with a development firm to build something you'll own majority equity in and commercialize across your industry.
The commercial model has three components that work together to align risk and reward between you and your development partner.
When you hire a vendor through traditional procurement, their quote includes their profit margin. A project that costs them $200,000 in actual development expense might be quoted at $500,000 because that 60% markup is how software companies make money. In a co-build model, the development partner works at cost plus overhead with no profit margin on the build phase. That $500,000 quote becomes $200,000 in actual development cost.
You're paying for the engineering work, the design effort, the project management, and the operational overhead to deliver it. But you're not paying vendor profit margin. Instead of taking profit on the build, the partner takes equity in the outcome.
Because the development partner is working without profit margin on the build, they receive minority equity in the intellectual property created. You retain majority ownership, typically between 60-80% depending on the specific structure of the partnership and the relative value each party contributes. The IP doesn't live in the vendor's product portfolio. It lives in a joint venture entity where you're the majority stakeholder.
This creates fundamentally different incentives than traditional vendor relationships. The development partner succeeds when the solution succeeds in the market, not when they maximize billable hours or upsell additional services. You succeed when the solution generates commercial value, not just when it improves internal metrics.
When you license the solution to other companies in your industry, revenue splits according to equity percentage. If you own 70% and your development partner owns 30%, that's how licensing revenue divides. Your CX innovation investment generates recurring revenue that flows back to you based on your majority stake.
Consider a healthcare system that needs a patient experience platform integrating appointment scheduling, pre-visit preparation, post-visit follow-up, and care plan management. This isn't a unique problem. Every health system deals with patient journey fragmentation. The traditional approach would be to budget $600,000, hire a vendor, build the platform, and use it internally.
In a co-build model, the economics look different. The development cost at cost-plus-overhead might be $250,000. The healthcare system retains 70% equity. The development partner takes 30% equity instead of profit margin on the build. Once the platform is deployed and validated internally, they license it to other health systems in non-competing markets.
A regional health system with 500,000 patients annually might pay $75,000-100,000 per year to license a proven patient experience platform rather than building their own for $600,000. If the solution gets licensed to just three other health systems in the first year, that's $225,000-300,000 in annual recurring revenue. At 70% equity, the original healthcare system receives $157,500-210,000 annually.
Their total investment was $250,000. First-year licensing revenue at their equity percentage covers 63-84% of the initial investment. By year two, they're profitable on the development cost while also benefiting from improved patient experience in their own operations. The platform continues generating licensing revenue for as long as other health systems find value in it.
Compare this to the traditional model: $600,000 invested, zero revenue generated, ROI justified entirely through internal operational improvements that are notoriously difficult to quantify in financial terms.
The same pattern applies across industries.
Not every customer experience initiative makes sense as a co-build partnership. Some CX improvements are genuinely unique to your business model or so specific to your operations that commercializing them would be impossible. The co-build model works when three conditions align.
If you're the only organization that faces this particular friction point, there's no commercial market for a solution. But if your competitors, partners, or companies in adjacent sectors deal with the same challenge, you're solving a problem with market demand. Patient scheduling complexity in healthcare, authentication friction in financial services, service appointment management in field operations—these are industry-wide challenges with commercial potential.
Some CX improvements are so intertwined with your specific technology stack, business processes, or organizational structure that adapting them for another company would essentially mean rebuilding from scratch. Those don't work for co-build. But if the solution addresses a common workflow, uses standard integration patterns, and solves the problem in a way that's valuable to others without major customization, it has commercial viability.
If there are only two or three other potential customers in your industry who might want this solution, the licensing revenue probably doesn't justify the go-to-market effort. But if there are dozens or hundreds of potential customers—health systems, banks, retailers, manufacturers, logistics companies—then the market size supports building with commercialization in mind.
Co-build partnerships are not without tradeoffs. Understanding what you're giving up and what you're gaining matters for evaluating whether this model makes sense for your specific situation.
What you're trading: Traditional procurement gives you 100% ownership of the solution built. Nobody else has equity. All decisions are yours. If you choose to commercialize later, all revenue is yours. In a co-build model, your development partner has minority equity. Commercial decisions require alignment. Revenue is shared according to equity split. You don't own 100% of what gets built.
You're also trading speed-to-market in some cases. Traditional vendor procurement might move faster if you're willing to pay premium pricing for dedicated resources. Co-build partnerships typically work in 90-day sprints with clear milestones, which can be faster than traditional enterprise software projects but requires more active participation from your team throughout the process.
What you're gaining: Development cost at cost-plus-overhead instead of vendor markup means 40-60% cost reduction on the build itself. Instead of $500,000, you might invest $200,000-250,000 for the same capability. That cost savings alone often justifies the model even before considering revenue potential.
You're gaining alignment of incentives with your development partner. They succeed when the solution succeeds commercially, not when they bill more hours. This creates partnership dynamics where both parties are invested in building something that works well enough to generate market demand.
Most importantly, you're gaining revenue potential that traditional procurement doesn't offer. Your CX innovation becomes an asset that generates licensing revenue, creates commercial value, and delivers ROI through both internal improvement and external monetization.
The implementation path for co-build partnerships follows a structured process that validates market demand before committing to full development and commercialization.
You and your development partner map the customer experience challenge, validate that it's an industry-wide problem, identify potential commercial customers, and size the addressable market. The output is a business case that quantifies both the internal CX improvement value and the external commercial opportunity. This phase answers whether co-build makes strategic sense before significant investment.
You serve as the anchor customer, meaning the solution gets built to solve your specific CX challenge first. This validates product-market fit in a real operational environment. The development follows the same design-build-validate process as traditional software projects, but at cost-plus-overhead pricing and with you retaining majority equity in the IP being created.
The IP gets transferred to a joint venture entity. You and your development partner establish go-to-market strategy, identify initial commercial customers, and begin licensing. Revenue generation starts when other companies begin paying to use the solution you validated internally.
This phased approach de-risks the model. You're not committing to commercialization before you know the solution works. You validate internally first, prove the value, and only then shift to commercial licensing when you have working software and validated use cases.
Contact Condado to explore whether your next CX initiative qualifies for co-build partnership.
Understand the trade-offs of consolidating CRM and CCaaS with Salesforce Agentforce, including integration benefits and maturity risks.
Learn how AI can streamline physician referrals, reduce leakage, and improve patient experience across complex healthcare systems.
