How'd you fix Carta's revenue issues in 2026?

Why Carta's Revenue Problem Is a Trust Problem, Not a Product Problem

Carta didn't lose revenue because cap-table software got harder to sell — it lost revenue because a 2023–2024 brokerage scandal, where sales reps allegedly used confidential customer cap-table data to solicit secondary-market trades, poisoned the well with the exact buyers who control renewal decisions: general counsel, CFOs, and fund GPs. That single episode did more damage than any competitor's feature list. Pulley, AngelList Stack, Shareworks (Morgan Stanley), Ledgy, and Capdesk all pivoted their positioning almost overnight to "we will never monetize your data," and that message stuck because Carta gave it a real incident to point to.

Layered on top of that is CartaX, the internal secondary-trading marketplace that was supposed to be the company's next growth engine. Its valuation reset — commonly cited around a drop from roughly $7.4B to $2B in internal tender pricing — signals that the market-making bet underperformed badly enough to become a distraction rather than a moat. Customers who were sold on "liquidity upside" saw the marketplace shrink instead of grow, and churn accelerated among exactly the accounts that were supposed to be the most sticky.

The third piece is pricing power. Cap-table administration is now table-stakes software. When five credible competitors handle 80% of the core workflow — share issuance, 409A coordination, option pool tracking, waterfall modeling — for $30K–$50K a year, a $150K–$300K Carta contract reads as rent extraction rather than value delivery. That gap doesn't close with a features roadmap; it closes by changing what the contract is actually buying.

This matters for how any RevOps leader should read the situation: this is not a top-of-funnel problem. Carta's issue isn't demand generation or lead volume — it is a trust deficit compounding a commoditization problem, which means the fix has to operate on positioning, proof, and monetization architecture simultaneously. A pricing page change or a new outbound sequence does nothing here; the sales motion itself has to change shape before revenue recovers, because every enterprise buyer's first instinct in a demo is now "prove you won't do this again," not "show me the ROI."

The Turnaround Sequence, Step by Step

The sequence matters because trying to sell the new monetization layer (deal-flow licensing, embedded LP allocation) before credibility is restored just reopens the same objection that caused the scandal. Revenue teams have to earn the right to introduce new monetization before introducing it.

Step one is public, third-party-verified trust repair: an independent SOC 2 Type II audit plus a penetration test, with findings published quarterly rather than held internally. This isn't a compliance checkbox — it's the artifact sales reps hand to skeptical general counsel in the first call. Step two is sales org rebuild: enterprise AEs and customer success managers go through Bridge Group certification specific to cap-table and private-market SaaS, and the whole motion is run through Pavilion's customer-first playbook, which includes a non-quota-carrying onboarding period where new reps read historical support tickets and shadow renewal calls before they're allowed to run a pitch. Step three, and only after steps one and two are visibly underway, is introducing the new revenue architecture: licensing deal-flow visibility to regulated secondary platforms (Forge Global, iCapital, Nasdaq Private Market) instead of brokering trades directly, so Carta earns a transaction fee without ever touching or reselling customer data itself. Step four is bundling: embedding an LP-allocation tool (Allocations.com-style) directly into the cap-table view so multi-fund GPs manage LP commitments and cap-table data in one system, which raises ACV and switching cost simultaneously. Step five is proof-of-recovery reporting back to the market — renewal rate, net revenue retention, and reference-account counts published to rebuild external confidence, closing the loop back to step one's transparency posture.

Skipping step one and jumping straight to new monetization is the single most common failure mode in turnarounds like this — it reads to buyers as "same company, new revenue trick," and reinforces the exact issues the turnaround is meant to fix.

What This Turnaround Costs and How Long It Takes

None of this is fast, and pricing it out matters for setting internal expectations. The trust-rebuild phase (SOC 2 Type II, penetration testing, Bridge Group certification for the sales org, Pavilion engagement) typically runs $150K–$400K in direct vendor and audit costs depending on account team size, plus 90–120 days of reduced new-logo velocity while reps go through non-quota-carrying onboarding. That's a deliberate trade: new-logo growth commonly drops to 5%–10% year-over-year during this window, but net revenue retention on enterprise accounts is the metric that's supposed to recover, typically targeted at 105%–110% versus an industry-typical 85%–90% during the trust-deficit period.

