Carta vs Forge When Your Buyer Pool Needs Vetting Too

Before modeling a tender at all, pull the confidentiality and vendor-security clauses in your largest client contracts. Some enterprise and government-adjacent clients require that any party with visibility into your ownership or financial structure pass the same vetting a new hire would, which can rule out an open institutional marketplace before you even get to price.

Carta's tender process keeps the transaction inside your existing shareholder group and the company's own broker-dealer relationship, so it rarely triggers a client's third-party access clause in the first place. For an MSSP whose whole value proposition rests on being trustworthy with sensitive access, keeping a liquidity event entirely internal is often worth the tradeoff of a smaller buyer pool.

If your largest clients are commercial rather than government-adjacent, or your contracts do not extend confidentiality obligations to your own cap table, Forge's institutional buyer network can still work, provided you run the same vetting question through legal before disclosure documents go out. Some institutional secondary funds are used to this kind of diligence and can accommodate it; others are not, so ask early rather than assuming.

A smaller, more restricted buyer pool tends to mean a wider pricing discount than a comparable SaaS company would see, since fewer eligible buyers means less competitive tension on price. Bring your 409A appraiser a realistic picture of how few institutional buyers actually clear your vetting bar before finalizing a number, rather than pricing off a benchmark built for companies without that constraint.

Whatever you decide, keep a written record of which clients' clauses you checked and what your counsel concluded, since a client audit or a future acquirer's diligence team may ask how you protected sensitive access during a prior liquidity event. Treat this the same way you would treat any other compliance decision: documented, dated and available if someone asks later, not a conversation nobody wrote down. A short memo naming the clauses reviewed, the conclusion reached and who signed off is usually enough; the point is having something concrete to produce, not building an elaborate file nobody will ever read.

Questions to answer before choosing a platform:

• Which of your largest client contracts include confidentiality or vetting clauses that reach ownership or financial data?
• Which institutional buyers, if any, could pass the same vetting a new hire would face?
• Does counsel's written conclusion on each clause sit in your compliance records with a date on it?
• Has your 409A appraiser seen how small the eligible buyer pool really is before you finalize a price?
• Have employees been told plainly why the buyer pool is smaller than at a typical startup tender?

Say an MSSP with $9M in annual recurring revenue has three federal-adjacent clients whose contracts require vetting of anyone with cap table visibility, alongside a dozen commercial clients with no such clause. The board runs a Carta tender funded from treasury, capped at a level the company can afford without external capital, and explicitly documents that the transaction never left the existing shareholder group. Two years later, when a larger commercial buyer approaches through Forge for a bigger transaction, the earlier documentation makes that second, more open process far easier to clear with the security-sensitive clients still on the roster.

Staff who hold equity generally do not know their own employer's client contracts include vetting clauses, and a vague explanation for why the buyer pool is smaller than a friend's startup tender can breed suspicion rather than confidence. Explain the constraint plainly during the disclosure walkthrough: certain clients require anyone with visibility into ownership to be vetted, which is exactly why the company protects that trust by keeping this transaction internal. Framed that way, most employees read the smaller buyer pool as evidence the company takes its security commitments seriously rather than as a limitation being hidden from them.

Once you have gone through the exercise of mapping which client clauses affect a liquidity event, feed that lesson back into how your sales team negotiates future enterprise and government-adjacent contracts. A narrower, clearly scoped vetting clause that specifically addresses systems access rather than broadly covering all ownership and financial information gives you more flexibility the next time a liquidity program comes up, without weakening the security commitment your clients actually care about. Bring your legal lead into contract renewal conversations specifically to test this language, since a clause written years ago by someone who never anticipated a cap table event is often broader than the client actually needed.

Compare a broader marketplace approach too.