How do you answer "what if your startup goes under?"

Answer it before they ask, in writing, with a one-page continuity plan: how they get their data out, what happens to their contract if you shut down or get acquired, how much notice you'll give, and how long you can run. Buyers who ask this have usually watched a vendor disappear. A plain exit plan shrinks the fear faster than any reassurance.

Why do buyers worry about startup vendors?

Because it happens, and it happens to well-funded companies too.

TechCrunch reported on May 20, 2025 that Builder.ai, once worth over $1 billion and backed by Microsoft, was entering insolvency proceedings and appointing an administrator. Customers of a vendor that disappears inherit a migration project nobody budgeted for.

And someone inside the buyer picked that vendor. That's the real fear behind the question. Your champion is the one who has to explain the decision if you fail, so the question underneath is whether choosing you could hurt them.

So answer the desire underneath: they want to pick the better tool and still look smart a year from now.

What goes in a continuity plan?

One page. Seven items.

1. Data export. What they can export, in what format, how often, and whether they can do it themselves without a support ticket.
2. Exit rights. What happens to their contract if you shut down or get acquired, including prepaid fees. Set these terms with your counsel.
3. Wind-down notice. How much notice you'll give before shutting down the service, and what export help comes with it.
4. Source code escrow, for core deals. A third party holds your code and releases it to the customer on defined events, like insolvency. It's overkill for small deals and a strong answer when your product runs something critical.
5. Runway and funding. A plain sentence. More on this below.
6. Security posture. Link the packet you already send for security reviews.
7. Who else runs on you. A reference or two, if you have them, from customers who'd take the call.

How do I talk about runway without scaring them?

Plainly, and in one or two sentences.

"I have [X] months of runway at current burn, and revenue covers [Y]% of costs." If you can't share numbers, share what you can: who your investors are, when you last raised, and whether you're profitable or on a path to it.

Founders who dodge this make it worse. A vague answer sounds like a secret. A plain answer, even a modest one, sounds like someone who knows their business.

When should I bring it up?

Before they do, once the deal reaches a real evaluation.

Put the continuity page in the proposal or in your security packet. Say one line about it on the call: "Since you're buying from a startup, here's exactly what happens to your data and contract if something happens to us."

A question you answer first sounds like confidence. The same answer, given only after they push, sounds like you were hoping they wouldn't ask.

What if they still want a bigger vendor?

Ask what would make the risk small enough, then build it into the deal structure.

• A shorter first term. Six months or a year instead of three years.
• A paid pilot. Scoped tight, with a clear decision at the end. Here's how to run one without giving away the work.
• Escrow for the deals where your product is critical.
• Stronger exit rights if you're acquired.

Use structure, not discounts. A lower price doesn't make you less likely to fail. A shorter term and a clean exit actually reduce their risk.

Some buyers will still pick the incumbent. Let them. Log the term and the renewal date, because they may come back when the incumbent disappoints, as covered in when to go back to a deal you lost.

What mistakes make the objection worse?

• Getting defensive, as if the question were an insult.
• Overclaiming. "We'll be around forever" is a promise nobody believes.
• Promising contract terms your counsel hasn't approved.
• Hiding what happens on acquisition. Buyers ask, and a dodge here kills trust.
• Treating it like the build-it-in-house objection. That one is about capability. This one is about the champion's risk.

What should I do this week?

1. Write your one-page continuity plan.
2. Run your own data export end to end and fix anything slow or broken.
3. Decide your position on escrow and acquisition terms with counsel.
4. Add the page to your proposal template.
5. Practice a two-sentence runway answer out loud.

Builder.ai was once worth over $1 billion and backed by Microsoft. Your buyer knows a big valuation guarantees nothing. Show them the exit plan, and the small vendor looks safer than they expected.

Start Signals, Convert, Grow

FAQ

What is source code escrow?

An arrangement where a neutral third party holds a copy of a vendor's source code and releases it to the customer if defined events happen, such as the vendor going out of business.

Should a startup share runway with a prospect?

Share what you're comfortable defending: months of runway, funding status, or profitability. A plain answer builds more trust than a polished dodge.

How do I answer "what if you get acquired?"

Say what the contract allows: whether they can leave, what happens to prepaid fees, and what notice they'll get. Put it in writing on the continuity page.

Does this objection go away after you raise a big round?

It gets quieter, and it doesn't go away. Well-funded companies fail too. Keep the continuity page in every proposal.