My coverage ratio was 1.8x against a 3x target, and a board member asked about it before I'd finished my second slide. I spent ninety seconds stammering about "headwinds," and watched the room's confidence in me drop faster than the number itself.
Why founders freeze on this question
The panic isn't really about the ratio. It's that most founders walk into the meeting with a number and no plan for what happens when someone asks about it. So the first instinct is to defend it, explain it away, or bury it in caveats about deal timing. All three read as evasive, even when the underlying business is fine. A board that trusts your read on a bad number will give you room to fix it. A board that thinks you're spinning a bad number starts asking for weekly updates instead.
The three-part answer that actually works
The founders who handle this well aren't hiding a better number. They're using a fixed structure that turns a scary metric into evidence they're on top of the business. It has three parts, always in this order.
- Name the real number first, unprompted. Say the ratio and the target in one sentence before anyone asks: "Coverage is 1.8x against our 3x target this quarter." Volunteering it signals you're not surprised by it. Waiting to be asked signals the opposite.
- Reframe with the weighted number, not the raw one. Raw pipeline value treats a deal in discovery the same as one in final negotiation, which is why the topline ratio looks scarier than reality. Follow the raw number immediately with the weighted one: "Weighted by stage probability, effective coverage is closer to 2.4x, and the gap is concentrated in two deals I'm tracking closely."
- Commit to one action with a date, not a vibe. Close with what you're doing about it and when they'll hear back, not a general assurance. "I'm reviewing the two largest deals with the rep this week and will have an updated read by next Friday's update" is a commitment. "We're pushing hard on pipeline generation" is not.
What this sounds like in the room
Board member: "Your pipeline coverage is under 2x this quarter. Should I be worried?"
Founder: "Correct, raw coverage is 1.8x against our 3x target. Weighted by stage, it's closer to 2.4x, and about 60% of the gap sits in two enterprise deals that are both in final procurement. I'm reviewing both with the rep this week, and I'll have a firmer read on close probability by next Friday's update. If either slips, I'll flag it immediately rather than wait for the next board meeting."
That's four sentences. It names the number, reframes it honestly, isolates the actual risk, and commits to a specific follow-up. Nobody in the room needs to ask a second question, because you already answered the one they were actually worried about: do you know what's happening in your own pipeline.
Phrases to cut before you walk in
Two habits sink this conversation every time. The first is vague reassurance: "we're confident," "it's still early," "the team is pushing hard." None of these are falsifiable, and an experienced board member hears them as a founder who hasn't looked closely at the number. The second is a jargon dump: walking through every stage definition and CRM field before getting to the actual answer. If the first thing out of your mouth after the question isn't the number itself, you've already lost the room's patience.
Prep this before your next board meeting
Calculate your weighted coverage number ahead of time, not live in the meeting. If you haven't built that formula yet, here's how the real coverage math works once you move past the generic 3x rule. Know your two or three largest open deals by name and stage before you walk in, since they're almost always where the follow-up questions land. And if you haven't scrubbed the pipeline in the last month, do that first: a quick zombie-deal check before the meeting means the number you're defending is at least real.
Frequently asked questions
What if the coverage ratio actually is bad, not just misunderstood?
Then say that too, using the same structure. "Coverage is genuinely thin this quarter, weighted or not, and here's the specific plan to close the gap" is still a stronger answer than deflection. Boards forgive a bad number handled directly far more often than they forgive being caught off guard by one.
How much deal-level detail should I give?
Enough to show you know the specifics, not so much that you're reading a CRM export out loud. Naming the two or three deals driving the gap, their stage, and your confidence level is usually the right depth. Save the full deal history for a follow-up question, not the initial answer.
What if I don't have a weighted-coverage number yet?
Build it before the meeting, not during it. A rough version, applying a probability estimate per stage to open deal value, takes under an hour to put together and is far more credible live than promising to calculate it later.
Should I bring this up before they ask?
Yes, whenever coverage is below target. Put it on the slide with the same three-part structure, unprompted. It's a stronger position than waiting for the question, and it usually shortens the conversation instead of extending it.
The number in the deck was never really the question. What your board is actually asking, every time, is whether you can be trusted to see a problem before it becomes one. A four-sentence answer that names the real number, reframes it honestly, and commits to a specific next step is how you show them the answer is yes.