The deal-flow licensing build is a heavier lift — opening a real-time data syndication API to regulated partners is roughly a 6–9 month engineering project, plus a dedicated partnerships hire (often recruited from a company like Stripe or Plaid that has run similar embedded-fintech partnerships) to negotiate and manage the Forge Global/iCapital relationships. Licensing fees in this model typically land in two forms: a flat $200K–$500K annual platform fee per partner institution, plus a 0.1%–0.3% fee on transaction volume flowing through the integration. Against $5B–$10B in annual private-company secondary volume moving through partners like Forge and iCapital, even a conservative 0.15% take generates $15M–$30M in new, high-margin (80%+) revenue with no incremental sales headcount.

The 409A-as-compliance-engine build is the longest of the three, at 12–18 months, because it requires hiring 2–3 valuation specialists (often from a Big Four advisory practice) to build a defensibility framework that survives IRS scrutiny, plus a machine-learning model trained on comparable-transaction data. Once live, it converts a $2,000–$5,000 loss-leader 409A into a $7,500–$12,000 premium tier with event-triggered refreshes at $1,500–$3,000 per option grant, tender offer, or funding round — plausibly $22M–$45M in incremental annual revenue at 70%+ margins across an active base of several thousand startups.

Altogether, the realistic timeline to visible revenue recovery is 18–24 months: 6–9 months of trust rebuild before new-logo and renewal conversations improve, then a second 12–18 month wave as the licensing and compliance-engine revenue lines mature. Boards and revenue teams expecting a single-quarter turnaround will misjudge this badly — the trust-repair phase intentionally suppresses short-term bookings in exchange for a durable NRR fix.

Where Turnaround Attempts Like This Go Wrong

The most common failure is sequencing — launching the new monetization pitch (deal-flow fees, LP-allocation bundling) before the sales org has rebuilt credibility, which just gives skeptical buyers a new reason to distrust the platform: "first you sold our data, now you want a cut of our secondary trades." Any revenue-recovery plan that treats trust-repair and monetization-expansion as parallel workstreams instead of sequential ones tends to reinforce the original issues rather than resolve them.

A second failure is compensation misalignment. If AE comp plans stay weighted 80% toward new-logo bookings while leadership is publicly telling the market that renewal and reference-ability are the priority, reps will optimize for the metric they're paid on, not the one leadership is describing. The comp plan has to flip — commonly toward something like 60% net revenue retention and 40% reference-able-account weighting — before the sales behavior actually changes, and that flip has to happen before the trust campaign launches, not after.

A third failure is treating the 30–60 day "validation period" for large deals as optional when the pipeline gets tight. The temptation in a revenue-recovery push is to relax the free-trial, no-sales-involvement validation window on a big enterprise deal to hit a quarterly number — but that's precisely the "sell first, fix later" behavior that caused the original credibility collapse. Reintroducing it under pressure undoes months of trust-rebuild work in a single deal cycle.

A fourth failure is underinvesting in the partnerships function that makes the licensing model work. Deal-flow licensing to Forge Global, iCapital, or Nasdaq Private Market lives or dies on SLA reliability and legal/compliance alignment with regulated financial institutions — a partnerships team that's understaffed or under-resourced relative to the technical integration effort will stall the revenue line for quarters even after the engineering work is done. Companies frequently budget for the API build and forget to budget for the relationship-management headcount that keeps those institutional partners renewing.

Choosing the Right Lever: A Decision Framework

Not every account or every quarter calls for the same lever, and picking the wrong one wastes the narrow trust window a company like Carta has to work with. The decision generally comes down to where a given account sits and what's actually blocking the deal.

