You send it Sunday night: "Would love your thoughts on our GTM." Monday morning: four confident paragraphs about not hiring a VP of Sales until the founders have closed thirty deals themselves, plus a book recommendation. None of it is unreasonable. None of it is about you. It would have been equally true of any of the eleven companies this person advises.
The reflex is to assume they phoned it in. Usually they didn't. You handed them a topic, and a topic has exactly one available answer: the modal one.
Why the generic answer is the honest answer
An advisor or non-executive director is, functionally, a pattern-matcher running on a stale cache. They see many companies; they see yours in a two-hour block once a quarter, plus whatever stuck from a deck you sent in March. The compression is what makes them valuable — it lets them recognise your situation as an instance of something seen before.
So when the question is "thoughts on GTM," the only thing available to retrieve is the base rate: what is usually true of companies resembling the one they remember. Fast, authoritative, and no better than a podcast. The specific answer becomes available only when you hand them something the base rate fails to explain. That is your job, not theirs. Four moves.
Ask about a decision, not a topic
"Thoughts on GTM" is a topic. "We're choosing between hiring one senior AE in October and putting the same money into two more months of founder-led selling, and I commit by the 20th" is a decision.
The difference isn't politeness, it's tractability. A topic has no closing condition, so answering it well is unbounded — and unbounded tasks get deferred or answered with generalities. A closed list is a multiple-choice question a busy person can answer between two meetings. The general form is in how to ask for a decision so you actually get one.
Give them the two or three facts that break the pattern
Then the facts that make the default answer wrong. The test is mechanical: would this change the advice? If yes, include it; if not, cut it, however proud of it you are. In the hiring example, the pattern-breakers might be that your sales cycle runs nine months rather than three weeks, that both founders are already at capacity on existing accounts, and that the pipeline you'd hire against sits in two logos. An advisor holding those three facts cannot give the generic answer; it visibly doesn't fit.
You'll be tempted to add the history — how you got here, what you tried in Q1. Cut most of it. History is what you'd say in the room; what is true right now is what they need.
Say what you're leaning toward
"I'm leaning toward the AE hire. I'd flip if we can't get an October start, because then we're paying for ramp through the quarter that matters."
People skip this out of misplaced deference — surely you shouldn't prejudge the question you're asking. But advisors are far better at attacking a position than generating one cold. A stated lean converts their task from "produce a strategy" to "find the flaw": easier, faster, likelier to surface what you missed.
It is diagnostic, too: a specific lean that still draws a generic reply tells you how much attention this relationship holds.
An introduction is not an opinion
The word "input" hides three requests that spend completely different things — one costs an advisor time, one costs them credibility, and one is not really an email at all:
- An opinion. Ten minutes of their judgment. The cheapest of the three, and the only one you should expect on a Sunday night.
- An introduction. This spends their credibility rather than their time. A real cost, and one that deserves its own explicit request, with enough detail that they can forward your words unedited.
- A formal sign-off. If you need a decision your company records rather than someone's view of a problem, an email between meetings is the wrong vehicle however well written — and what requires formal process is a question for your counsel or company secretary, not a matter of writing.
Naming it in the first line prevents the common misfire: you wanted an intro, they gave you an opinion, and neither of you noticed for a week.
What the format does that tone can't
All of this works in plain email. The reason to reach for a structured briefing is that two of the moves stop depending on how well you phrase things at 11pm.
A briefing carries the ask as a field, with a response shape — decision, opinion, review — and an honest urgency beside it. "Opinion, by Thursday, and here's what I do if I don't hear" becomes a property of the message rather than a tone you have to strike. It also resists urgency inflation: mark three things urgent that weren't, and the fourth one, which is, gets opened on Friday.
Assumptions do work too. Work the decision through with your assistant first and each one arrives labelled as stated by you or inferred by your AI. An advisor reading "inferred by sender's AI: pipeline concentration persists through Q1" knows where to push — and pushing on your assumptions is among the highest-value things they do. Same move as breaking a deadlock with a cofounder: the written form makes disagreement land on something specific rather than a mood.
The honest limit
The best advisor input often doesn't come from writing at all. It comes from twenty minutes in which they ask three questions you didn't anticipate, and the second reframes the decision. No format produces that.
So write the specific ask when you understand the decision well enough to frame it. When you don't, ask for the twenty minutes — as its own request, with one line on where you're stuck. "I can't frame this one cleanly; can we talk Thursday?" beats four paragraphs pretending you can.
If you'd rather have the ask, the urgency, and the labels handled as fields than as tone, connect your assistant.