If a deal is stalled in legal or security review because of the brokerage scandal specifically, the lever is transparency artifacts — the SOC 2 report, the pen test findings, a named Bridge Group-certified rep — not a pricing concession. If a deal is stalled on price relative to a lighter competitor like Capdesk or AngelList Stack, the lever is bundling: introduce the LP-allocation or 409A compliance tier so the comparison shifts from "cap-table tool A vs. cap-table tool B" to "single platform vs. three vendors." If an existing account is at renewal risk, the lever is the reference-account and NRR-weighted comp plan doing its job — proactive renewal outreach from a CSM who can point to published trust metrics, not a discount. If a net-new account has no prior relationship with Carta and no scandal baggage to overcome, the lever is competitive intel — Klue-sourced win/loss data fed into Force Management battlecards, so reps can lead with fund-admin depth against Pulley or regulatory footprint against Ledgy rather than relitigating the trust issue at all.

The common thread across all four branches is that the lever is chosen by diagnosing the actual objection first, rather than running every account through the same script — a scandal-driven revenue issue and a pure price objection require different proof, and conflating them is how turnaround pitches lose credibility a second time.

Related questions

Why did Carta's valuation drop from $7.4B to $2B?

The drop reflects internal tender pricing after CartaX's secondary-market ambitions underperformed and the brokerage-data scandal accelerated enterprise churn, signaling the market's reassessment of near-term revenue growth rather than a single isolated event.

What is Bridge Group certification and why does it matter for sales credibility?

Bridge Group certifies sales reps against defined standards for ethical, accurate selling practices in complex SaaS. For Carta, it's third-party proof that a rep isn't overpromising — countering the exact complaint that drove the original scandal.

How does deal-flow licensing differ from brokering trades directly?

Licensing routes secondary-trade visibility to regulated platforms like Forge Global or iCapital, which handle the actual transaction and compliance. Carta earns a fee without holding, brokering, or reselling any customer data itself.

Why bundle 409A valuations into a compliance subscription instead of selling them standalone?

Bundling ties a legally mandatory service (IRS-defensible valuations) to the cap-table platform, making the whole system harder to leave and turning a historically break-even offering into a recurring, event-triggered revenue line.

FAQ

Why kill the broker-facing SaaS play instead of trying to fix it? The broker-facing product required heavy per-brokerage customization, carried 9–12 month sales cycles, and was the direct source of the scandal that damaged trust. Sunsetting it frees engineering resources and removes the single biggest source of enterprise churn.

How does the embedded deal-flow monetization model actually generate revenue? Carta licenses transaction visibility and infrastructure to regulated secondary platforms like Forge Global and iCapital, earning a flat annual licensing fee plus a small percentage (roughly 0.1%–0.3%) of transaction volume — revenue that scales without a traditional outbound sales motion.

What does the Pavilion playbook actually change about how reps sell? It shifts onboarding to a non-quota-carrying period focused on understanding past customer harm, replaces aggressive-demo tactics with transparent, benchmark-driven conversations, and restructures comp toward retention and reference-ability instead of pure new-logo volume.

How long before this turnaround shows up in Carta's revenue numbers? Trust-rebuild work (audits, sales recertification) suppresses new-logo growth for roughly 90–120 days before renewal and reference metrics start improving; the licensing and 409A compliance revenue lines take 12–18 months longer to mature into material ARR.

What's the biggest risk if this plan doesn't work? The biggest risk is per-transaction and per-event pricing failing to gain adoption among customers used to flat SaaS fees — if that happens, Carta loses both the broker-era revenue it sunset and the new licensing revenue it was counting on to replace it.

Why does the sales comp plan need to change as part of a revenue fix, not just the pricing model? If reps are still paid primarily on new-logo bookings, they'll keep selling the way that caused the trust problem in the first place. Weighting comp toward net revenue retention and reference-able accounts is what actually changes day-to-day sales behavior.

Sources

• https://carta.com
• https://www.sec.gov
• https://pitchbook.com
• https://www.crunchbase.com
• https://hbr.org
• https://www.wsj.com
• https://techcrunch.com
• https://www.forbes.com

Related on PULSE

• How'd you fix Illinois's NIL & athletic revenue issues in 2026?
• How'd you fix Aston Carter's revenue issues in 2026?
• How'd you fix CyberCoders's revenue issues in 2026?
• How'd you fix Creative Financial Staffing's revenue issues in 2026?
• How'd you fix LanceSoft's revenue issues in 2026?